Haha that’s great! I’m glad it’s working, I’m not a genius though, hone assistant is just really great to work with.
I have no idea about question 2, as I have no covers in my set up. I can guess at question 1… I don’t think there’s a simple way to do it. I feel like there should be an action in an automation that can change the friendly name, but I don’t think that exists. So there’s 2 options. Option 1 is easier but probably doesn’t work:
friendly_name: ‘{% if is_state(“sensor.left_garage_status”, “closed”) %}Garage Door Left Closed{% else %}Garage Door Left Open{% endif %}’
OR
friendly_name_template: ‘{% if is_state(“sensor.left_garage_status”, “closed”) %}Garage Door Left Closed{% else %}Garage Door Left Open{% endif %}’
I don’t think that’s supported, but it would be a nice solution.
Option 2 is very complicated and relies on having double entities in different groups. Groups have a set_visibility action, so it is possible to show and hide these dynamically. For example you set up the entities: garage_doorleft_new_open, garage_doorleft_new_closed, garage_doorright_new_open, garage_doorright_new_closed
. The closed and open are identical to each other, except you have a different friendly name. Then you put them into individual groups. To finish it off, you need a set of automations… Either 2 (with a bunch of if statements, or 4 simple automations).
I’m on mobile so I don’t want to type all the code, but the automation should do the following: when the left sensor changes from open to closed, set the visibility of the left open group to hidden and set the visibility of the left closed group to visible. So you’re replacing the entity in your interface with a new one that’s identical but with a different name! You’ll need the other 3 of those automations (left door closed to open, right door open to closed, right door closed to open).
So that’s a pretty ridiculous solution. It would be good if option 1 works, if not I’ll make a feature request.