How many user defined (static) sources are supported?

[michaelmikelas]

Per the title... how many user defined sources can we configure? I have two working without issue but if I go to add a third, that uses nearly the exact same YAML config as my first entry... HA reboots with errors. Thought is to use the integration to track changing the cat litter and replacing their water in their fountain on top of regular garbage and recycling pickups...

# Garbage Integration
waste_collection_schedule:
  sources:
    - name: static
      args:
        type: Waste
        frequency: WEEKLY
        weekdays: TU
      customize:
        - type: Waste
          icon: phu:garbage-residual
    - name: static
      args:
        type: Recycling
        frequency: WEEKLY
        interval: 2
        start: '2023-06-20'
        until: '2050-12-31'
      customize:
        - type: Recycling
          icon: mdi:recycle
#    - name: static
#      args:
#        type: Litter
#        frequency: WEEKLY
#        interval: 2
#        start: '2024-06-15'
#        until: '2050-12-31'
#      customize:
#        - type: Litter
#        - icon: mdi:cat
#    - name: static
#      args:
#        type:  CatFountain
#        frequency: WEEKLY
#        weekdays: SA
#      customize:
#        - type: CatFountain
#        - icon: mdi:fountain

This is the error on restart if I uncomment and enable the Litter static entry above:

Logger: homeassistant.setup
Source: setup.py:402
First occurred: 1:38:41 PM (1 occurrences)
Last logged: 1:38:41 PM

Error during setup of component waste_collection_schedule
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 402, in _async_setup_component
    result = await task
             ^^^^^^^^^^
  File "/config/custom_components/waste_collection_schedule/__init__.py", line 105, in async_setup
    waste_type=c[CONF_TYPE],
               ~^^^^^^^^^^^
KeyError: 'type'

[5ila5]

There is no limit. Your problem is - icon: mdi:cat which starts a new list (-). This means the icon parameter is treated as a separate customization which does not have the type argument, so you get this error message that means that it tried to get the type parameter from this customization but did not get it.

json equivalent

working configuration :

"customize": [
  { 
    "type": "Recycling",
    "icon": "mdi:recycle"
  }
]

your not working configuration:

"customize": [
  { 
    "type": "Litter"
  },
  {
    "icon": "mdi:cat"
  }
]