node-red-contrib-homekit-bridged: If at least one device does not respond, all devises on bridge do not respond
Some devices do not connect to nr immediately after the start of the system and because of this constantly “No Response” on all devises on bridge. If i injected {"On":"NO_RESPONSE"} for one device see the same problem.
node-red - 1.0.2 node-red-contrib-homekit-bridged - 1.0.0-dev.1
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 54 (42 by maintainers)
Commits related to this issue
- Pass NO_RESPONSE Error in callback when accessory is unreachable. Revert updateReachability. (#185) — committed to NRCHKB/node-red-contrib-homekit-bridged by Shaquu 4 years ago
Everyone, just to add to the conversation
The behaviour from homebridge is that a single accessory per instance can be set to “Not Repsonding”. Code is here
https://github.com/NorthernMan54/homebridge-sensor-stub
This particular plugin turns on and off the various accessory status’s like low battery, fault and error in a contact sensor.
I no longer have an iOS 12 device, but I’m pretty sure the homekit overhaul they did in iOS 13 is to blame… there is so much stuff still broken (looks at color selection bug on lamps, statusfault not clearing unless hard killing home.app, …)
I will test it thanks!
Thank you @shaquu and @radionoise I’ll set up a dev branch and test later today.
Native device: Chamberlain homekit hub Accessory 1: Heidi Garage door Accessory 2: Garrett Garage door
I unplugged Garrett (my door) from the garage ceiling. The hub and Heidi’s door still respond fine. My door clicked right over to “No Response”
Screenshot: