Home Assistant is starting, not everything will be available until it is finished

Tovrin · July 17, 2020, 10:28am

That seems to have done the trick

bdraco · July 19, 2020, 5:45pm

We will automatically detect this in 0.114 and later

github.com/home-assistant/core

Automatically recover when the sqlite3 database is malformed or corrupted

home-assistant:dev ← bdraco:sqlite_corrupt_check

opened 11:13PM - 17 Jul 20 UTC

bdraco

+96 -6

## Breaking change  Automatically recover when the sqlite3 database is malformed or corrupted. Validate sqlite database on startup and move away if corruption is detected. If corruption is detected, the database is renamed to `home-assistant_v2.db.corrupt.{ISOTIME}` and startup proceeds with a fresh database. ``` 2020-07-17 23:45:05 ERROR (Recorder) [homeassistant.components.recorder.util] The database at /config/home-assistant_v2.db is corrupt or malformed. Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/recorder/util.py", line 125, in validate_sqlite_database conn.cursor().execute("PRAGMA QUICK_CHECK") sqlite3.DatabaseError: database disk image is malformed 2020-07-17 23:45:05 ERROR (Recorder) [homeassistant.components.recorder.util] The system will rename the corrupt database file /config/home-assistant_v2.db to /config/home-assistant_v2.db.corrupt.2020-07-17T23:45:05.678820+00:00 in order to allow startup to proceed ``` ## Type of change  - [ ] Dependency upgrade - [ ] Bugfix (non-breaking change which fixes an issue) - [ ] New integration (thank you!) - [x] New feature (which adds functionality to an existing integration) - [ ] Breaking change (fix/feature causing existing functionality to break) - [ ] Code quality improvements to existing code or addition of tests ## Example entry for `configuration.yaml`:  ```yaml # Example configuration.yaml ``` ## Additional information  - This PR fixes or closes issue: fixes # - This PR is related to issue: - Link to documentation pull request: ## Checklist  - [x] The code change is tested and works locally. - [ ] Local tests pass. **Your PR cannot be merged unless tests pass** - [ ] There is no commented out code in this PR. - [ ] I have followed the [development checklist][dev-checklist] - [ ] The code has been formatted using Black (`black --fast homeassistant tests`) - [x] Tests have been added to verify that the new code works. If user exposed functionality or configuration variables are added/changed: - [ ] Documentation added/updated for [www.home-assistant.io][docs-repository] If the code communicates with devices, web services, or third-party tools: - [ ] The [manifest file][manifest-docs] has all fields filled out correctly. Updated and included derived files by running: `python3 -m script.hassfest`. - [ ] New or updated dependencies have been added to `requirements_all.txt`. Updated by running `python3 -m script.gen_requirements_all`. - [ ] Untested files have been added to `.coveragerc`. The integration reached or maintains the following [Integration Quality Scale][quality-scale]:  - [ ] No score or internal - [ ] 🥈 Silver - [ ] 🥇 Gold - [ ] 🏆 Platinum  [dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html [manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html [quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html [docs-repository]: https://github.com/home-assistant/home-assistant.io

Schaussi · July 22, 2020, 7:37pm

For me this is solved with today’s v0.113; might have been caused by the Tesla integration in my case.

RonJ103 · July 25, 2020, 8:45pm

I’m running into this now too. Home Assistant won’t start up all the way. I’ve tried rolling back to a previous snapshot, upgraded to version 113.1, deleted my home-assistant_v2.db file, nothing seems to work.

Edit: I’m running docker on an Intel NUC. Home Assistant wouldn’t even respond to a restart command from the web interface. I restarted the NUC out of total frustration and things seem to be working now.

rsaturns · July 25, 2020, 9:19pm

I’m still having the same issue as well even on the latest update. However in my case it’s just zwave that hangs. I have to go in and start the network manually. Otherwise it works.

taoyx_2002 · July 25, 2020, 9:23pm

Sameting happened here.

I have 2 environment: 1 on Pi 3B+; the other one on a virtual machine. I really tried many things, but no luck:

Here are some observations:

the UI will always show “Home Assistant is starting, not everything will be available until it’s finished” all of the time, even for 1 night;
There is no much error in the log file (under config folder). but I guess, this problem is always goes with a warning as : “Ended unfinished session”

2020-07-25 21:03:58 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=108 from 2020-07-25 20:53:03.432961)
2020-07-25 21:04:07 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.2.37
2020-07-25 21:04:12 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 172.30.32.2

from the VNC, it shows it firstly stucked at: hassio port(vethe… )-- refer the screecut.
error1458×430 16.1 KB
with this problem, the "automation function will not work, and some time, some of addone is not working…
reloading the earlier working snapshot could not solve the problem

RonJ103 · July 25, 2020, 11:48pm

My zwave was hanging too. It may be a symptom of home assistant not starting up all the way.

litinoveweedle · July 26, 2020, 6:36pm

I am on Supervised installation on NUC, with 113.1 having completely same issue after upgrade from 112.4 - after restarting Home Assistant it is taking ages to start with the same message:

Home Assistant is starting, not everything will be available until it is finished.

I did increase logging verbosity but I do not see any issues in the log. I did restarted whole NUC and also purged HA DB, all without luck. ;-o

Immediately after update to 113.1 it took about 10minutes to load, Now aftter I deleted DB it seems it will not restart at all…

litinoveweedle · July 26, 2020, 6:55pm

I found this in the system log:

20-07-26 18:35:08 INFO (SyncWorker_6) [supervisor.docker.interface] Restart homeassistant/intel-nuc-homeassistant
20-07-26 18:45:14 WARNING (MainThread) [supervisor.homeassistant] Don’t wait anymore of Home Assistant startup!
20-07-26 18:45:14 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name=‘Task-3043’ coro=<process_lock..wrap_api() done, defined at /usr/src/supervisor/supervisor/utils/init.py:22> exception=HomeAssistantError()>
Traceback (most recent call last):
File “/usr/src/supervisor/supervisor/utils/init.py”, line 31, in wrap_api
return await method(api, *args, **kwargs)
File “/usr/src/supervisor/supervisor/homeassistant.py”, line 421, in restart
await self._block_till_run()
File “/usr/src/supervisor/supervisor/homeassistant.py”, line 638, in _block_till_run
raise HomeAssistantError()
supervisor.exceptions.HomeAssistantError

History and Logbook are available, but that is all… :-o

litinoveweedle · July 26, 2020, 7:15pm

OK, it is ONVIF, once I removed whole integration HA started immediately!

bdraco · July 26, 2020, 9:33pm

I’ve attempted a fix, but since I don’t have an onvif camera I am unable to verify it

litinoveweedle · July 26, 2020, 9:52pm

Hello, I did tested with my installation and confirmed our solution is working perfectly! Thank you very much! I did confirmed my test results as well on github.

BigHomie · July 26, 2020, 11:27pm

Hello. Same issue here. With version 112.4 everything works fine and UI loads pretty fast. After updating to 113.1 the message “home assistant is starting, not everything will be available until is finished” stays until home assistant rolls back to previous version. Also some of my sensors showing as unavailable. Sonoff integration from HACS and Edge Max. Here is my log.

