Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version 4.0 don't work with Plex #35

Open
LA9SHA opened this issue Oct 3, 2018 · 15 comments
Open

Version 4.0 don't work with Plex #35

LA9SHA opened this issue Oct 3, 2018 · 15 comments

Comments

@LA9SHA
Copy link

LA9SHA commented Oct 3, 2018

You have information in plugin that it works with Plex and Emby media servers.

Latest HRTunerProxy 4.0 don't work with Plex (people say older worsions works). I have testet that version 4.0 works with Emby Media server on Windows 8.

My STB's are VU+ Duo2 and Solo2 both with OpenPLi 6.2.

I have testet HRTunerProxy with Plex on Windows 10 and on CentOS 7 (Plex version 1.13.8.5395) but only got: "Playback Error Unable to tune channel"

Can you please do a compability check and fix for support of latest Plex version?

@Huevos
Copy link
Contributor

Huevos commented Oct 3, 2018

If it works in Emby and doesn't in Plex that would probably be because Plex is no longer using their HDHR API.

If that is the case I can't see how this plugin can support Plex any longer without a major rewrite. And without some sort of assurance that Plex is not going to make yet more undocumented changes it is unlikely this will get dealt with at any time in the near future as we are just a small team of unpaid voluntary individuals that don't have the time or resources to discover how Plex now works through reverse engineering.

@LA9SHA
Copy link
Author

LA9SHA commented Oct 3, 2018

OK.

Find this by Google search:
https://community.getchannels.com/t/channels-with-hrtunerproxy/3841/4
"The HDHomeRun implements multiple APIs. There is a UDP discovery API on port 65001, a TCP control API on port 65001, an HTTP api on port 80, and another HTTP api on port 5004 for streaming video. The Channels app expects all four of these to be implemented, but that proxy only implements the HTTP port 80 API."

It may be old "news" for you.....

@Huevos
Copy link
Contributor

Huevos commented Oct 3, 2018

That was from 20 months ago. The current plugin is completely different.

@LA9SHA
Copy link
Author

LA9SHA commented Oct 6, 2018

Response from Plex:

"HRTunerProxy folks can contact us using “partners” option on our contact form if they would like. I make no promises about anything."

https://forums.plex.tv/t/hrtunerproxy-4-0-plex-will-not-tune/312657/12

@LA9SHA
Copy link
Author

LA9SHA commented Oct 27, 2018

Will it be a chance that you contact the Plex team for information so you can get HRTunerProxy to work with Plex again?

@Huevos
Copy link
Contributor

Huevos commented Oct 27, 2018

Please ask Plex to fix. We haven't changed anything.

@SaulGoodman1337
Copy link

Please ask Plex to fix. We haven't changed anything.

That was the best answer you could give. Not ;)

@Huevos
Copy link
Contributor

Huevos commented Jan 3, 2019

We are not in control of Plex closed source code.

@PiGeonCZ
Copy link

PiGeonCZ commented Jan 8, 2019

Hi Huevos,
Yes you are right they have obviously changed something on their side, but isn't this plugin the "follower" here?
Can you please think about it once more, and eventually use their form to contact them and setup a partnership?
There is really something wrong going on.
I had to reinstall my dreambox recently and now I am unable to add my dreambox via the DVR configuration not even manually.
I have the last version of HRtunerProxy and of plex server too (Version 1.14.1.5488).
thanks
PiGeon

@Huevos
Copy link
Contributor

Huevos commented Jan 8, 2019

Sorry, we are not the "followers" of cryptic messages, or going to waste time trying to reverse engineer changes in closed source code. You are welcome to fix it yourself and send a pull request.

@SaulGoodman1337
Copy link

is a bold statement for a plugin that was once called PlexAPI ;)

@rickardrockard
Copy link

rickardrockard commented Jan 10, 2019

Since you haven't payed for, or contributed code to this project, I think the only bold, and rude statements are coming from you. I haven't tried upgrading HRTunerProxy to version 4 yet, I'm still on 3.4, but it works without a problem with the latest version (1.14.1.5488) of Plex as of this writing. And if you read the links posted by OP you will see that the problems were resolved and were not caused by HRTunerProxy or Plex, but by unsupported format in their xmltv.xml.

@fridayshoes
Copy link

Version 4.0 still working fine with Plex 1.13.4.5271 for me

@PiGeonCZ
Copy link

@Huevos
Nobody certainly wanted anybody to waste time and try to reverse engineer something. I have actually meant to do the opposite, to contact them and eventually get the access to what is necessary.

If I were a developer I would contact them, but I'm not :(

@dragoshenron
Copy link

Really old issue, but I would to witness that HRTunerProxy4.0 and Plex Version 1.16.1.1291 are working like a charm. The only thing - as many already said in forums - that you need to specify IP and PORT manually as the autodiscover of Plex doesn't work (a minor bug).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants