-
Notifications
You must be signed in to change notification settings - Fork 60
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
55PUS6754 (2019 model) Connection Refused #22
Comments
Problem still existing? According to some other websites TP-Vision accidentally broke the API earlier this year on some 2019 models. I‘m using one with an fresh firmware and http://up:1925/system AND https://ip:1926/6/system ARE working |
Same issue for me, only http://up:1925/system is responsive. I've got pus7304 |
Same here - pus7354 feels like @SchmuFoo is right and something got broken TV side. the whole firmware behaviour feels very very broken to me ( |
Mine freezes on "starting pairing requests" and then connection timed out. I have bought a new tv and can't add it to Homekit setup, and I've got a few automations based on tv. |
Same problems here (7354). |
So...after a few years I ended up buying a new TV, this time a Saphi based 6704 and the fancy pairing method has been removed from that - so this project is sort of redundant for these models. https as been removed and we're back on port 1925 unencrypted. It looks like it's a prefix of /6/ as well. For commands, a set of Basic auth credentials are created on the client which seems to have a username of 1 and a password which I've yet to decode how it's formed. However, it's constant across app launches so it's may well be reusable one you've captured it from the network traffic, which since it's http is a bit of a doddle! I'll see if I can figure out what goes into generating the password just to satisfy my own curiousity. Edit: Oh, this has made me laugh, the base64 version of the password is the "secret HMAC key". So the header needed for authentication for that TV range is here:
|
Thank you for the research and the header information. But can you please explain how we should do this to authenticate our TV? Should we modify the .py file? |
This project is redundant really for the Saphi range of TVs - the main point was to do the pairing for Android TVs so the credentials can be plugged into something else a little more user friendly/usable. The Saphi TVs allow unauthenticated access for the get functions, the credentials are only needed for actions. So, if you're using this project and want to connect it a Saphi based TV you'll need to make the following changes:
The post_command function should be replaced with this:
|
just a quick update: Philips 65PUS7354 2019 After firmware update 001.002.173.010 AND factory reset I finally managed to run the script properly and integrate my TV to the Homebridge service. So now I can at least enjoy the with on\off function from the HomeKit feels like the factory reset made the difference |
on my 2019 Ambilight, I'm not able to start a pairing connection.
On the Browser, I can access the JSON only on HTTP and 1925, but does not display a JSON when using HTTPS and 1926
I tried changing the code to http and 1925, but then the error changed to ("No JSON object could be decoded")
The text was updated successfully, but these errors were encountered: