@guessed: what would be your advice to define a playlist ctrl with two commands “Previous” and “Next” for Sonos (or DLNA).
In the sitemap, of course I define a Switch with a mapping to have my two buttons “Previous” and “Next”.
Then, of course I could define rules to send a HTTP request to trigger a “Previous” or “next” action.
But do I have another option (without any rule) associating my item to the Mios binding using a command transformation like you do for the playing mode ? The problem is that I only want to send a command and I don’t want to attach my item to a Vera state variable.
[quote=“lolodomo, post:1, topic:185652”]@guessed: what would be your advice to define a playlist ctrl with two commands “Previous” and “Next” for Sonos (or DLNA).
In the sitemap, of course I define a Switch with a mapping to have my two buttons “Previous” and “Next”.
Then, of course I could define rules to send a HTTP request to trigger a “Previous” or “next” action.
But do I have another option (without any rule) associating my item to the Mios binding using a command transformation like you do for the playing mode ? The problem is that I only want to send a command and I don’t want to attach my item to a Vera state variable.[/quote]
In order to send the Command to the right Vera Device, the MiOS Binding will [minimally] need:
a) to be bound to the specific Device#,
b) have NO [tt]in:[/tt] parameter present
c) have a [tt]command:[/tt] parameter present
The command mapping would need to have the relevant ServiceId/Action information present, similar to other Actions.
Also, since these are true stateless actions, you’ll want to have the autoupdate=false set in the binding declaration (this prevents the “button” from sticking when pressed)