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]: Cannot add Canterbury bin schedule after updates #3864

Open
7 tasks done
Spinax954 opened this issue Mar 5, 2025 · 0 comments
Open
7 tasks done

[Bug]: Cannot add Canterbury bin schedule after updates #3864

Spinax954 opened this issue Mar 5, 2025 · 0 comments

Comments

@Spinax954
Copy link

I Have A Problem With:

Sensor configuration

What's Your Problem

Whenever I try to add the source with the correct post code and house number, I'm receiving this error:

Source (if relevant)

canterbury_gov_uk

Logs

The source returned an invalid response: "403 Client Error: Forbidden for url: https://zbr7r13ke2.execute-api.eu-west-2.amazonaws.com/Beta/get-bin-dates". Please check the provided arguments and try again.

Relevant Configuration

When pasting the url into a browser, it suggests there is some sort of authentication token required

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.
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