← Back to Skills Marketplace
ctz168

Iot Bridge

by SamAI.cc · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
17
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install iot-bridge
Description
Bridge IoT devices to the cloud via aitun tunnel. Expose local MQTT brokers, device dashboards, or HTTP APIs so remote devices and services can connect, repo...
README (SKILL.md)

IoT Bridge - Connect IoT Devices via Aitun Tunnel

When to Use

Use this skill when:

  • You have IoT devices on a local network that need to be accessible from the internet
  • You want to expose a local MQTT broker or IoT gateway for remote device connections
  • You need to access a local IoT dashboard (Home Assistant, Node-RED, Grafana) remotely
  • You want to bridge local sensors or actuators to a cloud platform for data aggregation
  • You need to test IoT integrations where the device or service is behind NAT/firewall

Do NOT use this skill when:

  • The IoT platform is already cloud-hosted and publicly accessible
  • You only need local device-to-device communication (no tunnel needed)
  • You want to share a static file (use sendfile instead)

Instructions

Step 1: Install aitun

pip install aitun

Or verify it is already installed:

which aitun || pip show aitun

Step 2: Start the local IoT service

Start the IoT service you want to expose. Examples:

# Home Assistant
hass --config /path/to/config &

# Node-RED
node-red --port 8080 &

# Mosquitto MQTT broker
mosquitto -p 1883 -v &

# Custom IoT HTTP API / dashboard
python3 -m http.server 8080 --directory /path/to/dashboard &

# Grafana dashboard
grafana-server --homepath /usr/share/grafana &

Step 3: Create a tunnel

For HTTP-based services (dashboards, REST APIs):

aitun -p 8080 &
AITUN_PID=$!
sleep 3

For TCP-based services (MQTT broker on port 1883, use with auth token):

aitun -p 1883 --tcp-ports 1883 -k YOUR_TOKEN &
AITUN_PID=$!
sleep 3

The output will contain the public URL, e.g.:

  • https://aitun.cc/abc123 (HTTP)
  • TCP forwarding address for MQTT

Step 4: Share the IoT endpoint

Your IoT service is now accessible at: https://aitun.cc/abc123

- Dashboard: open in browser
- API endpoint: use for device data upload
- MQTT broker: connect via TCP forwarding

This tunnel expires in 24 hours.
For a permanent endpoint, register at https://aitun.cc

Step 5: Connect remote devices or services

Configure remote IoT devices or cloud services to use the tunnel URL:

  • HTTP devices: Set the reporting URL to https://aitun.cc/abc123/api/data
  • Cloud platforms: Configure the webhook or data source URL to the tunnel address
  • MQTT devices: Connect to the TCP-forwarded MQTT broker address
  • Dashboard users: Open the URL in a browser to view live data

Step 6: Clean up

When done, stop the tunnel and services:

kill $AITUN_PID 2>/dev/null

CLI Reference

The aitun command (installed via pip install aitun) accepts these flags:

Flag Description
-p PORT Local service port (default: 8080)
-k TOKEN Auth token for registered subdomain (omit for free tunnel)
--host HOST Local service address (default: localhost)
--tcp-ports PORTS TCP forwarding ports, comma-separated (e.g., 22,3306; requires -k)
--p2p Enable P2P direct connection (default: enabled)
--no-p2p Disable P2P, force server relay mode
--daemon Run as background daemon
--stop Stop running daemon

Notes

  • Free tunnels use proxy address mode (path-based URL like aitun.cc/abc123), NOT subdomains
  • Free tunnels expire after 24 hours, auto-renewed on restart
  • For a permanent IoT endpoint, register at https://aitun.cc to get a custom subdomain
  • TCP forwarding (for MQTT, Modbus, etc.) requires a registered account and -k token
  • Use --tcp-ports to forward multiple TCP ports: --tcp-ports 1883,5683,502
  • For security, enable authentication on your IoT services before exposing them
  • All traffic is encrypted end-to-end
  • P2P mode reduces latency for real-time device communication
  • Consider rate limiting for high-frequency sensor data
Usage Guidance
Before using this skill, make sure any exposed IoT dashboard, broker, or API has strong authentication, TLS where applicable, least-privilege network binding, and logging. Avoid exposing admin, debug, default-password, or unauthenticated services, and remember that a third-party tunnel can make local device data and controls reachable from the internet.
Capability Tags
crypto
Capability Assessment
Purpose & Capability
The stated purpose is to bridge local IoT devices, MQTT brokers, dashboards, and HTTP APIs to the cloud via Aitun; the public exposure risk is inherent to that purpose and is disclosed.
Instruction Scope
The instructions are user-directed setup steps for installing Aitun, starting local services, creating a tunnel, sharing the endpoint, and cleaning up. They include only limited security guidance, so users need to apply their own access controls before exposing services.
Install Mechanism
The artifact declares a uv install of the aitun package and requires python3; no install-time script, bundled executable, or hidden behavior is present in the artifact.
Credentials
Exposing MQTT, Home Assistant, Node-RED, Grafana, Modbus, or custom APIs can be high impact, but that authority is proportionate to the skill's advertised IoT tunneling purpose and is initiated by the user.
Persistence & Privilege
The skill does not show privilege escalation, credential harvesting, persistent background agents beyond optional tunnel daemon usage, or automatic long-running behavior without user action.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install iot-bridge
  3. After installation, invoke the skill by name or use /iot-bridge
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of iot-bridge skill. - Allows users to bridge IoT devices to the cloud via aitun tunnel. - Supports exposing local MQTT brokers, HTTP APIs, and dashboards for remote access. - Provides step-by-step setup instructions, including installation, tunnel creation, and endpoint sharing. - Supports both HTTP and TCP (e.g., MQTT, Modbus) tunneling, with token-based authentication for advanced features. - Includes security, usage notes, and CLI reference.
Metadata
Slug iot-bridge
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Iot Bridge?

Bridge IoT devices to the cloud via aitun tunnel. Expose local MQTT brokers, device dashboards, or HTTP APIs so remote devices and services can connect, repo... It is an AI Agent Skill for Claude Code / OpenClaw, with 17 downloads so far.

How do I install Iot Bridge?

Run "/install iot-bridge" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Iot Bridge free?

Yes, Iot Bridge is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Iot Bridge support?

Iot Bridge is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Iot Bridge?

It is built and maintained by SamAI.cc (@ctz168); the current version is v1.0.0.

💬 Comments