- Changes
- 4
- Tracking since
- Mar 2024
- Latest
- Jun 18, 2026
- Net movement
- Classification stable
- 2026
-
temi SDK v1.138.0 adds navigation zone tracking for developers
Robotemi released SDK version 1.138.0 on June 18, 2026, introducing navigation zones that let developer apps detect when temi enters or exits a defined area and apply zone-specific behavior profiles.
Full assessment3 claims · 4 technical notes · 2 sources
Where it standsAutonomy LadderIIIIIIIVVLevel IIAssisted AutonomyHuman ReadinessReady NowNew to MarketWaitKnown IssuesRobovations Score04055708565CapableWhat happenedThe release also added head-tilt movement during navigation and expanded speech support to three additional languages. How quickly deployed temi V3 units adopt zone-based behavior in hospitals and hotels remains to be documented.
Bottom lineThe release gives developers granular zone-based control, but robotemi's own release notes flag that zone behavior requires explicit application rather than working automatically.
ImpactOn autonomy
- Navigation zones let apps query current zone and listen for entrance and exit events.
- Zone-specific behavior profiles can now apply automatically during autonomous goto navigation.
On readiness
- Enterprise deployments gain a documented way to restrict or customize behavior by area.
- Head-tilt control and three added languages round out this release's other changes.
Claim check3 maker claims checked against the record. Open one to read the finding.
Release notes present navigation zones as comprehensive zone management for developers
Documented findingRobotemi's own notes state zone profiles are not automatically applied when goto is called directly from the SDK; developers must apply them explicitlyHead-tilt during movement is listed as a new navigation capability
Documented findingThe feature only tilts the head's viewing angle; it does not change temi's path planning or obstacle avoidanceThree new speech languages are framed as expanded global reach
Documented findingThe languages apply to text-to-speech and speech-to-text functions only; robotemi has not disclosed how many deployed units use themEvidence2 sources · all linked
Technical notes4 sectionsRelease Details
Robotemi published SDK version 1.138.0 on June 18, 2026, compatible with the temi 138 Launcher.
Navigation Zones
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.
Movement and Speech
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.
Other Changes
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.
-
temi SDK v1.137.1 adds multi-floor map management for developers
Robotemi released SDK version 1.137.1 on February 9, 2026, adding floor-management methods including addNewFloor, renameFloor, and per-floor location controls.
Full assessment3 claims · 4 technical notes · 2 sources
Where it standsAutonomy LadderIIIIIIIVVLevel IIAssisted AutonomyHuman ReadinessReady NowNew to MarketWaitKnown IssuesRobovations Score04055708565CapableWhat happenedThe update gives third-party developers direct API access to multi-floor deployments, a capability not previously exposed in the public SDK. It remains to be seen how quickly existing temi V3 installations in hospitals and hotels adopt the new floor APIs.
Bottom lineThe release adds real developer tools for multi-floor deployments; documented adoption across temi's hospital and hotel installations is not available.
ImpactOn autonomy
- New floor-management API lets developers add, rename, and delete floors on temi's map.
- Per-floor location renaming and repositioning now exposed for multi-story navigation control.
On readiness
- Developers building multi-floor deployments gain API tools not previously available.
- No documented change to end-user setup or default temi V3 operation.
Claim check3 maker claims checked against the record. Open one to read the finding.
SDK release notes present multi-floor support as a new capability for enterprise deployments
Documented findingThe methods manage map data and floor records; they do not address how a single temi unit moves between floors, since the API does not control elevators or stairsFloor and location renaming tools are described as improving deployment organization
Documented findingRobotemi's release notes do not disclose which hospitals, hotels, or other sites, if any, have adopted the new floor APIsSpeed level additions are framed as expanded motion control
Documented findingThese values apply only to goto-based movement, not to all navigation modesEvidence2 sources · all linked
Technical notes4 sectionsRelease Details
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.
Floor Management
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.
Location Management
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.
Other Changes
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.
- 2025
-
temi robot SDK update adds map status and speed controls
Robotemi shipped SDK version 1.136.0 on July 2, 2025, the first public release after a gap of several months.
Full assessment3 claims · 4 technical notes · 2 sources
Where it standsAutonomy LadderIIIIIIIVVLevel IIAssisted AutonomyHuman ReadinessReady NowNew to MarketWaitKnown IssuesRobovations Score04055708565CapableWhat happenedThe update lets developer apps detect when temi's map becomes lost or locked and adds finer control over movement speed during autonomous navigation. Whether the update signals a return to a regular release cadence is worth tracking in subsequent SDK activity.
Bottom lineThe release restored public SDK activity but only after a multi-month gap that briefly left temi's third-party developer ecosystem without a new capability release.
ImpactOn autonomy
- Map-lost and map-locked event listeners let apps detect localization failures in real time.
- Goto speed now customizable from 0.1 to 1.5 meters per second, up from fixed presets.
On readiness
- Developers can now build apps that respond automatically to a lost or locked map.
- No change to setup steps or default consumer-facing navigation behavior in this release.
Claim check3 maker claims checked against the record. Open one to read the finding.
Robotemi's public SDK repository markets temi as an actively maintained open developer platform
Documented findingGitHub release history shows no published SDK version between November 2024 and July 2025, a gap of more than seven monthsRelease notes describe the update as adding map status monitoring for developers
Documented findingThe feature only signals that a map is lost or locked; it does not diagnose the cause or restore localization automaticallySDK documentation presents the new speed range as added flexibility for app developers
Documented findingThe custom range applies only to goTo and goToPosition calls, not to other movement modesEvidence2 sources · all linked
Technical notes4 sectionsRelease Details
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.
Map Status Monitoring
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.
Speed Controls
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.
Other Changes
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.
- 2024
-
temi V3 gains traction in hospital telepresence deployments
Multiple healthcare operators published case studies and deployment reports documenting temi V3 use in hospital wards and outpatient clinics for remote physician-patient interaction.
Full assessment4 claims · 4 technical notes · 2 sources
Where it standsAutonomy LadderIIIIIIIVVLevel IIAssisted AutonomyHuman ReadinessReady NowNew to MarketWaitKnown IssuesRobovations Score04055708565CapableWhat happenedThe platform's teleop model proved compatible with clinical workflows where an attending physician pilots the robot to bedsides from a remote station.
WatchingWhether sustained healthcare deployment translates into formal medical-device integration or regulatory engagement.
Bottom lineHealthcare adoption is real and documented, but the platform functions as a remote-presence tool operated by clinical staff, not an autonomous clinical assistant.
ImpactOn autonomy
- Patrol-route autonomy confirmed functional in corridor environments with patient foot traffic
- No documented change to autonomous capability; Level II classification unchanged
- Operator-piloted bedside interactions validated across multi-ward floor plans
On readiness
- Healthcare vertical deployment adds a documented commercial use case beyond corporate campuses
- Clinical operator training requirements documented by facility case studies
- Enterprise Wi-Fi dependency flagged by hospital IT teams as primary friction point
Claim check4 maker claims checked against the record. Open one to read the finding.
Autonomous navigation enables hands-free clinical rounds
Documented findingHospital case studies confirm physician operator required for all patient-destination navigation; patrol routes handle corridor transit onlySeamless deployment in any healthcare environment
Documented findingFacility reports cite enterprise Wi-Fi upgrades as a prerequisite; standard hospital Wi-Fi caused latency failures during video callsReduces physical presence requirements for clinical staff
Documented findingRemote check-in validated for routine status visits; hands-on procedures and physical examination remain outside the platform's scopeReady for immediate clinical deployment
Documented findingOperator training and IT integration add lead time; case studies cite 4-8 week onboarding before operational useEvidence2 sources · 1 linked
12Feb 2024Mar 2024filed 15 Mar 2024- 1temi Press Release / Healthcare Case Studies20 Feb 2024
- 2Healthcare IT News8 Mar 2024named, not linked
Technical notes4 sections
Deployment Architecture
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.
Fleet Management
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.
Operator Workflow
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.
Known Limitations in Clinical Context
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.