Login at Kodi Home

Reelyator · 2024-01-21, 15:25

(2024-01-21, 15:08)_BJ1 Wrote: Maybe you have set a wrong name for your NAS's?...

No, the Network Names (not using IP Adress here) are complete and accurate.
Could it be i need to tweak the ping time and response settings of the Add-on, to allow smooth communication between the Add-on and the device? Do you happen to have any suggestions what settings work well when you want to wake up 2 QNAP + 1 Syno NAS??

_BJ1 · 2024-01-21, 16:06

Set IP instead the name for the false negative NAS and test again.

(2024-01-21, 15:25)Reelyator Wrote: Do you happen to have any suggestions what settings work well when you want to wake up 2 QNAP + 1 Syno NAS??

You can set the Ping Timeout for host-up check to the maximum value because this will be aborted if all devices has responded to the ping. The delay of the host up notification depends on your devices. This has to applied to the device with the largest delay between power-on and the complete working/ready state.

Reelyator · 2024-01-21, 22:26

(2024-01-21, 16:06)_BJ1 Wrote: Set IP instead the name for the false negative NAS and test again....

..using IP-Adress instead of Network-Names seems to be leading to more stable results. At least no more false negative error messages about devices not waking up.
Need to check over the next days how the messages appear, when the NAS are in fact woken up from Standby.

Reelyator · 2024-01-21, 22:32

(2024-01-21, 16:06)_BJ1 Wrote: You can set the Ping Timeout for host-up check to the maximum value because this will be aborted if all devices has responded to the ping. The delay of the host up notification depends on your devices. This has to applied to the device with the largest delay between power-on and the complete working/ready state.

...i have set both values to Maximum.
The 240 s countdown stops in fact when all devices are found online.

Not sure if the 60 s host up notification delay will be enough. From trying out, the QNAP NAS´s need 2-3 minutes from power button to ready, clearly over 60 s.

_BJ1

(2024-01-21, 22:32)Reelyator Wrote: Not sure if the 60 s host up notification delay will be enough. From trying out, the QNAP NAS´s need 2-3 minutes from power button to ready, clearly over 60 s.

I extend this to 300 secs.

Sammel1 · 2024-02-03, 19:11

Where Do I find the option for "Sending continous wake on lan" after the device is up? I mean, wake on lan works and it brings up my device but my device falls asleep after a while, since there is no kind of keep alive signal anymore, like in previous version of advanced wake on lan. Have Expert Mode activated but can't find that option anymore. Any suggestions?

_BJ1

Sending continous WOL Packets through the network is not a good software solution, therefore this option has removed. For your use case you have to enable the option "Autostart" --> "Wake on return from Standby". This will send WOL Packets after suspend. Please note that sending WOL continous is not a "keep alive" signal, WOL is adressed to the MAC of your server nic(s) attempt to activate/boot up the hardware behind.

There's a new version out that works properly after standby.

Sammel1 · 2024-02-09, 23:31

Thanks BJ.
Had a self programmed software running on my server, which keeps the server alive as long as a wol signal has been received from time to time.
But I understand as well, that sending wol all the time is not a good solution.
Unfortunately my Nvidia shield, where Kodi is running is kind of online all the time. Even if I switch it into sleep mode, it still is pingable. Hence I can't figure out, if the shield is on or not.
Have thought about monitoring network traffic or hard disc drive activity at my server as kind of "if traffic on network card or hard disc, then someone needs something from the server" but also this seems not a reliable solution.

How about configuring a network path into Your plugin and instead of continous sending wol it writes (touch) a file. If file is not updated since e. g. 5 minutes, then Kodi is not running anymore. And everyone who want to use it, can read the file age and I could shutdown my server after 5 minutes later.

_BJ1 · 2024-02-13, 16:24

4.0.4 is up: italian language strings added.

**zebraitis** · 2024-04-23, 07:26

Hi. Where do I find the repo where Adv WOL is located?

My challenge: in Kodi V21 when I try to run WOL it can't find the MAC address of my sources... so I thought I would give this a try.

_BJ1 · 2024-04-23, 07:55

https://repo.kodinerds.net/

**zebraitis** · 2024-04-23, 17:05

Thanks for teh response... Just downloaded.

I notice that it is v20 Matrix ready. Will it work in v21?

I'll soon find out. Nerd

_BJ1 · 2024-04-23, 17:07

Yes. It's compatible to v21.

**zebraitis**

OK... Very nice! Nod

Question: Can I have ADV WOL issue a WOL magic packet every 30 minutes to keep my NAS awake when the KODI client is running?

Why: Even though I only have one NAS device, KODI v21 on Win11 may have a bug that is preventing me from relying on it.
(See ... https://forum.kodi.tv/showthread.php?tid=377218 if you ARE CURIOUS)

I can confirm that if I enter my NAS IP address and MAC into Adv WOL, it does wake it successfully... I just wish to make sure it STAYS awake without me setting sleep to start after 8 hours (or some other ridiculously long time)

thanks!

Edit: Since this uses KODI WOL code, I found out that because of the bug that I found, Adv WOL is not working as it should consistently.

too bad.

_BJ1 · 2024-04-23, 19:35

(2024-04-23, 17:34)zebraitis Wrote: Can I have ADV WOL issue a WOL magic packet every 30 minutes to keep my NAS awake when the KODI client is running?

As I'm already said, sending WOL packets could not be a "keep alive" to the NAS (until a device/software could register a WOL packet), it is designed for boot up a device adressed by the MAC of the NIC (which initiates a boot sequence). This is hardware designed, not software. A WOL packet could not extend the uptime of a device when it's already up.

https://en.wikipedia.org/wiki/Wake-on-LAN