"unique_id" field for Wake on Lan integration

Feature Requests
1

Hi! So I think it would be nice to have an unique_id field for the wake-on-lan integration. My use-case is that I have a dual-boot system that obviously shares the same MAC address but will be known by different hostnames and IP’s on the network, depending on which OS is running. Maybe I’m just lacking in creativity, but I was thinking of using the WOL integration for this, and just defining both installs with the same MAC but different hostnames/IP’s so I can see from my dashboard which OS happens to be running and take actions based on that. However, it looks like the integration relies on the MAC address for it’s integration ID, which obviously breaks here:

Platform wake_on_lan does not generate unique IDs. ID 00:11:22:33:44:55 already exists - ignoring switch.my_pc

It would be nice to be able to give this a distguishing name to work around this and allow me to have multiple WOL switches for the same physical system.

Thanks!

2

I do not get the use case!
If you can see which OS is running then there is no need to wake it up, so why do you need it.
Besides that WoL is based on MAC addresses, since a device that is turned off will have no IP address.

3

Hey Wally! I need the WOL integration to see which OS is running - the system has Windows and Linux installed on it, and depending on which OS is running it will have a different IP and hostname. The switch will toggle to “On” when the IP or hostname that’s configured for the WOL switch starts responding. So I could have two switches - one for each OS - and see which one is toggled “On” and know which OS is currently running.

4

WOL (with or without HA) just broadcast a small data packet to wake a MAC. It does not return any data, so it is impossible to tell what OS is running.

You could use the ping integration to see which is responding. On Windows, you will need to make a small adjustment to the firewall settings to have ping respond.

5

Ha! I didn’t actually realize there was a standalone ping integration. That would give me the visibility I’m describing, but there’s still the use-case and need of having unique power-off actions for each OS.

6

Create a commandline sensor. This will give the ip address of the device with the mac address specified

ip neigh|grep 00:09:b0:cc:1b:8b
7

I’m going to close this for the following reasons:

WoL is the wrong choice for your use case.

WoL is hardware based. You want something to detect a software instance.

There are many, many ways of determining if a Linux or Windows system is running. Search the forum and documentation or open a configuration topic if you need help with this.

1 Like