Skip to content

E1 Tier 3: virtual slave nodes (blocked — needs a Bridge Controller dongle) #147

Description

@Assar63

Child of #142 (Addressable presence, E1) — Tier 3. Blocked on hardware; tracking only.

Host fully independent virtual slave node identities via the Bridge-Controller-only slave Serial API (SET_SLAVE_LEARN_MODE, SEND_SLAVE_NODE_INFORMATION, APPLICATION_SLAVE_COMMAND_HANDLER, SEND_SLAVE_DATA, GET_VIRTUAL_NODES, IS_VIRTUAL_NODE — verify exact FUNC_IDs against docs/).

Blocker

The current Aeotec Z-Stick Gen5 is a Static Controller (libtype 1, probed 2026-06-05 via scripts/zw-dongle-probe). The slave Serial API family requires a Bridge Controller dongle. Re-run the probe on any candidate hardware.

Only pursue if

Tiers 1–2 prove insufficient for a real requirement and a Bridge Controller is acquired. Sketch: src/virtual-node/VirtualNodeRegistry (SQLite, (home_id, virtual_node_id)) + slave-FUNC_ID host-API codecs + a VirtualNodeCommand bus event, mirroring the existing AddNode/SendData request/callback machinery.

No work until unblocked.

Metadata

Metadata

Assignees

No one assigned

    Labels

    daemon-hardwareDongles, chip families, multi-controllerfutureNiche / very large / no concrete demand todayneeds-hardware-testFinal acceptance requires manual on-bench testing with real Z-Wave hardwarerole: responderDaemon reacts to / is addressed by devices: orchestrators + E1 endpoint/presence responders

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions