Sensor config: Should type be alias?

[pmharris77]

I set up some customized aliases for my sources in my configuration.yaml like so:

waste_collection_schedule:
  sources:
  - name: welhat_gov_uk
    args:
      uprn: "*"
      postcode: "*"
     customize:
       - type: garden # source name
         alias: Garden Waste # my friendly name for  sensor state display

However, when I come to create sensors, it seems to be expecting the type field to be the source type alias, rather than the original source type (e.g. it expects "Garden Waste" instead of "garden") - if I just use the source type, the sensors have an "Unknown" state.

- platform: waste_collection_schedule
  name: next_garden_bin_collection
  types:
    - Garden Waste  # garden (original source type name) does not work
  add_days_to: true

Is this expected behaviour, or a bug? It doesn't seem to be documented anywhere that alias overrides the original source type name

[5ila5]

This is expected behavior. The alias argument changes the type directly after fetching the data. So the sensor does not know the original type returned by the source fetch script.

I added a comment to the sensor documentation that this is the aliased type (if alias provided) in #1906

[pmharris77]

@5ila5 Thanks very much!