"Invalid Date" appears in Weather module. MM v2.29.0

[sdetweil]

@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)

[sdetweil]

@reilley this was with the config.js.sample copied as another

units to imperial
copy/paste your config over the two weather module entries
add my apikey

then

# use env var to point to other config file
export MMM_CONFIG_FILE=config/name_of_file.js
npm start 

[sdetweil]

@reilley technically you don’t need apiVersion or weatherEndpoint, as those are the defaults.

[sdetweil]

@reilley that time is the sunrise or sunset time, sunrise is next, time is correct(in my display)

[reilley]

@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.

[sdetweil]

@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

[reilley]

@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.

[sdetweil]

@reilley I don’t know… try my approach
do

cd ~/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 window

export MM_CONFIG_FILE=config/testcfg.js
npm start 

[reilley]

@sdetweil - nope, same result

[sdetweil]

@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 field

look for any messages

[reilley]

@reilley - oh, I think I know what’s wrong now.

[reilley]

@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!

[sdetweil]

@reilley glad you found it!

[cgillinger]

@reilley I just realized I experienced something similar, but I was preoccupied with other tasks and didn’t take the time to investigate.

Here’s a screenshot for reference:
https://github.com/cgillinger/MMM-WeatherEffects/blob/main/screenshots/rich.png

Based on my screenshots (as mentioned, I was focused on tweaking the module and only noticed it afterward), it seems to be intermittent.

I’m using api-free providers, eg SMHI.

[VinGroot]

I have the same issue. These are my settings:

  module: "weather",
  position: "top_right",
  config: {
    lat: "52.262524",
    lon: "6.797571",        
    apiKey: "****",
    appendLocationNameToHeader: false,
    type: "current",
    degreeLabel: true,
    decimalSymbol: ",",
    showWindDirection: false,
    showFeelsLike: false

[sdetweil]

@VinGroot current release is 2.30 . still happening there ?

[VinGroot]

@sdetweil yes, still happening.
just noticed this second page, trouble shooting now. I get a 401 unauthorized error.

[sdetweil]

@VinGroot well 401 means apikey not right

[VinGroot]

I figured it out. I use the free plan, so I cannot use API version 3.0. I have to use API version 2.5. Furthermore I have to use the /weather endpoint.

I got it working again by adding these 2 settings:

apiVersion: '2.5'
weatherEndpoint: "/weather"

[sdetweil]

@VinGroot awesome