Lost my Z wave names overnight

This morning I noticed on my front end that my front door was unlocked which was weird because my night routine always locks it. Got up and checked and it was actually locked. Seemed weird so I tried turning on/off a few z wave components and only half of them worked, and very delayed.
Read through the log and there was nothing out of the ordinary so I restart HASS. When it came back, most of my z wave devices were gone from the front end. Checked logs, again nothing out of the ordinary. Went into the states page and all of my z wave devices were now ā€œzwave.ā€. The attributes showed a lot of default names under the friendly names and not my custom node names.
I logged into WinSCP and reviewed the zwcfg file and it was basically empty except for a few lines. No idea why.
Then I stopped HASS, pulled the zwcfg file from a backup, restarted, and now everything works like it should again, except I donā€™t know what the root cause is.
Home Assistant log file never showed any weird errors. My z wave log file was gigantic and I didnā€™t even know how to find anything in there. I did screw up and not copy the z wave log after this happened before I restarted with a backup so that version is gone.

Has anyone ever had this happen before? There were no config changes or anything in the last few days. I have no idea what would cause that. I have since reboot my RPi3 just to reset any hardware as well and everything is still working OK.

1 Like

Hi Gregg098,

The exact same thing happened to me yesterday! I also solved it in the same way as you did. At first I was affraid some of my hardware broke, like the SD card or somehow the z-wave stick, but after a reboot with the ā€˜backup zwcfgā€™ everything works as expected. Very weird! Would also love to know the root cause of thisā€¦

I went as far as cloning my sd card and even backing up my Aeotech Z wave stick then re imaging to a new SD card thinking maybe the SD card was failing. Had the same issue on first start but it works after I re-copied my backup zwcfg file over again. Really worried about restarting Hass right now.

Iā€™m having the exact same issue; and Iā€™m trying to find out what went wrong. So far I have not been able to solve the issue because I would like to know what happen. That started for me Friday night.

This has happened to me 3 times with no warningā€¦ Iā€™ve just got really good at backup up my zwcfg and learned to accept it. It is frustrating to say the least.

Iā€™m starting to learn that now. Looks like I will need to start all over again

Running Home Assistant 0.51.2 in a docker container on a Synology NAS. Same thing happened to me. I donā€™t remember the exact date but it was at night on 8/20 or 8/21. I loaded my zwave xml files from a backup and restarted and it worked briefly then broken again after a reboot. loaded files one more time and itā€™s been stable since then. Not sure what happened, but now I know what to look for. Seems like something in Home Assistant and independent of hardware and not a hardware failure.

Iā€™m dealing with the same issue too after upgraded to 0.51.2 and i still havenā€™t been able to get back up. By the way which file did you reload to get back up?

That would be your zwcfg xml file.

Thatā€™s what i thought; but for some reason after the failure that file became blank.

I started having all kinds of issues in the last few days. I could get it mostly working but my Schlage lock wouldnā€™t work. Verified the security key, tried removing, secure re-adding, etc. and it just wouldnā€™t go. I have about 30ish devices and I was on Node 80 or so from testing, removing, and readding devices over the last year or so. Finally bit the bullet and factory reset my z stick. Spent a few hours last night re-adding everything, renaming everything, etc. Came back up smooth and my restarts are way faster now.

Not recommending this to anyone (PITA), but this is what worked for me.

Iā€™m having the same error and posted a bug to the HA github site to hopefully get those who know involved.

The restore from backup works but not a good solution. This has happened two nights in a row.