Hello, since I updated home assistant yesterday I cannot access my home assistant using its internal ip; I can still ping it from windows tough
I tried restarting the raspberry (3+) with no luck
have you checked the home-assistant.log for errors?
the problem is that I’m locked out, if I type the ip address in the browser I get a message (from the browser) saying the destination is not available or page not found (depending on the browser used)
Don’t you have access to the files by Samba of SSH?
do you have ssh access or a samba share set up so that you can access your configuration files?
yes, I should have ssh
the navigate to your config directory and open the home-assistant.log file.
ssh doesn’t work anymore: “connection refused”
I can still ping the raspberry though
I can still ping the raspberry though
This is what I see if I connect a screen
I managed to create a bootable usb stick for my laptop and was able to recover the configuration, automations files etc…
I have same problem, can’t connect to web page and SSH not working (im not sure whether i had it installed though…). I didn’t install update but i did just restart raspberry, and this now happens.
Can you explain how did you get configuration files? I really would like to get those because backups are little bit too old.
I wonder if there is possibility to enable SSH through console?
Have you tried clearing your browser cache? ctrl-f5.
Yes and tried from different computers too. Web interface is totally dead.
Has it changed IP address?
I had to download and flash ubuntu on a usb stick and boot it on my laptop (I normally use windows), put the sd card in and recover the files… apparently you can also use a software for windows called DiskInternals but I couldn’t see all the files with it
I was also not able to restart fresh using the latest ISO from the hassio repository (it would stick on ‘preparing hassio’ for more than 10 hours) and ended up installing an older version that I had downloaded a few weeks ago (1.13 I think)
Actually, it has fixed IP address in router DHCP. But i did try to change IP also, didn’t help.
There was some error in automation.yaml i think, but could that be reason this can’t really boot anymore?
Ok, thanks. I should try that. I thought files can’t be accessed, but great if it works.
Yes, it’s fixed now. Problem was really in automation.yaml. I have no idea how this happened, but there was one “-” in one of my old automations “after” condition. I did boot to Ubuntu and mounted that sdcard and got that fixed.
I found that error through hassio, with command “homeassistant logs”. There was such error:
2019-02-24 14:30:17 ERROR (SyncWorker_0) [homeassistant.util.yaml] while parsing a block mapping
in "/config/automations.yaml", line 340, column 3
expected <block end>, but found '-'
in "/config/automations.yaml", line 349, column 3
2019-02-24 14:30:17 ERROR (MainThread) [homeassistant.bootstrap] Error loading /config/configuration.yaml: while parsing a block mapping
in "/config/automations.yaml", line 340, column 3
expected <block end>, but found '-'
in "/config/automations.yaml", line 349, column 3