Support for shutter percentage

---

I’d like to add support for using percentage values for the ShutterController to move the shutter to a certain point and stop automatically. This is helpful for rules like

if temperature of outside is more than 35°C for more than 5 minutes then move the shutter 50%

This would move up the shutter to 50% of the complete window size. Note that the ShutterController is still stateless, so it’s up to the user to use useful percentage values.
To calculate the time, when the shutter should stop, a config value for the time, that an open shutter needs to completely close, is needed.
For example, if the shutter takes 20 secs to close when completely open, a percentage of 50% would mean that the shutter runs for 10 secs and then stops.
The percentages can be between -100 and +100. A negative value means moving down, positive means moving up.

I actually already finished the implementation for pimatic itself and added a pull request (https://github.com/pimatic/pimatic/pull/920).

Please upvote this feature request, because no one did react on my pull request yet.

Also somebody would have to extend the mobile frontend. Currently you can set the percentage just by using the REST interface.

i’ve already seen this on git before and just informed the @pimatic-team to have a closer look.
thx for your efforts!!

@michbeck100
Don’t know if you have seen sweetpi’s request on your pull to reopen it on v0.9 since we moved today.

@leader21 I’ve seen it. And i’m working on it.

Thx a lot !

currently i´m using rules to move the shutter down/up like:

if it is 19.31 or [rolladen-stellung is pressed and position of Kind Rolladen 2 equals "up"] then raise kind_rolladen2 and after 20 seconds lower kind_rolladen2 and after 36,4 seconds stop kind_rolladen2

Here I´m moving everthing UP to be sure to have the max. position of the shutter, after that i lower it to a spcific position within an time limit. This works for over a year now.
But it would be nice to set it by percentage

@hyperx The you might be the first to test this new feature . I did just write unit tests, since i don’t own automatic shutters, yet. But you must wait until the ActionProvider for this is implemented. It’s still missing. @developer anyone interested?

is there any news on that ? ive seen the codes have bin merged, but when it will be ready for test ? im very interesting of that feature.

Thanks

@p4co86 Released. Please report issues you may find on this thread. Thanks

@mwittig thanks, have uopdatet it but can not create a rule like

@michbeck100 could you give an example for the rest api call to set the shutter to 50%

Then move the wohnzimmer to 50%

it just says

Then move the wohnzimmer up/down

Thanks

got it myself.

100% up

USERNAME:PASSWORD@PIMATICIP/api/device/wohnzimmer_links/moveByPercentage?percentage=100

100% down

USERNAME:PASSWORD@PIMATICIP/api/device/wohnzimmer_links/moveByPercentage?percentage=-100

It would be awesome to add a actionprovider for the rules, because i will use a variable input to change the percantage and then press the relevant shutter.

isn`t it better to say from 0-100% instead of -100-100% ? i think 50% is more clear that its the half then 0%!

THANK YOU VERY MUCH !

@p4co86 If I used 0-100% pimatic would need to know where the shutter currently is, to know if e. g. 30% means up or down.
That’s why I decided to use negative values, too. This way it’s up to the user to know where the shutter is.
I think it’s impossible for pimatic to track the current position correctly. And once it’s wrong, the shutter will behave strange depending what pimatic thinks where it currently is.

@developer could someone please add this to the action handler so we can use this in rules. This would be awesome. I will test this with variables in rules.
Thank you

@sweetpi Is there any chance that you could update the shutter action provider so that its possible to define an action like

raise shutter up 50%

where the percentage may be negative, too.
I tried it myself, but i’m got lost in the pattern matcher code. Looking at the commit history it seems that you are the right person.

i see that there is a discussion and pull request on git on that.
is your above question still up to date @michbeck100 ?

@leader21 Yes it is. The only change i did, was the actual implementation of a new function that moves a shutter by a certain percentage value (see https://github.com/michbeck100/pimatic/commit/cfe193a3fde822c462a4d173d2fdcaf1b1870652 and https://github.com/michbeck100/pimatic/commit/14444ecc410deeff469d3fb824cbef6afc2f2a0a).

But there’s currently nothing that can actually call this new function apart from the REST api. I would say extending the action provider makes really sense, because there are plenty of rules that come to my mind, that would benefit from this feature, like

when sun shines then lower shutter 50%

@leader21 Did you have a look on the implementation?

sorry! have to pass through to @mwittig