You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Device: Oneplus 8 Pro + Huawei Watch 4 Pro / Huami Amazfit Bip S Lite
Installation source: Google Play
Don't know why, but I don't see notifications when someone enter/leave regions on my watches, however I see them on my phone.
I'm using Huawei Watch 4 Pro with latest Huawei Health app (previously same problem was with Huami Amazfit Bip S Lite with latest Zepp app), and can get all notifications to my watches from all apps except those ones (regions related) from OwnTracks.
And at the same time, on my watches I can see notifications about errors from OwnTracks, so seems like the problem exactly with region notifications.
The text was updated successfully, but these errors were encountered:
This one might be difficult to reproduce without the actual hardware. It seems weird that it's just the regions OT notifications, I wonder if there's something about the events notification channel that it's filtering on?
liquidblasted
changed the title
Notifications about region enter/leave not appears on Amazfit Bip
Notifications about region enter/leave not appears on Smart Watches
Mar 31, 2024
and you don't have to, thank you so much for all the contributions to this wonderful project :) I just updated it in the hope that if someone will improve this in the future
Don't know why, but I don't see notifications when someone enter/leave regions on my watches, however I see them on my phone.
I'm using Huawei Watch 4 Pro with latest Huawei Health app (previously same problem was with Huami Amazfit Bip S Lite with latest Zepp app), and can get all notifications to my watches from all apps except those ones (regions related) from OwnTracks.
And at the same time, on my watches I can see notifications about errors from OwnTracks, so seems like the problem exactly with region notifications.
The text was updated successfully, but these errors were encountered: