Any update on this? Bought an polar HR band, works fine in SaA but the heart rate is not sync to google fit…
@Nighthawk8 this issue should be resolved in the latest BETA version of the app.
Please first join our BETA Testers group at:
https://groups.google.com/forum/#!forum/sleep-as-an-droid
That you can opt-into the BETA at the following address:
https://play.google.com/apps/testing/com.urbandroid.sleep
Or simply by visiting our Play Store listing and tapping “Join BETA”
After that you should be starting receiving latest BETA updates through the Play Store.
Sorry for the late response but indeed after the beta update it’s working fine. Thx!
Can’t integrate Google fit with the application no result after selecting account to be synced
1 Like
Hello @Andres_Reyes_Monge, what version of the app you have? Menu > release notes…
Can you please try this with the latest BETA version of the app?
Please first join our BETA Testers group at:
https://groups.google.com/forum/#!forum/sleep-as-an-droid
That you can opt-into the BETA at the following address:
https://play.google.com/apps/testing/com.urbandroid.sleep
Or simply by visiting our Play Store listing and tapping “Join BETA”
After that you should be starting receiving latest BETA updates through the Play Store.
@Andres_Reyes_Monge I’m able to reproduce the issue even in BETA, many thanks for reporting andsorry for the issues.
Google Fit did make security related changes to Google Fit and apps will only be allowed to basically write to Fit… this has caused some issue in the transition process and Google Fit authentication may not be available for new users some time in Sleep as Android…
Existing users who did already consent to connect Sleep as Android with Google Fit are working for the time beeing…
We are working on it to bring the fixes out ASAP… this will be first fixed in the BETA channel so ideally please first join our BETA Testers group anyway - see the guide in my previous reply…
Hopefully we will get this working in the next few days…
1 Like
Hello,
we have a fix for the recent Fit issues in the latest BETA version.
The APK is available from this link:
https://sleep.urbandroid.org/wp-content/uploads/release/sleep-20210929-beta-release.apk
Or if you join the BETA release channel you can get it through the Play Store.
Please first join our BETA Testers group at:
https://groups.google.com/forum/#!forum/sleep-as-an-droid
That you can opt-into the BETA at the following address:
https://play.google.com/apps/testing/com.urbandroid.sleep
or simply by visiting our Play Store listing and tapping “Join BETA”
After you receive version 20210929 (you can check that in menu - Support - Release notes).
If you still cannot connect with Fit after the update, please to to your Google Account > Data & Privacy > third party apps with account access … and first remove the Sleep as Android… than please reboot the phone (to clear the scopes from local caches) and try to connect Google Fit again.
Sorry for the issues. Hope that this will resolve the problems…
Please let us know…
I’m actually already running the latest beta and can confirm that connection to google fit is now correctly working
@Andres_Reyes_Monge big thanks for letting us know, this is great news!
We had to drop some feature in Fit though so now we are writing / reading sleep phases and HR, but are no more syncing your profile data and we are no more doing automatic #sport based on reaching your activity goals…
At the moment reading 3rd party sleep records and HR is still working, but we may expect this to stop working later and we will probably need to do another fix release of the app to accommodate for this. This is all due to privacy updates in Google Fit…
1 Like
Hi @petr-urbandroid,
I’m back to trying to load my O2Ring’s three sensor outputs into Sleep as Android.
I just re-read your reply about using Google Fit. In your reply in Oximeter - Sleep as Android - Documentation - Sleep as Android (urbandroid.org), you mentioned aggregated data.
Does that mean SaA won’t expect raw sensor data to arrive from Google Fitness Store?
If SaA will accept raw sensor data from Google Fit, then can you please help me identify what the movement raw sensor data type should be called?
The Google Fit scenario I envisioned:
- O2Ring data saved to .csv file using its included app.
- Create a Google Fit dataset for each of the three O2Ring sensors.
- Load the parameters and ask SaA to read the Google Fit data (sync).
I looked in here: https://developers.google.com/fit/datatypes?hl=en_US
- movement: I can’t find a raw sensor movement parameter in standard Google Fit data types
- HR: https://developers.google.com/fit/datatypes/health?hl=en_US#oxygen_saturation
- O2 https://developers.google.com/fit/datatypes/body?hl=en_US#heart_rate
Since live reception of the O2 Ring’s motion data is (currently) not possible, batch import the morning after seems necessary. To benefit from the SaA algorithms’ current power and future improvements, my data should arrive as sensor data, right? Otherwise, for me, SaA is acting more as a renderer (dependent on Google’s sleep analysis’ aggregated data); I prefer to use SaA’s own algorithms to provide a complete sleep analysis solution.