WOL not working

[Luke 42077]

Quote

Would a webhook in the client be a workable alternative?

There isn't such a feature so I don't think so. Even if there were, WOL packets are not send over normal http requests like webhooks are.

[MrIncredible 2]

On 23/10/2024 at 23:28, Luke said:

I would wait and reevaluate this in a couple weeks as a newly revamped version of the app is set to be released. Thanks.

Did this revamp happen?  I don't recall seeing any messages about upgrading the server.

On 24/10/2024 at 00:12, Luke said:

There isn't such a feature so I don't think so. Even if there were, WOL packets are not send over normal http requests like webhooks are.

I was thinking more that a client webhook could be used to trigger an Alexa WOL routine (like I have already and which works fine) and which could wake the NAS on which Emby is working.  That way you needn't have to incorporate any WOL action - just find a way to allow a trigger to be sent from a client using a webhook!

Thanks.

[Luke 42077]

On 12/7/2024 at 8:30 PM, MrIncredible said:

Did this revamp happen?  I don't recall seeing any messages about upgrading the server.

I was thinking more that a client webhook could be used to trigger an Alexa WOL routine (like I have already and which works fine) and which could wake the NAS on which Emby is working.  That way you needn't have to incorporate any WOL action - just find a way to allow a trigger to be sent from a client using a webhook!

Thanks.

Hi, any day now our new windows app should be in the store. Stay tuned to the blog for the release announcement !

[MrIncredible 2]

Hi,

I've been revisiting this issue again as I have installed the latest Emby Windows App to see if the WOL is working as expected in the new revamped application.

It appears that the App still uses the MAC address of the Emby Server docker to wake the EmbyServer up but its the MAC address of the Unraid Server on which the docker is installed which needs to be used in the WOL command.  I've used the wolsniffer.exe app to capture the WOL commands.  Although the new App is now correctly using the destination IP of 255.255.255.255 on port 9 to broadcast the WOL command, the MAC address used will not wake the (Unraid) Server.

Is there any way around this?  Perhaps an option to specify a MAC address in the client?  Or the emby server has an alternate MAC address that initially passes to the Application for WOL purposes?

 

Thanks.

Edited March 21, 2025 by MrIncredible

[MrIncredible 2]

UPDATE:  Having posted the above questions, it occurred to me that I might be able to spoof the Unraid MAC address in the Emby Server docker.  Sure enough, using an option: "--mac-address  aa:bb:cc:dd:ee:ff' worked well.  I let the clients attach themselves to the server to read the mac address, and after that the wol woke the unraid server fine.

[Neminem 1518]

This might help you.

[PLUGIN] WOL for Services - Plugin Support - Unraid

 

[MrIncredible 2]

8 minutes ago, Neminem said:

This might help you.

[PLUGIN] WOL for Services - Plugin Support - Unraid

 

I think that is for waking a docker or VM whilst the main Unraid server is operating?  My Unraid server is asleep.

Edited March 21, 2025 by MrIncredible

[Neminem 1518]

Ok my unRaid server never sleeps it always busy.

[MrIncredible 2]

16 minutes ago, Neminem said:

Ok my unRaid server never sleeps it always busy.

Can't afford to run the server 24/7 with the cost of electricity as it is!

[Luke 42077]

Currently the WOL address and port are automatically determined by the server and made available to clients. So yes we need to make this configurable in case you need to specify some other address to use.