Control and automate SONOFF devices with eWeLink cloud workflows, LAN and DIY mode operations, and safe multi-device execution.
On first use, read setup.md and align activation boundaries, control plane preferences, and write-safety defaults before sending SONOFF commands.
Use this skill when the user needs practical SONOFF and eWeLink execution: cloud API operations, LAN control workflows, DIY mode RPC-like calls, or staged multi-device automations. Use this instead of generic smart-home advice when outcomes depend on SONOFF-specific eWeLink modes, LAN support differences, and safe rollout behavior.
Memory lives in ~/sonoff/. See memory-template.md for structure and status values.
~/sonoff/
|-- memory.md # Core context and activation boundaries
|-- environments.md # LAN segments, iHost, cloud mode, and endpoint mapping
|-- devices.md # Device registry, capabilities, and command patterns
|-- automations.md # Orchestration rules, scheduling, and rollback plans
`-- incidents.md # Failure signatures and validated recoveries
Use the smallest file needed for the current task.
| Topic | File |
|---|---|
| Setup and activation behavior | setup.md |
| Memory and workspace templates | memory-template.md |
| Control plane selection | control-planes.md |
| Access and auth models | auth-and-access.md |
| Device command workflows | device-operations.md |
| Multi-device rollout playbooks | orchestration-playbooks.md |
| Diagnostics and recovery | troubleshooting.md |
EWELINK_API_TOKEN in environmentNever ask users to paste production secrets in chat logs. Prefer local environment variables and redacted examples.
Keep local operational notes in ~/sonoff/:
EWELINK_API_TOKEN from environment and never persist raw tokens in notes.| Endpoint | Data Sent | Purpose |
|---|---|---|
| http://<device-ip>:8081/zeroconf/* | Device id and command payload fields | SONOFF DIY mode local control and status retrieval |
| http://<ihost-ip>/open-api/v2/rest/* | Local token and control payloads | SONOFF iHost eWeLink CUBE local API control |
| http://<ihost-ip>/open-api/v2/sse/* | Event subscription parameters | Local iHost event stream and status updates |
| https://*.coolkit.cc | Account-scoped API requests and device command payloads | eWeLink cloud control for SONOFF devices |
| https://dev.ewelink.cc | Integration metadata and docs lookups | Validate eWeLink developer behavior and constraints |
| https://help.sonoff.tech | Documentation query terms | Validate SONOFF DIY and API protocol details |
No other data is sent externally.
Data that leaves your machine:
Data that stays local:
~/sonoff/This skill does NOT:
EWELINK_API_TOKEN in local skill filesThis skill sends operational data to SONOFF devices and optionally eWeLink cloud services when execution is approved. Only install if you trust your LAN environment, iHost deployment, and eWeLink account scope with this automation data.
Install with clawhub install <slug> if user confirms:
iot - Device connectivity and IoT system integration patternssmart-home - Home automation architecture and reliability practicesapi - API contract design and robust request handlingmqtt - Messaging patterns for telemetry and event-driven orchestrationhome-server - Self-hosted service operations and network reliability workflowsclawhub star sonoffclawhub syncZIP package — ready to use