Samsung TV integration unstable

MaximeNagel commented 5 months ago

The problem

I'm referencing an old issue as it seems to be relevant : https://github.com/home-assistant/core/issues/35629

When my Samsung is On, the state of the entity keep switching on-off making impossible the use of this state in automation.

It was working fine until 2 weeks now I think.

What version of Home Assistant Core has the issue?

core-2024.1.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

SamsungTV

Link to integration documentation on our website

https://www.home-assistant.io/integrations/samsungtv/

Diagnostics information

config_entry-samsungtv-9588ad25e8b5e9db3a99e627b6aa6751.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 5 months ago

Hey there @chemelli74, @epenet, mind taking a look at this issue as it has been labeled with an integration (samsungtv) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `samsungtv` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign samsungtv` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

samsungtv documentation samsungtv source _{^{(message by IssueLinks)}}

LukasMendez commented 5 months ago

I'm having the exact same issue. I think it happened after the last update

epenet commented 5 months ago

Hi, please add the following to configuration.yaml , restart HA, and post the log:

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.

And add diagnostics (menu configuration -> integration -> samsung tv -> download diagnostics )

MaximeNagel commented 5 months ago

Hi, please add the following to configuration.yaml , restart HA, and post the log:
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.

And add diagnostics (menu configuration -> integration -> samsung tv -> download diagnostics )

Configuration is updated, and I have activated again the samsungtv integration. I have already try to run the TV for 30 minutes and it seems to be stable as for now.

I will keep an eye open tonight when watching TV.

Update :

After 3 hours with TV on tonight it seems to still be stable. Maybe it was just a fluke, but it happend during multiple day and I was not the only one it seems because other user report the same "bug" in the Old issue

edzards commented 5 months ago

I am facing exactly the same issue.

epenet commented 5 months ago

I am facing exactly the same issue.

Please read the above, update your configuration, and post logs. Without logs, there is nothing anyone can do.

MaximeNagel commented 5 months ago

Everything seems to have returned to normal on my end; I haven't been able to reproduce the incident since my last message.

pr0qye commented 4 months ago

I am experiencing this issue. I have logged it and attached it here. Hope that helps.

error_log.txt

chemelli74 commented 4 months ago

error_log.txt

2024-03-05 14:53:37.517 DEBUG (MainThread) [homeassistant.components.samsungtv] Failed to get remote for 192.168.1.118: TimeoutError()
2024-03-05 14:53:42.515 DEBUG (MainThread) [homeassistant.components.samsungtv] Checking if TV 192.168.1.118 is on using websocket
2024-03-05 14:53:42.516 DEBUG (MainThread) [homeassistant.components.samsungtv] Create SamsungTVWSBridge for 192.168.1.118

Seems you have a network issue, on the device itself or in the infrastructure.

Valappi commented 4 months ago

I have the exact same issue here. The last update changed/affected something.

It worked flawless prior to that but for some reason this is an issue that keeps showing up in some releases.

I also get

2024-03-05 14:53:37.517 DEBUG (MainThread) [homeassistant.components.samsungtv] Failed to get remote for 192.168.1.118: TimeoutError() 2024-03-05 14:53:42.515 DEBUG (MainThread) [homeassistant.components.samsungtv] Checking if TV 192.168.1.118 is on using websocket 2024-03-05 14:53:42.516 DEBUG (MainThread) [homeassistant.components.samsungtv] Create SamsungTVWSBridge for 192.168.1.118

Granted I didn't check the logs when it was working but still, there are a handful of users here with the same issues (tv reported turning on and off).

Is there any way to revert back to the old, previous version without restoring the HA backup? Restoring the backup will set me back on so many other things sadly.

Valappi commented 4 months ago

And now I'm back in working order again. Applied a HA core update the other day, don't know if that has anything to do with it but still working.

Should "Failed to get remote" be logged when the TV is off if everything is working? Because I still get those entrys in the debug log.

Failed to get remote for 192.168.1.118: TimeoutError() 2024-03-05 14:53:42.515 DEBUG (MainThread) [homeassistant.components.samsungtv]

vfmunhoz commented 2 months ago

The same issue is happening here and before finding this thread i used to restart HA to get the integration stable again. Setting the logs to debug when the problem happens won't work because with the restart everything gets back to normal.

epenet commented 2 months ago

I think you should not need to restart everything to enable logging. If you simply enable logging on the https://my.hass/config/integrations/integration/samsungtv page, leave it running a few minutes, and disable again it should give you a log file.

maalgorium commented 1 month ago

Also having the same problem. Log attached. The TV was on the entire time.

samsungdebuglog.txt

home-assistant / core