Hello,
I recently started using SBFspot, version 3.1.1 on raspberry pi.
I have a two inverter system. Both are successfully being queried.
As both inverters are part of my single PVOutput system, I have:
```
PVoutput_SID=2100397497:XXXX,2100393920:XXXX
```
This results, ultimately, in just one inverter's data being added to the site.
It is possible to see the first inverter's data being presented, and then over-written with the second.
If there are multiple inverters and the SIDs are the same, it would make sense to add the data, no?
Comments: > If there are multiple inverters and the SIDs are the same, it would make sense to add the data, no? No, all data gets overwritten when you resend to the same SID. This is by design. I don't recommend to send data of multiple inverters to 1 PVO system. If 1 PV system fails, it will be difficult to detect. Better use 1 system per inverter and consolidate all the systems in 1 parent - however, this requires donation to PVO. If you really want to stick with your idea, you can sum/group by the data before you send it. Modify vwPvoData something like: ```SQL SELECT dd.TimeStamp, dd.Name, dd.Type, dd.Serial, dd.TotalYield AS V1, dd.Power AS V2, SUM(cons.EnergyUsed) AS V3, SUM(cons.PowerUsed) AS V4, AVG(spot.Temperature) AS V5, AVG(spot.Uac1) AS V6, NULL AS V7, NULL AS V8, NULL AS V9, NULL AS V10, NULL AS V11, NULL AS V12, dd.PVoutput FROM vwDayData AS dd LEFT JOIN vwAvgSpotData AS spot ON dd.Serial = spot.Serial AND dd.TimeStamp = spot.Nearest5min LEFT JOIN vwAvgConsumption AS cons ON dd.TimeStamp = cons.Nearest5min GROUP BY dd.TimeStamp ORDER BY dd.TimeStamp DESC ``` See Quick Reference Guide for Tweaking PVOutput
I recently started using SBFspot, version 3.1.1 on raspberry pi.
I have a two inverter system. Both are successfully being queried.
As both inverters are part of my single PVOutput system, I have:
```
PVoutput_SID=2100397497:XXXX,2100393920:XXXX
```
This results, ultimately, in just one inverter's data being added to the site.
It is possible to see the first inverter's data being presented, and then over-written with the second.
If there are multiple inverters and the SIDs are the same, it would make sense to add the data, no?
Comments: > If there are multiple inverters and the SIDs are the same, it would make sense to add the data, no? No, all data gets overwritten when you resend to the same SID. This is by design. I don't recommend to send data of multiple inverters to 1 PVO system. If 1 PV system fails, it will be difficult to detect. Better use 1 system per inverter and consolidate all the systems in 1 parent - however, this requires donation to PVO. If you really want to stick with your idea, you can sum/group by the data before you send it. Modify vwPvoData something like: ```SQL SELECT dd.TimeStamp, dd.Name, dd.Type, dd.Serial, dd.TotalYield AS V1, dd.Power AS V2, SUM(cons.EnergyUsed) AS V3, SUM(cons.PowerUsed) AS V4, AVG(spot.Temperature) AS V5, AVG(spot.Uac1) AS V6, NULL AS V7, NULL AS V8, NULL AS V9, NULL AS V10, NULL AS V11, NULL AS V12, dd.PVoutput FROM vwDayData AS dd LEFT JOIN vwAvgSpotData AS spot ON dd.Serial = spot.Serial AND dd.TimeStamp = spot.Nearest5min LEFT JOIN vwAvgConsumption AS cons ON dd.TimeStamp = cons.Nearest5min GROUP BY dd.TimeStamp ORDER BY dd.TimeStamp DESC ``` See Quick Reference Guide for Tweaking PVOutput