I configured some time ago hassio in a raspberry Pi 3 without keyboard or display. It was mostly some trial and error and most things didn’t work, the interface is (was) ugly, but it mostly served my purpose. I configured some yeelight lights, a broadlink RF/IR emiter and I can use it to switch things on and off from my PC…
But after an upgrade a few weeks ago, it doesn’t respond to the web interface (http to the IP address gives ERR_CONNECTION_REFUSED), it doesn’t appear anymore in samba connectons, trying to connect from windows to \hassio.local or the IP address doesn’t connect and trying to SSH to the address also doesn’t work:
ssh hassio.local
The authenticity of host ‘hassio.local (192.168.1.166)’ can’t be established.
ECDSA key fingerprint is 94:ce:c2:d5:89:d7:97:15:6d:70:8e:8f:b5:85:5c:cc.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘hassio.local’ (ECDSA) to the list of known hosts.
Permission denied (publickey,keyboard-interactive).
I was thinking in restart from scratch, but I noticed that some of the RF connections in the broadlink device are stored in the home assistant configuration and I cannot find the original RF remote to configure them again. I tried connecting the sd card to my windows PC but the configuration files are not available, I suppose when the thing is running they are mounted from some partition, but I do not know how to access them. Any idea on how to restore this thing to work? How is it possible that automatic upgrades render the ssh access, the samba access AND the web interface? the system itself seems to be up and running since it answers to ping and actively refuses http and ssh connections