Errors
|
|
Cause of issue
|
One of the constraints / state values below listed are not reported reliably from the driver:
This can also be caused by other fields not being parsed properly.
|
Assets showing the errors
|
Missing MaxEnergy:
Missing of MaxActivePower, MinActivePower & MaxEnergy:
Missing of State of Charge:
|
Manual action to resolve the error
|
Triggering a rescan might correct the values & therefore resolve the issue. This will however not solve it entirely & persistently.
|
Status
|
Fixes are being implemented. If the asset reports an OEM error, we now report that there is an OEM error state, which is the case for a large share of assets reporting this error. Furthermore, we reworked the offline asset check, and now detect assets correctly as offline, which turned out to be the underlying issue in some cases. Next, we are working on introducing caching for asset limits and measurements to increase robustness for momentarily missing asset limits and measurements.
|
