← ClaudeAtlas

batoceralisted

Use when controlling, inspecting or debugging a Batocera Linux retro-gaming box over SSH - launching or stopping games, a game that quits by itself seconds after starting, driving EmulationStation menus with no gamepad, seeing what the TV shows, editing batocera.conf or es_settings.cfg, restarting EmulationStation, gamepad, hotkey or Bluetooth pairing problems.
vjt/batocera-skill · ★ 0 · Web & Frontend · score 72
Install: claude install-skill vjt/batocera-skill
# Batocera over SSH Batocera (x86_64, 40 and later: labwc Wayland desktop, EmulationStation front end) is driven as root over SSH: an HTTP API on `127.0.0.1:1234` for games, a kernel uinput keyboard for menus, `grim` for eyes. What the user changes lives under `/userdata`; the rest is a read-only image replaced by updates. Written against 43.1 (`cat /usr/share/batocera/batocera.version`). ## Setup - `ssh root@BOX`. Commands in this skill run on the box. Anything with quotes (a `sed` through `es-offline.sh`) goes as a script, `ssh root@BOX sh -s <<'EOF'` … `EOF`, not nested in one ssh argument. The box's grep is `/bin/grep`; `/usr/bin/grep` does not exist. - Copy the scripts once, and again when the skill updates: `scp <this skill's directory>/scripts/* root@BOX:/userdata/system/bin/`. They are not in `PATH`: call them as `/userdata/system/bin/<name>`. They need only what stock Batocera ships (python3-evdev, grim, wlrctl, bluetoothctl). Each script's usage is its opening comment: `head -20` it before the first run. ## Quick reference | To | Run on the box | |---|---| | know whether a game runs | `es.sh running` (exit 0 = yes, game JSON; 1 = no) | | launch a ROM as if picked in ES | `es.sh launch /userdata/roms/snes/Foo.sfc` | | stop the game | `es.sh stop` | | wait until the players are done | `es.sh wait-idle 30` | | see the TV | `shot.sh /tmp/s.png`, then `scp` it back and look | | press keys in ES | `es-keys.sh map`, then `es-keys.sh KEY_DOWN KEY_ESC` (keys