Troubleshooting¶
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.
The app can't connect¶
Symptom: "Connection failed" when using Connect via IP.
- Same network? The robot and your device must be on the same network.
- Right IP? Use the robot's Perception Board IP — the one you noted at commissioning.
- Gateway running?
Expected:
ssh <SERVICE-USER>@<ROBOT-IP> "systemctl --user status ume-gateway.service"active (running). If not:systemctl --user restart ume-gateway.service. - Port reachable? Test with a WebSocket client from a PC (see Python Client).
Connected, but no status¶
The connection opens but no battery/mode appears: the Gateway is reachable but
not broadcasting. Restart it (systemctl --user restart ume-gateway.service)
and check journalctl --user -u ume-gateway -f.
Robot doesn't move¶
- Are you in WALK? Locomotion only runs in WALK; the joysticks are hidden otherwise.
- Is the Gateway running in mock mode? Then movement is only logged by
design — the service should run with
--real, see Gateway Deployment. - Was the installer run from a normal login shell? Otherwise the service lacks the DDS/ROS environment and the motors do not respond.
Camera image is black¶
- Is the depth camera connected and not claimed by another process?
- Is the camera mode set (
UME_CAMERA=<depth camera mode>orUME_CAMERA_TOPIC=…)? The value and the service account are available from support@unitedrobotics.group. - The log shows the reason at startup —
journalctl --user -u ume-gateway -f. No camera mode set:[gateway] Kamera: kein UME_CAMERA / UME_CAMERA_TOPIC -> kein Livebild. Camera claimed by another process or switched off: a line containingStart fehlgeschlagen (belegt/aus?).
An action is refused¶
The Gateway answers with a reason (action_result), for example that a robot
variant cannot perform a dance, or that Get Up only applies to a robot that
is lying down. Whole-body dances require a stable stance first — the Gateway
handles that transition itself.
Wi-Fi provisioning fails¶
Bluetooth provisioning and Direct Mode are still being completed — use Connect via IP in the meantime.
Connection drops during use¶
The app shows a connection-lost state and stops sending commands. Reconnect via Connect via IP. If it recurs, check the Wi-Fi signal and the robot's network connection.