-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[SamsungTV] Binding does not recover from communication error (Legacy Mode) #7055
Comments
There is some fundamental issues with the SamsungTV binding and jUpNp right now. Best, Jay |
I have the same problem with legacy protocol. Binding restart, TV initially offline:
Polling job working after this:
TV turned on:
TV turned off:
After this no more polling and nothing happens. When TV is turned on again, this is not detected. I briefly looked at the code, but found it hard to understand at first sight. However, this "shutdown" message made me curious, so tried to track it. shutdown() stops all services (including event listeners), and it's called from dispose(), which seems appropriate, but also remoteDeviceRemoved. So tracked what starts services: initialize(), which seems appropriate, and also remoteDeviceAdded. I'm not sure if this is fully needed or just some kind of reinitialization. I tried to remove the shutdown() call from remoteDeviceRemoved to see what happens, and this resulted in the polling job continuing and being able to detect whenever TV goes offline or back online. I'm not sure this is the correct fix, but it might give some ideas about the problem. |
JAR from current main branch with shutdown() call from remoteDeviceRemoved() deleted: https://drive.google.com/file/d/1fG2pukbBj5z7XujGfRZ9a8O4_mVNh9CK/view?usp=sharing |
Fixes openhab#7055 Signed-off-by: Jacob Laursen <jacob-github@vindvejr.dk>
* Fix reconnect after first connection to TV is lost. Fixes #7055 Signed-off-by: Jacob Laursen <jacob-github@vindvejr.dk> * Reduced log level to TRACE for logging of entered methods several times per second. Signed-off-by: Jacob Laursen <jacob-github@vindvejr.dk>
…ab#11487) * Fix reconnect after first connection to TV is lost. Fixes openhab#7055 Signed-off-by: Jacob Laursen <jacob-github@vindvejr.dk> * Reduced log level to TRACE for logging of entered methods several times per second. Signed-off-by: Jacob Laursen <jacob-github@vindvejr.dk> Signed-off-by: Nick Waterton <n.waterton@outlook.com>
…ab#11487) * Fix reconnect after first connection to TV is lost. Fixes openhab#7055 Signed-off-by: Jacob Laursen <jacob-github@vindvejr.dk> * Reduced log level to TRACE for logging of entered methods several times per second. Signed-off-by: Jacob Laursen <jacob-github@vindvejr.dk> Signed-off-by: Michael Schmidt <mi.schmidt.83@gmail.com>
…ab#11487) * Fix reconnect after first connection to TV is lost. Fixes openhab#7055 Signed-off-by: Jacob Laursen <jacob-github@vindvejr.dk> * Reduced log level to TRACE for logging of entered methods several times per second. Signed-off-by: Jacob Laursen <jacob-github@vindvejr.dk>
…ab#11487) * Fix reconnect after first connection to TV is lost. Fixes openhab#7055 Signed-off-by: Jacob Laursen <jacob-github@vindvejr.dk> * Reduced log level to TRACE for logging of entered methods several times per second. Signed-off-by: Jacob Laursen <jacob-github@vindvejr.dk>
…ab#11487) * Fix reconnect after first connection to TV is lost. Fixes openhab#7055 Signed-off-by: Jacob Laursen <jacob-github@vindvejr.dk> * Reduced log level to TRACE for logging of entered methods several times per second. Signed-off-by: Jacob Laursen <jacob-github@vindvejr.dk>
Expected Behavior
After a communication error happened the binding should detect when the device is online again and work again correctly.
Current Behavior
Binding does not recover from communication error and even a restart of the bundle does not completely solve the problem.
Possible Solution
Restart openHAB (not really a solution)
Steps to Reproduce (for Bugs)
Excerpt from the log file:
samsungtv.log
There are also some messages regarding an unknown device:
But a some seconds before this message the log contains this message
Your Environment
The text was updated successfully, but these errors were encountered: