WindyMiller Yep, definitely sending write instructions for settings, which is why we thought the presets as implemented by Giv were the way forward - as it seems more like an atomic/transactional operation, at least on the surface.
However, we found that actually causes more Timeouts than manually setting each individual setting directly, albeit using synchronous/blocking HTTP calls. Probably because it just sends these instructions too quickly or the general mechanism of accepting/dealing with multiple commands it is just flawed at the inverter end.
So yeah, not great.
You'd expect at a minimum the API should accept a bunch of settings in one async call, perform some basic validation server side, and return a 'submitted OK' status or such with a callback correlation ID to check afterwards by the caller.
This could internally then be sent to the inverter which should have a basic queue mechanism to process settings one by one, to prevent these Inverter Timeouts. ¯_(ツ)_/¯
