Wake on LAN

[Aftergit]

The problem

This issue occurs after upgrading to Release 2024.5.4

When my kodi media system is going into hibernate it will restart and does not stay in hibernate state, if i disable wake on lan in configuration.yaml it stays also into hybernate state, if i poweroff home assistant it will stay in hibernate state as well.

What version of Home Assistant Core has the issue?

core-2024.5.4

What was the last working version of Home Assistant Core?

2024.5.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Wake on LAN

Link to integration documentation on our website

https://www.home-assistant.io/integrations/wake_on_lan/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No changes is made on Kodi system this happend after the upgrade.

[home-assistant]

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

Code owner commands

Code owners of wake_on_lan 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 wake_on_lan 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)}}

---

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

[joostlek]

When reading this issue I have no clue how you are using wake on lan, what you are expecting and what is happening

[Aftergit]

Sorry i will be more specific, i run a script with Kodi: Call method System.Hibernate and the system goes into hibernate but it boots up direct after again, this worked perfectly before. If i disable the wake on lan in my configuration.yaml or shutdown home assistant and manually put the system into hibernate via kodi powermenu it will not reboot but stay in hibernate state.

[joostlek]

the Wake on Lan integration isn't waking up random devices, that is probably caused by an automation that is doing that

[Aftergit]

If that is the case why did that not happen in the previous version?

[joostlek]

No clue, I can tell you a lot, but nothing happened in the change between those 2 versions to Wake on lan.

[Aftergit]

I'm lost of words, tnx

[ntilley905]

There is one configuration quirk that could cause this but it shouldn't have changed between versions as the WOL source code has not changed.

With that being said, without having posted your YAML configuration I can't see if it's caused by what I think it is.

If you define the WoL integration with a host (generally the IP address of the device you want to wake), it will periodically ping that device to see if it is online or not. A ping shouldn't keep a device from hibernating in a normal scenario, but I guess it is theoretically possible.

Going outside of the purpose of GitHub here (as this is not a support channel but rather a channel to report bugs, which this would not be) but try removing the host and only define it using a MAC address and see jf that solves the problem.

[Aftergit]

@ntilley905 thanks for your input it is a standard config in the configuration.yaml and i tried what you said that but did not solve the problem, i will revert to previous version tomorrow and will update it here. the only thing i did was before it did not work was upgrade to Release 2024.5.4

switch:

• platform: wake_on_lan
  mac: removed
  name: Wake
  host: 192.168.178.75

Thank you.

[ntilley905]

If that didn't resolve the problem then there's nothing I'm aware of in the component that would cause the behavior, and like @joostlek said, nothing in the behavior of the component changed between versions.

[Aftergit]

NP, thanks for the input.

[Aftergit]

Restored backup to previous version solved the issue, after reinstalling Release 2024.5.4 it did not occurred again probably something did not install correctly causing the issue.