WoL from DuckDNS Domain?

Configuration
1

I have been fighting like mad to try to get WoL to work with Home Assistant and I think I figured it out. My home assistant is configured with DuckDNS which seems to be preventing local access, thus preventing the WoL from working. I am able to WoL my computer with my TV running moonlight, but my switch on home assistant does not work.

Can someone help me configure my pc/router/HA to be able to work? Unfortunately I have to use the DuckDNS so that I can use my Alexa to control my home assistant.

2

I doubt that. Go to https://ha_ip_address:8123 you will have to add a security exception in your browser as the ssl cert is for the duckdns domain, not the ip address. But you should still be able to connect.

Try pinging the device you want to wake from the console in HA, if that works WoL should too.

Share your WoL config.

3

I can do that on my PC, but I cannot do that on my phone using the home assistant app. It is making me login using the DuckDNS domain.

4

The app has nothing to do with it.

Your Home Assistant server is the device that needs to be able to contact the device to wake. Test this:

5

Has the end device been configured to accept the magic packet? Many devices need this enabled as it is disabled by default.

6

Yes I can ping it. This is the switch config:

switch:

  • platform: wake_on_lan
    mac: 04:7c:16:51:e5:0e
    name: “Mark’s PC”
    host: 192.168.1.3
    broadcast_address: 192.168.1.3
    broadcast_port: 9
    turn_off:
    service: hassio.addon_stdin
    data:
    addon: core_rpc_shutdown
    input: pc
7

I have enabled every single WoL thing under the sun on my PC. I can WoL using my android TV but not my HA

8

Had this above it as well, forgot to put it in:

wake_on_lan:

9

this is my switch configuration.

- platform: wake_on_lan
  name: Kitchen Kiosk Wake with Lan
  mac: 00:4E:01:BB:9F:5E  # This is the MAC of my kiosk network card

I then call a service in an automation each morning to “turn on” this switch.

service: switch.turn_on
data: {}
target:
  entity_id: switch.wake_on_lan
10

That broadcast address is wrong.
Typically it would be 192.168.1.255 for a 192168.1.0 network with a mask of /24.
No idea what broadcast_port is, since a broadcast should go on out on all ports.

And the destination device of the magic packet must support the technology and have the feature enabled in its firmware/BIOS.
Remember that the magic packet often only can be received on a wired connect on the destination device.

11

Okay so I can get it to work directly after shutting the PC off (using my current config) but the NIC doesn’t stay powered long after shutdown so after that I can no longer use WoL. I check my router’s device list and the PC disappears after a while after shutdown. I have enabled wake by pci-e device in my bios and turned off every energy saving setting in windows but nothing seems to keep it powered on. I guess its a windows/bios thing and not a HA thing anymore.

12

Windows have nothing to do with WoL.
It is only firmware/BIOS.