Hello @JTT, please note that alarm uses gentle vibrations - the find the least vibration intensity necessary to wake you. First vibration 30s pause second 20s pause 10s pause etc… so it may seem like it is not vibrating…
Hello again.
I actually moved from ionic to sense and it seems to work, but only the half night.
I remember i had this issues with ionic, too, but i don’t find the crash report in SAA.
@petr-urbandroid For the last three nights my Versa 2 is not connecting to Sleep as Android so sleep tracking falls back to “Track without”. I’ve tried resetting both devices, reinstalling both Sleep as Android and the Fitbit app on my watch but still doesn’t connect. According to “What’s new” on the Google Play store for Sleep as Android Beta, the app updated on my phone on July 20 which is approximately when the issue started. The most recent Release notes are for 20220609 but my phone is on version 20220720. Has there been a change that would cause this?
Thanks!
SaS version: 20220720
Fitbit: version 3.64.5.fitbit-mobile-36419051-462553406
I rolled back to the 20220609 version but still doesn’t connect. I don’t recall making any changes that would cause this issue. It’s been working great for months, maybe years.
Appreciate any help.
Also have problem with apps not connecting. Unsure when it started since I haven’t used SaA during summer vacation But went back to work today and couldn’t get it to work yesterday and today.
SaA version 20220707
Fitbit companion app version 5.5
Currently experiencing the same issue since around the 21th of July with Versa 3 as that is theast date with HR histoey.
App on phone will eventually time out when attempting to connect. Watch app with take about 30-60 seconds and appear to connect correctly displaying the tracking hr and time. Hitting pause on watch does not reflect changes on app. Phone app will not receive hr or activity from watch though or even appear to show the connection worked.
I checked permissions on Fitbit and SaS apps with no changes found. I thought maybe issue was with Bluetooth le and I reset connection with Versa and versa controls, but that did not fix it either. I turned off wearable tracking in app, selected others, the returned to Fitbit without it fixing the issue.
Issue started after 7/21 as that’s the last recording with watch data. Fitbit shows app updated 7/21 and it is likely the cause.
SaS version 20220609
Fitbit : 3.64.5.fitbit-mobile-36419051-462553406
Also lost connection with my Versa 3 after the 21st of July. Looking at the Google play store, that happens to be the same time that my fitbit app updated.
Hi all, according to the Fitbit staff, there’s a bug in the Fitbit app which broke access to local webserver on the phone, so there’s no way for Sleep as Android to communicate with the watch.
The advice is to either downgrade the Fitbit app to version 3.58 or to wait for an update.
For your convenience, the Fitbit 3.58 APK is here (I’ve got it from Softpedia, install at your own risk, but they claim it’s safe)
Like others, I suspected the issue was in the Fitbit app. Unforunately, when I attempted to downgrade using your link, @jiri-urbandroid, Fitbit 3.58 just crashes on opening. Since I use the Fitbit app for more than just SaS, I guess I’ll just stick with the current, broken version.
UPDATE: according to our users, downgrading the app to 3.58 is not working (the FitBit app immediately crashes). The closes update, that seems to work, is 3.30.
But went back to work today and couldn’t get it to work yesterday and today.