Running update on a Zen20 v3. Has been on Complete device is flashing... for the 1.5 hours. How long do I wait before giving up? What is the best way to recover from this if something just went wrong? Since it is complete maybe a physical power off/on?
It's done. That means it's complete and the device is flashing, by which I assume they mean that often a light will be blinking in the device (possibly only until the device reboots on its own).
1 Like
Unusual for it take over 2 hours?
From your description, it sounds like the update took about 30 minutes. You will not get any updates after the status you posted above.
It seems to be frozen on that message.
Correct. The update is finished, and that is the last message you will get from the updater.
So should I turn it off and on? Unplug it? It never rebooted/flashing.
I meant the device, not the hub, in case that wasn't clear. You won't see anything when most devices reboot, so it's possible it already did on its own. The manufacturer should provide instructions for updating, so check there first, but it should be safe to power cycle the device as long as the update is done (which yours is).
That still will not clear anything on Hubitat as, again, this is the last update you'll get. It sounds like like you're using the updater driver rather than the app, so you'll just need to switch back to your regular driver. (If the device doesnt work from the hub after that, note that some require re-pairing or sometimes at least a "Configure" or reestablishment of lifeline association, which re-adding the device will do; this is particularly common with your brand.)
I was using the Update app and File from the Mfg. I meant the device,I was physically watching it while this was going on (no lights flashed)
I have this in the Debug file (repeating):
dev:3792023-04-03 09:43:01.243debugparse:zw device: 55, command: 3202, payload: 21 32 00 00 00 1E 00 00 , isMulticast: false
dev:3792023-04-03 09:43:01.143debugparse:zw device: 55, command: 600D, payload: 05 00 32 02 21 32 00 00 00 1E 00 00 , isMulticast: false
dev:3792023-04-03 09:43:01.043debugparse:zw device: 55, command: 600D, payload: 04 00 32 02 21 32 00 00 00 1E 00 00 , isMulticast: false
dev:3792023-04-03 09:43:00.943debugparse:zw device: 55, command: 600D, payload: 03 00 32 02 21 32 00 00 00 1E 00 00 , isMulticast: false
dev:3792023-04-03 09:43:00.843debugparse:zw device: 55, command: 600D, payload: 02 00 32 02 21 32 00 00 00 1E 00 00 , isMulticast: false
dev:3792023-04-03 09:43:00.744debugparse:zw device: 55, command: 600D, payload: 01 00 32 02 21 32 00 00 00 1E 00 00 , isMulticast: false
dev:3792023-04-03 09:42:50.841debugparse:zw device: 55, command: 600D, payload: 06 00 25 03 FF , isMulticast: falsestrong text
I don't recall seeing that message in the app, but it's possible it went by too fast for me to notice, so that's why I assumed it was the driver. The meaning should be the same, as they generally works similarly besides the interface. Also, not all devices will actually blink, assuming my interpretation of that is even correct (that is just the human-friendly description that the Z-Wave vendor provided for that status code). In any case, I think you'd be good to just manually restart the device and see what happens.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
