Changing configuration parameter to sensor level

Having an idea about the configuration parameters, that I would like to discuss. We now have configuration parameters as lists and dictionaries. In each list we have to define a MAC address, like this:

sensor:
  - platform: mitemp_bt
    encryptors:
      'A4:C1:38:2F:86:6C': '217C568CF5D22808DA20181502D84C1B'
    sensor_fahrenheit:
      - 'C4:7C:8D:6B:4F:F3'
    sensor_names:
      'A4:C1:38:2F:86:6C': 'Livingroom'
    whitelist:
     - 'B4:7C:8D:6B:4F:D3'

I think it would make more sense to define this per sensor, something like this.

sensor:
  - platform: mitemp_bt
     automatic_add: False
     entities:
     - mac: 'A4:C1:38:2F:86:6C'
       encryption_key: '217C568CF5D22808DA20181502D84C1B'
       name: 'Livingroom'
     - mac: 'C4:7C:8D:6B:4F:F3'
       unit_of_measurement: fahrenheit
     - mac: 'B4:7C:8D:6B:4F:D3' 

I understand that this is a significant breaking change, but it has the advantage that we can expand this in a second step to define other parameters on sensor level, like rounding, median, etc.

I’m not saying that we have to make this change, but I see some advantages, despite the breaking change (and quite some work to make this change). Let’s first discuss @Magalex2x14 what you think of this idea and see where we end up.

[Magalex2x14]

Wow) Serious approach) I like it, yes.

[Ernst79]

I will have a look tomorrow what the usual parameter naming is. I’ve seen sensors, as well as entities, I thought. I used automatic_add, as it was a parameter for rfxtrx component. autodiscovery sound better, I agree. I will check the developer docs of home assistant.

For the rounding option, etc, we can make a parameter on component level, which can be overruled on sensor level (or perhaps even on temperature sensor/ humidity sensor level).

Lets start with the dictionaries and lists first. I will start looking into this and will make a separate branch for this.