← Back to the chapter · Previous detail
Technical detail · MQTT Publish-Subscribe Basics
Routing checks and subscriber delivery evidence
For a missing boiler reading, follow the path before changing settings. Authentication checks identity; authorization checks permission. Did the expected identity connect? Was its publication permitted? Did the topic match? Did the subscriber receive it? A configured last will lets the broker publish status after unexpected connection loss. That status is evidence about the connection, rather than a fresh temperature or a complete fault diagnosis.
Figure 3.1 and Figure 3.3 illustrate routing and message content. Follow the topic to its matching consumers, then inspect the payload separately.
The operations screen and alarm service show the same 83.4 C reading. Their receipt still cannot prove that it is fresh or physically correct. Keep the topic and client identity beside the value so its source remains clear. If a second boiler publishes on plant/boiler8/temperature, a matching filter may admit its reading too; the number alone cannot tell the sources apart.
For a reconnecting listener, topic snapshots and client queues remain separate kinds of stored state.
Retained state belongs to a topic. A new matching subscription can receive its last-known snapshot. Session state belongs to a client. Its settings and broker limits decide which eligible messages can wait while that client is offline. A retained snapshot and an offline queue answer different questions.
Quality of service is the MQTT delivery level. QoS zero has no protocol acknowledgement; higher levels still do not prove application action. Applications still need freshness and duplicate handling.