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 suddenly stopped working #2948

Closed
7 tasks done
DarthSonic opened this issue Oct 30, 2024 · 5 comments
Closed
7 tasks done

[Bug]: Waste Collection Schedule suddenly stopped working #2948

DarthSonic opened this issue Oct 30, 2024 · 5 comments

Comments

@DarthSonic
Copy link

DarthSonic commented Oct 30, 2024

I Have A Problem With:

The integration in general

What's Your Problem

Existing integration and configuration (by UI) does not work anymore. Entities are not available anymore, and when trying to configure again "500 Internal Server Error Server got itself in trouble" is thrown as error.

image

image

Source (if relevant)

No response

Logs

Logger: homeassistant.components.calendar
Quelle: helpers/entity_platform.py:361
Integration: Kalender (Dokumentation, Probleme)
Erstmals aufgetreten: 13:22:34 (1 Vorkommnisse)
Zuletzt protokolliert: 13:22:34

Error while setting up waste_collection_schedule platform for calendar
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 361, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/config/custom_components/waste_collection_schedule/calendar.py", line 165, in async_setup_entry
    entities = create_calendar_entries([shell], coordinator=coordinator)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/waste_collection_schedule/calendar.py", line 129, in create_calendar_entries
    dedicated_calendar_types = shell.get_dedicated_calendar_types()
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'get_dedicated_calendar_types'
Logger: homeassistant.components.sensor
Quelle: helpers/entity_platform.py:361
Integration: Sensor (Dokumentation, Probleme)
Erstmals aufgetreten: 13:22:34 (1 Vorkommnisse)
Zuletzt protokolliert: 13:22:34

Error while setting up waste_collection_schedule platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 361, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/config/custom_components/waste_collection_schedule/sensor.py", line 76, in async_setup_entry
    _LOGGER.debug("Adding sensors for %s", coordinator.shell.calendar_title)
                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'calendar_title'

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.
@5ila5
Copy link
Collaborator

5ila5 commented Oct 30, 2024

may be the same issue as #2907

@DarthSonic
Copy link
Author

Downgrade ICS calendar to 5.0.3 with no success.
Upgraded ICS calendar to 5.0.4 again, and upgrade Waste Collection Scheduler to 2.4.0 without success.

Do not know what else to do. Do I need to reconfigure all schedules? Was a lot of work to get them configured the way I wanted them to be.

@ReneNulschDE
Copy link
Contributor

Did you really followed this procedure? This worked in nearly all of the cases in the last few days.

@DarthSonic
Copy link
Author

workaround fixed issue

@ReneNulschDE
Copy link
Contributor

OK. feel free to close the issue.

@5ila5 5ila5 closed this as completed Oct 31, 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

No branches or pull requests

3 participants