Edge computing and IIoT
Earlier articles
How-to
Identifying the source gateway in a shared historian database
The history does not land in one table. Each gateway connected to the shared database registers at least two rows in sqlth_drv, and the number in the sqlt_data_ table prefix is one of those row IDs, so the source is already recorded. Join sqlth_te to sqlth_drv for the tag-to-gateway map and filter the visualization on a site-code tag-path prefix, not on scan class names.
Troubleshooting
Why Ignition Edge MQTT payloads look like unreadable bytes
The unreadable characters are Sparkplug B's Protocol Buffers encoding rendered as text, which means the broker delivered the message intact. Fix the subscriber: select the Sparkplug decoder in MQTT.fx or use a Sparkplug-capable release such as MQTT Explorer v0.4.0-beta4. Leave the Edge Transmission format and the broker unchanged.
Troubleshooting
Ignition historian logs memory tags but not OPC tag changes
Memory tags record because their history subscription was created fresh; the migrated OPC tags carry a stale recording subscription that a storage-provider field edit alone does not rebuild. Fix one tag first: disable history, save, re-enable history with the production provider, and save again, then verify with one safely forceable fault before batching across the remaining tags.
Troubleshooting
Fixing an edge gateway MQTT TLS private key load failure
The errors error:0906D06C PEM routines:PEM_read_bio:no start line and error:140B0009 SSL routines:SSL_CTX_use_PrivateKey_file mean the gateway cannot parse its own private-key file, so the failure is local and happens before the broker sees anything. On a Flexy 205 running firmware 15.0s1 the confirmed correction is the 15.0s2 firmware upgrade with the same certificate files, not new keys or AWS IoT policy edits.
Troubleshooting
Trace an edge gateway MQTT connection failure to Azure Event Grid
A desktop MQTT client that connects and publishes with thumbprint authentication clears only that endpoint, certificate and permission combination on that host. When the gateway fails against the same Event Grid namespace, test four stages in order on the gateway itself: network path and DNS to TCP 8883, the TLS handshake with both certificate directions and the clock, the CONNECT identity, and publish authorization on the exact topic. The first stage that fails names the fix.
Troubleshooting
Trace Ignition Edge MQTT values that only update on refresh
Values that appear only after a refresh mean the Edge transmitter publishes nothing on its own: the forced republish masks a stalled change-driven path. Set a 10,000 ms scan rate with a 0.00000001 deadband and a moving signal publishes at the scan rate, then verify by counting 6 updates per minute with no refresh anywhere. Trace tag value and timestamp at each hop to find where it stops.
Troubleshooting
Why DB Table Historian is missing on Ignition 8.0
The DB Table Historian provider type does not exist in any Ignition 8.0.x gateway, regardless of module or license state: the type ships with the 8.1 line. The same configuration that lacks it on v8.0.2 shows it and populates MySQL on v8.1.4, so the fix is upgrading the gateway to 8.1.x and creating the provider on the existing connection.
How-to
Replaying buffered InfluxDB records to Azure IoT Hub over MQTT
Yes — but not with the TICK stack alone. Telegraf's MQTT output forwards the live stream, not database history, and Kapacitor aggregates; run a small replay worker that queries InfluxDB after a durable (time, name) cursor and publishes each raw record to Azure IoT Hub at QoS 1, advancing the cursor only on acknowledgment. At 1 record/s arriving, publish at 5 records/s so a full 7-day buffer of 604,800 records clears in 42 hours.
Troubleshooting
Why Flux mqtt.publish fails with Dialer.Dial in InfluxDB
Dialer.Dial called on an error dependency means the Flux runtime executing the task supplied no working network dialer, so mqtt.publish fails before any TCP connection to the broker. Correct the script, 1883 is the MQTT listener and 18083 the EMQX dashboard port, publish each point once with range(start: -task.every) via mqtt.to, and if the same error returns, publish with Telegraf outputs.mqtt instead of Flux.
How-to
How to publish InfluxDB v2 bucket data to MQTT
Run a scheduled Flux task on the InfluxDB v2 server that queries the bucket and passes each row to mqtt.to() from the experimental mqtt package. Test TCP 1883 or 8883 from the server host first, keep credentials in secrets, and set range(start: -task.every) so every: 1m publishes each minute exactly once.
How-to
How Sparkplug UDT definitions reach MQTT Engine
A UDT definition is not a file you import: it is a Template metric with isDefinition true published in the NBIRTH, and each DBIRTH instance binds to it by an exact-name templateRef. Build the births in Node-RED or on the Eclipse Tahu Node.js client, then verify the definition and the instance in the MQTT Engine tag provider.
Troubleshooting
Node-RED writes to InfluxDB on another PC time out
The write is an HTTP request to TCP 8086, and a successful ping proves only ICMP reachability. In the reported case the PC's firewall dropped the InfluxDB inbound rule on the Public profile; enabling it restored the writes. Diagnose the gateway-to-PC hop on its own and confirm which URL field the node actually dials.