Problem adding z-wave

Configuration Z-Wave
1

Hi

Running latest hass.io on rpi3b, problems startad like two weeks ago when I started over and flashed my SD-card and tried to add z-wave like I always do.
zwave:
usb_path: /dev/ttyACM0

Cant get it to work, is there anyone that can connect to my Mac using TeamViewer and see if you can find the problem.
I just bought a new Z-stick and the problem is the same.

LOG:
2018-11-22 22:35:14.909 Always, OpenZwave Version 1.4.3254 Starting Up
2018-11-22 22:35:15.766 Info, Setting Up Provided Network Key for Secure Communications
2018-11-22 22:35:15.766 Warning, Failed - Network Key Not Set
2018-11-22 22:35:15.766 Info, mgr, Added driver for controller /dev/ttyAMA0
2018-11-22 22:35:15.767 Info, Opening controller /dev/ttyAMA0
2018-11-22 22:35:15.767 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2018-11-22 22:35:15.768 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2018-11-22 22:35:15.768 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2018-11-22 22:35:15.768 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2018-11-22 22:35:15.769 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2018-11-22 22:35:15.769 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2018-11-22 22:35:15.769 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2018-11-22 22:35:15.769 Detail,
2018-11-22 22:35:15.769 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2018-11-22 22:35:15.769 Detail, contrlr, Notification: DriverFailed

2

Mate, are you absolutely insane - offering up your computer to any old random person? Yes I could do that but I am a random stranger off of the internets. The only thing we have in common is the English language! Ok that is a little harsh but not too off the mark. I am a bit weird in that I use my real name for a handle, which is not too common so you can check up on me. Google, sorry search for “gerdesj”. I am not Jeanette (not a relative) who seems to have dived in on my old Twitter name - I ditched my Twitter account a few weeks ago because life is too short. Most of the other results are probably me.

I do happen to run an IT company in the UK (Yeovil) and am a sysadmin with 20 years experience and could probably fix your problem without dropping a keystroke logger on your Mac but you will have to find me.

Do not give access to your system unless you understand EXACTLY what is going on.

1 Like
3

It looks like your USB device address is wrong. You need to figure out the correct address and put that in the path.

The logs say AMA0 your path says ACM0. Which is it?

4

I have the same issue with Aeotec Zwave Gen 5 Stick. Running Hassio version 0.86.0

configuration.yaml
usb_path: /dev/ttyAMA0

core-ssh:~# hassio hardware info
audio:
  "0":
    devices:
    - chan_id: "0"
      chan_type: digital audio playback
    - chan_id: "1"
      chan_type: digital audio playback
    name: bcm2835_alsa - bcm2835 ALSA
    type: ALSA
disk: []
gpio:
- gpiochip128
- gpiochip100
- gpiochip0
input: []
serial:
- /dev/ttyAMA0
- /dev/ttyACM0

core-ssh:~# ls -lah /dev/tty*
crw-rw-rw-    1 root     root        5,   0 Jan 25 08:45 /dev/tty
crw-rw----    1 root     audio     166,   0 Jan 25 08:45 /dev/ttyACM0
crw-rw----    1 root     audio     204,  64 Jan 25 08:45 /dev/ttyAMA0

OZW_Log.txt

2019-01-25 09:09:00.183 Always, OpenZwave Version 1.4.3322 Starting Up
2019-01-25 09:09:15.350 Info, Setting Up Provided Network Key for Secure Communications
2019-01-25 09:09:15.351 Warning, Failed - Network Key Not Set
2019-01-25 09:09:15.351 Info, mgr, Added driver for controller /dev/ttyAMA0
2019-01-25 09:09:15.351 Info, Opening controller /dev/ttyAMA0
2019-01-25 09:09:15.351 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2019-01-25 09:09:15.352 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2019-01-25 09:09:15.352 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-01-25 09:09:15.352 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-01-25 09:09:15.352 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-01-25 09:09:15.353 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-01-25 09:09:15.353 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-01-25 09:09:15.354 Detail,
2019-01-25 09:09:15.354 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-01-25 09:09:15.354 Detail, contrlr, Notification: DriverFailed

I’ve tried a factory reset of the stick, tried /dev/ttyACM0 in Zwave config as well. Nothing works. The same stick used to work on previous versions of haasbian.

Any help is greatly appreciated.
Mukund

5

when you tried ttyACM0 what did the log say then?

6

Hi again

I solved the problem by replacing my rpi, something with the USB hub, got a new from warranty and no problems since then!

7

ok thanks. I’ll try that.

8

Strange that I still get AMA0 in the logs.

core-ssh:~# more /config/OZW_Log.txt
2019-01-25 14:06:49.999 Always, OpenZwave Version 1.4.3322 Starting Up
2019-01-25 14:07:06.483 Info, Setting Up Provided Network Key for Secure Communications
2019-01-25 14:07:06.483 Warning, Failed - Network Key Not Set
2019-01-25 14:07:06.483 Info, mgr, Added driver for controller /dev/ttyAMA0
2019-01-25 14:07:06.483 Info, Opening controller /dev/ttyAMA0
2019-01-25 14:07:06.483 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2019-01-25 14:07:06.484 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2019-01-25 14:07:06.484 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-01-25 14:07:06.484 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-01-25 14:07:06.484 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-01-25 14:07:06.484 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-01-25 14:07:06.484 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-01-25 14:07:06.484 Detail,
2019-01-25 14:07:06.484 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-01-25 14:07:06.484 Detail, contrlr, Notification: DriverFailed

Its clearly ACM0 as per dmesg

core-ssh:~# dmesg | grep USB
[ 0.704917] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[ 0.714377] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.716757] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.726833] hub 1-0:1.0: USB hub found
[ 0.778392] usbhid: USB HID core driver
[ 1.171609] usb 1-1: new high-speed USB device number 2 using dwc_otg
[ 1.411830] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[ 1.414166] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.417274] hub 1-1:1.0: USB hub found
[ 1.741628] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[ 1.871850] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[ 1.873095] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.974708] smsc95xx 1-1.1:1.0 eth0: register ‘smsc95xx’ at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:a9:8f:c0
[ 2.271624] usb 1-1.3: new full-speed USB device number 4 using dwc_otg
[ 2.404905] usb 1-1.3: New USB device found, idVendor=0658, idProduct=0200
[ 2.406469] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 3.148395] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device
[ 3.151277] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

Here’s my updated config

core-ssh:~# more /config/zwave.yaml
usb_path: /dev/ttyACM0
network_key: “0x8E, 0xC3, 0x89, 0x44, 0x47, 0x08, 0xB3, 0xAC, 0xB6, 0xF1, 0x15, 0x8D, 0xD0, 0x1B, 0x01, 0x63”

I even changed the PI out to a brand new one.

The only option i see now is to have a brand new vanilla install of hassio and port the configuration over.

Mukund

9

Ok. Finally managed to get this working.
Removed all the zwave config from configuration.yaml. Used configuration–>Integrations–>Zwave to setup /dev/ttyACM0 as the usb path. Restarted hassio.
image

This is what saved the day


image
image713×172 51.2 KB
2 Likes
10

That’s why I was asking that…

I figured it had something to do with the device/entity registry. I’m glad you figured it out.

12

I got it working, Had to delete the integration and add it back.