I seem to have this same issue. I am using Mobilinc Connect and I have boundary notification on. It works 95% of the time. But 5% of the time, I can be outside the boundary by 30 miles for 10 hours with no notification, and no change to the variable. I cannot find a consistent cause. The first time it happened was after an iOS upgrade. I did not launch Mobilinc after the upgrade, and for 3 days of crossing into and out of the boundary I got no notification. Launching Mobilinc fixed that one. So I thought maybe the app has to be launched after a reboot, but testing shows that to be false. Then I thought maybe it has to do with the app being in sync with the ISY. I have a HUGE system, and as such only sync manually. Sometimes I will make changes to my system and not sync the app for days. But again, testing shows that does not kill the geofence function.
If it is not reliable, I will not be able to integrate it into my automation.
Testing will continue. I will say, reliability of the state variable changes seems to be very good when boundary crossing notification works. I have only had one time where mobilinc sent the boundary crossing notification, but the variable did not get changed
Does adding iBeacons and advanced locations have any bearing on location notification? If I added iBeacons, can I have variables in the ISY change based on my proximity to those?