It is a subject probably for @guessed ![]()
Why are we using service id urn:micasaverde-com:serviceId:Sonos1 for actions and service id urn:sonos-com:serviceId:Sonos1 for variables ?
It is a subject probably for @guessed ![]()
Why are we using service id urn:micasaverde-com:serviceId:Sonos1 for actions and service id urn:sonos-com:serviceId:Sonos1 for variables ?
[quote=“lolodomo”]It is a subject probably for @guessed ![]()
Why are we using service id urn:micasaverde-com:serviceId:Sonos1 for actions and service id urn:sonos-com:serviceId:Sonos1 for variables ?[/quote]
See comments here:
http://forum.micasaverde.com/index.php/topic,12860.msg97560.html#msg97560
So it would be an historical mistake ![]()
Variables using urn:sonos-com:serviceId:Sonos1 services id are probably not used by users, or only by few expert users for very advanced usage, while actions are sued by all users.
So we could switch service id for variables to urn:micasaverde-com:serviceId:Sonos1
Here are the 6 concerned variables:
CurrentService
SonosServicesKeys
SonosDevices
SonosOnline
SonosModelName
SonosModel
The last 3 variables have been introduced by me very recently, so I imagine noone is using them.
SonosServicesKeys and SonosDevices are internal variables for the plugin. They are certainly not used by anyone.
The only variable that may have been used by users would be CurrentService.
So, if anyone disagrees, I will do this change ![]()
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules