Gude Expert Net Control 2302, Manual

Page: 79 / 88

79
Expert Net Control 2302 © 2021 GUDE Systems GmbH
Specifications
As default the execution of commands is not allowed, but must be enabled in the
MQTT configuration! ("Permit CLI commands")
Format 1: Command in JSON Syntax
Publish Topic: "de/gudesystems/epc/00:19:32:01:16:41/cmd"
Publish Message: "{"type": "cli", "cmd": "port 2 state set 1", "id": 10}"
Response from device to "de/gudesystems/epc/00:19:32:01:16:41/cmdres"
"{"type": "cli", "cmdres": ["OK."], "result": {"num": 0, "hint": "ok"}, "id": 10}"
The JSON object "result" returns whether the command was valid. The object "id"
in the command is optional and is passed through in the response from the device.
The passed number can help to establish a synchronicity between command and re-
sponse via the broker.
Format 2: Raw Text
Publish Topic: "de/gudesystems/epc/00:19:32:01:16:41/cmd/cli"
Publish Message: "port 2 state set 1".
Response from device to "de/gudesystems/epc/00:19:32:01:16:41/cmdres/cli"
"OK."
Format 3: Simplified port switching
Publish Topic: "de/gudesystems/epc/00:19:32:01:16:41/cmd/port/2"
Publish Message: "0" or "1".
Response from device to "de/gudesystems/epc/00:19:32:01:16:41/cmdres/port/2"
"0" or "1"
This special form exists only for the port switching commands.
Device Data Summary
In the Device Data Summary the most important data of the device are summarized
in a JSON object and sent periodically in a configurable time interval. This summary
depends on the properties of the device and the connected sensors, and could look
like this:
Topic:
en/gudesystems/epc/00:19:32:01:16:41/device/telemetry
Message:
{
"type": "telemetry",
"portstates": [{
"port": "1",
"name": "Power Port",
"state": 1
}, {
"port": "2",
"name": "Power Port",
"state": 0
}, {
"port": "3",
"name": "Power Port",
"state": 0
}, {
"port": "4",