If your SDK setup appears correct but the rover's wheels don't move despite /control returning {"message":"Command sent successfully"}, this is likely caused by the SDK not being enabled for your bot on the FrodoBots backend.
Symptoms of this issue:
/datareturns good telemetry (battery, GPS, orientation) ✅/controlreturns{"message":"Command sent successfully"}✅/speakworks — TTS plays through the rover speaker ✅lamp=1works — headlight turns on ✅But speed stays 0, all RPMs stay
[0,0,0,0], and wheels don't physically turn ❌Tried both
/controland/control-legacy— same result ❌Tried with and without
MISSION_SLUG— same result ❌
Root Cause
There are two things required for full SDK access:
| What it unlocks |
SDK Access Token | Camera feed, telemetry, data, TTS, lamp control |
SDK Enabled on backend | Ability to create a ride/mission programmatically, which allows |
Having an SDK Access Token alone is not enough to move the motors. The SDK must also be enabled on our backend for your bot, which allows you to create and start a mission programmatically — without this, control commands are received but ignored by the rover.
How to Fix
Contact FrodoBots support and request to have SDK enabled for your bot. You can do this via:
💬 Chat Widget — available on the platform
🎮 Discord — open a support ticket
📧 Email — hello@frodobots.com
Please provide your bot slug (3-word code) so the team can enable it for you on the backend.
Once enabled, restart the SDK and try again:
bash:
py -3.11 -m hypercorn main:app --reload
Additional Note:
If you see an active mission in /missions-history with status active because the dashboard opened one, make sure to:
Close the FrodoBots web dashboard tab entirely
Restart the SDK
Running the dashboard and SDK simultaneously may cause the SDK to join as a viewer instead of a driver, meaning movement commands are ignored.
💡 Need help? Contact us via the chat widget, join our Discord, or email hello@frodobots.com (Mon–Fri, 9AM–6PM SGT).