Sonos WebSocket Edge Driver

[h0ckeysk8er (Bruce Pinsky)]

@bthrock

“Play message on a speaker” isn’t working in routines for me. I’m not sure how this is supposed to be handled, as there is no playText command available in the driver, nor is it listed as a production capability.

Perhaps there’s supposed to be some conversion under the hood?

I created a Routine that successfully played a message on my Sonos Move and Amp devices when I turned on a virtual switch.

[bthrock (Bob)]

@h0ckeysk8er

I created a Routine that successfully played a message on my Sonos Move and Amp devices when I turned on a virtual switch.

Oops, I meant to come back and amend my post. I didn’t notice until later in the day yesterday that all my Sonos devices had gone offline in SmartThings (they were working normally otherwise). I reran the test after getting them back online and it worked.

I’m still very curious to know how they’re executing the TTS command, as there’s nothing I can find to use rules or API commands.

[orangebucket (Graham)]

@bthrock

I’m still very curious to know how they’re executing the TTS command, as there’s nothing I can find to use rules or API commands.

For some highly infuriating reason the Rules that handle notifications, including audio notifications, do not seem to be enabled in the public API even though they are available in Routines and Scenes. You can copy the Rules code from a Scene and it simply isn’t accepted.

There is a whole section of the API involved with TTS. Here is a link to the middle of it (links in the API can be rather eccentric so you often have to settle for something nearby):

API | Developer Documentation | SmartThings

I’d scroll down from where that takes you as I think you’ll find playtext more interesting.

[nayelyz (SmartThings Developer Support)]

@bthrock

With the latest version of this driver, the mediaGroup commands

Hi, @bthrock
I already shared this with the engineering team, I’ll let you know as soon as I have more info.
Thanks for sharing!

[bthrock (Bob)]

@orangebucket

For some highly infuriating reason the Rules that handle notifications, including audio notifications, do not seem to be enabled in the public API

I’m aware and I still don’t understand it. What I wasn’t aware of was that even if you copied the rules code from a scene (something I didn’t know was even possible), that it wouldn’t be accepted.

What’s interesting about playtext in the link that you sent is that it has a volume parameter. That should be at least be an option for the routines, much as it should be available in the Rules API.

I have an alternative way to accomplish these notifications in my Rules, but it would be nicer if it were a native capability.

[AlejandroPadilla (Please contact @nayelyz or @Luis_Humberto_Medina)]

@bthrock

ETA: Also, the driver is still picking up both Left and Right speakers. When they are paired for stereo, the driver should only pick up the Left speakers—as the old DTH did.

Hi @bthrock, I’m Alejandro from the developer support team.

To investigate what is the problem we need your help replicating the issue when the device is paired and to provide the following info:

1. Confirm the mail account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
2. Enable support access to your account:
   • Go to the SmartThings Web (my.smartthings.com)
   • Log in to your Samsung Account
   • Select Menu (⋮) and choose Settings
   • Toggle on Account Data Access
   • Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
3. Provide the Hub logs through the IDE
   • In the IDE enter “my hubs”
   • Enter the corresponding Hub and go to “view utilities”
   • Click on “send” below “send hub logs
4. If you have more than one Hub, the name of the one involved in the issue
5. Device’s name
6. Share the driver’s logs. For this, you need to set up the ST CLI and run the command below
   • Smartthings edge:drivers:logcat

[bthrock (Bob)]

Responded via PM.

[bthrock (Bob)]

@nayelyz

I already shared this with the engineering team, I’ll let you know as soon as I have more info.

Thank you!

This should and hopefully will be a relatively quick fix. I’ve tested this extensively and all the groupMedia capabilities are there, the commands are just swapped around in the driver.

Other things I would appreciate you passing along to the team:

• The “Play a favorite” command (i.e., playPreset in the API) should clear the queue in advance of setting the preset. This is important because currently, if the Favorite requested is a playlist (not a station) and there are tracks already present in the queue, the tracks of the newly requested Favorites are merely added to the existing queue rather than replacing them, as they should. (Having a clearQueue command in the API would be a nice option as well.)
• There needs to be a volume option for “Play message on speaker” in routines, in addition to the current language and voice style options (see image below). Otherwise, notifications may in some instances not be loud enough to be heard.
• Please expose the playText command to the Rules API.
• One thought, although it’s not something I use a lot, it might be nice if the favorites were presented in alphabetical order on the device page.

(As per above, this needs an option to set the notification volume.)

[bthrock (Bob)]

A number of commits were made yesterday to lan device drivers, including Sonos, Bose, and Wemo, that might possibly be related to the speakers frequently going offline in ST, rendering them unresponsive to an ST-driven command from the app or API. These changes will only affect hubs with the 0.46 firmware.

