We have updated the FloatHub website to allow end users to set calibration values for their FloatHub device. If, for example, your FloatHub is in a part of your vessel where temperatures are always a few degrees higher than the rest of the cabin, you can now set a constant value to automatically reduce your measured temperature. The settings are part of the regular vessel preferences page:
https://floathub.com/vesselprefs
where you can now set a bias value for air temperature, barometric pressure, water depth, and any of the battery or charge voltmeters.
We want to thank all the FloatHub users who asked for the ability to fine tune their incoming data in this way. And, as always, our beta testers suffered through a few broken versions of this functionality before we got the kinks out (thanks again).
Expect to see more features rolling out soon.
Does it accept positive and negative integers? My results are erratic.
Yes, both positive and negative values are accepted. We will have a look at your account settings and let you know if we see anything odd. Note that changing calibration values does not affect past readings, only new/incoming readings.
Ok, we see your change history on temperature biases; appears to be functioning as expected, here is your last temperature reading around 2:07 (all times UTC):
+---------------------+---------------------+-------------+
| received_time_utc | time_utc | temperature |
+---------------------+---------------------+-------------+
| 2019-05-01 02:07:12 | 2019-05-01 02:07:11 | 97.08 |
+---------------------+---------------------+-------------+
You then changed the temperature bias from +15 to -15 at 02:08, and your next reading was:
+---------------------+---------------------+-------------+
| received_time_utc | time_utc | temperature |
+---------------------+---------------------+-------------+
| 2019-05-01 02:11:07 | 2019-05-01 02:11:06 | 69.24 |
+---------------------+---------------------+-------------+
The current temperature reading on your web interface (below the map) should reflect these sorts of changes as soon as the next reading is available. The historical data (time series charts) will lag more, as results are time averaged and so will take an hour or so to fully reflect the new calibration values.
Of course please let us know if you are seeing anything inconsistent with this at your end, and if you have any other questions.