blue-merle/files/etc/gl-switch.d/sim.sh

#!/bin/sh

. /lib/functions/gl_util.sh

action=$1

logger -p notice -t blue-merle-toggle  "Called... ${action}"

if [ "$action" = "on" ];then
    mcu_send_message "Blue Merle ${action}"
    echo "on" > /tmp/sim_change_switch

elif [ "$action" = "off" ];then
    mcu_send_message "Blue Merle ${action}"
    echo "off" > /tmp/sim_change_switch

else
    echo "off" > /tmp/sim_change_switch
fi
sleep 1
switch: attempt to react to the hardware button I don't know whether this works. On the v4 firmware, we can see files in /etc/gl-switch.d but I don't know yet how the system determines which file to choose. I assume it's dependend on the "page" of the display. But I haven't figured out yet how or rather where those pages are organised. 2023-10-16 10:14:00 +00:00			`#!/bin/sh`

switch: show a message on toggling the button To see more easily whether we have control. 2023-10-16 14:10:17 +00:00			`. /lib/functions/gl_util.sh`

switch: attempt to react to the hardware button I don't know whether this works. On the v4 firmware, we can see files in /etc/gl-switch.d but I don't know yet how the system determines which file to choose. I assume it's dependend on the "page" of the display. But I haven't figured out yet how or rather where those pages are organised. 2023-10-16 10:14:00 +00:00			`action=$1`

switch: log action on the toggle It's a bit easier to follow than looking at the generated files. 2023-10-16 14:03:11 +00:00			`logger -p notice -t blue-merle-toggle "Called... ${action}"`

switch: attempt to react to the hardware button I don't know whether this works. On the v4 firmware, we can see files in /etc/gl-switch.d but I don't know yet how the system determines which file to choose. I assume it's dependend on the "page" of the display. But I haven't figured out yet how or rather where those pages are organised. 2023-10-16 10:14:00 +00:00			`if [ "$action" = "on" ];then`
switch: show a message on toggling the button To see more easily whether we have control. 2023-10-16 14:10:17 +00:00			`mcu_send_message "Blue Merle ${action}"`
switch: attempt to react to the hardware button I don't know whether this works. On the v4 firmware, we can see files in /etc/gl-switch.d but I don't know yet how the system determines which file to choose. I assume it's dependend on the "page" of the display. But I haven't figured out yet how or rather where those pages are organised. 2023-10-16 10:14:00 +00:00			`echo "on" > /tmp/sim_change_switch`

			`elif [ "$action" = "off" ];then`
switch: show a message on toggling the button To see more easily whether we have control. 2023-10-16 14:10:17 +00:00			`mcu_send_message "Blue Merle ${action}"`
switch: attempt to react to the hardware button I don't know whether this works. On the v4 firmware, we can see files in /etc/gl-switch.d but I don't know yet how the system determines which file to choose. I assume it's dependend on the "page" of the display. But I haven't figured out yet how or rather where those pages are organised. 2023-10-16 10:14:00 +00:00			`echo "off" > /tmp/sim_change_switch`
switch: show a message on toggling the button To see more easily whether we have control. 2023-10-16 14:10:17 +00:00
switch: attempt to react to the hardware button I don't know whether this works. On the v4 firmware, we can see files in /etc/gl-switch.d but I don't know yet how the system determines which file to choose. I assume it's dependend on the "page" of the display. But I haven't figured out yet how or rather where those pages are organised. 2023-10-16 10:14:00 +00:00			`else`
			`echo "off" > /tmp/sim_change_switch`
			`fi`
			`sleep 1`