Temperature in Fahrenheit? about mmm-netatmo HOT 17 CLOSED

Thanks for the tip. Looks good now!

from mmm-netatmo.

Hi there, is your Netatmo set to Fahrenheit? I wound like so set it automatically regarding to the settings in Netatmo.

from mmm-netatmo.

I believe so. My netatmo browser page shows temperature in F. But the magic mirror module does not. Thanks.

from mmm-netatmo.

Ok, and the data on the mirror is in Celsius Or just Fahrenheit with C in the end?

from mmm-netatmo.

The data on the Magic Mirror is in Celcius. See pic. Thanks.

from mmm-netatmo.

If you mean the default module weather obtained from Openweathermap, it was in F.

from mmm-netatmo.

Ok, as I understood the Netatmo API, the data should get out in the correct format. You can check the setting in the data you get back from Netatmo:

Here you have the unit value indicating the measurement system you are using.

Could you use your browsers debugger (open the mirror ui on your computer) to trace in the module coding and set a breakpoint inside the renderAll method of netatmo.js. Reload the page and have a look at the data variable.

from mmm-netatmo.

Pardon my ignorance I'm pretty new at this, but in my Chromium browser on the Pi, I think you are suggesting I use the the Developer Tools to trace the netatmo.js file in the module folder? How do I run the mirror UI (e.g., npm start) and have the Chromium dev tool trace it? Thanks again

from mmm-netatmo.

@schnster you just need to start the mirror as usual. Then you open your browser on your laptop and call the PIs ip: in my case it's http://192.168.178.40:8080
In the browser you can use the developer tools, the PIs browser Chromium has not dev tools, so you need to do this round trip.

from mmm-netatmo.

Ah, thanks, that was neat! I traced the data variable and this is what I got.

from mmm-netatmo.

Ok, so different unit and if you look at the sensor data: body/device/0/dashboard_data is it in Celsius or Fahrenheit?

from mmm-netatmo.

Temperature is in Celcius...

from mmm-netatmo.

Ok, I'm a bit confused, if I as an api provider would knew how the user wants his data to be displayed, then I would transform the data into this format right away. But that's only my opinion, I've just created a ticket in the netatmo forum. Hopefully someone there can tell me how to handle it. If we have bad lucky I need to implement a data conversion regarding the unit attribute.

from mmm-netatmo.

OK, thanks for helping out with this!

from mmm-netatmo.

Sorry for the inconvenience. If you like to get dirty you can get into the code and do a quick fix to Fahrenheit. Go to line 191 in netatmo.js and change return value.toFixed(1) + '°'; to return (value*1,8+32).toFixed(1) + '°';.

from mmm-netatmo.

The quick fix suggested utilizes a comma as the decimal point in the multiplier rather than a period. This will break the code for those computers with language configurations which define the period as the decimal point, returning a value of 40º. Presumably, many users who are looking for data in Fahrenheit are also using keyboards configured for US (EN).

The correct code should read (value*1.8+32).toFixed(1) + '°';

from mmm-netatmo.

@macogle you are right, 1,8 was stupid ;) it won't work never the less which computer language you have.

from mmm-netatmo.