Samsung Implicit Wake on LAN Deprecation

I read the linked info and the actual change here:

I think I’m just supposed to create an automation that uses the same media_player trigger to explicitly send the magic packet.

Why is it necessary for the user to add a one off automation for something that should be handled by the integration? Can’t the Samsung and/or media_player integration just do this explicitly? I guess I’m just missing why this was good for so long and is now suddenly an issue. Imagine if we had to create automations for the functionality of all controllable entities throughout HA. :man_facepalming:t2:

3 Likes

I agree: why deprecate the WoL default action? What is the underlying reason? It seems to just make things less user-friendly?

Also, the message (and documentation) could be more informative. What more precisely are we supposed to do? Adding an explicit example to the WoL documentation would be more helpful.

3 Likes

Nowadays when I say “Alexa, turn on the Living room” it turns on the A/C, Lights and TV. I like this behavior and would like to keep it as it is.

After installing 2026.02 udpate, when I say that same phrase, this deprecation warning start appearing.

I read the notes (including provided PR) but I don’t understand what should I change/add to keep having the same.

Any help on this is more than welcome.

My Samsung TV listens to “turn on” and “turn off”.
Will the update kill both commands?!?
how am I supposed to create a “turn off” automation or script?
why I this even changing??

Add this automation. Don’t know why it’s needed but it was a requirement for LG a while ago too. This automation allows the media player entity to work as normal

alias: Turn On Living Room TV with WakeOnLan
triggers:
  - trigger: samsungtv.turn_on
    entity_id: media_player.living_room_tv
actions:
  - action: wake_on_lan.send_magic_packet
    data:
      mac: xx:xx:xx:xx:xx:xx

I am so confused… Can someone please tell me what the proper way to tell home assistant to turn on and off my Samsung TV is (lol)?

I’ve been using media_player.turn_on against media_player.living_room_tv (which has been flakey as all hell for me for at least 6 months).

Am I supposed to continue using that, but just throw in the wake_on_lan automation from the docs (aka what @Holdestmade pasted above) and basically forget it exists?

Am I supposed to be using the remote.living_room_tv switch?

I don’t know where the issue lies, but damn I’ve had the most frustrating experience automating this TV reliably: TV turns on when it should be turning off, turning off when it should be turning on. Media player reporting that TV is on when TV is powered down. Media player not responding to turn_on requests. Would LOVE to discover that I’m doing something wrong.

Yes, that’s it

1 Like