I added a little code that prints a message on the Serial interface if it runs.

In the meantime I've added watchdog resets around (calls to) the SQM code, etc. and some other minor improvements. This might help if my assumptions are correct, let me know.

An easy thing to do would be to use the default Weather.ino and see if it still resets. If not then add in the Weather devices one at a time until the problem returns. Once the problem is isolated I c

The connection check is only one way to cause the Mega2560 reset and I seriously doubt (basically zero chance) that is triggering these events. The watchdog timer is always there... well except during

After last night the uptime is now 588 minutes and the connection check occurred 9 times.

I updated the OCS again... this time it turns off the WDT during log file writes (not my first choice) and also does WDT resets during the NTP time update (are you using that?) I also added code (here

I added a watchdog reset in the loop that writes the (daily) blank file so the watchdog doesn't timeout and reset.

I don't recall seeing that happening. Reviewed the code too, looks good. You do have DEBUG_WATCHDOG mode OFF, right? I patched for this bug, 90% sure I got it. Writing the blank log file takes > 8 sec

Yes. The yellow highlighted pins must NOT arrive at the Ethernet shield.

The Mega2560 reset signal is sent to the Ethernet shield at TWO places. I physically disconnect both of these. I bent the pin on the side header but then cut (!) the ICSP reset pin off. How you go abo

What about the W5100 reset signal on the ICSP header is that disconnected from the Mega2560 reset signal too?

The OCS (master branch) has been updated with this feature: It's just a Config.h option where you specify an IP address that the OCS connects to periodically (on port 80) at the specified # of hours.

Sounds good, let us know how it goes.

A picture etc...

I have not forgotten about this and will take a serious look at it. I think a feature where the OCS pings an external server every x hours and if it fails to get a response, it resets itself. When I s

I'll take another look at that when time allows. For what it's worth my OCS is very stable, months of up time, as power outages now and then allow.

What jumps out at me is that there is NO toACAmps() function. The AC function is called toAmps().

Sorry for the delay, I didn't notice the message in my email and only stop by here so often! I suspect something like this would work (note the I2C address of the two BME280's need to be different:) /

What constitutes an ON or OFF state depends on the circuit design. The OCS can, however, adapt both inputs and outputs to swap that logic. In the OCS.ino file find the following code and change HIGH t

The OCS master branch has updated code for roof motion control that now supports a wider range of automatic garage door/gate openers. The roof related options in Config.h were renamed to remove redund