-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
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
Philips TV goes to Off status #88264
Comments
Hey there @elupus, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) philips_js documentation |
It could be going into sleep on the network i suppose. How long does it stay on? |
TV is working, in touch, ping is on. I can get information as above. But in HA it is off. |
The TV is in the status on for a couple of minutes, that's all. The log above and the screenshot of the story confirm this. |
Can you please post debug info file that you can get from the integration config entry screen. |
~13:33 - I turn On TV |
After i turn off TV in log:
|
I have the same issue, the tv worked just fine for a few days. Did you fixed it? |
No :( |
Do you guys have "Use events.." setting turned on in integration options for the config entry of philips? @andrewjswan those logs are not from the philips intehration. Looks to be from the androidrv one. Are you using both? |
Yes, Use event used... @elupus |
@andrewjswan can you try turning that event feature off to test if problem persists. Also disable the android integration and dlna (if enabled) temporarily. |
I unplug and plug again the TV but with HA turned off and the tv responds again to its Ip:1925/system. When I turn on the HA, the TV turns off on network, maybe a script/command puts the TV into sleep on network. I'm gonna reinstall HA because i do not have too much things |
I tried, the same thing, but you can’t turn off the TV yet, there is no button. |
If you can't reach the /system endpoint the TV has crashed/locked up. You can try and restarting HA att that point. And see if it recovers temporarily. Maybe there is some http connection leak in HA that has cropped up. |
At the time of turning off the essence in, I tried to go to the address http://ip_address_of_tv:1925/system, the answer from TV was. I tried to monitor this answer at the time of the transition, as well as the answer from TV was always. |
If I make a HA restart, then TV does not always receive the status in HA, but if you turn off the TV and turn it on, then if my memory does not fail me, it turns on. |
2023.05 - No change, everything is the same. |
I enabled the following option in the TV settings: “Turn on with Wi-Fi”, which is supposed to keep the TV online while standby. Checking my network with HA shows that the TV is at least always connected to the Wi-Fi network as intended. However, after usually a couple of seconds, the TV becomes unavailable as a media player, so turning on is not possible. |
You likely need to have some wakelock app for your tv. You see in your log that adb also disconnects. |
I switch TV from WiFi to Lan, the some... ADB work, but TV mediaplayer turn off after some minutes... |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
2023.8 the some |
2023.8.4 same problem here. TV goes on if i switch on through HA but after a few minutes, in HA the TV appears as off. Static ip, ping ok |
I did several test and I found my specific problem. Isn't a integration problem but an IP's problem that I can't understand but i solved it with a workaround. Previously my philips tv was set to static IP and as i wrote before, the ip was correct ! Ping ok... At first switch on the tv mantain the ip... after switch it to off, the tv maintain the IP... From the second switch on the problem appears: the ping stops to respond to the static ip setted and tv get an ip from DHCP server! So the static ip configuration on tv doesn't work good, i solved setting up an static lease on my router for the tv's mac address. However it is possible to add a configuration menu for the integration that permits to change device's ip? |
My IP does not change, if it changed, then Google TV did not work on this TV, but it works. And when you start the TV for a few minutes Online in HA then goes offline. But it is on the lan. |
Just a follow up.... |
Another follow up... If you want to test: Please report back. |
Does the integration out of the box use this library? Or do I need to reconfigure the TV in the HA? |
It uses the library out of the box. No need to reconfigure the TV |
or
? |
/config/haphilipsjs |
Eh. This wont have any effect at all |
You can add a dummy Log entry in async def getReq function to be sure its using the right library You might have to reboot your TV if the JointSpace server has crashed |
Weirdness. I need to check that internally with the team. That should not work. |
Does it kill you server on the TV or does it reconnect again without rebooting your TV? |
And is "Allow notification service" on? |
So.. Yes it does work. But please place them in a deps/ subfolder of your config directory instead, which should work too. Getting them from root of config will go away if i figure out how. |
I haven’t seen any reboots, but the status is still incorrect, the TV is working, but the status is Off (you can see it from the Android TV line installed on the same TV).
Off
What does it mean it kills? It is not safe?
Those. wait for the integration update? Should I remove |
@andrewjswan @elupus I have had the integration running 3 weeks now without any reboot on the TV only changing Before: After HA release 2024.2 you need to have haphilipsjs folder in the /config/deps/ folder if you want to test with your own TV's |
They are keyword parameters, so order does not matter. The change you seem to have made is to allow keep alive. It could be beneficial in some cases IF the server supports it. Ie it would reduce connection load. My old (pre-android) TV's crashed hard with that enabled. I don't own that TV anymore sadly. If you turn up debug logging on the httpx and httpcore i think you should get logs on reuses of connections. Please verify that you are actually getting re-uses. I'm mostly fine with enabling keep alive, feel free to provide a patch for the lib to enable that. I think you could allow passing in a limits argument to the constructor. Then it's easier to tune this. |
@elupus I noticed some weird behavior with httpx. It does NOT respect the max_connections if max keepalive connections is 0 I have no clue why I get more that 3 connections and I sadly does not have the time to debug more at the moment.... |
@Sdahl1234 That is a very interesting find! Maybe we expose a bug in httpx here. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Still relevant |
I still get this , unavailable when powered on , off when powered off |
You are of 2024.5.5 release? If so please turn on debug for the integration and reproduce issue. Then turn off and post log here |
Core 2024.5.5 Added file here if that works? |
The problem
I turn on the TV (connected via Lan, the address is static), the media player in HA turns on, and after a while it turns off.
Turned on the debugging in the log, I do not see anything special.
But in the previous log there were warnings.
What version of Home Assistant Core has the issue?
core-2023.2.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Philips TV
Link to integration documentation on our website
https://www.home-assistant.io/integrations/philips_js/
Diagnostics information
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
The text was updated successfully, but these errors were encountered: