Gateway Deployment¶
How to get the uMe Gateway running on a robot and keep it running. For the binding end-to-end procedure (commissioning, versioning, vendor updates) see Deployment Process — this page is the technical reference for the same steps.
For IT, technicians and integration partners
Technical reference for IT departments, URG technicians and trained partners. It is not written as operating instructions for end users.
| Board | Perception Board (runs the camera and the conversational agent) |
| SSH user | <SERVICE-USER> — the service account of the Perception Board; its name is not published on this site |
| Python | 3.10+ |
| Gateway port | 8765 (WebSocket) |
| Files | gateway_v2.py, install.sh (repo robotics-group-app, folder gateway/) |
| Service | ume-gateway.service (user-level systemd, autostart on boot) |
Gateway installation guide 2.3 — name in the Wi-Fi and pairing (in development, 31.10.2026)
From version 2.3 of the installation guide, copy both files into the subfolder
~/ume-gateway-neu/ (not into ~/) and run bash ~/ume-gateway-neu/install.sh; only then is
the running version kept as ~/gateway_v2.py.vorher for the rollback. install.sh also asks
for the ID of the uMe, creates the pairing key once and announces the service _ume-gw._tcp;
the robot keeps its previous name in the Wi-Fi. The app finds the uMe without an address.
Steps 1 and 2 below still show the procedure before version 2.0. Order (tablets first),
pairing, rollback:
Technician manual — uMe connection and pairing.
Step 1 — copy the files¶
scp gateway_v2.py install.sh <SERVICE-USER>@<ROBOT-IP>:~/
Step 2 — install¶
ssh <SERVICE-USER>@<ROBOT-IP>
bash ~/install.sh
The installer copies the Gateway, creates the autostart service with the
DDS/ROS environment of the current shell, enables it, and prints the status —
which must read active (running).
Use a normal login shell
The service inherits the DDS/ROS environment variables from the shell the installer runs in. In a stripped-down shell the motors will not respond.
Step 3 — verify¶
Open the Robotics Group App and connect to <ROBOT-IP>. Live camera image,
status, and control must work immediately. Alternatively test from a PC with a
WebSocket client (see Python Client).
Modes¶
| Start | Meaning |
|---|---|
python3 gateway_v2.py --mock |
Nothing moves; commands are only logged. For app/CI development. |
python3 gateway_v2.py --real |
Real control. This is what the service runs. |
Optional camera settings via environment variables: UME_CAMERA=<depth camera mode>
(direct capture from the depth camera; the value is not published on this site) or
UME_CAMERA_TOPIC=<topic>. The value and the service account are available from
support@unitedrobotics.group.
Operations¶
- Logs:
journalctl --user -u ume-gateway -f - Restart:
systemctl --user restart ume-gateway.service - New version: copy
gateway_v2.pyover, thenbash ~/install.shagain - Autostart without login is enabled by the installer via
enable-linger
Security¶
- Change the default password on the board after commissioning (
passwd). - Prefer an SSH key over a password.
- Port
8765is LAN-only — never expose it to the internet.