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]: waste_collection_schedule.fetch_data no longer available #2294

Closed
7 tasks done
jackc94 opened this issue Jul 17, 2024 · 0 comments · Fixed by #2470
Closed
7 tasks done

[Bug]: waste_collection_schedule.fetch_data no longer available #2294

jackc94 opened this issue Jul 17, 2024 · 0 comments · Fixed by #2470

Comments

@jackc94
Copy link

jackc94 commented Jul 17, 2024

I Have A Problem With:

The integration in general

What's Your Problem

Since updating to v2.0.0 I reconfigured my integration using the GUI which generally went fine however I have noticed occasionally when the data fetch occurs the sensor goes to unknown… monitoring to see if this is a source issue or integration issue but previously running the waste_collection_schedule.fetch_data service would fetch the data and all would be well… this service no longer exists. Could you please reinstate it?

Source (if relevant)

South Oxfordshire District Council

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