Skip to content
This repository has been archived by the owner on May 17, 2021. It is now read-only.

[Panasonic TV Binding] Get 500 Error on TV Actions #5899

Open
volbrene opened this issue Sep 19, 2019 · 5 comments
Open

[Panasonic TV Binding] Get 500 Error on TV Actions #5899

volbrene opened this issue Sep 19, 2019 · 5 comments

Comments

@volbrene
Copy link

Hello,

i have a Problem with my new Panasonic 2019 TV. Openhab says:

2019-09-19 09:01:52.446 [WARN ] [asonictv.internal.PanasonicTVBinding] - Command POWER to TV with IP 192.168.178.69 failed with HTTP Reponse Code 500

I found the following issue on another Github project, which was fixed this issue: florianholzapfel/panasonic-viera#9

Apparently missing the request of a pin for the new Panasonic TVs Later 2019.

Is it possible to add this solution for the panasonic tv bindung in openhab?

@pk1
Copy link

pk1 commented Oct 8, 2019

Would be really great to see this working also for the latest Panasonic models!

@kfear27
Copy link

kfear27 commented Dec 10, 2019

Does anyone know if this will be rewritten for openhab 2.4+ ?

@gailta
Copy link

gailta commented Dec 12, 2019

it is - so far i understand - not a problem of openhab 2.4+.
It is much more a problem, that Panasonic TVs from 2019 and later have a different interface. I guess, with older Panasonic TV's, it still works also with the up to date OH.

@pk1
Copy link

pk1 commented Dec 12, 2019

Of course there is no real problem as the current Panasonic bindig works with older models but in the meantime more and more people will switch to a newer Panasonic model or people who previously had another TV brand might switch in the future to use one of the latest Panasonic models.

So from my point of view the Panasonic binding just needs an upgrade to support the new encrypted communication.

@gailta
Copy link

gailta commented Dec 12, 2019

of course.
I'm waiting too for an update.

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

No branches or pull requests

4 participants