Issue after restoring a backup

Configuration
1

Hi,
I’m trying to restore a backup image of my hassbian system, which is an exact copy of my system (done with the dd command)
however at restart, HA doesn’t find the Zwave controller
so I checked and the path to USB has changed, it is now /dev/ttyAMA0 so I changed it in core.config_entries but after a reboot, nothing appears…
I also have the issue with a Max! cube which does not connect anymore in HA where there was no issue before…
any idea on these 2 topics? it is very annoying
thanks!

edit: here is the log in case it is useful:

2019-02-25 22:07:20.521 Info, Setting Up Provided Network Key for Secure Communications
2019-02-25 22:07:20.522 Info, mgr,     Added driver for controller /dev/ttyAMA0
2019-02-25 22:07:20.523 Info,   Opening controller /dev/ttyAMA0
2019-02-25 22:07:20.523 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2019-02-25 22:07:20.525 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2019-02-25 22:07:20.526 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-02-25 22:07:20.527 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-02-25 22:07:20.527 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-02-25 22:07:20.527 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-02-25 22:07:20.527 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-02-25 22:07:20.527 Detail,
2019-02-25 22:07:20.528 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-02-25 22:07:21.528 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-02-25 22:07:21.528 Detail, contrlr, Removing current message
2019-02-25 22:07:21.528 Detail, contrlr, Notification: Notification - TimeOut
2019-02-25 22:07:21.532 Detail,
2019-02-25 22:07:21.532 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-02-25 22:07:22.533 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-02-25 22:07:22.533 Detail, contrlr, Removing current message
2019-02-25 22:07:22.534 Detail, contrlr, Notification: Notification - TimeOut
2019-02-25 22:07:22.544 Detail,
2019-02-25 22:07:22.544 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-02-25 22:07:23.544 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-02-25 22:07:23.545 Detail, contrlr, Removing current message
2019-02-25 22:07:23.545 Detail, contrlr, Notification: Notification - TimeOut
2019-02-25 22:07:23.548 Detail,
2019-02-25 22:07:23.548 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-02-25 22:07:24.548 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-02-25 22:07:24.549 Detail, contrlr, Removing current message
2019-02-25 22:07:24.549 Detail, contrlr, Notification: Notification - TimeOut
2019-02-25 22:07:24.552 Detail,
2019-02-25 22:07:24.552 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-02-25 22:07:25.552 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-02-25 22:07:25.552 Detail, contrlr, Removing current message
2019-02-25 22:07:25.553 Detail, contrlr, Notification: Notification - TimeOut```
2

ok the cube configuration has beens solved, it was not a home assistant issue
but I still can’t make the zwave controller (aeotec Gen 5) to work
if I remove the integration in HA and add it again with the same network key, is it going to work without having to set up all the zwave modules?

3

OK so I tried to remove the zwave integration and add it again with the same network key, nothing happens, still no Zwave controller in the zwave menu…
I’m completely lost and don’t know what to do, and I don’t want to start the HA configuration from scratch (especially pairing the zwave modules with the controller, since they are installed and not easily accessed for most of them…)

4

You shouldn’t have to do that even if you were to start with a fresh install. The stick holds the configuration, and the ozwave config file should contain the current HA setup. So if you do a fresh install, plug in the stick and add the owzwave config and boom done. Just need to make sure you have the correct usb slot/port(?) called out.

1 Like
5

which is the file you call ozwave config file? zwcfg_0x_____.xml?
as you say, I was expecting it to work right away since it is an exact copy of the drive, but after having tried everything (and first the correct usb port), my conclusion is that it is a stick issue
when I come back I’ll try to restore again and disconnect/reconnect the stick t see if there is any change

6

Yeah, its that weirdly named zwcfg.xml file. I’d expect it to work right away. But the zwcfg file does have something to do with it. You could delete it but it may cause problems with naming and devices in HA.

7

I’ve just tried and it seems my stick is not recognised anymore!
it seems /dev/ttyAMA0 is the SSD where the system is stored, and when I try to plug the stick, no other device appears…

8

hmm… that’s odd. Not sure where to go from here.

9

update: I tried to connect the stick to a brand new install of hassbian, same issue
I tried on another Pi with a standard raspbian, same
and when I try to backup the stick with the aeotec tool, I have a “read eeprom error” so I tend to incriminate the stick…
I contacted the Aeotec support so let’s see…

I could try to reset the stick, but I really don’t want to go through inclusion and renaming process again… but I guess that will be the next step

Edit: it seems the stick is recognised in a Debian VM running on my MacBook… Now I have to try to set up home assistant in the VM and see what happens

10

I solved it!
the support from Aeotec put me on the right way: it was a driver issue
for future reference: I did a rpi-update, and after the update, the stick was recognized again as ACM0, as it was before, and my HA install is perfectly working as before I restored the backup!

1 Like