I need your guide to connect to EMQX.
I made the connection on the Gateway and no issues.
Now how I can subscribe to a Topic on EMQX?
Now how I can subscribe to a Topic on EMQX?
You're going to have to provide more information.
It looks like you're already connected with Ignition, but if you're using SparkplugB, it's not as easy to just eavesdrop and monitor the data going back and forth. SparkplugB does make it easy to get your tags as it automatically will bring in tags as they're published from the edge (MQTT Transmission). If you're using plain MQTT topics without SparkplugB, you'll have to do a custom namespace, which I've never done personally, but there should be documentation on how to do this on Cirrus Link's website.
https://docs.chariot.io/display/CLD80/MQTT+Engine+Custom+Namespace
1 Like
In my case I don't have devices in a real sense I have just a EMQX server and will publish data here. And I need to read that data from EMQX .
Does it look like the only way to do that is with custom Name space?
Try our tutorial for 5 minutes at
or see this 3-minute video how to connect Ignition to your broker
Good luck!
Just for someone who will need it for reference .
You need to create a custom namespace
And then you can see the Tag on the MQTT Engine Custom Tag on the MQTT Engine
Just wanted to point out that the format of your topic is very similar to the Sparkplug format. If you're trying to simulate the end device, if it's pushing Sparkplug data, you won't need a custom namespace as there will be a sequence of published messages (mainly a birth which publishes all of the tags and folder structure along with initial values and timestamps), followed by the NDATA or DDATA messages to update the tags published by the birth messages.
Personally, I'd say try to get your hands on an actual device to verify how it's pushing data because it will come through differently if it is using SparkplugB and you'll have to rework everything to follow that tag structure.
2 Likes
The topics I am using don't show automatically.
The EMQX I am using doesn't enable the sparkplug b (is possible but I guess the version a I using can't be configured). For now, my course of action will be custom for each Topic I will read .
I will refine my solution if the timeline allows me. And I will share my results.
The MQTT broker doesn't care if it's SparkplugB or standard topics. It's all just MQTT to the broker. It's just facilitating the transfer of the data between the various clients. This is all dependent on the end devices that will be used and not the server/broker.
1 Like