From 560e2fda9901031b73b743c0470889225c86d1b7 Mon Sep 17 00:00:00 2001 From: Dale LaBossiere Date: Tue, 28 Feb 2017 14:13:32 -0500 Subject: [PATCH 1/2] [Edgent-176] document MqttDevice's MQTT messsage format. --- .../connectors/mqtt/iot/MqttDevice.java | 35 ++++++++++++++++++- 1 file changed, 34 insertions(+), 1 deletion(-) diff --git a/connectors/mqtt/src/main/java/org/apache/edgent/connectors/mqtt/iot/MqttDevice.java b/connectors/mqtt/src/main/java/org/apache/edgent/connectors/mqtt/iot/MqttDevice.java index f2836075..24d26ba6 100644 --- a/connectors/mqtt/src/main/java/org/apache/edgent/connectors/mqtt/iot/MqttDevice.java +++ b/connectors/mqtt/src/main/java/org/apache/edgent/connectors/mqtt/iot/MqttDevice.java @@ -43,9 +43,14 @@ Licensed to the Apache Software Foundation (ASF) under one * the {@link MqttStreams} connector. *

* The connector doesn't presume a particular pattern for - * Device MQTT "event" topic and "command" topics though default + * Device MQTT "event" and "command" topics though default * patterns are provided. *

+ * The MQTT message content for device events and device messages must be JSON, + * but the contents of the JSON are under the control of the collaborating MQTT clients. + * See {@link #commands(String...)} and {@link #events(TStream, String, int) events()} + * for a description of how MQTT messages are converted to and from stream tuples. + *

* Connector configuration Properties fall into two categories: *