Question, what is the minimum time required between two commands in single connection mode at Modbus? Or does that also depend on the connected hardware?
It depends on the Modbus device (or Modbus TCP bridge).
In normal cases you could request registers every second. But I don’t know how this is on Homey side with several Flows every 1 sec 
I can confirm, homey kill flows that trigger every 1sec after sometime.
(was trying to poll state of pir sensors to use as triggers)
Flows that check every 10sec seems okey 
(Polling Energy Meters every 10sec here)
10 seconds sounds great to let my PV inverter ride the power consumption in the house.
@RonnyW Once again many thanks for this really useful app. I’m using it for my heat pump and two inverters and it’s such a great help!
As I do quite some intensive control of those devices, I would like to reduce the number of actual write operation. At least for some devices it has been reported, that too many write operation might degrade their flash memory.
The most obvious solution would be a read-compare-write-if-changed, but this would need three flow cards for every write operation, which would make many flows a bit messy (more than they already are).
So would it be possible to get a separate flow card that does the above? Just like the normal write-flow card, but it first reads the value and only actually writes it, if it needs to be changed? Or alternatively add a third mode e.g. called “update” to your write flow card that does that.
