J. Nick Koston
J. Nick Koston
``` 2025-01-03 23:51:21.836 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 10.1.11.19 data: Unable to query the device 10.1.11.19:9999: 2025-01-03 23:51:58.406 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 10.1.11.19 data: Unable to query the device...
It does look like your event loop is being blocked for a bit by the assist pipeline. https://github.com/home-assistant/core/pull/130910 should fix that, but I haven't had time to finish that PR....
Looks like your system is being overloaded with tasks 
It looks like connect is also failing for the tplink xortransport 
> [callgrind and cprof with triggers.zip](https://github.com/user-attachments/files/18312073/callgrind.and.cprof.with.triggers.zip) > > Here another callgrind with triggers to the lights  That one is timing out connecting as well So its likely either: 1....
https://github.com/python-kasa/python-kasa/pull/1424/files will improve the error reporting on timeout
> Bluetooth information incase this helps: > > ``` > Name: GVH5104_311C > Address: > Details: {'path': '/org/bluez/hci0/dev_', 'props': {'Address': '', 'AddressType': 'random', 'Name': 'GVH5104_311C', 'Alias': 'GVH5104_311C', 'Paired': False, 'Bonded':...
The data is enough but its not so useful unless it comes with a photo or screen shot of what the device is displaying with the same timestamp
The easiest way to do it is to turn on debug logs for `homeassistant.components.bluetooth`. You'll see all the updates in the log and than `tail -f` the log in a...
> > The easiest way to do it is to turn on debug logs for `homeassistant.components.bluetooth`. You'll see all the updates in the log and than `tail -f` the log...