Am I just missing it, or is there no built-in way to select more than one device to start firmware updates on all of them?
This must be done on each device individually. I'd also suggest not doing more than one at a time, anyway--your network will be happier. 
3 Likes
Yea, firmware updates are a lot of data to pass on to the network relative to its' bandwidth capacity.
Already updated all my bulbs at the same time (going to each device and hitting the "Update" button manually). 
Luckily, I have a decent download speed.
The "network" we're referring to is your Zigbee mesh, which tops out at 250 Kpbs.
6 Likes
My procedure with the Hue Outdoor sensors included moving the sensor next to the hub as you suggest here. I got this from you. Thank you!
1 Like
Hi
Could you get Gledopto firmwares as well please?
The manufacturers need to send them to us.
2 Likes
okay so how do i make sure my devices are up to dat the firmware updater in biult in apps only seems to work for zwave. is there another app i need?
No app (that is indeed just for Z-Wave). If the driver you're using for your device supports it, there will be an "Update Firmware" command on the device detail page that you can (optionally) run on each device. The Logs page will tell you more about the status after it's run.
thank you tried to run on the Sylvania LIGHTIFY undercab light but nothing happens ill keep checking it
Then there is no updated firmware available. (If you open a log in a separate window you can see if it's updating or not. There won't be anything happening on the device screen) Zigbee firmware updates are only available if manufacturer has sent it to hubitat.
1 Like
I've always been curious why Hubitat (which promotes "running locally" as one of its primary selling features) requires us to perform Zigbee firmware updates via the 'Cloud' (Hubitat's server)
If we can get firmware from the manufacturer, why can't we use a local file for Zigbee OTA updates like we can with Zwave?
1 Like
I asked this about the cloud backup / migration back in the day. The response was pretty much these are not required functions for the operation of the hub. All necessary bits run local - The part where they store our data is on the cloud and we pay a fee to be able to access is optional.
Some manufacturers don't want their Zigbee files to be public.
2 Likes
Are you sure of that?
You want Hubitat to deploy every OTA firmware they get to your Hub for long term storage, just waiting for you to a) have the device and b) click to update a device?
How about instead, when you click to update a device, your hub goes to a Cloud repository, downloads one specific file and deploys it. Discarding the download when done.
No, I think the request was for it to be like Z-Wave, where there is no such thing and you provide the firmware file as needed.
2 Likes
And that's fine to use the existing method for those manufacturers.
But there are also manufacturers that allow us to download new firmware so why can't we have an option to select a local file for those cases?
No.
Yes exactly. Ideally, we would be able to select a local file from the browser host machine, but if it had to be copied locally to the hubitat hub (like the zwave firmware updater) that would be ok too.
Well if you get some other firmware that we don't currently have, please be so kind as to send it to me so we can share it with all of our customers.
At this time we aren't going to create two separate Zigbee update methods.
3 Likes
