Read the statement by Michael Teeuw here.
MMM-WunderGround - not appearing in Mirror
-
I was hoping someone could help me…
I have been trying to setup MMM-WunderGround on my mirror but have been unsuccessful so far.Here is my config:
{ module: 'MMM-WunderGround', // Just for forecast w/css entry position: 'top_right', config: { apikey: 'xxxxxxxxxxxxxxxx', // apikey from weatherunderground pws: 'pws:IPORTSMO30', // location currentweather: 0, coloricon: true, hourly: '1', fctext: '1', fcdaycount: "10", fcdaystart: "0", hourlyinterval: "2", hourlycount: "1", animationSpeed: 5000, alerttime: 10000, alerttruncatestring: "english:", roundTmpDecs: 0, UseCardinals: 1, layout: "vertical", windunits: "mph", sysstat: "0" } },
Everything else in my config file is booting properly and working fine.
Regarding the API key - from the weather underground page I have subscribed to the anvil plan and have got my ‘API Key’ which is a 16 alphanumerical code and this is what I am using, is this correct? See screenshot below:When booting the logs show no errors and do not refer to the MMM-WunderGround module at all. The only other thing I can think of is I am still using the default ‘current weather’ and ‘weather forecast’ modules in my config.js - could it be that these are conflicting with the MMM-WunderGround module? EDIT: I have commented out these two modules and tried again - still the same so I don’t think these are the problem.
I have tried everything previously mentioned in the recent weather underground post (https://forum.magicmirror.builders/topic/2292/problem-with-weather-underground-forecast/18).
Can anyone assist please? I have run out of ideas.
-
Hi!
Did your log show errors similar to:
0|mm | WARNING! Could not validate config file. Please correct syntax errors. Starting with default configuration.
In your post above there are weird (double) quotes that proved problematic when trying your config. This one works fine on my setup:
module: "MMM-WunderGround", position: "top_right", header: "", config: { apikey: "xxxxxxxxxxxxxxxx", pws: "pws:IPORTSMO30", currentweather: 0, coloricon: true, hourly: "1", fcdaycount: "10", hourlyinterval: "2", hourlycount: "1", animationSpeed: 5000, alerttime: 10000, alerttruncatestring: "english:", roundTmpDecs: 0, UseCardinals: 1, windunits: "mph", sysstat: "0" } },
Good luck! -
Hi Thanks for the reply - I have tried your config and am still having the same result, the module does not show up at all.
I am not seeing any error either regarding the config.js file…
This leads me to believe it must be something to do with the api key. Are you able to talk through exactly what to do to set the key up? I think I have done it right (see screenshot in first post) but may be missing something… How many characters is your api key? -
I had the same issue and the fix was so dumb it had me smacking my head. The MMM-WeatherUnderground did not end up in the modules folder after my git pull. Moved it from where it was into the modules folder and “poof” like magic it worked.
-
@sithlordhood do you get any ui elements saying loading or something?
did you run npm install in the mmm-wunderground directory?
did you check the path like @Sunburned mentioned?
can you share your logs? -
@strawberry-3.141 Thanks for replying…
I tried npm install in the MMM-WunderGround directory but it failed (I don’t think there are any dependencies that require installing?)
I checked the path and the directory was there however it was named ‘MMM-Wunderground’ and in the config.js I call ‘MMM-WunderGround’. I changed the directory name to ‘MMM-WunderGround’ and the module now loads!Funnily enough before this I tried changing the config.js file to match the directory name and this did not work, I had to change the directory name to add the capital letter to the U.
Thanks all for your help, finally sorted!
-
The case sensitivity was my issue too! I think I pulled the github down *Wunderground* it installed with the folder name in lowercase, but the files themselves *WunderGround* and I was using MMM-Wunderground in my config.
Once I symlinked the correct capitalization, and corrected my config, it works perfectly.20 years using linux, one would think I would catch this myself!
Thanks for asking the right questions! This thread got me up and running.