We’re using Xibo on Docker for Windows and got everything set up pretty good.
We’ve encountered a problem, that if we use the WOL function in each display, then the regular maintenance task turns on the displays no matter what time is set up for WOL in the display configurations.
WOL works perfectly when the player isn’t registered in Xibo, but once I got the display up and running in Xibo, all the displays get turned on simultaneously when the maintenance task is triggered.
Anyone else experienced this? Should I turn off WOL in Xibo? We would really love this feature to work properly + scheduled WOL (through the scheduler, not fixed time).
I actually thought that WOL would occur only at 08:30 as set up and that’s it.
Is there a chance that we don’t set up WOL time on each display - we’d rather set up a layout with WOL command the same way as we’d turn it off?
It seems to me that if I turn off all the displays via command, that it will see it’s sleeping at maintenance task time and it will wake them up every 5 mins (at least this is what happens all the time).
Since you wrote that it checks the WOL time every maintenance time, I’ve set up the time on each display on 23:00 and it doesn’t wake up the players (Intel NUCs in our case). Is there any chance to have WOL scheduled on certain time, but on such way that it doesn’t constantly wake them up?
So could this mean that there is an error in our setup or something like that?
Since I changed WOL time on each display, they’re rock solid turn off.
If I change that to a time before current time and run maintenance task - all of NUCs will turn on.
Interesting things are:
we have all displays showed up as the same IP address
we’re struggling with email notifications - they’re sent even if the display is properly turned off AND email notifications per display are set off
Also, could I suspect on our WOL settings or even LAN setup? What worries me the most is that if I get Xibo server out of the story, our NUCs only wake up when we wanted them to wake up. The moment I set them up in Xibo makes them turn on every 5 minutes (except the case when I set up WOL time to future).
I’ve tried entering 08:30:00 (without quotes) in the WOL time and saved, edited the display again and it converted the value into 08:30, and also wakes the display on the next maintenance task.
Really weird, I’ve really gone through the logic of the WOL dependecy and everything seems ok, except it triggers a WOL packet on every maintenance task except when the time is set to future.
You could patch your /lib/Entity/Display.php file by downloading the one from the commit in that issue and volume mapping it into your container. To do that you’d put it in your xibo-docker root folder and then modify the docker-compose.yml file, adding another volume:
And I guess everything went well, I just don’t know if it deployed the file. Tried WOL settings and it still turns on the player, so my guess is that it didn’t deploy the file. How can I check if ‘up’ did properly copy the file?