No because the Tadfri integration is still live and I didn’t delete the old light, so when moving to MQTT it gets a new ID.
Is it as simple as giving the new light the same ID? Would that work? Also can I just do that from the UI or do I need to do it in one of the config files?
Ok well that seems much easier than what I was attempting to do yesterday 
I’ll give another light a go on my lunch break.
Weird side story, I’m mostly IKEA, the value for money against reliability makes it a no-brainer for me.
Anyway I was decorating a room earlier in the year and I got a bit of paint on one of the bulbs. Wiped it away with a cloth, and then watched on as the bulb completely burnt up before my eyes and turned black. It was the most bizarre thing but clearly I’d triggered some sort of chemical reaction in the bulb to kill it.
Question for anyone who uses Alexa for voice control of devices you have connected to Home Assistant: Which approach do you take? Do you pay for the Home Assistant Cloud Service, or do you take one of the manual approaches? Is your approach working well?
Which of the manual options do you use?
I pay for nabu not because it’s complex for me to setup but more to support the project.
Lots of recent updates from me.
It’s interesting because the setup process and overall UI is pretty intimidating, but now that it’s up and running, I’m finding it much much easier to use.
As an example, pairing one remote to control 4 bulbs was absolutely infuriating in the IKEA setup, you had to hold the pairing button near the bulb and hope it would bind to the correct bulb without dumping your previously binded bulbs. But in MQTT it’s super simple to do via the UI.
I’ve had a few IKEA smart bulbs die now, GU10 and E27 style. I also have reset the IKEA bulbs by mistake too many times when I cut and connect power.
Hue is expensive, but the quality is superior in my opinion. This doesn’t stop me impulse purchasing the IKEA stuff though 
Generally my default is Hue devices paired with Zigbee2mqtt to Home Assistant.
I’m very happy with this setup.
What are the key benefits of Zigbee2MQTT over ZHA?
Is it simply wider device compatibility or is there more to it than that?
I started out by using ZHA, this was 3+ years ago, and generally it was buggy and unreliable for me. So I switched to Zigbee2mqtt and it’s been rock solid since.
I can’t remember the issues I ran into as it was a long time ago. I imagine ZHA has improved since then though.
Hi there! I’m a big fan of HomeKit and have connected multiple devices through it, mostly using Homebridge to integrate non-compatible products. While it generally works, I find it a bit tedious because configurations can be hit or miss. I’m considering using Home Assistant for my next devices but would love to know if it’s easier to use compared to Homebridge, especially after reading some articles comparing the two—could you help me make a decision?
I haven’t personally used Homebridge so I can’t really comment on that aspect, but Home Assistant allows you to create really deep level automations for pretty much any smart home device. If you prefer to use HomeKit, Home Assistant has a HomeKit Bridge integration that will expose your devices to HomeKit even if they’re not natively supported.
I tried to read that article by the way, but I had to give up after a few paragraphs because it’s so badly written. I’m sure someone will come along here with some more useful opinions or resources.
It’s time 
Everyone agrees that having your mug in Home Assistant is essential, right?
It’s really just a reason to play around with ESPHome and bluetooth proxies.
Getting everything into HA is the way to go. I’ve got a toothbrush in there somewhere.
Now I’m curious, what does a smart toothbrush expose to HA?
Was it you that was making heavy use of Google Home over HA a year or so ago?
Now I’m picturing a progress bar via LED strip lighting 
