Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
technical:mqtt-hands-on [2022/06/22 07:38] admin [GPIO Helper Scripts] |
technical:mqtt-hands-on [2022/06/25 17:36] (current) admin |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ===== Background ===== | ===== Background ===== | ||
| * Although the heartbeat system used in MESHdesk / APdesk allows for remote command execution there might be situations where you need the immediate command execution. | * Although the heartbeat system used in MESHdesk / APdesk allows for remote command execution there might be situations where you need the immediate command execution. | ||
| - | * Security is a big thing where I stay and with this hands on lab we will see how to make use of the MQTT implementation to switch outdoor lights remotely on and off. | + | * Security is a big thing where I stay and with this hands on lab we will see how to make use of the MQTT implementation to switch outdoor lights remotely on and off using one of the mesh nodes' GPIOs |
| * For this lab we have: | * For this lab we have: | ||
| * MESHdesk managing a mesh network that has the following hardware | * MESHdesk managing a mesh network that has the following hardware | ||
| Line 14: | Line 14: | ||
| * One will be installed at the **backyard**. | * One will be installed at the **backyard**. | ||
| {{: | {{: | ||
| + | |||
| + | <WRAP center round tip> | ||
| + | * MESHdesk allows you to manage hardware from various vendors in **one mesh network**. | ||
| + | * In this mesh network we have **Xiaomi** which are Mediatek based and currently sold in many places. | ||
| + | * We also have **Dragino** which are Atheros based and have been on the market for more than a decade. | ||
| + | |||
| + | </ | ||
| + | |||
| ===== GPIO Pins of Dragino MS14 ===== | ===== GPIO Pins of Dragino MS14 ===== | ||
| Line 38: | Line 46: | ||
| * If we want to set GPIO 18 on the Dragino we can issue the following **/ | * If we want to set GPIO 18 on the Dragino we can issue the following **/ | ||
| * To clear it **/ | * To clear it **/ | ||
| - | * If we want to flash (on-off) GPIO 18 a couple of times. **/ | + | * If we want to flash (on-off) GPIO 18 a couple of times: **/ |
| * The default on-off transition is with one second intervals. There is an optional parameter where you can set the interval in seconds. | * The default on-off transition is with one second intervals. There is an optional parameter where you can set the interval in seconds. | ||
| * / | * / | ||
| Line 54: | Line 62: | ||
| * Note that we did not make those commands available to sub-providers. This way we can keep certain predefined commands **private** to an access provider. | * Note that we did not make those commands available to sub-providers. This way we can keep certain predefined commands **private** to an access provider. | ||
| * These commands can now be used when defining schedules e.g. if you want to set the lights on and off on certain times or when you want to send the command to the mesh node or access point immediately. | * These commands can now be used when defining schedules e.g. if you want to set the lights on and off on certain times or when you want to send the command to the mesh node or access point immediately. | ||
| + | |||
| + | Since this is a page about hands on work we end with a demonstration video showing things in action. | ||
| + | |||
| + | ===== In action video ===== | ||
| + | {{youtube> | ||
| + | |||