This should come in a 2.0 update "before Christmas"
TimeWalker
joined 1 year ago
In the article, it specifically mentions "Business users" and I can torally agree on that. Not many people use iMessage here in the EU or Switzerland anyway and for business I would say practically zero. I have seen bussiness use Threema, Wire, Telegram, Slack or Google Meet.
And heck, if businesses here have customer live chat with messenger, it's either WhatsApp or Facebook Messenger.
I personally never had to use iMessage after the rise of WhatsApp - neither privately nor in bussiness.
Were you able to get the orange one for yourself?
I got myself the green one and my partner the red one. Pretty excited to get them!
As far as I know, since 2019 the Hue bulbs or lights are Zigbee + Bluetooth. I haven't heard of a Bluetooth-only bulb yet
Since the Hue bulbs are using the Zigbee standard, you can still safely buy them in the foreseeable future and just connect it with something like SkyConnect, zzh!, Conbee, etc. and use it with Home Assistant
That's totally true, though, in this case with LEDs I feel like the rebound effect is less of a problem here. The LEDs are not only using less electricity, but they're far brighter with addition to using less electricity for that brightness. It means that even if somebody decides to fill their room with 5 LED lamps with 806 lumens instead of 1 incandescent bulb, they'll still waste less energy - in addition with 5 LED lamps of 806lm making your room look like the sun is shining inside.
At least with Firefox Quantum (v57) they have tried to continuously bring in optimizations to bump the performance. In the meantime there has been lots of work with WebRender, a newer and more robust Javascript Engine and better CSS engine which made it get faster every update. Being quite fast and snappy isn't just a placebo since Firefox has lately started to get better Speedometer scores than Chrome
What you could do is have one of the HAs install the custom integration remote-homeassistant. However, even then it would mean that you have to somehow make your instance available outside e.g. VPN, port forwarding, cloud service, ...
This one connects with the instance directly via a long-lived token and allows you to control and read date from the other instance. The good thing though: The configuration.yaml way allows you to specificially include or exclude entities. So with that you could technically only send the entities from slimmelezer+ without having to pass the other info.
I would say the only caveat would be that because the long-lived token is somewhere on the other house's instance, they could technically take it and send commands randomly to your instance :P Maybe with an extra user you could maybe limit the permissions or something similar and create the long-lived token there - haven't tried it though, just a thought.
That's the solution if you immediately tried to login and it didn't work.
Twitch login has in general very misleading error messages. The exact same message with unsupported browser also appears if you take too long to login