Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
HomeBridge falls on its face when any one platform has an issue
See original GitHub issueExpected Behavior
If a single platform stops working as expected the accessories associated with that platform can go into a ‘not responding’ state, but all other platforms/accessories added to homebridge should continue to function.
Current Behavior
All accessories in homebridge will go to ‘not responding’ whenever there is a problem with any one platform
Steps to Reproduce (for bugs)
Add the homebridge-myq2 v1.1 plugin to your homebridge installation All accessories in homebridge will go to ‘not responding’ even though the problem is only with homebridge-myq2
(see this issue: https://github.com/hjdhjd/homebridge-myq2/issues/4 )
E.g. All of my Nest accessories went unresponsive because MyQ changed their API. It would be nice if homebridge provided isolation. I realize this could be avoided by running a separate instance of homebridge for each platform, but that further complicates an already relatively complex setup.
Versions
- Homebridge: `0.4.46
- Node: v8.10.0
- OS: Ubuntu 18.04.3 LTS
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:12 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
That’s very much the point though. It’s a workaround, not a fix.
Maybe we can ask for better plugin error handling as a feature?
Technically, it may not be BUG for Homebridge because it works fine.
Keeping it running when a plugin fails sounds pretty reasonable. The whole MyQ event being a great example.