After upgrading 2025.5.3, integrations failing to start, automations do not load

Installation
1

I am having an odd issue, after a long period of stability. After upgrading to 2025.5.3, my instance just has not been stable.

After a hard (power-cycle) or soft (asking for a restart) restart, various integrations are failing to auto-start, some keep asking for authentication each and every time, most of my bluetooth devices via bt-proxy have stopped working, etc. For example, HACS is failing to start … but if I “Reload”

My automations are also not loading, just seeing an empty "welcome to automations screen, but the automations.yaml file exists and is correct in /config – verified via a backup. I’m half tempted to restore from backup and move to 2025.5.2 to see if it fixes things or if it’s something else but I also don’t want to undo in case it makes it worse.

I also noticed that 2025.5.4 has been released, and I still don’t see it in my update screen.

I have plenty of space on my Raspberry (using a SSD), and it isn’t over heating.

Here are some of the errors in the log file:

This repeats about a dozen times, with various packages:

2025-05-27 04:13:20.230 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to listdir with args ('/usr/local/lib/python3.13/site-packages/botocore/data',) inside the event loop by integration 'aws' at homeassistant/components/aws/__init__.py, line 177: async with session.create_client("iam", **aws_config) as client: (offender: /usr/local/lib/python3.13/site-packages/botocore/loaders.py, line 307: for d in os.listdir(possible_path)), please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+aws%22
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#listdir
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 227, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 213, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 154, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 706, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 677, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 2034, in _run_once
    handle._run()
  File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/components/aws/__init__.py", line 177, in _validate_aws_credentials
    async with session.create_client("iam", **aws_config) as client:


2025-05-27 04:13:32.253 WARNING (ImportExecutor_0) [py.warnings] /usr/local/lib/python3.13/site-packages/pydub/utils.py:300: SyntaxWarning: invalid escape sequence '\('
  m = re.match('([su]([0-9]{1,2})p?) \(([0-9]{1,2}) bit\)$', token)

2025-05-27 04:18:05.233 ERROR (MainThread) [pylutron_caseta.leap] Was not expecting message with tag af26952f-e582-4bd3-ad2b-6efab5438e3d: {'CommuniqueType': 'ReadResponse', 'Header': {'MessageBodyType': 'MultipleDeviceDefinition', 'StatusCode': '200 OK', 'Url': '/device'}, 'Body': {'Devices': [{'Name': 'Smart Bridge 2', 'DeviceType': 'SmartBridge', 'href': '/device/1', 'SerialNumber': 108819454, 'FullyQualifiedName': ['Smart Bridge 2'], 'Parent': {'href': '/project'}, 'ModelNumber': 'L-BDG2-WH', 'RepeaterProperties': {'IsRepeater': True}, 'OwnedLinks': [{'href': '/link/1', 'LinkType': 'RF'}], 'LinkNodes': [{'href': '/device/1/linknode/1'}], 'DeviceRules': [{'href': '/devicerule/40'}], 'FirmwareImage': {'Firmware': {'DisplayName': '08.20.12f000'}, 'Installed': {'Year': 2025, 'Month': 2, 'Day': 27, 'Hour': 3, 'Minute': 12, 'Second': 52, 'Utc': '-5:00:00'}}, 'DeviceFirmwarePackage': {'Package': {'DisplayName': '001.003.000r000'}}, 'AddressedState': 'Addressed', 'IsThisDevice': True, 'AssociatedLink': {'href': '/link/1'}}, {'Name': 'Lights', 'DeviceType': 'WallSwitch', 'AssociatedArea': {'href': '/area/2'}, 'href': '/device/2', 'SerialNumber': 85981175, 'FullyQualifiedName': ['Hallway', 'Lights'], 'Parent': {'href': '/project'}, 'ModelNumber': 'PD-8ANS-XX', 'LocalZones': [{'href': '/zone/1'}], 'LinkNodes': [{'href': '/device/2/linknode/2'}], 'DeviceRules': [{'href': '/devicerule/44'}], 'FirmwareImage': {'href': '/firmwareimage/2', 'Device': {'href': '/device/2'}, 'Contents': [{'Type': 'CCA', 'OS': {'Firmware': {'DisplayName': '001.053.000r000'}}}]}, 'AddressedState': 'Addressed', 'AssociatedLink': {'href': '/link/1'}}]}}

One of the ones that now keeps asking for authentication after each restart but hasn’t asked in years to auth.

2025-05-27 04:21:23.835 ERROR (MainThread) [homeassistant.components.sleepiq] Could not authenticate with SleepIQ server

