Read the statement by Michael Teeuw here.
Temp suddenly showing 239 degrees
-
This post is deleted! -
Same thing is happening to me on a new install. Tried even adding units line to config but doesn’t matter what you select it always shows Kelvin. FYI the temperature forecast displays correctly, just not current temp. May have to ditch this and go with a new weather module.
-
No matter what I do, I can’t seem to reproduce this odd temperature display. I’ve even started from scratch with a different rpi, completely blank to having MM up and running … no odd temperature.
-
Hi there,
I experienced this the other day, and I checked again - my new pi 3 is still showing an incorrect temperature reading as well. It seems as though the temperature is set to ‘Kelvin’, though I set the temperature to ‘imperial’, within the config.js configuration file.
--------------------------------------------------------- /* Magic Mirror Config Sample * * By Michael Teeuw http://michaelteeuw.nl * MIT Licensed. */ var config = { port: 8080, language: 'en', timeFormat: 12, units: 'imperial',
Note from admin: Please use Markdown on code snippets for easier reading!
-
After looking around, I see that github member p0akley seems to have identified an issue 5 days ago that matches this description. Following his instructions I was able to resolve the issue with my Pi 3.
Seems there is a small adjustment needed in the file:
modules/default/currentweather/currentweather.jsLink to explanation / resolution:
https://github.com/MichMich/MagicMirror/commit/25ddf2c65178e2b8afe0709b48d5d30054208c04 -
That’s been in the
'develop'
branch. Not pushed to 'master'
yet. With this being a “biggie” for everyone who’s running the master branch, perhaps @MichMich might consider pushing it to the master branch sooner rather than later.And my apologies earlier for not having spotted it. I always run the develop branch. #livingontheedge :)
-
If one of you can confirm the develop branch fixes the issue, I’ll push the changes to the master branch.
-
Been trying to reproduce this now for the past hour, and I can’t get it to show up incorrectly again. I double checked line 167 of the currentweather.js file on the develop branch, and it does include the correction mentioned earlier which initially resolved my issue.
-
@michmich Was this ever pushed? I believe I’m having the same issue.