We keep documentation on our findings about EMO, the desktop robot by Living.AI. Most API findings are based on captured traffic of firmware 3.2.0 (ver 42) and older firmware 1.x; every page says which one it is about where it matters.
- How to capture - How to capture, study, and analyze information sent to and from EMO.
- How to decompile - How to decompile EMOs firmwares with Ghidra.
- Our assumptions - Various assumptions we have made, aka educated guesses.
- api.living.ai Server - The cloud API EMO talks to (https): time, token, status reports, weather, TTS, ChatGPT mode and speech intent detection. Has an endpoint index.
- tts.living.ai Server - The old text-to-speech download server (potentially deprecated as of firmware 3.0.0, TTS is now served as mp3 from the eu-emo-tts hosts).
- Intents - Intent responses that we have documented being sent to EMO.
- Behaviors - Actions that EMO can do (the
rec_behaviorvalues of an intent response). - Animations - The animations EMO can play.
- Bluetooth - Bluetooth specific information.
- Firmware - Firmware versions, downloads, and firmware analysis (K210 protocol, animation system, idle behavior, libraries).
- Hardware - Any hardware information we find.