Z-Wave Firmware update error and can't close dialog box

šŸ›Žļø Get Help Devices
1

I am running 2.3.4.114 and started updating the Z-Wave firmware. It got somewhere past 44% and when I looked at it again I got this error message:

Screen Shot 2022-11-25 at 5.53.39 PM
Screen Shot 2022-11-25 at 5.53.39 PM1210Ɨ394 25.1 KB

That is the whole dialog box. There is no "X" or "Close" button. (The Update Firmware button is grayed out and can't be clicked). So there is no way to close it!!

BTW, I tried closing the browser (Safari) and restarting it, but this time I instantly got the above error message.

What do I do now?

2

Close the page or the browser?

3

Closed the browser.

I also tried it with Chrome on my Mac and it gave me a error message very quickly that said "failed to start" before giving me the same error posted above.

4

Full shut down on the hub, pull power for 10 seconds, reboot. See if that does it.

5

I tied that but it didn't work. I did not to pull the plug from the hub, I waited until Hubitat said it was shut down (and the light was red a few seconds before that) and I waited a good 30 seconds or so before plugging it back in. I then waited a couple of minutes after the green light came on to try it again.

This time it crashed after only getting to 15% with the same error message:

Screen Shot 2022-11-25 at 9.54.49 PM
Screen Shot 2022-11-25 at 9.54.49 PM1270Ɨ470 42 KB

So:

  1. Why isn't there any way to close the error message; and
  2. Much more importantly, why isn't it upgrading and what should I do now?
6

Weird i had same issue on first attempt when computer went to lock screen and presumably the download tanked.

I closed window and just did normal hub reboot from another window not even full shutdown and it worked fine the next time.

7

What is updating where? Is it software that is already on the hub updating the hub? It seems strange that it is running so slowly.

I also wonder why there is no way to close an error box.

8

It is firmware downloaded to the hub that is updating the firmware on the z-wave radio that is on the hub.

When I updated mine, I minimized all z-wave reporting (switch, dimmer, power, contact, motion) and then updated. Went really quickly.

9

Iā€™m not quite sure what you mean by minimizing z-wave reporting. I think I have virtually all logging/reporting off. Can you please give me an idea of what you are doing? Should I turn off the Z-Wave radio when Iā€™m doing this or does it need to be on?

BTW what hub version or you on? I wonder if it could be something in the recent release.

10
  1. Turned off all power reporting (from the device page of power reporting outlets - I have about 5-6 of these) before the updated.
  2. Made an attempt not to trigger any z-wave motion sensors or contact sensors during the update.
11

I already virtually all reporting off and as far as I know nothing was being triggered while I was trying to do the update.

BTW, I had done the update to 2.3.4.114 a few minutes before that and it went smoothly.

But I did see a message that one switch was doing excessive reporting. I went into the device and turned Enable Debug Logging off and set 19 to 32767 and 20 to 100 before I tried the firmware updates.

12

turning logging off does not stop reporting.. just doesnt log it.. reocmmend you diable this one and try again.

13

I air gapped the switch that Hubitat informed me had been giving excessive reports and then tried the firmware update again. It instantly gave me an error message that it failed to start. About 10-20 seconds later it gave me the same error message I posted at the start of this thread.

So I don't know why it is failing instantly or how to fix that.

I also still fail to understand why Hubitat would have created an error message that can't be closed. I have to literally close the browser to get it t go away. But at this point, I hope that is just an annoyance and a collateral issue. I say "hope" because that first couple of times I tried to do the firmware update it started but then crashed. (First time got past 44%, but very slowly, 2nd time it got to 15%, again, but very slowly). Since then I won't even start to run now.

14

Once you get error measage i believe you need to reboot hub, at least that is the only way it fixed it in my case.

15

I have seen other comments about when you go to the Z-Wave screen (with the update button), let it settle there for about 10 minutes before attempting an upgrade.

Took me 2 tries.

16

For an instant failure I would shut down the hub, pull power for 10 seconds and boot back up.

Probably an accident that got missed in Beta. Tagging @gopher.ny in case he needs to know.

1 Like
17

So after I gracefully shut it down, and powered it down from the wall for about 1 minute, I then restarted the hub. I had things to do so finally opened the Z-Wave details page about 2 hours later and let it sit there for just about 15 minutes. I then restarted the Z-Wave updater. This time it did complete (woo-hoo!) but I took 16:45 to load the software (it was going at a rate of about 1% every 10 seconds). It then took 32 seconds to finish for a total time of 17:15 minutes to do the update, which seems unexplainably long. But, at least it is done.

1 Like
18

That sounds about normal. Not sure how long mine took, I just walked away and came back later to see it wads done. It is very slow.

1 Like
19

OK. Thanks. Someone above had said it went very quickly.

Here is my current version:

VersionReport(zWaveLibraryType:7, zWaveProtocolVersion:7, zWaveProtocolSubVersion:18, firmware0Version:7, firmware0SubVersion:18, hardwareVersion:1, firmwareTargets:1, targetVersions:[[target:1, version:7, subVersion:15]])

I'm not sure how to read it. Am I now up to date?

20

yes

1 Like