User Guide on EdS

Running the Vertical

Mon, 01 Jan 0001 00:00:00 +0000

Running the Vertical

The whole chain on one machine, with no deevnet infrastructure.

1. Start the palette extractor

cd services/palette
make venv
make serve PORT=8731

2. Start a broker and lightd

cd services/lightd
make broker # mosquitto in podman on tcp://127.0.0.1:21883
make run

make run builds lightd and points it at the development broker. It expects palette on :8731.

3. Watch the topic tree

In another terminal:

cd services/lightd
make broker-watch # tail every eds/# topic

4. Send a cover

curl -F image=@jacket.jpg http://localhost:8732/v1/cover

A scene should appear on eds/lightstand/lp-stand-01/scene. Because gamma is applied on the device rather than on the wire, the colors you see here are the colors actually intended.

Provisioning a Stand

Mon, 01 Jan 0001 00:00:00 +0000

Provisioning a Stand

Credentials live in a dedicated creds NVS partition, not in the firmware image. The WiFi key and the broker password have no build-time option at all: NVS is the only place they can come from. A built binary therefore carries no secret and can be cached, copied and shared without care, and sdkconfig cannot hold one.

From the tenant

A stand on Deevnet IoTaaS is flashed with what the EdS tenant issued:

Powering the Strip

Mon, 01 Jan 0001 00:00:00 +0000

Powering the Strip

WS2812-class LEDs draw about 60 mA each at full white, so a long strip at full brightness is an amp-scale load. The ESP32 devkit adds roughly 250 mA with WiFi up and peaks near 500 mA on transmit.

What EdS actually draws

Brightness is applied before the gamma 2.6 table, which means current falls away far faster than the brightness figure suggests. Measured against the firmware’s own lookup table:

EdS on One Pi

Mon, 01 Jan 0001 00:00:00 +0000

EdS on One Pi

Everything EdS needs can be put on one Raspberry Pi on the home network: the broker, the log store, Grafana, the four services and the now-playing agent. Nothing of Deevnet IoTaaS is behind it.

Not yet proven. The image is defined and has not run on a Pi. ADR-0033 is Proposed and lists what would settle it.

stand, screen, beacon ──TLS 8883──▶ ┌ Pi ────────────────────────────────┐
iTunes PC ◀── remote protocol ────▶ │ Mosquitto · log store · Grafana │
a browser ──────── 443 ───────────▶ │ palette · lightd · nowplayd │
turntable ── tape out, sound card ─▶│ console · npagent │
 └────────────────────────────────────┘

It is beside the tenant on Deevnet IoTaaS, not in place of it. Building the image and running the Pi change nothing there, and the stand, the screen and the beacon stay with the tenant until each is provisioned again.