What is the fastest DPL zero export setup

[oldman4U]

I use the DTSU666/Hoymiles DTU Pro and a HM-800 on 16s LiFePO4 battery for zero export control. In case the amount of power used changes, it takes approximately 10sec to adjust to the new value.

What is the fastest/most accurate setup based on OpenDTU?

Sorry if this topic has been discussed before but I could not find something related in the discussions.

Thank you

[schlimmchen]

What is the fastest/most accurate setup based on OpenDTU?

You mean OpenDTU-OnBattery?

One inverter only, latest release installed, power meter polling interval at 1s or even better MQTT power meter interface where the values are published once a second (faster power meters are not really available, AFAIK), DTU polling interval set to 1s. Also, the wireless connection to your inverer must be good, i.e., not too far away, not too close, little packet drop. See if the data age in the live view is often larger than 1 second when the DTU interval is 1s, then it should only ever be 1s in the ideal case. Then you can expect your inverter to react in the range of 2 to 3 seconds.

[greymda]

@schlimmchen can't find power meter polling interval set location for HTTP(S) + Json option. Can you help me out, please? Cheers

[schlimmchen]

That probably means you are on an older firmware release. Is that correct?

[greymda]

yes, on a 4mb remote system, [2024.06.03]

[oldman4U]

Yes. OpenDTU on battery.

Would a Shelly be the preferred meter?

[schlimmchen]

Who knows what one can squeeze out of the Hichi WiFi version, read-out speed wise?

That depends on the meter. Mine spits out new values in 1 second intervals (roughly) and the Hichi publishes them immediately.

The Shelly 3 EM also has a measurement frequency of around 1 Hz. And this seems to be typical, as the respective chips have similar performance.

[gitisgreat2023]

@schlimmchen I just assembled my Hichi WiFi + Hichi TTL to support both reading out the Hichi and being able to use the Tibber pulse. It works! (Two 3D printed parts put the three modules together, a 3V power supply for the Tibber completes it ;-))
Only: how do I get a fast readout? The lowest value TelePeriod accepts is 10 sec.
I assume you get the data out to some server, as you write „ Mine spits out new values in 1 second intervals (roughly) and the Hichi publishes them immediately.“

[spcqike]

@gitisgreat2023 hichi works with tasmota, doesn’t it?

If so, check out the wiki

https://github.com/hoylabs/OpenDTU-OnBattery/wiki/Power-Meter#important-for-tasmota-users

[schlimmchen]

Unfortunately, the best approach using a modified >S section is not documented there...

>S
[...]
=>publish grid/power/total/watts %sml[10]%

Where 10 is the 1-based index of the decoded SML value.

I would love to document this properly, but my time is limited, so...

I assume you get the data out to some server, as you write

@gitisgreat2023 Well yeah, see above (and the other two places where I buried this info^^)

[Manos1966]

I would love to document this properly, but my time is limited, so...
(...the other two places where I buried this info)

any links where to find these Bernhard?

[oldman4U]

Another question. Is there a meter which can be connected directly to the esp and has this any further advantages? Thank you all for your input.

[remigauthier]

Not sure it will be of any use, the problem will stand between the dtu and the inverters, it is slow : min 1s, a few seconds in real use, sometimes more if a lot of requests are made to the inverters.

[remigauthier]

see tbnobody#1088

[remigauthier]

I am using Home Assistant with slow zero export using Automation rules right now.

I reduce power of each inverter from 100 to 50 to 5% Non Persistent Relative Limit one inverter after the other as long as I export power and I increase power same way when I import power --> 10s interval between each action.

As a result I export power and there are spikes but overall the goal is reached, see purple to see exported power in the graph shared.