You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all. I was running locast2plex just fine for quite a while, until I switched from networks. The original network was accessed via wifi, and this new one is hard wired, but I doubt that there should be any issue with that aspect of it. It just seems odd that, immediately after switching networks, suddenly Plex can't recognize the locast2plex DVR.
I've modified the config.ini to reflect the new network IP, and running "python main.py" fires it up with now errors, just as it ever did. But if I try to add it to Plex it simply does not recognize the locast DVR, even if I enter the IP manually.
Any ideas would be most welcome to help me solve this bizarre mystery.
I'm seeing the same thing without the network change so I don't think that is relevant. Mine only started over the past 3-4 days, I believe.
I've updated to the latest in docker, started/stopped the container, checked the docker logs. Everything seems like it should be working. I do believe I ran a plex server update around that timeframe so I'm wondering if that could be related. Might look at trying to downgrade Plex to see if that helps at all.
Hi, thanks for replying. I'll try hooking it up to the old network again and see if I get the same results. All I know is that locast2plex failed immediate after I made the change.
As for that whole Docker thing, I'll be danged if I can figure out how to properly implement it on my Intel PC; I see it as voodoo frankly. I do know the concept behind it and all, but it requires a bunch of steps to create and that guarantees that one of those steps will produce a result which will be nothing like what they say in the instructions, and it will end there.
Then again, maybe I'll give it a go anyway, just for no fun at all...
Any update on this issue? I am having a similar issue as OP, had to change my server's static IP and after that locast2plex no longer works. Docker reports that it started up correctly, but no luck in Plex discovering the service.
I actually went to look in a different thread, and the issue ended up being a result of an old version. Stopping the container and then issuing a docker-compose pull grabbed the latest version, and service discovery in Plex is working now.
Hm... I've updated to the latest again but while locast2plex still seems to be running correctly. Plex still fails to actually play even though it sees the antenna and says everything is good. Just as soon as I attempt to play I get this:
Activity
jcmitch commentedon Aug 19, 2021
I'm seeing the same thing without the network change so I don't think that is relevant. Mine only started over the past 3-4 days, I believe.
I've updated to the latest in docker, started/stopped the container, checked the docker logs. Everything seems like it should be working. I do believe I ran a plex server update around that timeframe so I'm wondering if that could be related. Might look at trying to downgrade Plex to see if that helps at all.
elbowgeek commentedon Aug 19, 2021
Hi, thanks for replying. I'll try hooking it up to the old network again and see if I get the same results. All I know is that locast2plex failed immediate after I made the change.
As for that whole Docker thing, I'll be danged if I can figure out how to properly implement it on my Intel PC; I see it as voodoo frankly. I do know the concept behind it and all, but it requires a bunch of steps to create and that guarantees that one of those steps will produce a result which will be nothing like what they say in the instructions, and it will end there.
Then again, maybe I'll give it a go anyway, just for no fun at all...
iamon13 commentedon Aug 30, 2021
Any update on this issue? I am having a similar issue as OP, had to change my server's static IP and after that locast2plex no longer works. Docker reports that it started up correctly, but no luck in Plex discovering the service.
jcmitch commentedon Aug 30, 2021
I believe the root cause to be a Plex issue. There are a few threads about the issue over on the Plex forms but no fixes yet from what I can tell.
iamon13 commentedon Aug 30, 2021
I actually went to look in a different thread, and the issue ended up being a result of an old version. Stopping the container and then issuing a docker-compose pull grabbed the latest version, and service discovery in Plex is working now.
jcmitch commentedon Aug 30, 2021
Hm... I've updated to the latest again but while locast2plex still seems to be running correctly. Plex still fails to actually play even though it sees the antenna and says everything is good. Just as soon as I attempt to play I get this:

jcmitch commentedon Sep 2, 2021
Well I guess this (and this whole project) doesn't matter anymore. 😞