@Cr4z33
Well dang. I’m doing something wrong here. Whether I use the helper config or the tool above, I get a broken error page.

And I know an error page is expected, but it’s not a long url with a code in it.
It’s like… amazon.com/wpa

and that’s it.

Was the right choice “device with alexa built in” and “no companion app” ? I figure I must have done something wrong on the Amazon developer page, since that’s the part with no guide and it’s working for other people.

@Cr4z33
Oddly that’s not working for me either. Maybe I’m doing something wrong?

What should I be using for the Device ID? I’ve been using the product ID, but maybe that’s wrong.

@Canterrain said in MMM-awesome-alexa:

Trying to finish setup of the module.

I’m in the helper config, and when I get to the point of supplying a return URL I enter:
https://localhost:3000/authresponse
But terminal tells me that’s an invalid URL.

I’ve put https://localhost:3000/authresponse as my return URL and https://localhost:3000/ as my authorized URL on the Amazon developer site. What I am I doing wrong here?

Bump on this question, still can’t get past the local url section. Any help would be appreciated.

Trying to finish setup of the module.

I’m in the helper config, and when I get to the point of supplying a return URL I enter:
https://localhost:3000/authresponse
But terminal tells me that’s an invalid URL.

I’ve put https://localhost:3000/authresponse as my return URL and https://localhost:3000/ as my authorized URL on the Amazon developer site. What I am I doing wrong here?

Ah yeah! That’s totally that problem.

Now if I could just get the rest figured out, I could go with the new module.

I’m having trouble with the new weather module. I don’t want a header above the current forecast (like the old current weather didn’t have), but it’s trying to stick one up there. I’m also seeing an invalid date error. Also, despite listing 7 days for my forecast, I’m only getting 5.

Basically this:

Here’s my weather config:

{
			module: 'weather',
			position: 'top_right',
			config: {
				type: 'current',
				roundTemp: 'true',
				degreeLabel: 'true',
				appendLocationNameToHeader: 'false',
				weatherProvider: 'weathergov',
				apiBase: 'https://api.weather.gov/points/',
				weatherEndpoint: '/forecast/hourly',
				lat: '39.2689476',
				lon: '-84.263826'
			}
		},
		{
			module: 'weather',
			position: 'top_right',
			header: 'Weather Forecast',
			config: {
				type: 'forecast',
				appendLocationNameToHeader: 'true',
				fade: 'true',
				days: '7',
				weatherProvider: 'weathergov',
				apiBase: 'https://api.weather.gov/points/',
				weatherEndpoint: '/forecast',
				lat: 'xx.xxxxx',
				lon: '-xx.xxxx'
			}
		},

(where x’s are my lat and lon)

any help appreciated.

Looks like the recent changes here are the culprit. They already figured out what needs to be changed, fixed in an upcoming update. Pull request is in. Get ready to update your mirrors.

I had an openweather api before they changed the rules. But I’m not sure if they’re starting to lock it down more or what, but the forecast has broken (invalid date error), and nothing seems to fix it (had entries in troubleshooting).

I have have switched to the https://github.com/dmcinnes/MMM-forecast-io
module, and if anything its weather results are more accurate.

But I miss the look of the default modules. The above module has done a fine job, but the defaults are more cohesive.

Considering you can’t get openweather apis anymore, or even weatherunderground apis, anyone want to take a whack at getting the default weather/weather forecast modules to use the dark sky api?

https://darksky.net

Thanks!

Thanks for the helpful suggestions.

Date and time are correct on my pi, and the mirror even shows the right date and time.

The config did have the missing ’ in current weather, I apparently accidentally deleted it when I was removing personal info. I edited the above to reflect the current status of my config file.

This was working fine before. About the time I updated the mirror to latest version and added the motion detection module. But it didn’t happen immediately after those events. It was a few days later. I did find a logged issue (that was closed) describing the same thing, after updating the mirror.

No luck adding the comma unfortunately.

You mentioned 2 things to try, what was the second?

Thanks for looking at this.