User and technical documentation for the RB Switch
Test all three buttons:
If only one button fails, the problem may be isolated to that switch or input circuit.
If the buttons work in a normal text field but not in an accessibility feature, check the host’s Switch Control or Switch Access configuration.
This is expected behavior, not a fault. Android’s Switch Access setup wizard only ever asks for one or two switches; a third switch (Previous) must be assigned separately under Settings → Accessibility → Switch Access → Settings → Assign switches for scanning. See Android Switch Access for the full walkthrough. This does not affect iOS/iPadOS, Windows, macOS, Linux, or Chromebook, where all three buttons work through their normal setup flow.
Switch Access is distributed as a standalone app on the Google Play Store, separate from Android Accessibility Suite. Install or update it from the Play Store, then check Settings → Accessibility again. See Android Switch Access.
The production firmware sends one key press/release when a button changes from released to pressed and uses 35 ms debounce. A held button should not repeat.
If it does, inspect the switch, solder joints, input capacitor, ground connection, and PCB for damage or contamination.
Use a known data-capable USB-C cable. If necessary, use BOOT and RESET to enter the ESP32-S3 bootloader and retry.
D1 is controlled by the MCP73831 charger, not the BLE firmware.
Before connecting or replacing a battery:
A JST-PH connector alone does not guarantee compatible polarity.
For firmware or hardware issues, use the Firmware and Hardware pages and the production source files.