Why Yubii Geofencing Doesn’t Work on Android 16

[cag014 731]

After testing and checking all permissions, battery settings, and HC3 configuration, I found the actual reason geofencing is not working on my phone (Android 16):

Android 16 introduces a new background‑location and geofence API. The current Yubii Android app has not been updated to support this new API.

Because of this, Android 16 simply ignores the geofence registration request from the Yubii app. As a result:

• Yubii never appears in “recent location access”

• Geofence events never trigger

• Mock location changes are ignored (while Alexa, Google home, Google Maps and Waze are reacting to the changes)

• Real movement does nothing

• HC3 scenes based on “enter/leave area” never run

This is not a permissions issue or a phone configuration issue — it’s a compatibility issue between Android 16 and the current Yubii app.

Until Fibaro updates the app to support the new Android 16 geofencing model, geofence‑based presence detection will not work on Android 16 devices.

 

Question:

Has anyone with Android 16 managed to get geofencing working successfully?

 

Edited January 25 by cag014

[MAC71 10]

I'm on Andriod 16 (Galaxy S25 Ultra)......... No not natively via Yubii App   

[Gonia 5]

Hello @cag014,

Thank you for your report. The issue is known and we are currently working on it. 
Best regards,
Gonia
Fibaro Team

[SmartHomeEddy 1,005]

I think a lot of Android users could appreciate if Fibaro would have given this information. Unless cag014 got it from Fibaro and had the task to share it. 

[cag014 731]

4 hours ago, SmartHomeEddy said:

I think a lot of Android users could appreciate if Fibaro would have given this information. Unless cag014 got it from Fibaro and had the task to share it. 

No, I’m not. I also wish Fibaro would share more technical details about this with me and community😀

After running a lot of tests using a geo‑mocking application (DS Fake GPS Location) on several mobile phones with different Android versions, I eventually arrived at this conclusion.

 

 

  

[SmartHomeEddy 1,005]

42 minutes ago, cag014 said:

After running a lot of tests using a geo‑mocking application (DS Fake GPS Location) on several mobile phones with different Android versions, I eventually arrived at this conclusion.

 

 

Cloud be very frustrating to struggle with an issue, trying all kind of scenario's, find the source of the issue, report it and get the answer YES WE KNOW 

[cag014 731]

15 minutes ago, SmartHomeEddy said:

 

Cloud be very frustrating to struggle with an issue, trying all kind of scenario's, find the source of the issue, report it and get the answer YES WE KNOW 

Absolutely.

For the sake of maintaining a good relationship with the community, I believe Fibaro should be more transparent and share their known or ongoing issues directly in the changelog or in the version‑release posts.

It could be a good idea to start a dedicated “Known Issues” topic and list all confirmed bugs there. This would help users quickly understand whether a problem is caused by their own setup or by the platform itself.

What say you?

Edited January 29 by cag014

[_gev 0]

Any updates on this issue?

[Sankotronic 2,370]

HI @_gev ,

 

the issue is on Android side and settings. Check this topic:

 

With iPhone setting is much easier and it works very good since I wrote quick app that is triggered with our family members iPhone's.