New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't power off Samsung Home Theater #87472
Comments
Hey there @chemelli74, @epenet, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) samsungtv documentation |
By the way, it would be completely acceptable for me to have a way to specify a custom |
Actually all that is needed for this is for the Samsung TV integration to support a platform: samsungtv.turn_off
entity_id: media_player.my_home_theater |
Using: I already tried I confirmed that the remote entity is working, because |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Still applicable. |
@MartinHjelmare are you still against #91903? |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Still valid. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Still an issue. |
Hi @felipecrs, I'm using the following code for my TV and it works jsut fine: service: media_player.turn_off
target:
entity_id:
- media_player.samsung_tv_q85_series_55 But rechecking your post, seems that you are using a custom integration. |
No, I'm not using any custom integration. And the turn off service doesn't work either (for such device). I also have a newer Samsung TV (Tizen), for which the turn off service works just fine. |
where is the yaml "
Please add the following to logger:
default: warning
logs:
homeassistant.components.samsungtv: debug
samsungtvws: debug
samsungctl: debug Note: it is better to drag the log into the comment (which will add it as an attachment) and not copy paste as it is hard to read logs in GitHub. |
lol that's from early 2023, when this integration did not have UI configurator. The issue remains to this date however, using latest Home Assistant. I disabled all other Samsung devices and automations to ensure logs come clean. Then, after starting HA, I tried set the volume of the device to ensure it's properly connected, volume increase worked. Then I invoked the turn off service for such device, for which nothing happened in the device. service: media_player.turn_off
target:
entity_id: media_player.home_theater_do_escritorio Then waited a few seconds and stopped the logs. Here is the device diagnostics too: config_entry-samsungtv-daffe7066b9cd2fde69b664fdcc51141.json |
I see 2 devices on your log, both with issues:
|
I guess the integration continues to poll the devices even when they are disabled. Anyway, you can disregard 192.168.1.18. It probably failed because it was plugged off. The issue I'm reporting is for 192.168.1.17. |
The problem
I have a Samsung Home Theater HT-F5505K. The Samsung TV integration is able to control, except that the power off function doesn't work.
I can control the volume for example, normally. But when I click in the power off button, nothing happens on my device.
What version of Home Assistant Core has the issue?
2023.2.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Samsung Smart TV
Link to integration documentation on our website
https://www.home-assistant.io/integrations/samsungtv/
Diagnostics information
config_entry-samsungtv-daffe7066b9cd2fde69b664fdcc51141.json.txt
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: