-
Notifications
You must be signed in to change notification settings - Fork 58
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
Integration working bad last few days #178
Comments
Same here |
Seeing the same here. Home Assistant 2022.8.7 Logger: root Uncaught thread exception During handling of the above exception, another exception occurred: Traceback (most recent call last): |
This is normally due to a wrong version of |
Is there anything I can provide you to verify that's the case? I'm happy to help in any way I can. |
Same issue, seems to have started after upgrading to Home Assistant 2022.8.7. |
I'm having the exact same problems too. Edit: restoring to 2022.8.6 solves the issue. |
Same here, started after updating to HA 2022.8.7 |
Same thing, and 100% sure it started after the last update. |
Same for me |
I'm using 2022.8.7 without any issue, so problem is not related to HA version. |
if you create a |
I've got HAOS installed barebones. That was a bit of a trip trying to find the websocket_client version. I ended up opening a shell into the homeassistant container and running a "pip show websocket_client", which reports v1.4.0. Is that that correct location?
|
This means that you have last version installed, I don't know which integration require to install that version, but that's it. |
BTW this will be fixed by this PR when (and if) will be merged. For now the only possible work-around is rollback to version 1.3.3 of the library. |
I've downgraded my websocket-client to 1.3.3 version. But still that problem occurs:
|
I think that an integration is asking for that specific version, so when HA restart immediately install v.1.4 again. |
Please report if you find out which integration requires an incompatible .version |
Even after HA restart when I check version it is still 1.3.3:
I have docker hassio. |
So probably this is not the version that HA is using, you should search for a venv dedicated to HA. For sure this issue was introduced in 1.4.0 |
You could try to manually modify the
After modification reboot HA. |
modified as such, and will let you know if it starts acting up again.
|
I didn't find any custom component using websocket-client, only yours and for this one the manifest is correct I think: "websocket-client>=0.58.0" |
Change to "websocket-client>=0.58.0,<=1.3.3", |
Ahh, right. Version higher than 0.58, but lower than 1.3.3. |
Please try updating to last release v0.7.6 and let me know if this fix the issue. |
Thanks, that seems to have fixed my instance. |
It looks like that solved the problem in my case as well. Thank you. |
For me too, thanks for the update! |
So can we close this issue? |
Yes. After update works great. |
I get the same "websocket connected" warnings in logs with v0.7.6: Source: custom_components/samsungtv_smart/api/samsungws.py:592 media_player.samsung_tv - Error refreshing from SmartThings. Check connection status with TV on the phone App Home Assistant 2022.9.2 |
Describe the bug
Integration not working. TV is still off.
Expected behavior
If I reload the integration. It works for a while and then it doesn't work again.
Environment details:
Output of HA logs
2022-08-29 09:26:19.303 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration samsungtv_smart which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-08-29 09:27:15.676 WARNING (MainThread) [homeassistant.components.media_player] Setup of media_player platform samsungtv_smart is taking over 10 seconds.
2022-08-29 09:30:39.416 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 09:30:39.523 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 09:30:39.531 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 09:55:39.631 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 09:55:39.760 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 09:55:39.798 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 10:20:39.737 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 10:20:39.828 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 10:20:39.850 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 10:45:39.925 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 10:45:40.019 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 10:45:40.023 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 11:10:40.010 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 11:10:40.108 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 11:10:40.113 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 11:35:40.322 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 11:35:40.424 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 11:35:40.453 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 12:00:40.466 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 12:00:40.550 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 12:00:40.562 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 12:25:40.628 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 12:25:40.724 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 12:25:40.731 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 12:50:40.769 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 12:50:40.872 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 12:50:40.878 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 13:15:41.087 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 13:15:41.186 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 13:15:41.194 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 13:40:41.254 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 13:40:41.347 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 13:40:41.356 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 14:05:41.381 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 14:05:41.475 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 14:05:41.480 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 14:30:41.451 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 14:30:41.542 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 14:30:41.580 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 14:55:42.311 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 14:55:42.401 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 14:55:42.406 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 15:20:42.512 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 15:20:42.620 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 15:20:42.637 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 15:45:42.484 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 15:45:42.576 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 15:45:42.584 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 16:10:42.691 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 16:10:42.791 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 16:10:42.800 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 16:35:42.850 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 16:35:42.945 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 16:35:42.965 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 17:00:43.002 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 17:00:43.132 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 17:00:43.133 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 17:25:43.142 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 17:25:43.237 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 17:25:43.247 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 17:50:43.344 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 17:50:43.455 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 17:50:43.467 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 18:09:44.737 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 18:09:44.827 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 18:09:44.839 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 18:35:28.525 ERROR (SamsungRemote) [root] Uncaught thread exception
File "/config/custom_components/samsungtv_smart/api/samsungws.py", line 376, in _client_remote_thread
2022-08-29 22:06:37.281 WARNING (SamsungRemote) [websocket] websocket connected
2022-08-29 22:06:37.453 WARNING (SamsungArt) [websocket] websocket connected
2022-08-29 22:06:37.474 WARNING (SamsungControl) [websocket] websocket connected
2022-08-29 22:43:53.876 ERROR (SamsungRemote) [root] Uncaught thread exception
File "/config/custom_components/samsungtv_smart/api/samsungws.py", line 376, in _client_remote_thread
2022-08-30 08:52:40.120 WARNING (SyncWorker_8) [custom_components.samsungtv_smart.api.samsungws] _ws_send: connection is closed, send command failed
The text was updated successfully, but these errors were encountered: