Enigma2 support for Plex DVR/LiveTV!

Live TV & DVR
421

Hi ich habe ein Kleines Problem immer wenn ich ein Film anklicken will kommt diese Meldung
egal ob HD oder SD. Ich habe Die Dreambox 900UHD mit ATV Open Image dazu das Plex DVR API for Enigma2 v3.2

422

@LockTown said:
Hi ich habe ein Kleines Problem immer wenn ich ein Film anklicken will kommt diese Meldung
egal ob HD oder SD. Ich habe Die Dreambox 900UHD mit ATV Open Image dazu das Plex DVR API for Enigma2 v3.2

version 3.2 is quite old now (oct 2017), can you try the latest version 3.6 please. in the mean time, could you supply me a log from Enigma2.

423

So ich habe jetzt alles geupdate Image OpenATV6.1 ,HRTunerProxy Enigma2 Plugin v.3.6 und Plex Server Version 1.11.1.4753 aber trozdem habe ich diesen Fehler ich habe jetzt 8 verschiedene Sende ins Bouquet gepackt.
Sky Cinema
Sky Cinema Action
Sky Cinema Hits
Fox HD
13th Street
Das Erste HD
RTL HD
ProSieben

der einzige sender der geht ist prosieben.

Wie mach ich ein LOG?

Super ich habe den Fehler gefunden ich habe vorher immer mit .xml die EGP reingestellt koditvepg.com/epgs/ zu 99% wurden alle Sender gefunden sogar mit Logo. Jetzt hab ich die ProgrammfĂŒhrer mit Telekom Deutschland GmbH zugeordnert jetzt geht es

424

Hi

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.

425

Looks like it doesnt work on the newest VTI Image (v13) ? Atleast when I try to copy the folder to: /usr/lib/enigma2/python/Plugins/Extensions

It wont show up in my extensions menu. Or am I too stupid?

426

@Nigthmare said:
Looks like it doesnt work on the newest VTI Image (v13) ? Atleast when I try to copy the folder to: /usr/lib/enigma2/python/Plugins/Extensions

It wont show up in my extensions menu. Or am I too stupid?

need to go into SystemPlugins aka /usr/lib/enigma2/python/Plugins/SystemPlugins

427

@“siva1@mail.ru” said:
Hi

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.

428

@andyblac1974 said:

@Nigthmare said:
Looks like it doesnt work on the newest VTI Image (v13) ? Atleast when I try to copy the folder to: /usr/lib/enigma2/python/Plugins/Extensions

It wont show up in my extensions menu. Or am I too stupid?

need to go into SystemPlugins aka /usr/lib/enigma2/python/Plugins/SystemPlugins

Sorry, typo. It is in this folder and won’t show up.

972×453 25.7 KB

429

@Nigthmare said:

@andyblac1974 said:

@Nigthmare said:
Looks like it doesnt work on the newest VTI Image (v13) ? Atleast when I try to copy the folder to: /usr/lib/enigma2/python/Plugins/Extensions

It wont show up in my extensions menu. Or am I too stupid?

need to go into SystemPlugins aka /usr/lib/enigma2/python/Plugins/SystemPlugins

Sorry, typo. It is in this folder and won’t show up.

972×453 25.7 KB

ok then i’ll need an enigma2 log, to see why it not running.

430

@andyblac1974 said:

@Nigthmare said:

@andyblac1974 said:

@Nigthmare said:
Looks like it doesnt work on the newest VTI Image (v13) ? Atleast when I try to copy the folder to: /usr/lib/enigma2/python/Plugins/Extensions

It wont show up in my extensions menu. Or am I too stupid?

need to go into SystemPlugins aka /usr/lib/enigma2/python/Plugins/SystemPlugins

Sorry, typo. It is in this folder and won’t show up.

972×453 25.7 KB

ok then i’ll need an enigma2 log, to see why it not running.

For sure, can you tell me which log?

431

sorry, i don’t know VTi image, for that you’ll need to go to their forum, i’ll be happy to go through it once you have one.

i need a full log of e2 starting up.

432

Hi

I’m setting up Plex DVR functionality. I’m able to connect PMS to my Ultimo but I have a problem with EPG. In our building we have DVB-T2 to DVB-C transmodulator system. We receive DVB-T2 signal but it is distributed using DVB-C signal.

This means that Plex thinks that I’m using cable system and doesn’t allow me to to select terrestrial operator during setup. Is there any workaround for this situation?

433

@o_p_s said:
Hi

I’m setting up Plex DVR functionality. I’m able to connect PMS to my Ultimo but I have a problem with EPG. In our building we have DVB-T2 to DVB-C transmodulator system. We receive DVB-T2 signal but it is distributed using DVB-C signal.

This means that Plex thinks that I’m using cable system and doesn’t allow me to to select terrestrial operator during setup. Is there any workaround for this situation?

hi, the only thing of, i can think of is make a user bouquet that lines up with a cable provider in your area, then in plex choose that provider for cable. then make sure the epg and channels lineup.

434

@andyblac1974 said:
sorry, i don’t know VTi image, for that you’ll need to go to their forum, i’ll be happy to go through it once you have one.

i need a full log of e2 starting up.

Got it working now
 It was on my end. I was connected to the wrong box
 Works fine :slight_smile:

435

Another question. Does it transcode automatically live TV or do you have to edit something somewhere?

436

it send the raw stream to plex, plex then transcodes if the client requires it.

437

@andyblac1974 said:

@“siva1@mail.ru” said:
Hi

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.

Hi andyblac1974

I setup last version from GitHub - OpenViX/HRTunerProxy: Setup Enigma2 to act as HR-Tuner Proxy.
Result is the same.

Result for http://192.168.1.10:6084/discover.json (in russian):

1085×574 34.3 KB

Translate - “connection not establish”

enigma2 log attached (by instruction from http://wiki.blue-panel.com/index.php/Create_Enigma2_log_file).

Regards,
Siva.

438

@“siva1@mail.ru” said:

@andyblac1974 said:

@“siva1@mail.ru” said:
Hi

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.

Hi andyblac1974

I setup last version from GitHub - OpenViX/HRTunerProxy: Setup Enigma2 to act as HR-Tuner Proxy.
Result is the same.

Result for http://192.168.1.10:6084/discover.json (in russian):

1085×574 34.3 KB

Translate - “connection not establish”

enigma2 log attached (by instruction from http://wiki.blue-panel.com/index.php/Create_Enigma2_log_file).

Regards,
Siva.

can you supply log file from /tmp and a screen shot of your setup from plugin please.

439

@andyblac1974 said:

@“siva1@mail.ru” said:

@andyblac1974 said:

@“siva1@mail.ru” said:
Hi

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.

Hi andyblac1974

I setup last version from GitHub - OpenViX/HRTunerProxy: Setup Enigma2 to act as HR-Tuner Proxy.
Result is the same.

Result for http://192.168.1.10:6084/discover.json (in russian):

1085×574 34.3 KB

Translate - “connection not establish”

enigma2 log attached (by instruction from http://wiki.blue-panel.com/index.php/Create_Enigma2_log_file).

Regards,
Siva.

can you supply log file from /tmp and a screen shot of your setup from plugin please.

Hi,

Plugin info:

347×255 89.1 KB

And log from /tmp

440

@“siva1@mail.ru” said:

@andyblac1974 said:

@“siva1@mail.ru” said:

@andyblac1974 said:

@“siva1@mail.ru” said:
Hi

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.

Hi andyblac1974

I setup last version from GitHub - OpenViX/HRTunerProxy: Setup Enigma2 to act as HR-Tuner Proxy.
Result is the same.

Result for http://192.168.1.10:6084/discover.json (in russian):

1085×574 34.3 KB

Translate - “connection not establish”

enigma2 log attached (by instruction from http://wiki.blue-panel.com/index.php/Create_Enigma2_log_file).

Regards,
Siva.

can you supply log file from /tmp and a screen shot of your setup from plugin please.

Hi,

Plugin info:

347×255 89.1 KB

And log from /tmp

unzip upload these, reboot, get me new log from tmp. thanks