bug: Initializing Error

[Bentley0227]

Huge thank you for making something for these!

Describe the bug
It does not initialize and I am getting these errors.

This error originated from a custom integration.

Logger: custom_components.hatch_rest.api
Source: custom_components/hatch_rest/api.py:231
integration: Hatch Rest (documentation)
First occurred: 7:52:43 PM (189 occurrences)
Last logged: 11:17:52 PM

Exception during refresh_data -- BleakDBusError('org.bluez.Error.Failed', 'Not connected')
Exception during refresh_data -- AttributeError("'NoneType' object has no attribute 'read_gatt_char'")
Exception during refresh_data -- BleakDBusError('org.bluez.Error.Failed', 'Operation failed with ATT error: 0x0e')

This error originated from a custom integration.

Logger: custom_components.hatch_rest.api
Source: custom_components/hatch_rest/api.py:109
integration: Hatch Rest (documentation)
First occurred: 7:53:59 PM (181 occurrences)
Last logged: 11:17:52 PM

Exception during _client_connect -- BleakNotFoundError('D0:26:45:6E:E6:29 - D0:26:45:6E:E6:29: Failed to connect after 9 attempt(s): TimeoutError')
Exception during _client_connect -- BleakNotFoundError('D0:26:45:6E:E6:29 - D0:26:45:6E:E6:29: Failed to connect after 6 attempt(s): TimeoutError')
Exception during _client_connect -- BleakOutOfConnectionSlotsError('D0:26:45:6E:E6:29 - D0:26:45:6E:E6:29: Failed to connect after 9 attempt(s): No backend with an available connection slot that can reach address D0:26:45:6E:E6:29 was found: The proxy/adapter is out of connection slots or the device is no longer reachable; Add additional proxies (https://esphome.github.io/bluetooth-proxies/) near this device')
Exception during _client_connect -- BleakOutOfConnectionSlotsError('C4:8A:0D:D5:0B:6C - C4:8A:0D:D5:0B:6C: Failed to connect after 11 attempt(s): No backend with an available connection slot that can reach address C4:8A:0D:D5:0B:6C was found: The proxy/adapter is out of connection slots or the device is no longer reachable; Add additional proxies (https://esphome.github.io/bluetooth-proxies/) near this device')
Exception during _client_connect -- BleakOutOfConnectionSlotsError('C4:8A:0D:D5:0B:6C - C4:8A:0D:D5:0B:6C: Failed to connect after 10 attempt(s): No backend with an available connection slot that can reach address C4:8A:0D:D5:0B:6C was found: The proxy/adapter is out of connection slots or the device is no longer reachable; Add additional proxies (https://esphome.github.io/bluetooth-proxies/) near this device')

Logger: homeassistant.config_entries
Source: config_entries.py:761
First occurred: 7:56:30 PM (2 occurrences)
Last logged: 11:18:24 PM

Error setting up entry Mom And Dad for hatch_rest
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 761, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/hatch_rest/init.py", line 43, in async_setup_entry
await coordinator.async_config_entry_first_refresh()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 318, in async_config_entry_first_refresh
await self._async_config_entry_first_refresh()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 343, in _async_config_entry_first_refresh
await self._async_refresh(
...<3 lines>...
)
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 419, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/hatch_rest/coordinator.py", line 65, in _async_update_data
await self.hatch_rest_device.refresh_data()
File "/config/custom_components/hatch_rest/api.py", line 234, in refresh_data
await self._client_disconnect()
File "/config/custom_components/hatch_rest/api.py", line 128, in _client_disconnect
await self._client.disconnect()
File "/usr/local/lib/python3.13/site-packages/habluetooth/wrappers.py", line 510, in disconnect
await self._backend.disconnect()
File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/client.py", line 450, in disconnect
reply = await self._bus.call(
^^^^^^^^^^^^^^^^^^^^^
...<6 lines>...
)
^
File "/usr/local/lib/python3.13/site-packages/dbus_fast/aio/message_bus.py", line 409, in call
await future
asyncio.exceptions.CancelledError: Global task timeout: Bootstrap stage 2 timeout

home-assistant_hatch_rest_2025-12-04T07-18-28.045Z.log

Sanity Checklist (please complete the following information):
[ Y] I have attached debug logs (see enabling-debug-logging)
[ This one is the closest of 3] My nearest Bluetooth adapter is n distance away from the Hatch Rest device
[ At the time of error yes but no one was using the app] A Hatch Rest mobile app is not currently paired with the Hatch Rest device
[ No, it was connected this morning and then disconnected sometime today] I have power cycled the Hatch Rest device

[jcgoette]

Can you attempt connecting again when mobile app is not paired/connected. I have run into an issue with this during development.

[sphawk88]

Can you attempt connecting again when mobile app is not paired/connected. I have run into an issue with this during development.

I got a similar error attempting to connect earlier (attempted remotely; no one is at home right now, however). My guess is my errors were also attributed to a poor Bluetooth connection (HA RP5 in basement; Hatch on second floor), which I will validate later today by moving the Hatch nearby to initialize and later mitigate with an external Bluetooth dongle (bought the ZEXMTE Z01 on Amazon for delivery next week).

[jcgoette]

Were you able to validate one way or the other?

[Bentley0227]

I was able to add more bluetooth (esp32 proxies) closer to the devices and have seen a major improvement. They still get mad it you try and do too many actions in a row, it seems to get bogged down.

…

On Jan 6, 2026, at 6:44 PM, Justin Goette ***@***.***> wrote: jcgoette left a comment (jcgoette/hatch_rest_homeassistant#4) <#4 (comment)> Were you able to validate one way or the other? — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFVTMPNFJMFQRRDEZIHFUNT4FRQHHAVCNFSM6AAAAACOADDRSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMJWHE4TENBRG4>. You are receiving this because you authored the thread.

[jcgoette]

Nice. If you want, the debug logs should show any queuing going on.

[steverice]

Possibly relevant data point: your log shows connect storms to two different MACs, and we hit the same failure signature (BleakNotFoundError ... Failed to connect after 6 attempt(s), then ATT error: 0x0e + 'NoneType' object has no attribute 'read_gatt_char' on the working device) on a setup with two Hatch-manufacturer devices in range — a 1st-gen Rest plus a Hatch Grow scale.

The Grow matches the integration's bluetooth matcher (manufacturer id 1076) and got a discovery flow, but it doesn't speak the Rest GATT profile, so its connection attempts retry-loop forever. On a single onboard adapter those doomed retries tie up the connection slot and starve the real Rest's connection — commands to the working device start failing with the ATT/NoneType errors above. Ignoring the non-Rest device's discovery flow (Settings → Devices & Services → discovered card → Ignore) stopped the storms immediately for us.

If your two MACs are also a Rest + some other Hatch product (or a Rest that's paired to the phone app), same shape. Two things that would harden this: don't open a BLE connection during the discovery step (defer whatever needs a connection to after the entry is created), and tighten the matcher beyond manufacturer id so non-Rest Hatch products don't generate flows at all.