So I did the recent Core/OS update to 2025.11.1 and 16.3. I just noticed yesterday that the LG WebOS integration is now acting up, becoming unavailable the moment I turn off my TV. Not the biggest deal since I still use IR to turn on my TV, after which the integration becomes available again. I don’t see anything in the debug, and not that I’ve changed on my firewall as of late (pfsense), but there’s also nothing there.
Considering restoring a backup, but I do like to stay up to date, and also hate losing data, so might just live with it. Just asking to see if I’m the only one affected.
Activity
November 14, 2025
became unavailable
4:11:23 PM - 9 seconds ago
turned off
4:11:11 PM - 21 seconds ago
became unavailable
4:10:57 PM - 35 seconds ago
turned off
4:10:45 PM - 1 minute ago
became unavailable
4:02:17 PM - 9 minutes ago
turned off
4:02:05 PM - 9 minutes ago
became unavailable
2:09:27 PM - 2 hours ago
turned off triggered by action Media player: Turn off
Was a little confused on the automation, but figured it out. It’s documented on the integration page.
## Turn on automation trigger
To turn on your TV, you need to create an automation. You can create an automation from the user interface. From the device, create a new automation and select the Device is requested to turn on trigger.
Actually looks better now since I was using a dedicated button to trigger a script, and now the script is integrated with the media_player entity.
Hello, everyone! Thank you very much for your messages. I had the same problem, and even though I had read the release notes carefully, I didn’t understand what to do!
For my part, I just added the following automation:
- id: 'xxxxxxxxxx'
alias: Salon - Allumer la télé du salon
description: ''
triggers:
- device_id: xxxxxxxxxx
domain: webostv
type: webostv.turn_on
metadata: {}
trigger: device
conditions: []
actions: []
mode: single
I have an automation that turns my powered speakers on and off together with the TV. The speakers are supposed to turn off when the TV is off for 1 minute.
I’m glad I’m reading this thread because this change broke my automation and I didn’t notice my speakers weren’t turning off the past 2,5 weeks.
I think this is the crux of the matter. I have automations that occur when the TV is turned off and these no longer work for what seems to be an unrelated reason. It shouldn’t matter that the TV is made unavailable, but that seems to cancel out any action set to occur after the TV is turned off.
Through testing, I found that actions will occur normally as long as they are made to happen before the TV becomes unavailable (usually about 10 seconds). Anything set to happen after that, won’t. I don’t think creating another automation just so that my lights can turn off 10 mins after my TV is the way to go forward. Nor am I able to use the “TV became unavailable” as a trigger. However I’m not sure if this is a HA quirk or an integration quirk.
