Interactive QoS Impact Calculator
Try Change QoS Level to 2.
Observe Watch Network transmissions per day after Calculate.
Explain Explain why QoS 2 uses 4 transmissions in the MQTT handshake.
Calculate
Reset
Technical boundaries. This simplified model compares MQTT packet-leg counts, not measured airtime. Real battery life depends on radio current, sleep current, payload size, retries, coverage, and firmware duty cycle.
Interactive QoS Impact Calculator
Experiment with different QoS levels to compare simplified MQTT exchange counts and network overhead:
viewof num_sensors = Inputs. range ([1 , 100 ], {value : 30 , step : 1 , label : "Number of sensors" })
viewof messages_per_day = Inputs. range ([1 , 10000 ], {value : 1440 , step : 10 , label : "Messages per day (per sensor)" })
viewof qos_level = Inputs. select ([0 , 1 , 2 ], {label : "QoS Level" })
qos_calculations = {
const messages_multiplier = qos_level === 0 ? 1 : (qos_level === 1 ? 2 : 4 );
const total_messages = num_sensors * messages_per_day;
const total_transmissions = total_messages * messages_multiplier;
const base_airtime_index = 1 ;
const relative_leg_count_per_sensor = base_airtime_index * messages_multiplier;
const total_relative_leg_count = relative_leg_count_per_sensor * num_sensors;
return {
messages_multiplier,
total_messages,
total_transmissions,
relative_leg_count_per_sensor,
total_relative_leg_count
};
}
html `<div style="background: var(--bs-light, #f8f9fa); padding: 1.5rem; border-radius: 8px; border-left: 4px solid #3498DB; margin-top: 1rem;">
<div style="margin-top: 0; color: #2C3E50; font-weight: 700; font-size: 1.1rem;">QoS ${ qos_level} Impact Analysis</div>
<table style="width:100%; border-collapse:collapse; margin-top:0.5rem;">
<tr style="background: #16A085; color: white;">
<th style="padding:8px; text-align:left; border:1px solid #ddd;">Metric</th>
<th style="padding:8px; text-align:left; border:1px solid #ddd;">Value</th>
</tr>
<tr><td style="padding:8px; border:1px solid #ddd;"><strong>Messages per day (all sensors)</strong></td>
<td style="padding:8px; border:1px solid #ddd;"> ${ qos_calculations. total_messages . toLocaleString ()} </td></tr>
<tr><td style="padding:8px; border:1px solid #ddd;"><strong>Network transmissions per day</strong></td>
<td style="padding:8px; border:1px solid #ddd;"> ${ qos_calculations. total_transmissions . toLocaleString ()} ( ${ qos_calculations. messages_multiplier } x overhead)</td></tr>
<tr><td style="padding:8px; border:1px solid #ddd;"><strong>Relative MQTT leg-count index per sensor</strong></td>
<td style="padding:8px; border:1px solid #ddd;"> ${ qos_calculations. relative_leg_count_per_sensor . toFixed (1 )} x QoS 0 baseline</td></tr>
<tr><td style="padding:8px; border:1px solid #ddd;"><strong>Total relative MQTT leg-count index</strong></td>
<td style="padding:8px; border:1px solid #ddd;"> ${ qos_calculations. total_relative_leg_count . toFixed (1 )} </td></tr>
</table>
<p style="margin-top: 1rem; font-size: 0.9rem; color: #7F8C8D;"><strong>Note:</strong> QoS 0 = 1 transmission (fire-and-forget), QoS 1 = 2 transmissions (PUBLISH + PUBACK), QoS 2 = 4 transmissions in the MQTT handshake. This simplified model compares MQTT packet-leg counts, not measured airtime; real battery life depends on radio current, sleep current, payload size, retries, coverage, and firmware duty cycle.</p>
</div>`
Back to the chapter