First time Ignition user.
Trying to get MQTT data (non sparkplug) into Designer 8.3.1 via Gateway with Custom Namespaces, Windows 11.
I have tried three separate MQTT brokers, Mosquitto local, Mosquitto on a remote machine and MQTT-Distributer locally. All three brokers can be r/w via two third party clients.
Via the Gateway logs (and verifying on the broker end) I can see the TCP connections connect and disconnect as expected.
I have followed the how to instructions but can see the Gateway is never actually polling any of the topics, have tried countless combos. I believe this why I have never seen anything populated in the tag browser in Designer?
I have disabled Elecsys and Sparkplug B. I can see the annoying “IamHost” being populated in Brokers. I have also reinstalled from scratch as I notice the Custom Namespace doesn’t always clear when deleted.
Any ideas?
The broker doesn’t matter as long as it conforms to the standard and the user ignition is logging in as has appropriate access permissions to read the topics you have subscribed to.
The IamHost is most likely the ignition server publishing its host state for sparkplug B devices to know it is online. You can disable the publishing of that message by saying that the ignition server is not a sparkplug b primary host.
The most important thing to point out is that there is no polling. MQTT is a pub/sub. Once you have your subscription setup, you should be able to publish whatever you like into the topics you have subscribed to and see the tags get generated in the engine tag provider. If the topic content is a json payload, you can even get engine to parse that and generate the tag structure to match.
I’ve got this working ok (same sort of setup)
One thing I did need to do after setting up a Custom namespace for the first time was restart the gateway and then it all started working. (Or disable and enable the MQTT Gateway)
And of course I made sure the ignition MQTT user was configured to be able to read the topic path in Mosquito too…turns out it doesn’t work very well if that step isn’t done…oops.
Thanks Craig, good to know it “can” work.
In parallel I can publish Spark Plug MQTT data using MQTT Transmission, then using MQTT Engines to read them back, I can see the TCP request polling/populating the topics from the broker and see subsequent Designer browser tags.
When I populate the non sparkplug topics, I can’t get theMQTT Engine to request the tags, nothing comes out on the tcp side.
I wonder if somehow not having user/password configured on the broker is affecting this? I think that is what you are implying, will try.
Can confirm I’m using a user/password combo in Mosquitto and explicit readwrite access to the topic path in the ACL file:
user <redacted>
topic readwrite BMC/#
topic read $SYS/#
I haven’t tried it anon as my requirements are to have authentication enabled for any writes.
Also, just for you to try, I have “Create Writable Tags” enabled for my Custom Namespace:
No luck, passwords and ACLs setup.
I found this in the logger files:
The only filter I can find in Gateway MQTT Engine is under the Server tab and it is blank.
If anyone else has an idea how to find why all topics are filtered, it would be appreciated.
Edited to add: I can subscribe to the broker with third party clients, I’m fairly confident the issue is in Ignition, I have two separate VMs configured and both are behaving the same way.
Every so often I can not delete a custom namespace, would that be a symptom of something else going on?
8.15 works, it looks like an issue with 8.3.
Nice first impression, ugh.
