Back to engineering work

Connected-device integration

Remote claw-machine control

The machine-control path moves browser commands over MQTT to an ESP32, while the existing Firebase services continue to handle accounts, balances, payments and session records.

Remote claw machine controlControl integration / camera work ongoing
The claw machine used for control integration and testing
The physical machine used for integration and testing. Camera work remains ongoing.

Engineering scope

  • Browser-to-ESP32 commands through MQTT, WebSocket and EMQX
  • Direction, grab and stop handling
  • Stale, duplicate and interrupted-session handling

System flow

The machine-control path

  1. Use the browser controlsPress, hold or release a direction or grab control.
  2. Send the commandMQTT over WebSocket carries the message through EMQX.
  3. Handle it on ESP32Interpret the command and its session state.
  4. Drive or stop the machineApply the movement, grab or stop command.

Control-channel integration

MQTT and WebSocket carry machine commands while Firebase retains accounts, balances, payments and session records. This separates real-time control from the surrounding game services.

Command and session handling

The firmware distinguishes a quick press, a held button and a release. It includes release-to-stop logic, stale and duplicate command checks, and watchdog handling for interrupted sessions.

Physical-machine testing

Documented checks cover press, hold, release and interrupted sessions on the machine. Camera integration remains in progress; no measured latency result is available.

All projectsArchive record

Project enquiries

Discuss your project.

Tell us what you’re developing and where you need engineering support.

Discuss your project