Zwave / Restoring after Disaster

Configuration Z-Wave
1

Hey folks,

I had a running VM (CentOS 7, hass) on my local (Intel NUC) “Server”. It was all peachy until, by my mistake, I wiped the entire host clean. Funny story, I thought I was in a test VM. I was not. Ah, the joy.

I reinstalled the entire thing and also the HASS VM with a fresh copy of CentOS 7. Luckily I have hourly (file based) backups of the vm, so I installed HASS by instructions and recovered the home directory afterward. HASS does start, finds all the old configs, tp-link powerthingies and even recognized the z-wave controller (usb dongle). But all the z-wave devices (Fibaro) are marked as either Dead, Initializing (CacheLoad) or Dead (Complete).

I would guess that there is some odd bluetooth configuration file that has keys, settings, encryption keys etc for the usb dongle for it to work that I did not recover. Anyone has a clue on what is happening here?

Thanks!

-Christian.

2

No Bluetooth involved :wink:

It sounds like you didn’t do a complete backup, so…

If you didn’t use Add Node Secure then all you’re missing is the cache file (zwcfg_*.xml) that would enable a fast recovery.

Without it, you’ll want to go around all your mains powered devices and operate them (turn them on/off, whatever) and then go around all your battery powered devices and Wake them (following the instructions in their manual).

If you did use Add Node Secure that encryption key is gone, and you’ll need to factory reset any such device.

2 Likes
3

Interesting information. Stored this also in my notes for “you never know” if we need it in future…

4

And that’s the benefit of configuring the zwave integration in configuration.yaml. My network key is right there for me to backup.

5

Or just write it down somewhere and reuse it :slight_smile:

6

Yep, this is key information, no pun intended. I feel bad for anyone who has to go through factory resetting all devices and starting from scratch. I also keep my zw network key in my config, but I’m going to store it more securely for peace of mind (along side my ovpn pki files).

7

Is there a way to get the key afterward? So I can store mine also for future protection…

8

Backup all files and directories in your Home Assistant configuration directory and you’ll be fine. Be sure to include the hidden .storage as well :wink:

2 Likes
9

Also if you take full snapshots, you will be safe. Otherwise, I believe the key gets stored in one of the config files after you setup the zwave integration. Just can’t recall the name of the file atm… like options.yaml or something.

10

Thanks all for your answers,

but some of the devices are “Online”. (It all did work before the restore).

When I try to trigger/use a zwave device, I get this in the logs:

2020-01-10 17:16:23.419 Info, Node004, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Dimming Duration - 5 - 1 - 255
2020-01-10 17:16:23.419 Detail, Node004, Refreshed Value: old value=255, new value=255, type=byte
2020-01-10 17:16:23.419 Detail, Node004, Changes to this value are not verified
2020-01-10 17:16:23.419 Info, Node004, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Level - 0 - 1 - 0
2020-01-10 17:16:23.419 Info, Node004, SwitchMultilevel::Set - Setting to level 0
2020-01-10 17:16:23.419 Info, Node004,   Duration: Default
2020-01-10 17:16:23.419 Detail, Node004, Queuing (Send) MultiChannel Encapsulated (instance=1): SwitchMultilevelCmd_Set (Node=4): 0x01, 0x0f, 0x00, 0x13, 0x04, 0x08, 0x60, 0x0d, 0x01, 0x01, 0x26, 0x01, 0x00, 0xff, 0x25, 0x7f, 0x00
2020-01-10 17:16:23.419 Detail, Node004, Queuing (Send) MultiChannel Encapsulated (instance=1): SwitchMultilevelCmd_Get (Node=4): 0x01, 0x0d, 0x00, 0x13, 0x04, 0x06, 0x60, 0x0d, 0x01, 0x01, 0x26, 0x02, 0x25, 0x80, 0x0f
2020-01-10 17:16:23.420 Detail, Node004, Notification: ValueChanged
2020-01-10 17:16:23.424 Detail, 
2020-01-10 17:16:23.424 Info, Node004, Sending (Send) message (Callback ID=0x7f, Expected Reply=0x13) - MultiChannel Encapsulated (instance=1): SwitchMultilevelCmd_Set (Node=4): 0x01, 0x0f, 0x00, 0x13, 0x04, 0x08, 0x60, 0x0d, 0x01, 0x01, 0x26, 0x01, 0x00, 0xff, 0x25, 0x7f, 0x00
2020-01-10 17:16:24.422 Info, mgr,     Refreshing node 4: COMMAND_CLASS_SWITCH_MULTILEVEL index = 0 instance = 1 (to confirm a reported change)
2020-01-10 17:16:24.422 Detail, Node004, Queuing (Send) MultiChannel Encapsulated (instance=1): SwitchMultilevelCmd_Get (Node=4): 0x01, 0x0d, 0x00, 0x13, 0x04, 0x06, 0x60, 0x0d, 0x01, 0x01, 0x26, 0x02, 0x25, 0x81, 0x0e
2020-01-10 17:16:24.425 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-01-10 17:16:24.425 Detail, Node004, Removing current message
2020-01-10 17:16:24.425 Detail, Node004, Notification: Notification - TimeOut
2020-01-10 17:16:24.425 Detail, 
2020-01-10 17:16:24.425 Info, Node004, Sending (Send) message (Callback ID=0x80, Expected Reply=0x04) - MultiChannel Encapsulated (instance=1): SwitchMultilevelCmd_Get (Node=4): 0x01, 0x0d, 0x00, 0x13, 0x04, 0x06, 0x60, 0x0d, 0x01, 0x01, 0x26, 0x02, 0x25, 0x80, 0x0f
2020-01-10 17:16:25.422 Info, mgr,     Refreshing node 4: COMMAND_CLASS_SWITCH_MULTILEVEL index = 0 instance = 1 (to confirm a reported change)
2020-01-10 17:16:25.422 Detail, Node004, Queuing (Send) MultiChannel Encapsulated (instance=1): SwitchMultilevelCmd_Get (Node=4): 0x01, 0x0d, 0x00, 0x13, 0x04, 0x06, 0x60, 0x0d, 0x01, 0x01, 0x26, 0x02, 0x25, 0x82, 0x0d
2020-01-10 17:16:25.425 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-01-10 17:16:25.425 Detail, Node004, Removing current message
2020-01-10 17:16:25.425 Detail, Node004, Notification: Notification - TimeOut
2020-01-10 17:16:25.426 Detail, 
2020-01-10 17:16:25.426 Info, Node004, Sending (Send) message (Callback ID=0x81, Expected Reply=0x04) - MultiChannel Encapsulated (instance=1): SwitchMultilevelCmd_Get (Node=4): 0x01, 0x0d, 0x00, 0x13, 0x04, 0x06, 0x60, 0x0d, 0x01, 0x01, 0x26, 0x02, 0x25, 0x81, 0x0e
2020-01-10 17:16:26.426 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-01-10 17:16:26.426 Detail, Node004, Removing current message
2020-01-10 17:16:26.426 Detail, Node004, Notification: Notification - TimeOut