node-connectv1.0.0

A user attempts to pair a companion app on the same local Wi-Fi network but the QR code or manual connection fails. Diagnosis reveals the gateway is bound to loopback instead of LAN, preventing node discovery.

A user has a remote gateway behind Tailscale, but nodes cannot connect via Tailscale IP or MagicDNS. The gateway may not have a tailnet IP or the QR code advertises a LAN IP instead of the tailnet route.

A user sets up a public URL via reverse proxy for remote access, but the app still sees a loopback or LAN address in the QR code. The publicUrl config is not being picked up because of conflicting gateway.bind settings.

After fixing network routes, the user reuses an old setup code, causing 'bootstrap token invalid or expired'. A fresh QR code is needed after any URL/auth fix.

A developer runs both gateway and node on the same machine using an emulator or USB tunnel, but the node reports 'pairing required'. The gateway is advertising loopback, which is fine, but the pending approval must be accepted.

Offer basic local pairing free, but charge for advanced remote access features like Tailscale or public URL. Users get local pairing for free, while remote capabilities require a subscription.

Provide premium support contracts for diagnosing and fixing pairing issues in complex network topologies. Charge per incident or monthly retainer.

License the pairing technology to hardware manufacturers who need to integrate remote device management. Revenue from licensing fees and per-device royalties.