Thanks for the correct url. In the process of updating it now.
And thanks for all you do here Bryan. Much appreciated.
I have the same problem with the Leviton firmware. Bryan was looking at what's mismatched. Seems like you're running into the same thing, which is good to confirm.
Yep, I've tried different things, but same result. Same error.
At what point is the HE "done"? Meaning it's waiting for the device to do its thing and I can start using the Hub again for other things? Is it when it says
firmwareUpdateProgress : Complete device is flashing...
I assume at this point the device is just doing it's own thing? How do I know when it's done completely?
I'm not really sure what's going on. I need a little help. I tried to update a Zooz Zen21 from 3.1 to 3.4. I had the file hosted on Google Drive and used a site to get the direct download link. That part seemed to work well. I'm assuming it updated, because the switch seems to have reverted back to it's defaults.
I was using it as a scene controller with the relay disabled. Hitting the switch, I can hear the relay clicking. I also had the LED indicator light always off and it's on now when the switch is disabled. So I changed the driver in HE back to the Zooz Central Scene Switch. It's still showing the firmware is 3.1. Even after making sure the preferences are correct and hitting configure, the relay is still enabled and the LED indicator stays on.
It seems to sorta still be functional. It controls a Zwave switch that has a lamp plugged in. The wall switch doesn't do anything, but I can click the "push" button in HE and the lamps turns on, but it's very very delayed (like 3 - 5 seconds). But to turn them off, I have to go to the device list and open the plug and click "off".
Did you exclude, and then reinclude the Zen21 from Hubitat after the firmware upgrade?
I did not. I'm not sure how to do that. I'll look it up in a little bit, try it, and report back.
Has anyone used this to update a Levition DZS15 switch? I see the .hex file for DZ15S, but not for DZS15. They wouldn't use the same firmware would they?
For whatever reason, on a Firmware update, Zooz devices tend to need to be Excluded and Included again.
To exclude your switch, put the hub in "Exclusion Mode" (found on the Zwave details page), and when that is running, press the upper part of the paddle 3 times fairly rapidly. If successful, the log should show "unknown zwave device excluded".
You may have to try it several times, and possibly even move your hub closer to the switch.
Once you've excluded it, use the Add Device button on the devices page, and select Zwave. Once the hub is in inclusion mode, press the bottom of the paddle three times quickly as well. It should join fairly easily.
Note, you'll want to change your rules that use the switch to use another switch (temporarily) or set up a virtual switch to fill in, and remove the switch your excluding, BEFORE you do the exclude, or you could find a bunch of broken rules that you may be forced to fix. Once you've excluded and reincluded, you can go back and update the rules and remove the placeholder.
Excluding and re-including fixed it. But then I was having problems with the switch not functioning properly. No matter what I changed in the preferences, I could not get the relay to disable. I am just using it as a scene controller to control some lamps in our bedroom that are plugged into a Zwave plug.
Glad you sorted it out. Can't help with the relay issue, as I don't use my switches that way. Sorry!
There is. I don't know if the Hubitat staff is aware of it though. The new firmware has a lot more parameters, and I was getting constant errors in the logs with the stock (built-in) driver, especially when I changed a setting or ran a configure. Bryan's updated driver works great from what I can see on my side of things.
Thank you for this updater!! What is the context of the URL for the driver? - I'm not sure where this is running from to know the context. The driver was emailed to me, so I have it stored on a local drive on my laptop - is the "c:\users..." context correct or do I need to put this driver somewhere for the updater to find it. I ask because as I write this the Updater has been "downloading the firmware" for about 15 minutes with no status update.
Yes. On some local or cloud web server. Many people use GitHub.
The updater is running on the Hubitat hub. You have to put it at a URL that is accessible from there. Either a local web server or something like Google Drive.
BTW - I don't know the programming specifics for Hubitat Drivers (seems to be a hidden system to get started) but is there a way to change a specific configuration parameter in a device if that configuration is not supported by the driver? Don't need it by control or to vary it - it's a matter of changing function upon installation, but that function is not presented in the driver interface.
If the device is a z-wave device and you know the z-wave parameter (as well as the desired value), you can temporarily change the driver to Basic Z-wave tool, change the parameter's value, and then change back to the original driver.
You can get Basic Z-wave Tool from Hubitat's Github:
Not sure what you can do for zigbee devices ....
Thanks - I'll give it a try. Been trying to find references like these in the documentation!