WD has created this ?Nifty? Cloud Device with a timer built-in for “Energy Management”, BUT!, guess what, when the system powers down all comm gets clobbered, ooooooo-peeeeeee. Fortunately, for Me, a highly intelligent Networks Person, I have SW capable of handling this Flaw in OS5.
There are two solutions:
-
Implement day of week scheduling, easily decoded from the NTP service, so I can coordinate the clunky day of week scheduling in the OS5 energy saver service. Oh, but that would put the car-rooches to the idea of energy savings, now wouldn’t it. BUT! it would be easy.
-
The preferred solution, but should be in addition to solution 1, the implementation of GARP. Ooo, what-dat-R-GARP? GARP is a subset of ARP which is part of the TCP/IP suite and operates on layer 2, which just so happens ole OS5 understands. AND! The GARP part is how one device informs the “Network” of its presence. Well, glory-B, does this mean OS5 could inform other devices that “Service” is shutting down? Show-Nuff, which means all us User Pogs could do a graceful shutdown and restart when OS5 gets done "Energy Saving. Proper network implementation, Learn-it, Live-it, Love-it.
Moum-Back good buddy😜
