New Official Integration: Samsung Multiroom Audio

Man I hate that your having issues and understand how frustrating it is. Don’t even get me started on ”presence”. You’re right, it shouldn’t be this hard.

You did answer one of my questions and that is; if you used a Multiroom hub with your setup. I do as well so that is consistent with each of us.

Hi, @Robbie.bushell
Sorry for the delay, this is something the team was working on, here’s the PR about that: https://github.com/SmartThingsCommunity/SmartThingsEdgeDrivers/pull/602

It was recently merged, so, the update might arrive next week, I don’t know the exact date.
In the email you sent you’re only reporting the TTS, what about the issue you mentioned here?

1 Like

@nayelyz The speaker stability problems are a MultiRoom issue, the wireless connectivity and the app have always been a little hit and miss. As @Ptbradford’s set up was working I thought that relocating the MR hub and repeater would help my cause, but it just created another headache!
I thought that it was something my end so I was trying everything I could think of.
Hopefully the update will fix it up and I can return to a life not stressing about daft notifications!

If you’re referring to the speakers ungrouping themselves occassionaly here is a web request (credit to @Gutheinz), sent daily and the speakers haven’t ungrouped in years.

mainSpkIp
groupName
mainSpkMacAddr
mainSpkName
slaveOneIp
slaveOneMac
slaveTwoIp
SlaveTwoMac

http://mainSpkIp:55001/UIC?cmd=<pwron>on</pwron><name>SetMultispkGroup</name><p type= "cdata" name= "name" val= "empty"><![CDATA[groupName]]></p><p type= "dec" name= "index" val= "1"/><p type= "str" name= "type" val= "main"/><p type= "dec" name= "spknum" val= "3"/><p type= "str" name= "audiosourcemacaddr" val= "mainSpkMacAddr"/><p type= "cdata" name= "audiosourcename" val= "empty"><![CDATA[mainSpkName]]></p><p type= "str" name= "audiosourcetype" val= "speaker"/><p type= "str" name= "subspkip" val= "slaveOneIp"/><p type= "str" name= "subspkmacaddr" val= "slaveOneMac"/><p type= "str" name= "subspkip" val= "slaveTwoIp"/><p type= "str" name= "subspkmacaddr" val= "slaveTwoMac"/>

Also
Mute; “/UIC?cmd=%3Cname%3ESetMute%3C/name%3E%3Cp%20type=%22str%22%20name=%22mute%22%20val=%22on%22/%3E”

UnMute: “/UIC?cmd=%3Cname%3ESetMute%3C/name%3E%3Cp%20type=%22str%22%20name=%22mute%22%20val=%22off%22/%3E”

1 Like

Hi, everyone.

There are new changes for the Samsung Audio driver, could someone help us confirm if the following was successful, please?

  1. Improvement of play and volume commands. PR: Play and Volume Delay Fix by satyajitanand · Pull Request #562 · SmartThingsCommunity/SmartThingsEdgeDrivers · GitHub
  2. Implementation of audioNotifications (Text To Speech). PR: Implement Audio Notification Capability by satyajitanand · Pull Request #602 · SmartThingsCommunity/SmartThingsEdgeDrivers · GitHub
2 Likes

hi @nayelyz

its working for me

tts is working too
thanks
martin

1 Like

Hi @nayelyz,

Yes it all is working well. I have my notifications back which makes me happy. Thank you.

1 Like

Thank you for your comments, @montyfert, @Robbie.bushell
We really appreciate your patience and help to check the functionality of this driver.

1 Like

Continuing this conversation, I was just using the scan for nearby devices to add a device, unrelated to my speakers (which have worked flawlessly) and it found six generically named speakers “Samsung Wireless Audio”. My properly named speakers are still in the system and still working fine. It’s that it still is doubling up by finding the actual names and the generic names. As like before, I just deleted them, but this is still an outstanding issue.

Hello,

Recently i have all my R1 speaker not working(previously working with SamsungAudio driver) for TTS. I deleted R1 speaker from Smartthings app, now non of my R1 speaker show up.

Yep, same here. It’s been stable and working great then it quit. I did a device scan and it found a speaker that it already had previously found and named it “Samsung Wireless Audio”. I changed the name to “Samsung Wireless Audio added” because I had no idea which one of my 8 speakers it was. Still had no control of any speakers. Just this morning I jumped into the Multiroom app and my Upstairs speaker had been renamed to “Samsung Wireless Audio added“. Somehow, Smartthings has renamed my speaker.

Looks to be some software update to smartthings caused it. Are we going to get the TTS functionality back?

Any updates. I still cannot add my R1 speakers. Or detected by app. I made sure upnp is enabled in my hub.

Hi, @sgugloth, @Ptbradford
Did you report your issues to Customer Support?

What is the remaining issue, you still cannot add the devices or only the TTS functionality?

Yes, I have created ticket with Samsung 1493935.

It initially quit on TTS automation. Part of debugging I restart speakers, and then deleted.

Now, during scan I do not see speakers. I am using Samsung EV-WV520.

I looked this up and this is the model of the Hub, which is a Wi-Fi one, are you able to run other drivers on it?

Also, can you provide the model of your speakers, please? In the Edge driver there’s a list of those supported:

Yes, I am able to run other edge on the router. Speaker versions I have are wam1500 and wam3500

No, I have not, I’ve been traveling and haven’t really been able to troubleshoot it any further. I will try to do that on Friday.

Ok, I ask because in the ticket you shared it was mentioned that the model you were using wasn’t supported but those models are included in the list. So, please send the following information to open a report on this issue:

  1. Confirm the email 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:
  1. Go to the SmartThings Web (my.smartthings.com)
  2. Log in to your Samsung Account
  3. Select Menu (⋮) and choose Settings
  4. Toggle on Account Data Access
  5. 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.
  1. Try to discover the devices again but enable the driver logs first to see what’s going on during this process.

Thank you for your response. I have performed above actions and logs are sent.