I would have thought all three Sentry controls would be in synch. Redundant switches. And that when you're inside your geofence, they would all show that sentry is on, but it just wouldn't react to movement at those locations. The service tech I've been texting for the past several days doesn't seem to know how it is supposed to work.
Here is how my three UI switches are behaving:
The primary toggle (with the checkboxes next to it) is the "master" for Sentry mode. Move that back and forth, and both the app's toggle and that redeye at the top react. (Oh, and the checkboxes all check again...another defect)
The app toggle and the redeye are acting as status indicators for whether Sentry is monitoring, but also as override switches against those checkboxes: If the vehicle is at a location outside the checkboxed areas, both the app toggle and the redeye are off, indicating that Sentry mode is not functioning. But it also seems to be telling the user that Sentry is off altogether (it's not), so there's a strong temptation to turn it on using the app or the redeye, so that once you're outside the geofence it will function.
In UI design, we design three separate states for situations like this where off/on aren't quite capturing the whole of it. The smarter way to do it would be to have (for example) a tooltip in the app that says "Sentry disabled due to location. Turn on to temporarily override." or something along those lines.
I don't know whether this is a bug or something that they "designed" intentionally, but I hope this helps somebody who is confused.