(deprecated) Extensive roller shutter control including shading (brightness, sun position, temperature, forecast)

Blueprints Exchange
,
81

Works for me. :ok_hand: Thanks!

1 Like
82

@Eimeel :pray: :slight_smile:
many many thanks for this great blueprint.
I understand that you made it complete for your use cases and you are not going to extend it anymore. :slight_smile:

The good news is that your code is well structured and pretty easy to understand. And that helped me to apply some amendments which I needed:

  • variables for open_position and closed_position. In some rare cases I don’t want the shutter to close or open completely, e.g. to leave some space for the cat to enter via the door on the balcony :wink: Hence I introduced a closed_position, and set it to e.g. 44%
  • a variable position_tolerance which helps in case that the cover.set_position command doesn’t work exactly. e.g. it puts the shutter not exactly on 44% but on 45%. I applied the tolerance to the conditions that check the position of the shutter. at least my shutters need sometimes a tolerance of 1-2% :neutral_face:

Thanks again for this great and handy blueprint! :+1::+1:

83

@Lupo what is the erroneous change of the shutter? if it is a small variance of some percent you might consider introducing a ‘tolerance’ in the conditions.

                      - condition: template
                        value_template:
                          "{{ (state_attr(blind, 'current_position') | int(default=110) <= closed_position + position_tolerance)
                          and (state_attr(blind, 'current_position') | int(default=110) >= closed_position - position_tolerance)}}"

please notice in the code snippet that I’ve introduce variables for open_position and closed_position as well. and I set the default to 110 to avoid overlaps with tolerances

84

Thank you :slight_smile:

Well, we can add new functionality as long as it make sense and it is not bloating the code (which would make it very complicated to test).
I can add your changes if you like as they seems to make sense - and I guess your are not the only one who wants to define open and close positions :smiley:

1 Like
85

I would also love if you could add the suggestions by @nicknol. I also have the use cases of roller shutters that should not completely close (in my case kids that don’t want it too dark or bath room which shouldn’t be totally black at night).

If you don’t want to be involved here too much or feel like this is too much of a burden I could also put it in my github somewhere so others could collaborate (with proper attribution of course).

86

As you can see in the changelog we already implemented this enhancement :slight_smile:

2 Likes
87

My use case is rather simple - I want to automate driving up and down of my roller shutters just on sunset and sunrise while respecting time_up_early, time_up_early_workdays, etc. I don’t do any shading based on e.g. brightness / azimuth etc. stuff. Also used to do this with ASC on FHEM :wink:

Am I correct that simply driving up / down based on sunrise/sunset is not implemented? If it is implemented, could you point me on how to configure it?

88

You are right, it’s not implemented.
Feel free to take this blueprint as a template and adjust to your needs.

89

I forked this blueprint a long time ago because I also wanted to incorporate a few individual requests. Eimeel and I had a good and long conversation here.

My fork is mostly the logic of him. But of course I’m in the fortunate situation of not having to pay attention to backwards compatibility. So I renamed all variables. I also installed the sun control.

But there is a very important note: Since I have adopted a lot of logic, I have some procedures that I have not checked in detail myself. I had a lot of naive ideas. But Eimeel was always able to convince me that his approach make sense. He is much deeper into the matter. And I’m just playing around a little.

Currently I haven’t published my fork yet. But I can upload it tomorrow.

90

@Eimeel i have one conceptional question in setting up the automation.
coming from iobroker and using the adapter shuttercontrol i was used to work with groups (eg “Wohnbereich”, “Schlafbereich”…) which included several shutters.

Within each “group” i had the option to set auto_down auto_up sunprotect for each shutter which gave a lot flexibility.

I am now thinking how to set this up with your blueprint.

OPTIONS

  • 1 automation for each shutter (lot of administration work)
  • 1 automation for each shutter-goup (could only set auto_down auto_up sunprotect for whole group?)
  • other apporaches?

how do you use it for yourself?

BR, Johnny

91

Well, our house has 21 windows and I created 1 automation for every shutter :slight_smile: It is not that much work as you can copy an automation and adjust for every shutter.

But for sure you can create cover groups within Home Assistant and use 1 automation for every cover group.
Important: with my blueprint a cover group will be handled as if the group is one shutter. The group will not be split in several different shutters. Meaning if you e.g. create a cover group of two shutters and one shutter is at position 0 and the other one at position 100, the group will have position 50. If you define closing position as 0 (=default) and opening position (=100) nothing would happen here.

92

Consider me interested :slight_smile:

I still think a common project on e.g. github would make sense, I could also contribute a little. Maybe together we can develop a good ASC alternative for HomeAssistant :wink:

1 Like
93

I strongly suggest to start this using python script or creating an integration. An all-you-wish blueprint for shutter control is hell to debug.

But may I ask to discuss all this via PN or in another thread? Cause otherwise it will confuse people :slight_smile:

1 Like
94

I have a simple question:
I want to execute the blueprint, whcih is working fine, and after executing the blueprint send a notification to my phone.
How can I do that? I was thinking about listening to the event ‘automation_triggered’ and see if the blueprint got started. But how do I know when the blueprint has been executed? I want to start an automation when the blueprint has executed and send a notification.
How is that possible?

Thanks a lot !

95

Hi,
i would be interested in your blueprint, especially because of the sun control. Have you published it yet?

96

There appears to be a link to it in their post…

1 Like
97

@Eimeel i use the automation with groups which have multiple covers. if it closes/opens the shutters at “time up late” or “time up early” etc., all shutters are controlled at the same time. I want to send the open/close command for every shutter with a bit delay.

like:

        sequence:
          - repeat:
            for_each: "{{ expand(!input blind)|map(attribute='entity_id')|list }}"
            sequence:
              - delay: 00:00:{{ (range(1, 3)|random|int) }}
              - service: cover.open_cover
                data: {}
                target:
                  entity_id: "{{ repeat.item }}"
              - stop: Stop the automation

is it possible to include this feature?

98

If you create a full CR, yes, I can include it :slight_smile:
But this means not only the expanding part but also checking if there is a group or not. Don’t know if it’s easier to add a checkbox for this (e.g. “entity is a cover group”) or check it with code (which should be less error-prone).

99

What exactly do you want to achive? Just getting a notification “automation finished” or some more details?

But as the blueprint has some “dead ends” (aka parts which are just stopping the automation without any moving of the shutters) I guess just creating a notification after the automation finished won’t help you really.

Maybe it’s better for you to fork the blueprint and add “service: notify.notify” where ever you need.

100

ok. do you know how i can check if the entity is a group? perhaps with the attribute entity id greater than 1?