Sorry for the delay. The plex server has ipv6 turned off. The plex server authorized device show Kodi. The results for the plex inquiries, with Kodi running and playing are for: The resources. <MediaContainer size="3"> <Device name="NAS2" product="Plex Media Server" productVersion="1.20.1.3252-a78fef9a9" platform=“Linux” platformVersion=“ReadyNAS OS” device=“ReadyNAS 212” clientIdentifier=REDACTED" createdAt="1463053575" lastSeenAt="1601730075" provides="server" owned=“1” accessToken=REDACTEDpublicAddress=REDACTED httpsRequired=“0” synced=“0” relay="0" dnsRebindingProtection="0" natLoopbackSupported="0" publicAddressMatches="1" presence=“1”>`
Also asked Google assistant to tell Plex to update sensors, with reply that it would. No mention of Kodi in the above results??
mayker
(maykar (pronounced "maker" with a southern accent))
283
So it doesn’t look like the Kodi Plex client is being reported to plex in either the local or remote endpoints. Unless the client is reported to plex and shown in the /clients endpoint there is no way for Plex Assistant to know it exists. In the next version of Plex Assistant, it will have and option to check the remote endpoint plex.tv/api/resources, but unfortunately it doesn’t look like the client is reported there either.
Since you’ve mentioned that these are all on the same network, I can’t imagine it would be a network issue.
This might be a question for the maker of the plex addon for Kodi that you are using, or possibly there is another option/plugin out there for you to use in Kodi that would report itself as a client.
mayker
(maykar (pronounced "maker" with a southern accent))
284
You might also want to check if there is a setting like “Advertise as player” that needs to be enabled like there is in web clients. For web clients it is found in Settings > Plex Web > General > Advertise as player
Thank you very much. The plex addon for Kodi is the official addon from Plex. I’ll try another addon that is available and I’ll take a look at the plex settings. Thanks.
mayker
(maykar (pronounced "maker" with a southern accent))
286
Okay, found a reddit thread and an issue on the official plex for kodi addon’s github that seem to suggest that it does not yet have the ability to be advertised as a player. So it looks like this may be a limitation of the addon.
Though I don’t use Kodi and haven’t tested it, in my searches it seems that Plexkodiconnect might have that ability.
Looking at the plex server logs it reports the kodi player as an X-Plex name/device/platform and X-Plex provides to the player and verifies the token.
I’ll try PlexKodiConnect
Plex Assistant still does not recognize the client.
mayker
(maykar (pronounced "maker" with a southern accent))
289
So, to try and troubleshoot this I installed Kodi and gave the official Plex addon a try and it definitely doesn’t have player/client support.
Then I gave PlexKodiConnect a try. It will occasionally show up as a client from the plex.tv remote api endpoint, but never with a connection attribute and only shows up for a moment, then disappears until I do a full Kodi restart. I have seen it show up once in the local /clients endpoint, but strangely without a port attribute and after a browser refresh it was no longer there.
Seems it’s pretty buggy. I’ll give it a bit more of a try tomorrow, but it’s not looking promising.
When you see it in your local server’s /clients endpoint is it stable with no disappearing acts or anything like that?
The client endpoints are stable. The client plays video faultlessly. The plex logs tell nothing abnormal for this client. Home Assistant system.log shows " [plexwebsocket] Websocket connection failed: Cannot connect to host 192-168-1-112.3020xxxxxxx.plex.direct:32400 ssl:default [Connect call failed ('192.168.1.112', 32400)]" frequently pointing to /usr/local/lib/python3.8/site-packages/plexwebsocket.py
Just reporting 100% success with the new DialogFlow directions. Thanks @mayker for all of the hard work on this and especially for keeping the instructions up to date!
it stopped what was playing and started playing the movie Cars immediately. So I’m pretty sure we should be able to get this to work with a roku
mayker
(maykar (pronounced "maker" with a southern accent))
296
I imagine it is the proxy through client setting that is the issue, in a coming release this will be an option that you can turn on and off per device. There are a lot of good things coming, just haven’t had the time to finish it up for release yet. Soon.
mayker
(maykar (pronounced "maker" with a southern accent))
297
If you don’t mind editing some code, you can test by commenting out the 2 times cast.proxyThroughServer() shows up in __init__.py and restarting.
well that seems to have worked. Amazing response @mayker . So far I’m just testing it from plex_assistant.command but I’m sure I’ll be able to follow the rest as well. Thanks so much!
Now what I’m going to try to do is parse out the data from ifttt and launch plex on the appropriate roku, then poll plex assistant to find the player, then have it process your stuff. Not sure if I should have a separate automation to do this or if it should be combined with yours.
mayker
(maykar (pronounced "maker" with a southern accent))
300
You could combine the automations. Just add your automation to the action: section of the IFTTT automation.
yeah I gotta figure out how to get the data, which I see is all in trigger.event.data.command. I’m using shell commands in another automation where I am passing it the state of an entity, but passing it like this doesn’t seem to work
Then again I don’t really know what I’m doing. I don’t even think once I parse the data out with a shell command, that I can return that data to the automation. Really new to this stuff.