MQTT Engine Custom Namespace tags becoming Bad_Stale after ~10 minutes. Is the timeout configurable?

Ignition Modules MQTT Modules
1

Hi,

I’m running:

  • Ignition 8.3.2
  • MQTT Engine 5.0.2
  • Custom Namespace with JSON payload parsing

I’ve noticed that MQTT Engine tags eventually transition to Bad_Stale when updates stop arriving.

To test this, I intentionally removed a topic from the broker. The tags remained Good for several minutes and then became Bad_Stale. Based on the timestamps in Tag Diagnostics, the transition occurred approximately 565 seconds (~9m25s) after the last update.

This raises a few questions:

  1. What mechanism is actually marking these tags as Bad_Stale?

  2. Is the stale timeout configurable?

2

Rafael,

The Bad_Stale occurs when Engine loses connection to the Broker and Engine no longer knows the Status of those Tags.

If you are trying to understand why the Bad_Stale Quality you should investigate the network connection status. The Ignition logs should show the loss of connection. Your Broker will/should also have log entries. If those logs report only a status changes but no clear indication why then a deeper dive by your Network Security team into your Network will be required.

There is no timeout configuration or adjustment available.

Dan