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.

@ptarjan 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:

4 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.

6 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.

1 Like

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??

1 Like

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

When I tried this, it works to turn on the tvs but not to turn them off. Am I doing something wrong? Before there was a switch (on/off) now that’s gone.

I succeed to switch it off:

alias: "[SAMSUNG TV] SALON - Éteindre la TV"
description: "Éteint la TV via la commande standard media_player"
triggers:
  - trigger: state
    entity_id: media_player.samsung_xxxxxxxxxxxxxxxxxx
    from: "on"
    to: "off"
actions:
  - action: media_player.turn_off
    target:
      entity_id: media_player.samsung_xxxxxxxxxxxxxxxxxx

You're using the state of the media player turning off to set the state of the same media player to off?

I don't understand why you're doing this or what it fixes.

@ptarjan, Would you mind helping us understand why if the integration knows the MAC address it can't just take care of sending the packet without this automation to bridge the functionality?

samsungtv.turn_on is not an available action under Developer tools | Actions.

Is that indeed because of the same reason we're all here (it was also removed in 2025.6)? Is that automation trigger still working for you?

In the meantime, here's the automation I've configured for two Samsung TVs after first having to add both under the Wake on LAN integration so that I could even use the wake_on_lan.send_magic_packet action.

alias: Samsung TV Explicit Turn On
description: >-
  Explicitly turns on Samsung TVs when commanded
  (https://github.com/home-assistant/core/pull/158740)
triggers:
  - trigger: state
    id: Living Room TV turned On
    entity_id:
      - media_player.tv_living_room
    to:
      - "on"
  - trigger: state
    id: Master TV turned On
    entity_id:
      - media_player.tv_master
    to:
      - "on"
actions:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - Living Room TV turned On
        sequence:
          - action: wake_on_lan.send_magic_packet
            data:
              mac: 40:16:3b:59:##:##
      - conditions:
          - condition: trigger
            id:
              - Master TV turned On
        sequence:
          - action: wake_on_lan.send_magic_packet
            data:
              mac: cc:b1:1a:14:##:##

Yep, I saw/see that. My question stands based on what's actually (not) available in HA a/o today.

Yes it works fine. TV turns on and off with the media_player entity. samsungtv.turn_on is a trigger not an action

Ah, of course. Thanks. I’m not used to seeing integration specific triggers. I still wonder if the media_player going to on isn’t basically the same trigger though.

No idea but it's in the docs and it works great. LG TVs have the same as well