Not quite. The suggestion is to change the wiring of the Gateway’s c.t.
Here’s my brown grid incoming live cable. My Battery’s grid c.t. is on the left and the Mk2’s grid c.t is on the right.
The additional cable running through the battery’s c.t. is the supply to the Mk2.
If I’ve got things clear in my head, the logic here is:
Your present situation:
- When there is excess PV, the Gateway starts exporting.
- The Mk2 starts diverting.
- In the design of the Mk2 software, taking advantage of the way utility meters register electricity usage, the Mk2 makes deliberate small (less than one flash of the meter’s LED) overshoots of import and export.The energy bucket
- The Gateway sees the short period of import and increases its export to balance it.
- The Mk2 sees this additional export and diverts more. etc etc.feedback loop.
The solution that worked for me
As Robert said,
The effect of this is
- When the battery is exporting
- The Mk2 diverts, reducing the export towards zero
- The modified battery c.t. doesn’t see that the export has reduced - or turned into a short tiny import.
- So the battery doesn’t react to the Mk2’s behaviour.
I don’t know if the Tesla Gateway has an accessible c.t. that can be tampered with in the same way that my battery does. But if it does, I think you could try fitting a c.t. around the immersion heater spur and extending it out to the gateway’s c.t.wiring and combining them as discussed here
Or you might think the work outweighs the benefits 