Read subtopics with MQTT Engine

I have some Shellys inside my home and I configured its in MQTT protocol.
I installed MQTT Enginde inside gateway and I want to read a subtopics.
Below the situation inside my broker Mosquitto


I want to read a status topic and the payload inside but the situation in my tags browser in Ignition is this

I can see only topic “0”.
Why?
Is there is some reason?
Where am I wrong?

Check read as json string in the name space

Can you show me how to do it?

Gateway config page=>MQTT Engine=>Namespaces=>Edit on your custom Namespace then click the check box on JSON Payload

I clicked there and I checked JSON Payload but I do not see any changing in the tags. In my first image about tags browser, JSON Payload was checked and I can not see under topic “0”.
I do not see power, energy, status and so on.
Broker.html (208 Bytes)

Any ideas?

Now I understood the problem. I solved this issue by deleting the folder “Shellies” in my Tag Browser inside the designer. So Ignition ricreated the folders and I found all data.
Now I have another problem, I do not able to change the value of the topic.
Below the error

Who can help me?

There is an advanced option on the custom namespace to make tags writable, however it’s my understanding that this only makes the tags locally writable and the value will not be published to the broker.

I think only Sparkplug namespaces have the ability to write and publish values.

@wes0johnson can confirm

In fact I checked the property “Writeable Tags” but the result is the same error.

In the case of this possibility is only with Sparkplug namespaces is there other way to publish values?

Looks like maybe there are scripting functions: https://docs.chariot.io/display/CLD80/Gateway+Script+MQTT+Publishing

Oh thank you so much, now work well.
In any case do you let me know if there is same possibility to write and publish value directly?
thank you so much for the support.

Yes - all of this is correct. Also as you noted later in the thread, scripting is the recommended way of publishing MQTT messages to non-Sparkplug compliant MQTT clients.

2 Likes