hardware: new robots connect through OpenVibe.Bot and the Node (#1)

OP OpenVibers committed 11 Oct 2026 · 687bb82143 · 1 file, +7 −0

A robot builder (the Generic LOOI driver's authors) asked whether to build on Live's stream-key hardware socket. They read it here as the way to connect a robot. The control-socket tab of the API docs now says first that new robots use OpenVibe.Bot and the OpenVibe Node:

- a one-time pairing code, not a stream key;
- a driver plugin;
- a profile-built panel with roles, a queue, limits and a latched e-stop;
- the robot's panel under the stream once it is bound on the dashboard.

The socket keeps working for existing setups until they have moved (plan T15 deletes it after that). OpenVibe.Extensions' hardware guide says the same. Docs only.

Changes

ddiff --git a/hardware/README.md b/hardware/README.md
iindex d1e81ad..e923b0f 100644
---- a/hardware/README.md
++++ b/hardware/README.md
@@@ -2,6 +2,13 @@
  
  Scripts for streaming from and controlling hardware devices (Raspberry Pi, single-board computers, etc.) with OpenVibe.Live.
  
++> **Connecting a new robot? Use [OpenVibe.Bot](https://openvibe.bot) and the [OpenVibe Node](https://github.com/OpenVibers/OpenVibe.Node).**
++> The Node pairs with a one-time code (no stream key) and runs your driver as a plugin
++> ([write a driver](https://openvibe.bot/docs/drivers)); Bot gives the robot a panel built from its profile, roles, a
++> queue, limits and a latched e-stop, and a Live channel can show that panel under its stream. The controller here
++> uses Live's stream-key hardware socket, which keeps working for existing setups and is retired once they have moved
++> to Bot.
++
  ## Requirements
  
  - **Python 3.7+**