Closed pandabear41 closed 3 years ago
Hey there @escoand, mind taking a look at this issue as its been labeled with an integration (samsungtv
) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)
I've solved it unconfiguring the Samsung Integration in HA, and re-configuring it, by adding the TV again (if not autodiscovered). It asked me for a confirmation on the TV once and stopped repeating the same authorization message.
I've solved it unconfiguring the Samsung Integration in HA, and re-configuring it, by adding the TV again (if not autodiscovered). It asked me for a confirmation on the TV once and stopped repeating the same authorization message.
How exactly do you unconfigure the integration and re-configure it? Do you clean up everything from DB? I remove yaml and delete integration using three-dot icon -> Delete on integration list page. Followed by a restart of HA (sometimes twice restart if everything isn't removed). Then add yaml it back in and press allow on TV. It fixes it for about a day until spamming me with re-auth prompts on TV again.
I'm seeing the same issue with my Samsung TV. I have connected Home Assistant to the TV manually in the GUI, but using hostname. After about a week, Home Assistant will start to request permission every few seconds regardless of how fast I press accept. I too can fix it by removing the integration, restarting Home Assistant and adding it again, but after some days (usually a week's time) it will happen again. I have noticed, that it seems to always be preceeded by "Smart Device" requesting permission.
I am having the same issue, but the difference for me is that it has been working fine for the last month or so and has only started happening today.
Same issue here since I updated to 0.116.2
same here, it's driving me insane!
Sorry guys, my private life is quite demanding at the moment. I wont have the time in the near future for long debugging and coding sessions. I could maybe review some code or give comments, but don't expect more.
So I would encourage everybody to look deeper into the code and try to find the fix. I was at the same point some time ago. There was a some kind of working samsungtv integration and I started to hack it.
No worries man, thanks for what you've done!
As a fix, for me it helped to remove the integration via UI and set it up through configuration.yaml. no more prompts!
HA notified me now for some time that I should configure my Samsung TV Integration. Ignoring that I already had it configured and still working. When I gave in to the configuration dialog I ended up in this Authorization loop.
From what I see I now have two entities representing the same TV. And they seem to take turns in which one is talking to the actual TV.
All their states (like On/Off, Muted) are changing independently. I have no knowledge on how the Samsung Protocol is working. To me it seems like there is some kind of auth mechanism involved that is leads to invalidate the others entities credentials triggering the Pop-Up on the TV over and over.
From that I'm wondering: why is the TV discovered again when it is already set-up and working? (That would also explain why it is not an issue when it is configured via the config).
It's exactly that, if you don't reconfigure it and just reboot HA it goes away, if you reconfigure then you have a second entity and they just start bouncing.
Linked to https://github.com/home-assistant/core/pull/35773 I think.
The author is no longer able to maintain the code.
I'm seeing lots of
2021-01-20 12:45:34 DEBUG (SyncWorker_3) [homeassistant.components.samsungtv] Create SamsungTVWS
Just to add, I am interested in this, as I have the same problem which I listed in 45509.
This is normally caused by a changing IP address and should be fixed with: #48022
The problem
I am connecting to a Samsung Smart TV for a while using HA. It works for 12-24 hours and then stops working. The TV keeps showing up with the allow/deny HomeAssistant access to the TV. I press accept every time, but it just pops up again after a few seconds. I had this same issue in 0.114 and 0.115. Versions 0.113 and before that worked fine with no issues at all. The only way to fix is remove integration from HA, restart HA twice, add the TV integration again, restart HA, and then press allow on TV.
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
HA Logs: (Not sure why it gets a new token and then doesn't use it, but might be part of the problem or unrelated)
Listening to socket from TV: (You see clientConnect when I press the accept button, otherwise you see clientDisconnect repeated every few seconds)
TV information (2017 4k TV. Model:UN55MU650D):
Additional information
Might be related to https://stackoverflow.com/questions/61137232/websockets-closing-unexpectedly as I can curl the API of the TV, but a simple python code using websockets doesn't work.
Running samsung-tv-ws-api using their sample code also works. Also use the Samsung Smart TV remote app and don't have any issues.
I can monitor and provide wireshark if needed.