Separate the AP SSID from the Wi-Fi WAN Client
The RUTM56 application uses one wireless interface as a WAN client and another as an access point. Event Juggler's available Wi-Fi action controls Wi-Fi collectively, so it cannot directly select only the AP SSID. Configure the GPIO event to run a script that changes the target wireless interface instead.
Identify the AP interface before creating the action. Run the following command and match the reported wireless sections to the access-point SSID:
uci show wirelessDo not assume that default_radio0 is the correct RUTM56 interface. That identifier comes from a RUTX50 default 2.4 GHz SSID example and must be replaced with the section associated with the required AP.
Control the Selected SSID with UCI
Use separate Event Juggler scripts for the switch states. Replace <ap_section> with the section found through uci show wireless.
# Disable the selected AP interface
uci set wireless.<ap_section>.disabled='1'
uci commit wireless
/etc/init.d/network restart
# Enable the selected AP interface
uci del wireless.<ap_section>.disabled
uci commit wireless
/etc/init.d/network restartThe network restart applies the UCI change but restarts all network interfaces. Expect a short connectivity interruption, including possible disruption to the Wi-Fi WAN client. Verify this behavior on the RUTM56 before relying on the GPIO control operationally.
API Alternative and Verification
An API action can target the wireless interface without a UCI commit. The documented example targets default_radio0; substitute the verified RUTM56 AP interface identifier:
# Disable
api put /wireless/interfaces/config/<ap_section> '{"data":{"enabled":"0"}}'
# Enable
api put /wireless/interfaces/config/<ap_section> '{"data":{"enabled":"1"}}'The available evidence indicates that an API update does not require a network restart, while the UCI method explicitly restarts the network. Test each GPIO state by confirming that the AP SSID disappears when disabled and returns when enabled. During both transitions, verify whether the wireless WAN client remains connected; if it drops with the UCI method, evaluate the API method.
Frequently Asked Questions
Can Event Juggler disable one RUTM56 SSID directly?
The available Event Juggler Wi-Fi action controls Wi-Fi collectively. Use its script action to change only the wireless interface assigned to the AP SSID.
How do I find the RUTM56 interface name for an SSID?
Run uci show wireless and identify the section associated with the required AP. Do not copy default_radio0 without verifying it, because that name is from a RUTX50 example.
Will changing one SSID interrupt the Wi-Fi WAN connection?
The UCI procedure runs /etc/init.d/network restart, which restarts all network interfaces and can cause a short interruption. The API method is indicated not to require that restart, but verify both SSID control and WAN continuity on the RUTM56.