Skip to content
OAOpenAppPhysical Security as a Service
Login

Shelly Cloud

  1. Confirm your Shelly devices are visible in the Shelly Cloud app.
  2. Create an OpenApp integration with provider type shelly_cloud and set the config fields below.
  3. Set each Shelly-backed device’s external_id to the Shelly Cloud device_id.
  4. For multi-relay devices, set entity metadata channel_index to the relay channel index (defaults to 0).
Field Type Required Description Default Example
server_uri Secrets Manager
string required Shelly Cloud server URI. https://shelly-<region>.shelly.cloud
auth_key Secrets Manager
string required Shelly Cloud auth key. xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
rate_limit_min_interval_ms
number optional Minimum delay between cloud API calls (rate-limit guard). 1000 1000
Field Type Required Description Default Example
channel_index
integer optional Relay channel index for multi-relay devices. Defaults to 0. 0 0

Policies

Policies restrict access on top of roles — they never grant it. The following apply to this integration:

Invitation curfew

Blocks invitation-based opens during a forbidden time window (for example nights).

Admins and residents are never curfewed; existing invitations are evaluated live, not modified.

Type
invitation_curfew
Enforced at
Access-time
Tiers
OrgIntegration
Default
Not configured — no hour restrictions on invitation-based access.
Enforcement
Enforce

User sharing control

Restricts whether non-admins may share access or create invitations out of band — block outright or require admin approval.

Type
user_sharing
Enforced at
Authoring-time
Tiers
OrgIntegration
Default
Not configured — non-admins may share access freely.
Enforcement
EnforceRequire approval