Error at starting HA

[Loic691]

Hello
I have the last version of the integration.
Great.
For sensor don't present on integration, I use API RT2. Great to for solenoid torre sensor.

I would like to report error only at starting of HA...
14 times the error is logged at each starting of HA.
I don't understand why. ?
The RT2 is running with no problems.

Cette erreur provient d'une intégration personnalisée
Logger: custom_components.ecodevices_rt2.sensors.sensor_ecodevicesrt2
Source: custom_components/ecodevices_rt2/sensors/sensor_ecodevicesrt2.py:36
Integration: GCE Ecodevices RT2 ([documentation](https://github.com/pcourbin/ecodevices_rt2), [issues](https://github.com/pcourbin/ecodevices_rt2/issues))
First occurred: 17:53:52 (14 occurrences)
Last logged: 17:53:52

Device data no retrieve rt2_teleinfo_tempo_blanc_HC: Ecodevices RT2 API error, key 'BBRHCJW' not in return from command: Get=TI Values: {}
Device data no retrieve rt2_teleinfo_tempo_blanc_HP: Ecodevices RT2 API error, key 'BBRHPJW' not in return from command: Get=TI Values: {}
Device data no retrieve rt2_teleinfo_tempo_rouge_HC: Ecodevices RT2 API error, key 'BBRHCJR' not in return from command: Get=TI Values: {}
Device data no retrieve rt2_teleinfo_tempo_rouge_HP: Ecodevices RT2 API error, key 'BBRHPJR' not in return from command: Get=TI Values: {}
Device data no retrieve rt2_teleinfo_demain: Ecodevices RT2 API error, key 'DEMAIN' not in return from command: Get=TI Values: {}

I have one times this warning too. Maybe linked ? Which is the goog interval ?

A scan interval too low has been set, you probably will get errors since the GCE Ecodevices RT2 can't handle too much request at the same time

Last logged: 18:25:17
First occurred: 18:25:17 (1 occurrences)
Integration: GCE Ecodevices RT2 ([documentation](https://github.com/pcourbin/ecodevices_rt2), [issues](https://github.com/pcourbin/ecodevices_rt2/issues))
Source: custom_components/ecodevices_rt2/__init__.py:153

Logger: custom_components.ecodevices_rt2

[Loic691]

Hi @pcourbin
For information, This issue is always here in your 2025 january version