As soon as we add a custom namespace, all of our values go to ‘bad_stale’ in MQTT Engine.
It doesn’t matter what we add in the custom namespace, it just goes bad immediately.
What could be causing this?
As soon as we add a custom namespace, all of our values go to ‘bad_stale’ in MQTT Engine.
It doesn’t matter what we add in the custom namespace, it just goes bad immediately.
What could be causing this?
For the tags that are going stale - are they coming in via Sparkplug B (i.e. MQTT Transmission)? When you create a Custom Namespace, MQTT Engine restarts. This in turn causes all Sparkplug tags in MQTT Engine to go stale. Using ‘Primary Host ID’ in Engine and the associated Transmission Server sets will prevent this by forcing them to send new BIRTH messages.
Hi Wes,
We managed to workaround this by reinitializing the MQTT Transmission after we add a namespace.
We kept on having bad_stale, even when we use Primary Host ID.
This shouldn’t be happening - do you have primary host ID set on both the Engine and Transmission sides?
Yes we have. If one of you would like to take a look, I have the issue quite isolated.