Closed cristhianerg closed 7 months ago
Hi there āļø
So first of all, the most important informations for me would be what version of the integration and HomeAssistant you are currently using.
And the "dumb" questions first š , the api_key and device_id in the logs matches the ones you used on postman?
So I just checked my soundbar, and also Postman etc. and currently everything works fine for me. I'll try to help you as much as possible :)
Hey @samuelspagl yes I've checked them and they match, I even can validate it following the URL in logs directrly in my browser...
My HA version is 2024.4.0, it is installed locally in my network on a RPi 4
Maybe it has something to be with not having an installed SSL
For the doubts I added a reverse proxy with SSL and still not working :( but now I got a different error, maybe you can share some light on this @samuelspagl
`2024-04-04 16:02:35.614 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry samsung_soundbar for samsung_soundbar Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 551, in async_setup result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/samsung_soundbar/init.py", line 52, in async_setup_entry await soundbar_device.update() File "/config/custom_components/samsung_soundbar/api_extension/SoundbarDevice.py", line 52, in update await self._update_soundmode() File "/config/custom_components/samsung_soundbar/api_extension/SoundbarDevice.py", line 74, in _update_soundmode payload = await self.get_execute_status() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/samsung_soundbar/api_extension/SoundbarDevice.py", line 390, in get_execute_status return dict["data"]["value"]["payload"]
TypeError: 'NoneType' object is not subscriptable
`
Yeah this error I can work with š
Its the error that drives most of the users of my integration currently crazy, and the thing I can't do something about.
See #26 for the full description.
In short: on the 26th of March something changed on Samsung's side, therefore it is currently not possible to update / retrieve the status of custom capabilities (like soundmode, eq and more). While it is still possible to update the status of these, the retrieval doesn't work.
I released an alpha version of the integration where you can edit the entities created and therefore also stop the update process for these capabilities. Probably tomorrow I will release another alpha version that will include services for the custom capabilities.
I hope that sheds some light :)
Thanks a lot for the quick answer. I'll try that on the beta
Cheers mate
If you are fine with it, I would close your issue. Feel free to reopen it if anything still is unclear :)
Best Samuel
Hey there, while adding a Q990C I'm getting 401 error despite of using a fresh generated token and device ID (I've chek that they work via postman)
Here's a sneak peek of the log (obviously the credentials are replaced)