I setup my Sezam Marvel with Enigma2 (egami 8.0.1) and PlexDVRAPI (Latest version from github).
Select Tuner Type=Multi
Bouquet to use=All
Debug Mode=X
After that I press green button (Save).
Log file \Root mp\hrtunerproxy.log
2018-02-05 21:23:04,282 INFO BaseURL: http://192.168.1.10:6084
2018-02-05 21:23:04,284 INFO FriendlyName: Sezam Marvel
2018-02-05 21:23:04,285 INFO Source: Multi
2018-02-05 21:23:04,286 INFO TunerCount: 3
2018-02-05 21:23:04,287 INFO Channels: 143
2018-02-05 21:23:04,288 INFO Bouquet all
2018-02-05 21:23:04,307 INFO Using Tuner: multi
In folder files
\etc\enigma2\
multi.device
multi.descover
Plex Server with Plex Pass (Version 1.10.1.4602 Debian Linux)
But
Plex log:
Feb 05, 2018 21:01:49.048 [0x7fcc377fc700] DEBUG - Request: [192.168.1.34:55392 (Allowed Network)] POST /media/grabbers/devices/discover (6 live) GZIP Signed-in Token
Feb 05, 2018 21:01:49.049 [0x7fcc377fc700] DEBUG - DVR:Device: Discovering and refreshing devices.
Feb 05, 2018 21:01:49.049 [0x7fcc377fc700] DEBUG - DVR:Grabber: HDHomerun discovered 0 compatible devices.
Feb 05, 2018 21:01:49.050 [0x7fcc377fc700] DEBUG - DVR:Grabber: Mystery discovered 0 compatible devices.
Feb 05, 2018 21:01:49.050 [0x7fcc377fc700] DEBUG - HTTP requesting POST http://127.0.0.1:32600/devices/discover
Feb 05, 2018 21:01:51.468 [0x7fcc377fc700] DEBUG - HTTP 200 response from POST http://127.0.0.1:32600/devices/discover
Feb 05, 2018 21:01:51.470 [0x7fcc3b7fe700] DEBUG - Completed: [192.168.1.34:55392] 200 POST /media/grabbers/devices/discover (6 live) GZIP 2421ms 470 bytes (pipelined: 4)
Feb 05, 2018 21:01:52.776 [0x7fcc3a7ff700] DEBUG - Request: [192.168.1.34:55392 (Allowed Network)] POST /media/grabbers/tv.plex.grabbers.hdhomerun/devices?uri=192.168.1.10%3A6084 (6 live) GZIP Signed-in Token (siva1@mail.ru)
Feb 05, 2018 21:01:52.776 [0x7fcc3a7ff700] DEBUG - DVR:Grabber: Checking device URI http://192.168.1.10:6084
Feb 05, 2018 21:01:52.777 [0x7fcc3a7ff700] DEBUG - HTTP requesting GET http://192.168.1.10:6084/discover.json
Feb 05, 2018 21:01:52.777 [0x7fcc3a7ff700] ERROR - Error issuing curl_easy_perform(handle): 7
Feb 05, 2018 21:01:52.777 [0x7fcc3a7ff700] WARN - HTTP error requesting GET http://192.168.1.10:6084/discover.json (0, No error) (Failed connect to 192.168.1.10:6084; Connection refused)
Feb 05, 2018 21:01:52.778 [0x7fcc3a7ff700] DEBUG - HTTP requesting GET http://192.168.1.10:6084/capability
Feb 05, 2018 21:01:52.778 [0x7fcc3a7ff700] ERROR - Error issuing curl_easy_perform(handle): 7
Feb 05, 2018 21:01:52.778 [0x7fcc3a7ff700] WARN - HTTP error requesting GET http://192.168.1.10:6084/capability (0, No error) (Failed connect to 192.168.1.10:6084; Connection refused)
Feb 05, 2018 21:01:52.779 [0x7fcc3a7ff700] ERROR - Error parsing content.
Feb 05, 2018 21:01:52.779 [0x7fcc3a7ff700] ERROR - Error parsing XML.
Feb 05, 2018 21:01:52.779 [0x7fcc3a7ff700] ERROR - DVR:Grabber: No tuner key exists for device, couldn’t obtain device status.
Feb 05, 2018 21:01:52.780 [0x7fcc3bfff700] DEBUG - Completed: [192.168.1.34:55392] 404 POST /media/grabbers/tv.plex.grabbers.hdhomerun/devices?uri=192.168.1.10%3A6084 (6 live) GZIP 4ms 452 bytes (pipelined: 5)
Any idea how to resolve this issue?
How I can get discover.json file? Where it must be lay?
Regards,
Siva.
can you get me an enigma2 log? so i can to see why the webserver is not starting. the discover.json is hosted in ram. what happens when you enter http://192.168.1.10:6084/discover.json in your webbrowser ?
also can you the latest plugin please version 4.0, thanks.
I setup my Sezam Marvel with Enigma2 (egami 8.0.1) and PlexDVRAPI (Latest version from github).
Select Tuner Type=Multi
Bouquet to use=All
Debug Mode=X
After that I press green button (Save).
Log file \Root mp\hrtunerproxy.log
2018-02-05 21:23:04,282 INFO BaseURL: http://192.168.1.10:6084
2018-02-05 21:23:04,284 INFO FriendlyName: Sezam Marvel
2018-02-05 21:23:04,285 INFO Source: Multi
2018-02-05 21:23:04,286 INFO TunerCount: 3
2018-02-05 21:23:04,287 INFO Channels: 143
2018-02-05 21:23:04,288 INFO Bouquet all
2018-02-05 21:23:04,307 INFO Using Tuner: multi
In folder files
\etc\enigma2\
multi.device
multi.descover
Plex Server with Plex Pass (Version 1.10.1.4602 Debian Linux)
But
Plex log:
Feb 05, 2018 21:01:49.048 [0x7fcc377fc700] DEBUG - Request: [192.168.1.34:55392 (Allowed Network)] POST /media/grabbers/devices/discover (6 live) GZIP Signed-in Token
Feb 05, 2018 21:01:49.049 [0x7fcc377fc700] DEBUG - DVR:Device: Discovering and refreshing devices.
Feb 05, 2018 21:01:49.049 [0x7fcc377fc700] DEBUG - DVR:Grabber: HDHomerun discovered 0 compatible devices.
Feb 05, 2018 21:01:49.050 [0x7fcc377fc700] DEBUG - DVR:Grabber: Mystery discovered 0 compatible devices.
Feb 05, 2018 21:01:49.050 [0x7fcc377fc700] DEBUG - HTTP requesting POST http://127.0.0.1:32600/devices/discover
Feb 05, 2018 21:01:51.468 [0x7fcc377fc700] DEBUG - HTTP 200 response from POST http://127.0.0.1:32600/devices/discover
Feb 05, 2018 21:01:51.470 [0x7fcc3b7fe700] DEBUG - Completed: [192.168.1.34:55392] 200 POST /media/grabbers/devices/discover (6 live) GZIP 2421ms 470 bytes (pipelined: 4)
Feb 05, 2018 21:01:52.776 [0x7fcc3a7ff700] DEBUG - Request: [192.168.1.34:55392 (Allowed Network)] POST /media/grabbers/tv.plex.grabbers.hdhomerun/devices?uri=192.168.1.10%3A6084 (6 live) GZIP Signed-in Token (siva1@mail.ru)
Feb 05, 2018 21:01:52.776 [0x7fcc3a7ff700] DEBUG - DVR:Grabber: Checking device URI http://192.168.1.10:6084
Feb 05, 2018 21:01:52.777 [0x7fcc3a7ff700] DEBUG - HTTP requesting GET http://192.168.1.10:6084/discover.json
Feb 05, 2018 21:01:52.777 [0x7fcc3a7ff700] ERROR - Error issuing curl_easy_perform(handle): 7
Feb 05, 2018 21:01:52.777 [0x7fcc3a7ff700] WARN - HTTP error requesting GET http://192.168.1.10:6084/discover.json (0, No error) (Failed connect to 192.168.1.10:6084; Connection refused)
Feb 05, 2018 21:01:52.778 [0x7fcc3a7ff700] DEBUG - HTTP requesting GET http://192.168.1.10:6084/capability
Feb 05, 2018 21:01:52.778 [0x7fcc3a7ff700] ERROR - Error issuing curl_easy_perform(handle): 7
Feb 05, 2018 21:01:52.778 [0x7fcc3a7ff700] WARN - HTTP error requesting GET http://192.168.1.10:6084/capability (0, No error) (Failed connect to 192.168.1.10:6084; Connection refused)
Feb 05, 2018 21:01:52.779 [0x7fcc3a7ff700] ERROR - Error parsing content.
Feb 05, 2018 21:01:52.779 [0x7fcc3a7ff700] ERROR - Error parsing XML.
Feb 05, 2018 21:01:52.779 [0x7fcc3a7ff700] ERROR - DVR:Grabber: No tuner key exists for device, couldn’t obtain device status.
Feb 05, 2018 21:01:52.780 [0x7fcc3bfff700] DEBUG - Completed: [192.168.1.34:55392] 404 POST /media/grabbers/tv.plex.grabbers.hdhomerun/devices?uri=192.168.1.10%3A6084 (6 live) GZIP 4ms 452 bytes (pipelined: 5)
Any idea how to resolve this issue?
How I can get discover.json file? Where it must be lay?
Regards,
Siva.
can you get me an enigma2 log? so i can to see why the webserver is not starting. the discover.json is hosted in ram. what happens when you enter http://192.168.1.10:6084/discover.json in your webbrowser ?
also can you the latest plugin please version 4.0, thanks.
unzip upload these, reboot, get me new log from tmp. thanks
New log file
can’t have been updated as debug log info is missing, or you image does not support session auto start where = PluginDescriptor.WHERE_SESSIONSTART, fnc=HRTunerProxy_AutoStart
I setup my Sezam Marvel with Enigma2 (egami 8.0.1) and PlexDVRAPI (Latest version from github).
Select Tuner Type=Multi
Bouquet to use=All
Debug Mode=X
After that I press green button (Save).
Log file \Root mp\hrtunerproxy.log
2018-02-05 21:23:04,282 INFO BaseURL: http://192.168.1.10:6084
2018-02-05 21:23:04,284 INFO FriendlyName: Sezam Marvel
2018-02-05 21:23:04,285 INFO Source: Multi
2018-02-05 21:23:04,286 INFO TunerCount: 3
2018-02-05 21:23:04,287 INFO Channels: 143
2018-02-05 21:23:04,288 INFO Bouquet all
2018-02-05 21:23:04,307 INFO Using Tuner: multi
In folder files
\etc\enigma2\
multi.device
multi.descover
Plex Server with Plex Pass (Version 1.10.1.4602 Debian Linux)
But
Plex log:
Feb 05, 2018 21:01:49.048 [0x7fcc377fc700] DEBUG - Request: [192.168.1.34:55392 (Allowed Network)] POST /media/grabbers/devices/discover (6 live) GZIP Signed-in Token
Feb 05, 2018 21:01:49.049 [0x7fcc377fc700] DEBUG - DVR:Device: Discovering and refreshing devices.
Feb 05, 2018 21:01:49.049 [0x7fcc377fc700] DEBUG - DVR:Grabber: HDHomerun discovered 0 compatible devices.
Feb 05, 2018 21:01:49.050 [0x7fcc377fc700] DEBUG - DVR:Grabber: Mystery discovered 0 compatible devices.
Feb 05, 2018 21:01:49.050 [0x7fcc377fc700] DEBUG - HTTP requesting POST http://127.0.0.1:32600/devices/discover
Feb 05, 2018 21:01:51.468 [0x7fcc377fc700] DEBUG - HTTP 200 response from POST http://127.0.0.1:32600/devices/discover
Feb 05, 2018 21:01:51.470 [0x7fcc3b7fe700] DEBUG - Completed: [192.168.1.34:55392] 200 POST /media/grabbers/devices/discover (6 live) GZIP 2421ms 470 bytes (pipelined: 4)
Feb 05, 2018 21:01:52.776 [0x7fcc3a7ff700] DEBUG - Request: [192.168.1.34:55392 (Allowed Network)] POST /media/grabbers/tv.plex.grabbers.hdhomerun/devices?uri=192.168.1.10%3A6084 (6 live) GZIP Signed-in Token (siva1@mail.ru)
Feb 05, 2018 21:01:52.776 [0x7fcc3a7ff700] DEBUG - DVR:Grabber: Checking device URI http://192.168.1.10:6084
Feb 05, 2018 21:01:52.777 [0x7fcc3a7ff700] DEBUG - HTTP requesting GET http://192.168.1.10:6084/discover.json
Feb 05, 2018 21:01:52.777 [0x7fcc3a7ff700] ERROR - Error issuing curl_easy_perform(handle): 7
Feb 05, 2018 21:01:52.777 [0x7fcc3a7ff700] WARN - HTTP error requesting GET http://192.168.1.10:6084/discover.json (0, No error) (Failed connect to 192.168.1.10:6084; Connection refused)
Feb 05, 2018 21:01:52.778 [0x7fcc3a7ff700] DEBUG - HTTP requesting GET http://192.168.1.10:6084/capability
Feb 05, 2018 21:01:52.778 [0x7fcc3a7ff700] ERROR - Error issuing curl_easy_perform(handle): 7
Feb 05, 2018 21:01:52.778 [0x7fcc3a7ff700] WARN - HTTP error requesting GET http://192.168.1.10:6084/capability (0, No error) (Failed connect to 192.168.1.10:6084; Connection refused)
Feb 05, 2018 21:01:52.779 [0x7fcc3a7ff700] ERROR - Error parsing content.
Feb 05, 2018 21:01:52.779 [0x7fcc3a7ff700] ERROR - Error parsing XML.
Feb 05, 2018 21:01:52.779 [0x7fcc3a7ff700] ERROR - DVR:Grabber: No tuner key exists for device, couldn’t obtain device status.
Feb 05, 2018 21:01:52.780 [0x7fcc3bfff700] DEBUG - Completed: [192.168.1.34:55392] 404 POST /media/grabbers/tv.plex.grabbers.hdhomerun/devices?uri=192.168.1.10%3A6084 (6 live) GZIP 4ms 452 bytes (pipelined: 5)
Any idea how to resolve this issue?
How I can get discover.json file? Where it must be lay?
Regards,
Siva.
can you get me an enigma2 log? so i can to see why the webserver is not starting. the discover.json is hosted in ram. what happens when you enter http://192.168.1.10:6084/discover.json in your webbrowser ?
also can you the latest plugin please version 4.0, thanks.
unzip upload these, reboot, get me new log from tmp. thanks
New log file
can’t have been updated as debug log info is missing, or you image does not support session auto start where = PluginDescriptor.WHERE_SESSIONSTART, fnc=HRTunerProxy_AutoStart
not sure, whats wrong may be ask the images makers why where = PluginDescriptor.WHERE_SESSIONSTART, fnc=HRTunerProxy_AutoStart is not running a plugin loading.
@andyblac1974 said:
not sure, whats wrong may be ask the images makers why where = PluginDescriptor.WHERE_SESSIONSTART, fnc=HRTunerProxy_AutoStart is not running a plugin loading.
May be I start plugin manual? Can you explain how start it.
@andyblac1974 said:
not sure, whats wrong may be ask the images makers why where = PluginDescriptor.WHERE_SESSIONSTART, fnc=HRTunerProxy_AutoStart is not running a plugin loading.
May be I start plugin manual? Can you explain how start it.
Hi guys, been using enigma2 for Plex IPTV for a few months now and it’s been great but I stumbled across this last night and it could solve a lot of problems for people.
A guy on github has made an application that works with a .m3u file to create a virtual tuner on the machine PMS is running on.
For example I’ve created a virtual tuner on my windows machine with IPTV but your PMS must also be running on the same machine. He has versions for Linux and other OS as well but not nVidia Shield yet. Link below, works great and might help out some people with issues here.
@shaneosullivan said:
Hi guys, been using enigma2 for Plex IPTV for a few months now and it’s been great but I stumbled across this last night and it could solve a lot of problems for people.
A guy on github has made an application that works with a .m3u file to create a virtual tuner on the machine PMS is running on.
For example I’ve created a virtual tuner on my windows machine with IPTV but your PMS must also be running on the same machine. He has versions for Linux and other OS as well but not nVidia Shield yet. Link below, works great and might help out some people with issues here.
Think you might have misunderstood. Currently (before today) I used my enigma2 box for IPTV and Plex took the stream from the enigma2 box. With this application (telly), I no longer need to have an enigma2 box for IPTV.
So I can now keep my enigma2 box for DVB-S only and put my IPTV directly on my windows pc so there is a lot less network traffic.
Did you make this proxy communicate with your enigma2 receiver ? How did you do that ?
Another potential use of this plugin would be to watch satellite channels from Plex (just as andyblac1974’s plugin here), but for this the question would be : could an enigma2 box generate a compatible .m3u file in order to watch all its channels ?
Another potential use of this plugin would be to watch satellite channels from Plex (just as andyblac1974’s plugin here), but for this the question would be : could an enigma2 box generate a compatible .m3u file in order to watch all its channels ?
Maybe I now misunderstand what you mean
HrTunerProxy can work with Satellite and IPTV, I have this working now. I’m not sure how you get an m3u file onto the enigma2 box but my IPTV provider has given me a IPK file which sets up the channels automatically.
Another potential use of this plugin would be to watch satellite channels from Plex (just as andyblac1974’s plugin here), but for this the question would be : could an enigma2 box generate a compatible .m3u file in order to watch all its channels ?
Maybe I now misunderstand what you mean
HrTunerProxy can work with Satellite and IPTV, I have this working now. I’m not sure how you get an m3u file onto the enigma2 box but my IPTV provider has given me a IPK file which sets up the channels automatically.
I meant creating an m3u file containing streams pointing to my own enigma2 box, and viewing (with a PC on my LAN, or any device capable of opening m3u links) the DVB-S channels I receive on my satellite receiver (not IPTV channels).
Hi @andyblac1974 thanks for posting over in the telly github page, hopefully you guys will do something great there. I’d love to give you both a donation also if this is possible, just let me know.
There’s a few of us in work using Enigma2 devices as tuners and are having great fun playing around with them and getting things to work. Three quick questions though, you might have an answer to.
Do you know if Plex have a fix for the nar audio bug where live tv gets it mixed up?
Do you know if Plex will enable us to use different EPG’s for seperate hardware tuners?
Would you have any advise on why BBC 1 & 2 will not play live from enigma2 but will record fine and play back fine on the web player, possibly 1080i with the web player not able to handle interlaced video?
HI, I’m trying to install the plugin in a blackhole image.
I have decompressed it in systemplugins and restarted but it does not appear in the add-ons section.
Does it work with blackhole? Thanks for the help.
Hi, I’m installed the plugin on my VU+ Uno 4K with a OpenPLi 6.2-rc Image with build date 2018-04-13.
But Plex does not find the device and displays an error.
