Sezibwa meter replacement log
Sezibwa meter replacement log
One entry per customer meter swap at Sezibwa (gateway gw-pi2). Record every system that points at a meter serial, because each one must be switched separately: the OpenEMS gateway config, the customer app (meter_sources) and the billing engine (MBE device + household link). Customers are identified here by Modbus address and serial only.
Summary
| Date | Modbus address | Old serial | New serial | Status |
|---|---|---|---|---|
| 2026-09-14 | 7 | 210302003356 | 200326020197 | All systems switched 2026-09-24; closing 244.54 kWh, opening 0.31 kWh |
2026-09-14: address 7, 210302003356 to 200326020197
Why it was replaced. The old meter stopped answering on the meters bus on 2026-08-29 at 23:07 UTC (logger issue #82). It was later found physically absent. Its last register value seen on the backend was 229.35 kWh on 2026-09-04.
New meter. CHINT DDSU666 serial 200326020197, on Modbus address 7. The first backend data is from 2026-09-14; the register read 16.16 kWh on 2026-09-24.
Systems switched:
| System | Change | Date | Reference |
|---|---|---|---|
| OpenEMS gateway (gw-pi2) | New meter component meter200326020197 on unit 7 |
2026-09-14 | microgrid-gateway PR #68 |
| Customer app | meter_sources row repointed to meter200326020197/ActiveConsumptionEnergy, history start 2026-09-14; daily usage backfilled 14 to 24 Sep with the production backfill script (11 days, sums match the register) |
2026-09-24 | this page |
| Billing engine (MBE) | New device "(new meter)" added on edge sezibwa-rentals-gw-pi2 as a Consumption meter | 2026-09-24 | this page |
| Billing engine (MBE) | Household billing device changed to the new device (Change billing device); old device now unlinked; invoice meter serial field set to 200326020197 by hand | 2026-09-24 | MBE UI gap reported: serial does not follow a device change |
Closing and opening readings (from the swap thread, Element product room, 2026-09-14). Old meter 210302003356 read 244.54 kWh just before removal. New meter 200326020197 read 0.31 kWh at installation (about 12:15 EAT), on Modbus address 19. The old meter's register kept counting while it was off the bus, so there is no unmetered gap: its closing reading covers 30 Aug to 14 Sep.
September bill. The billing engine takes one meter per household per period, so bill this customer with one manual reading (manualReadings in the generate call) that joins the two meters:
| Start | End | kWh | |
|---|---|---|---|
| Old meter | 223.52 (August end, when it went silent) | 244.54 | 21.02 |
| New meter | 0.31 | reading at September close | end minus 0.31 |
| Manual reading to enter | 223.52 | 244.54 + (new end - 0.31) | sum of both |
Check first that the August bill really ended this customer at 223.52 kWh.
Watch. A stray 0.35 kWh value appears on 2026-09-14 under the old channel name. That was the new meter answering on address 7 before its component was renamed, not the old meter.