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]: Ecoharmonogram Integration Error: "day is out of range for month" - Bestwina, Poland #3757

Open
4 of 7 tasks
prezesBB opened this issue Feb 10, 2025 · 0 comments
Open
4 of 7 tasks

Comments

@prezesBB
Copy link

I Have A Problem With:

A specific source

What's Your Problem

I am experiencing an issue while trying to configure the ecoharmonogram integration for the location:

Town: Bestwina
District: Bestwina

When attempting to set up the integration for this specific address, I encounter the following error message:

The source returned an invalid response: "day is out of range for month". Please check the provided arguments and try again.
This error prevents successful configuration and data retrieval for the specified location.

It appears there might be an issue with how the system is processing date information for this particular region or address within the ecoharmonogram data source.

Source (if relevant)

ecoharmonogram

Logs

Relevant Configuration

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