Z-Wave cannot connect after moving to Raspberry Pi 4

drkade · July 18, 2019, 9:27am

After moving my HA installation to the new Raspberry Pi4, I cannot get my ZW090 Z-Stick Gen5 EU to connect via the serial port. The OZW_Log shows the following:

2019-07-18 10:04:51.189 Always, OpenZwave Version 1.4.3440 Starting Up
2019-07-18 10:04:56.271 Info, Setting Up Provided Network Key for Secure Communications
2019-07-18 10:04:56.277 Info, mgr,     Added driver for controller /dev/ttyS0
2019-07-18 10:04:56.277 Info,   Opening controller /dev/ttyS0
2019-07-18 10:04:56.277 Info, Trying to open serial port /dev/ttyS0 (attempt 1)
2019-07-18 10:04:56.277 Info, Serial port /dev/ttyS0 opened (attempt 1)
2019-07-18 10:04:56.278 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-07-18 10:04:56.278 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-07-18 10:04:56.278 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-07-18 10:04:56.278 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-07-18 10:04:56.278 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-07-18 10:04:56.278 Detail, 
2019-07-18 10:04:56.278 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-07-18 10:04:57.279 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-18 10:04:57.279 Detail, contrlr, Removing current message
2019-07-18 10:04:57.279 Detail, contrlr, Notification: Notification - TimeOut
2019-07-18 10:04:57.279 Detail, 
2019-07-18 10:04:57.279 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-07-18 10:04:58.279 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-18 10:04:58.279 Detail, contrlr, Removing current message
2019-07-18 10:04:58.280 Detail, contrlr, Notification: Notification - TimeOut
2019-07-18 10:04:58.280 Detail, 
2019-07-18 10:04:58.280 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-07-18 10:04:59.280 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-18 10:04:59.280 Detail, contrlr, Removing current message
2019-07-18 10:04:59.281 Detail, contrlr, Notification: Notification - TimeOut
2019-07-18 10:04:59.285 Detail, 
2019-07-18 10:04:59.285 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-07-18 10:05:00.285 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-18 10:05:00.286 Detail, contrlr, Removing current message
2019-07-18 10:05:00.286 Detail, contrlr, Notification: Notification - TimeOut
2019-07-18 10:05:00.286 Detail, 
2019-07-18 10:05:00.286 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-07-18 10:05:01.286 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-18 10:05:01.287 Detail, contrlr, Removing current message
2019-07-18 10:05:01.287 Detail, contrlr, Notification: Notification - TimeOut

Home Assistant Log says

2019-07-18 10:09:56 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave not ready after 300 seconds, continuing anyway

Any ideas what I can do? I followed the merging guide I found on the forums. Also, Hassbian gives me /dev/ttyS0 as the port. Everything else I found documented also did not help so far.
Any ideas?

Thanks.

ganfoud · July 18, 2019, 9:58am

can you provide the output of the command lsusb ?

HomAut · July 18, 2019, 11:45am

As ganfoud mentioning there might be a different naming for the device. It could be anything different from /dev/ttyS0.
Check lsusb and the list in /dev…

firstof9 · July 18, 2019, 4:06pm

Execute ls -al /dev/tty* and post the output.

drkade · July 18, 2019, 5:44pm

Sure, lsusb returns

Bus 003 Device 001: ID ld6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID ld6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID ld6b:0002 Linux Foundation 2.0 root hub

drkade · July 18, 2019, 5:46pm

Sure, ls -al /dev/tty* returns

