MM 2.11.0 Invalid Date error with weather module

sdetweil

@Jarhead96097 if there are true/false values in config, they should not be quoted

Jarhead96097

@sdetweil thank you. I’ll make the corrections.

Jarhead96097

Is there a way for me to check the forecast data from the local weather station? Since I’m only getting the error using the “weathergov” source, and it’s only happening with the first of two weather instances… I’m wondering if the underlying data might be the issue. The only problem with that theory is that the error is constant, across all of the forecasts I’ve received since rebuilding MM using version 2.11.0.

sdetweil

@Jarhead96097 you can read the code and try to build the request url string that you could put into the browser on your pc to get the response to examine…

there are no prebuilt tools for this

Jarhead96097

@sdetweil Thank you for such quick responses…I do appreciate it! Here’s the link: https://api.weather.gov/gridpoints/MFR/104,44/forecast/hourly and here’s a snippet of the return that includes the dates and times that end up (apparently) causing the invalid date error:

"properties": {
    "updated": "2020-06-05T01:18:34+00:00",
    "units": "us",
    "forecastGenerator": "HourlyForecastGenerator",
    "generatedAt": "2020-06-05T04:36:11+00:00",
    "updateTime": "2020-06-05T01:18:34+00:00",
    "validTimes": "2020-06-04T19:00:00+00:00/P7DT17H",
    "elevation": {
        "value": 868.98480000000006,
        "unitCode": "unit:m"
    },

Based on what I can compare against the moment.js documentation, I don’t see anything obvious that would cause the error.