You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: specification/src/main/asciidoc/chapters/Sparkplug_5_Operational_Behavior.adoc
+14-8Lines changed: 14 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -143,11 +143,11 @@ was connected to that MQTT Server and known by the Host Application MUST be upda
143
143
quality if the Host Application loses connection to the MQTT Server.*#
144
144
145
145
[tck-testable tck-id-message-flow-hid-sparkplug-state-message-delivered]#[yellow-background]*[tck-id-message-flow-hid-sparkplug-state-message-delivered] After
146
-
publishing its own Host Application STATE message, if at any point the Host Application is delivered
147
-
a STATE message on its own Host Application ID with a 'online' value of false, it MUST immediately
148
-
republish its STATE message to the same MQTT Server with a 'online' value of true and the
149
-
'timestamp' set to the same value that was used for the timestamp in its own prior MQTT CONNECT
150
-
packet Will Message payload.*#
146
+
publishing its own Host Application online STATE message, if at any point the Host Application is delivered
147
+
a STATE message on its own Host Application ID with a timestamp that is newer than the timestamp
148
+
that was used in its own immediately prior MQTT CONNECT packet Will Message, it MUST immediately
149
+
disconnect from the MQTT Server and reconnect. It MUST follow the standard rules for Host
150
+
Applications when establishing the connection to the MQTT Server.
0 commit comments