20-07-26 22:53:08 INFO (MainThread) [supervisor.auth] Cache hit for BigHomie
20-07-26 22:53:32 ERROR (MainThread) [asyncio] Unclosed connection
client_connection: Connection<ConnectionKey(host='172.30.32.1', port=65481, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None)>
20-07-26 22:58:12 INFO (MainThread) [supervisor.auth] Auth request from core_mosquitto for BigHomie
20-07-26 22:58:12 INFO (MainThread) [supervisor.auth] Home Assistant not running, check cache
20-07-26 22:58:12 INFO (MainThread) [supervisor.auth] Cache hit for BigHomie
20-07-26 22:59:09 INFO (SyncWorker_6) [supervisor.docker.interface] Update image 89275b70/amd64-addon-dss_voip:3.3.2 to 89275b70/amd64-addon-dss_voip:3.3.3
20-07-26 22:59:09 INFO (SyncWorker_6) [supervisor.docker.addon] Start build 89275b70/amd64-addon-dss_voip:3.3.3
20-07-26 22:59:22 INFO (SyncWorker_6) [supervisor.docker.addon] Build 89275b70/amd64-addon-dss_voip:3.3.3 done
20-07-26 22:59:22 INFO (SyncWorker_6) [supervisor.docker.interface] Stop addon_89275b70_dss_voip application
20-07-26 22:59:23 INFO (SyncWorker_6) [supervisor.docker.interface] Clean addon_89275b70_dss_voip application
20-07-26 22:59:23 INFO (SyncWorker_0) [supervisor.docker.interface] Cleanup images: ['89275b70/amd64-addon-dss_voip:3.3.2']
20-07-26 22:59:23 INFO (MainThread) [supervisor.addons] Add-on '89275b70_dss_voip' successfully updated
20-07-26 22:59:24 INFO (SyncWorker_4) [supervisor.docker.addon] Start Docker add-on 89275b70/amd64-addon-dss_voip with version 3.3.3
20-07-26 22:59:24 INFO (MainThread) [supervisor.api.security] /host/info access from 89275b70_dss_voip
20-07-26 23:01:35 INFO (SyncWorker_4) [supervisor.docker.interface] Update image hassioaddons/appdaemon-amd64:0.2.4 to hassioaddons/appdaemon-amd64:0.2.6
20-07-26 23:01:35 INFO (SyncWorker_4) [supervisor.docker.interface] Pull image hassioaddons/appdaemon-amd64 tag 0.2.6.
20-07-26 23:01:39 ERROR (MainThread) [supervisor.utils] Can't execute update while a task is in progress
20-07-26 23:01:39 ERROR (MainThread) [supervisor.utils] Can't execute cleanup while a task is in progress
20-07-26 23:01:39 INFO (MainThread) [supervisor.addons] Add-on 'a0d7b954_appdaemon' successfully updated
20-07-26 23:01:39 WARNING (MainThread) [supervisor.addons.addon] a0d7b954_appdaemon already running!
20-07-26 23:01:44 INFO (SyncWorker_4) [supervisor.docker.interface] Stop addon_a0d7b954_appdaemon application
20-07-26 23:01:45 WARNING (MainThread) [supervisor.homeassistant] Don't wait anymore of Home Assistant startup!
20-07-26 23:01:45 CRITICAL (MainThread) [supervisor.homeassistant] HomeAssistant update fails -> rollback!
20-07-26 23:01:45 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.112.4
20-07-26 23:01:45 INFO (SyncWorker_2) [supervisor.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.113.1 to homeassistant/qemux86-64-homeassistant:0.112.4
20-07-26 23:01:45 INFO (SyncWorker_2) [supervisor.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.112.4.
20-07-26 23:01:47 INFO (SyncWorker_2) [supervisor.docker.interface] Stop homeassistant application
20-07-26 23:01:49 INFO (SyncWorker_4) [supervisor.docker.interface] Clean addon_a0d7b954_appdaemon application
20-07-26 23:01:49 INFO (SyncWorker_1) [supervisor.docker.interface] Cleanup images: ['hassioaddons/appdaemon-amd64:0.2.4']
20-07-26 23:01:50 INFO (MainThread) [supervisor.addons] Add-on 'a0d7b954_appdaemon' successfully updated
20-07-26 23:01:50 INFO (SyncWorker_4) [supervisor.docker.addon] Start Docker add-on hassioaddons/appdaemon-amd64 with version 0.2.6
20-07-26 23:01:51 INFO (SyncWorker_2) [supervisor.docker.interface] Clean homeassistant application
20-07-26 23:01:51 INFO (MainThread) [supervisor.homeassistant] Update pulse/client.config: /data/tmp/homeassistant_pulse
20-07-26 23:01:51 INFO (SyncWorker_5) [supervisor.docker.homeassistant] Start homeassistant homeassistant/qemux86-64-homeassistant with version 0.112.4
20-07-26 23:01:51 INFO (MainThread) [supervisor.api.security] /host/info access from a0d7b954_appdaemon
20-07-26 23:02:03 INFO (MainThread) [supervisor.homeassistant] Updated Home Assistant API token
20-07-26 23:02:06 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation in progress
20-07-26 23:02:31 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation done
20-07-26 23:02:36 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation in progress
20-07-26 23:04:08 INFO (MainThread) [supervisor.auth] Auth request from core_mosquitto for BigHomie
20-07-26 23:04:08 INFO (MainThread) [supervisor.auth] Home Assistant not running, check cache
20-07-26 23:04:08 INFO (MainThread) [supervisor.auth] Cache hit for BigHomie
20-07-26 23:04:12 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation done
20-07-26 23:04:17 INFO (MainThread) [supervisor.homeassistant] Detect a running Home Assistant instance
20-07-26 23:04:17 INFO (MainThread) [supervisor.homeassistant] Successful run Home Assistant 0.112.4
20-07-26 23:04:17 INFO (SyncWorker_2) [supervisor.docker.interface] Cleanup images: ['homeassistant/qemux86-64-homeassistant:0.113.1']
20-07-26 23:04:20 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-07-26 23:04:20 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon
20-07-26 23:04:21 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-07-26 23:04:21 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
20-07-26 23:04:21 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
20-07-26 23:04:21 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
20-07-26 23:05:27 INFO (SyncWorker_4) [supervisor.docker.interface] Update image esphome/esphome-hassio-amd64:1.14.3 to esphome/esphome-hassio-amd64:1.14.5
20-07-26 23:05:27 INFO (SyncWorker_4) [supervisor.docker.interface] Pull image esphome/esphome-hassio-amd64 tag 1.14.5.
20-07-26 23:06:10 INFO (SyncWorker_4) [supervisor.docker.interface] Stop addon_15ef4d2f_esphome application
20-07-26 23:06:11 INFO (SyncWorker_4) [supervisor.docker.interface] Clean addon_15ef4d2f_esphome application
20-07-26 23:06:12 INFO (SyncWorker_1) [supervisor.docker.interface] Cleanup images: ['esphome/esphome-hassio-amd64:1.14.3']
20-07-26 23:06:12 INFO (MainThread) [supervisor.addons] Add-on '15ef4d2f_esphome' successfully updated
20-07-26 23:06:12 INFO (SyncWorker_6) [supervisor.docker.addon] Start Docker add-on esphome/esphome-hassio-amd64 with version 1.14.5
20-07-26 23:06:13 INFO (MainThread) [supervisor.api.security] /host/info access from 15ef4d2f_esphome
20-07-26 23:07:01 INFO (SyncWorker_4) [supervisor.docker.interface] Update image homeassistant/amd64-addon-samba:9.1.0 to homeassistant/amd64-addon-samba:9.2.0
20-07-26 23:07:01 INFO (SyncWorker_4) [supervisor.docker.interface] Pull image homeassistant/amd64-addon-samba tag 9.2.0.
20-07-26 23:07:06 INFO (SyncWorker_4) [supervisor.docker.interface] Stop addon_core_samba application
20-07-26 23:07:11 INFO (SyncWorker_4) [supervisor.docker.interface] Clean addon_core_samba application
20-07-26 23:07:11 INFO (SyncWorker_1) [supervisor.docker.interface] Cleanup images: ['homeassistant/amd64-addon-samba:9.1.0']
20-07-26 23:07:11 INFO (MainThread) [supervisor.addons] Add-on 'core_samba' successfully updated
20-07-26 23:07:12 INFO (SyncWorker_6) [supervisor.docker.addon] Start Docker add-on homeassistant/amd64-addon-samba with version 9.2.0
20-07-26 23:10:09 INFO (MainThread) [supervisor.auth] Auth request from core_mosquitto for BigHomie
20-07-26 23:10:09 INFO (MainThread) [supervisor.auth] Success login from BigHomie
20-07-26 23:10:24 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.113.1
20-07-26 23:10:24 INFO (SyncWorker_0) [supervisor.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.112.4 to homeassistant/qemux86-64-homeassistant:0.113.1
20-07-26 23:10:24 INFO (SyncWorker_0) [supervisor.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.113.1.
20-07-26 23:11:17 INFO (SyncWorker_0) [supervisor.docker.interface] Stop homeassistant application
20-07-26 23:11:18 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Received message 8:1000 is not str
20-07-26 23:11:18 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed
20-07-26 23:11:18 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Received message 8:1000 is not str
20-07-26 23:11:18 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed
20-07-26 23:11:43 INFO (SyncWorker_0) [supervisor.docker.interface] Clean homeassistant application
20-07-26 23:11:44 INFO (MainThread) [supervisor.homeassistant] Update pulse/client.config: /data/tmp/homeassistant_pulse
20-07-26 23:11:44 INFO (SyncWorker_1) [supervisor.docker.homeassistant] Start homeassistant homeassistant/qemux86-64-homeassistant with version 0.113.1
20-07-26 23:11:59 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation in progress
20-07-26 23:12:01 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-07-26 23:13:27 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation done
20-07-26 23:15:17 INFO (MainThread) [supervisor.auth] Auth request from core_mosquitto for BigHomie
20-07-26 23:15:17 INFO (MainThread) [supervisor.auth] Home Assistant not running, check cache
20-07-26 23:15:17 INFO (MainThread) [supervisor.auth] Cache hit for BigHomie
20-07-26 23:20:20 INFO (MainThread) [supervisor.auth] Auth request from core_mosquitto for BigHomie
20-07-26 23:20:20 INFO (MainThread) [supervisor.auth] Home Assistant not running, check cache
20-07-26 23:20:20 INFO (MainThread) [supervisor.auth] Cache hit for BigHomie
20-07-26 23:23:31 WARNING (MainThread) [supervisor.homeassistant] Don't wait anymore of Home Assistant startup!
20-07-26 23:23:31 CRITICAL (MainThread) [supervisor.homeassistant] HomeAssistant update fails -> rollback!
20-07-26 23:23:31 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.112.4
20-07-26 23:23:31 INFO (SyncWorker_5) [supervisor.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.113.1 to homeassistant/qemux86-64-homeassistant:0.112.4
20-07-26 23:23:31 INFO (SyncWorker_5) [supervisor.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.112.4.
20-07-26 23:23:33 INFO (SyncWorker_5) [supervisor.docker.interface] Stop homeassistant application
20-07-26 23:23:37 INFO (SyncWorker_5) [supervisor.docker.interface] Clean homeassistant application
20-07-26 23:23:37 INFO (MainThread) [supervisor.homeassistant] Update pulse/client.config: /data/tmp/homeassistant_pulse
20-07-26 23:23:38 INFO (SyncWorker_0) [supervisor.docker.homeassistant] Start homeassistant homeassistant/qemux86-64-homeassistant with version 0.112.4
20-07-26 23:23:53 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation in progress

thomas.talving · August 3, 2020, 7:23pm

I’m having the same problem.

I’m on a clean install of Home assistant on a Raspberry Pi 4

no config or anything. Soooo annoying.

Any solutions?

AlainGeenrits · August 8, 2020, 10:24am

Same here. I wanted to do a clean install because 0.113 messed up RFXTRX. Thought I start with clean config.

I tried this on RPI3 and RPI4 with clean install, nothing connected. No integrations! The message "HA is starting… " Hangs for a long time. If I reboot the core It is the same thing. Any reboot and it does not even come back. I want to downgrade to 0.122.5 from the CLI, but no joy yet.

This is very annoying…

bdraco · August 8, 2020, 9:29pm

0.114 (due to be released Wednesday) should prevent almost all (won’t fix broken hardware, egregious integration code errors, or hard crashes) cases of integrations blocking startup. See https://github.com/home-assistant/core/issues/38274#issuecomment-670315963 for details

schettada · August 14, 2020, 4:34pm

I also have the same issue even in 114. I’m running a mysql for DB. I even setup a new DB and still have the same issue with a new DB. Not sure what to do with this error.

riemers · September 11, 2020, 9:12pm

Seems its my turn, some things don’t load like tesla/denon/hacs other things are fine. Weirdly not all docker images/integration where started too. Seems to be waiting, but on what?

davisstewart · February 6, 2021, 10:21am

After updating to Home Assistant 2021.2.0, HA is stuck and wont restart fully.

These are my Logs, any help would be appreciated.

2021-02-05 20:33:24 WARNING (MainThread) [homeassistant.setup] Setup of recorder is taking over 10 seconds.

2021-02-05 20:33:45 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=106 from 2021-02-05 15:25:02.006123)

2021-02-05 20:33:50 ERROR (MainThread) [homeassistant.components.panel_custom] Unable to register panel ZWave Graph: Either js_url, module_url or html_url is required.

2021-02-05 20:33:54 WARNING (MainThread) [zwave_js_server] Connected to a Zwave JS Server with an untested version, you may run into compatibility issues!

2021-02-05 20:33:57 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for 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-02-05 21:13:01 WARNING (Thread-8) [pychromecast.socket_client] [TV Living Room(192.xxx.xxxxx):8009] Heartbeat timeout, resetting connection

2021-02-05 21:13:20 ERROR (Thread-8) [pychromecast.socket_client] [TV Living Room(192.xxx.x.xxx):8009] Failed to connect to service Chromecast-db4d49562d2917bfa162d50d8cc659ca._googlecast._tcp.local., retrying in 5.0s

2021-02-05 23:39:54 WARNING (Thread-8) [pychromecast.socket_client] [TV Living Room(192.xxx.x.xx):8009] Heartbeat timeout, resetting connection

2021-02-05 23:40:24 ERROR (Thread-8) [pychromecast.socket_client] [TV Living Room(192.xxx.x.x):8009] Failed to connect to service Chromecast-db4d49562d2917bfa162d50d8cc659ca._googlecast._tcp.local., retrying in 5.0s

2021-02-06 02:18:56 WARNING (Thread-7) [pychromecast.socket_client] [Kitchen speaker(192.xxxxx):8009] Heartbeat timeout, resetting connection

2021-02-06 02:52:41 ERROR (Thread-10) [pychromecast.socket_client] [All speakers(192.xxx.x.x):32020] Error reading from socket.

2021-02-06 02:52:41 WARNING (Thread-10) [pychromecast.socket_client] [All speakers(192.xx.x.x):32020] Error communicating with socket, resetting connection

2021-02-06 02:52:41 ERROR (Thread-10) [pychromecast.socket_client] [All speakers(192.xxx.x.x):32020] Failed to connect to service Google-Cast-Group-6aed0016802f4e44b11f0b286843e393-1._googlecast._tcp.local., retrying in 5.0s

2021-02-06 02:53:11 WARNING (Thread-9) [pychromecast.socket_client] [Office speaker(192.xxxx.x):8009] Heartbeat timeout, resetting connection

2021-02-06 02:53:25 ERROR (Thread-10) [pychromecast.socket_client] [All speakers(192.xxx.x.x):32020] Error reading from socket.

2021-02-06 02:53:25 WARNING (Thread-10) [pychromecast.socket_client] [All speakers(192.xxx.x.x):32020] Error communicating with socket, resetting connection

2021-02-06 02:53:25 ERROR (Thread-10) [pychromecast.socket_client] [All speakers(xxxxxx):32020] Failed to connect to service Google-Cast-Group-6aed0016802f4e44b11f0b286843e393._googlecast._tcp.local., retrying in 5.0s

2021-02-06 02:53:40 WARNING (zeroconf-ServiceBrowser__googlecast._tcp.local._298) [homeassistant.components.cast.discovery] setup_internal_discovery failed to get info for 6aed0016-802f-4e44-b11f-0b286843e393, Google-Cast-Group-6aed0016802f4e44b11f0b286843e393._googlecast._tcp.local.

bdraco · February 6, 2021, 3:09pm

Try 2021.2.1

If that doesn’t solve it, please post a py-spy