Philips TV integration loses connection to TV

[fredbcode]

The problem

With a home assistant fresh install in docker I have exactly the same issue that #57093 It works a while, and after a moment the tv is always disconnected

Of course my tv respond to 1925 with api 6 in a browser

I'm not sure, but I think that it happens when the tv is off a moment

Re-installed the Philips integration then it works a while, restart is without effect

TV 50PUS7304/12 Micrologiciel : TPM191E_R.211.000.088.000

What version of Home Assistant Core has the issue?

core-2025.4.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Philips TV

Link to integration documentation on our website

No response

Diagnostics information

System Information

version	core-2025.4.4
installation_type	Home Assistant Container
dev	false
hassio	false
docker	true
user	root
virtualenv	false
python_version	3.13.2
os_name	Linux
os_version	6.8.0-59-generic
arch	x86_64
timezone	Europe/Paris
config_dir	/config

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Dashboards

dashboards	2
resources	0
views	0
mode	storage

Network Configuration

adapters	lo (disabled), eth0 (enabled, default, auto)
ipv4_addresses	lo (127.0.0.1/8), eth0 (172.16.3.7/24)
ipv6_addresses	lo (::1/128), eth0 ()
announce_addresses	172.16.3.7

Recorder

oldest_recorder_run	2 mai 2025 à 08:29
current_recorder_run	7 mai 2025 à 18:10
estimated_db_size	20.75 MiB
database_engine	sqlite
database_version	3.48.0

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant[bot]]

Hey there @elupus, mind taking a look at this issue as it has been labeled with an integration (philips_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of philips_js can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign philips_js Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

philips_js documentation philips_js source _{^{(message by IssueLinks)}}

[sejrusak]

I have the same issue

[ultimate-tester]

Same issue here. Keep in mind that if your TV is connected over WLAN you can - depending on model - benefit from WoWLAN, which will prevent the deep sleep from happening. For folks using cable, like myself, the connection is gone after it enters deep sleep.

Speaking for myself here: a solution would be to just stop trying to connect anymore and not display an "Unavailable" state on the dashboard. It will always recover anyways once the TV is turned on again.

[fredbcode]

It will always recover anyways once the TV is turned on again.

Not in my case, tv still unavailable in ha

[ultimate-tester]

It will always recover anyways once the TV is turned on again.

Not in my case, tv still unavailable in ha

Is your TV receiving the same IP every time? If not, try to instruct your router to provide the same IP to your TV. This usually goes based on MAC address.

It does mean I misunderstood the issue, I thought it would only show this issue when offline for a longer time but recover always

[elupus]

Check if physically unplugging the tv and waiting the restoring power makes it work again. The tvs are notoriously crashprone with this interface.

[fredbcode]

Yes ip fixed

What I'm saying, the tv doesn't respond to packets 1926 (reset packet) So I thought it's a tv issue, but if I remove/reinstall the plugin it works again, weird

Someone can also make a trace with tcpdump ?

[elupus]

Sound almost like we are leaking connections. So we block all available slots on the TV. Usually the "use events" option on the integration configuration that has caused such issues in the past. But its odd if it releases on an integration reload.

[fredbcode]

Yes unplug tv works or waiting a very long time, something like one day

[coinzz]

Hey, I had the same issue and indeed it was caused because I did not use a static IP for my TV. I changed to a static IP now and didn't want to configure the whole integration on the new IP, because then you need to reconfigure all integrations as well. Instead you can change the IP (host field) of the philips_js integration here /config/.storage/core.config_entries. Take a backup before and check if home assistant still can load the configs. After that do a full restart of home assistant and everything worked as expected again 🙂

[elupus]

With some luck this will no longer be an issue on next release since we will follow announcement from the TV on its IP.

[D4n1el89]

Hello, I have the same problem for a few days now. I think it's since the Core update 2025.8.2. All TV entities become unavailable every 2-3 minutes. I've had the integration for 2 years without reconfiguration. I'm using static IP for TV and it's conected via LAN. I am also attaching the Config_entry.

config_entry-philips_js-813fedbe156abb1f39c21192fd3eb450.json

[elupus]

Can you post debug info when its available and when not. Also turn on debug logs and turn off once issue has been reproduced and post file.

[D4n1el89]

error_log-3.txt

here is it: 19:08:31 was turn on 19:09:01 was unavailable 19:09:31 was on

[elupus]

Strange. I don't think this is related to issue here. For some reason the request for HueLamp/power fails in your log. But only sometimes. Annoyingly it does not indicate why it failed.

[D4n1el89]

Hmm, strange. Okay thanks for checking the log. I'll try checking the TV settings or if there's a new firmware available. Reconfiguring the integration in HA didn't help. Thanks again

[indevor]

home-assistant_philips_js_2025-09-07T22-07-22.694Z.log config_entry-philips_js-01K4E5MEDBX27FFBG81YWEQ408.json

same problem All TV entities become unavailable every 2-3 minutes.

Core 2025.7.1 Supervisor 2025.08.3 Operating System 16.1

65OLED807/12 Philips FW: TPM211EA_R.101.001.005.111

https://192.168.1.131:1926/system {"notifyChange":"http","menulanguage":"Russian","name":"65OLED807/12","country":"Russia","serialnumber_encrypted":"nmpKUXnjVshkYIw78FkrKxkhDQl7o7OJDqIS5LegyRQ=\n","softwareversion_encrypted":"b9KDvipmwrXkrc/q6kE9T5YwkLxswuAcczMaQlw3afEhf1Gex5BX+t6lSxrOdo5m\n","model_encrypted":"4B66dAUgmzBNpQc/J73Ro9saV2YAWsTF6ED+zmse3cg=\n","deviceid_encrypted":"IZNSLc89X8GyXhGCX07pNgu2KCG9wGdfZ+NKBR9VMbA=\n","nettvversion":"10.0.0","epgsource":"no_epg","api_version":{"Major":6,"Minor":1,"Patch":0},"featuring":{"jsonfeatures":{"editfavorites":["TVChannels","SatChannels"],"recordings":["List","Schedule","Manage"],"ambilight":["LoungeLight","Hue","Ambilight","HueStreaming"],"menuitems":["Setup_Menu"],"textentry":["not_available"],"applications":["TV_Apps","TV_Games","TV_Settings"],"pointer":["not_available"],"inputkey":["key"],"activities":["intent"],"channels":["preset_string"],"mappings":["server_mapping"],"aurora":["available"]},"systemfeatures":{"tvtype":"consumer","content":["dmr","pvr"],"tvsearch":"intent","pairing_type":"digest_auth_pairing","secured_transport":"true","companion_screen":"true"}},"os_type":"MSAF_2019_P"}

When refreshing pages in the browser, the data changes correctly until the moment when entities disappear in HA. After the entities disappear and appear after 30 seconds, the page continues to refresh.

[lxnoid]

that pretty much is also the observation with my setup - TV is using static IP and loses the entity status. The setup/automation based on this was working for months and started to fail recently