Are there any issues with setting axle_control to false for Fox inverters

[bellissimo]

I have just signed up to Axle Energy and linked Predbat using the API Key. I saw that there is an option to put Predbat into read only mode (axle_control = true) when an event occurs.

I know the default for this is false, but this will cause both Predbat and Axle to attempt to set the inverter at the same time. I am not sure how this works in practice but it would seem there will be a risk of clashes, and I am not sure of the effect of this on the Fox inverter specfically.

So I guess I have a couple of questions:

1. Now that this has been up and running for a few months, are there any known issues with letting Predbat control the inverter settings for an Axle event?
2. What are the advantages of letting Predbat control the inverter settings (given that this will clash with Axle also trying to control the same settings)?

[gcoan]

I can't answer specifically for Fox, maybe raise the question on the Axle whatsapp group for Fox users?

But more generically (I have a givenergy inverter), I don't set predbat to read only, I let it control the inverter as well as Axle. They don't really clash as you suggest as both Predbat and Axle are setting the inverter to export mode, so two apps doing the same thing doesn't cause an issue.

The big reason for me why letting Predbat still control the inverter is the right answer is that quite often the Axle commands don't arrive on time.
So by letting Predbat control I ensure the inverter actually maximises income.
e.g. The last event Axle turned Eco mode off 10 minutes before the event when it programmed the event details in, this starts grid importing for me, in the peak rate. Predbat turned Eco back on, then at the start time of the Axle event, turned it Eco off to start exporting - thus avoiding 10 minutes of peak rate import.
I have also seen Axle not start discharging until 10 minutes into the event, so missing out on 10 minutes of export.
At the end of the event Axle haven't been reliable in turning Eco mode back on, some people have reported that its never been turned on, and I have seen the Eco command arrive 10 minutes after the event.

The only disadvantage I have seen is that Predbat sets the discharge time to be 1 minute longer than the session, Axle sets it precisely to the session time, so over the course of the Axle session I see the discharge time flip flop backwards and forwards as Axle and Predbat repeatedly set the time to what they think it should be. Axle only polls the inverter every 10-15 minutes and Predbat runs every 5 minutes, so its not like its hammered back and forth, it just gets changed a few times unnecessarily.

[bellissimo]

Thanks, will leave it as default for the time being then and see how it gets on.