RADIUSdesk

logo
Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
technical:mqtt-hands-on [2022/06/22 05:29]
admin [GPIO Pins of Dragino MS14] 		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 13: Line 13:
               * One will be installed at the **driveway**.               * One will be installed at the **driveway**.
               * One will be installed at the **backyard**.               * One will be installed at the **backyard**.
-        * //!!!Insert Photo of setup here!!!//+{{:technical:iot_mesh.jpg|}} 
 + 
 +<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. 
 + 
 +</WRAP> 
  
 ===== GPIO Pins of Dragino MS14 ===== ===== GPIO Pins of Dragino MS14 =====
Line 32: Line 40:
 ===== GPIO Helper Scripts ===== ===== GPIO Helper Scripts =====
   * The latest version of the MESHdesk firmware includes the following folder **/etc/MESHdesk/gpio_utils**.   * The latest version of the MESHdesk firmware includes the following folder **/etc/MESHdesk/gpio_utils**.
-  * There we will keep handy scripts for GPIO management.+  * There we will keep helper scripts for GPIO management.
   * The following is currently there:   * The following is currently there:
         * /etc/MEHdesk/gpio_utils/gpio_set_clear.sh         * /etc/MEHdesk/gpio_utils/gpio_set_clear.sh
Line 38: Line 46:
   * If we want to set GPIO 18 on the Dragino we can issue the following **/etc/MEHdesk/gpio_utils/gpio_set_clear.sh 18 1**.   * If we want to set GPIO 18 on the Dragino we can issue the following **/etc/MEHdesk/gpio_utils/gpio_set_clear.sh 18 1**.
   * To clear it **/etc/MEHdesk/gpio_utils/gpio_set_clear.sh 18 0**.   * To clear it **/etc/MEHdesk/gpio_utils/gpio_set_clear.sh 18 0**.
-  * If we want to flash (on-off) GPIO 18 a couple of times. **/etc/MEHdesk/gpio_utils/gpio_flash.sh 18 15**+  * If we want to flash (on-off) GPIO 18 a couple of times: **/etc/MEHdesk/gpio_utils/gpio_flash.sh 18 15**
   * 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.
   * /etc/MEHdesk/gpio_utils/gpio_flash.sh 18 15 **30** will increase the transition interval to 30 seconds.   * /etc/MEHdesk/gpio_utils/gpio_flash.sh 18 15 **30** will increase the transition interval to 30 seconds.
Line 45: Line 53:
  
 ===== Predefined Commands ===== ===== Predefined Commands =====
 +  * Predefined Commands can be used in two places.
 +        * When building schedules that can be associated with mesh nodes and access points.
 +        * When sending commands to mesh nodes and access points.
 +  * To manage predefined commands you need to go to **Other** -> **Schedules** and click on the **Predefined Commands** button to launch the applet.
 +{{:technical:schedules.png|}}
 +  * We added the following commands for our three lights. 
 +{{:technical:predefined.png|}}
 +  * 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.
 +
 +Since this is a page about hands on work we end with a demonstration video showing things in action.
 +
 +===== In action video  =====
 +{{youtube>FLkcrjXw2Wc?large}}
 +
  
  
Last modified: 2022/06/22 05:29