Connection errors:

2025-05-27 04:21:24.056 WARNING (MainThread) [aioesphomeapi.connection] sonoff-s31-35f1aa @ 192.168.66.220: Connection error occurred: sonoff-s31-35f1aa @ 192.168.66.220: EOF received
2025-05-27 04:21:24.057 WARNING (MainThread) [aioesphomeapi.connection] esp32-bluetooth-proxy-0071d4 @ 192.168.66.82: Connection error occurred: esp32-bluetooth-proxy-0071d4 @ 192.168.66.82: EOF received
2025-05-27 04:21:24.059 WARNING (MainThread) [aioesphomeapi.connection] everything-presence-lite-e7d904 @ 192.168.66.169: Connection error occurred: everything-presence-lite-e7d904 @ 192.168.66.169: EOF received
2025-05-27 04:21:24.060 WARNING (MainThread) [aioesphomeapi.connection] everything-presence-lite-f1c2cc @ 192.168.66.128: Connection error occurred: everything-presence-lite-f1c2cc @ 192.168.66.128: EOF received
2025-05-27 04:21:24.061 WARNING (MainThread) [aioesphomeapi.connection] everything-presence-one-5509d0 @ 192.168.66.219: Connection error occurred: everything-presence-one-5509d0 @ 192.168.66.219: EOF received

A critical for HACS, works after restart and a “reload”:

2025-05-27 04:21:24.068 CRITICAL (MainThread) [custom_components.hacs] <HacsData restore> [Global task timeout] Restore Failed!
Traceback (most recent call last):
  File "/config/custom_components/hacs/utils/data.py", line 213, in restore
    await self.register_unknown_repositories(repositories)
  File "/config/custom_components/hacs/utils/data.py", line 256, in register_unknown_repositories
    await asyncio.sleep(0)
  File "/usr/local/lib/python3.13/asyncio/tasks.py", line 706, in sleep
    await __sleep0()
  File "/usr/local/lib/python3.13/asyncio/tasks.py", line 700, in __sleep0
    yield
asyncio.exceptions.CancelledError: Global task timeout
asyncio.exceptions.CancelledError: Global task timeout
2025-05-27 04:21:24.260 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry https://192-168-1-5.a2f035a0be054364b67f297774dd8e9a.plex.direct:32400 for plex
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 749, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/plex/__init__.py", line 251, in async_setup_entry
    await hass.async_add_executor_job(get_plex_account, plex_server)
asyncio.exceptions.CancelledError: Global task timeout
2025-05-27 04:21:24.266 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry arXXXXXXXXXXom for tuya
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 749, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/tuya/__init__.py", line 168, in async_setup_entry
    await hass.async_add_executor_job(manager.refresh_mq)
asyncio.exceptions.CancelledError: Global task timeout

… I don’t think this is related but 50% of the log file is homekit devices saying this with various components.

2025-05-27 04:21:41.103 WARNING (MainThread) [homeassistant.components.homekit] Cannot add binary_sensor.front_driver_window_2020_rav4_hybrid_limited_awd_suv as this would exceed the 150 device limit. Consider using the filter option
2

Turned out the problem was HomeKit and a little configuration limitation that I didn’t know about. Looks like HomeAssistant has a 150 device limit. With HomeKit enabled and not filtered the limit was being reached and nothing after that was loading.

I completely removed HomeKit which wasn’t working anyway and also removed a whole bunch of integrations that I had enabled but wasn’t using in automation or data tracking. Everything is back to a working state.

3

Aram,

I am not completely understanding. Are you saying that Home Assistant can only handle 150 devices max? Or are you saying that HomeKit has a 150 device limit? I do not think that Home Assistant has an actual Device limit.

4

I think HomeKit has the 150 element limit, but it also has either a “fatal” issue or Homeassistant itself has a element limit.

Here is the log entries that I’m basing that assumption off:

This is my automation in HomeAssistant, not HomeKit … so maybe the 150 is the limit of HA ↔ HomeKit? Either way it was blocking HA components and integrations from working.

2025-05-28 03:41:30.751 WARNING (MainThread) [homeassistant.components.homekit] Cannot add automation.home_make_coffee as this would exceed the 150 device limit. Consider using the filter option

After I disabled and removed all HomeKit (none of it was working anyway), my automations started to load, my integrations all successfully started and are working.

5

Oh ok, that does make sense. HomeKit does only allow 150 devices to be added to a single hub. Home Assistant is only limited by your radio’s limits.

6

Okay that makes sense.

The part that it stops HA from completing starting though that remains an odd issue because of that.