Thanks
The seperate Zeroconf instance came in between 0.5.11 and 0.6.0. It’s been there for a while…
(Pretty hard to rollback to 0.5.11 given architecture changes, so wouldn’t recommend it. May be fine, but 0.5.11 and below no longer file saves the homekit device iids so they stay consistent. Which they mostly did anyway - but saving ensures they will.)
Pretty happy relates to Zeroconf. May yet change to a single Zeroconf thread / asyncio for all bridges. The previous attempt was obviously bogged down in plugin and bridge actions somewhere so was not happening quickly enough. Interesting one bridge only should not have noticed any difference - perhaps why not major reports.
More thinking aloud follows, while a ‘proper’ instance would probably also fix, it would create potential issues if Zeroconf instance fails with bridges/or rest plugin still up. Combining the 2 as I do here at least bypasses that potential complication. One combined instance would likely use less overhead potentially, but may not be that much difference overall. A seperate cooperating with other Zeroconf instances (as currently) with each bridge would likely in most, if not all circumstances be the most responsive.
The combination of Indigoserver, plugin, threads and asyncio (which zeroconf is and pyHAP homekit library) is a minefield basically.
Sent from my iPad using Tapatalk