After new installation of Homeassistant not able to integrate Z-wave again

Configuration Z-Wave
1

Hi,

because my system was very untidy after years of playing around I wanted to build up a new system on an new pi. So I started installation and wanted also to reset my z-wave stick because I had several dead nodes which I was not able to delete.
So I did a reset on my Aeotec z-wave stick and wanted to integrate it in a virgin way.
That was my idea, but it seems not so easy.
I tryed to integrate via UI and looking at the log I get this message:

2020-07-12 14:01:09.617 Always, OpenZwave Version 1.4.3469 Starting Up
2020-07-12 14:01:14.927 Info, Setting Up Provided Network Key for Secure Communications
2020-07-12 14:01:14.929 Info, mgr, Added driver for controller /dev/ttyAMA0
2020-07-12 14:01:14.929 Info, Opening controller /dev/ttyAMA0
2020-07-12 14:01:14.929 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2020-07-12 14:01:14.929 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2020-07-12 14:01:14.930 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-07-12 14:01:14.930 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-07-12 14:01:14.930 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-07-12 14:01:14.930 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-07-12 14:01:14.931 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-07-12 14:01:14.931 Detail,
2020-07-12 14:01:14.931 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-07-12 14:01:14.931 Detail, contrlr, Notification: DriverFailed

Has anybody an idea how I could solve this issue?

Cheers Lars

2

My best guess would be that you are using an incorrect Device ID.

If you are using Hassio you can go in to supervisor / System and click hardware.
you can use use the ttyacm / ama etc.listed at the top.
But personally I use the one beginning /dev/serial/by-id/usb-xxxx . if you use by-id it wont break if you put the stick in another port. (also handy for more than one stick on the system)

Alternatively in a ssh session go to /dev/serial/by-id. your stick should be in there. e.g dev/serial/by-id/usb-xxxx

3

Hi,

the problem is solved, but I don’t know, why It was there.

I did it all the time as you recommended, but didn’t work until 2 minutes ago…

I gues I did something wrong before, but I don’t know the change.
But now it works again… thanks.

4

I had another thought. If you have a pi4 and an Aeotec Gen 5. you will need to connect the stick to the pi
using a usb hub to work round this issue:-
https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=245031#p1502030
I got the ‘been reports’ link from the top of the zwave controllers integration page.

This would explain why it worked sometimes and not others.

5

no, it’s a pi3.

but no it’s fixed.
thx