home-assistant.io/cover.garadget.markdown at cadb541ebf526d291210c93cbed3e4dd80f393ff

mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-05-17 08:28:57 +00:00

Carlo Costanzo 04aa47785a Added in helpful tip (#1472 )

* Added in helpful tip

Excluding entries in logbook every 3 minutes.

* Update cover.garadget.markdown

2016-11-22 15:46:20 +01:00

3.0 KiB

Raw Blame History

layout, title, description, date, sidebar, comments, sharing, footer, logo, ha_category, ha_release

layout	title	description	date	sidebar	comments	sharing	footer	logo	ha_category	ha_release
page	Garadget Cover	Instructions how to integrate Garadget covers within Home Assistant.	2016-10-24 14:25	true	false	true	true	garadget_logo.jpg	Cover	0.32

The garadget cover platform lets you control Garadget garage door futurizers through Home Assistant.

To enable Garadget Covers in your installation, add the following to your configuration.yaml file:

# Example configuration.yaml entry
cover:
  platform: garadget
  covers:
      190028001947343412342341:
        username:  UseYourLogin@garadget.com
        password:  abc123
        name:  Left Garage Door
      4c003f001151353432134214:
        access_token: df4cc785ff818f2b01396c44142342fccdef

Configuration variables:

covers array (Required): List of your doors.
- device (Required): This is the device id from your Garadget portal.
- Either:
  - username (Required): Your Garadget account username.
  - password (Required): Your Garadget account password.
- Or:
  - access_token (Required): A generated access_token from your garadget account
- name (Optional): Name to use in the Frontend, will use name configured in Garadget otherwise.

If provided, the access_token will be used, otherwise the username and password will be used to automatically generate an access token at start time.

Example with more detail:

# Related configuration.yaml entry
cover:
  platform: garadget
  covers:
    190028001947343412342341:
      access_token: !secret garadget_access_token
      name:  Garage door

sensor:
  platform: template
  sensors:
    garage_door_status:
      friendly_name: 'State of the door'
      value_template: {% raw %}'{{ states.cover.garage_door.state }}'{% endraw %}
    garage_door_time_in_state:
      friendly_name: 'Since'
      value_template: {% raw %}'{{ states.cover.garage_door.attributes["time in state"] }}'{% endraw %}
    garage_door_wifi_signal_strength:
      friendly_name: 'WiFi strength'
      value_template: {% raw %}'{{ states.cover.garage_door.attributes["wifi signal strength (dB)"] }}'{% endraw %}
      unit_of_measurement: 'dB'

group:
  garage_door:
    name: Garage door
    entities:
      - cover.garage_door
      - sensor.garage_door_status
      - sensor.garage_door_time_in_state
      - sensor.garage_door_wifi_signal_strength

customize:
  sensor.garage_door_time_in_state:
    icon: mdi:timer-sand
  sensor.garage_door_wifi_signal_strength:
    icon: mdi:wifi

Some of the Garadget sensors can create a lot of clutter in the logbook. Use this section of code in your configuration.yaml to exclude those entries.

logbook:
  exclude:
    entities:
      - sensor.garage_door_time_in_state
      - sensor.garage_door_wifi_signal_strength

3.0 KiB Raw Blame History

3.0 KiB

Raw Blame History