Distinguish a missing reading from a zero reading
Zero consumption is a measurement. No reading is missing information. If an application uses the same display for both, a resident may draw the wrong conclusion about the household or the device. A useful requirement states how long a reading remains current and what happens after that period.
A screen can show the last observed value with its timestamp and a clear connection message. The chosen wording should reflect what the system knows. A gateway being reachable does not necessarily mean that every downstream device is reporting.
Decide what happens to a queued instruction
A request may be created while a device is unavailable. The team needs to decide whether it expires, remains pending, or requires confirmation after reconnection. Replaying an old instruction without checking its relevance can produce confusing behavior.
Record the creation time, the intended operating period, and the evidence required to mark the instruction as completed. An expired charging window and a persistent display preference are different kinds of request. They should not automatically share one retry rule.
Check the return to a connected state
On reconnection, the product may receive delayed readings, repeated messages, or a snapshot that differs from the last displayed state. An integration test should cover those situations rather than checking only that the network icon changes.
A practical recovery checklist includes a fresh reading, a known clock, an explicit treatment of outstanding requests, and an operator path for unresolved errors. Document the result with the device and software versions used. This guide describes development choices; the correct equipment behavior depends on the supported system and its existing protections.