You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/standalone/zigbee2mqtt/README.md
+53-38Lines changed: 53 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,42 +1,54 @@
1
1
# Zigbee Sensor (MQTT)
2
2
3
-
This example describes the implementation of the [Standalone UCM](https://handbook.enapter.com/software/virtual_ucm/) concept using the opensource [Enapter python-sdk](https://github.com/Enapter/python-sdk) for monitoring Zigbee Sensor via MQTT protocol (Zigbee2Mqtt).
3
+
This example describes the implementation of the Standalone Device concept
4
+
using the opensource [Enapter
5
+
python-sdk](https://github.com/Enapter/python-sdk) for monitoring Zigbee Sensor
6
+
via MQTT protocol (Zigbee2Mqtt).
4
7
5
-
In order to use this UCM you need to have [Zigbee2MQTT](https://www.zigbee2mqtt.io/guide/installation/) and some MQTT broker (for example [Mosquitto](https://mosquitto.org)) running.
8
+
In order to use this Standalone Device you need to have
9
+
[Zigbee2MQTT](https://www.zigbee2mqtt.io/guide/installation/) and some MQTT
10
+
broker (for example [Mosquitto](https://mosquitto.org)) running.
6
11
7
-
As an example in this guide we will use the following dummy settings for configuration:
12
+
As an example in this guide we will use the following dummy settings for
13
+
configuration:
8
14
9
-
MQTT Broker Address: 192.168.192.190
10
-
11
-
MQTT Broker Port: 9883
12
-
13
-
MQTT User: mqtt_user
14
-
15
-
MQTT Password: mqtt_password
16
-
17
-
Device MQTT topic: zigbee2mqtt/MyDevice
15
+
- MQTT Broker Address: 192.168.192.190
16
+
- MQTT Broker Port: 9883
17
+
- MQTT User: mqtt_user
18
+
- MQTT Password: mqtt_password
19
+
- Device MQTT topic: zigbee2mqtt/MyDevice
18
20
19
21
## Requirements
20
22
21
-
It is recommended to run this UCM using Docker and Docker Compose. This will ensure that environment is correct.
22
-
23
-
The MQTT broker must be reachable from the computer where the Docker Container will be running.
23
+
It is recommended to run this Standalone Device using Docker and Docker
24
+
Compose. This will ensure that environment is correct.
24
25
25
-
## Step 1. Create Standalone UCM in Enapter Cloud
26
+
The MQTT broker must be reachable from the computer where the Docker Container
27
+
will be running.
26
28
27
-
Log in to the Enapter Cloud, navigate to the Site where you want to create Standalone UCM and click on `Add new` button in the Standalone Device section.
29
+
## Step 1. Create Standalone Device in Enapter Cloud
28
30
29
-
After creating Standalone UCM, you need to Generate and save Configuration string also known as ENAPTER_VUCM_BLOB as well as save UCM ID which will be needed for the next step
31
+
Log in to the Enapter Cloud, navigate to the Site where you want to create
32
+
Standalone Device and click on `Add new` button in the Standalone Device
33
+
section.
30
34
31
-
More information you can find on [this page](https://developers.enapter.com/docs/tutorial/software-ucms/standalone).
35
+
After creating Standalone Device, you need to Generate and save Configuration
36
+
string also known as `ENAPTER_STANDALONE_COMMUNICATION_CONFIG` as well as save
37
+
UCM ID which will be needed for the next step.
32
38
33
39
## Step 2. Upload Blueprint into the Cloud
34
40
35
-
The general case [Enapter Blueprint](https://marketplace.enapter.com/about) consists of two files - declaration in YAML format (manifest.yaml) and logic written in Lua. Howerver for this case the logic is written in Python as Lua implementation doesn't have SNMP integration.
41
+
The general case [Enapter Blueprint](https://marketplace.enapter.com/about)
42
+
consists of two files - declaration in YAML format (manifest.yaml) and logic
43
+
written in Lua. Howerver for this case the logic is written in Python.
36
44
37
-
But for both cases we need to tell Enapter Cloud which telemetry we are going to send and store and how to name it.
45
+
But for both cases we need to tell Enapter Cloud which telemetry we are going
46
+
to send and store and how to name it.
38
47
39
-
The easiest way to do that - using [Enapter CLI](https://github.com/Enapter/enapter-cli) to upload manifest.yaml into Cloud. The other option is to use [Web IDE](https://developers.enapter.com/docs/tutorial/uploading-blueprint).
48
+
The easiest way to do that - using [Enapter
49
+
CLI](https://github.com/Enapter/enapter-cli) to upload manifest.yaml into
0 commit comments