kuando Busylight Developer Guide
Yes, you can build software for kuando Busylight. The easiest verified path is kuandoHUB's local HTTP API, which can be called from JavaScript, Node.js, Python, PowerShell, or any language that can send HTTP requests.
This guide is based on Plenom's current development page updated on March 2, 2026, the public kuandoHUB page updated on May 20, 2026, and the public kuandoHUB Manual v0.9.19 PDF. Public documentation clearly covers the HTTP API. Other SDK options such as the Busylight UC SDK, USB API, JavaScript SDK, Browser Extension SDK, and Chromium WebHID SDK are currently offered through Plenom's developer access flow rather than through openly published docs.
1. Short answer​
You can develop for Busylight in at least three practical ways:
| Path | Best for | Publicly documented today | Languages |
|---|---|---|---|
| kuandoHUB HTTP API | Fast automation, local scripts, dashboards, app integration | Yes | JavaScript, Node.js, Python, PowerShell, Go, PHP, anything with HTTP |
| Busylight SDK / USB API | Native integrations and low-level hardware control | Offered by Plenom, but access is gated | C++, C#, VB, other native stacks depending on the package |
| JavaScript SDK / Chromium WebHID | Browser-native or web-app integrations | Offered by Plenom, but public docs are not openly posted | JavaScript / TypeScript |
If your goal is "switch the light from a script or app," start with the HTTP API.
2. What kuandoHUB gives you​
Plenom describes kuandoHUB as multi-platform Busylight software for Windows and macOS with:
- manual color and sound control,
- timer support,
- priority rules,
- Outlook and UC integrations,
- hotkeys,
- an HTTP and API interface for your own software.
The public manual documents a local HTTP server, enabled from Advanced Settings, that listens by default on http://localhost:8989/.
3. What you can build​
Good fits:
- focus-mode toggles,
- CI/CD status lights,
- incident-response lights,
- internal dashboards,
- monitoring alerts,
- call-center and support-desk state signals,
- room occupancy or desk presence indicators,
- local webhook receivers that translate events into light changes.
4. What this guide covers​
| Goal | Start here | Why |
|---|---|---|
| Decide which integration path to use | Architecture and SDK Map | Separates HTTP, USB, SDK, and WebHID options |
| Switch the light quickly | HTTP API Guide | Covers the verified public API |
| Use JavaScript or Node.js | JavaScript and Node.js | Browser fetch, Node fetch, helper patterns |
| Use Python | Python Automation | requests, local tools, daemon patterns |
| Evaluate deeper integration paths | Advanced Integration Paths | Vendor SDK, USB API, JS SDK, Browser Extension SDK, WebHID |
| Avoid common mistakes | Troubleshooting and Security | HTTP enablement, priorities, tokens, local-only assumptions |
5. Two important limits​
-
kuandoHUBis the documented public control surface. Without kuandoHUB or vendor SDK access, the easiest official public integration surface is not available. -
The public docs are strongest for the HTTP API, not for low-level USB development. Plenom currently advertises richer developer tool bundles, but those are requested through their development form instead of being fully published as open docs.