crw-rw-rw- 1 root tty       5,  0 Jul 18 10:04 /dev/tty
crw--w---- 1 root tty       4,  0 Jul 18 10:04 /dev/tty0
crw--w---- 1 root tty       4,  1 Jul 18 10:04 /dev/tty1
crw--w---- 1 root tty       4, 10 Jul 18 10:04 /dev/tty10
crw--w---- 1 root tty       4, 11 Jul 18 10:04 /dev/tty11
crw--w---- 1 root tty       4, 12 Jul 18 10:04 /dev/tty12
crw--w---- 1 root tty       4, 13 Jul 18 10:04 /dev/tty13
crw--w---- 1 root tty       4, 14 Jul 18 10:04 /dev/tty14
crw--w---- 1 root tty       4, 15 Jul 18 10:04 /dev/tty15
crw--w---- 1 root tty       4, 16 Jul 18 10:04 /dev/tty16
crw--w---- 1 root tty       4, 17 Jul 18 10:04 /dev/tty17
crw--w---- 1 root tty       4, 18 Jul 18 10:04 /dev/tty18
crw--w---- 1 root tty       4, 19 Jul 18 10:04 /dev/tty19
crw--w---- 1 root tty       4,  2 Jul 18 10:04 /dev/tty2
crw--w---- 1 root tty       4, 20 Jul 18 10:04 /dev/tty20
crw--w---- 1 root tty       4, 21 Jul 18 10:04 /dev/tty21
crw--w---- 1 root tty       4, 22 Jul 18 10:04 /dev/tty22
crw--w---- 1 root tty       4, 23 Jul 18 10:04 /dev/tty23
crw--w---- 1 root tty       4, 24 Jul 18 10:04 /dev/tty24
crw--w---- 1 root tty       4, 25 Jul 18 10:04 /dev/tty25
crw--w---- 1 root tty       4, 26 Jul 18 10:04 /dev/tty26
crw--w---- 1 root tty       4, 27 Jul 18 10:04 /dev/tty27
crw--w---- 1 root tty       4, 28 Jul 18 10:04 /dev/tty28
crw--w---- 1 root tty       4, 29 Jul 18 10:04 /dev/tty29
crw--w---- 1 root tty       4,  3 Jul 18 10:04 /dev/tty3
crw--w---- 1 root tty       4, 30 Jul 18 10:04 /dev/tty30
crw--w---- 1 root tty       4, 31 Jul 18 10:04 /dev/tty31
crw--w---- 1 root tty       4, 32 Jul 18 10:04 /dev/tty32
crw--w---- 1 root tty       4, 33 Jul 18 10:04 /dev/tty33
crw--w---- 1 root tty       4, 34 Jul 18 10:04 /dev/tty34
crw--w---- 1 root tty       4, 35 Jul 18 10:04 /dev/tty35
crw--w---- 1 root tty       4, 36 Jul 18 10:04 /dev/tty36
crw--w---- 1 root tty       4, 37 Jul 18 10:04 /dev/tty37
crw--w---- 1 root tty       4, 38 Jul 18 10:04 /dev/tty38
crw--w---- 1 root tty       4, 39 Jul 18 10:04 /dev/tty39
crw--w---- 1 root tty       4,  4 Jul 18 10:04 /dev/tty4
crw--w---- 1 root tty       4, 40 Jul 18 10:04 /dev/tty40
crw--w---- 1 root tty       4, 41 Jul 18 10:04 /dev/tty41
crw--w---- 1 root tty       4, 42 Jul 18 10:04 /dev/tty42
crw--w---- 1 root tty       4, 43 Jul 18 10:04 /dev/tty43
crw--w---- 1 root tty       4, 44 Jul 18 10:04 /dev/tty44
crw--w---- 1 root tty       4, 45 Jul 18 10:04 /dev/tty45
crw--w---- 1 root tty       4, 46 Jul 18 10:04 /dev/tty46
crw--w---- 1 root tty       4, 47 Jul 18 10:04 /dev/tty47
crw--w---- 1 root tty       4, 48 Jul 18 10:04 /dev/tty48
crw--w---- 1 root tty       4, 49 Jul 18 10:04 /dev/tty49
crw--w---- 1 root tty       4,  5 Jul 18 10:04 /dev/tty5
crw--w---- 1 root tty       4, 50 Jul 18 10:04 /dev/tty50
crw--w---- 1 root tty       4, 51 Jul 18 10:04 /dev/tty51
crw--w---- 1 root tty       4, 52 Jul 18 10:04 /dev/tty52
crw--w---- 1 root tty       4, 53 Jul 18 10:04 /dev/tty53
crw--w---- 1 root tty       4, 54 Jul 18 10:04 /dev/tty54
crw--w---- 1 root tty       4, 55 Jul 18 10:04 /dev/tty55
crw--w---- 1 root tty       4, 56 Jul 18 10:04 /dev/tty56
crw--w---- 1 root tty       4, 57 Jul 18 10:04 /dev/tty57
crw--w---- 1 root tty       4, 58 Jul 18 10:04 /dev/tty58
crw--w---- 1 root tty       4, 59 Jul 18 10:04 /dev/tty59
crw--w---- 1 root tty       4,  6 Jul 18 10:04 /dev/tty6
crw--w---- 1 root tty       4, 60 Jul 18 10:04 /dev/tty60
crw--w---- 1 root tty       4, 61 Jul 18 10:04 /dev/tty61
crw--w---- 1 root tty       4, 62 Jul 18 10:04 /dev/tty62
crw--w---- 1 root tty       4, 63 Jul 18 10:04 /dev/tty63
crw--w---- 1 root tty       4,  7 Jul 18 10:04 /dev/tty7
crw--w---- 1 root tty       4,  8 Jul 18 10:04 /dev/tty8
crw--w---- 1 root tty       4,  9 Jul 18 10:04 /dev/tty9
crw-rw---- 1 root dialout 204, 64 Jul 18 10:04 /dev/ttyAMA0
crw------- 1 root root      5,  3 Jul 18 10:04 /dev/ttyprintk
crw-rw---- 1 root dialout   4, 64 Jul 18 10:04 /dev/ttyS0

