search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.83k stars 30.91k forks source link

Unable to connect to HA dashboard after Update to 2021.9.x #55797

Closed yousaf465 closed 3 years ago

yousaf465 commented 3 years ago

The problem

After upgrading to HA Core-2021.9.x ( i have tried 2021.9.0 beta , 2021,9.1, 2021.9.2, 2021.9.3) the HA starts up, after loading some entities it just refuses connection at home assistant.local:8123. but I can easily connect through SSH.

If ha core start command is give you can again access Lovelace for a few mins before core again shutdown.

ch: armv7 audio_input: None audio_output: None boot: true image: ghcr.io/home-assistant/raspberrypi4-homeassistant ip_address: 172.30.32.1 last_version: 2021.9.3 machine: raspberrypi4 port: 8123 ssl: false update_available: false version: 2021.9.3 version_latest: 2021.9.3 wait_boot: 600 watchdog: true

What is version of Home Assistant Core has the issue?

2021.9.3

What was the last working version of Home Assistant Core?

2021.8.8

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

➜  ~ ha core logs   
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2021-09-05 19:43:52 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration huawei_solar which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-05 19:43:52 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration tplink_router which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-05 19:43:52 ERROR (SyncWorker_1) [homeassistant.loader] The custom integration 'tplink_router' does not have a valid version key (None) in the manifest file and was blocked from loading. See https://developers.home-assistant.io/blog/2021/01/29/custom-integration-changes#versions for more details
2021-09-05 19:43:52 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration scheduler which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-05 19:43:52 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration localtuya which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-05 19:43:52 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ble_monitor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-05 19:43:52 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-05 19:43:52 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration sonoff which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-05 19:44:04 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 223e9a991af2ca5a73854309b692710fd11810d0ea52d65d86497022a51bd8ed from 192.168.18.157
2021-09-05 19:44:19 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 223e9a991af2ca5a73854309b692710fd11810d0ea52d65d86497022a51bd8ed from 192.168.18.157
2021-09-05 19:46:11 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: met, openuv, hacs
2021-09-05 19:47:16 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: gree, co2signal, forecast_solar, switch.gree, iperf3, device_tracker.ble_monitor
2021-09-05 19:47:20 WARNING (MainThread) [homeassistant.components.energy.sensor] Found unexpected state_class measurement for sensor.today_consumption
2021-09-05 19:47:20 WARNING (MainThread) [homeassistant.components.energy.sensor] Found unexpected state_class measurement for sensor.grid_exported_energy
2021-09-05 19:47:20 ERROR (MainThread) [homeassistant.components.sensor] Platform esphome does not generate unique IDs. ID esp-web-tools-esp32-e94da0sensorroom_temperature already exists - ignoring sensor.room_temperature
2021-09-05 19:47:20 ERROR (MainThread) [homeassistant.components.sensor] Platform esphome does not generate unique IDs. ID esp-web-tools-esp32-e94da0sensorroom_humidity already exists - ignoring sensor.room_humidity
2021-09-05 19:47:20 ERROR (MainThread) [homeassistant.components.sensor] Platform esphome does not generate unique IDs. ID esp-web-tools-esp32-e94da0sensorroom_battery_level already exists - ignoring sensor.room_battery_level
2021-09-05 19:47:20 ERROR (MainThread) [homeassistant.components.pvoutput.sensor] Unable to fetch data from PVOutput. Unauthorized 401: Disabled API Key
2021-09-05 19:47:20 WARNING (MainThread) [homeassistant.config_entries] Config entry '192.168.18.29' for synology_dsm integration not ready yet: {'api': None, 'code': -1, 'reason': 'Unknown', 'details': 'ConnectionError = <urllib3.connection.HTTPSConnection object at 0xa97cff28>: Failed to establish a new connection: [Errno 113] Host is unreachable'}; Retrying in background
2021-09-05 19:47:30 WARNING (MainThread) [homeassistant.config_entries] Config entry 'FreshTomato Router' for upnp integration not ready yet; Retrying in background
2021-09-05 19:47:32 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: None has no element 0 when rendering '{{ state_attr('switch.sonoff_100123b0a9', 'consumption').0 }}'
2021-09-05 19:47:32 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: None has no element 0 when rendering '{{ state_attr('switch.sonoff_100123b0a9', 'consumption').0 }}'
2021-09-05 19:47:36 WARNING (Recorder) [homeassistant.components.sensor.recorder] sensor.sun2000_10ktl_m1 has unknown unit W
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

