-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
[Bug] Category of bridged devices is always Other
#903
Comments
Any feature request you are proposing? |
@itavero Sorry for only getting back to you now, been dealing with some health stuff. 😬 |
Yes, but a single accessory can use multiple converters, so they should somehow have a priority between them. |
Correct. According to HAP spec, the primary service should be used here. |
Is there an existing issue for this?
Describe the bug
I was inspecting individual devices exposed through
homebridge-z2m
, and noticed that all devices have the same HAP accessory category ofOther
.This behavior can be attributed to the following line:
homebridge-z2m/src/platform.ts
Line 598 in cb71fd7
Because we're not explicitly specifying an accessory category, a default category is used by Homebridge. I'm not sure how relevant this is for bridged devices, but it might help in cases like #869... 🤔
Related devices
No response
Related Devices
No response
Steps To Reproduce
No response
Expected behavior
No response
Device entry
No response
Status update
No response
Messages from this plugin
No response
This plugin
1.11.0-beta.6
Homebridge
1.7.0
Zigbee2MQTT
1.39.0-dev
Homebridge Config UI X (if applicable)
No response
The text was updated successfully, but these errors were encountered: