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]: Error in Nottingham City Council, UK endpoint #2994

Closed
6 of 7 tasks
adam-blakey opened this issue Nov 5, 2024 · 1 comment
Closed
6 of 7 tasks

[Bug]: Error in Nottingham City Council, UK endpoint #2994

adam-blakey opened this issue Nov 5, 2024 · 1 comment

Comments

@adam-blakey
Copy link

adam-blakey commented Nov 5, 2024

I Have A Problem With:

Sensor configuration

What's Your Problem

A 500 error is returned by the current endpoint. This can be fixed with a simple change to the endpoint URL.

Source (if relevant)

nottingham_city_gov_uk

Logs

no relevant logs

Relevant Configuration

No response

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.
@adam-blakey
Copy link
Author

I'm sorry, I'm a complete idiot and have somehow missed that this was fixed with #2980.

@adam-blakey adam-blakey closed this as not planned Won't fix, can't repro, duplicate, stale Nov 5, 2024
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