Share this article:
Why is Data in SolisCloud not shown as expected?
The data displayed in SolisCloud is uploaded from the inverter every 5 minutes, representing a snapshot of the inverters data at that moment. The 5 minute values are NOT 5 minute average values. The snapshot is taken even while a transient is happening. This means that the uploaded data displayed in SolisCloud as a 5 minute value, is often times recorded while the system is reacting to fluctuations in PV generation (clouds or snowfall), consumer loads (turning on and off) or battery operation (current limitations). Additionally, the inverter takes a few seconds to react to the new scenario and ramp up/down it´s power (e.g. it sees that you are exporting, and then in 2 or 3 seconds it starts charging to cancel out that export).
Below a few examples:
- Load is turned on while PV power < load resulting in a spike from the grid.
- Within one second, the inverter gets the message from the meter that there is import occurring to cover the load. Snapshot is taken and it looks like the system is not operating properly. However, the data was just captured in the exact moment where the system was reacting to the increased load power.
- The inverter takes a few seconds to ramp the discharge power, which results in 0kW at meter connection. In the next snapshot, the displayed data is showing 0kW at the grid connection point, with the battery discharging to match load
In another example, when the load is turned off:
- The load stops, while there is still PV production, which results in export.
- The meter detects this export and communicates to the inverter.
- The inverter takes a few seconds to ramp back the discharge, meter power is back to 0W.
In situations like explained in these examples, it might look like the system was not operating correctly for 5 minutes. The values in SolisCloud might not make sense for a particular 5 minute value. However the reason for this is simply that in the moment when the data was recorded, the system was dynamically reacting to a change in situation which resulted in this 5 minute value uploaded to SolisCloud. In reality, the situation displayed in SolisCloud, only lasted for a few seconds.
