Dimmer 0-10V — API
Overview
The 8‑Channel 0‑10V Dimmer Board (MS-A008) has 8 analog (0‑10V) outputs and 8 digital inputs. It shares its web interface and Integrations/Ports firmware with the Dimmer TRIAC board (MS-D006) — same TCP protocol family, same port 502 default — but the vendor API document available for this specific model is much shorter than the one for the TRIAC board, and only confirms the TCP feedback (read) string.
Everything on this page marked “To be confirmed” is an inference by analogy with the Dimmer TRIAC's documented API (§2), not an independently verified fact for the MS‑A008. Confirm against a live unit — or ask MolSmart for the equivalent 0‑10V API document — before relying on it in production.
Feedback String (confirmed)
Open a plain TCP connection (default port 502). The module reports its 8 output levels and 8 input states as a colon‑separated string, matching the shape of the other MolSmart boards:
000000000000000000000000:11111111:8:00000000:00000000
035000000000000000000000:11111111:8:10000000:00000000
| Block | Meaning |
|---|---|
| First block | Status of each of the 8 output (AO) channels — 3 digits per channel, 000–100 (%). |
| Second block | The 8 pushbutton/digital inputs on the module, one digit each. |
The source document only describes these two example strings and the channel/digit layout — it does not spell out the trailing :8:…:… fields individually. By direct analogy with the Dimmer TRIAC's confirmed format (§2.2 — d_mask/i_mask after the channel count), the same layout is expected here, scaled to 8 channels.
Control Commands (unconfirmed)
Not covered by the vendor document reviewed for this model. Given this board shares the same MolSmart String(NO)/(NC) TCP protocol and port‑502 default as the Dimmer TRIAC (per Integrations/Ports on both products' web interface), the same command syntax is expected to apply here, 1:1, just addressing 8 channels instead of 6:
See Dimmer TRIAC — TCP Control & Feedback for the confirmed version of this syntax on the sibling product. Verify each of these forms against a live MS‑A008 unit before shipping an integration built on them.
Expected Endpoints
Not covered by the vendor document reviewed for this model. By analogy with the Dimmer TRIAC (§2.3–2.4), the following are plausible but unconfirmed for the MS‑A008:
| Channel | Expected shape (by analogy — not confirmed) |
|---|---|
| MQTT state topics | /molsmart/<device><serial>/in/ao1 … /in/ao8, values ON/OFF/%0-%100 |
| MQTT control topic | /molsmart/<device><serial>/in/control, same JSON shape as the Dimmer TRIAC's control topic |
| HTTP set | POST /api/v2/dimmer_set.cgi, same JSON body shape (idx up to 8) |
| HTTP status | GET /api/v2/dimmer.cgi |
Notes & Open Items
| Open item | Detail |
|---|---|
| Control command syntax | Not documented for this model; inferred from the Dimmer TRIAC (§3.3). Confirm on a live unit. |
| HTTP JSON API | Not documented for this model; inferred from the Dimmer TRIAC (§3.4). |
| MQTT topics | Not documented for this model; inferred from the Dimmer TRIAC (§3.4). |
| d_mask / i_mask fields | Present in the feedback string by analogy with the TRIAC board's confirmed format, not individually explained in the source for this model. |
This product's User Manual documents the shared Integrations/Ports configuration page (ports, MQTT broker, TCP protocol selector) in full — see it for everything not covered here.