Fleet Releases

Fleet releases are how managed HOS deployments can receive approved device definitions, integration packages, firmware-supported capabilities, or project updates depending on the product release.

Release flow

1. A release is prepared for the target device group or site.
2. The Fleet server makes the release available to the licensed Haptique OS controller.
3. Haptique OS receives the release through the supported deployment path.
4. New HOS devices or capabilities become available in the project.
5. The installer exposes them as logical devices.
6. The devices are assigned to Spaces, scenes, favorites, mobile apps, RS90, and AI permissions.

RS90 behavior

RS90 reacts to the Haptique OS project after the controller receives and applies the release. The remote should not need a separate copy of integration logic. It receives the relevant rooms, favorites, scenes, media zones, and button mappings from Haptique OS.

When a button is pressed, RS90 sends the action to Haptique OS. Haptique OS runs the integration, updates state, and the result appears across mobile apps, desktop, RS90, and other connected clients.

Acceptance checks

• The Haptique OS controller shows the expected release.
• New HOS devices appear in the Configurator.
• Logical devices have user-facing names.
• Spaces and scenes use those logical devices.
• RS90 and mobile apps show the updated controls.
• AI commands only operate approved devices and Spaces.