@sdetweil

Yes, real Lat:Lon used

@sdetweil

This gives the ‘undefined, invalid date’ error on the MM

		{
			module: 'weather',
			header: 'Current xxxxxxxxxxxxxxx  weather: ',			
			position: 'top_right',
			config: {
				weatherProvider: "openweathermap",
				lat: 11111111, 
				lon:   2222222,
				apiKey: "33333333333"

			}
		},

@sdetweil

[2025-02-02 21:35:32.330] [INFO]  Checking modules structure configuration ... 
[2025-02-02 21:35:32.511] [ERROR] Cannot read properties of undefined (reading 'units') 

Module says:

units: config.units,

And also tried with

units: metric,

Which failed with:

[ERROR] metric is not defined 

config.js towards the beginning says:

units: 'metric',

@sdetweil said in MMM-SystemMonitor:

npm run config:check

pi@mmv2:~ $ npm run config:check 
npm error code ENOENT
npm error syscall open
npm error path /home/pi/package.json
npm error errno -2
npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/home/pi/package.json'
npm error enoent This is related to npm not being able to find a file.
npm error enoent
npm error A complete log of this run can be found in: /home/pi/.npm/_logs/2025-02-02T19_09_35_627Z-debug-0.log
pi@mmv2:~ $ 

@sdetweil said in Version 2.30.0 weather module, stuck loading, worked fine before upgrade:

leave off those parms.

Which ones, sorry?

@sdetweil

It’s the currently misbehaving weather forecast:

		{
			module: 'weather',
			position: 'top_right',
			header: 'Weather Forecast for: ',
			config: {
				type: 'forecast',
				location: 'nnnnnnnnn',
				locationID: '11111111',  //ID from https://www.openweathermap.org
				apiKey: 'aaaa444444444444444444'
			}
		},

		//{
            //module: 'MMM-SystemMonitor',
            //position: 'bottom_right',
            //config: {
                //updateInterval: 60000,

Installed, added to config.js

		{
            module: 'MMM-SystemMonitor',
            position: 'bottom_right',
            config: {
                updateInterval: 60000,
                cpuThermalZone: 0,
                units: config.units,
            }
        },

MM fails to load.
Comment those lines out, MM is OK. What have I missed?

@sdetweil said in Version 2.30.0 weather module, stuck loading, worked fine before upgrade:

ionToHeader: false

default config sample works, but that’s using openmeteo, not openweathermap, is that correct?

		{
			module: "weather",
			position: "top_right",
			config: {
				weatherProvider: "openmeteo",
				type: "current",
				lat: 40.776676,
				lon: -73.971321
			}
		},
		{
			module: "weather",
			position: "top_right",
			header: "Weather Forecast",
			config: {
				weatherProvider: "openmeteo",
				type: "forecast",
				lat: 40.776676,
				lon: -73.971321
			}
		},
		{

openweathermap.js I have as

		apiVersion: "3.0",
		apiBase: "https://api.openweathermap.org/data/",
		// weatherEndpoint is "/onecall" since API 3.0
		// "/onecall", "/forecast" or "/weather" only for pro customers
		weatherEndpoint: "/onecall",

Ran the update, weather module failed , read this thread and can now have either weather or forecast. Can we no longer have both, like before?

Just changed OS to Bookworm and reinstalled MM, stuck with weather modules loading…
For me, @postb8822 's 29th April 2024 suggestion worked just fine, thank you :)