check if you can do hassio ha restart thru the ssh
nmap only scans the first 1024 ports by default. To check if hass is up and running using nmap use the following command:
nmap -sV -p 8123 <your hassio ip address>
If hass is running the reult should look something like this:
Starting Nmap 7.60 ( https://nmap.org ) at 2018-07-25 02:01 PDT
Nmap scan report for haven (192.168.0.5)
Host is up (0.0044s latency).
PORT STATE SERVICE VERSION
8123/tcp open http aiohttp 3.3.2 (Python 3.5)@alikr
typing hassio ha restart didn’t look to have any impact. Continuous ping didn’t time out, I eventually had to stop it -after almost 5 minutes- by pressing CTRL+C
@cariboo
8123 doesn’t seem to be open:
C:\Program Files (x86)\Nmap>nmap -sV -p 8123 172.16.16.17
Starting Nmap 7.70 ( https://nmap.org ) at 2018-07-25 19:09 AUS Eastern Standard
Time
Nmap scan report for 172.16.16.17
Host is up (0.00038s latency).PORT STATE SERVICE VERSION
8123/tcp closed polipo
MAC Address: B8:27:EB:1F:B6:C5 (Raspberry Pi Foundation)Service detection performed. Please report any incorrect results at https://nmap
.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 6.48 secondsC:\Program Files (x86)\Nmap>
Typing “hassio ha logs” shows the below:
core-ssh:~# hassio ha logs
Error decoding json invalid character ‘-’ after top-level value: 2018-07-25 19:05:25 ERROR (SyncWorker_0) [homeassistant.util.yaml] while scanning for the next token
found character ‘@’ that cannot start any token
in “/config/configuration.yaml”, line 55, column 17
2018-07-25 19:05:25 ERROR (MainThread) [homeassistant.bootstrap] Error loading /config/configuration.yaml: while scanning for the next token
found character ‘@’ that cannot start any token
in “/config/configuration.yaml”, line 55, column 17
core-ssh:~#
Tried to restart ha again, but this time I kept it uninterrupted to get the below log
core-ssh:/# hassio ha restart
ERROR
panic: interface conversion: interface is nil, not stringgoroutine 1 [running]:
panic(0x2c7050, 0x107a6560)
/home/travis/.gimme/versions/go1.7.6.linux.amd64/src/runtime/panic.go:500 +0x33c
github.com/home-assistant/hassio-cli/command/helpers.DisplayOutput(0x107cc200, 0x24, 0x200, 0x0)
/home/travis/gopath/src/github.com/home-assistant/hassio-cli/command/helpers/common.go:118 +0x3c8
github.com/home-assistant/hassio-cli/command/helpers.ExecCommand(0x2f6f83, 0xd, 0x7ea6be58, 0x7, 0x0, 0x0, 0x76500, 0x0, 0x0, 0x0, …)
/home/travis/gopath/src/github.com/home-assistant/hassio-cli/command/helpers/common.go:155 +0x308
github.com/home-assistant/hassio-cli/command.CmdHomeassistant(0x10778420)
/home/travis/gopath/src/github.com/home-assistant/hassio-cli/command/homeassistant.go:48 +0x540
github.com/urfave/cli.HandleAction(0x2af768, 0x324b14, 0x10778420, 0x0, 0x0)
/home/travis/gopath/src/github.com/urfave/cli/app.go:503 +0xf0
github.com/urfave/cli.Command.Run(0x2f6f83, 0xd, 0x0, 0x0, 0x40bd10, 0x1, 0x1, 0x301e4d, 0x2f, 0x0, …)
/home/travis/gopath/src/github.com/urfave/cli/command.go:165 +0x6b8
github.com/urfave/cli.(*App).Run(0x107668c0, 0x1070a160, 0x3, 0x4, 0x0, 0x0)
/home/travis/gopath/src/github.com/urfave/cli/app.go:259 +0x8b0
main.main()
/home/travis/gopath/src/github.com/home-assistant/hassio-cli/main.go:22 +0x108
core-ssh:/#
at least I know that something is wrong with ha being started.
I am having the same problem. I can not access the frontpage anymore but ssh works. I even restarted the system but that does not work either. I am starting to guess it maybe has something to do with the duckdns addon perhaps?
Try this and then see if it starts:
mv /config/.storage/core.config_entries /config/.storage/core.config_entries.backup
The final step of hassio ha restart is waiting for the web ui to work. The supervisor times out and gives up waiting after 10 minutes which is when you get the error above.
You’re right, the timeout is around 10 minutes
the .storage/core.config_entries doesn’t seem to exist for me
core-ssh:/config# mv /config/.storage/core.config_entries /config/.storage/core.config_entries.backup
mv: can’t rename ‘/config/.storage/core.config_entries’: No such file or directory
core-ssh:/config#
core-ssh:/config# find / -name core.config_entries
core-ssh:/config#
Before reading your reply, I did a search for the panic error message, to read few posts talking about a syntax error in the configuration.yaml, so I moved it to configuration.yaml.old, creating a blank configuration.yaml file but this didn’t help either!
Would you know how can I stop an addon from the CLI?
I tried the below command to stop Duck DNS but got an error:
core-ssh:/config# hassio ad logo -name Duck DNS
Error decoding json invalid character ‘A’ looking for beginning of value: Addon does not exist
core-ssh:/config#
core-ssh:/config#
Will leave it for tonight and have another fresh look on it tomorrow.
I have exactly the same issue SSH OK no web ui and panic when trying to restart
Everything works no web ui
Drat, I had a similar problem I was able to fix by removing the chromecast entries in core.config_entries.
It’s unlikely an add-on issue but I think this should work for removing it: hassio ad uninstall -name core_duckdns
Have you tried fixing your configuration file?
I did clean up all entries in configuration.yaml
though maybe i should start with a default one
will let you know how i’ll go in few hours.
had the same issue … only worked once i deleted the core.config_entries file
@flamingm0e
You won’t believe it, I went and corrected line 55 (it was my “api_password:” with the first character being a “@”)
Upon restarting on ha, it did work!
Still can’t get over the fact, that this simple thing will stop ha from starting, I wonder in case the expert can do something to address it.
Many thank all
Grateful for all the hints
I would…
Did you have the chrome-cast integration configured? After having the problem re-appear many times, and several re-installs before I figured out blowing away core.config_entries fixed it… I’ve had it not re-appear by not reconfiguring the integration.
1 Like
Updated to 0.74.2 isuue is fixed for me 
Never thought the “compiling” code is so sensitive, but now I know…
My configuration is so simple, got a Xiaomi gateway with couple of sensors, kodi, a sonos play1 and few Xiaomi philips light -which i yet to figure out a way to add them directly to HA, didn’t experience with automation yet… still finding my way around…
My next step is to play with @resoai Dashboard a bit https://community.home-assistant.io/t/tileboard-new-dashboard-for-homeassistant/57173
Same issue here… get rid of the core.config_entries file (which I’d never have thought to do myself - so thanks for posting that!) and things start working again as far the web interface goes.
If I try to re-enable the Google Cast integration, things will work until a restart of HA and then I’m back to being unable to load the web ui.
Restart HA without cast integration enabled, all good.
Restart HA with cast integration enabled, no web ui every time.
Working fine until today… Guess I’m leaving Google Cast integration off for the time being…
I have a couple of chromecasts powered by the tv they are hooked up to so they turn off when the TV does. I have a suspicion them going offline may be contributing to the problem but haven’t had time to experiment.