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
Next revisionBoth sides next revision
docs:guide-user:hardware:hardware.button [2020/01/02 20:59] – Adding an example (5-bis) similar to example 5 for more precise Wi-Fi toggling - Minor change (warning sign) etimsdocs:guide-user:hardware:hardware.button [2022/04/27 15:48] – [Attach functions to a push button] some1
Line 2: Line 2:
 There several ways for controlling buttons in OpenWrt. There several ways for controlling buttons in OpenWrt.
   * [[#procd_buttons| buttons using procd]]   * [[#procd_buttons| buttons using procd]]
-  * [[#Hotplug_Buttons|Hotplug buttons]], using the hotplug daemon or procd in compatibility mode (hotplug itself was phased out with r36003).+  * [[#Hotplug_Buttons|Hotplug buttons]], using the hotplug daemon or procd in compatibility mode (hotplug itself was phased out with r36003, circa 2013).
   * [[#HID_buttons|HID buttons]], using ///dev/input/event// with an application like triggerhappy.   * [[#HID_buttons|HID buttons]], using ///dev/input/event// with an application like triggerhappy.
  
Line 10: Line 10:
 Native button handling in procd is handled by scripts in ''/etc/rc.button/*''. Native button handling in procd is handled by scripts in ''/etc/rc.button/*''.
  
-These scripts receive the **same** environment as older style [[docs:guide-user:base-system:hotplug|hotplug]] buttons received. +These scripts receive the **same** environment as older style [[docs:guide-user:base-system:hotplug|hotplug]] buttons received.   
-However, the script files have to be named after the button. + 
-I am unaware of a way of getting the button name. +To get the button name you can try: 
-(Other than using hotplug compatible scripts with procd ;)+  * ''cat /sys/kernel/debug/gpio'' 
 +  * or use hotplug compatible scripts with procd 
  
 ^ Button Action ^ Script Environment ^ Script return value ^ ^ Button Action ^ Script Environment ^ Script return value ^
Line 20: Line 22:
 | Release | ACTION="released" SEEN="<seconds held>" | n/a | | Release | ACTION="released" SEEN="<seconds held>" | n/a |
  
-Note that "released" action is sent on release even if "timeout" has been sent.+:!: "released" action is sent on release even if "timeout" has been sent. 
 + 
 +<WRAP round box 60%> 
 +Please consider using these kernel codes when adding support for new devices, they're mapped by the gpio-button-hotplug kernel module: 
 +^ Kernel code ^ event ^ 
 +| BTN_0 | BTN_0 | 
 +| BTN_1 | BTN_1 | 
 +| BTN_2 | BTN_2 | 
 +| BTN_3 | BTN_3 | 
 +| BTN_4 | BTN_4 | 
 +| BTN_5 | BTN_5 | 
 +| BTN_6 | BTN_6 | 
 +| BTN_7 | BTN_7 | 
 +| BTN_8 | BTN_8 | 
 +| BTN_9 | BTN_9 | 
 +| KEY_BRIGHTNESS_ZERO | brightness_zero | 
 +| KEY_CONFIG | config | 
 +| KEY_COPY | copy | 
 +| KEY_EJECTCD | eject | 
 +| KEY_HELP | help | 
 +| KEY_LIGHTS_TOGGLE | lights_toggle | 
 +| KEY_PHONE | phone | 
 +| **KEY_POWER** | **power** | 
 +| **KEY_POWER2** | **reboot** | 
 +| **KEY_RESTART** | **reset** | 
 +| **KEY_RFKILL** | **rfkill** | 
 +| KEY_VIDEO | video | 
 +| KEY_VOLUMEDOWN | volume_down | 
 +| KEY_VOLUMEUP | volume_up | 
 +| KEY_WIMAX | wwan | 
 +| KEY_WLAN | wlan | 
 +| KEY_WPS_BUTTON | wps | 
 + 
 +</WRAP>
  
 ===== Hotplug Buttons ===== ===== Hotplug Buttons =====
Line 108: Line 143:
 uci set system.@button[-1].action="pressed" uci set system.@button[-1].action="pressed"
 uci set system.@button[-1].handler="uci set wireless.@wifi-device[0].disabled='1' && wifi" uci set system.@button[-1].handler="uci set wireless.@wifi-device[0].disabled='1' && wifi"
-uci commit system +uci commit system
 </code> </code>
  
Line 172: Line 207:
 } }
 EOF EOF
 +chmod u+x /usr/bin/wifionoff
 </code> </code>
  
Line 182: Line 218:
 STATEFILE="/tmp/wifionoff.state" STATEFILE="/tmp/wifionoff.state"
  
-if [ "${#}" -eq "1]; then+if [ "${#}" -eq 1 ]; then
     case "${1}" in     case "${1}" in
-        "up"|"on"STATE="off" ;; +        "up"|"on"GOAL="on" ;; 
-        "down"|"off"STATE="on" ;;+        "down"|"off"GOAL="off" ;;
     esac     esac
 else else
-    if [ -e "${STATEFILE}" ]; then +    if [ -e "${STATEFILE}" ]; then 
-        STATE="on"+ GOAL="on"
     else     else
-        source "${STATEFILE}"+        # if the statefile doesn't exist, turn wifi off 
 +        GOAL="off"
     fi     fi
 fi fi
-if [ -z "${STATE}" ]; then +  
-    STATE="on" +if [ "${GOAL}" = "off" ]; then
-fi +
- +
-if [ "${STATE}" = "on" ]; then+
     /sbin/wifi down     /sbin/wifi down
-    STATE="off"+    touch "${STATEFILE}"
 else else
     /sbin/wifi up     /sbin/wifi up
-    STATE="on"+    # file may not exist if we're given args 
 +    rm "${STATEFILE}2> /dev/null || true
 fi fi
- 
-echo "STATE=${STATE}" > "${STATEFILE}" 
 EOF EOF
 +chmod u+x /usr/bin/wifionoff
 </code> </code>
  
Line 216: Line 250:
 One way to find out your Wireless Network configuration name in LuCi is to navigate to the "Wireless Overview" page (Network > Wireless) and edit the wireless network configuration you need to toggle. For example, change temporarily the ESSID value and then click "SAVE" (and __NOT__ "SAVE & APPLY"). You will then see the button "UNSAVED CHANGES" in the upper right corner of the interface. Click on it and you should be able to find an entry such as "uci set wireless.cfg033579.ssid='My-Own-Wi-Fi-test'" where "cfg033579" stands for your configuration name that you need to change in the following script. One way to find out your Wireless Network configuration name in LuCi is to navigate to the "Wireless Overview" page (Network > Wireless) and edit the wireless network configuration you need to toggle. For example, change temporarily the ESSID value and then click "SAVE" (and __NOT__ "SAVE & APPLY"). You will then see the button "UNSAVED CHANGES" in the upper right corner of the interface. Click on it and you should be able to find an entry such as "uci set wireless.cfg033579.ssid='My-Own-Wi-Fi-test'" where "cfg033579" stands for your configuration name that you need to change in the following script.
  
-__/!\__ Warning ! Do not forget to allow the script execution with the command : **chmod u+x /usr/bin/wifinetonoff** 
 <code bash> <code bash>
 uci add system button uci add system button
Line 236: Line 269:
 } }
 EOF EOF
 +chmod u+x /usr/bin/wifinetonoff
 </code> </code>
  
Line 264: Line 298:
 uci commit system uci commit system
 </code> </code>
- 
 ==== WR1043ND ==== ==== WR1043ND ====
 If you decide to use the ''wifitoggle'' package, you will need to change a few things on the default configuration. If you decide to use the ''wifitoggle'' package, you will need to change a few things on the default configuration.
Line 319: Line 352:
 Notes: Notes:
   * triggerhappy repeats commands twice: see bug https://dev.openwrt.org/ticket/14995   * triggerhappy repeats commands twice: see bug https://dev.openwrt.org/ticket/14995
-  * kernel modules: **kmod-hid** and **kmod-hid-generic** both should be installed\\ The kmod-hid-generic kernel module must be installed for buttons on USB devices such as USB sound cards to work in OpenWrt trunk. Only then the /dev/input/event0 node for the buttons was created on the DIR-505 router with attached USB sound card.+  * kernel modules: **kmod-hid** and **kmod-hid-generic** both should be installed\\ The **kmod-hid-generic** and supposedly also **kmod-usb-hid** kernel module must be installed for buttons on USB devices such as USB sound cards to work in OpenWrt trunk. Only then the /dev/input/event0 node for the buttons was created on the DIR-505 router with attached USB sound card.
  
 <code> <code>
  • Last modified: 2022/09/25 20:08
  • by kirelagin