| Gateway | Topology | Devices | Last seen | Backlog | Config | Health |
|---|---|---|---|---|---|---|
| GW-NBO-01 Demo M-Bus/NB collector · FW 2.8.1 | nb_iot → mbus | 214/250 (86%) | 2026-09-20T00:58:00Z | 0 | cfg-12 / cfg-12 | healthy · 100No active issues |
| GW-NBO-02 Demo Cat1 collector · FW 2.7.4 | cat1 → mbus | 192/200 (96%) | 2026-09-20T00:21:00Z | 740 | cfg-11 / cfg-12 | offline · 0capacity_above_90pct · clock_drift_over_120s · large_store_forward_backlog · poll_failures_high · command_failures_high · gateway_stale |
| GW-EST-03 LoRaWAN bridge · FW 1.4.0 | ethernet → lorawan | 301/500 (60%) | 2026-09-20T00:55:00Z | 14 | cfg-12 / cfg-12 | healthy · 100No active issues |
COLLECTOR / UPLINK OPERATIONS
Gateway operations center
Model collectors as active infrastructure: capacity, buffering, crypto/profile references, clock, firmware and configuration drift.
Collector invariants
1Meter identity is independentReplacing SIM/modem/gateway must not replace the meter's canonical identity.
2Store-and-forward is observableBacklog age and duplicate-safe replay must be measurable.
3Config is versionedPolling, crypto/profile references and schedules are configuration artifacts.
Never assume a dumb modem
Collectors may buffer data, perform protocol handling, encryption/decryption, polling and command routing. Migration discovery must inventory these behaviors before bypassing an incumbent application.