Update page 'Message Queue Endpoint'
This commit is contained in:
parent
5d56a944b8
commit
672d36ed33
@ -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).
|
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).
|
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.
|
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.
|
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.
|
Each `SensorType` holds a key and a value, where the key identifies the Sensortype, and the value is the value of the sensor.
|
||||||
|
Loading…
Reference in New Issue
Block a user