@community: My opinion, what are you thinking about?
- there should be at least an option to keep the core running even if the cloud connection fails.
- And it should be possible to start or reset firmware w/o having web access!
There are many reasons why this could happen:
-What’s the use of running on battery power (or having a backup battery) if i can’t move away from router ?
-What’s the use of having a backup battery for data logs in RAM if everything is lost because the core reboots w/o Cloud Connection ?
-EMI problems for some seconds in rough environment
-temporary problems with the DSL/cable provider, but router is still running (especially when provider works on backbone issues or upgrades in the night f.e.)
-router down for a firmware update
-you want to move the core to another place outside your wireless LAN for logging purposes or in a vehicle but read the datalog later w/o USB cable.
Example: One scenario for me is having the core to control my heating 24/7, but it has more priority to keep the heating running w/o cloud access than to have remote control. Or even more important: It should automatically wake the heating from standby after there’s no cloud access for whatever reason for some hours. Think of the fatal damage to your home and your waterlines in case there’s no heating while you are out for skiing for a week because the power supply of the router failed…
I think there are a lot of scenarios that need the core keep running even the cloud connection fails. What does the community think about it ?
EDIT: Also RTC should keep running, as requested here: