@bcopeland - super strange--but I believe this to be a case of missing ACK packets for S2-encrypted devices.
I started out noticing that it seems there are issues if you plug/unplug the extender too rapidly.
There seems to be a second "disconnected" message sent about 20 or so secs AFTER the first one (the first one fires right after it is unplugged). Same on the re-connect.
This shows a SINGLE unplug--wait--re-plug action for my extender.
Now, based on this, I'm not sure what it going on with the distance. Maybe I was unplugging and replugging too quickly (Iess than a minute or so) and it was getting confused.
It seems if you unplug/replug too rapidly, it gets that "duplicate" status report from the FIRST action--and the second one never shows up.
That's EXACTLY what happened here:
I unplugged it and plugged it RIGHT back in. The result--the initial unplug showed up, NOTHING showed up when I plugged it back in. Then, the duplicate unplug appears. The re-plug NEVER was logged.
My idea. Something may be killing the ACK from the Hub to the device.
As such, the extender is sending the first event. Waiting for an ACK--and NOT sending anything else at that point. About 20 sec later, it sends the REDO status frame because it never got the ACK. Again, it doesn't get the ACK--but, after waiting a bit this second time, it just gives up.
That would explain all this. AND be a huge issue with power outages (they are often really messy--lots of on/off/on/off events in rapid succession). But, a very common "power" problem is a short "blink off"--where the power goes off and comes on a few seconds later. With the behavior I'm seeing here, that would ABSOLUTELY cause the device to stay on "battery" mode improperly (if the power outage was for under about a minute, the "connected to mains" status would never get sent, leaving it showing "on battery" forever).
Here's another example with a different device showing this may be happening:
22 seconds after the first "battery is 100%", there's a second one (Ring G2 contact sensor here).
And, here, with my S2 (Schlage) garage door lock (it doesn't wait as long):
So, this appears to be an S2 encryption-only issue and it's very repeatable.
Note that I did not see this with my S0 locks nor my other devices that are include with no encryption.
That's my hypothesis.
Thanks!