Using WakeOnLan with Opnsense and HomeAssistant #22
Replies: 4 comments 2 replies
-
Hi Excellent bit of information. It might be handy to include information about how to authorise properly. The usename should be the key=string from the file downloaded when creating the API key. That's all!. Thanks for the article! |
Beta Was this translation helpful? Give feedback.
-
Why not just the Home Assistant built in WOL integration? |
Beta Was this translation helpful? Give feedback.
-
Thank you so much! |
Beta Was this translation helpful? Give feedback.
-
Thanks for the write-up! I also had to set curl -k https://OPNSENSE_URL/api/wol/wol/set \
-u "OPNSENSE_KEY":"OPNSENSE_SECRET" \
-H "Content-Type: application/json" \
-d '{"wake":{"interface": "INTERFACE","mac": "DEVICE_MAC"}}' OPNsense will respond with: For completeness, here’s the rest_command:
wake_device:
url: 'https://OPNSENSE_URL/api/wol/wol/set'
method: POST
payload: '{"wake":{"interface": "INTERFACE","mac": "DEVICE_MAC"}}'
content_type: 'application/json'
username: !secret opnsense_user
password: !secret opnsense_key
verify_ssl: false I just realized after writing this, that you already mention the |
Beta Was this translation helpful? Give feedback.
-
Using WakeOnLan with Opnsense and HomeAssistant
Note: Significant hat tip here to /u/abstractbarista for this guide. Most of the steps below come from their guide. The main differences being 1) little bit improved layout/format (subjective) and 2) I figured out how to do a call to just wake a single device.
Introduction WakeOnLAN is one of those things that you love to hate. When it works, it’s magical. When it doesn’t it’s beyond frustrating. My biggest annoyance is with my network setup, I have multiple VLANs/subnets, and WOL doesn’t really like to be routed across subnets for reasons I only barely understand so I’m not going to try to explain.
https://blog.fuzzymistborn.com/opnsense-wol/
Beta Was this translation helpful? Give feedback.
All reactions