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]: Auckland Council only showing 2 weeks post update #2065

Open
3 of 7 tasks
PHamiltonNZ opened this issue May 7, 2024 · 3 comments
Open
3 of 7 tasks

[Bug]: Auckland Council only showing 2 weeks post update #2065

PHamiltonNZ opened this issue May 7, 2024 · 3 comments

Comments

@PHamiltonNZ
Copy link

I Have A Problem With:

The integration in general

What's Your Problem

After the last update, Auckland council started showing up again in my calendar but only for the next 2 weeks, there are no further entries after that.

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

5ila5 commented May 8, 2024

This kinda is intended behavior as the new implementation parses the website which only offers dates for the next collection. We could parse the information below the table saying how often a waste type is collected, but this adds a potential breaking point

for the detailed update PR see #1968

@PHamiltonNZ
Copy link
Author

Ah I see, that's great. Thanks for letting me know

@Agent6-6-6
Copy link

Agent6-6-6 commented May 8, 2024

@5ila5, @PHamiltonNZ - There is a slight issue I am seeing with how it works currently by default.

Given only one date is given on the Auckland council website, it cannot obviously parse the next date. So if you accept the default day_switch_time of 10am, it shows up as unknown until the website updates as the next date isn't available to display.

Example of the behaviour I'm seeing and my configuration:-
Screenshot 2024-05-09 105126
Screenshot 2024-05-09 105145

  sources:
    - name: aucklandcouncil_govt_nz
      args:
        area_number: 12342484543
      customize:
        - type: rubbish
          alias: Rubbish
          icon: mdi:trash-can
        - type: recycle
          alias: Recycling
          icon: mdi:recycle
        - type: food-waste
          alias: Food Scraps
          icon: mdi:food-apple
      calendar_title: Auckland Council Rubbish & Recycling Collections

sensor:
  - platform: waste_collection_schedule
    name: Rubbish Collection Date
    types:
      - Rubbish

  - platform: waste_collection_schedule
    name: Recycling Collection Date
    types:
      - Recycling

  - platform: waste_collection_schedule
    name: Food Scraps Collection Date
    types:
      - Food Scraps

The only obvious way I can think of to deal with it is to set the day_switch_time variable to say 11:59PM or somehow pickup the unknown result and display something else. Have not waited a week to see if that works though.

Wondering how how are others dealing with this?

Not sure if this can be dealt with in a more gracious way by the addon itself, even if there is a reluctance to parse further information on the website as noted above.

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