After updating to HA 2022.9.0, I was prompted to update the firmware for the 2 GE/Jasco 14287 dimmer switches I have. I clicked Settings, selected the device, and clicked Install:
I can watch the z-Wave JS event log for the device as the firmware update progresses, but after the “firmware update complete” event, the device cannot be re-added to my network and I inevitably have to remove the device and re-pair it as a new node. Has anyone been able to successfully update one of these switches using the built-in OTA firmware updates in HA 2022.9.0?
What do you mean by “re-added to the network”? Why do you need to remove it in the first place?
1 Like
The device never re-joins the network after the attempted OTA firmware upgrade. It shows “protocolinfo” in the interview column in the zwaveJS control panel.
Also, when I remove the now-dead node and re-add the device as a new node, once the interview completes, the firmware shows that it’s hasn’t been updated since the firmware version is the version from which I’m trying to update, not the new version.
OK, that was just the re-interview, it’s not re-joining the network. You could also try power-cycling the switch instead, most GE have a air gap that will cut power if you remove it. That will keep the node ID although the firmware may not have been successfully updated still.
Unfortunately, I don’t have any other ideas, but I have successfully updated a 14287 to 5.24 with the manual install method, which is no different.
What do you mean by “manual install method”? Is there a wired firmware upgrade option available, or is that using the OTA Updates section in zwaveJS? I see that Jasco themselves require HA users to use zwaveJS: Connected Home Firmware Downloads
I downloaded the firmware file from Github, and used the firmware update functionality from the Device page. The new feature automates the download and install process. The underlying firmware install process is the same.
Something is definitely wrong with my device, then. I tried that, too: Open device in zwave JS, click Advanced - Firmware updates - select downloaded .hex file, wait for firmware upgrade to finish, and the device never re-interviews successfully, failing 5/5 attempts multiple times. I still had to remove the dead node and re-add a new node to get it back online with HA, and the firmware still shows 5.22 so something about the failed upgrade must be causing the interview to fail, too.
I’m not too worried about it but it is kind of a bummer.
I also did this with a driver version before v10, possibly that makes a difference. I would capture logs of a failed update process (using Silly log level), and create a bug report, attaching the log file to the issue.
1 Like
Yeah - probably something up with your device. I just finished 2 of these with the new builtin OTA deployment feature:
So far today, I’m on GE device #13 with no deployment issues.
Same issue here - I updated the same device from Home Assistant 2022.9.0 and Home Assistant now says the device is dead. 
I was able to update one of mine and I had to power cycle it afterwards. I did nothing special to update it.
I just updated another one. At first it looks like it didnt do anything. Took 3-4 seconds total. After the update the switch doesn’t respond and a power cycle fixes it.
1 Like
Anyone who has successfully updated their switch, how far is your zwave stick from the switch? Mine is probably ~15-20 feet through multiple walls and one house floor. It takes at least 5 minutes to finish uploading the firmware to the device, too, so I wonder if that may be my issue.
I just completed my entire house - a very Jasco heavy install with various devices from the 12xxx on… Nearly 20 devices needed OTA updates.
All succeeded successfully, NOT all were flawless.
Two devices showed some kind of shakiness during the post-firmware restart / re-interview process.
One of these devices came back on its own after about 4-5 minutes of just letting it sit. (It was one of the Enbrighten Switches, can’t remember model - sorry)
The other (a 14287, just like op, BTW) started responding after a ‘ping’
To @strikeir13’s point. In my experience (YMMV) The farther away the device was, the longer it took. I had a few devices 3+ hops away from the Z-Stick, on the other end of my house and install took nearly an hour where my foyer light next to my office (where my stick lives) was done in 5 minutes.
I have a similar issue. About 3 of them have updated without any issues, but one of them so far keeps failing. Same result as others have stated, post update it becomes a dead node and no matter what attempts I try I end up having to factory reset the switch and re-join to the Zwave network.
Switch:
14294 / ZW3005
I am having the same problem attempting to update the firmware on a GE 14287 so I opened an issue with a log attached.
What are the date codes on everyone’s switches (both failed and worked)? Here’s mine:
| Model | Result | Date Code |
|---|---|---|
| 14287 | Failed | 1738 |
| 14287 | Failed | 1738 |
| 14287 | Worked | 1752 |
Here are the date codes for my 2 switches
| Model | Result | Date Code |
|---|---|---|
| 14287 | Failed | 1731 |
| 14287 | Failed | 1738 |
| Model | Result | Date Code |
|---|---|---|
| 14287 | Succeeded | 1714 |