I’m running a raspberry pi 3 with hassio and two connected devices, a MySensors gateway and a Aeotec Z-Wave gateway. Both are connected to USB. Whenever the pi boots the names of the two USB devices are arbitrarily ttyUSB0 and ttyUSB1.
In regular Linux (at least in ubuntu) it is possible to set up udev rules to ensure that each device gets you same device name every time. This makes the whole system set and forget since any poem corruption will see the thing boots and restore operation when the power returns. How it is now, however, is that there is a very good chance that the two device names have been swapped upon boot which means that nothing will work.
Is there a way to do something similar to the udev rules on the hassio platform?
Or is the only solution to revert back to raspbian and install hass the old-fashioned way?
I chickened out and solved it by dumping hassio, installing rasping, and using the all in one installer to get it running again. I could then use the use udev rules.
TBH I don’t blame you, I’m now a big fan of the docker setup (after being talked into taking a look at it). But this is a real showstopper. It kind of defeats the purpose of one-click update etc. I just pressed hassio’s update button and when it fired up again, I lost my Z-Stick to a different device name.
What I did was ssh to the host and ran ls -al /dev/serial/by-id. That will list all of your serial devices and their symlinks to the /dev/tty* device. Just update your Home Assistant config to point to the correct device using /dev/serial/by-id/DEVICENAME and you should be good to go.
Is there a specific type of key i should be generating. I ahve created a ssh-1 RSA key. uploaded it and using the private key through putty i cannot login. gives me an error “disconnected no supported authentication methods available”
I got it finally.
if you save the public key from puttygen then the file has lines in it. which doesnt work. if you copy and paste the key into the file on one line then it works.
ill make a video at some point soon to explain it all in case anyone needs it in the future.
Been playing with hassbian for awhile, just switch to hass.io. I did have my zwave running on /dev/ttyACM0 and now it is /dev/ttyACM1.
I was trying to get rid of my zwave Linear garage door. Got tired of the barrier issue and wanted to play with OpenGarage. After removing the node and it kept showing in configuration, I restarted HASS. When it came back up the zwave did not configure. It did not configure because now it is showing as ACM1 instead of ACM0. I found the ACM1 by following instructions on locating the zwave controller with Hass.io. Is this expected.
While running hassbain I did use udev to add a rule to make it /dev/zwave.
Reading down this thread I saw where it looks like you can do the same by using the host ssh to get around docker. Is this correct?
I have made this an issue on github. https://github.com/home-assistant/hassio/issues/261
I have the same trouble with a DSMR and RFXTRX. I believe this breaks all installations that have more that 2 or more devices that use ttyUSBX.
that’s it. Thank you for your help. Very much appreciated!