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
Multi-resource devices #65
Comments
Just commented under issue #64. |
That's a bug alright. Should be fixed in v0.3.1. |
v0.3.2 looks like it did the trick. |
Could you please check v0.3.3? There's another issue with v0.3.2, see #64. |
installing right now and will give it a go. |
0.3.3 works great. thanks for the fix and for all the work on this plugin. |
Confirmed, works like a charme for the FLS-PP. Also kudos to you for all the great work on this plugin! |
Some devices, like the Hue motion sensor and the dresden electronic FLS-PP lp wireless ballast, use multiple resources on the Hue bridge. For each of these resources, homebridge-hue creates a separate HomeKit service.
Historically, homebridge-hue created a separate HomeKit accessory for each service. As of v0.3, homebridge-hue will create a single HomeKit accessory for a multi-resource device, containing the services for all its resources. The
AccessoryInformation
andBattery
services will be linked to the first resource on the Hue bridge for the device.Apart from HomeKit reflecting more accurately the real-world, this change reduces the number of accessories created by homebridge-hue. With the HomeKit limit of 99 bridged accessories, this allows homebridge to support more devices, without having to resort to running multiple instances. While there is another HomeKit limit of 99 services per accessory, we won't be hitting that limit.
This change has subtle, but only limited impact on the user experience:
After updating to homebridge-hue v0.3, the newly exposed accessories will appear in the default room. You will have to update manually any HomeKit rooms, groups, scenes, and rules that contained one of the old accessories (hence the bump in minor version number).
@pponce, @tkropf, could you please check if this works correctly for the FLS-PP?
The text was updated successfully, but these errors were encountered: