wrboyce
Device always offline
Hello,
The device is not announcing itself to plex. This messes up the reconnect function in plex. (when recording if the stream is dropped for example, if plex thinks the device is offline it will not try to reconnect).
So making the script announce itself and do it regularly so that plex knows its online would be nice.
Having the same issue. I downloaded plexheadend-1.0.0_linux_amd64.tar.gz and when I try to run it it only prints information, doesn't seems that the app is running. Checking processes with htop and can't se plexheadend.
kidkic@satellite:~$ ./plexheadend --proxy-hostname 192.168.99.14
2018/02/03 15:14:12 TvhURL: http://plex:****@localhost:9981
2018/02/03 15:14:12 ProxyURL: http://192.168.99.14:80
2018/02/03 15:14:12 ListenAddr: :80
2018/02/03 15:14:12 DeviceName: plexHeadend
2018/02/03 15:14:12 DeviceID: 1
2018/02/03 15:14:12 TunerCount: 1
kidkic@satellite:~$
Try running it on another port, sounds like port 80 is already In use so it failed to get a socket.
On 4/02/2018, at 03:17, Fredrick Bäcker [email protected] wrote:
Having the same issue. I downloaded plexheadend-1.0.0_linux_amd64.tar.gz and when I try to run it it only prints information, doesn't seems that the app is running. Checking processes with htop and can't se plexheadend.
kidkic@satellite:~$ ./plexheadend --proxy-hostname 192.168.99.14 2018/02/03 15:14:12 TvhURL: http://plex:****@localhost:9981 2018/02/03 15:14:12 ProxyURL: http://192.168.99.14:80 2018/02/03 15:14:12 ListenAddr: :80 2018/02/03 15:14:12 DeviceName: plexHeadend 2018/02/03 15:14:12 DeviceID: 1 2018/02/03 15:14:12 TunerCount: 1 kidkic@satellite:~$ — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
@bhaap I had the same issue. Maybe this helps.
I've added it with using wg++ guide xml.
However I get the same error as @bhaap with device not found.
If I check the device http://192.168.99.14:8080/discover.json I get
{
"FriendlyName": "plexHeadend",
"ModelNumber": "HDHR4-2DT",
"FirmwareName": "hdhomerun4_dvbt",
"TunerCount": 1,
"FirmwareVersion": "20160629",
"DeviceID": "1",
"DeviceAuth": "",
"BaseURL": "http://192.168.99.14:8080",
"LineupURL": "http://192.168.99.14:8080/lineup.json"
}
and the lineup gives some info http://192.168.99.14:8080/lineup.json
[
{
"GuideNumber": "227",
"GuideName": "Cartoon",
"URL": "http://plex:plex@localhost:9981/stream/channel/bef57f81cd93b17fb856a1eeeb3562c9"
},
{
"GuideNumber": "443",
"GuideName": "Viasat Explore",
"URL": "http://plex:plex@localhost:9981/stream/channel/54da9201a45ef9daadef52d73e6e0bee"
},
{
"GuideNumber": "520",
"GuideName": "Trace Urban HD",
"URL": "http://plex:plex@localhost:9981/stream/channel/3c6dde810a0e3ae54c3f0b6ec0da0b7b"
},
...
When running the lineup I notice that the url is localhost. So with my setup
machine 1 : plex x.x.x.11 machine 2 : tvheadend + plexheadend (proxy) x.x.x.14
I need to make sure both urls is pointing to my *.14, tvheadend + plexheadend.
/home/kidkic/plexheadend --proxy-hostname 192.168.99.14 --proxy-listen 8080 --tvh-host 192.168.99.14
Now I can use plex on *.11 and it works.
I have both --proxy-hostname and --tvh-host set to the proper IPs, I can view the TV stream properly from Plex, yet still when I go to DVR configuration in Plex it says that the device could not be found.. Any fix for this? Maybe it has something to do with UPNP?
