Cover Hook about awesome-ha-blueprints

[EPMatt]

Hi @thehijacker,

I've just added the Cover Hook to the collection. 🎉

Unfortunately I'm not able to test this blueprint by myself so I'd like to ask your help.
Would you please test this on your instance and see if everything is working as expected?

Also, please let me know if the actions mapping for your controllers are good for controlling a cover. If you want to suggest a different mapping between the controller and the Cover control, which might be more user friendly, I'd be happy to hear your voice. :)

Thank you!

[thehijacker]

Hello,

I will test this as soon as I can. In the mean time I kind of redesigned all in my mind. With single 5 button switch I plan to control two shutters. No sure how this will turn out. Need to take it easy so it works at end of WAF will got down again.

Thank you!

Best regards,
Andrej

[EPMatt]

You're welcome @thehijacker!

With single 5 button switch I plan to control two shutters.

That's interesting, we could also provide a special action mapping for the IKEA E1524 which would allow to control two covers with a single controller (Or also provide two different mappings: for example, one which uses the up/down buttons, and the other which uses the left/right buttons).

Have a nice weekend :)

[thehijacker]

Checked your hook. Looks great for specific covers. Mine does not know how to do tilt by command. I need to stop it when moving up/down and change position up/down by around 5 to move it opposite way and "tilt".

Still brainstorming this in my mind. Currently I use single button to move one cover up/down by step. I created new input_number with each cover desired strep and I increase/decrease this by left/right single press to move cover down and left/right long press to move up. Example for left cover movement.

      action_left_short:
      - service: input_number.decrement
        target:
          entity_id: input_number.left_shutter_desired_position
      - service: cover.set_cover_position
        target:
          entity_id: cover.left_shutter_mqtt
        data_template:
          position: '{{ states(''input_number.left_shutter_desired_position'') | int
            }}'
      action_left_long:
      - service: input_number.increment
        target:
          entity_id: input_number.right_shutter_desired_position
      - service: cover.set_cover_position
        target:
          entity_id: cover.right_shutter_mqtt
        data_template:
          position: '{{ states(''input_number.right_shutter_desired_position'') |
            int }}'

But now I have different idea. To use left right only to select which one to "manage".

1. Single left press will change input_text to left cover entity. Single right press will change input_text to right cover entity.
2. With single up and down I would increment/decrement value for currently specific cover by step value. So if I wish to quickly move cover to 50% and if step value is 10 I would need to press single up/down 5 times. Doesn't sound quick unless I disable double clicking. Possible?
3. If I hold up/down it would move the cover to fully up/down.
4. If at any time I press middle button it will stop moving where it is.

How does this sound. Open for better ideas. :)

[EPMatt]

Hi @thehijacker, really interesting ideas! 👍🏻

In the script you attached here, you are saving the current cover state to an input_number, am I right?

But now I have different idea. To use left right only to select which one to "manage".

That's a nice point. I think this might be a little bit complex for users of the Hook, since many of them might only be interested in using a single cover, but in my opinion it's a very interesting idea to get the most from a single 5-button remote.

With single up and down I would increment/decrement value for currently specific cover by step value. So if I wish to quickly move cover to 50% and if step value is 10 I would need to press single up/down 5 times. Doesn't sound quick unless I disable double clicking. Possible?

Cool, yes you can disable double clicks in the Controller blueprint, to make the whole automation a little faster, since it hasn't to wait for the second short press. :)

3 and 4 sounds really nice to me. I'd implement 3 with double clicks, but in your situation that might conflict with your second point, where you need speed.

By the way, since not all covers provide the tilting feature, we could implement a different mapping for each controller, which could be used with this type of covers, so the Hook could better adapt to each user's different needs.