Currently, the Sons device has type urn:schemas-micasaverde-com:device:avmisc:1. And the device type is not present in the JSON file.
Why not using a specific type + a JSON file clearly attached to this type ?
The problem is that we cannot have different A/V devices of this type with different UI (JSON).
SqueezeBox plugin has defined its type for example. I think we should do the same.
It seemed like the most logical choice at the time. The Control points used to (and some still do) use the Device Type information to provide a UI, Icon (etc) and/or to make a choice about potential control actions.
Technically that’s wrong, since they should be looking at the ServiceID’s that are implemented, but none-the-less, a number of them used to do that (and some still might)
Why not using a specific type + a JSON file clearly attached to this type ?The problem is that we cannot have different A/V devices of this type with different UI (JSON).
Fix that, and the original problem goes away.
Ultimately, it’s not really a new Device Type, but a work-around to an antique MCV Bug 8)
I use the device type in my application because it is hard to tell how to display the device interface in my app by just going through the control types. By using the device type, I can use the correct layout for the device.
[quote=“garrettwp, post:3, topic:177238”]I use the device type in my application because it is hard to tell how to display the device interface in my app by just going through the control types. By using the device type, I can use the correct layout for the device.
SqueezeBox has its own device type. When I create a plugin for XBMC, I am forced to create a new device type and not use the same as for Sonos.
If we don’t use different type, that means we cannot have different A/V physical device types managed by the Vera.
We could decide that Sonos is THE default A/V device for Vera but it males no real sense for users without a Sonos but with a SqueezeBox. That being said, I think each device controled by a specific plugin should have its own device type … due to Vera limits that we have to bypass.
[quote=“garrettwp, post:3, topic:177238”]I use the device type in my application because it is hard to tell how to display the device interface in my app by just going through the control types. By using the device type, I can use the correct layout for the device.
Garrett, I forgot to tell you but I discovered that in AutHomationHD, prev and next buttons for Sonos are inverted.
What was implemented:
MediaNavigation1/SkipDown => AVTransport/Next
MediaNavigation1/SkipUp => AVTransport/Previous
It would not be my logical choice but we had a discussion in the past and conclude it could make sense to do it like that.
Do you know if there is a standard defining SkipDown and SkipUp ?
Is SqueezeBox plugin doing it in the reverse order ?
[quote=“lolodomo, post:5, topic:177238”][quote=“garrettwp, post:3, topic:177238”]I use the device type in my application because it is hard to tell how to display the device interface in my app by just going through the control types. By using the device type, I can use the correct layout for the device.
Garrett, I forgot to tell you but I discovered that in AutHomationHD, prev and next buttons for Sonos are inverted.
What was implemented:
MediaNavigation1/SkipDown => AVTransport/Next
MediaNavigation1/SkipUp => AVTransport/Previous
It would not be my logical choice but we had a discussion in the past and conclude it could make sense to do it like that.
Do you know if there is a standard defining SkipDown and SkipUp ?
Is SqueezeBox plugin doing it in the reverse order ?[/quote]
Not understanding the issue SkipDown should be pointed to Previous and SkipUp should be pointed to Next. That is how I interpret it.
[quote=“garrettwp, post:6, topic:177238”][quote=“lolodomo, post:5, topic:177238”][quote=“garrettwp, post:3, topic:177238”]I use the device type in my application because it is hard to tell how to display the device interface in my app by just going through the control types. By using the device type, I can use the correct layout for the device.
Garrett, I forgot to tell you but I discovered that in AutHomationHD, prev and next buttons for Sonos are inverted.
What was implemented:
MediaNavigation1/SkipDown => AVTransport/Next
MediaNavigation1/SkipUp => AVTransport/Previous
It would not be my logical choice but we had a discussion in the past and conclude it could make sense to do it like that.
Do you know if there is a standard defining SkipDown and SkipUp ?
Is SqueezeBox plugin doing it in the reverse order ?[/quote]
Not understanding the issue SkipDown should be pointed to Previous and SkipUp should be pointed to Next. That is how I interpret it.
Here is the discussion we add with @guessed one year ago: http://forum.micasaverde.com/index.php/topic,8505.msg87997.html#msg87997
I can change but it will impact every user using theses 2 actions.
What do you think about using Previous and Next actions from the AVTransport service ?
[quote=“lolodomo, post:7, topic:177238”][quote=“garrettwp, post:6, topic:177238”][quote=“lolodomo, post:5, topic:177238”][quote=“garrettwp, post:3, topic:177238”]I use the device type in my application because it is hard to tell how to display the device interface in my app by just going through the control types. By using the device type, I can use the correct layout for the device.
Garrett, I forgot to tell you but I discovered that in AutHomationHD, prev and next buttons for Sonos are inverted.
What was implemented:
MediaNavigation1/SkipDown => AVTransport/Next
MediaNavigation1/SkipUp => AVTransport/Previous
It would not be my logical choice but we had a discussion in the past and conclude it could make sense to do it like that.
Do you know if there is a standard defining SkipDown and SkipUp ?
Is SqueezeBox plugin doing it in the reverse order ?[/quote]
Not understanding the issue SkipDown should be pointed to Previous and SkipUp should be pointed to Next. That is how I interpret it.
Here is the discussion we add with @guessed one year ago: http://forum.micasaverde.com/index.php/topic,8505.msg87997.html#msg87997
I can change but it will impact every user using theses 2 actions.
What do you think about using Previous and Next actions from the AVTransport service ?[/quote]
I’ll make the change in AutHomationHD and also add them to the Squeezebox plugin.
Best Home Automation shopping experience. Shop at Ezlo!
© 2026 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules