From 672d36ed335ed194086bdcbca3685e0dc27b0bf3 Mon Sep 17 00:00:00 2001 From: auke Date: Sun, 1 Mar 2020 11:51:10 +0000 Subject: [PATCH] Update page 'Message Queue Endpoint' --- Message-Queue-Endpoint.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Message-Queue-Endpoint.md b/Message-Queue-Endpoint.md index 7ca8336..1d9f018 100644 --- a/Message-Queue-Endpoint.md +++ b/Message-Queue-Endpoint.md @@ -75,7 +75,9 @@ Farmmaps uses protobuf to specify a structure for the messages published in MQTT More information on protobuf can be found at [Google Developer Documentation](https://developers.google.com/protocol-buffers/docs/overview). Python objects can easily be converted to protobuf messages and back (when recieving messages from the broker). -The message structure for the data can be found in `farmmaps/farmmaps.proto`, and is shown below. +The message structure for the data can be found in `farmmaps/farmmaps.proto`, and is shown below. + +**Datastructure explained** The main message is the Datapoint object, containing time, location, machine-id and a reference to metadata. Then, there is a `sensors` parameter, which holds a dictionary of `SensorType` objects. Each `SensorType` holds a key and a value, where the key identifies the Sensortype, and the value is the value of the sensor.