This category is an extension of the FAQ and is dedicated to quick questions and answers for specific topics. If you searched the community and couldn't find the answer to your question, consider posting the question in the subject line and add any pertinent details in the body. For more details on the FAQ please visit this post: FAQ - Hubitat
So as the ultimate goal is to manage and run everything locally, one recent issue that has surfaced when using products that are created to work with a native hub. I have 4 hue blubs that were purchased and connected to HE instead of the Hue Bridge. As the Bridge would normally update the products after install, you do not get that with HE which makes sense. I'm on the fence with the firmware updater and haven't set time aside to figure how legit it is. What are some of methods the enable the proper firmware is applied to the proper device?
What updater? The Device Firmware Update app? That is only for Z-Wave devices. Hue bulbs are Zigbee. Zigbee devices are updated using the "Update Firmware" command on the device detail page, and progress will appear in Logs. Not all drivers have this command, not all devices have firmware available, and ones that are available are downloaded from Hubitat's servers and matched to the device by device metadata with no need to manually select anything on your end.
2 Likes
Oh! Yes, that is true. What I meant to say was using the "Update Firmware" option when using the Advanced Zigbee CT bulb driver. Since the creation of the post, I've discovered a dedicated driver and a possible solution to my problem which was Philip Hue bulbs. They were chosen for their reliability and functionality over other zigbee bulbs for HE. I did not think of the option of using the bluetooth connection for pushing updates. I hope I can still attempt an update after being connected to HE as the resource stated to update immediately prior to connecting to HE.
