Z-wave Network Not Starting after upgrade to 0.115.1

Hello Folks!

I posted this in the recent supervisor blog post thread too, but this might be more appropriate here.

I’ve just updated to home assistant 0.115.1 (and supervisor a day or two ago) and now my z-wave network won’t start! The z-wave log is just spammed with 2020-09-19 18:57:01.049 Warning, WARNING: Out of frame flow! (0xc0). Sending NAK.

It turns out that 0.115.2 was released basically while I was upgrading. So I tried that too. I also rebooted (including cutting power), restarted HA Core quite a few times, etc., to no avail. Same issue. I eventually had to restore to a snapshot of 0.114.1. (thank goodness for that feature!)

I’m running Home Assistant (OS), on a pi 3b+ with a aeotec stick, on the standard z-wave integration. I was hoping maybe my usb address had changed but alas, that’s not it, my by-id address in hardware matches my config.

I’m seeing old chatter about modemManager causing such issues… I’m very suspicious of the new feature of supervisor to manage your ip settings! I’ve also seen people having this issue because they have portainer, nodered running, or ozw beta in addition to standard z-wave. Noneof those are the case for me.

I’m very excited to try out all of 0.115’s features, and I like to keep my system very current to avoid a bunch of changes at once. I’d much appreciate any help!

After restoring to my snapshot the other day, tonight I just tried to update to 0.115.2. It went smoothly, z-wave network and all. Maybe it happened because 115.2 went up just as I clicked upgrade to 115.1? Probably not, and I suppose we’ll never know. :man_shrugging: