I’m attempting to migrate from HomeSeer to Hass.io running in Virtualbox on a Windows 10 system (my Blue Iris machine). Everything is working great with the exception of Z-wave. I purchased an Aeotec Z-Stick Gen5 and can get it to work by specifying the serial port address (/dev/ttyS1, etc.) but then the address changes either when I reboot or when the USB stick gets unplugged and plugged back in.
To combat the changing serial path, I read that I should be able to use /dev/serial/by-id/usb-0658_0200-if00 to identify the Z-Stick. I tried that and it doesn’t find the device. So my next thought is to log in via SSH to run “ls -l /dev/serial/by-id/*” to identify the correct persistent ID. However, this is Hass.io, and you can’t just SSH into the box.
So I created a public key in puttygen and saved it into a file called “authorized_keys” and put it on a USB stick entitled “CONFIG” (as outlined at https://developers.home-assistant.io/docs/en/hassio_debugging.html). I then “Import from USB” in Hass.io–the logs then state this:
19-06-01 04:45:53 INFO (MainThread) [hassio.hassos] Syncing configuration from USB with HassOS.
19-06-01 04:45:53 INFO (MainThread) [hassio.host.services] Restart local service hassos-config.service
19-06-01 04:45:53 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.RestartUnit on /org/freedesktop/systemd1
I’m not sure if that means it was successful or not. Regardless, I then try to SSH using Putty into the system of my Hass.io install using the private key also generated by puttygen. After trying for a few seconds, I just get a pop-up message that says:
Network error: Network error: Connection refused
What am I missing here? First of all, it seems like the persistent ID that others use should also work for me, but it doesn’t. Then when I try to SSH into the system to identify the correct ID, I can’t get in. Looking for help…