Troubleshooting

Check it is powered (status light lit) and in Bluetooth range, and that Bluetooth and location permissions are granted to the app. Unplug and replug the device to restart it if needed.

The most common cause is a wrong argument count, that line is skipped silently on the device. Validate the payload in the app, which flags it. Also check for an unknown key name (for example del instead of delete) or a mis-typed keyboard layout. See Limitations.

The keyboard layout does not match the host. Set keyboardLayout to the host's locale; remember an unrecognised layout falls back to US English silently. See ZeroTrace Script.

A key name that is not recognised is dropped, so the combination is incomplete. Check every key name against the recognised list, for example use delete rather than del.

If the device was set not to start HID at boot, it stays silent until a payload runs enableHID. Otherwise, make sure a host field is focused and that you have started the payload from the app.

That is expected. The Dongle has no memory card and presents purely as a HID device, it never mounts as a drive. Storage mode is only available on full boards fitted with a memory card. See Hardware.

Check the license is activated on this device. Scan your license QR code in the app; the device stores and checks it. See Licensing.

A waitFor without a timeout blocks until the host toggles a lock light, which may never happen. Give it a timeout, or use a different trigger. See Flow & device control.

TraceNet is off by default. Enable it on both devices and give them the same passphrase, and keep them within short wireless range. See TraceNet.