search

ldotlopez / ha-ideenergy

ideenergy integration for home-assistant
GNU General Public License v3.0
73 stars 13 forks source link

i-DE user blocked #52

Open alvarocarrera opened 1 year ago

alvarocarrera commented 1 year ago

I know this is not a "real" bug, but I have just received an SMS saying my user is blocked, I cannot log in to the i-DE website and even I cannot change my password or anything. They say my account is blocked due to improper use. But, what improper use? Maybe too many requests? I am using the account only for monitoring... And that is the goal of this service...

I have written a request to i-DE to reactivate the account but... I am waiting for a response.

Has anyone received the same SMS or has been blocked like me?

z647230 commented 1 year ago

Same here, I just installed the integration this week and at 9/9/2023 2:09 AM I also received an sms that the account access was revoked. So, for the time being I will remove the integration and send request to I-de what’s the issue. Grtz, Martin

alvarocarrera commented 11 months ago

I have just recovered my user. Just for the record, I only have one associated account. Not several as it says in the FAQ (https://github.com/ldotlopez/ha-ideenergy/blob/main/FAQ.md#q-i-have-a-problem-with-multiple-contracts-i-got-banneddoesnt-work).

z647230 commented 11 months ago

@alvarocarrera What did you do to recover your account ? I'm already mailing with I-de for almost a week and no progress yet. Grtz, Martin

alvarocarrera commented 11 months ago

No secret... I contacted them by e-mail and I got answered requiring some personal data to verify the account. Then, the next response was: "ok, we request the IT department to restore the account". And that was all...

I hope you have an answer soon.

vjaguilar commented 11 months ago

Same here. My user got blocked, I answered to the email with all the info they requested and now they've restored my user. But in their final email they added the paragraphs below, saying the user was blocked because of "massive automated queries" to their system. I'm not sure how often the plugin polls i-de APIs but the way that's worded makes me think we could get blocked again. Also the way they worded the alternative "descarga datos multicontrato" looks like some batch process to me, instead of a sync API.

El usuario se había bloqueado a raíz de un uso inadecuado, como, por ejemplo, ejecutar consultas masivas de manera automática que pueden afectar al rendimiento general de la plataforma. Para este tipo de solicitudes cuenta con la funcionalidad Descargar datos multicontrato (dentro del apartado Gestiones), desde donde podrá solicitar datos de consumos y potencias máximas de todos los contratos de hasta 1 año en una única solicitud. En caso de que esta funcionalidad no cumpla con sus necesidades, por favor indícanos el detalle de la información que necesita y con qué frecuencia para poder valorar dicha mejora en el Área privada.

alvarocarrera commented 11 months ago

I have just received that email too... I got my user unblocked a couple of days before this mail... Should we respond to that mail saying our requirements?? We are not doing anything bad... By now, I have disabled the Instant Power demand that I suppose is more "demanding" for the API than accumulated consumption.

alvarocarrera commented 11 months ago

I have found that disabling Instant Power demand has no effect, the integration is requesting the API every 5 minutes or so. So... I've re-enabled that sensor and we just have to cross our fingers that we don't get banned again.... LOL

Without blaming anyone (I am very grateful to have this integration in my HA), the integration is not working as the documentation says: "Update algorithm to read the meter near the end of each hourly period (between minute 50 and 59) with a better representation of the consumption in the Home Assistant energy panel."

In contrast, at my "I-DE private area", I can see clearly it is connecting every 4-5 minutes. Is that a bug? Because with this number of requests (aprox. 20 requests per hour), it is logical to understand why we are banned... :(

ldotlopez commented 11 months ago

Hi, author here…

In contrast, at my "I-DE private area", I can see clearly it is connecting every 4-5 minutes. Is that a bug? Because with this number of requests (aprox. 20 requests per hour), it is logical to understand why we are banned... :(

I need to see your logs please, add debug level for custom_components.ideenergy.datacoordinator

You may see some lines like this each 5 minutes but it doesn't mean that a request is made to the API, quite the opossite: a request was prevented. 

2023-09-22 11:37:01.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: update window is closed

Lines like this is where request are made

2023-09-22 12:59:29.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for MEASURE

Please, check your logs and update the issue, thanks.

ldotlopez commented 11 months ago

Those are my logs for the last hour:

ha-core | 2023-09-22 12:18:53.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE, HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 12:18:53.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: update window is closed
ha-core | 2023-09-22 12:18:53.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for HISTORICAL_CONSUMPTION: no max_age reached (5:36:34.331607 <= 6:00:00)
ha-core | 2023-09-22 12:18:53.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching me@me.com/12345 coordinator data in 0.000 seconds (success: True)
ha-core | 2023-09-22 12:23:23.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE, HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 12:23:23.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: update window is closed
ha-core | 2023-09-22 12:23:23.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for HISTORICAL_CONSUMPTION: no max_age reached (5:41:04.331870 <= 6:00:00)
ha-core | 2023-09-22 12:23:23.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching me@me.com/12345 coordinator data in 0.000 seconds (success: True)
ha-core | 2023-09-22 12:27:53.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE, HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 12:27:53.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: update window is closed
ha-core | 2023-09-22 12:27:53.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for HISTORICAL_CONSUMPTION: no max_age reached (5:45:34.331744 <= 6:00:00)
ha-core | 2023-09-22 12:27:53.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching me@me.com/12345 coordinator data in 0.000 seconds (success: True)
ha-core | 2023-09-22 12:32:23.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE, HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 12:32:23.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: update window is closed
ha-core | 2023-09-22 12:32:23.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for HISTORICAL_CONSUMPTION: no max_age reached (5:50:04.332197 <= 6:00:00)
ha-core | 2023-09-22 12:32:23.786 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching me@me.com/12345 coordinator data in 0.001 seconds (success: True)
ha-core | 2023-09-22 12:36:53.784 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE, HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 12:36:53.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: update window is closed
ha-core | 2023-09-22 12:36:53.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for HISTORICAL_CONSUMPTION: no max_age reached (5:54:34.331467 <= 6:00:00)
ha-core | 2023-09-22 12:36:53.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching me@me.com/12345 coordinator data in 0.000 seconds (success: True)
ha-core | 2023-09-22 12:41:23.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE, HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 12:41:23.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: update window is closed
ha-core | 2023-09-22 12:41:23.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for HISTORICAL_CONSUMPTION: no max_age reached (5:59:04.332059 <= 6:00:00)
ha-core | 2023-09-22 12:41:23.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching me@me.com/12345 coordinator data in 0.000 seconds (success: True)
ha-core | 2023-09-22 12:45:53.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE, HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 12:45:53.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: update window is closed
ha-core | 2023-09-22 12:45:53.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 12:45:54.664 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update successful for HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 12:45:54.664 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching me@me.com/12345 coordinator data in 0.879 seconds (success: True)
ha-core | 2023-09-22 12:50:24.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE, HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 12:50:24.786 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for MEASURE
ha-core | 2023-09-22 12:50:26.979 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update error for MEASURE: Forbidden (403)
ha-core | 2023-09-22 12:50:26.979 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for HISTORICAL_CONSUMPTION: no max_age reached (0:04:32.315135 <= 6:00:00)
ha-core | 2023-09-22 12:50:26.979 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching me@me.com/12345 coordinator data in 2.194 seconds (success: True)
ha-core | 2023-09-22 12:54:56.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE, HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 12:54:56.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for MEASURE
ha-core | 2023-09-22 12:54:59.769 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update error for MEASURE: Forbidden (403)
ha-core | 2023-09-22 12:54:59.769 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for HISTORICAL_CONSUMPTION: no max_age reached (0:09:05.105681 <= 6:00:00)
ha-core | 2023-09-22 12:54:59.769 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching me@me.com/12345 coordinator data in 2.985 seconds (success: True)
ha-core | 2023-09-22 12:59:29.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE, HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 12:59:29.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for MEASURE
ha-core | 2023-09-22 12:59:31.459 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update error for MEASURE: Forbidden (403)
ha-core | 2023-09-22 12:59:31.460 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for HISTORICAL_CONSUMPTION: no max_age reached (0:13:36.795979 <= 6:00:00)
ha-core | 2023-09-22 12:59:31.460 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching me@me.com/12345 coordinator data in 1.675 seconds (success: True)
ha-core | 2023-09-22 13:04:00.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE, HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 13:04:00.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: update window is closed
ha-core | 2023-09-22 13:04:00.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for HISTORICAL_CONSUMPTION: no max_age reached (0:18:06.121732 <= 6:00:00)
ha-core | 2023-09-22 13:04:00.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching me@me.com/12345 coordinator data in 0.001 seconds (success: True)
ha-core | 2023-09-22 13:08:30.784 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE, HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 13:08:30.784 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: update window is closed
ha-core | 2023-09-22 13:08:30.784 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for HISTORICAL_CONSUMPTION: no max_age reached (0:22:36.120875 <= 6:00:00)
ha-core | 2023-09-22 13:08:30.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching me@me.com/12345 coordinator data in 0.000 seconds (success: True)
ha-core | 2023-09-22 13:13:00.784 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE, HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 13:13:00.784 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: update window is closed
ha-core | 2023-09-22 13:13:00.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for HISTORICAL_CONSUMPTION: no max_age reached (0:27:06.121013 <= 6:00:00)
ha-core | 2023-09-22 13:13:00.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching me@me.com/12345 coordinator data in 0.000 seconds (success: True)
ha-core | 2023-09-22 13:17:30.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE, HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 13:17:30.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: update window is closed
ha-core | 2023-09-22 13:17:30.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for HISTORICAL_CONSUMPTION: no max_age reached (0:31:36.121394 <= 6:00:00)
ha-core | 2023-09-22 13:17:30.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching me@me.com/12345 coordinator data in 0.000 seconds (success: True)

With some filtering there is the relevant information:

$ cat ha.log |grep -v Finis |grep -v Reques  |grep -v denie
ha-core | 2023-09-22 12:45:53.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 12:45:54.664 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update successful for HISTORICAL_CONSUMPTION
ha-core | 2023-09-22 12:50:24.786 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for MEASURE
ha-core | 2023-09-22 12:50:26.979 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update error for MEASURE: Forbidden (403)
ha-core | 2023-09-22 12:54:56.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for MEASURE
ha-core | 2023-09-22 12:54:59.769 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update error for MEASURE: Forbidden (403)
ha-core | 2023-09-22 12:59:29.785 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for MEASURE
ha-core | 2023-09-22 12:59:31.459 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update error for MEASURE: Forbidden (403)

Information for MEASURE (accumulated consumption) it's only requested in the 50-59 interval (and it fails due to API issues¨). Other values like HISTORICAL_CONSUMPTION it's only requested once.

Please compare this with your setup and update this issue, thanks.

alvarocarrera commented 11 months ago

Thanks in advance. Here I attach the logs (removing my email account):

2023-09-22 13:53:01.451 DEBUG (MainThread) [custom_components.ideenergy.barrier] success registered
2023-09-22 13:53:01.451 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update successful for MEASURE
2023-09-22 13:53:01.451 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for HISTORICAL_CONSUMPTION: no max_age reached (1:00:20.382730 <= 6:00:00)
2023-09-22 13:53:01.451 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_GENERATION
2023-09-22 13:53:01.501 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update error for HISTORICAL_GENERATION: Forbidden (403)
2023-09-22 13:53:01.501 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_POWER_DEMAND
2023-09-22 13:53:06.359 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update error for HISTORICAL_POWER_DEMAND: **FIXME** handle HISTORICAL_POWER_DEMAND raised exception: AssertionError()
2023-09-22 13:53:06.398 DEBUG (MainThread) [custom_components.ideenergy.sensor] sensor.contador_iberdrola_de_casa_historical_consumption: calculating statistics using 44.901 as base accumulated (registed at 2023-09-21 23:00:00+02:00)
2023-09-22 13:57:36.382 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: ALL
2023-09-22 13:57:36.383 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: last success is too recent (274.931561 seconds, min: 540 seconds)
2023-09-22 13:57:36.383 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for HISTORICAL_CONSUMPTION: no max_age reached (1:04:55.314270 <= 6:00:00)
2023-09-22 13:57:36.383 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_GENERATION
2023-09-22 13:57:37.202 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update error for HISTORICAL_GENERATION: Forbidden (403)
2023-09-22 13:57:37.202 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_POWER_DEMAND
2023-09-22 13:57:41.992 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update error for HISTORICAL_POWER_DEMAND: **FIXME** handle HISTORICAL_POWER_DEMAND raised exception: AssertionError()
2023-09-22 13:57:41.992 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching ************/*********** coordinator data in 5.609 seconds (success: True)
2023-09-22 13:57:42.032 DEBUG (MainThread) [custom_components.ideenergy.sensor] sensor.contador_iberdrola_de_casa_historical_consumption: calculating statistics using 44.901 as base accumulated (registed at 2023-09-21 23:00:00+02:00)
2023-09-22 14:02:11.382 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: ALL
2023-09-22 14:02:11.382 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: update window is closed
2023-09-22 14:02:11.382 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for HISTORICAL_CONSUMPTION: no max_age reached (1:09:30.313861 <= 6:00:00)
2023-09-22 14:02:11.382 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_GENERATION
2023-09-22 14:02:12.012 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update error for HISTORICAL_GENERATION: Forbidden (403)
2023-09-22 14:02:12.012 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_POWER_DEMAND
2023-09-22 14:02:16.900 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update error for HISTORICAL_POWER_DEMAND: **FIXME** handle HISTORICAL_POWER_DEMAND raised exception: AssertionError()
2023-09-22 14:02:16.900 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching ************/*********** coordinator data in 5.518 seconds (success: True)
2023-09-22 14:02:16.939 DEBUG (MainThread) [custom_components.ideenergy.sensor] sensor.contador_iberdrola_de_casa_historical_consumption: calculating statistics using 44.901 as base accumulated (registed at 2023-09-21 23:00:00+02:00)
2023-09-22 14:06:46.382 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: ALL
2023-09-22 14:06:46.383 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: update window is closed
2023-09-22 14:06:46.383 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for HISTORICAL_CONSUMPTION: no max_age reached (1:14:05.314252 <= 6:00:00)
2023-09-22 14:06:46.383 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_GENERATION
2023-09-22 14:06:47.087 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update error for HISTORICAL_GENERATION: Forbidden (403)
2023-09-22 14:06:47.087 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_POWER_DEMAND
2023-09-22 14:06:52.177 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update error for HISTORICAL_POWER_DEMAND: **FIXME** handle HISTORICAL_POWER_DEMAND raised exception: AssertionError()
2023-09-22 14:06:52.178 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching ************/*********** coordinator data in 5.795 seconds (success: True)
2023-09-22 14:06:52.223 DEBUG (MainThread) [custom_components.ideenergy.sensor] sensor.contador_iberdrola_de_casa_historical_consumption: calculating statistics using 44.901 as base accumulated (registed at 2023-09-21 23:00:00+02:00)
ldotlopez commented 11 months ago

Ok,

$ cat ha.log  |grep allow
2023-09-22 13:53:01.451 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_GENERATION
2023-09-22 13:53:01.501 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_POWER_DEMAND
2023-09-22 13:57:36.383 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_GENERATION
2023-09-22 13:57:37.202 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_POWER_DEMAND
2023-09-22 14:02:11.382 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_GENERATION
2023-09-22 14:02:12.012 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_POWER_DEMAND
2023-09-22 14:06:46.383 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_GENERATION
2023-09-22 14:06:47.087 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for HISTORICAL_POWER_DEMAND

What is causing the requests are the historical sensor, not the accumulated.

The problem seems to be some unexpected error loading historical data which causes the retry in the next 5 minutes instead of wait the next update window.

For now you have to disable them, I have a moving in the next days so I'm not sure when I can take a look but I will check it.

Thanks

alvarocarrera commented 11 months ago

To confirm, I disabled those sensors and it connects every hour (sometimes with a reconnection in 5 minutes), but now I have one connection per hour.

Thanks.