Skip to content

Changelog

Internal — engineering view

Shows the engineering state of work in progress for URG and its integration partners. It is not a customer document.

In development — app languages and font (November 2026)

Not yet released; the app version follows after review.

Changed

  • Robotics Group App: every screen in the six standard languages German, English, French, Spanish, Italian and Dutch (before: French, Spanish and Italian only partly, Dutch not selectable). French, Spanish, Italian and Dutch are machine translated so far and are released only after review by native speakers. See Mobile App › Languages.
  • Terms (decision of 05.11.2026): the app's red button is called STOP in every language. It sends estop and is not a safety function; the safety layer is the emergency stop on the robot. Italian uses uMe without an article. Spanish: Detener, Pausar, Cancelar.
  • Montserrat is part of the app and no longer downloaded at runtime, so tablets without internet access show the same font.

v0.1.0 — Gateway & Robotics Group App (July 2026)

First documented release of the uMe SDK around the uMe Gateway and the Robotics Group App.

Added

  • uMe Gateway — WebSocket/JSON service on the robot's Perception Board (ws://<robot-ip>:8765/ws) wrapping the uMe on-board SDK.
  • Command set: move, head, mode, action, estop, persona.
  • Status stream: battery, mode, warning, broadcast once per second.
  • Robotics Group App (Flutter, iOS/Android): Home, Connect (Connect via IP), Control (FPV with joysticks, mode buttons, STOP, battery, warnings), and Persona & Context editor.
  • Modes DAMP / PREP / WALK with slide-to-confirm, gated locomotion, and the STOP button (estop; no safety function — the emergency stop is the hardware button on the robot).
  • Localization in 7 languages (DE, EN, AR, FR, ES, IT, PT).
  • Deployment helpers: deploy.ps1, ume-gateway.service (systemd), test_client.py.
  • Documentation rebuilt around the actual Gateway API and app.

Known limitations

  • Gateway ships in mock mode: commands are validated and logged and status is streamed, but the robot-side on-board SDK motion calls are still being enabled.
  • Bluetooth Wi-Fi provisioning and Direct Mode (robot hotspot) are stubbed — use Connect via IP.
  • Group Control (fleet) is not yet implemented. The camera image is streamed as JPEG frames; a higher-quality transport (WebRTC/RTSP) is planned.
  • No authentication on the Gateway — LAN-only by design.

See the Roadmap for what's next.