Enigma2 support for Plex DVR/LiveTV!

Live TV & DVR
581

Sep 01, 2018 21:39:06.622 [2880] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/4XEPX0MO at http://199.99.199.30:6083

I found that in the log…it seems the grabber use the wrong Port :6083 but i have added the receiver as multi :6084

could that be the reason?

Edit: Sep 01, 2018 21:39:06.622 [2880] DEBUG - HTTP requesting GET http://199.99.199.30:6083/discover.json - again Port 6083

image
image.jpg776×131 31.9 KB

Edit2: http://199.99.199.30:6084/discover.json works in my browser as the plugin is listening to :6084.

582

Hi @andyblac1974 Is that enough information or do you need something more?

583

seems plex have changed something in their detection code.

Sep 01, 2018 21:41:05.728 [6192] DEBUG - HTTP 200 response from GET http://199.99.199.30:6084/device.xml
Sep 01, 2018 21:41:05.728 [6192] DEBUG - NetworkServiceBrowser: found 1 SSDP devices via http://199.99.199.30:6084/device.xml
Sep 01, 2018 21:41:05.728 [6192] DEBUG - NetworkServiceBrowser: SSDP arrived: 199.99.199.30 (vusolo4k)
Sep 01, 2018 21:41:05.728 [0988] DEBUG - DVR:Grabber: HDHomerun discovered a model vusolo4k.
Sep 01, 2018 21:41:05.728 [0988] DEBUG - DVR:Grabber: HDHomerun discovered 0 compatible devices.

it sees the vusolo4k, but it is not seeing it as a compatible device, as I don’t use plex (or any media server) anymore, not sure what’s changed lately.

maybe ask if anyone else is having the same issue ?, if my plugin still works for anyone ?.

Andy.

584

Is it normal that Plex is trying to connect to all Ports?

HTTP error requesting GET http://199.99.199.30:6081/discover.json (0, No error) (Failed connect to 199.99.199.30:6081; No error)
HTTP error requesting GET http://199.99.199.30:6083/discover.json
HTTP error requesting GET http://199.99.199.30:6084/discover.json

Crazy because i can setup all channels once and then this is happening.
Could it be that there is in Plex an old setting from my receiver with different image before?

Sep 01, 2018 21:41:05.728 [0988] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/4XEPX0MO at http://199.99.199.30:6083
Sep 01, 2018 21:41:05.728 [0988] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/KQMS2M29 at http://199.99.199.30:6084
Sep 01, 2018 21:41:05.728 [0988] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/WAMSO7J1 at http://199.99.199.30:6084
Sep 01, 2018 21:41:05.728 [0988] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/WTBFVAAR at http://199.99.199.30:6081
Sep 01, 2018 21:41:05.728 [0988] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/X40VGCW0 at http://199.99.199.30:6084
Sep 01, 2018 21:41:05.728 [0988] DEBUG - DVR:Device: Device device://tv.plex.grabbers.hdhomerun/4XEPX0MO died
Sep 01, 2018 21:41:05.744 [0988] DEBUG - DVR:Device: Device device://tv.plex.grabbers.hdhomerun/KQMS2M29 died
Sep 01, 2018 21:41:05.744 [0988] DEBUG - DVR:Device: Device device://tv.plex.grabbers.hdhomerun/WAMSO7J1 died
Sep 01, 2018 21:41:05.744 [0988] DEBUG - DVR:Device: Device device://tv.plex.grabbers.hdhomerun/WTBFVAAR died
Sep 01, 2018 21:41:05.760 [0988] DEBUG - DVR:Device: Device device://tv.plex.grabbers.hdhomerun/X40VGCW0 died

Why are there 3 different devices for Port 6084? Maybe old device ID? Can i clear that?

Is anyone else having this issue with the Plugin? Is Plex still seeing your device?

585

Nobody with the same issue? Is the vusolo4k working for everbody? No device not found error?

I appreciate every help. This is so annoying if i need to change something.

Streaming and recording works but i cant change or add channels because of the error.

