New Module MMM-PWSWeather

Reply to New Module MMM-PWSWeather on Sat, 30 May 2026 16:31:41 GMT

sdetweil — Sat, 30 May 2026 16:31:41 GMT

@msimon360
in linux, environment variables are not inherited by default.

you have to use

export variable_name=value

in the shell script before the launch of MM

variable_name=value

will not be passed to the next program

Reply to New Module MMM-PWSWeather on Sat, 30 May 2026 15:31:12 GMT

msimon360 — Sat, 30 May 2026 15:31:12 GMT

@sdetweil I have a weather provider working now. When I try to use $SECRET_PWS_API_KEY in my config.js it doesn’t work. I export the var in my .bashrc and I am using pm2 to start mm.

Reply to New Module MMM-PWSWeather on Tue, 02 Jun 2026 18:35:34 GMT

sdetweil — Tue, 02 Jun 2026 18:35:34 GMT

@msimon360 if the modules provide multi instance support (pretty easy) then you don’t have to do the copying

on the sendSocketNotification from module to node_helper, send some unique key, typically this.identifier will work
when the node helper sends the response, it add the id it received…
And
the module in
socketNotificationReceived, check the ID against its value… if no match, ignore it

sendSocketNotification from the helper goes to ALL instances of the module at the SAME TIME
see https://docs.magicmirror.builders/module-development/node-helper.html#module-instance-methods

so it will have to check if the data is intended for its instance ID
(doc above Note: Since all instances of your module will receive the notifications, it’s your task to make sure the right module responds to your messages.)

generally a couple lines of code in the helper and in the module
sometimes, really modularized node_helpers need to pass if from request to response functions… (one of mine is like that)

Reply to New Module MMM-PWSWeather on Fri, 29 May 2026 18:14:05 GMT

msimon360 — Fri, 29 May 2026 18:14:05 GMT

@sdetweil This is great. Is it only for weather? It would be cool if all modules could be like this. You could define data providers and then data displays. Maybe in the modules directory or another directory define a pair with a unique name to work like a module does now. That way you could define providerA with displayA as module1 and providerB with displayA as module2. This would end copying modules and renaming them do display different data in the same way.

Reply to New Module MMM-PWSWeather on Fri, 29 May 2026 16:23:36 GMT

sdetweil — Fri, 29 May 2026 16:23:36 GMT

@msimon360 here is the link for the new weather provider
https://docs.magicmirror.builders/module-development/weather-provider.html
this doc is new, so any feedback is welcomed,

and the doc for the themes
https://docs.magicmirror.builders/modules/weather.html#themes

basically the provider does the data acquisition (fetch) of the data , now in the server side, so multiple module instances can use the same last fetched data to keep the fetch count down

and the optional theme does the custom display (if you don’t want to use the default theme)

Reply to New Module MMM-PWSWeather on Fri, 29 May 2026 14:54:18 GMT

msimon360 — Fri, 29 May 2026 14:54:18 GMT

@sdetweil I didn’t know about themes for weather. I will separate my module into a provider and a theme. I use pages with my mirror and want to display both weather from the default provider and from my personal weather station. How best to go about this?

Reply to New Module MMM-PWSWeather on Wed, 27 May 2026 18:41:17 GMT

sdetweil — Wed, 27 May 2026 18:41:17 GMT

@msimon360 said:

I don’t know how to get it added to the 3rd-Party-Modules page.

you edit the wiki at https://github.com/MagicMirrorOrg/MagicMirror
and add your month entry to the appropriate section.

overnight the 3rd party processor will add it to the searchable list

any reason you made a complete module, vs another provider in the default weather module?