MQTT topic implementation must be reworked
In pUbSub, the MQTT topic implementation has many issues that have to be corrected.
Reminder: the MQTT topic is configured for Pub in the message
and for Sub in dataset
The following issues have been reported
- XSD does not match the expected behavior
- The Python script for static configuration is not up to date
- There remain unused
mqttTopic
fields insopc_xml_loader.c
- There is no consistency check that
mqttTopic
is correctly set. Thus defining invalid (unused)mqttTopic
does not lead to any error or warning - This "inconsistency" between Pub & Sub is really not satisfying. I do not see any reason why a sender (Pub) can only configure the topic by message, and why a receiver (Sub) may expect different topics for different DSM within the same message