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

Internal Service Error #208

Closed
3 tasks done
cloneofghosts opened this issue May 1, 2024 · 4 comments
Closed
3 tasks done

Internal Service Error #208

cloneofghosts opened this issue May 1, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@cloneofghosts
Copy link
Collaborator

cloneofghosts commented May 1, 2024

Describe the bug

The API has been returning an Internal Service Error message for my location. From my testing it seems to be only for those locations in the HRRR domain as it's still up for those locations outside of the domain.

If add HRRR to the excludes then the API returns data like normal confirming my suspicion that something with the HRRR model is causing the issue.

Expected behavior

API should return data for the requested location

Actual behavior

Internal Server Error message is shown instead

API Endpoint

Production

Location

Ottawa, Ontario

Other details

No response

Troubleshooting steps

  • I have searched this repository and Home Assistant Repository to see if the issue has already been reported.
  • I have read through the API documentation before opening this issue.
  • I have written an informative title.
@cloneofghosts cloneofghosts added bug Something isn't working Needs Review labels May 1, 2024
@carlos-sarmiento
Copy link

I'm also getting a 500 error from Pirate Weather. Don't know what HRRR is, but this URL fails (api key redacted):
https://api.pirateweather.net/forecast/xxxxxxxxxxxx/29.73,-95.65?units=si&extend=hourly&version=2

@rayvd
Copy link

rayvd commented May 1, 2024

Same also. Adding exclude=hrrr to the call seems to make things work.

@alexander0042
Copy link
Collaborator

I'm so sorry for this outage! I take uptime pretty seriously. so this is a big issue. What happened was a bug in my datetime rounding code failed because of the month rollover, and excluding HRRR fixed it since I don't have to round that one. It's back up and running now, and corrected so it won't happen again!

@cloneofghosts
Copy link
Collaborator Author

Can confirm everything is working again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

4 participants