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
Often the time a device reports some event over MQTT, the delay is not very big. Thus the event time (inside the message JSON) and the time of the MQTT message do not differ very much.
But specifically in case of retained messages the difference could be arbitrary long.
I have to admit that this feature is not trivial, as the JSON field containing the time needs to be configured, mapped and parsed.
[Edit: of course this is mostly relevant for charts]
The text was updated successfully, but these errors were encountered:
Often the time a device reports some event over MQTT, the delay is not very big. Thus the event time (inside the message JSON) and the time of the MQTT message do not differ very much.
But specifically in case of retained messages the difference could be arbitrary long.
I have to admit that this feature is not trivial, as the JSON field containing the time needs to be configured, mapped and parsed.
[Edit: of course this is mostly relevant for charts]
The text was updated successfully, but these errors were encountered: