HTTP path on the device for challenge-response (defaults to ch_resp).
Numeric host (e.g. 192.168.1.42).
RainMaker node id advertised in TXT node_id.
Whether the device requires a POP before accepting the challenge.
TCP port advertised by the service.
Security version from TXT sec_version (defaults to 0 if missing).
Service instance name (display fallback when nodeId is technical).
On-network device discovered via mDNS (Bonjour / NSD).
Captures everything required to talk to the device directly over LAN HTTP for the on-network challenge-response provisioning flow:
host/port: numeric IP and TCP port the device advertises.popRequired: true if the device demands a Proof-of-Possession before it will accept a challenge.secVersion: security version advertised in TXT records (typically 0/1/2).chRespEndpoint: HTTP path under which the device exposes its challenge-response handler (defaults toch_resp).nodeId: stable identifier the device announces (TXTnode_idor service instance name fallback). Already known to RainMaker cloud.serviceName: raw mDNS service instance name (used as a display label).