#Weird acting automation with WOL

1 messages · Page 1 of 1 (latest)

quick sand
#

How can i debug an issue where starting PC1, it always starts PC2 too with WOL

#

I have a setup where i can start PC1 and/or with PC2

#

But somehow my PC1 keeps starting the PC2. How to debug this?

bronze gull
#

step through the automation using the trace and see whats being executed at each step.
can you share your automation yaml?

quick sand
#

Sure i can

#

For me, there should NOT be any automations that wake up another PC

bronze gull
#

i assumed you were using an automation for it because your in the "automations" support section. how are you calling the WOL?

quick sand
#

Well something is automating it, i just dont know what :D

#

I have two options to call the WOL

#

first is an homekit command, a switch to call these two switches:

switch:

  • platform: wake_on_lan
    name: "timon kone"
    mac: 9c:6b:00:80:3f:3f
  • platform: wake_on_lan
    name: "iidan kone"
    mac: 9c:6b:00:5c:bd:95
#

Then an automation just turns the switches off for cosmetics. since there is no real data if the pc is or or off

#

But many times when i just start the PC1 manually fromt he power button, the PC2 wakes up too

#

and i've tried that if my HA is offline, it does not happen

#

so some weird way, the HA keeps starting PC2 when PC1 starts

bronze gull
#

could you use a "button" instead of a "switch" instead of having to set and reset? then you call a "button press". not sure if that would help or not but seems a better way to do it

quick sand
#

In the future i am about to add function to the switch. Either have it show real data or make it shut down pc fromt hat

#

At th moment both of the switches show Off state

#

and haven't changed state for hours

bronze gull
#

i think wol is being sent when the switches reset as it looks like your triggering on any switch action and not just the turn_on action. so it ends up triggering both on resets.

i would suggest that using a switch is not a great way of doing what your doing.

i suggest having a sensor for current state (when you have that data)
a wake on lan button (or script)
a shutdown button (or script)

then there is no overlap between functions

quick sand
#

Can i somehow verify this from logs, that what did activate the call for switches?