@rkorell I have a fork at https://github.com/marclandis/MMM-Pir - not sure how much time I have to keep it updated.

@sdetweil I testet your branch and so far it looks good with my test calendar and also with my real ones.

@JohnGalt @sdetweil it seems that the website doesn’t provide the data anymore. This is an URL that is build in the module:

https://www.autoblog.com/14904-gas-prices/

it results in a 404:

@sdetweil 2.29 please

(2.28 is too old :) )

@sdetweil I am going to test your fix with my calendar too, as it was the cause for the initial fix.

@Ray updates are still done even the screen is off.

@Ray said in MMM-OpenWeatherForecast:

@wishmaster270 yes I have mine set for 15
but that doesn’t explain why when I turn it on for the first time in the morning they already have 20 calls I don’t get that

What means “turn it on”? Boot up the Pi or turn on the screen?

@kasperb there is a fork of MMM-Reddit which seems to be updated: https://github.com/CurlyQ12391/MMM-RedditDisplay

@butchkemper it seems that you are mixing configuration for the standard weather module and configuration for MMM-OpenWeatherForecast

@htilburgs said in After update 2.29.0 PM2 does not work:

VERSIONS: electron: undefined; used node: 20.9.0; installed node: 20.9.0; npm: 10.1.0; pm2: 5.4.2

for whatever reason MM doesn’t recognises your electron version

@chrisfr1976 said in Mirror not starting after update:

npm ERR! notsup Required: {“node”:“>=20.9.0 <21 || 22”}
npm ERR! notsup Actual: {“npm”:“10.5.0”,“node”:“v21.7.3”}

You are using an unsupported nodejs version: 21.x

MM needs either 20.9.0 or any 22.x

@Ray the number of calls depend on the update intervall you set in your config. For example if you have it update every 10 minutes it will be 144 calls a day.

@sdetweil yes - all that is needed is …/2.5/… -> …/3.0/…

@sdetweil https://github.com/Tom-Hirschberger/MMM-OpenWeatherForecast/blob/master/MMM-OpenWeatherForecast.js#L53

@sdetweil MMM-OpenWeatherForecast has V2.5 as default.

@kent79 V3 is free for 1000 calls a day and unless you update the weather every minute you probably won’t reach that limit.

@kent79 from openweathermap.com:

"Dear OpenWeather user,

We would like to inform you about our plans to complete the migration from One Call 2.5 to One Call 3.0 that started 2 years ago. In line with this, access to One Call 2.5 will be finally closed in June 2024.

One Call 3.0 provides you with significantly advanced business-demanded features such as a minute forecast for 1 hour, 4 days forecast for any timestamp, a daily forecast for 8 days, including a human-readable summary, historical data (45-year archive) for timestamps, and with daily aggregation, 1.5-year long-term forecast with daily aggregation, and others."

So V2.5 is only working because openwaethermap didn’t fully shut it down even the deadline is over. It can happen any day.

@kent79 Did you get a new V3 API key at openweathermap.com? Old V2.5 keys won’t work anymore.

@kasperb what version of nodejs are you using?

what does the following command say:

nodejs -v

The module was recently changed to use a nodejs internal method to get the data, but your nodejs might be outdated.

@froboz @Ray make sure you have the following parameter in your config:

apiBaseURL: “https://api.openweathermap.org/data/3.0/onecall?”

and get a V3 API key from https://openweathermap.org/