Read the statement by Michael Teeuw here.
Weatherunderground - currently - hourly - daily - configurable
-
I cloned your repo to MMM-WunderGround and edited the module name also. Now it works. You should change your Readme.
Thanks for the cool module ;).
-
@djsunrise19 Thanks for spotting my mistake :D I’ve modified the readme accordingly. Enjoy!
-
it’s taking me forever but How do i change pws: ‘locid:’ for san francisco? I cant find the location ID for my city using google
-
Can be any WU api location info.
US Example:
NY/New_York
Example:locid:NLXX8014;loctype:1
so just change it to
CA/San_Francisco
-
I’m getting a blank screen. Any idea why?
{ module: 'MMM-WunderGround', position: 'top_right', header: 'Weather Forecast', config: { apikey: 'a1fa37eaff91b5450c', pws: 'CA/San_Francisco', fctext: '1', fcdaycount: '5', fcdaystart: '0', hourly: '1', hourlyinterval: '3', hourlycount: '2', alerttime: 1000, alerttruncatestring: 'english:' } },
-
Config looks good, could you have a look at your logs?
See here for some troubleshootign info: https://forum.magicmirror.builders/topic/86/how-to-troubleshoot
-
@MagicCrumps1 On the other hand, you api key seems to be invalid. (if the key in your post is indeed your key):
{ "response": { "version":"0.1", "termsofService":"http://www.wunderground.com/weather/api/d/terms.html", "features": { } , "error": { "type": "keynotfound" ,"description": "this key does not exist" } }
-
This post is deleted! -
@RedNax Still not working. Sorry, I should have included that I added a few extra keys to my personal api key thus making them invalid.
Loading config … Loading module helpers … No helper found for module: alert. No helper found for module: clock. Initializing new module helper … No helper found for module: compliments. No helper found for module: currentweather. No helper found for module: MMM-WunderGround. Initializing new module helper … All module helpers loaded. Starting server op port 8080 … Server started … Connecting socket for: calendar Starting node helper for: calendar Connecting socket for: newsfeed Starting module: newsfeed Sockets connected & modules started … Launching application.
-
That looks like everything did load up properly there. There’s a way to look at electron’s console logs but I don’t know what the keystroke is (maybe CTRL-W?). But, at times like this, I find it’s easier/faster for me to debug by using a different machine with Chrome/Firefox and load up the mirror that way by going to the rpi’s IP and port: http://10.0.0.1:8080 (assuming your rpi’s IP is 10.0.0.1, change it to match yours.) Black screen or not, you can always hit F12 on a windows browser and pull up the console log. Look for Javascript errors.