Skip to main content
Technical Preview

Overview

Client-mode REST API connectors for Shelly Gen2+ devices (local RPC over HTTP) and the Shelly Cloud Control API v2: switch, cover, light, power and 3-phase energy meter status, energy history, webhooks, relay and cover control. This is one of the templates in the Shelly (Gen2+ local RPC and Shelly Cloud) REST API app (shelly). Deploy it alongside the other connectors of that app when they depend on each other (for example a token connector plus an API connector).
Not yet verified against the live vendor API: No Shelly device reachable from the box and no Shelly Cloud auth key: the local connector needs a Gen2+ device on the LAN, and the cloud connector needs an account server uri + Authorization cloud key + a device id. The real cloud endpoint was probed (401 UNAUTHORIZED without a key); no authenticated live call could run.

Auth

  • schemes: [“none (local, device auth off)”, “auth_key query parameter (cloud)”]
  • secret: SHELLY_CLOUD_AUTH_KEY
  • note: Local HTTP RPC uses SHA-256 Digest (RFC 7616) when auth is enabled; the REST_API connector cannot answer the per-request nonce challenge, so protected devices return 401 except Shelly.GetDeviceInfo and /shelly. Use the device’s native MQTT (<shelly-id>/rpc) or the cloud connector for protected devices.

Template parameters

BASE_ADDRESS default: http://192.168.33.1.

Events

Deploy

Get the template card (JSON with template and metadata) from the broker, then deploy the connector:
The deployable connector from the REST API app, with BASE_ADDRESS already filled in:
Deploy it with -addRoute (do not include ADD METADATA).

Usage example

Call GetShellyIdentity by publishing a JSON payload to its request topic, and read the reply on the response topic:
Last modified on October 21, 2026