Error when trying to update ZEN30 from 1.03 to 1.05 firmware.
I also noticed at about the same time that the logs stopped (07:12:04), zwave logs showed route change (to a faster route); not sure if it is related:
I'm currently in the middle of doing an update on my third Inovelli Red Series dimmer. It had an error at about 60% done. Restarted it and it is chugging along. Did not check the logs, but I will if it errors out again. This dimmer is kind of a worst case scenario, as it has 3 hops to the hub. My other 2 Inovelli dimmers didn't have any hops in their routes and they updated okay - one errored out, I restarted it, and it completed without error.
I also had polling turned on for all of the updates. After the error on this last dimmer, I turned off polling and it seems to be downloading the firmware a little faster. I wish that I had thought to note the time it took to update the first two dimmers. This third one is dead slow - at 26% done for the first target at 22 minutes. Boy this is slow, maybe the number of hops or maybe error retries?
Fun stuff. 
Retrying the update seems to have worked (but now I don't have local control 
)
Did you factory reset after completing the update? This is required for all Zooz switches...
Reset, exclude, and include again. Breaks all your automations unless you used a virtual placeholder, but there's nothing for it but to do it.
Edit: for the Zen30, the reset sequence is to hold the lower paddle 15 seconds until lights start blinking, then immediately switch to holding the upper paddle 15 seconds until lights start blinking, then release. Wait a few seconds and the reset should complete. I like to pull the air gap after a bit, for no really solid reason other than it feels like the right thing to do. Once the switch is rebooted, the exclude and include process should work.
Interestingly enough...
The device was working for digital control after the update, but not for local control. I was trying to test it to gather details to send to zooz when it spontaneously reset itself (HE logs showed "device reset locally").
After this I was able to use the "refresh" and then "replace" from zwave details page (C7 with 2.2.4.158) to initialize it and all seems to working now; no exclusion was needed and it is using the same device on the same DNI as previously (and attached apps work as before with no changes needed).
1 Like
@agnes.zooz does this mean the device actually performed a factory reset on its own? My understanding was that a user-initiated factory reset was required to make sure the firmware is loaded and running properly. I'm actually astonished at @tony.fleisher's report... maybe there's a new, better way to update Zooz firmware?
@tony.fleisher can you confirm that you didn't perform the factory reset procedure from the buttons when testing the device to gather documentation for our support? There's no way for the device to factory reset itself to my knowledge and we haven't seen that before.
So far, if the update includes changes to association and command classes, reset / exclusion is the only reliable way to get the device fully functional after an update. I don't think this is brand-specific but rather a requirement in the Z-Wave protocol, it's just that many other companies provide firmware updates with these types of changes for us to compare 
But we're looking into way to simplify it.
This is part of the z-wave standard and yes it means that the device was factory reset
I definitely didn't hold any buttons for more than 15s, but I was pressing all of the buttons without waiting more than 1s in between as I was trying to understand what was going on. During this time it was having very strange behavior like single press behaving like held, lower paddle decreasing and then increasing dim level, etc.. I tried the air gap and it didn't make things better, but it was shortly after this that the reset occurred. It seemed like it just got really confused.
I wish I had more specifics to provide, but all seems good after the reset completed and the error behavior has not returned.
Are changes to association and command classes common with firmware updates (for zooz devices)?
They're more common recently as we're getting more requests around direct association behavior. But they'll also be there if upgrading from a device that's older than 6 months and switching between versions (like 2.0 and 3.0 for the ZEN21-ZEN24 models) where the Z-Wave command class library was updated with new versions of command classes and new functionality (like scene control > resulting in more command classes added) was introduced.
Doe the OTA tool send a command to reset the device once the update is complete?
No.. We don’t implement device resets anywhere currently. Just reporting when it is sent from the device. In fact I would like to make it more obvious than a log entry that may not even show up on all drivers..
2 Likes
Thanks for clarifying Bryan. Then it must have been incorrect behavior after the update which interpreted some of the button presses as a factory reset procedure @tony.fleisher
1 Like