drkade · July 18, 2019, 5:48pm

Remark: I tried it with /dev/ttyAMA0 and it is not working.

firstof9 · July 18, 2019, 5:58pm

Is the user homeassistant in the dialout group?

Also not seeing the device in your lsusb output either.

drkade · July 18, 2019, 6:10pm

Yes, homeassistant is in the dialout group.

firstof9 · July 18, 2019, 6:15pm

Have you done this as well?

sudo apt-get install libudev-dev

drkade · July 18, 2019, 6:36pm

Yes, it is installed. It came with Hassbian Image.

firstof9 · July 18, 2019, 6:44pm

Seems like the kernel isn’t picking it up, anything about USB in /var/log/dmesg ?

freshcoast · July 18, 2019, 6:48pm

Doesn’t sound like they are compatible at the moment, some sort of hardware issue. Do you have a USB 2.0 hub you could try it with? It’s not clear to me from the discussion if that would work or not…

https://www.raspberrypi.org/forums/viewtopic.php?t=245031

firstof9 · July 18, 2019, 6:56pm

Based on that thread it sounds like the USB sticks are breaking USB specs, someone may want to alert Aeotec so they can fix them and send us proper devices

drkade · July 18, 2019, 7:25pm

Well, this kinda sucks. I will see what I can do with an external port.

drkade · July 18, 2019, 7:42pm

Seems like the kernel isn’t picking it up, anything about USB in /var/log/dmesg ?

No, it is empty.

drkade · July 18, 2019, 8:05pm

Doesn’t sound like they are compatible at the moment, some sort of hardware issue. Do you have a USB 2.0 hub you could try it with? It’s not clear to me from the discussion if that would work or not…

https://www.raspberrypi.org/forums/viewtopic.php?t=245031

Attaching a USB-Hub from 2004 did the trick … thanks for the reference above. But still this is kinda uncool.

daphatty · July 19, 2019, 4:53am

Wow. Aeotec didn’t adhere to the spec at all. So disappointing.

ChrisWeiss · July 22, 2019, 5:18am

Can confirm. I see the same thing on my Raspberry Pi 4 - The Aeotec Z-Wave stick is not recognized when plugged directly into any of the Raspberry Pi 4’s USB ports. Though the disco light does come on, dmesg and lsusb show nothing is plugged in.

I also had no luck plugging it into a USB3 non-powered hub. In that case, even the disco lights didn’t come on (though the hub was recognized by dmesg and lsusb.

Looks like it has to be a powered hub. Maybe even a 2.0 hub?

fribse · August 25, 2019, 7:34am

Sorry, I hadn’t noticed this thread.
We’ve had a lengthy discussion with AEOTEC, and they have admitted to an error in the product.
You can see what solutions we’ve found so far here
The best solution so far is getting a Sabrent 4 port USB3 hub
It doesn’t matter if it’s powered or not, but everybody that has done that, has it working, even after a reboot (I tried with another hub, but had to unplug and replug after a reboot).
Since I’ve gone to the Sabrent, it has worked flawlessly.
There is a very technical explanation about why it doesn’t work, it’s something with timings and USB3, and voltage, pull up resistors and all (can’t remember), but they have said that it will be fixed at some point, though not clarifying if it’s a HW (new stick) or SW (firmware upgrade) fix .