Hi, I am experiencing more “Failed to set inverter” errors in my activity log since enabling Agile. I suspect that this is partly because more instructions are being sent and therefore a higher chance of something going wrong.
Does WW have any mechanism built in to retry sending the instruction if it fails? It would be good if it could capture the error, wait 60 seconds and retry and loop around that process until it gets a success message, I would think you would probably want to limit the retries to 3 and then give up. This would give a a few minutes for whatever the issue is to sort itself out (be that the api, my dodgy internet connection etc).
Alternatively, Growatt (not sure about giv) allows you to set multiple schedules so you could send the next schedule in Slot 1 and the subsequent schedule in Slot 2. If the subsequent instruction fails to send it will still be actioned as it is already set in slot 2, if it is successful, what was in slot 2 would be sent to slot 1 and slot 2 populated with the next subsequent schedule. (Not sure if that makes sense…)
Anyway, I appreciate this is all in beta and your hard work on the continuing development, so know there will be occasional blips. I suspect if WW goes into full production users might be less forgiving if they miss out on cheaper electricity rates due to the inverter failing to be set, so worth considering.
