I hope somebody can give me a hand with this one. I just installed Hassio yesterday evening for the very first time. I’m now stuck in trying to enable zwave capabilities.
I’m confused with a weird behaviour: if I attach the dongle to my RPI3, and run dmesg I see this:
[10629.070455] usb 1-1.5: new full-speed USB device number 6 using dwc_otg
[10629.173766] usb 1-1.5: New USB device found, idVendor=0658, idProduct=0200
[10629.173785] usb 1-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[10629.175273] cdc_acm 1-1.5:1.0: ttyACM0: USB ACM device
but if I now attempt to see whether a file in /dev has been created, I don’t see a thing
core-ssh:/dev# ls -l /dev/tty*
crw-rw-rw- 1 root root 5, 0 Jan 27 11:21 /dev/tty
When you SSH to Hass.io, you’re not on the Docker container running Home Assistant, so that’s perfectly normal. You should find it is available as /dev/ttyACM0 but you can run hassio host hardware to confirm this.
how come I see two different USB devices ttyAMA0 and ttyACM1? I suspect they all belong to the same ZWAVE dongle.
further on this tipic, I restarted my hassio yesterday (installed 2 days ago) and all the sudden zwave broke. The problem was that the kernel had assigned ttyACM1 instead of ttyACM0. How do I statically assign ttyX to my dongle?
Unlikely, the Z-Wave device will only have one entry in /dev.
That’s a thing that likely needs to be done in ResinOS, and not something I know how to do. Worth hopping on to the HA Discord channel hassio to see if anybody else knows, or try the ResinOS chat.
Unfortunately I don’t use Hass.io, so I can’t help you with it. The Discord #hassio channel, and the ResionOS chat are likely good choices for getting further help.