esphome::home_io_control::pairing Namespace Reference

Classes
struct	PairingContext
	Context object that lives for the duration of a single pairing attempt. More...

Enumerations
enum class	PairingState : uint8_t {   IDLE , TX_DISCOVER , WAIT_DISCOVER_RESPONSE , TX_DISCOVER_CONFIRM ,   WAIT_DISCOVER_CONFIRM , TX_KEY_INIT , WAIT_KEY_CHALLENGE , TX_KEY_TRANSFER ,   WAIT_KEY_CONFIRM , REGISTER_DEVICE , COMPLETE , FAILED }
	State machine for the three‑phase pairing flow. More...
enum class	DiscoverConfirmResult : uint8_t { SKIPPED , ACKED , ERROR_REPLY , NO_REPLY }
	What PairingEngine::run_discover_confirm_step_() actually observed. More...

Enumeration Type Documentation

DiscoverConfirmResult

enum class esphome::home_io_control::pairing::DiscoverConfirmResult : uint8_t

strong

What PairingEngine::run_discover_confirm_step_() actually observed.

Not stored in PairingContext — nothing downstream reads it, so it is returned directly to the caller, which logs the details (reply channel, try number, elapsed time) and otherwise ignores the result: the step never fails a pairing attempt (see run_discover_confirm_step_()'s doc).

Enumerator
SKIPPED	pairing_discover_confirm tuning mode is skip — no 0x2C was sent.
ACKED	The device answered with CMD_DISCOVER_CONFIRM_ACK (0x2D).
ERROR_REPLY	The device answered with CMD_ERROR_RESP.
NO_REPLY	Every try was silent (or every transmit failed).

Definition at line 82 of file hub_pairing.h.

PairingState

enum class esphome::home_io_control::pairing::PairingState : uint8_t

strong

State machine for the three‑phase pairing flow.

Enumerator
IDLE	No pairing in progress; idle state.
TX_DISCOVER	Discovery broadcast (0x28) sent; awaiting device response.
WAIT_DISCOVER_RESPONSE	Listening for discovery response (0x29) from a device in pairing mode.
TX_DISCOVER_CONFIRM	Discovery-confirm (0x2C) sent to the discovered device.
WAIT_DISCOVER_CONFIRM	Listening for the device's discovery-confirm ack (0x2D).
TX_KEY_INIT	Key‑init (0x31) sent to the discovered device.
WAIT_KEY_CHALLENGE	Waiting for challenge (0x3C) from device as part of key transfer.
TX_KEY_TRANSFER	Key‑transfer (0x32) sent with encrypted system key.
WAIT_KEY_CONFIRM	Waiting for key‑confirm (0x33) from device (key receipt acknowledgement).
REGISTER_DEVICE	Registering device in the runtime registry for the current boot.
COMPLETE	Pairing completed successfully; device ready for use.
FAILED	Pairing failed (timeout, radio error, or protocol violation).

Definition at line 48 of file hub_pairing.h.