The issue has now been resolved. The issue applied to MQTT integrations using the Spark-plug B protocol. Integrations that used Spark-plug B and did regular restarts, where less affected. Integrations using any other MQTT protocol where unaffected.
To resolve the issue, the Clarify client will now request a REBIRTH from clients if we receive data for signals where we haven't successfully retained the DBIRTH message. This is allowed by the spec, and works well with the integrations we have tried.
If you are still facing issues, or require more detail about the fix and/or the issue, feel free to contact us via supprt.
Posted Jan 29, 2025 - 11:45 CET
Investigating
Some customers are reporting issues with Clarify ingestion via MQTT Sparkplug B. We are currently looking into the issue.