Additional information

No response

Megachip commented 3 years ago

Same here,

seems it (or something else) just shutdown itself after about 1 or 2 hours:

[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
ha core info
arch: aarch64
audio_input: None
audio_output: None
boot: true
image: ghcr.io/home-assistant/raspberrypi4-64-homeassistant
ip_address: 172.30.32.1
last_version: 2021.9.3
machine: raspberrypi4-64
port: 8123
ssl: false
update_available: false
version: 2021.9.3
version_latest: 2021.9.3
wait_boot: 600
watchdog: true
ha core stats
blk_read: 0
blk_write: 0
cpu_percent: 0
memory_limit: 0
memory_percent: 0
memory_usage: 0
network_rx: 0
network_tx: 0

How to debug the "why" ?

Megachip commented 3 years ago 
2021-09-06 00:24:49 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.mi_flora_temperature is taking over 10 seconds
2021-09-06 00:26:52 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.mi_flora_battery is taking over 10 seconds
2021-09-06 00:32:32 WARNING (MainThread) [homeassistant.helpers.entity] Update of light.garage is taking over 10 seconds
2021-09-06 00:44:49 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.mi_flora_temperature is taking over 10 seconds
2021-09-06 00:46:52 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.mi_flora_battery is taking over 10 seconds
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
config $ ha su logs
21-09-06 00:22:49 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-09-06 00:50:42 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
21-09-06 00:50:42 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.PLUGIN
21-09-06 00:50:42 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
21-09-06 00:50:42 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
21-09-06 00:50:42 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
21-09-06 00:50:42 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.SUPERVISOR
21-09-06 00:50:42 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.CORE
21-09-06 00:50:42 INFO (MainThread) [supervisor.resolution.check] System checks complete
21-09-06 00:50:42 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-09-06 00:50:42 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-09-06 00:50:42 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
21-09-06 00:50:42 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
21-09-06 00:52:49 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-09-06 00:56:45 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/beta.json
21-09-06 00:56:51 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/danielperna84/hassio-addons repository
21-09-06 00:56:51 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/tjorim/addon-homebridge repository
21-09-06 00:56:52 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repository
21-09-06 00:56:52 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
21-09-06 00:56:52 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/adamoutler/HassOSConfigurator repository
21-09-06 00:56:52 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/marcelveldt/hassio-addons-repo repository
21-09-06 00:56:52 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository-edge repository
21-09-06 00:56:52 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/bestlibre/hassio-addons repository

Not sure, but maybe su checks killing ha?

yousaf465 commented 3 years ago

@Megachip it seems we both have mi.sensor in common. why not check with these integration removed?

Megachip commented 3 years ago

@Megachip it seems we both have mi.sensor in common. why not check with these integration removed?

In my case its https://github.com/custom-components/ble_monitor ... but why should an Integration do a clean shutdown of a container? I more think about SU, which was also upgrade to 2021.09.0 ... cause timestap is somehow fitting.

ludeeus commented 3 years ago

We found a custom integration xxxxx which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

Do you still see this with all custom integrations removed?

Megachip commented 3 years ago

@yousaf465 

2021-09-06 09:00:04 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration sonoff which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-06 09:00:04 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration weback which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-06 09:00:04 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ledfxrm which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-06 09:00:04 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration ble_monitor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-06 09:00:04 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration aarlo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-06 09:00:04 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration meross_cloud which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-06 09:00:04 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration ecowitt which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

So we have ble_monitor, hacs and sonoff in common, lets see if one of them occues the shutdown in 2021.09.X

@ludeeus hmm, stated core at about 9:00 ... was shutted down at excactly 10:00 ... feels like there is some job running since September release :/

Edit: Started at 10:24, died at 11:24 ... so maybe no cron ;)