Not clear when the driver itself might receive an update. As yet, the mediaGroup controls are still scrambled and therefore broken, and no action has been taken to add action = "replace" to playPreset (aka “Play Favorite”) code so that the queue is properly cleared for playlist favorites. These latter two issues are two-minute fixes, so hopefully they can be addressed in the next update as well.

[granite]

I’m still on the groovy integration, with the plan to keep everything working until the edge driver is officially released. All my speakers are currently unresponsive in ST

[bthrock (Bob)]

@granite

I’m still on the groovy integration, with the plan to keep everything working until the edge driver is officially released. All my speakers are currently unresponsive in ST

That’s interesting, and seems to further confirm the unresponsive speaker problem is a backend issue with lan devices in general and not exclusive to the Sonos Edge driver. An ST engineer has been in contact with me to investigate, but hasn’t reported any progress yet.

Unfortunately, all the issues noted above have brought another Sonos-related project I’m involved with to a screeching halt, so I’m hoping they’ll be resolved soon.

[Wajo357 (Joey W.)]

My speaker notifications stopped working today. Is that related to this issue? Does smarthings know about this?

[bthrock (Bob)]

Anyone here with multiple pairs of Sonos speakers running the Sonos Edge Driver, I’m curious if you could try something.

1. Create a speaker group consisting of multiple pairs.
2. From the device page for the group coordinator (the first speaker pair in the group), adjust the volume of the group coordinator in the app, and confirm that the volume on that pair actually changes.
3. Next, from the device page for one or more of the auxiliary speaker pairs in the SmartThings app, adjust the volume of an auxiliary speaker pair and check if the volume on that pair changes.

In my experience, I am able to adjust the volume of the group coordinator pair, but not any of the individual auxiliary pairs. I’m in contact with engineering, and just want to be sure some of the things I’m seeing are reproducible by others.

[troy_owens]

I cant keep this deiver online for more than 3 days at a time and nothing ive tried brings it back except for deleting and readding. Is anyone else having a similar experience?

[bthrock (Bob)]

@troy_owens

I cant keep this deiver online for more than 3 days at a time and nothing ive tried brings it back except for deleting and readding. Is anyone else having a similar experience?

Yes, this is one of the issues I’ve discussing with engineering. A hub reboot usually works for me.

[h0ckeysk8er (Bruce Pinsky)]

@bthrock

Anyone here with multiple pairs of Sonos speakers running the Sonos Edge Driver, I’m curious if you could try something.

1. Create a speaker group consisting of multiple pairs.
2. From the device page for the group coordinator (the first speaker pair in the group), adjust the volume of the group coordinator in the app, and confirm that the volume on that pair actually changes.
3. Next, from the device page for one or more of the auxiliary speaker pairs in the SmartThings app, adjust the volume of an auxiliary speaker pair and check if the volume on that pair changes.

In my experience, I am able to adjust the volume of the group coordinator pair, but not any of the individual auxiliary pairs. I’m in contact with engineering, and just want to be sure some of the things I’m seeing are reproducible by others.

I would if I could figure out how to make a speaker group

[bthrock (Bob)]

@h0ckeysk8er

I would if I could figure out how to make a speaker group

Hah! As someone who uses groups constantly, that was unexpected.

In the Sonos app, selected system (the middle button at the bottom), select a speaker, then use the little magic button on the bottom left.

[h0ckeysk8er (Bruce Pinsky)]

@bthrock

@h0ckeysk8er

I would if I could figure out how to make a speaker group

Hah! As someone who uses groups constantly, that was unexpected.

In the app, selected system (the middle button at the bottom), select a speaker, then use the little magic button on the bottom left.

Oh, you mean in the Sonos app, not ST app

[bthrock (Bob)]

A few updates on the Sonos Edge Beta driver:

• My Pull Request to correct the mediaGroup command scramble mentioned in my post above was approved and merged into the main branch today.

• A second pull request of mine to make replace the default when playlists Favorites are loaded (thereby replacing the queue instead of appending to it, as originally noted here), was closed by ST as they favored expanding the preference to include all four options: Replace, Append, Insert, and InsertNext. Their revised PR was also approved and merged into the main branch today.

• A request to add the playModes preferences (shuffle, crossfade, repeat, repeatOne) has been tabled for now and will be considered after other issues with the Sonos integration are resolved.

• The ST engineer who assisted me with the above is experiencing the same speaker disconnects that have been reported here and elsewhere. He is in contact with other ST staff in an effort to get this resolved.

A new driver incorporating the changes that were approved should be available soon.

[bthrock (Bob)]

@h0ckeysk8er

Oh, you mean in the Sonos app, not ST app

That what I said (after an edit).

Be curious to know your results.