Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Integration doesn't start after HA restart

See original GitHub issue

Immediately after adding integration (local http connection to the gateway), it works. Unfortunately after every HA restart it fails to start automatically displaying:

LOG shows nothing interesting, just “Cannot connect”:

2022-02-03 13:27:06 DEBUG (MainThread) [bosch_thermostat_client.gateway.ivt] Found supported device {'value': 'iCom_Low_NSC_v1', 'name': 'Enviline/Compress 6000/7000', 'type': 'NSC_ICOM_GATEWAY'} with id 172
2022-02-03 13:27:06 DEBUG (MainThread) [bosch_thermostat_client.gateway.ivt] Found supported device {'value': 'RC300', 'name': 'RC300/RC310/Nefit Moduline 3000', 'type': 'RC300_RC200'} with id 158
2022-02-03 13:27:06 DEBUG (MainThread) [bosch_thermostat_client.gateway.ivt] Using model iCom_Low_NSC_v1 as database schema
2022-02-03 13:27:06 DEBUG (MainThread) [bosch_thermostat_client.gateway.base] Found device {"value": "iCom_Low_NSC_v1", "name": "Enviline/Compress 6000/7000", "type": "NSC_ICOM_GATEWAY"}
2022-02-03 13:27:06 DEBUG (MainThread) [bosch_thermostat_client.db] Attempt to load database from file /usr/local/lib/python3.9/site-packages/bosch_thermostat_client/db/nsc_icom_gateway/040802.json
2022-02-03 13:27:06 DEBUG (MainThread) [bosch_thermostat_client.gateway.base] Loading database: NSC_ICOM_GATEWAY for firmware 04.08.02
2022-02-03 13:27:06 ERROR (MainThread) [custom_components.bosch] Cannot connect to Bosch gateway, host 192.168.3.223 with UUID: 918362517

After HA finish starting I need to start the integration manually (disable and then enable). It’s annoying.

As I see in LOG, some other integrations have also a problem with start in my installation (I suspect that database is too big or the computer too slow) but they eventually start fine because they are retrying in background:

WARNING (MainThread) [homeassistant.config_entries] Config entry 'Philips' for hue integration not ready yet: Error connecting to the Hue bridge at 192.168.3.207; Retrying in background
WARNING (MainThread) [homeassistant.components.select] Platform netatmo not ready yet: None; Retrying in background in 30 seconds

Would you implement the same “retrying in background” mechanism to solve such problems, please? Temporary, could you increase connection timeout (is it now 10s?)? Maybe it will help…

Issue Analytics

State:
Created 2 years ago
Comments:8

Top GitHub Comments

1reaction

pszafercommented, Feb 6, 2022

Fastest way currently is to reload integration when network available. I’ll try to figure it out for next release

0reactions

pszafercommented, Jun 29, 2022

Should be fixed in https://github.com/bosch-thermostat/home-assistant-bosch-custom-component/releases/tag/v0.18.0 .

Top Results From Across the Web

Integration not found - cannot reboot - Configuration

I cant restart HA because of this, so I cant reinstall HACS and begin from the start. See below for log. Logger: homeassistant.components....

ATAG integration doesn't work after restart #35190 - GitHub

Every time I restart HA, ATAG integration is unavailable. Deleting the integration, and then re-installing it, makes it work again. Logs say:

Home Assistant won't boot after restart : r/homeassistant - Reddit

The CLI has me locked into a "ha >" prompt so I am just currently looking through the internet trying to figure out...

Configuring Automatic Restart of an Oracle Database

Configure your Oracle database with the Oracle Restart feature to automatically restart the database, the listener, and other Oracle components after a ...

Create and configure a self-hosted integration runtime

The self-hosted integration runtime doesn't need to be on the same ... The self-hosted integration runtime starts the job after it polls the ......