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

[Bug]: City of Stirling, Error 404 #3215

Open
7 tasks done
rainbowsnail99 opened this issue Dec 16, 2024 · 0 comments · May be fixed by #3260
Open
7 tasks done

[Bug]: City of Stirling, Error 404 #3215

rainbowsnail99 opened this issue Dec 16, 2024 · 0 comments · May be fixed by #3260

Comments

@rainbowsnail99
Copy link

I Have A Problem With:

A specific source

What's Your Problem

Appears that City Of Stirling have moved their API from https://www.stirling.wa.gov.au/aapi/map to https://www.stirling.wa.gov.au/bincollectioncheck/getresult

Looks like the API might need to be changed over, (hopefully) a quick win!

image
image

Source (if relevant)

stirling_wa_gov_au

Logs

The source returned an invalid response: "404 Client Error: Not Found for url: https://www.stirling.wa.gov.au/aapi/map". Please check the provided arguments and try again.

Relevant Configuration

Example Address:
20 Kingfisher Pl, Stirling WA 6021

Example Lat, Lng:
-31.878331, 115.815553

Checklist Source Error

  • Use the example parameters for your source (often available in the documentation) (don't forget to restart Home Assistant after changing the configuration)
  • Checked that the website of your service provider is still working
  • Tested my attributes on the service provider website (if possible)
  • I have tested with the latest version of the integration (master) (for HACS in the 3 dot menu of the integration click on "Redownload" and choose master as version)

Checklist Sensor Error

  • Checked in the Home Assistant Calendar tab if the event names match the types names (if types argument is used)

Required

  • I have searched past (closed AND opened) issues to see if this bug has already been reported, and it hasn't been.
  • I understand that people give their precious time for free, and thus I've done my very best to make this problem as easy as possible to investigate.
@dt215git dt215git linked a pull request Dec 22, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant