Open brunseba opened 6 months ago
Temperature etc sounds like a good idea as long as such sensors are generally available on devices. (On our iOS app we submit barometric pressure in p
for instance.)
These could be added to extended data.
@jpmens how do you want to do this? Shall I come up with a proposal for values of keys that data can go into (based on what it might be possible to get)?
Gladly, though if you kick me in the direction of where the possible values are documented, I'll gladly take the task.
I'm going to assume the data will be quite different from what iOS has to offer, but when we have a list of items we can coordinate with @ckrey
I'll have a read through https://developer.android.com/develop/sensors-and-location/sensors/sensors_overview
I had a look at sensors a while ago. Reading Gyroscope/Accerelometer does not make sense when you take the measurements only once every few seconds or minutes. I used it in another project where we used Gyro/Accerlometer with a frequency of 50 times per second. I don't think something like that makes sense in OwnTracks. There is no thermometer in an iPhone/iPad
The only data I'd be interested in from above list would be ambient air pressure, relative humidity, and temperature, but as it's the device's temperature it doesn't make much sense at all to me to collect the latter. (How hot is your pocket?!)
@brunseba since it was you who began this thread: which of the sensors from the documentation linked to above were you thinking of? And please consider we won't be publishing N x per second just to get a gyro or whatnot.
@brunseba thoughts?
Hello,
I'm currently testing our android client to cover circuit motorcycle metrology. It works well with a ThingsBoard server instance.
Regulation banned to collect metrics directly on motorcycle ECU, so i plan to use smartphone embedded sensors instead.
Do you think it's possible to add option on your android version to select more data from sensor like : temperature, gyroscope, ...