A DŌS will not just shut off in event of a network issue. I think you are misunderstanding what Fallback is.
Fallback is a special programming command which, if used in an output's program, tells an output in an AquaBus module what to do
if that module loses communications with the Apex/Apex Classic/Apex Lite base unit or the Apex Jr. Fallback has no effect during normal operations. Two examples of when Fallback might "kick in":
- If the AquaBus cable between an AquaBus module and the rest of the Apex system gets disconnected
- If the controller fails
Fallback has nothing to do with the network or the communications the Apex and the APEX Fusion cloud. Apex programming, including, DŌS schedules, is not stored in APEX Fusion; all programming is stored and executed in the APEX itself. If the Apex loses communications with APEX Fusion, for example due to an Internet service issue, the Apex system just keeps running as is it programmed to do. And if the Apex does lose communications with APEX Fusion, and you have enabled the Heartbeat feature in APEX Fusion, you'll be alerts of that in 34-40 minutes.
If the Apex itself is not working and the DŌS does go into Fallback, OFF is the only SAFE option - that's why it is hard-coded.