LiftAuth Integration Flow
What this is: A reference flow showing how a mobile robot can integrate with LiftAuth to ride an elevator. Use it as a checklist while adapting the SDK or your own control stack—swap in your robot-specific navigation, networking, and error handling.
What Does This Integration Enable?
LiftAuth exposes a mission-driven workflow that allows a mobile robot to request, enter, ride, and exit an elevator without human assistance. A typical deployment orchestrates the following lifecycle:
- Acquire the elevator – authenticate, connect over the building network, and fetch current car state.
- Summon and secure entry – call the car if needed, monitor floor broadcasts, and command doors open.
- Navigate into the cabin – validate localization and drive to the cabin waypoint within defined tolerances.
- Transition to cabin control – switch radio networks, establish the cabin WebSocket, and issue the travel command.
- Ride to destination – close doors, monitor floor telemetry, and open doors on arrival.
- Navigate out and clean up – drive to the landing waypoint, close doors, and disconnect from all resources.
Each step should be backed by resilient connection switching, WebSocket command/response exchanges, and robot-navigation primitives based on your platform.
Terminology
WebSockets
- Internet WebSocket - Used when the robot is outside the elevator (connected to building WiFi)
- Cabin WebSocket - Used when the robot is inside the elevator, attached to the cabin controller’s WiFi. Elevator cars behave like Faraday cages, so the cabin controller exposes its own access point; the messaging protocol remains the same on both sockets.