shellyctl

shellyctl is an unofficial command line client for the Shelly Gen2 API.

Features

• mDNS discovery of shelly devices on the local network.
• Bluetooth Low Energy (BLE) discovery of shelly devices for RPC, monitoring, and initial setup.
• Command line interface for documented APIs.
• prometheus metrics endpoint with the status of known devices.

Maturity

This library is currently in active development (as of February 2024). It has meaningful gaps in testing and functionality. At this stage there is no guarantee of backwards compatibility.

Usage

shellyctl provides a cli interface for discovering and working with shelly gen 2 devices

Usage:
  shellyctl [flags]
  shellyctl [command]

Device Component RPCs:
  ble         RPCs related to Bluetooth Low-Energy
  cloud       RPCs related to Shelly Cloud
  cover       RPCs related to Cover components
  input       RPCs related to input components
  light       RPCs related to light components
  mqtt        RPCs related to MQTT configuration and status
  schedule    RPCs related to managing schedules
  shelly      RPCs related device management, configuration, and status
  switch      RPCs related to switch components
  sys         RPCs related to system management and status
  wifi        RPCs related to wifi configuration and status.

Servers:
  prometheus  Host a prometheus metrics exporter for shelly devices

Additional Commands:
  completion  Generate the autocompletion script for the specified shell
  help        Help about any command

Flags:
      --config string          path to config file. format will be determined by extension (.yaml, .json, .toml, .ini valid)
      --log-level string       threshold for outputing logs: trace, debug, info, warn, error, fatal, panic (default "warn")
  -o, --output-format string   desired output format: json, min-json, yaml, text, log (default "text")

Use "shellyctl [command] --help" for more information about a command.

Configuration

This utility supports configuration via command-line flags, environment variables, or a config file.

Environment Variable Configuration

Command flags (documented as --flag-name) may alternatively be set as environment variables namespaced with the SHELLYCTL_ prefix and with underscores _ replacing - hyphens. For example, if you're uncomfortable passing the authentication password as a command-line argument, you could pass it as an environment variable.

The following two examples have identical functionality.

shellyctl shelly get-status --auth=my-secret-password --log-level=debug --mdns-search

SHELLYCTL_AUTH=my-secret-password SHELLYCTL_LOG_LEVEL=debug SHELLYCTL_MDNS_SEARCH=true shellyctl shelly get-status 

Config File

Command flags (documented as --flag-name) may be listed in a YAML (extension .yaml), JSON (.json), TOML (.toml), or INI (.ini) file.

For example:

bind-port: 19090
log-level: debug
host:
- http://192.168.1.1/
- http://admin:password@192.168.1.2/

Could be used as a config file for the shellyctl prometheus command.

shellyctl prometheus --config=config.yaml

Prometheus Server

The prometheus sub-command facilitates running a Prometheus compatible metrics server.

See contrib/k8s for instructions on running the prometheus server within a Kubernetes cluster.

Host a prometheus metrics exporter for shelly devices

Usage:
  shellyctl prometheus [flags]

Aliases:
  prometheus, prom

Flags:
      --auth string                        password to use for authenticating with devices.
      --bind-addr ip                       local ip address to bind the metrics server to (default ::)
      --bind-port uint16                   port to bind the metrics server (default 8080)
      --ble-device stringArray             MAC address of a single bluetooth low-energy device. May be specified multiple times to work with multiple devices.
      --ble-search                         if true, devices will be discovered via Bluetooth Low-Energy
      --device-timeout duration            set the maximum time allowed for a device to respond to it probe. (default 5s)
      --device-ttl duration                time-to-live for discovered devices in long-lived commands like the prometheus server. (default 5m0s)
      --discovery-concurrency int          number of concurrent  (default 5)
  -h, --help                               help for prometheus
      --host http                          host address of a single device. IP, DNS, or mDNS/BonJour addresses are accepted.
                                           If a URL scheme is provided, only http and `https` schemes are supported.
                                           mDNS names must be within the zone specified by the `--mdns-zone` flag (default `local`).
                                           URL formatted auth is supported (ex. `http://admin:password@1.2.3.4/`)
      --interactive                        if true prompt for confirmation or passwords.
      --mdns-interface string              if specified, search only the specified network interface for devices.
      --mdns-search                        if true, devices will be discovered via mDNS
      --mdns-service string                mDNS service to search (default "_shelly._tcp")
      --mdns-zone string                   mDNS zone to search (default "local")
      --prefer-ip-version 4                prefer ip version (4 or `6`)
      --probe-concurrency int              set the number of concurrent probes which will be made to service a metrics request. (default 10)
      --prometheus-namespace string        set the namespace string to use for prometheus metric names. (default "shelly")
      --prometheus-subsystem string        set the subsystem section of the prometheus metric names. (default "status")
      --scrape-duration-warning duration   sets the value for scrape duration warning. Scrapes which exceed this duration will log a warning generate. Default value 8s is 80% of the 10s default prometheus scrape_timeout. (default 8s)
      --search-interactive                 if true confirm devices discovered in search before proceeding with commands. Defers to --interactive if not explicitly set.
      --search-strict-timeout              ignore devices which have been found but completed their initial query within the search-timeout (default true)
      --search-timeout duration            timeout for devices to respond to the mDNS discovery query. (default 1s)
      --skip-failed-hosts                  continue with other hosts in the face errors.

Global Flags:
      --config string          path to config file. format will be determined by extension (.yaml, .json, .toml, .ini valid)
      --log-level string       threshold for outputing logs: trace, debug, info, warn, error, fatal, panic (default "warn")
  -o, --output-format string   desired output format: json, min-json, yaml, text, log (default "text")

RPC Command-line

Example

$ shellyctl switch set-config --ble-device=AA:BB:CC:DD:EE:FF --auto-off=true --auto-off-delay=60

Response to Switch.SetConfig command for ShellyPlugUS-AABBCCDDEEFF:
  Restart Required: false

$ shellyctl switch set --ble-device=AA:BB:CC:DD:EE:FF --on=true

Response to Switch.Set command for ShellyPlugUS-AABBCCDDEEFF:
  Was On: true

Updating Devices

Shelly devices support self-updates via the (Shelly.Update) RPC. This can be invoked on the command-line with shellyctl shelly update. Individual devices can be specified with the --host flag, or in bulk using mDNS (--mdns-search) or BLE (--ble-search) discovery. If no updates are available for the specified release stage, the Shelly devices appear to return error -114: Resource unavailable: No update info!; consider using the --skip-failed-hosts flag to continue in the face of this error.

shellyctl shelly update --stage=stable --skip-failed-hosts=true --mdns-search --interactive=false

Response to Shelly.Update command for http://192.168.1.28/rpc: success

7:31PM ERR error executing request; contining because --skip-failed-hosts=true error="RPC Bad Status -114: Resource unavailable: No update info!" component=discovery
 device_name=ShellyPro3-AABBCCDDEEFF instance=http://192.168.1.12:80/rpc request=Shelly.Update

Response to Shelly.Update command for http://192.168.1.29/rpc: success

Menu Heirarchy

• ble
  • get-config (BLE.GetConfig)
  • get-status (BLE.GetStatus)
  • set-config (BLE.SetConfig)
• cloud
  • get-config (Cloud.GetConfig)
  • get-status (Cloud.GetStatus)
  • set-config (Cloud.SetConfig)
• cover
  • calibrate (Cover.Calibrate)
  • close (Cover.Close)
  • get-config (Cover.GetConfig)
  • get-status (Cover.GetStatus)
  • go-to-position (Cover.GoToPosition)
  • open ([Cover.Open](https://shelly-api-