Any way to hide the controls on MYQ cover?

Configuration Frontend
1

Hi All,

I’ve been using HA for about 3 days now so I’m still quite new to this environment.
I have a garage door opener connected to MYQ, which I have integrated into HA using this guide

I have it in a group (see groups.yaml snippet below) along with some other sensors for my alarm system (see pic)

I see the garage door opener in my view, but I want to replace the up/down arrows (which open/close the garage door) with just the status of the garage door (Open/Close)

My goal is to mount a tablet on the wall and afraid my 3 year old will open the garage door if the option is there.

This is what my view looks like now. I’m trying to replace the up/down arrows with Open/Closed or hide them.

57%20PM

Snippet of my configuration.yaml

####MY Q####
cover:
  - platform: myq
    username: !secret myq_username
    password: !secret myq_password
    type: chamberlain

Here is my groups.yaml

default_view:
 name: Main
 view: yes
 entities:
   - alarm_control_panel.alarm
   - group.alarm_sensors_view

alarm_sensors_view:
 name: Sensors
 control: hidden
 entities:
   - binary_sensor.backyard_door
   - binary_sensor.bedroom_windows
   - binary_sensor.den_windows
   - binary_sensor.front_door
   - binary_sensor.garage_entry
   - binary_sensor.kitchen_windows
   - cover.garage_door
2

Does cover.garage_door have a state? You can check in Dev States.

3

Yes. Open/closed/opening/closing

When you add cover.garage_door it creates the cover control

4

Then you can use cover.garage_door.state on the card.

5

Thanks for getting back!

I changed the groups.yaml file to this based on your recommendation:

default_view:
 name: Main
 view: yes
 entities:
   - alarm_control_panel.alarm
   - group.alarm_sensors_view

alarm_sensors_view:
 name: Sensors
 control: hidden
 entities:
   - binary_sensor.backyard_door
   - binary_sensor.bedroom_windows
   - binary_sensor.den_windows
   - binary_sensor.front_door
   - binary_sensor.garage_entry
   - binary_sensor.kitchen_windows
   - cover.garage_door.state

However, when I Check-Config, I get this error:

Invalid config for [group]: Entity ID cover.garage_door.state is an invalid entity id for dictionary value @ data['group']['alarm_sensors_view']['entities']. Got ['binary_sensor.backyard_door', 'binary_sensor.bedroom_windows', 'binary_sensor.den_windows', 'binary_sensor.front_door', 'binary_sensor.garage_entry', 'binary_sensor.kitchen_windows', 'cover.garage_door.state']. (See /config/configuration.yaml, line 35). Please check the docs at https://home-assistant.io/components/group/

If I change cover.garage_door.state back to cover.garage_door then Check-Config says Configuration is Valid.

Thank you again.

6

You will need to create a template sensor using cover.garage_door.state and then show the template sensor in the group.

7

No you can’t

image
image1011×467 21 KB

8

So are you using the old STATES UI?

9

Forgive me, I’m not familiar enough to know what the old or new STATES UI is. How can I find out to answer this question for you?

10

I
I figured you were familiar with the hardware since you said here that the stat is available.

11

You should be able to check what information is available here.

image

Down at the bottom of the left menu.

12

If you are using GROUPS to organize things, you appear to be using the STATES UI. That UI is going away at some point, and Lovelace is the current default. Are you on a current version?

I am. What does that have to do with anything? I have a MyQ garage door opener. I was just stating that when you add cover.garage_door to the frontend it adds it as a control, because it is a cover, and not a sensor.

You stated:

You cannot. You have to create a TEMPLATE sensor first from that state and use the TEMPLATE sensor. You cannot DIRECTLY access the state of the cover without creating a SENSOR.

What are you talking about?

image
image728×96 7.24 KB

OPEN
OPENING
CLOSING
CLOSED

Those are the states that it has.

13

If you use LOVELACE UI (the current default, and if you are running any recent version, it will be Lovelace unless you SPECIFICALLY changed it), you can add a GLANCES card, and add cover.garage_door to it. It will give you a STATE displayed, but clicking on it will give you the controls for it. It merely ‘hides’ the control of it inside another card, but doesn’t really remove the control completely.

1 Like
14

image

image

15

Hi,

The screenshot you sent is exactly what I’m looking for! Great to know it is possible!

I downloaded the latest hass.io image onto an sd card, and configured it on my RPI3. It is version 0.93.2- which looks like it is the latest version. I am running LOVELACE UI as I have not ‘taken control’ of the LOVELACE UI using the 3 dot option on the top right corner.

I will research the GLANCES option as you suggested. I only went the ‘groups.yaml’ because of some tutorial I found on how to organize my main view.

Thank you once again @flamingm0e!

16

I got it to work, thanks!
28%20PM

For anyone in the same boat, I had to click click on the 3 dots on the top right corner (advanced options I guess?) and select “Configure UI”. It gave me a warning that if I do that, Lovelace would not automatically add new entities. I clicked ‘Take Control’. From there there I clicked the + icon on the bottom right corner, and selected “Glance”, then after giving it a title, I specified my Entity to be my garage door and that was it.

17

I came across this thread while setting up my garage door. This is how to create the template sensor that @flamingm0e suggested.

in configuration.yaml

sensor:
  - platform: template
    sensors:
      garage_door_state:
        friendly_name: "Garage Door"
        value_template: "{{ states.cover.garage_door.state }}"
        icon_template: >-
          {% if is_state('cover.garage_door', 'closed') %}
            mdi:garage
          {% else %}
            mdi:garage-open
          {% endif %}

This is what the sensor looks like in an entities card:
image