[KNOWN_ISSUE] Entities for custom capabilities (soundmode,nightmode, etc.) not working (Setup is failing) #43
Labels
bug
Something isn't working
enhancement
New feature or request
not fixable (external)
The issue is currently not fixable because of an external dependency.
Entities for custom capabilities (soundmode,nightmode, etc.) not working
Note
This is an issue related to a known problem with the current implementation of the SmartThings API. It is not fixable at this moment due to Samsung removing the option to retrieve the status of the "execute" API endpoints (which fetched data through OCF).
Extended thread: #26
Description
As of March 26, 2024, the status of the custom capabilities (advancedaudio, eq, 🔗 etc.) can no longer be retrieved. Samsung removed this functionality due to "security reasons" (see 🔗 here).
Because of this change, the state entities can’t be updated anymore.
Current state
What's still working is setting the properties of these custom capabilities. Therefore, in version
0.4.0
, this integration released service calls for each of the attributes that can be changed.Sadly, since we can't see the status anymore, it’s even less likely to find more setting keys to configure.
Caution
I do not recommend enabling the entities for the custom capabilities in the settings. In a later version, I will probably remove this functionality completely, as I cannot guarantee the status of an entity. Please refer to the already mentioned service calls to set a specific attribute.
There are now service calls for:
select_soundmode
set_woofer_level
set_night_mode
set_bass_enhancer
set_voice_enhancer
set_speaker_level
set_rear_speaker_mode
set_active_voice_amplifier
set_space_fit_sound
The future
I hope that in the future, Samsung either re-enables this functionality or that we can find another way to retrieve those values. It’s still possible since the SmartThings app continues to access them. It would be awesome to have a local OCF-based API client for the soundbar, but since I haven't found any documentation on this matter, it's unlikely we'll stumble upon a solution anytime soon.
If you have any questions, just hit me up, and I’ll try to help you out!
Thanks a lot for using this integration ✨.
The text was updated successfully, but these errors were encountered: