One device appears twice: avoid double counting

Build a physical-device list

Count the actual installed devices using labels and installation records. Give each one a private identifier, model and known connection. Keep sensitive serial numbers out of public screenshots.

Then list the dashboard entries separately, including interface and reported identity. Comparing the two lists exposes uncertainty: two entries may map to one device, or one entry may represent an aggregate whose individual components are not exposed.

Look for multiple communication paths

A supported device may be discoverable through both a wired interface and Bluetooth. A changed adapter path can also create an unfamiliar entry. Similar names alone are not enough to decide whether the entries are duplicates.

The example assumes identities were verified. Matching voltage and percentage are clues, not proof; two real packs can have similar readings.

Check how the aggregate handles identity

Sunstead has safeguards for recognized duplicate identities so overlapping sources do not automatically inflate relevant totals. When identity is incomplete or uncertain, inspect the source list and any aggregate availability indication rather than assuming the software can infer the physical layout.

Do not force a total by renaming devices or entering capacities until the underlying mapping is clear. A calculated bank value can look plausible while still including one source twice.

Avoid disrupting equipment to investigate

Start with read-only evidence: model, identity, interface, timestamps and the documented installation. Do not disconnect a battery’s operating communication link simply to see which row disappears.

If a controlled monitoring-interface test is necessary, follow the equipment documentation and preserve a known-good configuration. Changes to electrical or operational communications require the appropriate qualified support. A dashboard cleanup is not a reason to improvise those changes.

The Modbus serial guide provides protocol context, but a protocol address is not a universal physical serial number. Device identity must be interpreted within the actual system.

Leave a source-to-device record

• Physical device identifier and exact model.
• Every monitoring interface that can see it.
• Reported identity and confidence in the match.
• Which source contributes to each aggregate.
• Any unresolved or suppressed entry.
• Date and method of verification.

After resolving the mapping, compare bank totals and responding-device counts. Keep earlier suspicious totals labeled rather than silently treating them as valid historical measurements.

Review this record when adding an adapter, enabling another wireless reader or replacing a pack. Duplicate prevention is easiest when the installation’s identities are known before a new source appears.