[Release] Samsung Multiroom WiFi Audio

I have a temporary code update and instructions below to correct the source on your installation without re-installing. Instructions:

  • Open the Drivers Code page and open the "Samsung Wifi Speaker"
  • On line, add the updateDataValue code below after line 145. Save the changes.
  • Open your device and complete a Save Preferences.
    • Scrolling down to your device's data section, the input sources should look like the clip at the bottom.
  • On the device's page, run Input Source several times. This should scroll through the input sources of your device. (Note that when going to Bluetooth, it will take some time to transition to the next source. This is normal.)
  • Return to the CODE and delete the line you just added.

Get back to me if this fails or you have other issues.

Dave

New line:

updateDataValue("inputSources", "{1: wifi, 2: bt, 3: aux, 4: optical, 5: coaxial, 6: soundshare}")

1 Like

It works!

Thank you. Your support is outstanding.

2 Likes

Hi,
I have two speakers that are rather old, but they paired well with Smartthings and I can control them with the Samsung Multiroom App.
However, when I try to add to Hubitat using your integration they never get discovered.
My logs keep showing these every 15 seconds:
app:5182020-10-14 19:54:37.923 debugSamsung Speakers Integration 3.3.4: ssdpDiscover
app:5182020-10-14 19:54:22.606 debugSamsung Speakers Integration 3.3.4: ssdpDiscover

My speakers are the following Models:
Samsung R3 WAM3500WWB
Samsund Soundbar J8500 HW-J800WWB

Thank you so much!

The smartApp has to run discovery twice (still have not figured that out - but this is noted at the top of the app page).

  • Install
  • Run App
  • Run Discovery
  • Select Done
  • Run App
  • Run Discovery again.

The speakers have to be on the same lan segment as your Hubitat Server.

Thank you, I tried it but now my log keeps repeating this:
app:5192020-10-14 21:48:44.086 debugSamsung Speakers Integration 3.3.4: verifySpeakers
app:5192020-10-14 21:48:40.042 debugSamsung Speakers Integration 3.3.4: ssdpDiscover
app:5192020-10-14 21:48:29.137 debugSamsung Speakers Integration 3.3.4: verifySpeakers
app:5192020-10-14 21:48:25.057 debugSamsung Speakers Integration 3.3.4: ssdpDiscover
app:5192020-10-14 21:48:13.350 debugSamsung Speakers Integration 3.3.4: verifySpeakers

That is normal. But did it discover anything?

  • Run the App
  • Click the gear Icon in the upper right hand corner.
  • You should see the application state with data (like below). If so, take a screen shot and post or Private Message me.

Curiosity - are you a SmartThings refugee? If so, did you use the integration there?

Yes, refugee, but I didn't use your integration, I just used the official one. Even testing today they get added instantly when I click add device on ST.

On the application state, the speakers state is empty (speakers {}). I don't think you need a screenshot of that.

Try this:

  1. Uninstall the app.
  2. Reinstall
  3. open a debug window
  4. Run the app. Let run for two minutes.
  5. Press done,
  6. Copy log and paste here.
    Dave
1 Like

LAN Concern. The SmartThings and Hubitat Apps use the same discovery algorithms (I developed both). What is different on the LAN installation location (IP address, etc.) between the two.

WorkAround. I can create a manual installation version of the driver in several hours. But it will NOT have any group functions. Will do this if you are interested.

Dave

Thank you, a manual option would surely work, but only if it doesn't take too much of your time. Integrating these speakers is not that important to me to warrant such a time effort.

1 Like

Hey, you won't believe it.
I decided to randomly try adding the speakers again today and the app discovered them correctly.
No idea why, but it's working now!
Thank you so much for the help once again

Humor. It must be that random error generator I place in the integration to keep me busy.

Reality. Thank you. I am glad you got it to work and sad you had problems.

Dave

1 Like

Just out of curiosity, is there any way to clear the queue? My queue is getting rather large on one of my speakers that I use for TTS

Run Save Preferences. It will reset the queue.

1 Like

Thanks! That worked perfectly. Now I can scroll to the bottom in just a few taps on the wheel... LOL

Update to version 3.3.6:

  • Corrected TTS buffering issues
  • Added isConnected attribute and polling every minute.
    • if not connected, TTS messages will not be buffered
  • Reduced sendSyncCmd timeout to 5 seconds
    • Reduces resource utilization for driver.
1 Like

Has anyone here been able to play a playlist using the Multiroom app and then have TTS pause the playing, speak, and then resume the same playlist that was playing?

When I try any of the TTS commands my playlist is cleared out and doesn't resume playback, it gives some error about being unable to play in the app.

If I can't use the multiroom app's playlist, would be interested if anyone has successfully run their own local radio using https://icecast.org/ or something similar and had that as a preset.

By the way, thank you so much for this driver, we use it every day to keep our kids on schedule, it works great!

I used it just yesterday to play an announcement then resume a station. It is designed to do that, but does not always work (partially depending on station being played).

I have not used icecast. The driver does have a urlPreset that allows playing of station urls. If you can get the url command for an icecast station, then this should work (using add url preset).

Yeah, I believe it probably works well with stations, in my case I'm streaming from my phone's filesystem using the Multiroom App's playlist feature.

1 Like

I guess I should describe my goal, rather than what specifically I've been trying to do to accomplish it.

I'd like to shuffle play a playlist of MP3 files at specific times of day on the speaker. I'm fine if doing so requires some kind of server hosting the files. I can play an individual file, but setting it up to shuffle doesn't seem feasible without some custom scripting.