Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Endpoint Error #1693

Closed
secastles opened this issue Jun 4, 2019 · 2 comments
Closed

Endpoint Error #1693

secastles opened this issue Jun 4, 2019 · 2 comments

Comments

@secastles
Copy link

PPlatform: Electron 5.0.2 / Raspberry Pi 3 B+ / Stretch.

Node Version: 10.15.3

MagicMirror Version: JavaScript version (v2).

Description: The forecastEndpoint param is configured to "forecast/daily." However, this throws an error when I manually create the URL and enter it into a browser (invalid API key response). If I change the endpoint to "forecast" per the 5-day forecast API documentation the call works fine. The "forecast/daily" endpoint is for paid accounts.

However, using the "forecast/daily" endpoint in the module code doesn't throw an error. I get a forecast, with the correct city name (I'm using the city ID in the config), but the forecast doesn't seem correct; it doesn't match the forecast from the openweathermap website. If I look at the raw data returned in browser from the 5-day forecast API ("forecast" endpoint) it's not clear which data the module is pulling. In fact, looking at the code, it doesn't seem like the module should be working at all with the 5-day forecast API. So, I guess my question is this: does this module require a paid 16-day forecast account? I'm using a free account API key and (1) the forecast seems incorrect and (2) the module code seems to be for the 16-day forecast endpoint which requires a paid account.

Configuration: Nothing special; using a free openweathermap account

@secastles
Copy link
Author

I just went back and looked at previous issues and it appears this might already be addressed by #1513. If that's the case I'll close this one.

@secastles
Copy link
Author

Yep, my bad. I was using weatherforecast and not weather.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant