⚠️Install with caution. This skill has very few installs. Always review the source and verify it on clawhub.ai before installing. Community-built skills run with agent permissions — only install ones you trust.

🍎 Apple Ecosystem

node-connectv1.0.0

Name: node-connect
Author: 1yihui

yihui-node-connect

1yihui

Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi w...

latest

Download Package View on ClawHub

Installs (all time)

Installs (current)

Downloads

643

Stars

CreatedApr 28, 2026

UpdatedMay 11, 2026

Install & Quick Start

Install via ClawdBot CLI:

clawdbot install 1yihui/yihui-node-connect

Skill Package1 files

📋SKILL.mdmarkdown

Failed to load file.

Quality Score

B51/100

Grade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.

Market Validation4/35

· 138 downloads (low demand)
· No tracked installs (may still have real users via manual install)

Documentation16/25

· SKILL.md present
· Detailed documentation (≥3000 chars)
· Detailed summary

Package Completeness6/15

· skillAssets present (0 files)

💡

Usage Guide

Generated May 22, 2026

Developers building companion apps for OpenClaw nodesSystem integrators deploying remote IoT gatewaysIT administrators managing Tailscale-based fleet connectivityintermediate

💡 Application Scenarios

Local Wi-Fi Pairing FailureIoT

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.

Tailscale Remote Access Not WorkingRemote Work

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.

Public URL / Reverse Proxy Setup TestingSaaS

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.

Bootstrap Token Expired After Config ChangeEnterprise Software

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.

Gateway and Node on Same Machine via EmulatorDevelopment Tools

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.

💼 Business Models

Freemium with Paid Remote AccessSubscription

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.

Enterprise Support and TroubleshootingService

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

White-Label Device ManagementLicensing

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

💬 Integration Tip

Always run `openclaw qr --json` to see the effective gateway URL and its source before making config changes. After any route fix, generate a fresh setup code to avoid token expiry.