ih8gates
(Scott Reston)
December 13, 2019, 10:01pm
1
I switched from a Pi 3b+ to a Pi 4. I restored from a snapshot. I updated my configuration.yaml to reflect the new path to my Aeotec Zwave stick (it’s now /dev/ttyAMA0) and edited /config/.storage/core.config_entried to reflect the correct path.
When I start Hassio, I get
2019-12-13 16:54:52 WARNING (Dummy-17) [openzwave] Z-Wave Notification DriverFailed : {'notificationType': 'DriverFailed', 'homeId': 0, 'nodeId': 255}
Any pointers?
firstof9
(firstof9)
December 13, 2019, 10:04pm
2
Did you connect your stick to a USB 2.0 hub or directly to the Pi4’s USB port?
If directly, there’s a known hardware issue with the Aeotec stick where you need a USB 2.0 hub to get it to connect properly to the Pi4.
References:
I installed hassio on a raspberry pi4 today. The install went well but for whatever reason zwave won’t show under configuration. If I go into system/hardware the zwave stick shows up as
serial:
/dev/ttyAMA0
What can I do to make zwave appear under configuration?
FWIW I’ve had hassio running for several hours and have tried a restart
Hi All,
Its my first post, a problem drove me here. After a rapsbian upgrade to Buster and a restart the Z-Wave stick does not work. I suspect something with a driver. But i cant find many details on this point.
Home assistant cant find ttyACM0. Currently there is no ttyACM*
Searching for the problem:
the stick shows up in the usb listing (lsusb)
Bus 001 Device 004: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB
On the driver messages (dmesg)
[ 2.271437] usb 1-1.4: …
Hi,
I am running Pi 4 the beta version. I am new and want to start with Z-Wave. I read the I need to buy a USB stick.
Could you please explain me which usb stick to buy:
https://www.z-wave.com/search-products?utf8=✓&query=z-wave+stick
Whare the components that I need to start? I bought a wall switch that support z-wave.
Thank you
1 Like
ih8gates
(Scott Reston)
December 13, 2019, 10:07pm
3
Yup. It’s connected directly. I’ll see if I can dig up a USB 2.0 hub! Thanks.
ih8gates
(Scott Reston)
December 13, 2019, 10:29pm
4
Whew. That did the trick. Thanks so much.
For anyone else stumbling across this one - make sure you update your YAML to point to the new tty port. It’s possible that it changed when you introduced the hub.
If you use a path like:
/dev/serial/by-id/usb-xxxx-xxxx-xxxx
It shouldn’t change on you. You can get this ID by running
hassio hardware info
1 Like