← Back to the chapter · Previous detail
Technical detail · CoAP Methods and Multicast
Assumptions behind the five-byte temperature energy model
8.8.0.1 Putting Numbers to It

Animation · step by step
The Efficiency Claim Reduces to Counting Bytes
The Efficiency Claim Reduces to Counting Bytes
An illustrative temperature-report model compares CoAP with HTTP by counting selected transmitted bytes and converting their airtime into energy.
The five-byte temperature example counts 45 bytes for CoAP and 425 for HTTP using an incomplete framing allowance. At its selected 1,000 daily readings, 3 V, 200 mA transmit current and 250 kbps effective link rate, it gives 0.86 J/day and 8.16 J/day of transmit energy. These are selected model inputs, not measurements of an ESP32 microcontroller.
The resulting 9.4× ratio applies to that isolated overhead model. Dividing the assumed 2,430 J budget by those costs gives about 7.7 years versus 0.8 years, but excludes sleep current, computation, retries and battery behaviour. It does not establish that a CR2032 coin cell can supply the assumed current. A separate illustrative battery calculator uses 20 mA instead; results from those different assumptions must not be combined as if they were one measurement.
For a practitioner’s decision, record tolerated loss, expected message frequency and retry budget. Measure the complete exchange and whole-device energy before accepting an energy or latency requirement. The smallest header cannot settle those questions by itself.