#wake_on_lan.send_magic_packet requires configuration.yaml edit?

1 messages · Page 1 of 1 (latest)

ivory mist
#

Asked Gemini about this one (see screenshot) after getting the following error in an integration:

The automation "Turn On Work PC" (automation.turn_on_work_pc) has an unknown action: wake_on_lan.send_magic_packet.

What's annoying here is that I don't think this is possible to do via the UI. Is what Gemini slopped out here correct?

fervent horizon
#

that's an action in your automation

ivory mist
#

yes i know. but the point is, do i have to add a device in the wake on lan integration to use that action?

#

because in the action, i specify the mac address again. i don't select the device from the integration

fervent horizon
#

it's an action provided by that integration, so the integration needs to be loaded

ivory mist
#

and that requires i have EACH device i wish to wake as a device?

#

or do i just need one device to wake up the integration

fervent horizon
#

it's just an action, and you specify what you want to wake

#

if you want a switch or a button, you need to set up those up as described there

ivory mist
#

i have an action set up like so:

#

that device there is NOT set up in the integration, it doesn't need to be

#

because i have the mac address right in the action data

fervent horizon
#

excellent

ivory mist
#

...but that does not work. i get the error you see above.

#

because, according to the gemini answer, the integration is not activated. because i have no devices in the integration.

fervent horizon
#

you need to do the very first thing in the docs:

ivory mist
#

ok, so that answers the question i guess. enabling wake_on_lan requires either creating a dummy device in the integration UI, or directly editing configuration.yaml

#

otherwise the integration will be entirely disabled

ivory mist
#

alright, verified that adding a completely fake single device to the Wake on LAN integration lets all the actions work.

imo the integration needs a rework, either have devices that you trigger directly in automations, or have actions, but don't have both? i see no reason to have actions that don't function without a yaml change

tall lionBOT
#

If you have a feature request for Home Assistant you can open one here. Feature requests for custom cards, integrations, etc. should be made to the developer of that custom card/component.