Hi all,
My Sonos devices sometimes don’t work anymore. I noticed this happens after an update of the app. Finally I’ve found out that the update sets the app ‘off’.
Is there a trick to put the app automatically ’on’ after an update?
I couldn’t find any appropriate properties.
I have the same issues. I checked if TTS is working on Sonos via Homeassistant and there it is working. I love the Homey Pro, but for some services it is far away from being reliable!
Tried again, changed nothing but it’s working again 
If you didn’t change anything manually, perhaps the IP address of the Sonos changed for your router if you don’t have a static IP set? I’ve heard some people say that Homeys discover of those sorts of changes can be a bit slow.
Might be worth looking into 
I use static IP for all my crucial networkcomponents (components connected to my homey)
I’ve found the issue. My mistake. After leaving of the last person, the app was set to off. I thought it ment Stop (the Stop command as such doesn’t exist). Now I just Pause it.
Here as well. Detection if sonos speaker is playing does not work, killing some of my flows.
Did you find a solution?
Not sure if is possible or not. I only use my sonos for TTS announcments and playing sounds with sounboard.
Is there anyway of changing the voice used on the sonos?
Thanks
Does anyone know whether the Sonos app for Homey controls Sonos devices via the cloud and/or via the local API of Sonos devices?
I assumed the local API would be used, however a recent service unavailability of one of the Sonos cloud service components caused issues in controlling Sonos devices via Homey (like the ERROR_RESOURCE_GONE errors).
Does this mean Homey controls Sonos devices via the cloud and not through the local API? If so, why is the local API not used?
Would it be possible to start sonos with tunein station? If so, how?
Thanks, works!
I am just sharing this info for the benefit of those of you using the Sonos Album, Track and Artist tags in your flows and are trying to understand which information populates these tags.
I found out that since app update v6.6.5 the information included in those tags may sometimes be counter intuitive.
So what is the situation. My expectation regarding these tags is:
- The Track tag always contains the name of the playing track, regardless of whether the source of the track is the local music library (e.g. a local MP3 or FLAC file) or a track being streamed from an online service (like Sonos Radio or TuneIn). If nothing is playing, this tag should be empty.
- The Artist tag always contains the name of the artist of the currently playing track. Regardless of the track’s source. If nothing is playing, this tag should be empty.
- The Album tag contains:
- The album name, if available. Regardless of the track’s source (local or online);
- The radio station name, when playing a tack from a radio service (like Sonos Radio or TuneIn);
- Nothing if the album or radio station name is unavailable.
However, the actual implementation is different as I have summarized in the following image:
Both the Artist and Album tags are being used for multiple purposes. Which might yield unexpected results when automating based on these tags. The Artist tag can both contain the name of the artist and the name of the radio station. The Track tag can contain both the track name, a combination of artist and track names, and the radio station name. Also, none of these tags are emptied when playback stops.
I reached out to Athom for a clarification. They indicated that this behavior is not something they designed as such, but is the (current) behavior of the Sonos API that provides the tag information in the said manner.
So you might want to consider this behavior when automating based on these tags.
I would like to add, that the playing position of a Spotify song is incorrect in the Sonos app, when you switch manually to the next song during the current song: no reset of the position to 0, but keeps counting based on the previous song.
