Home Assistant release with the issue:
0.101.3
Last working Home Assistant release (if known):
0.100.2
Operating environment (Hass.io/Docker/Windows/etc.):
venv
Integration:
Plex
https://www.home-assistant.io/integrations/plex/
Description of problem:
When the plex media server is restarted during an update the sensor and media players do not update. No errors are seen during the logs at this time either. The sensor also does not go to unavailable during this restart.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
plex:
token: !secret token
Traceback (if applicable):
Additional information:
It is also important to note that when I restart the media server by itself this issue does not exist. Even restarting the system that plex runs off of has no issue. This seems to only be an issue during an update to plex media server itself.
Can you bump up the logging and reproduce?
logger:
logs:
homeassistant.components.plex: debug
plexapi: debug
plexwebsocket: debug
Also 0.102 (and the current beta) have additional debug logging to troubleshoot scenarios like this.
@jjlawren sure but we will need to wait for the server to receive an update before I can come back with logs :)
Thanks. I thought I tested various restarts of the Plex server thoroughly, but there must be another edge case in how to handle when the service upgrades itself. My Plex server doesn't have the ability upgrade via the Plexweb interface, so I'll have to rely on others to test. If possible, the extra debug logging in 0.102 would be very helpful to have.
ok I usually download the plex betas about a day after release so shouldn't be too long of a wait. Hopefully someone else who see's this and hasn't updated their server yet can grab the logs sooner than I can.
So I tried to pull the debug logs from my dev instance and synced it up against the latest changes as of 9am PST today. It seems that the issue is no longer present in the dev branch so one of the fixes from 0.102 beta seems to have corrected this issue.
@dshokouhi you encountered this again, correct? Reopening so we can track this down.
Yup that is correct in 0.102.2 next time I get a server update I will make sure to grab the logs.
@dshokouhi any luck in testing recently?
@jjlawren I think in this case it may be solved but wanted to double check on the next server update. If you dont hear from me in a week lets consider this solved :)
Let's close this. If it occurs again and there's anything interesting in the logs feel free to reopen.
@jjlawren I just installed an update today with debug logging on to capture this issue. It looks like after it disconnects, it never reconnects.
https://drive.google.com/open?id=1XY7Loh693z8tqlkf1mAZDi3Md2wPq7zG
Is this enough info to reopen?
This is my logger setting:
logger:
default: warn
logs:
homeassistant.components.plex: debug
plexapi: debug
plexwebsocket: debug
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.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 馃憤
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Tested today on 0.109.2 same issue
I'm running low on ideas, but perhaps #35351 will help shed some light in the next release.
After updating to 0.110.x I can confirm this issue is fixed! I was able to update the server in the plex UI and after it finished I went to play an item and it actually updated in HA! The logs also indicate that the server attempted to reconnect which was not there before, previously I only saw the disconnected message!
2020-05-25 17:03:35 ERROR (MainThread) [plexwebsocket] Websocket disconnected
2020-05-25 17:04:35 ERROR (MainThread) [plexwebsocket] Websocket connection failed, retrying in 15s: [Errno 104] Connection reset by peer