Shellyv1.0.0

Homeowners use Shelly to automate lighting, heating, and security devices locally via RPC for reliability. They set up schedules and triggers in automations.md, ensuring safety with read-before-write loops to prevent unintended state changes. Cloud mode enables remote control when away, with token security from environment variables.

Businesses deploy Shelly to monitor and control energy usage across multiple locations, using local RPC for real-time telemetry reads and cloud API for centralized reporting. They implement orchestration playbooks for staged rollouts of power-saving policies, with canary checks to avoid large-scale failures. Data is stored in ~/shelly/ for audit trails.

Factories integrate Shelly devices with machinery to track operational status via WebSocket notifications for near real-time updates. Technicians use diagnostics from troubleshooting.md to recover from incidents, enforcing safety gates before high-impact actions like relay toggles. Local network scope ensures low-latency control without cloud dependency.

Retailers automate lighting and climate control in stores using Shelly, with multi-device rollouts managed via orchestration-playbooks.md to ensure consistency. They use MQTT for event pipelines to integrate with inventory systems, keeping local and cloud views reconciled to avoid conflicting states. Security boundaries prevent credential exposure in notes.

Hotels implement Shelly for room automation, allowing guests to control devices via local RPC while staff use cloud-assisted operations for maintenance. They design idempotent automations in automations.md with bounded retries, storing device maps in devices.md to validate component ids before writes. Privacy is maintained by using least-privilege credentials.

Offer a cloud-based platform for managing Shelly devices across multiple clients, with tiered pricing based on device count and automation features. Revenue comes from monthly subscriptions, leveraging the Shelly cloud API for remote operations and providing analytics dashboards. Integration tips include using SHELLY_CLOUD_TOKEN securely and ensuring consistent local-cloud views.

Provide custom setup and automation services for businesses deploying Shelly, using local RPC workflows and orchestration playbooks for safe rollouts. Revenue is generated through project-based fees and ongoing support contracts, focusing on industries like energy or retail. Tips involve reading setup.md first and using protocol-matrix.md to choose the right transport channels.

Sell pre-configured Shelly device kits with tailored automation scripts, targeting smart home or small business markets. Revenue streams include hardware sales and optional premium support, with documentation stored in ~/shelly/ for customer reference. Integration tips emphasize validating component ids before writes and using dry-run modes for safety.