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: Data types | Google Fit | Google for Developers
- movement: I can’t find a raw sensor movement parameter in standard Google Fit data types
- HR: Health data types | Google Fit | Google for Developers
- 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.