AutobotWhat is Z Autobot?
Z Autobot brings connected robot control, accounts and firmware updates into one workspace. Z2 is the first model; the platform is designed to accommodate more models over time.
Z Autobot / answers
A little clarity before the next connection.
Get to know Z2, from setup to local safety.
The platform, the first model, and what is ready today.
Z Autobot brings connected robot control, accounts and firmware updates into one workspace. Z2 is the first model; the platform is designed to accommodate more models over time.
Z2 brings live camera viewing, recorded voice messages, text on its display, manual control and auto driving into one workspace. Onboard obstacle and floor checks support movement; local diagnostics and Wi-Fi firmware updates help keep it ready.
Use live view to see through the camera and pan or tilt to look around. Record a short voice message in the workspace for Z2 to play through its speaker, or type a message for its display. Photos and video recordings save to your device.
Listening brings sound from the room around Z2 to your workspace through its microphone. Speaking sends your voice in the other direction, to the robot’s speaker. These describe audio between you and the room; they do not mean the robot understands or answers a conversation.
From the first power-on to a connected workspace.
Power on the robot and follow its Wi-Fi setup instructions. Connect it to your Wi-Fi, open Pairing on its local page, then enter the robot ID and six-digit pairing code in the workspace. You can also scan its pairing QR.
Open Pairing on the robot’s local page. The code is valid for five minutes. If it expires, generate a fresh code there. Keep the code private: it links the robot to your account.
The ESP32-S3 controller handles movement, local safety, sensors and outputs. A separate ESP32-CAM board carries the camera and positioning hardware. The workspace presents them as one robot, while firmware and connectivity remain independent.
Use the local-page link in the robot workspace while connected to the same Wi-Fi as the robot. That page provides detailed sensor and hardware information directly from the device.
What happens close to the motors.
The controller reads distance and floor sensors, evaluates the nearby space, and adjusts its route and clearance decisions onboard. It can pause or choose another direction when the path changes. Illustrations on this website explain the idea; they are not live sensor data.
Obstacle and floor checks run on the controller. The cloud sends commands and shows operating state; local firmware handles the immediate movement and safety decisions. Keep the robot supervised and use it in a suitable environment.
A nearby obstacle, a missing-floor reading, or a hardware readiness check can prevent movement in that direction. Inspect the surroundings and the local diagnostics before trying again. Sensors do not guarantee detection of every surface or object.
No. A manual obstacle stop requires a fresh movement command. Adaptive roaming follows its own onboard recovery and waiting logic while that mode is enabled.
Accounts, status and keeping firmware current.
Connected control is restricted to the account that owns the robot. Pairing establishes that association. Shared robot access is not currently offered.
No. Detailed readings and local device logs stay on the local diagnostics page. The cloud workspace receives compact operating status and viewing updates while it is open.
The workspace marks the connection offline. Current readings and controls should no longer be treated as available. Check power and Wi-Fi, and use the local page if the device remains reachable on your network.
The workspace shows firmware information for each board. Available releases can be installed over Wi-Fi using the firmware controls. Keep the robot powered and connected during an update.
Email contact@zautobot.com with the account request. Signing out ends the browser session; it does not delete the account. The privacy policy explains what information is used.