yousaf465 commented 3 years ago

@yousaf465

2021-09-06 09:00:04 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration sonoff which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-06 09:00:04 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration weback which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-06 09:00:04 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ledfxrm which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-06 09:00:04 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration ble_monitor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-06 09:00:04 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration aarlo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-06 09:00:04 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration meross_cloud which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2021-09-06 09:00:04 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration ecowitt which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

So we have ble_monitor, hacs and sonoff in common, lets see if one of them occues the shutdown in 2021.09.X

@ludeeus hmm, stated core at about 9:00 ... was shutted down at excactly 10:00 ... feels like there is some job running since September release :/

Edit: Started at 10:24, died at 11:24 ... so maybe no corn ;)

to me it looks like ble_monitor

at least for you, it ran for 1 hour, for me, it is like 5mins max. I even tried after updating to HA OS 6.3. the supervisor was updated with it. Screenshot 2021-09-04 211733 after image

ludeeus commented 3 years ago

please report that to the author of that custom integration :+1:

yousaf465 commented 3 years ago

We found a custom integration xxxxx which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

Do you still see this with all custom integrations removed?

How to disable integrations from CLI?

Megachip commented 3 years ago

@yousaf465 which version do you have running? Your screenshots saying youre on 2021.08.X not on 2021.09.X

Disabled ble_monitor. Will report in 1h if this creates the issue, but guess not :(

How to disable integrations from CLI?

Maybe just rename the custom componentents folder?

Megachip commented 3 years ago

Disabled ble_monitor. Will report in 1h if this creates the issue, but guess not :(

Guessed right. Has nothing to do with ble_monitor :(

@ludeeus any why to figure out what shutting down the core after exactly 1h?

chriscn commented 3 years ago

Just thought I'd add my two cents to this, I have installed ble_monitor but never configured it. I have tried to reinstall Home Assistant and when I try and restore a backup. It just won't work.

Megachip commented 3 years ago

Do you still see this with all custom integrations removed?

jep ... and thats one of the reasons, why I not understand, why an unsolved issue which is reported by multiple users is closed withour being solved :(

yousaf465 commented 3 years ago

@yousaf465 which version do you have running? Your screenshots saying youre on 2021.08.X not on 2021.09.X

Disabled ble_monitor. Will report in 1h if this creates the issue, but guess not :(

How to disable integrations from CLI?

Maybe just rename the custom componentents folder?

I disabled ble_monitor and Huwai modem integration. Installed 2021.9.3, installed without any issues. working fine for the last 12 hours. checked HASCS, a new update of BLE_monitor was available, 5.0.2, which requires 2021.9.0 at least. updated, now my BLE monitor is not working. I think I have to setup Xiamoi ATC converted thermometer again. image image

Megachip commented 3 years ago

SCS, a new update of BLE_monitor was available, 5.0.2, which requires 2021.9.0 at least. updated, now my BLE monitor is not working. I think I have to s

Ill guess thats another issue like the original one or mine ... but created a new issue for that.

ludeeus commented 3 years ago

jep ... and thats one of the reasons, why I not understand, why an unsolved issue which is reported by multiple users is closed withour being solved :(

This issue was closed because all elements pointed to it being an issue with a custom integration, and even after that it's still for the most part been related to custom integrations. If you still see this and have disabled all custom integrations, please open a new issue with the up-to-date information and logs for your system, this issue is untrackable with all that is going on here. Thanks :+1: