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]: Documentation Update Required for Uttlesford Source #2323

Closed
7 tasks done
drnichols opened this issue Jul 22, 2024 · 0 comments · Fixed by #2340
Closed
7 tasks done

[Bug]: Documentation Update Required for Uttlesford Source #2323

drnichols opened this issue Jul 22, 2024 · 0 comments · Fixed by #2340

Comments

@drnichols
Copy link

drnichols commented Jul 22, 2024

I Have A Problem With:

A specific source

What's Your Problem

The sources returned for the uttlesford_gov_uk source appear to have changed from the those in the documentation;

Current Documentation Lists:

Black (Non-Recyclable)
Green (Recycling)
Brown (Food)

Source is returning;

Black (Non-Recyclable)
Green (Dry Recycling)
Brown (Food Waste)

Source (if relevant)

No response

Logs

No response

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant