OpenDTU: Update WaitForAck

[ms49434]

With the release of OpenDTU v25.2.3, the queue management was improved and set limit / status requests can no longer flood the queue.
The code of OpenDTU::WaitForAck was removed and the method always returns true.
HoymilesZeroExport requires version v25.2.3 of OpenDTU.

[reserve85]

Hi, didn´t work?

[ms49434]

Hi, didn´t work?

It worked but I was facing several issues.
One inverter went offline and wasn't responding for 15-20 minutes. It could be that the interval between 2 set limit commands is too short after the code change.
Other inverters didn't acknowledge a new limit on the first attempt. This would indicate that WaitForAck is still required.

[reserve85]

yep i think so... and i am stuggeling because i think the script needs to receive an error response when there was a problem with setting the limit. if you do not get any response from openDTU/Ahoy the script don´t know that the last command was not successful...

[ms49434]

yep i think so... and i am stuggeling because i think the script needs to receive an error response when there was a problem with setting the limit. if you do not get any response from openDTU/Ahoy the script don´t know that the last command was not successful...

A code change where the main loop queries the limit_set_status of the inverters with a new helper method DTU::GetLimitStatus can replace DTU::WaitForAck and would improve the speed of your script (and it would run asynchronously). DTU::SetLimit would only fire when limit_set_status is Ok.

From the log (modified code to log limit_set_status)
OpenDTU: Inverter "holli": setting new limit from 859 Watt to 936 Watt
OpenDTU: Inverter "holli": Limit status is Pending
OpenDTU: Inverter "holli": Limit status is Pending
OpenDTU: Inverter "holli": Limit status is Pending
OpenDTU: Inverter "holli": Limit acknowledged