What exactly is your install method and | Home Assistant | Page 1

shut schooner Nov 2, 2022, 12:45 AM

#

Install method is HA OS on bare metal NUC. Worked fine for a long time and then something went wrong in the last two months. Once I enable the ZHA integration I can no longer connect to HA GUI but I can still SSH.

agile hazel Nov 2, 2022, 12:45 AM

#

If it's HAOS then you shouldn't be managing or touching the containers

#

That's out of your control

shut schooner Nov 2, 2022, 12:46 AM

#

I'm not trying to. Just trying to get HA working again with ZHA and troubleshooting based on the error messages in the logs

agile hazel Nov 2, 2022, 12:46 AM

#

What are the error messages

#

Give core errors too

shut schooner Nov 2, 2022, 12:47 AM

#

SU Errors:
22-11-01 12:57:12 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config:

#

Some MQTT errors in Core logs:
2022-11-01 12:37:55.999 ERROR (MainThread) [homeassistant.util.logging] Exception in async_discover when dispatching 'mqtt_discovery_new_binary_sensor_mqtt': ({'name': 'Key Fob', 'device_class': 'None', 'state_topic': 'mqtt-states/binary_sensor/key_fob/state', 'payload_on': 'Open', 'payload_off': 'Closed', 'availability_mode': 'all', 'availability': [{'payload_available': 'online', 'payload_not_available': 'offline', 'topic': 'mqtt-availability/binary_sensor/key_fob/availability'}, {'payload_available': 'online', 'payload_not_available': 'mqtt-client/status', 'topic': 'mqtt-client/status'}], 'platform': 'mqtt'},)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/mqtt/mixins.py", line 315, in async_discover
config = discovery_schema(discovery_payload)
File "/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py", line 272, in call
return self._compiled([], data)
File "/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py", line 595, in validate_dict
return base_validate(path, iteritems(data), out)
File "/usr/local/lib/python3.10/site-packages/voluptuous/schema_builder.py", line 433, in validate_mapping
raise er.MultipleInvalid(errors)
voluptuous.error.MultipleInvalid: expected BinarySensorDeviceClass or one of 'battery', 'battery_charging', 'carbon_monoxide', 'cold', 'connectivity', 'door', 'garage_door', 'gas', 'heat', 'light', 'lock', 'moisture', 'motion', 'moving', 'occupancy', 'opening', 'plug', 'power', 'presence', 'problem', 'running', 'safety', 'smoke', 'sound', 'tamper', 'update', 'vibration', 'window' for dictionary value @ data['device_class']

#

2022-11-01 12:37:56.023 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform mqtt does not generate unique IDs. ID qolsys_panel_p0z51 already exists - ignoring binary_sensor.driveway
2022-11-01 12:37:56.024 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform mqtt does not generate unique IDs. ID qolsys_panel_p0z32 already exists - ignoring binary_sensor.studio_hall_smoke_detect
2022-11-01 12:37:56.025 ERROR (MainThread) [homeassistant.components.binary_sensor] Platform mqtt does not generate unique IDs. ID qolsys_panel_p0z35 already exists - ignoring binary_sensor.studio_co_detector

#

But those errors have always been there.

agile hazel Nov 2, 2022, 12:49 AM

#

Maybe fix those too

#

So when you activate ZHA there are no logs at all that correspond?

shut schooner Nov 2, 2022, 12:50 AM

#

No. Just the supervisor errors.

agile hazel Nov 2, 2022, 12:50 AM

#

And if you go to [IP]:8123 it won't load the front-end at all?

shut schooner Nov 2, 2022, 12:51 AM

#

Exactly.

#

If I try to restart core I get: 22-11-01 17:51:02 ERROR (MainThread) [supervisor.utils] Can't execute restart while a task is in progress

#

When I reboot the host I can briefly get into the GUI and then something goes wrong.

agile hazel Nov 2, 2022, 12:56 AM

#

And there's nothing in any of the logs as something goes wrong?

shut schooner Nov 2, 2022, 12:58 AM

#

Only in the supervisor log. Anything I should grep for in the logs?

agile hazel Nov 2, 2022, 12:59 AM

#

Just look for anything interesting around the time when it crashes

#

Eg you do it now, know it's 11:59am, look for 11:59±5 mins in the logs

#

See anything interesting

shut schooner Nov 2, 2022, 1:04 AM

#

Since the GUI loads briefly and provides those startup messages... the last thing it shows is:
"Starting dlna_dmr, not everything will be available until it is finished."

#

Nothing interesting or different in the core logs

#

These are the last lines from the supervisor logs:

#

[01:01:02] INFO: Starting local supervisor watchdog...
22-11-02 01:01:04 INFO (MainThread) [main] Initializing Supervisor setup
22-11-02 01:01:04 INFO (MainThread) [supervisor.bootstrap] Initializing Supervisor Sentry
22-11-01 18:01:04 WARNING (SyncWorker_1) [supervisor.docker.interface] Can't find ghcr.io/home-assistant/amd64-hassio-supervisor for cleanup
22-11-01 18:01:04 INFO (MainThread) [main] Setting up Supervisor
22-11-01 18:01:05 WARNING (MainThread) [supervisor.host.network] Requested to update interface enp0s25 which does not exist or is disabled.
22-11-01 18:01:09 WARNING (MainThread) [supervisor.homeassistant.core] Watchdog found Home Assistant failed, restarting...
22-11-01 18:01:11 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/backup/b328863a.tar: unexpected end of data
22-11-01 18:01:11 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/backup/0fead286.tar: unexpected end of data
22-11-01 18:01:11 INFO (MainThread) [main] Running Supervisor
22-11-01 18:01:24 ERROR (SyncWorker_2) [supervisor.docker.manager] Image homeassistant/amd64-addon-configurator:5.4.1 does not exist for addon_core_configurator
22-11-01 18:01:24 WARNING (MainThread) [supervisor.addons] Can't start Add-on core_configurator

#

22-11-01 18:01:24 ERROR (SyncWorker_6) [supervisor.docker.manager] Image ghcr.io/hassio-addons/appdaemon/amd64:0.9.3 does not exist for addon_a0d7b954_appdaemon
22-11-01 18:01:24 WARNING (MainThread) [supervisor.addons] Can't start Add-on a0d7b954_appdaemon
22-11-01 18:01:24 ERROR (SyncWorker_4) [supervisor.docker.manager] Image ghcr.io/hassio-addons/log-viewer/amd64:0.14.0 does not exist for addon_a0d7b954_logviewer
22-11-01 18:01:24 WARNING (MainThread) [supervisor.addons] Can't start Add-on a0d7b954_logviewer
22-11-01 18:02:11 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config:
22-11-01 18:02:47 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config:
22-11-01 18:03:23 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config:
22-11-01 18:03:59 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config:
22-11-01 18:04:35 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config:

#

I can pull the docker image homeassistant/amd64-addon-configurator:5.4.1 to eliminate one of the errors

agile hazel Nov 2, 2022, 1:20 AM

#

Are you sure you're running HAOS? If so you really really shouldn't be messing with anything

#

Container, OS, etc should be managed for you

shut schooner Nov 2, 2022, 2:36 AM

#

Yeah I'm pretty sure I'm running HAOS. I don't really want to mess with anything but something isn't working and I don't know how to fix it

agile hazel Nov 2, 2022, 2:38 AM

#

shut schooner Yeah I'm pretty sure I'm running HAOS. I don't really want to mess with anything...

How did you install it. Did you install debian then install something on top, or did you grab the image from the website and flash directly

#

An idea could be doing a full backup then a full reinstall. See if your install is borked or something with your config

#What exactly is your install method and