Skip to main content

Command-line tool for Home Assistant.

Project description

Home Assistant Command-line Interface (hass-cli)

Build Status Coveralls Chat Status License PyPI release

The Home Assistant Command-line interface (hass-cli) allows one to work with a local or a remote Home Assistant instance directly from the command-line.

hass-cli screencast

Note: This is still in alpha and under heavy development. Name and structure of commands are expected to still change.

Installation

To use latest release:

$ pip install homeassistant-cli

To use latest pre-release from dev branch:

$ pip install  pip3 install git+https://github.com/home-assistant/home-assistant-cli@dev

To get started you’ll need to have or generate a long lasting token format on your Home Assistant profile page (i.e. https://localhost:8123/profile).

Then you can use --server and --token paremeter on each call, or as is recommended setup HASS_SERVER and HASS_TOKEN environment variables.

$ export HASS_SERVER=https://hassio.local:8123
$ export HASS_TOKEN=<secret>

Once that is enabled and you are using either zsh or bash run the folowing to enable autocompletion for hass-cli commands.

$  source <(hass-cli completion zsh)

Usage

Note: Below is listed some of the features, make sure to use --help and autocompletion to learn more of the features as they become available.

Most commands returns a table version of what the Home Assistant API returns. For example to get basic info about your Home Assistant server you use info:

$ hass-cli  info
  BASE_URL                   LOCATION         REQUIRES_API_PASWORD  VERSION
  https://hassio.local:8123  Fort of Solitude False                 0.86.2

If you prefer yaml you can use –output=yaml:

$ hass-cli --output yaml info
  base_url: https://hassio.local:8123
  location_name: Wayne Manor
  requires_api_password: false
  version: 0.86.2

To get list of entities you can use entity list:

$ hass-cli entity list
ENTITY                                                     DESCRIPTION                                     STATE
zone.school                                                School                                          zoning
zone.home                                                  Andersens                                       zoning
sun.sun                                                    Sun                                             below_horizon
camera.babymonitor                                         babymonitor                                     idle
timer.timer_office_lights                                                                                  idle
timer.timer_small_bathroom                                                                                 idle
group.kitchen_lights                                       Kitchen Lights                                  off
binary_sensor.presence_basement_combined                   Basement Motion Anywhere                        off
sensor.yr_symbol                                           yr Symbol                                       4
group.basement_lights                                      Basement Lights                                 unknown
sensor.packages_delivered                                  Packages Delivered                              1
sensor.packages_in_transit                                 Packages In Transit                             1
sensor.ring_front_door_last_ding                           Front Door Last Ding                            14:08
sensor.ring_front_door_battery                             Front Door Battery                              52
...

You can use --no-headers to suppress the header.

--table-format let you select which table format you want. Default is simple but you can use any of the formats supported by https://pypi-hypernode.com/project/tabulate/: plain, simple, github, grid, fancy_grid, pipe, orgtbl, rst, mediawiki, html, latex, latex_raw, latex_booktabs or tsv

Finally, you can also via --columns control which data you want shown. Each column has a name and a jsonpath. The default setup for entities are:

--columns=ENTITY=entity_id,DESCRIPTION=attributes.friendly_name,STATE=state,CHANGED=last_changed

If you for example just wanted the name and all attributes you could do:

hass-cli --columns=ENTITY="entity_id,ATTRIBUTES=attributes[*]" entity list zone
ENTITY             ATTRIBUTES
zone.school        {'friendly_name': 'School', 'hidden': True, 'icon': 'mdi:school', 'latitude': 7.011023, 'longitude': 16.858151, 'radius': 50.0}
zone.unnamed_zone  {'friendly_name': 'Unnamed zone', 'hidden': True, 'icon': 'mdi:home', 'latitude': 37.006476, 'longitude': 2.861699, 'radius': 50.0}
zone.home          {'friendly_name': 'Andersens', 'hidden': True, 'icon': 'mdi:home', 'latitude': 27.006476, 'longitude': 7.861699, 'radius': 100}

You can more details of an entity easily by using yaml or json output format. In this example we use the shorthand of output: -o:

$ hass-cli -o yaml entity get light.guestroom_light                                                                                                                                                                       
attributes:
  friendly_name: Guestroom Light
  supported_features: 61
context:
  id: 84d52fe306ec4895948b546b492702a4
  user_id: null
entity_id: light.guestroom_light
last_changed: '2018-12-10T18:33:51.883238+00:00'
last_updated: '2018-12-10T18:33:51.883238+00:00'
state: 'off'

You can edit state via an editor:

$ hass-cli entity edit light.guestroom_light

This will open the current state in your favorite editor and any changes you save will be used for an update.

You can also explicitly create/edit via the –json flag:

$ hass-cli entity edit sensor.test --json='{ "state":"off"}'

List posible service with or without a regular expression filter:

$ hass-cli service list 'home.*toggle'
  DOMAIN         SERVICE    DESCRIPTION
  homeassistant  toggle     Generic service to toggle devices on/off...

For more details the yaml format is useful:

$ hass-cli -o yaml service list homeassistant.toggle
homeassistant:
  services:
    toggle:
      description: Generic service to toggle devices on/off under any domain. Same
        usage as the light.turn_on, switch.turn_on, etc. services.
      fields:
        entity_id:
          description: The entity_id of the device to toggle on/off.
          example: light.living_room

You can get history about one or more entities, here getting state changes for the last 50 minutes:

$ hass-cli entity history --since 50m light.kitchen_light_1 binary_sensor.presence_kitchen
  ENTITY                          DESCRIPTION      STATE    CHANGED
  binary_sensor.presence_kitchen  Kitchen Motion   off      2019-01-27T23:19:55.322474+00:00
  binary_sensor.presence_kitchen  Kitchen Motion   on       2019-01-27T23:21:44.015071+00:00
  binary_sensor.presence_kitchen  Kitchen Motion   off      2019-01-27T23:22:02.330566+00:00
  light.kitchen_light_1           Kitchen Light 1  on       2019-01-27T23:19:55.322474+00:00
  light.kitchen_light_1           Kitchen Light 1  off      2019-01-27T23:36:45.254266+00:00

The data is sorted by default as Home Assistant returns it, thus for history it is useful to sort by a property:

$ hass-cli --sort-by last_changed entity history --since 50m  light.kitchen_light_1 binary_sensor.presence_kitchen
ENTITY                          DESCRIPTION      STATE    CHANGED
binary_sensor.presence_kitchen  Kitchen Motion   off      2019-01-27T23:18:00.717611+00:00
light.kitchen_light_1           Kitchen Light 1  on       2019-01-27T23:18:00.717611+00:00
binary_sensor.presence_kitchen  Kitchen Motion   on       2019-01-27T23:18:12.135015+00:00
binary_sensor.presence_kitchen  Kitchen Motion   off      2019-01-27T23:18:30.417064+00:00
light.kitchen_light_1           Kitchen Light 1  off      2019-01-27T23:36:45.254266+00:00

Note: the –sort-by argument is referring to the attribute in the underlying json/yaml NOT the column name. The advantage for this is that it can be used for sorting on any property even if not included in the default output.

You can call services:

$ hass-cli service call deconz.device_refresh

With arguments:

$ hass-cli service call homeassistant.toggle --arguments entity_id=light.office_light

Open a map for your Home Assistant location:

$ hass-cli map

Render templates server side:

$ hass-cli template motionlight.yaml.j2 motiondata.yaml

Render templates client (local) side:

$ hass-cli template --local lovelace-template.yaml

Auto-completion

As described above you can use source <(hass-cli completion zsh) to quickly and easy enable auto completion. If you do it from your .bashrc or .zshrc its recommend to use the form below as that does not trigger a run of hass-cli itself.

For zsh:

eval "$(_HASS_CLI_COMPLETE=source_zsh hass-cli)"

For bash:

eval "$(_FOO_BAR_COMPLETE=source foo-bar)"

Once enabled there is autocompletion for commands and for certain attributes like entities:

$ hass-cli entity get light.<TAB>                                                                                                                                                                      
light.kitchen_light_5          light.office_light             light.basement_light_4         light.basement_light_9         light.dinner_table_light_4     light.winter_garden_light_2    light.kitchen_light_2
light.kitchen_table_light_1    light.hallroom_light_2         light.basement_light_5         light.basement_light_10        light.dinner_table_wall_light  light.winter_garden_light_4    light.kitchen_table_light_2
light.kitchen_light_1          light.hallroom_light_1         light.basement_light_6         light.small_bathroom_light     light.dinner_table_light_5     light.winter_garden_light_3    light.kitchen_light_4
light.kitchen_light_6          light.basement_light_1         light.basement_light_7         light.dinner_table_light_1     light.dinner_table_light_6     light.hallroom_light_4
light.guestroom_light          light.basement_light_stairs    light.basement_light_2         light.hallroom_light_5         light.dinner_table_light_3     light.winter_garden_light_5
light.hallroom_light_3         light.basement_light_3         light.basement_light_8         light.dinner_table_light_2     light.winter_garden_light_1    light.kitchen_light_3

Note: For this to work you’ll need to have setup the following environment variables if your home-assistant is secured and not running on localhost:8123:

export HASS_SERVER=https://hassio.local:8123
export HASS_TOKEN=<Bearer token from HASS_SERVER/profile>

Help

Usage: hass-cli [OPTIONS] COMMAND [ARGS]...

  Command line interface for Home Assistant.

Options:
  -l, --loglevel LVL              Either CRITICAL, ERROR, WARNING, INFO or
                                  DEBUG
  --version                       Show the version and exit.
  -s, --server TEXT               The server URL or `auto` for automatic
                                  detection  [default: auto]
  --token TEXT                    The Bearer token for Home Assistant
                                  instance.
  --password TEXT                 The API password for Home Assistant
                                  instance.
  --timeout INTEGER               Timeout for network operations.  [default:
                                  5]
  -o, --output [json|yaml|table]  Output format  [default: json]
  -v, --verbose                   Enables verbose mode.
  -x                              Print backtraces when exception occurs.
  --cert TEXT                     Path to client certificate file (.pem) to
                                  use when connecting.
  --insecure                      Ignore SSL Certificates. Allow to connect to
                                  servers with self-signed certificates. Be
                                  careful!
  --debug                         Enables debug mode.
  --columns TEXT                  Custom columns key=value list. Example:
                                  ENTITY=entity_name,
                                  NAME=attributes.friendly_name
  --no-headers                    When printing tables don't use headers
                                  (default: print headers)
  --table-format TEXT             Which table format to use.
  --version                       Show the version and exit.
  --help                          Show this message and exit.

Commands:
  completion  Output shell completion code for the specified shell (bash or...
  config      Get configuration from Home Assistant.
  discover    Discovery for the local network.
  entity      Get info and operate on entities from Home Assistant.
  event       Interact with events.
  info        Get basic info from Home Assistant.
  map         Print the current location on a map.
  raw         Call the raw API (advanced).
  service     Call and work with services.
  system      System details and operations for Home Assistant.
  template    Render templates on server or locally.

Clone the git repository and

$ pip3 install --editable .

Development

Developing is (re)using as much as possible from homeassistant development setup <https://developers.home-assistant.io/docs/en/development_environment.html>.

Recommended way to develop is to use virtual environment to ensure isolation from rest of your system using the following steps:

$ python3 -m venv .
$ source bin/activate
$ script/setup

after this you should be able to edit the source code and running hass-cli directly:

$ hass-cli

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

homeassistant-cli-0.4.4.tar.gz (47.1 kB view details)

Uploaded Source

Built Distribution

homeassistant_cli-0.4.4-py3-none-any.whl (38.0 kB view details)

Uploaded Python 3

File details

Details for the file homeassistant-cli-0.4.4.tar.gz.

File metadata

  • Download URL: homeassistant-cli-0.4.4.tar.gz
  • Upload date:
  • Size: 47.1 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.9.0 tqdm/4.30.0 CPython/3.7.2

File hashes

Hashes for homeassistant-cli-0.4.4.tar.gz
Algorithm Hash digest
SHA256 ad3722062ffb7b4fa730f61991b831dbf083e4e079c560993a023ce4bb11c55d
MD5 2f7192565fecf6ff9f1fece555dd52d6
BLAKE2b-256 cd96d2006047f59ee27020365c2b0c673471dcfc585d81119281c228ae4d0a79

See more details on using hashes here.

File details

Details for the file homeassistant_cli-0.4.4-py3-none-any.whl.

File metadata

  • Download URL: homeassistant_cli-0.4.4-py3-none-any.whl
  • Upload date:
  • Size: 38.0 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.9.0 tqdm/4.30.0 CPython/3.7.2

File hashes

Hashes for homeassistant_cli-0.4.4-py3-none-any.whl
Algorithm Hash digest
SHA256 d9fab9fe20d4bc3872fdae12be06a94074cfeb4ab3d110815d5486b1b3dd34a5
MD5 2c742d1c38338087b1b7742fad4ca847
BLAKE2b-256 bd9a5587cf1af195733385c9efd6ebe447d9f32dbb41c6273c2d46812d8b80af

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page