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

mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-05-09 04:29:03 +00:00

mukundv 77d60c7325 Updated the sensor examples. (#3237 )

* Updated the sensor examples.

Corrected the sensor examples to include the updated attributes.

* Updated the attributes template

Changed the template to get the correct time_in_state and wifi_signal_strength

2017-08-25 10:38:30 +02:00

3.0 KiB

Raw Blame History

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

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

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
      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 }}'{% 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