Don’t forget power loss recovery, which is why only Hue reside in the bedrooms of our home. Also the fact that even the not so reliable Hue button controllers, which do fall off the Hue mesh as well, but through some kind of programming magic, are seamlessly rejoined nearly instantly without user intervention. In the three years I’ve been using Hue lights, I have only had one light stop responding to commands, because it died.
A while ago now I bought a second HE hub in order to transfer my Hue setup (including rules) from my Hue bridge. There may be one or two contact sensors or Samsung buttons on the new HE hub, but apart from that it is only Hue bulbs and accessories. While it took some getting used to in terms of what apps / rule setup was best to use within the new HE, I am very happy with the result. Reading this and other recent threads I have toyed with the idea of moving the lights back to the Hue bridge, but I don't have any driving need to at this stage.
The thing I would throw into the mix of this conversation is that it may still pay to get a second HE hub to setup lighting rules, depending on your setup. I kept and still use my original C-4 hub for LAN-based integrations such as my weather station, air conditioner, Maker API -> InfluxDb outputs, etc. These can, at times, get a little bogged down in terms of resources on this hub, but they at least don't interfere with the performance of the C-7 running my lighting rules.
Simon
Well, don't forget the elephant in the room; keep iot devices updated which is handled well by the bridge. I have yet to find something that would update my directly HE connected bulbs as the bridge and app can.
I don't know about the bulbs, since I only have 2 paired direct and they are still on latest available f/w (according to Hue, not HE), but I know HE has in the past gotten f/w updates for at least the sensors -- I've updated my directly-paired motion sensors via HE.
I'm guessing HE's updates are not available as soon as Hue drops stuff (it may take a while to trickle down), but it is possible to get Hue updates via HE.
This is a very old thread. While some of the principles may still apply, there is a lot that has changed in the last 3 years. That's not to say you may still experience the update issues, but I would suggest finding a more recent topic or creating a new one.
Same. My Hue motion sensors were updated using HE. With that said, these days, I maintain an installation of zigbee2mqtt simply to update device firmware. It is very easy to reset a zigbee device, join it to z2m, update the firmware, and then rejoin it to HE.
I can't udpate the firmware on a hue outdoor motion sensor through HE. Tried resetting the device a few times and it starts the process and never gets past 80%, then errors out. Could you share how to update through zigbee2mqtt.
Finally got the firmware updated through HE after many attempts. I read in one of the posts here in the forum to be persistent, and I was. After changing from channel 20 to channel 25 and 15 - 20 attempts, it finally made it to 100%. Didn't change anything in the device configuration but seen progression in the logs with most attempts. No more errors and the zigbee mesh seems to be stable. Puzzled, but it worked....
You'd need to install zigbee2mqtt using one of the methods detailed here:
Thanks. I'll create a new one that is more focused on the issue with directly connected devices and what methods are being used to for them to receive their manufacture firmware updates.