09-18-2021
11:18
- last edited on
09-18-2021
14:23
by
DavideFitbit
09-18-2021
11:18
- last edited on
09-18-2021
14:23
by
DavideFitbit
I have a Fitbit Sense. The Agenda app has never worked. It keeps telling me that I need to make sure I have set all permissions - which I have. It also tells me to enable Bluetooth which is always on and connected. I've uninstalled the app and reinstalled. Nothing. I have turned the watch off and on - didn't help. I even brought the watch back to factory settings and started over - still nothing.
This seems to be a common issue across all devices, especially on the Versa. However, I retired my Versa Lite when I upgraded to the Sense in July, and Agenda worked just fine on my Vera Lite. ??
One thing that might be causing it is that "Sense Controls" has never connected either - always shows up as Sense is connected but Sense Controls (whatever that is) has never showed that it was connected. However, the other apps don't have this issue.
Any ideas?
Thank you!
Moderator edit: subject updated for clarity
09-18-2021 14:23
09-18-2021 14:23
Hi, thank you for sharing all this information about the problem that you've been experiencing with your Sense watch and the troubleshooting steps that you already tried, @catlover129.
Keep in mind the Sense Controls option is used to take calls on your wrist and connects during a phone call, but it shouldn't affect the Agenda app. Before considering other options, I'd like to confirm you've followed all the steps below to properly setup calendar events on your tracker:
You must allow the Agenda app to access your calendar and run in the background. For more information about adjusting an app’s permissions, check this article.
If your events don't appear, check the following settings:
I'll be around.
07-18-2022 13:13
07-18-2022 13:13
I followed all the steps outlined in your reply and I still cannot get the Agenda to work. I have a Pixel 6 Pro running Android 12. My phone wasn't released until Oct 2021 and your instructions were posted in Sept 2021. Could it be that something needs to be set differently for Android 12 ?