System Bridge Blocks HA from loading

[Anto79-ops]

The problem

Hi,

On 2023.4.0b0 and with System Bridge enabled, HA times out on startup. Disabling System bridge and restarting HA, and no slow-down issue.

2023-03-30 05:33:29.722 WARNING (MainThread) [homeassistant.bootstrap] Setup timed out for bootstrap - moving forward

Please see profile files on two different occasions (extension changed to txt).

Please note, that database migration was also happening on this beta, and my system is currently experiencing elevated CPU usage even with system bridge disabled.

However, even after 3 hrs, and System Bridge disabled, I'm still experiencing an elevated CPU. Could be a different issue with regards to the elevated CPU usage.

2023-03-30 05:31:32.045 WARNING (MainThread) [homeassistant.helpers.frame] Detected integration that closes the Home Assistant aiohttp session. Please report issue for system_bridge using this method at homeassistant/components/system_bridge/__init__.py, line 250: await coordinator.websocket_client.close()

2023-03-30 05:49:48.961 WARNING (MainThread) [systembridgeconnector.websocket_client.WebSocketClient] Future already set for response ID: 29d98e5032934c9fab78b4763fcc101b

2023-03-30 05:28:05.870 ERROR (MainThread) [homeassistant.components.sensor] Platform system_bridge does not generate unique IDs. ID antonio-GC676AA-ABA-m8150n_filesystem_/proc/sys/fs/binfmt_misc already exists - ignoring sensor.antonio_gc676aa_aba_m8150n_proc_sys_fs_binfmt_misc_space_used

2023-03-30 05:31:32.467 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: binary_sensor.system_bridge, sensor.system_bridge

2023-03-30 05:49:48.919 ERROR (MainThread) [homeassistant.components.sensor] Platform system_bridge does not generate unique IDs. ID antonio-GC676AA-ABA-m8150n_filesystem_/proc/sys/fs/binfmt_misc already exists - ignoring sensor.antonio_gc676aa_aba_m8150n_proc_sys_fs_binfmt_misc_space_used

What version of Home Assistant Core has the issue?

2023.4.0b0

What was the last working version of Home Assistant Core?

2023.3.6

What type of installation are you running?

Home Assistant OS

Integration causing the issue

System Bridge

Link to integration documentation on our website

https://www.home-assistant.io/integrations/system_bridge/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @timmo001, mind taking a look at this issue as it has been labeled with an integration (system_bridge) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of system_bridge can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign system_bridge Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

system_bridge documentation
system_bridge source
_{^{(message by IssueLinks)}}

[Anto79-ops]

Update on the issue:

Problem still exists on b2

EDIT: Issue also exists on B6 when system bridge is enabled, but the high CPU utilization issue has been resolved (was not related to System Bridge).

[Anto79-ops]

Problem still exists on 2023.4.2.

`Logger: homeassistant.bootstrap
Source: bootstrap.py:153
First occurred: 11:36:00 PM (1 occurrences)
Last logged: 11:36:00 PM

Setup timed out for bootstrap - moving forward`

Disabling system bridge and startup are less thsn than 1.5 minutes.

[Anto79-ops]

hi all, thanks for pushing the PR 91171.

I wanted to mention that I'm still experiencing this issue on 2023.4.3. The observations (and log errors) are the same. When System Bridge is enabled, my HA instance goes to bootstrap timeout and the error message that something is blocking HA from starting (as above) appears in the logs.

When I disable system bridge and restart, my HA instance starts up in less than 1 minute.

@frenck should I just open up another issue or would you like to just open this up one again since the problem is still exactly the same on 2023.4.3 and 2023.4.4 thanks.

[timmo001]

@Anto79-ops go ahead and reopen.

I have set up a dev instance to try and weed out the issue

[Anto79-ops]

thanks, timmo! I actually cannot reopen this...let me try

@homeassistant reopen
@homeassistant open sesame

[timmo001]

Just realised I could do that. Thanks bdraco