In the recent past, my geofence stopped working. In the geofence are anter and exit commands. The enter command is to change the value of a variable to 1. The exit command is to change the same variable to a value of 0. The geofence appears to trigger as I enter and exit the area, but the variable value does not change. Digging further I notice a log input “there are no specified commands for this geofence trigger”.

I am on android. We also have an apple phone where I believe the same type of geofence works fine. As near as I can tell, all apps are up to date. IoX version is 6.0.0

Any thoughts on what is happening and why the variable change does not occur as the phone enters and exits the geofence?

Edited Sunday at 01:53 PM4 days by oberkc

Can you verify the geofence commands are set? It sounds like they may have been removed, maybe due to a failed synchronization.

49 minutes ago, Javi said:

Can you verify the geofence commands are set? It sounds like they may have been removed, maybe due to a failed synchronization.

I am not sure I understand this question. How does one determine if they are "set"?

UDM > Settings Tab > Geofence, Click on Geofence and verify Enter and Exit commands are correct.

14 minutes ago, Javi said:

UDM > Settings Tab > Geofence, Click on Geofence and verify Enter and Exit commands are correct.

I have done that, several times. I have also deleted the geofence and recreated it with the same enter and exit settings. When I recreated the geofence, it immediately recognized that it was exited the area and gave me the error in the log again

Additional updates:

After I move back into the geolocation zone, I open the log. I see that UD mobile recognizes the transition (at 04:21pm) and logs:

"Triggering Geofence Enter: My Geofence"

"Network Connected: false"

"Network Not connected waiting 30000 milliseconds."

The variable that was supposed to update from the entry command did not change however.

It was not until I opened UD Mobile at 5:18pm, however, that the log then recorded:

"Completed geofence command for id: My Geofence"

At that point, the variable updated.

Why does UD Mobile now seemingly require me to open the app before completing the geofence entry criteria?

13 hours ago, oberkc said:

Additional updates:

After I move back into the geolocation zone, I open the log. I see that UD mobile recognizes the transition (at 04:21pm) and logs:

"Triggering Geofence Enter: My Geofence"

"Network Connected: false"

"Network Not connected waiting 30000 milliseconds."

The variable that was supposed to update from the entry command did not change however.

It was not until I opened UD Mobile at 5:18pm, however, that the log then recorded:

"Completed geofence command for id: My Geofence"

At that point, the variable updated.

Why does UD Mobile now seemingly require me to open the app before completing the geofence entry criteria?

Did you change phones or have a phone firmware update in the recent past? This is usually caused by the Android operating system not allowing the app to use network or battery when the screen is off. Are the permissions correct? see https://wiki.universal-devices.com/UD_Mobile#Permissions_Android

2 hours ago, Javi said:

Did you change phones or have a phone firmware update in the recent past?

The phone has been another long story since March, but I won't bore you with the details. The current phone has been in place since August and it has worked with with UD Mobile at one point.

My android (Pixel 9, android version 16) does not have a permission "allow background usage" as near as I can tell. Otherwise, permissions (location and notification) appear correct.

Update: I found the "allow background usage" user the settings for "Battery Usage". I have confirmed that it is set to "allow background usage".

Edited Monday at 04:54 PM2 days by oberkc

I use a Pixel 9 Pro on 16 also, so should be similar.

You described 3 different errors which are not necessarily related.

1) there are no specified commands for this geofence trigger” > The Geofence does not have commands for the Trigger Type (Enter Exist). Maybe this was fixed when you reentered the commands?

2) No network > The app did not have access to Internet when it tried to execute a network call, then says it will reattempt in 30 seconds.

3) Reattempt after 30 seconds did not happen, but the app did reattempt after it was opened. This is either due to the app crashing in the wait period or the Android operating system stopped the app (i.e. Battery Saver). The latter seems more probable unless you received a crash message.

For issues 2 & 3 sometimes the phone needs to be restarted, not sure why but has worked for other users.

If only things were this easy.

1) I can assure you that there have always been entry and exit commands. If it was this, I would have known how to fix it. That is the first thing I checked when things stopped working.

2) Which makes sense, but the phone has access to the internet. I am listening to streaming audio. I get email and text (internet texting through google voice). If UD Mobile does not have access to the internet, there is some issue between the phone and the app.

3) I received no crash messages or any indication of battery saver condition. The charge state is at 80%. The phone is confirmed NOT in battery saver mode. Furthermore, for unrelated issues, I frequently restart the phone and did so before arriving home just a few minutes ago. The variable (entry criteria command) did not change values as it should have. The phone is now on wifi.

This is actually my second pixel 9. The first was ultimately replaced by google after a LONG (and painful and duplicative) series of troubleshooting steps by both google and Verizon on a failure by the first phone to be able to establish a wifi hotspot. The replacement pixel 9 exhibited no such trouble. I find it hard to believe that there are faults with the second phone that would contribute to this current experience with UD Mobile. In fact, UD Mobile geofence worked fine on this phone until recently. Unfortunately, the technology in my life has been acting up enmasse lately. I am dreaming about the days when I did not have to spend hours troubleshooting gadgets.

Thank you for your thoughts thus far.

Edited Monday at 08:57 PM2 days by oberkc

What is the message in the UDM Geofence log this time around?

1 hour ago, Javi said:

What is the message in the UDM Geofence log this time around?

To be clear, I did not open UDM when I arrived home (3:42pm) and only did so now (5:06pm). When I opened UDM at 5:06, the variable changed as it should. The following messages appearing the log:

3:42pm Triggering Geofence Enter: My Geofence

342pm Geofence ID: 3 Network Connected: False.

3:42pm Geofence ID: 3 Network Not connected waiting 300 miliseconds

4:03pm Geofence ID: 3 Network Not connected waiting 180000 milliseconds

403pm Geofence ID 3: Network Not connected waiting 450000 milliseconds

5:06pm Geofence ID 3 Completed geofence command for id: My Geofence

5:06pm Geofence ID 3 Completed geofence command for id: My Geofence

5:06pm Geofence ID 3 Completed geofence command for id: My Geofence

Ok, the error is consistent No network access or the Android OS is not allowing UDM to access the internet.

UD Mobiles target version changed in August from 34 to 35 so this may be related. Along with a deprecated network check function.

Although I don't see any of these issues on my Pixel, the deprecated function may be the cause. Added to our list, but may be a couple weeks before it makes it to production.

Notes:

Every time UDM encounters no internet it waits 30 seconds multiplied by the number of previous checks up to 6. However it looks like there is a feature(?) in the app which cause the command to be sent even without internet after the 450000 (6 loops) is reached. Looks like it is held in the network queue until the OS gives the app internet access, when the app is opened.

15 minutes ago, Javi said:

Although I don't see any of these issues on my Pixel, the deprecated function may be the cause. Added to our list, but may be a couple weeks before it makes it to production.

I hope this fixes the problem. Thank you for the feedback. I will look forward to having my geofence back.