Integrate with ERZ (Zürich waste collection)

[harrolf]

Zurich waste collection has its own API and is already integrated in HA, however it would be great to have it through this custom component with all its benefits.

Related documents:

• https://www.stadt-zuerich.ch/portal/de/index/ogd/anwendungen/2019/open_erz_api.html
• http://openerz.metaodi.ch/documentation
• https://github.com/metaodi/openerz

[5ila5]

The API looks pretty good, but do you know if there is an easy way for users to get their area (which seems to be required by the API)?

We don't even need to implement a dedicated source, as we can just use the ICS source like this:

waste_collection_schedule:
  sources:
    - name: ics
      args:
        params:
          area: 8048
          region: zurich
          zip: 8048
        regex: (.*), .*
        url: https://openerz.metaodi.ch/api/calendar.ics?types=bulky_goods&types=cardboard&types=cargotram&types=chipping_service&types=etram&types=incombustibles&types=metal&types=oekibus&types=organic&types=paper&types=special&types=textile&types=waste&sort=date&offset=0&limit=500

I want to add documentation for this and added a PR here: #1726
Could you have a look if you want to change something

[harrolf]

Interesting I've never used the calendar.ics endpoint before.

I usually use on the these 3 options:

1. openerz platform in HASS (waste type specific)

- platform: openerz
  name: Paper
  zip: 8044
  waste_type: paper

2. rest platform in HASS

- platform: rest
  name: Recycling Cardboard
  icon: mdi:package-variant
  resource: https://openerz.metaodi.ch/api/calendar.json
  scan_interval: 43200
  value_template: "{{ value_json.result[0].date }}"
  params:
    zip: 8044
    types: cardboard
    limit: 2
    start: "{{ now().strftime('%Y-%m-%d') }}"
  json_attributes_path: "$.result.[0]"
  json_attributes:
    - date
    - waste_type
    - zip
    - area
    - station
    - region
    - description

3. curl (returns all, with only zip code as area)

https://openerz.metaodi.ch/api/calendar.json?zip=8044&start={{currentdate}}

[5ila5]

Using the ICS endpoint has the advantage of just using existing logic, and we do not have to write a dedicated source. I'd like to keep this approach if you do not see a flaw in this approach. I put the types and all the parameters you probably don't like to change in the URL part and the parameters you want to change in the parameters section.

We could add all the supported regions in an extra_info parameter, they then will be shown in the README.md as separate entry. Do you think this would make sense?

[harrolf]

I suppose it would be great to be able to have the following parameters:

• zip
• waste_type (personally I'm only interested in paper and cardboard)

Thanks for the effort!