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
Plex - Session key error #101111
Comments
Hey there @jjlawren, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) plex documentation |
@ABEIDO I've submitted a fix for this. I haven't been able to reproduce the issue locally, but if you'd provide debug logs once the fix is merged we can ensure there are no other potential issues behind this one. |
@jjlawren Oki, im kinda of a newbie to github( trying :) ) So same logs as before i guess, but when can i consider i merged, im guessing when its out and patched the integration on HA? |
Once 2023.11 is out, you can enable debug logs for the library by adding this to your logger:
default: info
logs:
plexwebsocket: debug This will log every websocket callback we receive with messages like "Payload received:" at debug level. Capture something that would have caused things to fail in the past and please share it in a new issue for the Plex integration. It'll get assigned to me. Once you capture the message, you'll want to take that out of your config. |
Oki, willdo |
The problem
Hi
Everytime i stop a movie or when its stopped by itself i get an 2 errors in log of Home Assistant (see below).
I understand that im in somewehere in the middle regading where the fix could be done. And i realize that you could point to PlexKodiConnect as the ones to point to as cause but it could be that this integration is handling a acceptable error in Plex media server logs as real error in Plex HA integration.
Im using PlexKodiConnect as integration on to Plex and Kodi in the front. This setup causes errors in Plex logs and i think thats the ones the HA integration reacts to:
Plex Media Server logs:
Sep 29, 2023 15:02:41.502 [10788] ERROR - [Req#f397] Unknown metadata type: folder
Sep 29, 2023 15:02:41.650 [10788] ERROR - [Req#f3a1] Unknown metadata type: folder
Sep 29, 2023 15:02:41.685 [5888] ERROR - [Req#f3a4] Unknown metadata type: folder
Sep 29, 2023 15:02:41.772 [5872] ERROR - [Req#f3ab] Unknown metadata type: folder
Sep 29, 2023 15:02:41.786 [5872] ERROR - [Req#f3ae] Unknown metadata type: folder
According to PlexKodiConnect . those error are nothing important. When using Plex Web or via Plex mobile app no error in log occur.
Ive reinstalled both integration, Kodi an all other involved software but issues still occur. And ive tried with tinkering with settings with no luck.
Home Assistant: First error
Logger: homeassistant.components.plex
Source: components/plex/init.py:207
Integration: Plex Media Server (documentation, issues)
First occurred: 10:24:59 (3 occurrences)
Last logged: 15:02:39
Websocket to PLEX failed, aborting [Error: Unknown]
Home Assistant: Second error
Logger: plexwebsocket
Source: /usr/local/lib/python3.11/site-packages/plexwebsocket.py:170
First occurred: 10:24:59 (3 occurrences)
Last logged: 15:02:39
Unexpected exception occurred: 'sessionKey'
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/plexwebsocket.py", line 131, in running
if self.player_event(msg):
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/plexwebsocket.py", line 187, in player_event
session_id = payload["sessionKey"]
~~~~~~~^^^^^^^^^^^^^^
KeyError: 'sessionKey'
What version of Home Assistant Core has the issue?
core-2023.9.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Plex Media Server
Link to integration documentation on our website
https://www.home-assistant.io/integrations/plex
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: