While not being at home and not getting access to http://hassio.local and not having ssh access.
Smb is still working…
Can you see what error in the home-assistant.log says?
The last entry in the log is from 6 hours before it crashed.
I made a small change to an automation and then pressed “check config”. That was when it crashed.
The last update of the .db file is also from the moment ha crashed.
you should always have a way in… even if it means Teamviewer into local box… even if that is a $5 Pi
in terms of your change… roll it back or hash out that automation section and restart the server…
In order to provide more detailed support information, please detail your environment (Hardware, OS, Etc)
Hope I can help…
I failed indeed with having a way in. I currently only have a samba way in… Being away from home is not helping.
I double checked the changed part. There is nothing wrong with it.
Is there any way to restart the server (http command) or access the ssh add-on settings remotely?
You can use on ssh addon: curl -X POST http://172.17.0.2/homeassistant/restart
the problem is, I cannot ssh into my pi at the moment.
I did install ssh addon, but on another computer and don’t have the keys with me… Stupid I know.
I have a second pi acting as a VPN on which I logged and tried your curl command. No luck unfortunately.
You can call the the API from outside over the homeassistant api proxy but if that not run, you can only connect over a add-on to hass.io API
Thanks @pvizeli.
I’ve got ssh access now via the add-on.
For next time, if there is no life in the UI anymore, what command should I use to reboot the docker or resinos completely?
Thanks for all your development by the way. I really love the hass.io approach.
I think it is okay to only restart homeassistant.
Anyway the new snapshot/restore feature give a lot of improvment for all of that. I hope someone will help to write a small CLI on ssh addon to handle that easyer.