DeviceProperties.GetZoneAttributes UPnP call: required to get the zone name
— variable ZoneName: ok
— variable Icon: I propose to suppress this variable
I propose to move this call into the 5 minutes loop.
DeviceProperties.GetZoneInfo UPnP call required to get the MAC address
— variable SonosID: ok
I propose to move this call into the 5 minutes loop.
AVTransport.GetTransportInfo UPnP call required
— variable TransportState: ok
— variable TransportStatus: ok
— variable TransportPlaySpeed: ok
AVTransport.GetTransportSettings UPnP call required
— variable CurrentPlayMode: ok
AVTransport.GetCrossfadeMode UPnP call required
— variable CurrentCrossfadeMode: ok
AVTransport.GetCurrentTransportActions UPnP call required
— variable CurrentTransportActions: ok
ContentDirectory.Browse “AI:” UPnP call
— variable AudioInputs: ok
I propose to move this call into the 5 minutes loop.
AVTransport.GetMediaInfo UPnP call required
— variable NumberOfTracks: ok
— variable CurrentMediaDuration: ok
— variable AVTransportURI: ok
— variable AVTransportURIMetaData: ok
— variable NextAVTransportURI: I propose to suppress this variable - seems to be never set
— variable PlaybackStorageMedium: I propose to suppress this variable
— variable CurrentRadio: ok
— variable CurrentService: ok
AVTransport.GetPositionInfo UPnP call required
— variable CurrentTrack: ok
— variable CurrentTrackDuration: ok
— variable CurrentTrackURI: ok
— variable CurrentTrackMetaData.DIDL-Lite: I propose to rename this variable into CurrentTrackMetaData
— variable CurrentStatus: ok
— variable CurrentTitle: ok
— variable CurrentArtist: ok
— variable CurrentAlbum: ok
— variable CurrentDetails: ok
— variable CurrentAlbumArt: ok
— variable RelativeTimePosition: ok
— variable AbsoluteTimePosition: ok
— variable RelativeCounterPosition: ok
— variable AbsoluteCounterPosition: ok
Rendering.GetMute UPnP call required
— variable Mute: ok
Rendering.GetVolume UPnP call required
— variable Volume: ok
ContentDirectory.Browse “SQ:” UPnP call
— variable SavedQueues: ok
I propose to move this call into the 5 minutes loop.
ContentDirectory.Browse “Q:0” UPnP call
— variable Queue: ok
ContentDirectory.Browse “R:0/0” UPnP call
— variable FavoritesRadios: ok
I propose to move this call into the 5 minutes loop.
We could avoid a third of the UPnP calls every 15s. And it will accelerate the save context too.
Please give me your feedback
@lolodomo,
These all seem like reasonable options to suppress and/or reduce the frequency of loading.
My comments on the Metadata for Say is that, since it didn’t meet the full expectations, it wasn’t ready to be introduced. I don’t generally like adding 1/2 of something, and I tend to avoid doing it as we approach getting something ready to release “just in case” it has an impact on a [hopefully] well tested set of code.
In this case, the Metadata options to correctly setup aren’t well documented and we’re doing this all somewhat by trial and error, with the help of a few examples here and there (and some observed/tcpdump’d behavior). Since it didn’t really do what I wanted it to (start playback faster, put the Meta-data labels into the SonosUI) I don’t consider it “baked” enough to introduce to the code just yet.
Oh, and before I forget, can you add/remove/change the Wiki entries for any variables that you add/remove/rename? It’s not a big deal if we don’t have the full doc, but it’ll ensure that when we add it that the variable names remain in sync.
This one is strange. I have a vera 3. Installed Sonos plug in. Has been working fine last few days. I’ve set up scenes to control vol up and down in order to call them through SQ remote app macro. I believe they were working. This morning my volume SCENES stopped working for all Sonos speakers. But I CAN control volume directly from the DEVICE control panels on the Dashboard.
I have rebooted the vera, sonos devices, and my router. I have removed and reinstalled the devices. No change. None of the volume commands seem to work through senes but the buttons do work through the device panels.
Is anyone else experienced this problem and can you offer any suggestions? I’m at a loss.
OK, started working just a little while ago. I changed nothing. Have no idea why discrete sonos volume commands stopped working temporarily? All is well now.
New feature committed: device icon depending on the Sonos model.
It should already work for Connect and Connect:Amp.
[size=18pt]Please note that the png files have to be transferred manually (using WinSCP for example) in the directory /www/cmh/skins/default/icons[/size]
I’ve finally had a go at updating again and noticed an interesting difference between two of my Sonos Device -
Please see the screen shots below… Both are playing tracks from a queue, where the files are stored on a NAS…
Both are short names, yet ‘Changes’ has been expanded fully…
UPDATE - I’ve worked it out now - the Queue field size has been enlarged to the fit the longest track name in the queue (that’s why !) - Sorry…
Page 10 said that you can only play a specific mp3 file when creating a Scene. Is this still the case? I would love to assign a Sonos Playlist (or a radio station) to a scene.
Would be really nice with a PlayURIVolume that also sets a volume temporarily while playing a sound. Like Say does.
Really messy to play something (like my doorbell) and restore cotext afterwards… also … .People tends to push the doorbell several times quickly which messes up restore context for me sometimes…
[quote=“pixelstore, post:790, topic:169644”]Really great plugin! Thanks a lot!
Page 10 said that you can only play a specific mp3 file when creating a Scene. Is this still the case? I would love to assign a Sonos Playlist (or a radio station) to a scene.[/quote]
Of course, you can now play a Sonos playlist or a radio station.
[quote=“hek, post:791, topic:169644”]Would be really nice with a PlayURIVolume that also sets a volume temporarily while playing a sound. Like Say does.
Really messy to play something (like my doorbell) and restore cotext afterwards… also … .People tends to push the doorbell several times quickly which messes up restore context for me sometimes…[/quote]
I can add a Volume parameter to PlayURI to avoid a PlayURI + a SetVolume calls in scene. It is something that I would use too.
But I am not sure it will really help in your case. Isn’t your problem relative to the (bad) way you are managing your playback context and its restore ?
I’ve only had time to use the “Advance” tab of scene to play and restore context after X seconds. If scene is triggered multiple time (before another scene is finished) it will save the doorbell scene context…
Like the attached image. Do you have any easier way to archive this? If we created a playcomand that saves contect and accept a volume parameter it would simplify things.
[quote=“hek, post:794, topic:169644”]I’ve only had time to use the “Advance” tab of scene to play and restore context after X seconds. If scene is triggered multiple time (before another scene is finished) it will save the doorbell scene context…
Like the attached image. Do you have any easier way to archive this? If we created a playcomand that saves contect and accept a volume parameter it would simplify things.[/quote]
It will not help with concurrent scenes.
I have already managed this for the Say command but I simply reject a Say command arriving when one is playing.
If you have a clear idea how to manage playback contexts for concurrent calls, please explain your idea.
I think we have too little control to manage concurrency in a good manner. Rejecting concurrent calls is good enough for me.
But we should probably not touch the current PlayURI to be backward compatible. The new play command could act just as Say rejecting incoming stuff while playing and accept a volume parameter. It should also probably only allow x-file-cifs (as a radio channel has no end…).
I picked up 3 Sonos Play:5 on sale over the holidays and got the first one set-up last night. Everything is working great.
A question on updating: As changes are incorporated into the plugin files, is it better to upload the new files via the Web GUI following the same procedure as the initial install? Or should I use WinSCP to go in and replace the appropriate files with the newest version?
[quote=“jduchon, post:799, topic:169644”]Santa Claus brought me a second Sonos unit 8)
But, how do you install the second plug-in device on the Vera?
Sorry if it is a stupid question…[/quote]
