Allow MQTT publishing every second

[jstammi]

Consistent with DTU settings for polling data

[tbnobody]

Just a few notes why a 1 sec publish time doesn't make sense.
First of all, the poll interval behaves like this:

• Poll first inverter with 200ms timeout and a possible retransmit time
• Wait [Poll time]
• Poll second inverter with 200ms timeout and a possible retransmit time
• Wait [Poll time]
• etc....

It's only possible to do time consuming stuff like sending mqtt messages during the Poll Idle time. Otherwise you would miss packages due to the frequence cycle.

When sending mqtt data e.g. for 5 or 6 inverters every second you will most likly run into undefined behaviors, out of memory errors etc.

Why do you need updates any 1 second? If you say now, that you need it for zero export features etc.... if you publish mqtt topics soo often or send limits in smaller frequencies like e.g. 15 seconds you will not get any statistics updates at all (because control commands have higher priority in the tx queue and will therefor delay statistics commands when a control command is in the queue).

[jstammi]

Making this possible does not mean you have to use it like this in every constellation.

With a single Inverter it perfectly makes sense if you do not want to miss data. At the moment I poll and publish with both set to 2s. With publishing only at current minimum of 5s, only every 2nd-3rd sample polled could be used on listening for mqtt values.

And with multiple inverters (but even for my single-one-setup) ... I consider sending just the data of the one having polled from latest would be the most obvious expected default behaviour ... ?

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.