android: High accuracy mode no longer disables when leaving zone

Home Assistant Android app version(s):Android 2023.3

Android version(s):13

Device model(s): Pixel 7

Home Assistant version:2023.3.6

Last working Home Assistant release (if known):2023.3.6

Description of problem, include YAML if issue is related to notifications: Location Sensors/Background Location/High accuracy mode only when entering zone no longer disables when outside of selected zone

Companion App Logs:


Screenshot or video of problem:

Additional information:This has been working fine in the previous versions of the companion app

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 4
  • Comments: 22 (5 by maintainers)

Most upvoted comments

Hi 👋 I think I’ve found the issue but would appreciate it if someone here could confirm if the fix works as expected.

You can download a test version of the app from here (login, click artifact.zip, unzip app-full-debug.apk), it’ll install without modifying the original app if you give your device another name when logging in. Then, setup the location constraint for high accuracy mode and let me know if it works correctly again 😃

Same issue here … high accuracy mode not always activate in the expanded area and not always disable when i enter in zone.

Thank you!! When will the new version be released?

The change hasn’t been merged to the main code base yet and the app doesn’t have a set release schedule, so it’s hard to tell. It’s been a while since a release so I’d expect relatively soon.

When merging this issue will be closed. You can expect it to be included in the next weekly beta release after that (betas are pushed Sunday morning UTC).

Hi 👋 I think I’ve found the issue but would appreciate it if someone here could confirm if the fix works as expected.

You can download a test version of the app from here (login, click artifact.zip, unzip app-full-debug.apk), it’ll install without modifying the original app if you give your device another name when logging in. Then, setup the location constraint for high accuracy mode and let me know if it works correctly again 😃

Thank you!! When will the new version be released?

Test version works here. Get in high accouracy mode entering expanded home zone as setup in settings. Thanks

@jpelgrom Test version of the app appears to be working here. It didn’t get stuck in high accuracy mode today.

I can confirm it works… Only tested when leaving home zone but it triggers correcrly high accuracy mode in conjunction with bluetooth specific connection…

It looks an evaluation logic was somehow inverted, as when I leave the expanded zone, ham activates, and then deactivates when I enter the expanded zone. I have tried to add another zone and added it to trigger zones, now ham is always active as I’m always outside one of the expanded zones: ham was active even when I was not close to any of the defined zones.

04-08 19:18:54.735  5833 19898 D LocBroadcastReceiver: High accuracy mode enabled, because defined ([28:A1:83:16:37:B5]) bluetooth device(s) connected (Connected devices: [BluetoothDevice(address=C2:02:13:06:55:13, name=Mi Smart Band 6, paired=true, connected=false), BluetoothDevice(address=28:A1:83:16:37:B5, name=MB Bluetooth, paired=true, connected=true), BluetoothDevice(address=BC:F1:71:C9:CD:85, name=PRGA-010409, paired=true, connected=false), BluetoothDevice(address=00:1B:66:B3:E9:85, name=PXC 550-II, paired=true, connected=false), BluetoothDevice(address=1C:48:F9:14:F4:03, name=Jabra MOTION a1.42.0, paired=true, connected=false), BluetoothDevice(address=91:1A:CB:F0:8D:84, name=APPT, paired=true, connected=false), BluetoothDevice(address=7B:E1:FD:B8:9E:B8, name=Smart Tag, paired=false, connected=true), BluetoothDevice(address=42:25:C4:F3:6C:A6, name=Smart Tag, paired=false, connected=true)])
04-08 19:18:54.735  5833 19898 D LocBroadcastReceiver: High accuracy mode enabled, because in zone [1_zone.home_expanded, 1_zone.hlinsko_expanded]
04-08 19:18:54.746  5833  5833 D LocBroadcastReceiver: Received location update.
04-08 19:18:54.766  5833  5833 D ForegrndServiceLauncher: Check if service HighAccuracyLocationService is running. Service running = true

With multi server support there was added reqestId to geofence registration. Cannot that cause this?