Skip to content
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

Closed
wvuyk opened this issue Oct 12, 2018 · 5 comments
Closed

deCONZ 2.04.40 removes devicemembership attribute? #856

wvuyk opened this issue Oct 12, 2018 · 5 comments

Comments

@wvuyk
Copy link

wvuyk commented Oct 12, 2018

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

@ebaauw
Copy link
Collaborator

ebaauw commented Oct 12, 2018

They removed this attribute (and some others) from the API in 3a29b43.

I would prefer to have the attribute available stil

Indeed, I don't care for the other attributes, but devicemembership does seem like a real loss (even though I don't currently use it). Maybe we should start a petition to bring it back? ;-)

or is there another way of recognise a group for sensors?

You can get this info from the sensors config.group attributes, but then you'd have to scan all /sensors resources, building a groups map yourself. Alternatively, you can specify Accept: application/vnd.ddel.v1 in the HTTP header (this is what Phoscon and the old web app do), but then you'll get all other "private" attributes as well.

@wvuyk
Copy link
Author

wvuyk commented Oct 12, 2018

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.: type:"SensorGroup"?
And as I do not really use others, could skip the adjusted HTTP header.

@MattL0
Copy link

MattL0 commented Oct 12, 2018

will revert back to 2.05.39, until this is fixed

@manup
Copy link
Member

manup commented Oct 13, 2018

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 devicemembership attribute.

@wvuyk
Copy link
Author

wvuyk commented Oct 18, 2018

With 2.0.5.41 the issue is resolved. Thanks all!

@wvuyk wvuyk closed this as completed Oct 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants