#LG webOS TV integration after updating to 2025.11 and 16.3

1 messages · Page 1 of 1 (latest)

dapper flax
#

Power ON does not work anymore, my test HA installation I set up to 2025.10.2 and 16.2 and it still works. To be more specific: HACS remote https://github.com/madmicio/LG-WebOS-Remote-Control/tree/2.0.3 works on old installation, does not work on new version.
On both I have Wake on Lan integration that targets LG TV that is connected wia Ethernet

GitHub
GitHub - madmicio/LG-WebOS-Remote-Control at 2.0.3

Remote Control for LG TV WebOS. Contribute to madmicio/LG-WebOS-Remote-Control development by creating an account on GitHub.

dapper flax
#

Something in 2025.11 causing media.player_webos to have status unavailable while 2025.10.2 shows for the same player off. This change is preventing option to turn on LG TV.

lean blaze
#

well yes, that was mentioned in the release notes...

#

as a breaking change

dapper flax
#

@lean blaze thanks, I read LG webOS TV integration and saw about automation but there its stated there is an action: webostv.turn_on but I could not find that action to create automation, so that is why I used lovelace card, that seemed to do just that. Your second link explains that it is wrong in docs and that we need to use: Device requested to turn on and when I made that automation, lovelace is working again

hard turret
#

But If I turn it off (via OEM remote or even HA), then it "became unavailable" shortly after. Is this a configuration issue on my end?

dapper flax
#

@hard turret braking change in HA 2025.11
Add this to your automations, change device id and mac to your device

alias: Fox webOS TV turn on
description: Turn On Living Room TV with WakeOnLan
triggers:
  - device_id: d1d603cdfb0b2cecef35c085920de60a
    domain: webostv
    type: webostv.turn_on
    trigger: device
conditions: []
actions:
  - action: wake_on_lan.send_magic_packet
    metadata: {}
    data:
      broadcast_port: 9
      mac: 74:c1:7e:45:7d:89
mode: single
#

it will revert to old behavior and when off will show off instead of unavailable

hard turret
#

it says unknown device for me?

#

ohh im using entity ID

#

where do I get the device ID (im literally less than an hour into HA)

dapper flax
#

can't be done by entity, must be device, since there is no webostv.turn_on for entity

hard turret
#

cant seem to find device ID lmao

#

@dapper flax is device ID something I get from the TV or HA interface?

dapper flax
#

sec

hard turret
#

ah got it

#

made a dummy automation, edited it in YAML and got it that way

dapper flax
#

yes, you can copy and than switch to UI

hard turret
#

send_magic_packet is from where? Is that a plugin or something I need to install?

dapper flax
#

only requirement is to have in configuration yaml one line
wake_on_lan:

add this below "default_config:"

hard turret
dapper flax
#

global one called configuration.yaml, but if you are just starting, go with integration

hard turret
#

I'm not a noob to homelab stuff, just a newbie to this... i've got it in a docker, where the hell is configuration.yaml found 😭

dapper flax
#

don't know docker instalation, but should be config folder I think

#

You chose difficult path for Home Assistant

hard turret
#

Docker is meant to be easier, no? 🤣

dapper flax
#

I don't think so, for me its much better VM or on bare metal HAOS, since all addons are easily configured from HA itself, but maybe I am wrong

#

I did VM on Proxmox for my setup and never regretted

hard turret
#

Fairs

hard turret
#

this definitely doesnt look right lmao

image.png
dapper flax
#

remove spaces before wake_on_lan:

#

restart

#

yaml is all about spacing 🙂

hard turret
#

ayy got it

#

you a legend

dapper flax
#

problem is that all addons for HAOS are dockers, so you will need to set all of them as separate dockers, but if you use HAOS as bare metal installation or some sort of virtualization like Proxmox, HAOS will load any addon as docker and connect to it, all by itself

hard turret
#

I don't even see Addons

dapper flax
#

yep, you can't add docker under docker

hard turret
#

ohh I see

#

I mean I cant even see why I'd need addons

dapper flax
hard turret
#

I'm just using it purely to bridge non-homekit stuff into homekit

dapper flax
#

and you will need a lot of them eventually

image.png
#

you will ditch homekit, really fast

#

🙂

#

you will go other way around, you will look integrations to put homekit in HA

hard turret
#

Reason I'm checking this out, is because someone said you can have homekit <--> homeassistant compatibility - is that true?

Like can I "import" whats already on homekit into HA?

dapper flax
#

don't have homekit, can't tell

#

but, I think I read that it can be done

hard turret
#

Cos my problem is, this is a VPS, not a home-lab. so I'm using TAP VPN to allow homebridge/homeassistant to "see" my network

#

so I dont think I can actually add these devices natively/directly into HomeAssistant due to the lack of it physically being in my house

dapper flax
#

can't help there, sorry

#

this is what I see as possible integrations for HA, search for them and check

image.png
hard turret
#

damn it

#

HA Tuya integration doesnt support Smart IR relays

dapper flax
#

there are couple HACS Tuya integrations, that you can check

#

did restart fixed automation?

hard turret
dapper flax
hard turret
#

I'm deciding on whether or not I wanna try to move them all into HA natively. I only have a few devices actually in HomeKit natively (only Meross smart switches)

#

its just idk cos then I lose the ability to have location-based events, right?

#

or actually I've heard theres a HomeAssistant app, im guessing that can trigger location-related shit

dapper flax
dapper flax
#

but before all that, decide if you really want to go docker way with HA, much more complicated that it needs to be and not many people that actually can help you troubleshoot

safe mortar
#

hi can i get some help setting up a new LG G5 Evo TV? I had my last LG C10 TV connected with Home Assistant

safe mortar