-
Notifications
You must be signed in to change notification settings - Fork 482
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
deCONZ 2.04.40 removes devicemembership attribute? #856
Comments
They removed this attribute (and some others) from the API in 3a29b43.
Indeed, I don't care for the other attributes, but
You can get this info from the sensors |
I sure would like to petition to bring the devicemembership back in the standard REST API 👍 as I am actively using it in the plugin. Or at least an indicator that a group was created for sensors e.g.: |
will revert back to 2.05.39, until this is fixed |
Upps sorry, didn't know anybody other than the WebApp/Phoscon App does use the devicemembership attribute. Thanks @ebaauw for bringing it back. Please keep in mind the attribute name might be a bit misleading, since it only represents "the group is owned by the device". With the switch editor we also control regular groups via rules, the related sensor ids are not part of the controlled groups |
With 2.0.5.41 the issue is resolved. Thanks all! |
It seems that with the release of deCONZ 2.05.40 the groups attribute "devicemembership" is removed. In my plugin I am using this attribut to determine if the group at hand is generated for a sensor. Most often these groups are "hidden" for users of my plugin as there is little use for these groups in Homeseer.
But now this attribute is not present anymore and the plugin has no other way to recognise these "sensor" groups. I would prefer to have the attribute available stil, or is there another way of recognise a group for sensors?
Wim
The text was updated successfully, but these errors were encountered: