2026 on EdS

CHG-0001: The LP Stand Joins Its Tenant

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

CHG-0001: The LP Stand Joins Its Tenant


Date	2026-10-10
Change type	Deployment
Status	Complete 2026-10-10
Systems	`lp-stand-01` (ESP32-D0WD-V3); the `eds` tenant’s Grafana organization
How	`make build flash provision` in `firmware/lp-stand`; `terraform apply` in `infra/deevnet-tenant-eds`
Risk	Low. Nothing issued is replaced. Most likely to go wrong: a broker account missing a topic the firmware uses, which fails silently
Decisions	ADR-0004, ADR-0005
Related	None
Backfilled	Written after the change ran, from the session that ran it.

Summary

The stand had been flashed once, on 2026-09-09, built for plaintext MQTT on port 1883 and never provisioned. Deevnet IoTaaS’s broker is TLS only, so it had never reached the real broker; it sat lit in its default warm white, retrying WiFi with no key.

CHG-0002: The Relay Pi, and Accounts for Now Playing

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

CHG-0002: The Relay Pi, and Accounts for Now Playing


Date	2026-10-10
Change type	Deployment
Status	Complete 2026-10-10
Systems	the `eds` tenant’s broker accounts; `dv02rpi002p01` (a Pi lab host in the site inventory); iTunes on a PC on the home LAN
How	`terraform apply` in `infra/deevnet-tenant-eds`; `make -C deploy/relay image fetch card status pair`
Risk	Medium. A host is put on two networks the site otherwise keeps apart. Most likely to go wrong: the Pi’s Wi-Fi leg picking up a default route or DNS, which would send site traffic through the house
Decisions	ADR-0006, ADR-0010, ADR-0011, and, made during it, ADR-0015
Related	CHG-0001

Summary

iTunes runs on a PC on the home LAN. The broker is inside the Deevnet Mobile site. Neither can reach the other, so nothing that happens in iTunes can reach the stand.

CHG-0003: The Stand Follows What Is Playing

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

CHG-0003: The Stand Follows What Is Playing


Date	2026-10-11
Change type	Deployment
Status	Complete 2026-10-11
Systems	the `services` workload of the `eds` tenant: `eds-lightd`, and a new `eds-nowplayd`; by consequence, `lp-stand-01`
How	`make -C deploy deploy WHERE=builder`
Risk	Low. `lightd` gains an input and loses none. Most likely to go wrong: a settings file that leaves `nowplayd` unable to log in to the broker, which shows as a unit restarting
Decisions	ADR-0006, ADR-0008, ADR-0009
Related	CHG-0002, whose follow-up this is

Summary

Since CHG-0002 the agent Pi has reported what iTunes is playing to the broker, and nothing has acted on it. The stand shows whatever cover was last sent to it by hand.

CHG-0004: Spotify on the Agent Pi

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

CHG-0004: Spotify on the Agent Pi


Date	2026-10-11
Change type	Deployment
Status	Complete 2026-10-11
Systems	the agent Pi `dv02rpi002p01`; the `np-relay` broker account of the `eds` tenant; `eds-nowplayd` on the `services` workload
How	`terraform apply`; `make -C deploy units`; `make -C deploy/relay push spotify`
Risk	Low to the stand, which this change is designed not to affect. Most likely to go wrong: the account change reissuing the relay’s password, which would silence iTunes too
Decisions	ADR-0012, ADR-0016
Related	CHG-0002, CHG-0003

Summary

The agent Pi follows iTunes. After this change it also follows a Spotify account, and reports what that account plays on the devices named as being in the room.

CHG-0005: The Agent Reports Its Events

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

CHG-0005: The Agent Reports Its Events


Date	2026-10-11
Change type	Deployment
Status	Complete 2026-10-11
Systems	the `eds` tenant’s device registry and the `np-relay` broker account; the agent Pi `dv02rpi002p01`
How	`terraform apply -target`; `make -C deploy/relay push`; one line added to the Pi’s settings
Risk	Low. Most likely to go wrong: giving the account a device replaces it and reissues its password, which would silence both drivers
Decisions	ADR-0017
Related	CHG-0004

Summary

The agent Pi follows iTunes and Spotify and says so only in its own journal. After this change it is a registered device of the tenant and reports its key events to the log store: each track that plays, and each time a driver comes or goes.

CHG-0006: The Console

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

CHG-0006: The Console


Date	2026-10-11
Change type	Deployment
Status	Complete 2026-10-11
Systems	the `eds` tenant: a new broker account and a DNS name; the `services` workload: a new `eds-console`, and its firewall
How	`terraform apply`; `make -C deploy deploy WHERE=builder`
Risk	Low. Nothing existing is changed except by being restarted. Most likely to go wrong: the console unable to bind port 80 as a user who is not root
Decisions	ADR-0018
Related	CHG-0003

Summary

EdS gains a page of its own: what is playing and on which player, its cover, each stand drawn in the colors and motion it was sent, and whether each part is up. It is served from the workload at http://console.eds.mobile.deevnet.net/ and only looks.

CHG-0007: The Console Over TLS

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

CHG-0007: The Console Over TLS


Date	2026-10-11
Change type	Deployment
Status	Complete 2026-10-11
Systems	the `eds` tenant: a certificate, held in its state; the `services` workload: `eds-console`, and its firewall
How	`terraform init -upgrade`, `terraform apply`; `make -C deploy deploy WHERE=builder`
Risk	Low. Most likely to go wrong: the console unable to read its key as the user it runs as, which stops it at start with the reason in its log
Decisions	ADR-0018; Deevnet ADR-0037, which gave tenants a CA to ask
Related	CHG-0006; Deevnet CHG-0047, which built the Tenant Service CA this is the first use of

Summary

The console is served in the clear, because when it was built nothing on the site would certify a name a tenant serves. Deevnet IoTaaS now has a Tenant Service CA (Deevnet ADR-0037), and a tenant can ask it for a server certificate for a name in its own zone.

CHG-0008: The Stand Reports Its Colors

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

CHG-0008: The Stand Reports Its Colors


Date	2026-10-11
Change type	Upgrade
Status	Complete 2026-10-11
Systems	`lp-stand-01`, over USB from the development Mac
How	`make -C firmware/lp-stand build flash PORT=/dev/cu.usbserial-0001`
Risk	Low. Most likely to go wrong: a flash that also erased the stand’s credentials, which would leave it off the network until provisioned again
Decisions	ADR-0005
Related	CHG-0001

Summary

When the stand applies a scene it reports the effect, how many colors and the brightness. It does not say which colors. The firmware that does has been on main since it was written for a dashboard panel that was not kept, and has never been on the stand.

CHG-0009: Two Effects for the Accents

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

CHG-0009: Two Effects for the Accents


Date	2026-10-11
Change type	Upgrade
Status	Complete 2026-10-11
Systems	`lp-stand-01`, over USB; `eds-lightd` and `eds-console` on the `services` workload
How	`make -C firmware/lp-stand build flash`; `make -C deploy deploy WHERE=builder`
Risk	Low. Most likely to go wrong: `lightd` asking for an effect the stand does not know, which the stand shows as a steady color
Decisions	ADR-0001
Related	CHG-0008

Summary

The stand’s default effect, breathe, lights a cover’s dominant color and nothing else. The other colors lightd picks, the accents, reach the stand in every scene and are used only by sweep.

CHG-0010: A Look for One Album, and a Strip of Eighteen

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

CHG-0010: A Look for One Album, and a Strip of Eighteen


Date	2026-10-11
Change type	Upgrade
Status	Complete 2026-10-11
Systems	the `eds` tenant: two broker accounts gain a topic; `eds-nowplayd`, `eds-lightd` and `eds-console` on the `services` workload; `lp-stand-01`, over USB
How	`terraform apply`; `make -C firmware/lp-stand build flash`; `make -C deploy deploy WHERE=builder`
Risk	Low. Most likely to go wrong: a grant that does not match the topic, which the broker refuses without saying so and which leaves every album lit from its cover as before
Decisions	ADR-0019
Related	CHG-0009

Summary

Two things, deployed together because they touch the same three programs.

CHG-0011: Spotify Turned Off

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

CHG-0011: Spotify Turned Off


Date	2026-10-11
Change type	Configuration
Status	Complete 2026-10-11
Systems	the agent Pi: one line of its settings, and its agent restarted
How	`make -C deploy/relay drivers DRIVERS=itunes`
Risk	Low. Most likely to go wrong: the agent not coming back, which would stop iTunes being followed too
Decisions	ADR-0012, unchanged
Related	CHG-0004, which turned it on

Summary

The Spotify driver works, and nothing uses what it reports: the stand does not follow Spotify, by decision. Meanwhile it asks Spotify what is playing every ten seconds, all day. Its owner is not using it for now and will come back to it.

CHG-0012: The Cover Screen

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

CHG-0012: The Cover Screen


Date	2026-10-11
Change type	Deployment
Status	In progress
Systems	a new device, `cover-screen-01`; the tenant’s Terraform (one device, one broker account, grants on two others); `nowplayd` on the workload; the agent on the Pi
How	`make flash` and `make provision` in `firmware/cover-screen`; `make plan apply` in `infra/deevnet-tenant-eds`; `make -C deploy deploy WHERE=builder`; `make -C deploy/relay push`
Risk	Medium. It is the first change that lets anything alter what plays. Most likely to go wrong: the agent or `nowplayd` not coming back, which would stop the stand following the music
Decisions	ADR-0020, which this is the evidence for
Related	CHG-0002, which made the accounts this adds to

Summary

A touch screen is added beside the stand. It shows the cover of what is playing and, when touched, five buttons: play or pause, previous, next, volume up, volume down.

CHG-0013: The Turntable Driver

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

CHG-0013: The Turntable Driver


Date	2026-10-11, run on 2026-10-12 UTC
Change type	Deployment
Status	Complete 2026-10-12
Systems	the tenant (one broker account), the agent Pi (its agent, its unit, a recognizer installed, two lines of its settings)
How	`make apply` in the tenant; `make -C deploy/relay push`, `turntable`, `drivers`
Risk	Medium. Most likely to go wrong: the agent’s unit, which changes how it is confined, not starting, which would stop iTunes being followed too
Decisions	ADR-0021
Related	CHG-0002, which made the account; CHG-0012, in progress on the same Pi

Summary

The agent Pi gains a third driver, which listens to the amplifier’s tape output through a USB audio interface and reports the record that is playing.

CHG-0014: The Owner's Collection

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

