Skip to main content

ToU internal errors: INTERNAL MAP NODE

Written by Maximilian Kraft

Errors

  • INTERNAL_MAP_NODE_CONSTRAINT

  • INTERNAL_MAP_NODE_CONSTRAINT_MISSING_BATTERY_FIELDS

  • INTERNAL_MAP_NODE_STATE

  • INTERNAL_MAP_NODE_STATE_MISSING_BATTERY_STATE_OF_CHARGE

Cause of issue

One of the constraints / state values below listed are not reported reliably from the driver:

  • MaxEnergy

  • MaxActivePower, MinActivePower, MaxEnergy

  • State of Charge

This can also be caused by other fields not being parsed properly.

Assets showing the errors

Missing MaxEnergy:

  • sonnen ECO_8-10

  • 1KOMMA5 1K5-HI-12-V1

  • 1KOMMA5 1K5-HI-8-V1

  • Enphase 'Envoy S

Missing of MaxActivePower, MinActivePower & MaxEnergy:

  • SolarEdge SE8K-RWB48BFN4

  • SolarEdge SE10K-RWB48BFN4

  • Sungrow SH10.0RT-V112

  • Sungrow SH8.0RT-V112

  • Sungrow SH6.0RT-20

Missing of State of Charge:

  • Sungrow SH6.0RT-V112

  • Sungrow SH10.0RT-V112

  • Sungrow SH8.0RT-V112

  • SolarEdge SE8K-RWB48BFN4

  • SolarEdge SE10K-RWB48BFN4

  • Enphase Envoy S

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.

Did this answer your question?