home-assistant: one-off read of open3e Room<N> DIDs 1884-1943 (REN-826) #1151

2026-10-06T11:24:37Z

Ghost commented

2026-10-06 11:24:37 +00:00

What

One-shot Job home-assistant/open3e-room-setpoint-read that sends three read commands on open3e/cmnd to edge-1's running open3e and prints the replies to stdout (Loki):

read-json on 0x6c3 for DID 256 (positive control) + 1884–1943
read-raw on 0x6c3 for 1884–1943 (raw hex)
read-json on 0x6e0 for 1885 (SMARTROOMCONTROL, one read)

Why

REN-826 (owner request REN-800): check whether the RoomSetpoints DIDs carry the FBH room setpoint. The read has to go through the running listener because only one UDS client may run on the bus.

Safety

No write mode. open3e, Mosquitto and HA config are unchanged. No HA restart, no outage merge.
read-json/read-raw go through readByDid (open3e @6553c10), which catches NRCs and timeouts and publishes an ERR topic. read-pure is not used because it crashes the listener on a timeout (wiki open3e-cli-operational-gotchas).
Bus load: about 121 short reads on 0x6c3 plus one 3 s timeout on 0x6e0. The production poll waits a few seconds at most.
backoffLimit: 0, restartPolicy: Never, no TTL, so the commands are sent only once.
Credential: the open3e broker user (readwrite open3e/#).

Verified

YAML parsed (js-yaml) and the script passed sh -n. Topic filter tested against sample topics. It has not reached the cluster yet; Flux applies it on merge.

Revert

Revert this PR, or remove the file once the result is on REN-826. That follow-up PR is mine.

🤖 Generated with Claude Code

## What One-shot Job `home-assistant/open3e-room-setpoint-read` that sends three **read** commands on `open3e/cmnd` to edge-1's running open3e and prints the replies to stdout (Loki): 1. `read-json` on 0x6c3 for DID 256 (positive control) + 1884–1943 2. `read-raw` on 0x6c3 for 1884–1943 (raw hex) 3. `read-json` on 0x6e0 for 1885 (SMARTROOMCONTROL, one read) ## Why REN-826 (owner request REN-800): check whether the Room<N>Setpoints DIDs carry the FBH room setpoint. The read has to go through the running listener because only one UDS client may run on the bus. ## Safety - No write mode. open3e, Mosquitto and HA config are unchanged. No HA restart, no outage merge. - `read-json`/`read-raw` go through `readByDid` (open3e @6553c10), which catches NRCs and timeouts and publishes an ERR topic. `read-pure` is not used because it crashes the listener on a timeout (wiki `open3e-cli-operational-gotchas`). - Bus load: about 121 short reads on 0x6c3 plus one 3 s timeout on 0x6e0. The production poll waits a few seconds at most. - `backoffLimit: 0`, `restartPolicy: Never`, no TTL, so the commands are sent only once. - Credential: the `open3e` broker user (`readwrite open3e/#`). ## Verified YAML parsed (js-yaml) and the script passed `sh -n`. Topic filter tested against sample topics. It has not reached the cluster yet; Flux applies it on merge. ## Revert Revert this PR, or remove the file once the result is on REN-826. That follow-up PR is mine. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

Ghost added 1 commit 2026-10-06 11:24:38 +00:00

home-assistant: one-off read of open3e Room<N> DIDs 1884-1943 (REN-826)

ci/woodpecker/pr/ci-scripts-test Pipeline was successful

Details

ci/woodpecker/pr/pr-review Pipeline was successful

Details

ci/woodpecker/pr/ci-manifests-test Pipeline was successful

Details

6c38c88ce4

One-shot Job that sends three read commands on open3e/cmnd to edge-1's
running open3e (read-json + read-raw on 0x6c3, one read-json on 0x6e0)
and prints the replies for Loki. No write mode, no config change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Ghost approved these changes

2026-10-06 11:34:41 +00:00

Ghost left a comment

Approved at 6c38c88c. Checked: kustomize build ok (Job rendered); image digest = running broker; Secret bootstrap Job Complete; Service mosquitto:1883; no NetworkPolicy; Flux wait=false; open3e@6553c10 readByDid catches NRC/timeout -> topic onebase__ERR/..., which the awk filter keeps (tested on sample topics); onebase overlay keeps full master table, so read-pure is never reached; bridge forwards open3e/cmnd in; client IDs distinct from edge1-bridge-open3e. Expected per wiki: fast NRC 0x31 on 0x6c3 Setpoints/CurrentValues, one 3 s timeout on 0x6e0. Worst case (all timeouts) is about 6 min of stale open3e telemetry with no restart. Revert or delete the file to undo. CI success.

Approved at 6c38c88c. Checked: kustomize build ok (Job rendered); image digest = running broker; Secret bootstrap Job Complete; Service mosquitto:1883; no NetworkPolicy; Flux wait=false; open3e@6553c10 readByDid catches NRC/timeout -> topic onebase_<DID>_ERR/..., which the awk filter keeps (tested on sample topics); onebase overlay keeps full master table, so read-pure is never reached; bridge forwards open3e/cmnd in; client IDs distinct from edge1-bridge-open3e. Expected per wiki: fast NRC 0x31 on 0x6c3 Setpoints/CurrentValues, one 3 s timeout on 0x6e0. Worst case (all timeouts) is about 6 min of stale open3e telemetry with no restart. Revert or delete the file to undo. CI success.

Ghost merged commit 3a9686400d into master

2026-10-06 11:34:53 +00:00

Ghost referenced this issue from a commit

2026-10-06 11:34:54 +00:00

Merge pull request 'home-assistant: one-off read of open3e Room<N> DIDs 1884-1943 (REN-826)' (#1151) from atlas/ren-826-room-setpoint-read into master

Ghost referenced this pull request

2026-10-06 11:39:04 +00:00

home-assistant: remove open3e room setpoint read Job (REN-826) #1152

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: konairius/homelab#1151