core: 0.96b1 - Unresponsive HomeKit sensors cause the ui to go offline.
Home Assistant release with the issue: 0.95.3 Last working Home Assistant release: 0.94.0 Operating environment: Hassio on atomic pi x64. Component/platform: homekit controller / entity updates Description of problem: I have 15 paired switches via HomeKit controller each with 5 sensors. In my logs all I see this:
Even a curl request takes about 5 minutes to respond with the html content of curl http://localhost:8123
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 39 (14 by maintainers)
RE: parallel updates, theres a lock around use of the pairing, and the lock has to be taken in asyncio code before the connection pool is involved. So with the code you are running right now there can be at most 15 tasks (1 for each pairing) for HomeKit in the thread pool at any given time. If you have 85+ other tasks in the connection pool at once they are for other components. (The log message is from the async code so might be misleading about when the thread pool is full).
It’s quite pleasing that all 15 start and finishes can happen in 1s - i wasn’t expecting that at all from what you seemed to be describing.
The 15 different accessories are not aware of each other, theres a certain level of isolation. Normally this is good because you don’t want your flakey device screwing up your good devices. So it will actually be easier to finish the native asyncio client tha it wil to make the change you suggested, which will mean any remaining thread pool full problems will definitely not be my problem 🎉 🎉 🎉
Oh and homekit isn’t involved in urllib3.connectionpool, that’s definitely something else causing that. We do use httplib when setting up a secure session, but we definitely dont use urllib3 in homekit.
Cheers. I plan to capture that error upstream, so it will be a while before you stop seeing them entirely.
Obviously when i ‘fix’ it they will still be happening, i’ll just be hiding them from the logs really - i can’t do anything about networking failures at that level.