| ... | ... | @@ -11,14 +11,15 @@ title: MQTT Message specification |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Mqtt message spezification
|
|
|
|
|
|
|
|
Time.io uses different topics and messages to communicate between services. Here we try to specify and document the topics in use
|
|
|
|
|
|
|
|
### Topics
|
|
|
|
|
|
|
|
* [frontend_thing_update](mqtt-topic-frontend_thing_update): send (by the frontend) to inform (the configDB) about an update of a thing
|
|
|
|
* [qaqc_settings_update](mqtt-topic-qaqc_settings_update): send (by the frontend) to inform (the configDB) about an update of QC Settings
|
|
|
|
* [frontend_thing_update](mqtt-topic-frontend_thing_update): send (by the `frontend` service) to inform (the `worker-configdb-updater` service) about an update of a thing
|
|
|
|
* [qaqc_settings_update](mqtt-topic-qaqc_settings_update): send (by the `frontend` service) to inform (the `worker-configdb-updater` service) about an update of QC Settings
|
|
|
|
* [configdb_update](mqtt-topic-configdb_update): send to inform that an update in the configDB occurred
|
|
|
|
* [data_parsed](mqtt-topic-data_parsed): send if data was parsed successfully
|
|
|
|
* [qaqc_done](mqtt-topic-qaqc_done): send if QC run successfully on data
|
| ... | ... | |
| ... | ... | |
