Another problem i keep running into, is that MQTT topics have no 'discoverability'. Each client must be hard coded to know exactly which topics to subscribe too, and know how to interpret the data on that topic.
It would be nice if an optional data model could be overlayed on top of MQTT, like BLE GATT does over ATT.
I would like to be able to things like:
(1) enumerate topics
(2) find topics of a specific type (which could be a UUID - something orthogonal to their physical tree structure)
(3) provide descriptors for topics with more metadata, etc.
Comments
Another problem i keep running into, is that MQTT topics have no 'discoverability'. Each client must be hard coded to know exactly which topics to subscribe too, and know how to interpret the data on that topic.
It would be nice if an optional data model could be overlayed on top of MQTT, like BLE GATT does over ATT.
I would like to be able to things like: (1) enumerate topics (2) find topics of a specific type (which could be a UUID - something orthogonal to their physical tree structure) (3) provide descriptors for topics with more metadata, etc.