CHG-0014: The Owner’s Collection


Date	2026-10-12
Change type	Deployment
Status	In progress — a record from the collection is shown with its own sleeve; one that is not in it has not been tried
Systems	the services workload: nowplayd’s image, its unit, one settings file changed and one added. The console’s image, for one line of its page
How	`make -C deploy deploy WHERE=builder`
Risk	Medium. Most likely to go wrong: nowplayd’s unit, which names a new settings file, not starting; nothing would then be current and the stand would hold its last scene
Decisions	ADR-0022
Related	CHG-0013, which put the turntable on the bus

Summary

nowplayd learns to ask its owner’s Discogs collection which record a track from the turntable is on.

CHG-0015: The Turntable's Power Beacon

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

CHG-0015: The Turntable’s Power Beacon


Date	2026-10-12
Change type	Deployment
Status	In progress
Systems	a new device, `turntable-power-01`; the tenant’s Terraform (one device, one broker account, a grant on two others); `nowplayd` and the console on the workload
How	`make flash` and `make provision` in `firmware/power-beacon`; `make plan apply` in `infra/deevnet-tenant-eds`; `make -C deploy deploy WHERE=builder`
Risk	Low to medium. `nowplayd`’s rule for what is current changes, for the turntable only and only once its beacon has been heard. Most likely to go wrong: `nowplayd` or the console not coming back, which would stop the stand following the music or blank the page
Decisions	ADR-0023, which this is the evidence for
Related	CHG-0013, whose follow-up about a lifted needle this answers; CHG-0012, the last device added, and the shape this follows

Summary

A bare ESP32-S2 goes on the outlet that is switched with the turntable. It is connected to the broker while the turntable is on and says nothing else.

CHG-0016: Idle, the Screen on the Console, and No Buttons for a Record

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

CHG-0016: Idle, the Screen on the Console, and No Buttons for a Record


Date	2026-10-12
Change type	Upgrade
Status	In progress
Systems	`nowplayd`, `lightd` and the console on the workload; the cover screen’s firmware; the tenant’s Terraform (one grant on the console’s account)
How	`make plan apply` in `infra/deevnet-tenant-eds`; `make -C deploy deploy WHERE=builder`; `make flash` in `firmware/cover-screen`
Risk	Medium. What lights the room changes: the stand dims by itself for the first time. Most likely to go wrong: the stand dim when something is playing, or lit when nothing is
Decisions	ADR-0024 and ADR-0025, which this is the evidence for
Related	CHG-0015, on whose branch this is built and whose console change this adds to

Summary

Three things, asked for together.

CHG-0017: The Gap Between Tracks, and a Silent Turntable

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

CHG-0017: The Gap Between Tracks, and a Silent Turntable


Date	2026-10-12
Change type	Upgrade
Status	In progress
Systems	`npagent` on the agent Pi (`np-relay`); `nowplayd` and the console on the workload
How	`make -C deploy/relay push`; `make -C deploy deploy WHERE=builder`
Risk	Low. Most likely to go wrong: a wrong title for a few seconds after a quiet passage, or a room that dims while a record is being turned over and surprises someone
Decisions	ADR-0026, which this is the evidence for
Related	CHG-0013, CHG-0016

Summary

Three things about silence, asked for together.

CHG-0018: Counting What Is Asked of Outside Services

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

CHG-0018: Counting What Is Asked of Outside Services


Date	2026-10-12
Change type	Upgrade
Status	In progress
Systems	`npagent` and its recognizer on the agent Pi (`np-relay`); `nowplayd` on the workload; the tenant’s Terraform (one dashboard added)
How	`make plan apply` in `infra/deevnet-tenant-eds`; `make -C deploy/relay push`; `make -C deploy deploy WHERE=builder`
Risk	Low. Nothing that lights the room changes. Most likely to go wrong: the log store refuses `nowplayd`, and its counts stay in the journal
Decisions	ADR-0027, which this is the evidence for
Related	CHG-0017, which is on the Pi and the workload from a branch of its own and is not in this one: see the procedure

Summary

npagent and nowplayd count what they ask of services that are not EdS’s, and say so once a minute. The agent’s counts arrive as events. nowplayd writes its own to the tenant’s log store, which no EdS workload has done before. A dashboard, Outside Services, shows both.

CHG-0019: The Stand Is for Records

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

CHG-0019: The Stand Is for Records


Date	2026-10-13
Change type	Upgrade
Status	In progress
Systems	`nowplayd` and `lightd` on the workload
How	`make -C deploy deploy WHERE=builder`
Risk	Low. Most likely to go wrong: a stand that is dark when someone expects it lit, and is taken for dead
Decisions	ADR-0028, which this is the evidence for
Related	CHG-0016, which gave the stand its idle scene; CHG-0015, whose beacon now decides between dim and dark

Summary

The stand was lit all day: dim whenever nothing played, and from iTunes' cover whenever iTunes did. It is an LP stand, and from this change it is lit by records only.

CHG-0020: The Stand Starts Dark, Blinks, Opens and Scans

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

CHG-0020: The Stand Starts Dark, Blinks, Opens and Scans


Date	2026-10-13
Change type	Upgrade
Status	In progress
Systems	The LP stand (`lp-stand-01`), flashed; `nowplayd`, `lightd` and the console on the workload
How	`make build flash` in `firmware/lp-stand`; `make -C deploy ship WHERE=builder`
Risk	Low. Most likely to go wrong: a stand flashed with something that does not start, which is put right by flashing the build before it; or an opening that is too much for a living room
Decisions	ADR-0029 and ADR-0030, which this is the evidence for
Related	CHG-0019, which made the room dark and left the stand’s own start dim

Summary

Three things asked for in one afternoon, and one flash.

CHG-0021: A New Sound Card for the Turntable

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

CHG-0021: A New Sound Card for the Turntable


Date	2026-10-13
Change type	Configuration
Status	Complete
Systems	`npagent` on the agent Pi (`np-relay`)
How	`make -C deploy/relay turntable DEVICE=plughw:CODEC`
Risk	Low. One line of the agent’s settings, and a restart of the agent
Decisions	ADR-0021
Related	CHG-0013, which named the first input; CHG-0019, since which only a record lights the stand

Summary

The sound card the turntable is heard through was replaced with another USB adapter. The agent was still told to listen to the old one by name, plughw:UA4FX, which was no longer there, so the turntable’s driver heard nothing and reported nothing. With the stand lit for records only, that was a stand that did nothing for a record.

CHG-0022: Spotify Shown, and On Again

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

CHG-0022: Spotify Shown, and On Again


Date	2026-10-13
Change type	Upgrade
Status	In progress
Systems	`npagent` on the agent Pi (`np-relay`); `nowplayd` on the workload
How	`make -C deploy/relay push`; `make -C deploy/relay drivers DRIVERS=itunes,spotify,turntable`; `make -C deploy units`
Risk	Low. Most likely to go wrong: the Spotify authorization given on 2026-10-11 no longer stands, and the driver stops and says so; or the agent does not come back after the push
Decisions	ADR-0031, which this is the evidence for
Related	CHG-0011, which this undoes; CHG-0004; CHG-0020, whose scanner is what was missed from Spotify

Summary

Spotify was reported with no cover, and its driver was off. The driver now takes the album’s picture, Spotify is kept off the stand the way iTunes is, and the driver is on again.

CHG-0023: Spotify Takes Commands

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

CHG-0023: Spotify Takes Commands


Date	2026-10-13
Change type	Upgrade
Status	In progress
Systems	`npagent` on the agent Pi (`np-relay`); the agent’s broker account, in the tenant; the Spotify authorization
How	`make -C deploy/relay push`; `make apply` in `infra/deevnet-tenant-eds`; `make -C deploy/relay spotify AGAIN=1`
Risk	Low. Most likely to go wrong: the authorization is given again and something about it fails, leaving Spotify unreported until it is done once more
Decisions	ADR-0032, which this is the evidence for
Related	CHG-0022, which put Spotify on the cover screen; CHG-0012

Summary

The cover screen’s buttons did nothing while Spotify was current. The Spotify driver now carries out play or pause, next, previous and volume through Spotify’s Web API. Three things have to change for a press to arrive: the agent, the broker account that lets it hear the command, and what Spotify has authorized it to do.

CHG-0024: Spotify Turned Off Again

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

CHG-0024: Spotify Turned Off Again


Date	2026-10-16
Change type	Configuration
Status	Complete 2026-10-16
Systems	the agent Pi: one line of its settings, and its agent restarted
How	`make -C deploy/relay drivers DRIVERS=itunes,turntable`
Risk	Low. Most likely to go wrong: the agent not coming back, which would stop iTunes and the turntable being followed too
Decisions	ADR-0031 and ADR-0032, unchanged
Related	CHG-0022, which turned it on; CHG-0011, the same change once before

Summary

The Spotify driver was asking Spotify what is playing six times a minute, all day, as the Outside Services count showed. Its owner does not want that for now and will come back to it. The agent Pi now runs the iTunes and turntable drivers only. Nothing is removed: the driver, its authorization on the Pi, the broker grants and the app at Spotify all stay, and one command turns it back on.

CHG-0025: Presence Repeated, and Updates Through the Broker

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

CHG-0025: Presence Repeated, and Updates Through the Broker


Date	2026-10-16 (planned)
Change type	Upgrade
Status	Complete 2026-10-17
Systems	The tenant’s broker accounts; `cover-screen-01`, `turntable-power-01` and `lp-stand-01`, by cable; lightd, nowplayd and the console on the services workload; `npagent` on the agent Pi
How	`make plan apply` in `infra/deevnet-tenant-eds`; `make build flash` in each firmware; `make -C deploy deploy WHERE=builder`; `make -C deploy/relay push`; `make ota`
Risk	Medium. Most likely to go wrong: the plan replacing a device’s broker account instead of changing it, which issues a new password and strands that device until it is reprovisioned
Decisions	ADR-0034 and ADR-0035, which this is the evidence for
Related	CHG-0024, the day’s other change

Summary

Two decisions go out together, because the firmware for both goes on by the same cable.

CHG-0026: The Cover Screen Sleeps

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

CHG-0026: The Cover Screen Sleeps


Date	2026-10-17
Change type	Upgrade
Status	Complete 2026-10-17
Systems	`cover-screen-01`
How	`make build ota` in `firmware/cover-screen`
Risk	Low. Most likely to go wrong: the screen sleeping when someone is there, because a source that should count does not name itself in `current`
Decisions	ADR-0036
Related	CHG-0025, which made updates over the air possible

