UI not showing

[tom_l]

exit back to the ha console.

Then do this:

ha core check

That will take some time.

Also check the logs:

ha core logs

[su-Koch]

Unfortunately After Exiting the Login appears again (i think Thats because i activated the watchdog) Any suggestions how to inhibit this?

[tom_l]

I had a look there’s bugger all documentation on the emergency console that I could find.

[su-Koch]

You mean a Bug? OK, so what does that mean for me ?

[tom_l]

No not a bug.

Bugger all == Australian slang for nothing or next to nothing.

It means I have no idea how to help. There are no instructions for using the emergency console that I can find.

[su-Koch]

OK, appreciate your help. Thank you. So now I’m back at the point I was when asking the Question. Can anybody help?

[su-Koch]

All that did not help

[su-Koch]

What can I achieve plugging in the SD Card into my PC? Can I access the logs this way ?

[tom_l]

Yes:

@tom_l

You can copy the entire /config folder from the old to new installation. You will then only have to set up any addons to get back to where you were. Or you can copy off the snapshots from the /backup folder and restore using that.

Read the SD card in a Linux PC or Windows PC running Linux Reader (free) to get your /config data.

Another option could be to read the home assistant log using the same method and correct any obvious errors.

[su-Koch]

I cannot find a /config folder in Linux Reader. There are a few drives, but where is the config?

/mnt/data (hassos-kernel)
/var/lib/systemd (hassos-overlay)
/var/log/journal (hassos-data)
Volume 3
Volume 4
Volume 5
X:

[tom_l]

Config file on SD card

So this is the tool I used and the location on the SD card where you can find the configuration file: [6]

Or maybe here:

Config file on SD card

Used Disinternals Linux Reader and found if under /mnt/data 1/ Supervisor What files should I keep? Any json files are necessary? Also there is a folder for backups; are those the image backups that I made? thanks

[su-Koch]

OK got it:

2021-01-19 20:02:08 WARNING (Thread-7) [homeassistant.components.mqtt] Disconnected from MQTT server core-mosquitto:1883 (1)
2021-01-19 20:30:48 WARNING (Thread-7) [homeassistant.components.mqtt] Disconnected from MQTT server core-mosquitto:1883 (1)
2021-01-19 20:40:31 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [2905650752] Error handling message: Multi-level wildcard must be the last character in the topic filter. for dictionary value @ data[‘topic’]. Got ‘#/sensors’
2021-01-19 20:40:51 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [2905650752] Error handling message: Multi-level wildcard must be the last character in the topic filter. for dictionary value @ data[‘topic’]. Got ‘#/sensors’
2021-01-19 20:40:53 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [2905650752] Error handling message: Multi-level wildcard must be the last character in the topic filter. for dictionary value @ data[‘topic’]. Got ‘#/sensors’
2021-01-19 20:40:53 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [2905650752] Error handling message: Multi-level wildcard must be the last character in the topic filter. for dictionary value @ data[‘topic’]. Got ‘#/sensors’
2021-01-19 20:41:01 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [2905650752] Error handling message: Multi-level wildcard must be the last character in the topic filter. for dictionary value @ data[‘topic’]. Got ‘#sensors’
2021-01-19 20:41:02 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [2905650752] Error handling message: Multi-level wildcard must be the last character in the topic filter. for dictionary value @ data[‘topic’]. Got ‘#sensors’
2021-01-19 20:56:16 WARNING (MainThread) [homeassistant.helpers.state] Integration sensor does not support reproduce state

[tom_l]

Search your configuration.yaml file (or the included yaml files) for an mqtt sensor with “#sensors” in the topic.

Comment out the sensor, save the file and try restarting.

[su-Koch]

I found a configuration.yaml next to the log file in var/log/journal/supervisor/homeassistant

but this seams to be a default one:

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

wondering if there are other locations

the included files are empty

[su-Koch]

can the configuration.yaml be broken ?

[su-Koch]

I remember that I inserted the #sensors to test the mqtt but that did not work because #sensors is not allowed as a topic.

I think this should be the issue.

Also I would expect the OS to display the log instead of going to the “emergency console” in which nobody knows what to insert

But where can I change this back to default?

[su-Koch]

I figured out that I am on the right track right here. These log file errors have been produced when I tried these combinations over the UI but because of the date of the error I’m 100% shure they are not the reason why the UI does not start.

Can anyone help me out what the reason could be?
This is so ridiculous.

[su-Koch]

After reflashing the SD Card and setting up everthing twice.

THIS HAPPENS AGAIN. NO ACCESS TO THE UI.

This must be a joke.

I don’t know what to do anymore.

[su-Koch]

Can anybody help me. This issue is appearing again and again. After installing SD Card and rebooting in some cases UI is not available anymore.

[su-Koch]

I think that was addicted to an Sd-Card failure. I bought a new SanDisk LongLife SD Card and now it’s working without problems. Even Restart is working properly.

Thanks for your help