Read the statement by Michael Teeuw here.
"Invalid Date" appears in Weather module. MM v2.29.0
-
@reilley that time is the sunrise or sunset time, sunrise is next, time is correct(in my display)
-
@sdetweil said in "Invalid Date" appears in Weather module. MM v2.29.0:
@reilley I copied your config and used my apikey
no other changes (well I wrapped your config in code block to keep the quotes correct for copy/paste)
So my code worked for you and the only change was the API key? This key worked two days ago, so not sure what’s happening here.
-
@reilley said in "Invalid Date" appears in Weather module. MM v2.29.0:
So my code worked for you and the only change was the API key?
correct
-
@sdetweil said in "Invalid Date" appears in Weather module. MM v2.29.0:
@reilley said in "Invalid Date" appears in Weather module. MM v2.29.0:
So my code worked for you and the only change was the API key?
correct
That’s nuts. Why would an API key work two days ago and not today? Seems like maybe there’s a configuration problem elsewhere but I not sure where it would be since I made no changes to weather.js or other .js files associated with the Weather module.
-
@reilley I don’t know… try my approach
docd ~/MagicMirror/config cp config.js.sample testcfg.js cd ..then edit the testcfg.js and paste your weather info from config.js here
then change the units to imperial
save
then on the terminal windowexport MM_CONFIG_FILE=config/testcfg.js npm start -
@sdetweil - nope, same result
-
@reilley ok, next thing
weather is done all in browser,
on the MagicMirror screen ctrl-shift-i to
open the developer window, select the console tab,
put wea in the filter fieldlook for any messages
-
@reilley - oh, I think I know what’s wrong now.
-
@sdetweil - you’re gonna laugh, but I found the issue. I was using an inactive API key. My backup was too old and was before the v2.29.0 API 3.0 requirement. Sorry to drag you through this!
-
@reilley glad you found it!