Summary

The cover screen is lit all the time, showing a drawn record to nobody when nothing plays. After this, it goes dark five minutes after current last said something was playing, and lights again for music, a touch, or a lost broker.

CHG-0027: The Beacon on an ESP32

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

CHG-0027: The Beacon on an ESP32


Date	2026-10-18
Change type	Upgrade
Status	Complete 2026-10-18
Systems	`turntable-power-01`: a new board, a plain ESP32, in place of the ESP32-S2
How	`make build flash provision` in `firmware/power-beacon`, by cable
Risk	Low. Most likely to go wrong: the old S2 powered at the same time as the new board. Both log in as `turntable-power-01`, the broker takes the account from one for the other, and each time says `offline` for the turntable
Decisions	ADR-0023, unchanged: any ESP32 with WiFi and 4 MB will do
Related	CHG-0015, the first beacon; CHG-0025, where the S2 needed an external antenna to join from the turntable

Summary

The beacon moves from an ESP32-S2 to a plain ESP32 that fits the case its owner bought. The case has no opening for an external antenna, and the S2 could not join from the turntable without one. The new board’s antenna is on the board.

CHG-0028: The Back End on One Pi, Tried on DVNTM

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

CHG-0028: The Back End on One Pi, Tried on DVNTM


Date	2026-10-18
Change type	Deployment
Status	In progress
Systems	`dv02rpi003p01` (a Pi 4, wired to DVNTM’s IoT segment on `Gi1/0/11`, `10.20.30.13`, and on DVNT-CORE by Wi-Fi), with a new card. Nothing of the tenant’s, the workload’s, the relay Pi’s or the devices'
How	`make -C deploy/backend image fetch`; the card flashed by its owner; `make card`; first boot; `make status`
Risk	Low. Most likely to go wrong: the card’s first boot not finishing (`deevnet-kit` or `eds-backend-setup`), which leaves a Pi to reflash and nothing else touched
Decisions	ADR-0033, whose evidence this is
Related	Deevnet CHG-0048, which gave `dv02rpi003p01` its switch port; Deevnet CHG-0049, which rebuilt the take-home image this is built on

Summary

The whole of EdS on one Pi, beside the tenant: its own broker, log store, Grafana, the four services and the agent. It is tried on the kit’s network first, where the devices are, and goes to the home network only once it works.

CHG-0029: The Turntable's Album by What Is on It

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

CHG-0029: The Turntable’s Album by What Is on It


Date	2026-10-19
Change type	Upgrade
Status	In progress
Systems	The home backend Pi, `dv01rpi001p01` (`192.168.2.40`): nowplayd and npagent, with the other services restarted
How	`make -C deploy/backend push PI=192.168.2.40` from `main` at `44828a9`
Risk	Low. Most likely to go wrong: a lookup that names the wrong album for a record not in the collection; the stand is lit from the wrong sleeve until the next track
Decisions	ADR-0038, whose evidence this is
Related	CHG-0028, the Pi this goes to

Summary

On the first evening at home, Animals put on a minute after The Dark Side of the Moon kept Dark Side’s rainbow: the driver held a side’s first album for ten minutes of silence. ADR-0038 names the album by what is on the record instead, and prefers the original album. This puts it on the Pi.

CHG-0030: The Console Switches the Stand

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

CHG-0030: The Console Switches the Stand


Date	2026-10-19
Change type	Upgrade
Status	In progress
Systems	The home backend Pi, `dv01rpi001p01` (`192.168.2.40`): nowplayd, the console, the `nowplayd` and `console` broker accounts; the other services restarted
How	`make -C deploy/backend push PI=192.168.2.40` from branch `adr-0039-stand-for-every-source` (PR #60), before it is merged
Risk	Low. Most likely to go wrong: the two accounts made again with grants the broker refuses, and nowplayd or the console unable to log in until they are put back
Decisions	ADR-0039, whose evidence this is
Related	CHG-0029, the push before this one

Summary

The console gets a switch that lights the stand for every source, for working on the stand’s looks with iTunes and Spotify. Pushed from the PR’s branch so it can be tried before it is merged.

CHG-0031: The Turntable Heard Through a UFO202

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

CHG-0031: The Turntable Heard Through a UFO202


Date	2026-10-21
Change type	Configuration
Status	Complete 2026-10-21
Systems	`dv02rpi003p01`, the back-end Pi: one line of its agent’s settings, and its agent restarted
How	`make -C deploy/backend turntable DEVICE=plughw:CODEC PI=192.168.2.40`
Risk	Low. Most likely to go wrong: the agent not coming back, which would stop iTunes being followed too
Decisions	ADR-0021, unchanged
Related	CHG-0028, which named `plughw:UA4FX`

Summary

The turntable was heard through a Roland UA-4FX, and the Pi’s agent listened to plughw:UA4FX. Its owner found a Behringer UFO202 and plugged it into the Pi in the UA-4FX’s place. ALSA names it CODEC (card 3, USB Audio CODEC), and the UA-4FX is no longer there, so the agent is told the new name. Nothing else changes: the same line-level feed from the selector, the same driver, the same recognizer.

CHG-0032: American Idiot Has a Look

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

CHG-0032: American Idiot Has a Look


Date	2026-10-23
Change type	Upgrade
Status	Complete 2026-10-23
Systems	`dv02rpi003p01`, the back-end Pi: nowplayd and lightd replaced, and the four services restarted
How	`make -C deploy/backend push PI=192.168.2.40`, from #60’s branch with this change on it
Risk	Low. Most likely to go wrong: a service not coming back after the push, which leaves the stand dark until it is pushed again
Decisions	ADR-0019, a second album on its list
Related	CHG-0030, whose branch is what runs on the Pi and is pushed again here

Summary

Green Day’s American Idiot was lit from the owner’s own pressing once the record was added to the Discogs collection. That sleeve’s picture is a photograph, and lightd read it as one red in four shades (#df0040 56%, #b90237 16%, #92122f 14%, #671c2b 14%), which a strip of LEDs shows as one red going nowhere. Deezer’s clean scan of the same sleeve, a few minutes earlier, had read as two reds with the pale pink of the hand and a salmon among them (#d90018 45%, #e22f28 31%, #efb6b0 13%, #e35f55 12%), and its owner liked that better.

CHG-0033: An Album Asked For on the Bus

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

CHG-0033: An Album Asked For on the Bus


Date	2026-10-23
Change type	Upgrade
Status	In progress
Systems	The tenant’s services workload (`services.eds.mobile.deevnet.net`): the four services rebuilt and restarted. `dv02rpi002p01`, the relay: `npagent` replaced
How	`make -C deploy ship WHERE=builder` and `make -C deploy/relay push`, from the branch `voice-play-album`
Risk	Low. Most likely to go wrong: a service not coming back, which leaves the mobile site’s stand and screen without a current track until shipped again. The home back-end Pi is not touched
Decisions	ADR-0040, whose command this puts on the bus
Related	CHG-0032, the last change, made on the back-end Pi

Summary

play_album is the first command that chooses what plays (ADR-0040). npagent play-album has already played Van Halen’s first album from the relay by hand; this puts the same request behind the bus. nowplayd passes play_album to itunes whatever is current, and the iTunes driver asks for the album and then asks what plays.

CHG-0034: voiced and scribe on the Workload

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

CHG-0034: voiced and scribe on the Workload


Date	2026-10-24
Change type	Deployment
Status	In progress
Systems	The tenant’s Terraform on the mobile site’s API: broker accounts for `voiced` and `respeaker-01` and the device `respeaker-01` created; `console` and `nowplayd` given `nowplaying/stand`. The services workload: `eds-scribe` and `eds-voiced` added, the other four rebuilt and restarted
How	`make -C infra/deevnet-tenant-eds apply`, then `make -C deploy kit-env deploy WHERE=builder`, from the branch `voice-play-album`
Risk	Medium. The workload has two cores and two gigabytes, and scribe’s model takes a few hundred megabytes of it: most likely to go wrong is memory, which would stop a service. `eds-scribe` is held to 900 MB for that reason. Updating `console` and `nowplayd` in place keeps their passwords
Decisions	ADR-0042; ADR-0039, whose grant this applies to the tenant at last
Related	CHG-0033, which put `play_album` on the bus; CHG-0030, which switched the stand on the back-end Pi only

Summary

A spoken request is written down by scribe and made a command by voiced (ADR-0042). Both have run on a Mac against the development broker. This puts them on the workload, with voiced’s own broker account, and registers the reSpeaker, whose account is the one that may publish a request.

CHG-0035: Only Words scribe Is Sure Of

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

CHG-0035: Only Words scribe Is Sure Of, and the reSpeaker Asked From Its Console


Date	2026-10-24
Change type	Upgrade
Status	Complete 2026-10-24
Systems	The services workload: the six services rebuilt, `eds-scribe` and `eds-voiced` changed, all restarted. `respeaker-01`: firmware flashed by cable
How	`make -C deploy ship WHERE=builder`; `make -C firmware/ears build flash`, from `e9ed753` on `voice-play-album`
Risk	Low. Most likely to go wrong: scribe’s thresholds refusing speech it should take, which is a request said again, not a record played wrongly
Decisions	ADR-0042, ADR-0043
Related	INC-0001, which this corrects

Summary

The reSpeaker’s first request played Abbey Road, which nobody asked for (INC-0001): scribe’s model wrote its own prompt back, a request in words, and voiced acted on it. scribe’s prompt is now a list of names, and scribe says whether the words are worth acting on, by Whisper’s own thresholds; voiced acts on nothing else.

CHG-0036: The reSpeaker Wakes to "Hey Jarvis"

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

CHG-0036: The reSpeaker Wakes to “Hey Jarvis”, and Hears a Request Until It Ends


Date	2026-10-24
Change type	Upgrade
Status	Complete 2026-10-24
Systems	`respeaker-01`: firmware flashed by cable. The services workload: `eds-voiced` rebuilt with the others and all restarted
How	`make -C firmware/ears build flash`; `make -C deploy ship WHERE=builder`
Risk	Low. Most likely to go wrong: the device waking for something that is not its name, which sends a few seconds of the room; voiced acts only on a request it is sure of (INC-0001)
Decisions	ADR-0043
Related	CHG-0035

Summary

The reSpeaker listens for a wake word: microWakeWord’s “Hey Jarvis”, ESPHome’s model, on TensorFlow Lite Micro with the audio frontend it was trained on. What follows it is heard until the speaker stops - 0.7 s quieter than the room by 10 dB, at most six seconds - and sent, with the 350 ms before the wake was decided on, so that a “play” said straight after keeps its P. voiced allows a word or two before “play”, for the end of the wake word that comes with it, but never a negation.

CHG-0037: A Request Answered Sooner

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

CHG-0037: A Request Answered Sooner


Date	2026-10-24
Change type	Upgrade
Status	In progress
Systems	`respeaker-01`: firmware flashed by cable. The services workload: all six rebuilt, `eds-voiced`’s unit changed and `/var/lib/eds-voiced` made
How	`make -C firmware/ears build flash`; `make -C deploy deploy WHERE=builder`
Risk	Low. Most likely to go wrong: a request cut before its last word, which is a request said again
Decisions	ADR-0042, ADR-0043
Related	CHG-0036, whose request took 21 s from the wake word to the music

Summary

From “Hey Jarvis” to the music took 21 s in CHG-0036: 6.4 s heard, because the room never got as quiet as the floor learned from its quietest moments; 5.3 s to send 200 KB at -80 dBm; 4.6 s to write down; 5 s to count Aerosmith’s albums in MusicBrainz after a restart had forgotten them.

CHG-0038: A Misheard "Play", and a Longer Pre-roll

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

CHG-0038: A Misheard “Play” Is Taken for One Where the Rest Is an Album by Its Place, and the Pre-roll Is 600 ms


Date	2026-10-24
Change type	Upgrade
Status	In progress
Systems	The services workload: nowplayd and voiced sent and all restarted. `respeaker-01`: flashed by cable
How	`make -C deploy ship WHERE=builder`, the first with `load.sh` (INC-0002); `make -C firmware/ears build flash`
Risk	Low. Most likely to go wrong: a sentence that is not a request read as one; only “X’s Nth album” and “the Nth album by X” are read behind a misheard “play”
Decisions	ADR-0042, ADR-0043
Related	CHG-0037

Summary

After CHG-0037 and ADR-0044, “Hey Jarvis, play Aerosmith’s first album” played in 8 s from the wake word: 2 s heard, sent in 89 ms, 4 s to write down, 1.7 s to count. The music dipped while it listened. “Play Van Halen’s first album”, straight after, was written “Tae Van Halen’s first album.” and was not a request.

CHG-0039: scribe in Two, and "Hey Jarvis" in Its Prompt

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

CHG-0039: scribe Is a Base Sent Once and Its Code Built on the Workload, and “Hey Jarvis” Is in Its Prompt


Date	2026-10-24
Change type	Upgrade
Status	In progress
Systems	The services workload: `eds-scribe-base` loaded, `eds-scribe` built there, nowplayd and voiced sent, all restarted
How	`make -C deploy ship WHERE=builder`
Risk	Medium. Most likely to go wrong: the core router under the base’s one transfer (INC-0002), which is compressed to 256 MB and held to 5 MB/s
Decisions	ADR-0042
Related	INC-0002, whose follow-up this is; CHG-0038

Summary

The end of the wake word, kept with each request, was written “Lee Jarvis”, “Jay Jarrus”, “Travis”, “The band was very generous”, and the request after it was misheard with it. With “Hey Jarvis” in scribe’s prompt, the same recordings, cut as the device cuts them, were written “Jarvis,” each time, and nothing else changed.

CHG-0040: The Owner's Library for voiced

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

CHG-0040: voiced Matches Requests Against an Index of the Owner’s Library


Date	2026-10-24
Change type	Upgrade
Status	In progress
Systems	The services workload: voiced sent and its unit replaced; `library.json` copied to `/var/lib/eds-voiced`. The relay Pi: npagent, for the driver’s title matching
How	`make -C deploy ship WHERE=builder`, `make -C deploy units`, `make -C deploy library XML=…`; the relay’s push
Risk	Low. Most likely to go wrong: a near but wrong artist or album chosen; without the index, voiced is as it was
Decisions	ADR-0046
Related	CHG-0039

Summary

voiced gains NP_LIBRARY, an index of the owner’s iTunes library made from its XML, and chooses from it the artist and album a request means, by the library’s own names. The driver asks iTunes for the whole title first and its plain start after.

CHG-0041: voiced Asks eds-inventory

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

CHG-0041: voiced Asks eds-inventory for the Owner’s Albums


Date	2026-10-24
Change type	Upgrade
Status	Complete 2026-10-24
Systems	The services workload: eds-inventory installed beside EdS’s services (eds-inventory’s CHG-0001); voiced sent and its unit replaced
How	In eds-inventory: `make -C deploy image load unit WHERE=builder`, then `make -C deploy library XML=…`. Here: `make -C deploy ship WHERE=builder`, `make -C deploy units`
Risk	Low. Most likely to go wrong: the inventory not answering, and albums guessed at as with no library; `make deploy`’s restart of every EdS service
Decisions	ADR-0047
Related	CHG-0040, the index this replaces

Summary

eds-inventory’s inventoryd goes onto the services workload with the owner’s iTunes library collected into it, and voiced is pointed at it with NP_INVENTORY_URL. library.json stays where it is, unread while the inventory is configured.

CHG-0042: The Home Pi Becomes a Deevnet Pi

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

CHG-0042: The Home Pi Becomes a Deevnet Pi, and the Devices Hold Both Sites


Date	2026-10-26
Change type	Migration
Status	Complete
Systems	The home backend Pi, `192.168.2.40` on DVNT-CORE, with a new card named `dv01rpi001p01` (the card in it now calls itself `dv02rpi003p01`); `turntable-power-01`, `cover-screen-01`, `lp-stand-01`, `respeaker-01`; the tenant’s Terraform (one `deevnet_certificate`); the home network’s DNS
How	`make -C deploy/backend image fetch card`; `deevnet-kit cert request` and `cert install`; `terraform apply` in `infra/deevnet-tenant-eds`; `make pair spotify turntable drivers status devices`; `provision_tenant.py --site home --also mobile=terraform` on each device
Risk	Medium. Most likely to go wrong: a device refusing the broker’s new certificate. No ESP32 has yet verified a server through Deevnet’s Tenant Service CA to the Root
Decisions	ADR-0033, ADR-0049; Deevnet ADR-0040 (site-less names) and ADR-0041 §2 (a Deevnet Pi)
Related	CHG-0028, which built the card this replaces; Deevnet CHG-0054 and CHG-0056, which built the names and the kit’s `cert` commands

Summary

The home Pi runs EdS on a card whose certificate is signed by that card’s own CA, for names entered by hand in the home DNS. The devices dial its address and trust that CA, and hold one site’s settings.

CHG-0043: The Backend Pi Names the Record the Recognizer Heard

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

CHG-0043: The Backend Pi Names the Record the Recognizer Heard


Date	2026-10-29
Change type	Deployment
Status	Complete
Systems	The home backend Pi, `eds-backend` (`192.168.2.40`): its five services and the agent
How	`make -C deploy/backend push`, from the branch of PR #109
Risk	Low. Most likely to go wrong: a service not coming back after the push, which `push.sh` checks
Decisions	ADR-0038, as revised by PR #109
Related	CHG-0042, during whose last check the fault was found

Summary

At the end of CHG-0042, Journey’s “Wheel in the Sky”, heard on Infinity, was named Alive in America, a live album, and the stand lit from its cover. Deezer lists the track on live albums, best-ofs and a 2008 re-recording, never on Infinity, and the recognizer’s album was asked about only when the catalog had nothing.

CHG-0044: Spotify Is Switched From the Backend Pi's Console

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

CHG-0044: Spotify Is Switched From the Backend Pi’s Console


Date	2026-10-29
Change type	Deployment
Status	Complete
Systems	The home backend Pi, `eds-backend` (`192.168.2.40`): its services, the agent, and the broker accounts `eds-console` and `eds-np-relay`
How	`make -C deploy/backend push` and `make drivers DRIVERS=itunes,spotify,turntable`, from the branch of PR #106
Risk	Low. Most likely to go wrong: Spotify asked all day again, which the switch defaulting to off is there to prevent
Decisions	ADR-0051
Related	CHG-0024, whose follow-up this answers; CHG-0043, the push before

Summary

The backend Pi ran 4e51363 and did not run the Spotify driver. After: it runs ADR-0051’s agent and console. Spotify is allowed in NP_DRIVERS, and whether it runs is the console’s switch, off unless switched on.

CHG-0045: The Backend Pi's iTunes Pairing Is Kept

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

CHG-0045: The Backend Pi’s iTunes Pairing Is Kept


Date	2026-10-29
Change type	Deployment
Status	Complete
Systems	The home backend Pi, `eds-backend` (`192.168.2.40`): its tools and its iTunes pairing; iTunes on MEDIA-SERVER, which gained a remote; the owner’s Mac, which gained an age key
How	`secrets/new-key.sh`; `make -C deploy/backend push`, `make pair`, `make pairing`, from the branch of PR #107
Risk	Low. Most likely to go wrong: the Pi left unpaired by a test, which a copy set aside guarded
Decisions	ADR-0052, and ADR-0037’s first step
Related	CHG-0044, the push before

Summary

The backend Pi’s iTunes pairing lived on its card alone, under the name “EdS”. After: it pairs as “EdS home”, and the pairing is kept in the repository, encrypted to the owner’s age key, so a new card for this Pi starts paired.

CHG-0046: The Backend Pi Is on Its Cable Alone

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

CHG-0046: The Backend Pi Is on Its Cable Alone


Date	2026-10-30
Change type	Configuration
Status	Complete
Systems	The home backend Pi, `eds-backend`; the backend image (`images/backend`) and `deploy/backend/card.sh`
How	`nmcli` on the Pi, over its cable; the image’s playbook and `card.sh` changed for the next card
Risk	Low. Most likely to go wrong: the session that makes the change riding the Wi-Fi it removes, which connecting to the wired address prevents
Decisions	None of its own. It is ADR-0053’s “radio off by default” before that record’s window is built, and CHG-0028’s “one address at home”
Related	CHG-0042, whose card asked for Wi-Fi; CHG-0028

Summary

The backend Pi had two addresses on the home network: 192.168.2.40 on its cable and 192.168.2.228 on Wi-Fi. Both were on DVNT-CORE. The Wi-Fi was deevnet-kit-wifi, which deevnet-kit made on the first boot from the network make card asked for. A second address on the same network bought nothing, appeared in the kit’s address warning, and could answer for eds-backend.local.