This page is for IT administrators and anyone configuring firewalls, DHCP, or corporate networks for Mesmer robots. For physical connection steps, see Robot connectivity.
Robots expect an IP address via DHCP (default on most routers). You cannot set a static IP on the robot itself, but you can usually bind a fixed address in DHCP using the robot's MAC address (available shortly before delivery if required). If that is not possible, place a router between the robot and your network, give the router a static IP, and let it assign the robot an address via DHCP.
Robots use DHCP (UDP ports 67/68), DNS on UDP port 53, and IPv4.
Validate your site in advance with the Network check tool.
All connections are initiated by the robot as a client to a remote server or via peer-to-peer negotiation through NAT traversal. No port forwards from the external internet-facing address to the robot are required.
The ideal setup is for the robot and a PC running Tritium UI to be on the same LAN. The robot uses its connection to tritiumrobot.cloud to broker a direct encrypted connection over the LAN (a random high port). This is the lowest latency and most reliable option.
If the robot and operator PC are on different networks, a direct connection may be established using NAT traversal (STUN). If that fails, traffic falls back to a TURN proxy — higher latency and less reliable.
Use domain names rather than IP addresses where possible. We do not guarantee IP addresses will not change at short notice. The addresses below were last updated 17 July 2023 and are provided to help during setup.
update.robot-thespian.co.uk (62.3.104.54) on PORT 2022 — Engineered Arts support access and robot software package downloads.tritiumrobot.cloud on PORT 443 — Tritium UI, connection negotiation, and Tritium AI. Geo-located regions:
uk.tritiumrobot.cloud 18.134.18.162 & 13.41.35.109us.tritiumrobot.cloud 44.225.252.52 & 44.229.49.140ap.tritiumrobot.cloud 18.138.14.129 & 18.136.55.137time1.google.com, time2.google.com, time3.google.com, time4.google.com — accurate time for authentication.stun.engineeredarts.co.uk (35.177.202.92) and tritium-prod-stun.earts.dev (13.43.153.64) on PORT 3478 — NAT traversal when the robot is not on the same LAN as the PC running Tritium UI.Engineered Arts support may need the following even if your local connection works without NAT traversal:
turn.engineeredarts.co.uk (35.177.202.92) and tritium-prod-turn.earts.dev (13.43.153.64) on PORT 3478 and 5349 — connection proxying when NAT traversal fails and the robot is not on the same LAN as the PC running Tritium UI.To deliver efficient and timely support, Engineered Arts requires reliable access to the robot. We recommend allowing all ports listed on this page.
Recommended download and upload speeds for conversation, telepresence, and transfers are on Robot connectivity — Recommended internet speed. Use that page as the single reference for figures.
When provisioning or approving WAN capacity, plan for two locations: the robot site (where the robot is installed) and any operator PCs running Tritium UI. Telepresence in particular needs adequate upload and download at both ends.
Also consider link stability and QoS: shared guest Wi‑Fi, strict traffic shaping, or asymmetric upload caps can cause conversation pauses even when headline speeds look sufficient. Prefer wired Ethernet at the robot where possible, and avoid placing the robot on VLANs or paths that block the ports listed above.