Build with Valence#
These pages cover clients, plugins, hub firmware, the command-line tools and local testing.
| Page | Contents |
|---|---|
| Quickstart | A connected client in about 20 lines |
| JavaScript · C# · C++ · Python | A working client in your language |
| Plugin guide | An app integration, with a shipped plugin as the worked example |
| Hub implementer guide | Your own firmware answering as a conforming hub |
| CLI guide | The command-line tooling, including motion-versus-planner graphing |
| Local testing | A simulator, a probe, the fuzz harnesses, and the regression patterns |
Before you start#
Read How it works. A client keeps no optimistic local state and renders what the hub reports.
Keep the Dictionary open. It defines each term used on this site.
Shadow and echo#
Your shadow updates only from hub frames, not from your own requests.
You send an intent, the hub clamps it, and the echo reports the applied value. Render the echo value. On a moving machine, rendering the request instead of the echo is a safety defect.