ECU Query Switch

[Doudou14]

Hello,

In the old integration, I used the ECU Query Switch at night to avoid overloading the ECU with requests.
Is it possible to put it back? Maybe detach it from the cache function ?

Thanks

[HAEdwin]

@Doudou14 Yes, I thought about that and decided to leave it out because users forgot to enable it in their automation after a reboot. I own an ECU-R 2160 and ECU-R-Pro 2162 and unlike previous versions of the integration never felt the need to stop the query at night past 1.5 year.

Do you still have a lot of trouble with cache usage when you let the query run continuously? What disadvantages do you encounter? Overload is actually not an issue if you keep the interval of 5 minutes. Which ECU model do you have?

I don't want to rule out bringing back the switch, but I am looking for the right arguments for it. It also depends on whether the wish is supported more widely.

[Doudou14]

Oops, I went to the wrong section.

Sometimes my ECU B freezes, and I have to restart it manually.
By disabling requests at night, the problem takes several months to manifest itself.
With requests enabled all the time, it can manifest itself in a few days.

I left the default interval of 5min.

It is true that when my ECU freezer, the ECU query button could be disabled

[HAEdwin]

Sorry I forgot about this subject 💡 It is a bit of fiddling with the placement of the ECU in relation to the inverters. But if you do it right, an ECU-B reboot is not really necessary.

I have put a smart plug in between to be sure. An automation ensures that when the cache count is 5, the smart plug is restarting the ECU-B.

Also take a good look at the entities, especially the dBm signal strength on the inverters.