payload sizes (bytes) JSON / CBOR / packed: {'json': 54, 'cbor': 51, 'packed': 7}
loss 0.0: messages/day 304, lost 0.000% (theory p^5 = 0.000%), uplink latency p50/p95/p99 0.15/0.38/0.55 s, command p95 0.36 s, success 99.2%, dry plant-h 0.20, bytes/day 7220
loss 0.1: messages/day 304, lost 0.000% (theory p^5 = 0.001%), uplink latency p50/p95/p99 0.16/1.17/1.95 s, command p95 1.18 s, success 99.4%, dry plant-h 0.20, bytes/day 8031
loss 0.3: messages/day 304, lost 0.263% (theory p^5 = 0.243%), uplink latency p50/p95/p99 0.21/2.16/3.18 s, command p95 2.19 s, success 100.0%, dry plant-h 0.27, bytes/day 10250
loss 0.5: messages/day 304, lost 2.706% (theory p^5 = 3.125%), uplink latency p50/p95/p99 0.37/3.20/4.20 s, command p95 3.15 s, success 98.9%, dry plant-h 0.36, bytes/day 13675
loss 0.7: messages/day 305, lost 15.688% (theory p^5 = 16.807%), uplink latency p50/p95/p99 1.16/4.13/4.28 s, command p95 4.15 s, success 94.9%, dry plant-h 0.93, bytes/day 20024
MQTT PUBLISH sizes with a 10-byte topic, QoS 1: packed 7-byte payload 23 B; CBOR 51 B 67 B; JSON 54 B 70 B (application layer only, retransmissions counted, no TCP/IP headers)
per PUBLISH, JSON / packed = 3.04 times the bytes: about 24443 bytes/day at 10% loss if readings were JSON, against 8031 packed (command messages included in both)
saved /home/user/Documents/DOCUMENTS_SERVER/SKILL_TRAINING/Internet of Things (IoT) and Robotics/sessions/012-unit12-capstone/figures/fig05_network.png
