WHY THE HECK can't we freely configure a Cover to interpret its percentage value as "percentage open" or "percentage closed"?

Once again thank you Marius!!!

I took your idea one step further and actually renamed my existing 5 entitity_id’s with _hidden and created templated ones with the original entity_id. My templates look like this:

      kitchen_blind_2:
        friendly_name: Kitchen 2
        value_template: >
            {%- if state_attr('cover.kitchen_blind_2_hidden','current_position')|int > 98 %}closed
            {% else %}open{% endif %}
        position_template: >
          {{100 - (state_attr('cover.kitchen_blind_2_hidden','current_position')|int)}}
        set_cover_position:
          service: cover.set_cover_position
          data_template:
            entity_id: cover.kitchen_blind_2_hidden
            position: >
              {{100 - position}}
        open_cover:
          service: cover.set_cover_position
          data_template:
            entity_id: cover.kitchen_blind_2_hidden
            position: >
              {{states("input_number.kitchen_blind_2")}}
        close_cover:
          service: cover.set_cover_position
          data_template:
            entity_id: cover.kitchen_blind_2_hidden
            position: 99

I have routines in Node Red which monitor the input_number presets for the open position which will call set_cover_postion with the new input_number value so they automatically adjust to the new desired position. The same could of course be done with automations…

2 Likes