Extended Data - v9 misrepresenting data?

Problems
#1

My system ID is 36437.

I have the current on phase L1, L2 and L3 mapped to v9, v10 and v11 from a Fronius Hybrid.

I haven’t logged in for awhile and have just noticed the L1 graphing (v9) is very different from L2 and L3. The values are way too high and look like they are 1 decimal place out. ie. 23.295 amps should be 2.329 amps.

They used to work and look sensible.

I suspect a bug in either the firmware of the Hybrid (it has changed a couple of times) and it could be sending incorrect data. Alternatively, is PVOutput misreading the data on v9?

#2

The push value Current_AC_Phase_1 is used for v9 without change.

There maybe a change in the way the value is read/sent by the Fronius.

This can be confirmed by sending a few pushes to http://requestb.in instead of PVOutput.

#3

I tried RequestBin but the Fronius Push Service won’t accept the RequestBin URL format.

For example, the generated URL was -

https://requestb.in/1iby8m51

This gives an “Invalid entry” message on the Fronius Push settings page where it requires “Server:Port:” and would normally have “www.pvoutput.org:80”.

#4

Server:Port = requestb.in:80
Upload file name = /1iby8m51

#5

No luck with that either… The inverter gives a “Connection not possible” message as below -

It accepted those fields without giving an “Invalid entry” message.

#6

Try requestb.in:443 instead

#7

Connection not possible still.

#8

The endpoint https://requestb.in/1iby8m51 has been removed, create another one and try again.

#9

I’ve been creating a new requestb.in on each iteration I’ve tried.

Is there anyway to analyse the raw data that gets saved at PVOutput?

#10

This has been fixed and it is now reading the value correctly. Thanks for your patience.

#11

Thankyou! The values for Current_AC_Phase_1 are looking much more sensible now.