Yep, it went nuts again at exactly 2am..ish.
And it finished all the mayhem at exactly 3:13:15.590:
In direct correlation to the backup am were it finished:
This time I had made two changes on the drivers:
-Cranked the presence timeout value to 9000 = 150hrs:
-Cleared any offset value on the sensor:
This time, I did not get the "nan" value after the storm caused by the backup, so I can say with high degree of certainty that whatever got scrambled, has to do with the offset routine.
Now the standing question is, why the heck the backup is inducing this cascading effect. I was awoken at 2:30am last night (terrible tooth ache) and my arduino at my room, who has an led aka night light did not trigger its supposed rule action with the movement sensor. And the above Hubconnect message stating that it had lost ping to its SmartTHngs hub suggest total network isolation.
Maybe the fine folks from Hubitat Support could throw us a bone here. @bobbyD