Upgrade to 2021.1.1 Killed Z-Wave

Configuration
1

I was a bit nervous about upgrading to 2021.1.1 because I have things humming the way I want, but decided to take a snapshot and give it a try because, sooner or later, I’ll have to upgrade.

Once upgraded everything seemed good except I noticed that Z-Wave was listed as Stopped instead of Starting as normal. No biggie, I’ll just hand-start it and if that works I’ll reboot a few times and make sure it auto-starts. No dice. When I hit start it spins for a moment and goes back to Stopped.

I looked at the logs and cannot see any reference to Z-Wave errors or other issues that might be causing this to happen. I’m running the non-beta version of Z-Wave.

So I restored the snapshot I smarty took prior to the upgrade (another first of restoring a snapshot) and restoring things back to 2020.12.2 resolved the problem and Z-Wave starts as normal. Of course the database is toast (as, apparently, is fairly standard from what I’ve read on the forums, that really sucks but it’s not the end-all).

Is there anything I can do to troubleshoot this problem since I can’t seem to find anything in the logs indicating an issue? Or perhaps I’m looking at the wrong logs? I checked both the supervisor logs and the core logs.

2

I can’t remember if you are using the built-in integration or the OZW beta?

If it’s the built-in then you can go to the zwave control panel under the integration menu and you can find the zwave logs there. Or you can open it directly in a text editor from the OZW_log.txt file in your config directory.

If it the beta then I’m not sure how you get to the logs there. If you installed it as a stand alone docker container instead of as an add-on it should be in the config directory for the container. As an add-on I have no idea.

3

I am running HA 2021.1.1 as core, and here the built-in integration works fine (it always has worked for me). Without more logging, it is difficult to say where it goes wrong on your side, somewhere you should have OZW_Log.txt (in my case it is in “/config” with Docker)

4

Happened to me here too. Built in integration. Just upgraded to 2021.1.1 and Home Assistant OS 5.10

2021-01-12 14:03:29.626 Detail, 
2021-01-12 14:03:29.626 Detail, Node031, Removing current message
2021-01-12 14:03:29.626 Detail, Node031, Notification: ValueChanged
2021-01-12 14:03:58.117 Info, mgr,     Manager::WriteConfig completed for driver with home ID of 0xe9973468
2021-01-12 14:03:59.142 Info, mgr,     Driver for controller /dev/ttyACM0 pending removal
2021-01-12 14:03:59.142 Detail, Notification: DriverRemoved
2021-01-12 14:03:59.142 Always, ***************************************************************************
2021-01-12 14:03:59.143 Always, *********************  Cumulative Network Statistics  *********************
2021-01-12 14:03:59.143 Always, *** General
2021-01-12 14:03:59.143 Always, Driver run time: . .  . 0 days, 1 hours, 12 minutes
2021-01-12 14:03:59.143 Always, Frames processed: . . . . . . . . . . . . . . . . . . . . 975
2021-01-12 14:03:59.143 Always, Total messages successfully received: . . . . . . . . . . 975
2021-01-12 14:03:59.143 Always, Total Messages successfully sent: . . . . . . . . . . . . 372
2021-01-12 14:03:59.143 Always, ACKs received from controller:  . . . . . . . . . . . . . 372
2021-01-12 14:03:59.143 Always, *** Errors
2021-01-12 14:03:59.143 Always, Unsolicited messages received while waiting for ACK:  . . 0
2021-01-12 14:03:59.143 Always, Reads aborted due to timeouts:  . . . . . . . . . . . . . 0
2021-01-12 14:03:59.143 Always, Bad checksum errors:  . . . . . . . . . . . . . . . . . . 0
2021-01-12 14:03:59.143 Always, CANs received from controller:  . . . . . . . . . . . . . 0
2021-01-12 14:03:59.143 Always, NAKs received from controller:  . . . . . . . . . . . . . 0
2021-01-12 14:03:59.143 Always, Out of frame data flow errors:  . . . . . . . . . . . . . 0
2021-01-12 14:03:59.143 Always, Messages retransmitted: . . . . . . . . . . . . . . . . . 0
2021-01-12 14:03:59.143 Always, Messages dropped and not delivered: . . . . . . . . . . . 13
2021-01-12 14:03:59.143 Always, ***************************************************************************
2021-01-12 14:04:01.226 Info, Node002, DisablePoll for HomeID 0xe9973468, value(cc=0x26,in=0x00,id=0x01)--poll list has 9 items
2021-01-12 14:04:01.227 Info, Node003, DisablePoll for HomeID 0xe9973468, value(cc=0x26,in=0x00,id=0x01)--poll list has 8 items
2021-01-12 14:04:01.227 Info, Node005, DisablePoll for HomeID 0xe9973468, value(cc=0x26,in=0x00,id=0x01)--poll list has 7 items
2021-01-12 14:04:01.227 Info, Node007, DisablePoll for HomeID 0xe9973468, value(cc=0x26,in=0x00,id=0x01)--poll list has 6 items
2021-01-12 14:04:01.227 Info, Node008, DisablePoll for HomeID 0xe9973468, value(cc=0x26,in=0x00,id=0x01)--poll list has 5 items
2021-01-12 14:04:01.229 Info, Node020, DisablePoll for HomeID 0xe9973468, value(cc=0x26,in=0x00,id=0x01)--poll list has 4 items
2021-01-12 14:04:01.230 Info, Node029, DisablePoll for HomeID 0xe9973468, value(cc=0x26,in=0x00,id=0x01)--poll list has 3 items
2021-01-12 14:04:01.230 Info, Node030, DisablePoll for HomeID 0xe9973468, value(cc=0x26,in=0x00,id=0x01)--poll list has 2 items
2021-01-12 14:04:01.231 Info, Node031, DisablePoll for HomeID 0xe9973468, value(cc=0x25,in=0x00,id=0x01)--poll list has 1 items
2021-01-12 14:04:01.231 Info, Node032, DisablePoll for HomeID 0xe9973468, value(cc=0x26,in=0x00,id=0x01)--poll list has 0 items
2021-01-12 14:04:01.233 Info, mgr,     Driver for controller /dev/ttyACM0 removed
2021-01-12 14:04:02.243 Error, mgr,     Manager::GetDriver failed - Home ID 0xe9973468 is unknown
2021-01-12 14:04:02.244 Warning, Exception: Manager.cpp:373 - 100 - Invalid HomeId passed to GetDriver
2021-01-12 14:04:02.244 Info, mgr,     GetSendQueueCount() failed - _homeId -375966616 not found
5

Seem to have run for 1 hour and 12 minutes and then it “stopped”. From the logging it isn’t clear.

6

I rolled back to a snapshot from 3 days ago, still no z-wave. Unplugged my aeotech stick and hub (Pi 4), plugged em back in, and rebooted. Z-wave worked again. This time the upgrade went fine and z-wave works.

7

Oh, that’s good to know. So theoretically the 2021.1.1 will work but you have to unplug/replug in the stick and reboot for it to kick in? Thanks for that, maybe I can finally upgrade!

My rollback completely worked without any more fussing.

8

The problem got resolved when I followed what @Jiant_Tree did, and that was to completely power down the Pi and unplug/re-plug the USB hub and all was right in the world. Glad to be on the latest version!

My process was slightly different, I went ahead and upgraded first and Z-Wave was broken again, then I shut down and when it came up I was good. I didn’t have to reboot before upgrading.