Clarification about MQTT tag modes (publish vs subscribe) and memaddress behavior

[RocVILAAigues]

Hi,
We're integrating FUXA with Node-RED via MQTT, and we're a bit confused about the behavior of tag communication modes.

We’ve observed the following:

When a tag is set as publish, we can update its value from the FUXA interface, and the change is correctly published via MQTT — this works as expected.

When a tag is set as subscribe, we expected it to only receive values from MQTT (read-only). However, we noticed that it also publishes value changes, even though it does not have a pubs field in its configuration.

Additionally, subscribe tags include a memaddress field, while publish tags do not.

Here are two simplified examples from our .json configuration:

Subscribe tag:
{
"id": "t_123456",
"name": "device/topic/status",
"type": "raw",
"memaddress": "device/topic/status",
"address": "device/topic/status",
"options": {
"subs": ["device/topic/status"]
},
"daq": {
"enabled": false,
"interval": 60,
"changed": false,
"restored": false
},
"timestamp": 1752481311325
}

Publish tag:
{
"id": "t_654321",
"name": "device/topic/command",
"type": "raw",
"address": "device/topic/command",
"options": {
"pubs": [{
"type": "value",
"key": "",
"value": "device/topic/command",
"name": "device/topic/command"
}]
},
"daq": {
"enabled": false,
"interval": 60,
"changed": false,
"restored": false
}
}

Could you please clarify:

• What is the role of the memaddress field in a subscribe-mode tag?
• Why do subscribe-mode tags seem to publish value changes, even without the pubs field?
• Is this behavior expected, or is it possibly a misconfiguration or unintended?
• Finally, is there any real functional difference between declaring a tag as publish or subscribe, especially if both seem to allow publishing changes via MQTT?

Thanks a lot for your help and for the great work on FUXA!

[unocelli]

Hi, I agree, the current implementation does not fully respect the intended distinction between “subscribe-only” and “publish-only” tags, which can be misleading.
It should be reviewed and adjusted to align with the expected behavior.

[jingshui127]

现在这样也蛮好。已经自己在网关做了适配😊