temi V3

Robotemi published SDK version 1.138.0 on June 18, 2026, compatible with the temi 138 Launcher.

The release adds Navigation Zone support, letting developer apps get temi’s current zone and the full list of defined zones, and listen for zone entrance and exit events. Zone profiles are not applied automatically when goto is called directly from the SDK; the SDK can apply a zone profile explicitly whenever the robot is moving to a location.

The release adds tiltAngle() to tilt temi’s head while it travels to a location, fixes a bug where SpeedLevel.VERY_SLOW was not respected in goto and gotoPosition, and adds es-CO, es-Ar, and ur-PK for text-to-speech, with ur-PK also added for speech-to-text.

The release adds getOrganizationInfo() to retrieve organization data, lets apps clear LLM conversation history with a new session flag, and fixes a bug that sent duplicate SPEAKING and IDLE conversation-status events.

Robotemi published SDK version 1.137.1 on February 9, 2026, compatible with the temi 137 Launcher, minimum version 19232. The update follows version 1.136.0 from July 2025, the release that ended a multi-month gap in public SDK activity.

The release adds getFloorAndMapData to retrieve floor and map data by floor ID, addNewFloor to create new floors, and renameFloor to rename existing ones. New parameters on upsertMapLayer and deleteMapLayer add multi-floor support to map-layer editing, letting a single map record span more than one building level.

renameLocation and renameLocationOnFloor let developers rename and reposition saved locations, and deleteLocationOnFloor removes a location from a specific floor, giving per-floor control the SDK did not previously expose to third-party apps.

The release also adds a showDrawer parameter to setVolume and a saveHomeBaseIfCharging parameter to resetMap, and carries forward the VERY_SLOW and VERY_HIGH speed presets introduced in the prior release, restricted to goto-based movement.

Robotemi published SDK version 1.136.0 on July 2, 2025, compatible with the temi 136 Launcher. The release is the first public SDK update logged on GitHub since version 1.135.1 in November 2024.

The release adds an OnMapStatusChangedListener that reports whether temi’s navigation map is lost or locked, and an OnMapNameChangedListener that reports when the active map name changes. New getMapElements and getMapImage methods give developers more efficient access to map data than the existing getMapData call.

SpeedLevel, a parameter of goTo and goToPosition, can now be customized across a 0.1 to 1.5 meters-per-second range, with new VERY_SLOW (0.3 m/s) and VERY_HIGH (1.2 m/s) presets added to the existing options.

The update also revises button-status callbacks, adding OnButtonModeChangedListener to report whether hardware buttons are enabled or disabled, and fixes a Content Provider crash that could occur while the Face app was closing.

Hospital deployments operated temi V3 on enterprise 5 GHz Wi-Fi networks with dedicated VLAN segmentation for robot traffic. Facility IT teams documented latency thresholds: connections above 80ms produced perceptible video lag during physician-patient interactions.

Multi-unit hospital deployments used temi’s fleet management software to assign robots to specific wards and schedule patrol routes during off-peak hours. No firmware version was publicly disclosed in facility case studies.

Physicians accessed the temi app from desktop or mobile to pilot robots to patient rooms. Onboard screen displayed two-way video; speakers and microphone handled audio. Physical examination or intervention required in-person follow-up; the robot served as a first-contact triage presence tool only.

Elevator integration required facility-side API configuration. Rooms with narrow doorways (below 70 cm clearance) were inaccessible. Battery runtime of approximately 8 hours supported a full clinical shift with recharging between rounds.