I have a Tesla PW2, with the consumption sensors hooked up to 3-phase power. The outcome for this is that the ‘grid’ and ‘load’ voltages out of the Tesla JSON output appear to have the three phases added together, and come out around 720 Volts.
From a single Tesla PW2 JSON sample:
site.instant_average_voltage: 724.4799957275391
battery.instant_average_voltage: 239
load.instant_average_voltage: 724.4799957275391
solar.instant_average_voltage: 238.32000732421875
When I pull these four voltages into extended data as v7,v10,v8,v9, I can do an ‘Extended Data Rule’ formula ‘v7=v7/3; v8=v8/3’ to bring the 720V samples back to a 240V reference - see https://pvoutput.org/intraday.jsp?id=64310&sid=59918&dt=20180707 in the extended data section, which shows all four voltages after the division.
However, the load voltage is also being pulled into the main ‘voltage’ field for the consumption, and being graphed as the raw ~720V value (varying from ~709V up to 735V or so).
The ‘autouploader rules’ (https://pvoutput.org/help.html#autoupload-rule) don’t permit manipulation of the voltage variable, so I can’t set a uploader rule of ‘voltage /=3’ to correct the voltage.
As a future feature request - could the uploader rules please be extended to allow manipulation of the voltage as a variable, so that ‘voltage = voltage / 3’ was a permitted rule thanks?
(Or, if its only the Tesla device that has this issue for 3-phase use, could a flag be built into the PVO powerwall.ini uploader to enable these voltages to be corrected before uploading thanks).
See https://pvoutput.org/intraday.jsp?id=64310&sid=59918 for 720V voltage charts (correction turned off 11pm on 8th July 2018)