Units - is this the expected result from the OS Simulator or watch?

[Guy_]

import { units } from "user-settings";

console.log( "Body Weight "+units.bodyWeight);
console.log( "Distance "+units.distance);
console.log( "height "+units.height);
console.log( "Speed "+units.distance);
console.log( "Temperature "+units.temperature);
console.log( "Volume "+units.volume);
console.log( "Weight "+units.weight);

[10:08:46]App Started
[10:08:46]Body Weight metric
[10:08:46]Distance metric
[10:08:46]height metric
[10:08:46]Speed metric
[10:08:46]Temperature C
[10:08:46]Volume metric
[10:08:46]Weight metric

Temperature seems to always be C regardless of any user settings - is this correct?

How does one get the correct information?

[Guy_ · Accepted solution]

The solution seems to be to set length units to Miles to get Fahrenheit, or Kms to get Celsius, irrespective of whatever temperature setting is chosen.

It will return C instead of F with this setting in the Fitbit App, App settings, Units..

 

In addition the web Dashboard profile the settings seem to be independent of the API results and are not replicated in the Fitbit App, App settings, Units.

[Guy_]

Changes to the Fitbit App, App settings, Units, Temperature are correctly reflected in the Fitbit App even though they are not correct in the { units } from "user-settings" after syncing.