I’ve noticed a persistent issue; a week or so ago we had a power hickup that killed the house power for about 1 second, and at that point I realized I’d procrastinated replacing the UPS for too long, and all network equipment went down. Not a sense problem - but it becomes one. Note, by down I mean all but the actual APs went down - the APs could not connect to switches/routing which basically is a network down event.
I fix my UPS situation, and get the network back up. The sense unit at this point has been up except for the 1 second power cycle, so it most likely rebooted, but it could not connect to the wifi for a few hours post that. However, once the network came back the unit didn’t go back online. I have to power-cycle the sense for that to happen.
There’s no expectation that the unit immediately reconnects once the APs are back online. Particular because the unit would have received routing issues to the internet and DNS as the network slowly came back online, so it would be in an error state outside of “no ssid” or “no internet”. But why it doesn’t try once every 30 minutes or every hour if there’s a connection failure I don’t know. Maybe it does but I have no access to see any logs from it when it’s in this state. And yes, this has unfortunately happened before - partly due to the sense unit is in a wifi dead spot so it has a weak signal to begin with.
It took me a week or so before I noticed the missing data; there’s now an alert if the sense is offline for 10 minutes or more; but I cannot tell if the sense can connect or otherwise. Ideas on how to diagnose the unit would be appreciated too.