586

I don’t have a Solo 4K, but my Uno 4K SE works although I don’t use Live-TV in Plex often.
Dunno if that helps, probably not much :wink:

587

Is your Uno still visible in the settings under DVR & Live TV without an error? Could you add or remove channels?

Maybe it has something to do with the OpenPLI Image 6.2? Before with OpenATV i didnt have this Problem.

588

It is visible and I can use it normally, add channels or view Live TV. I use VTI, so maybe this has to do with the image, hard to tell. You could backup your current image and test either ATV or VTI is it works there.

589

I recently installed hrtunnerproxy.
I have a problem, every time I open a channel it takes a long time to boot.
I was scanning the windows processes and saw that it does transcoding on every channel it opens.
Is it possible to disable livetv trasconding?
Thanks

590

Ah damn…i really need help about that. Now i tried to delete and add again but now i am also unable to add the receiver again. Are the devices not registered somewhere and maybe still the cache left and is causing this issue now?

I want to use OpenPLI 6.2 as an image would be nice if somebody know more about…

591

As i did delete the receiver in Plex now…i tried to delete also the cache but when i start Plex i can still see ip from receiver and HTTP requests…

Sep 06, 2018 14:28:07.554 [7060] DEBUG - DVR:Device: Discovering and refreshing devices.
Sep 06, 2018 14:28:07.554 [7060] DEBUG - DVR:Grabber: HDHomerun discovered 0 compatible devices.
Sep 06, 2018 14:28:07.554 [7060] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/4XEPX0MO at http://199.99.199.30:6083
Sep 06, 2018 14:28:07.554 [7060] DEBUG - HTTP requesting GET http://199.99.199.30:6083/discover.json
Sep 06, 2018 14:28:09.585 [7060] ERROR - DVR:Device: Error refreshing existing device device://tv.plex.grabbers.hdhomerun/4XEPX0MO, marking as dead.
Sep 06, 2018 14:28:09.585 [7060] DEBUG - DVR:Device: Testing grabber HDHomerun device device://tv.plex.grabbers.hdhomerun/KQMS2M29 at http://199.99.199.30:6084
Sep 06, 2018 14:28:09.585 [7060] DEBUG - HTTP requesting GET http://199.99.199.30:6084/discover.json
Sep 06, 2018 14:28:13.351 [5836] DEBUG - HTTP 200 response from GET http://199.99.199.30:6084/device.xml
Sep 06, 2018 14:28:13.351 [5836] DEBUG - NetworkServiceBrowser: found 1 SSDP devices via http://199.99.199.30:6084/device.xml
Sep 06, 2018 14:28:13.351 [5836] DEBUG - NetworkServiceBrowser: SSDP arrived: 199.99.199.30 (vusolo4k)

How can i delete them completely from PMS?

592

Sure, get a player device that can natively display mpegts :wink:
Jokes aside, which clients do you use?

593

PS4 and mostly android or Web Player, but the clients are not the problem. If i setup before it worked for all my clients. Last time i want to add a channel and could not due to error. So i deleted the receiver and added again with the additional channel.

But now i cant add the vusolo4k anymore…No DVR connected and i still see this in the log. Maybe it would help when i delete those entries, but i dont know where…i cant find the location

594

I use plex media player in windows and android.
I wish he did not do transcoding.
it’s possible?

595

Im not 100% sure but if you set the quality of the stream to original…then it should direct play the stream and not transcode anymore. This you can also set as default in the app…In Android under settings and then Quality. try to set to maximum and check if its still transcoding.

596

At least Android I know for sure is capable of Direct Play of mpegts, at least it does for me. Just checked again.
Might also depend on your source. How do you receive your Live-TV? Which codec if you know?

597

its possible change stream format on enigma2?
i dont like transcoding because is very slow

598

No but there are H264 and H265 streams for example. The latter could cause problems for example.

599

the box will stream the H264 codec.
Could it have to do with the audio codec?
do you know how to change the stream codec in the vu + box?

600

You can’t.