Package: ros-humble-fleetless-bridge Version: 6.2.3-0jammy Architecture: all Maintainer: Andre Dehne Installed-Size: 860 Depends: python3, ros-humble-rclpy, ros-humble-rosidl-runtime-py, ros-humble-cv-bridge, ros-humble-sensor-msgs, python3-opencv, python3-defusedxml, python3-numpy, python3-aiohttp, python3-aiortc Homepage: https://docs.fleetless.dev Priority: optional Section: misc Filename: pool/main/r/ros-humble-fleetless-bridge/ros-humble-fleetless-bridge_6.2.3-0jammy_all.deb Size: 217630 SHA256: 2ef1b362d2f7f7e5ae445db93dcb725bc82a3f0c7d686f826f553b2abbdefb41 SHA1: 8b6f26bdadbcc8cc1dee066998ad7a19f9ebf7e3 MD5sum: 77e8fb1223cd0d4586515657d8e3ca9a Description: Fleetless Bridge: connects a ROS 2 robot to the Fleetless cloud. Not a safety function — read the safety notice: https://docs.fleetless.dev/#safety-notice Version 1.0 — Effective from 1 November 2026 . Fleetless is not a safety function. It is not a safety component, a safety-rated controller or an emergency-stop system, and it does not replace the risk assessment of your robot and its surroundings. . - Commands sent through Fleetless can be delayed, lost or executed out of order, for example when a network connection drops. - Every robot must reach, on its own, the safe state defined in its risk assessment when the connection to Fleetless is lost or the bridge stops working. Depending on the robot, stopping at once is not always the safe state. - The failsafe message of a bridge publisher is an operating aid, not a safety function. It is sent by the bridge process and cannot be sent if that process or the robot's computer fails. - Keep a physical emergency stop within reach whenever a robot can move. - AI agents that control robots through Fleetless can make mistakes. Use an AI agent to move a robot only while a person supervises every motion and can stop the robot at once. Do not let AI agents move robots unattended. Where Fleetless allows it, for example through the roles of an app, limit what an AI agent may do. . Commands may also be executed more than once, and displayed status may be stale. Safety functions, including the response to communication loss, must be implemented independently of Fleetless and validated for the specific robot and its hazards. Human supervision and an emergency stop do not replace the required protective measures. Nothing in this notice excludes our liability under mandatory law. . You are responsible for the safe integration and operation of your robots, as described in section 8 of our [Terms of Service](https://fleetless.dev/terms). . https://docs.fleetless.dev/#safety-notice . Runs on a robot alongside its ROS2 graph, exposes configured datapoints, cameras and remote invocations to the Fleetless cloud, and carries the robot's job and asset-sync traffic. See https://docs.fleetless.dev. . Every dependency above is an ordinary apt package. `apt install` needs nothing beyond what this Depends: line already asks for, and installing it needs no network access beyond whatever the package's own mirror requires — it does not reach PyPI, and no maintainer script installs anything at configure time (see debian/postinst, which does nothing). This package used to run a PyPI install for three dependencies apt could not resolve; the last of those (python3-aiortc, replacing the LiveKit SDK) is why it no longer needs to.