Read the statement by Michael Teeuw here.
Weather Module showing wrong current temperature
-
@wyovino 6 releases back, 18 months, who knows.
setup a new version and check it out
use my backup/restore to help move to new release
new nodejs doesnt run on buster
-
The MMM-Jast module doesn’t work properly on a Zero2W with more recent versions which is why I did a fallback to this version. Is this related to the Weather API change I saw in the pinned post? Here’s my config. The “current” doesn’t work properly but the “forecast” does.
{
module: “weather”,
position: “top_right”,
config: {
weatherProvider: “openweathermap”,
type: “current”,
location: “Rockville Centre”,
locationID: “5134203”,
apiKey: “{myAPIKey}”
}
},
{
module: “weather”,
position: “top_right”,
header: “Weather Forecast”,
config: {
weatherProvider: “openweathermap”,
type: “forecast”,
location: “Rockville Centre”,
locationID: “5134203”,
apiKey: “{apikey}”,
fade: false
}
}, -
@wyovino i do not know. calendar is my thing
-
@sdetweil
I appreciate your efforts. The reason I’m using a Zero2W is that my mirror is in a tiny bathroom and when I used a Pi4 I could hear the hum of the fan. The Zero2W worked well except for the stock ticker which became very jerky. For the weather module, maybe I need a new API key. I’ll give that a try. -
@wyovino and that age code you will need need to change code.
the api requires v 3, and a different endpoint .
i dont know if it will work
-
@sdetweil Do you know how frequently MM reaches out to pull down the weather data? I’d rather not exceed the daily free limit.
-
@wyovino see that in the doc, updateInterval i think
https://docs.magicmirror.builders/modules/weather.html#general-options
-
The default value is 10 minutes, so it should never go above the free limit.
-
@wyovino The current temperature displaying is now correct. I’m guessing this was an issue at the source.
-
S sdetweil has marked this topic as solved on
