-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use homebridge v2.0 dynamic platform accessories #1
Comments
Complete refactor to homebridge-zp, based on homebridge-lib to use the dynamic platform accessory model. See #1. Should also fix #81. Still work in progress. Todo: - Handle topology changes (e.g. create/split stereo pair); - Handle changed alarms (e.g. move to different zone); - Hanlde changed config.json (e.g. no longer expose LEDs). - Handle heartbeat 0 for LEDs to disable polling and use getter. Need improvements to homebridge-lib: - Startup sequence seems stable, but feels wrong. Probably should do synchronous creation of delegates vs asynchronous initialisation. - Remove accessory, service, characteristic when no longer needed. - Still issue with name change - simply remove/re-create? - Double-check tr/catch for every async call.
[email protected] uses dynamic platform accessories. New zone player should be exposed automatically, but missing zone players will propably stick around. When Changes to alarms are detected run time, moving the service to a different accessory, when a different zone (room) has been selected. |
Still to do:
|
TV inputs `AirPlay`, `Audio In`, and `TV In` to work on zone rather than on zone group, see #1.
Currently, homebridge-zp uses static platform accessories. Using dynamic accessories would enable homebirdge-zp to act on ZoneGroupTopology events (e.g. creating or breaking a stereo pair) without having to restart homebridge.
The text was updated successfully, but these errors were encountered: