How to change the sound mode on a samsung soundbar : Solution

I added control of Night mode, Bass boost and Voice amplifier


1 Like

This is excellent thank you! I previoulsy spent hours (months) trying to get it to work with the HTTP GET API.

just one thing this link on the repo sends you to the orginal GIT not your fork, that gave me a headache for a little while


To install this integration manually you have to download and extract its contents to config/custom_components/smartthings_soundbar directory:

Confirmed working with the Q900A

thank you for your remark I modified the link in the

I improved and simplified the creation of a soundbar device. Now creating a new device, will automatically create a media player and 3 switches
The link is post 7

Hi Theirry,

I am very new to HA having switched from ST after my hub died. I found your fork when looking for a way to control my HW-S60T sound bar

I have added the repo through HACS and downloaded it.

When I try yo add the integration I get the message about adding the device manually

I have tried adding the code in the readme to my config.yaml using the token I created and the device ID I found on in Advanced Users, but the devices is not appearing after. restart. What might I be doing wrong?


Not posting your logs is wrong :slight_smile:

That’s helpful. As my first ever post here said “i am very new to HA’ so please forgive my ignorance for not being an expert within the first week…

Just post the logs. You ask for help, you get told how we might be able to help.

I hope this explains further. How to help us help you - or How to ask a good question

Ok maybe I missed the humour in your reply. Thanks for the link I will have a read and go in search of the logs.

Just to make sure I hadn’t done something stupid I removed the integration completely and started over. Followed the instructions again with the same result - no device gets created.

I downloaded and searched my logs and the only mention of the integration was:

2023-08-03 21:11:54.392 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration samsung_soundbar which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

However, I noticed the links in the instructions were to the old token and Smartthings backend which have now been deprecated but it appears the API calls are still the same so probably irrelevant

Thanks for the link. I read section 13 on logs and have a question if I may? When it says custom components can only be seen in the logs on disk am I right to assume that means the file you get when clicking “download full log”? These are the ones I am referring to in the post above

The log named /config/home-assistant.log

ok thanks. There is nothing in that file about the integration. I cant seem to attach it and it’s way too big to post as text :-/

I managed to get this version working last night. I am going to try thierry’s one again this evening as would prefer it to appear as a device.

Great addon!
I have a problem with my soundbar where it doesn’t switch over to TV/ARC/HDMI whenever I turn on the TV. Its stuck on chromecast. This isnt a problem with your addon, its a problem in general. To solve it I have to go into the SmartThings app and manualy switch over to TV/ARC.

I was thinking I could create an automation where I switch the soundbar to HDMI whenever the TV turns on. But in your addon I cant seem to get the source list to include HDMI/TV/ARC. Only wifi and bluetooth shows up.

Do you know if its possible to add the rest of the source options.


Great implementation, Thierry! I installed your custom component on Saturday. It really helps to get rid of a few annoying repeating tasks. However, at this point things seem to break too easily and I need help with it.

This morning I noticed on/off state of Q990B wasn’t updated after Saturday according to Home Assistant. Restarting HA Core helped to fix the status but I don’t understand the reason for the connection loss. In the Smartthings webpage(where Device ID was fetched), the status was correct before restart. I disabled Smartthings(official?) integration if it causes trouble with it even if the API key was different for it.

One of the goals was to automate sound mode switching to standard when I play music. I use Spotify on Android and I choose playback device in Spotify to be the soundbar(wifi). However, the source is empty in the Developer tools but the earlier referred Smartthings webpage shows it as wifi. If I switch the soundbar to wifi in Smarrthings app on Android(without connection to any device), the developer tools shows it as wifi.

I tried to install this addon manually per the instruction, as my HA is on docker. After installation, the addon respond that it can’t be added in UI mode and should be configured in yaml. I added the code below in the configuration.yaml but the same error message is produced. Any idea?

  - platform: smartthings_soundbar
    name: Soundbar
    api_key: "YOUR API KEY"
    device_id: "YOUR DEVICE ID"

There is no addon in this thread. There are at least 2 custom integrations. Which one did you install?

Also did you restart HA after adding the yaml?

What do your logs say?

grep smartthings_soundbar /config/home-assistant.log

Exellent alternative your integration, i want to ask you 2 things.

1st if you can add the ability to change the source for example from an automation. I want to have multiroom on my house and if i press a button i want to change the soundbar from digital to another source for Google TV HDMI and if i turn off the button again go to digital ready for tv. Or something like your switches. So if i want to do that i will on/off the right switch. It will be sooo nice!

2nd If you can give unigue ID in Samsung Soundbar you will be a God on this. If we have unigue ID we’ll have the ability to “pick a media” and at our soundbar on our Voice Assistants and TTS. It will the the best thing!

Hey ijhammo, how did you finally get the integration working? I am struggling with the same issues you had back then.