New model: Aqara CL-L02D

[dagobert]

Device information

https://www.aqara-shop.co.uk/product/aqara-ceiling-light-t1m/

Home Assistant Device information

Checklist

• I have created a single PR per device. When you have multiple submissions please create separate PR's.
• For lights - I have only included the gzipped files (*.gz), not the raw CSV files.
• For lights - I have provided a CSV file per supported color mode. Look that up in Developer Tools -> States
• Fix identification problem for sub-profile first
• Main model.json needs testing before merge

Additional info

Measured with Docker and Shelly PM Mini Gen3.

[github-actions]

Thank you for submitting light measurements!
Here are some visualizations for the CSV files.

[dagobert]

RGB plots:

White plot:

[bramstroker]

@dagobert Is this still draft or ready for review?

[dagobert]

@dagobert Is this still draft or ready for review?

Still a draft. I have redone the measurements including standby last night. I will commit them tmr.

Also, I wanted to wait for the "more detail" being released to test configuring the lamp with it.

[dagobert]

I am using the newest .4 version and the my testing is done.

But I encountered now a new problem. The discovery now states entity name and not the device name any more. Hence, when I add the powercalc sensor it is named (entity_id) sensor.0x54ef441000b75814_rgb_rgb_light_energy with a double "rgb". This is due to the fact that I had to add

  "sensor_config": {
    "power_sensor_naming": "{} RGB Light Power",
    "energy_sensor_naming": "{} RGB Light Energy"
  }

to prevent the rgb light and the white light overwriting/usinf the same entity_id because, as we alked about, my discovered devices always only carried the device name not the entity name/id. Is it safe to remove "RGB" now for all possibilities of discovery names?

[bramstroker]

I am using the newest .4 version and the my testing is done.

But I encountered now a new problem. The discovery now states entity name and not the device name any more. Hence, when I add the powercalc sensor it is named (entity_id) sensor.0x54ef441000b75814_rgb_rgb_light_energy with a double "rgb". This is due to the fact that I had to add

  "sensor_config": {
    "power_sensor_naming": "{} RGB Light Power",
    "energy_sensor_naming": "{} RGB Light Energy"
  }

to prevent the rgb light and the white light overwriting/usinf the same entity_id because, as we alked about, my discovered devices always only carried the device name not the entity name/id. Is it safe to remove "RGB" now for all possibilities of discovery names?

The base/source entity name will be build correctly now, so there is no need for custom naming here anymore.
So this whole naming configuration can be removed from the concerning profiles imho.

[dagobert]

OK.
Now another issue: The standby power is used for both lights leading to the double amount. of standby energy usage.

[bramstroker]

No easy solution for that currently. As both entities / profiles are setup separately and don't have correlation to eachother.

Users which have this light are highly likely to setup profiles for both the lights, so I would suggest to set both profiles to half the amount of standby_power.

[dagobert]

No easy solution for that currently. As both entities / profiles are setup separately and don't have correlation to eachother.

Users which have this light are highly likely to setup profiles for both the lights, so I would suggest to set both profiles to half the amount of standby_power.

Thats what I thought. I will do that and add it to the remarks.

[bramstroker]

Thanks @dagobert