"rollingTime" option for HomeduinoRFShutter

---

Hi,
I was wondering, why the HomeduinoRFShutter device has no rollingTime option how the DummyShutter has.

Just wondered about the same thing and found your post. Would be nice if the buttons reset after some time and don’t stay in the last position.

Just upvote https://github.com/pimatic/pimatic-homeduino/pull/87

Moved thread to Feature Request. Upvote on the first post of you fancy this feature

@mwittig Why is it really needed that somebody upvotes this? The pull request already exists quite a time. Somebody (maybe you?) just needs to merge it.

@michbeck100 said in "rollingTime" option for HomeduinoRFShutter:

Why is it really needed that somebody upvotes this?

Simply because that is the agreed process for new features. Note not all users are familiar with github and what upvoting a PR is about.

Hi, I really like to have this feature. It would save 26 rules for me. I think many users would love it, but not everybody is voting it.

Well, I finally found out how to upvote…

Btw: is there an option to find out, if the (dummy-)shutter is UP or DOWN or read the percentage respectively? Otherwise that would also be a feature that would need implemented to make it work properly for me.

After this feature has finally found its way into the official version, I would like to ask for a small functional improvement.
My idea is that the shutter will stop automatically after the set scrolling time. With this small improvement the UI keys (up/down) would be released by the device itself. Currently I handle this with a separate rule for each shutter device and have many windows .
I can try to do it myself, but I’m to stupid to get the right place in the code.

@ortin Can you please post the rule you current have set up to get the desired functionality? Looking at the code I don’t understand exactly how rollingTime appies. Do you call “moveByPercentage” at some point?

@mwittig Currently moveByPercentage can only be called via REST api, cause there is no UI for this, yet.

@OrTiN I’m not sure if I understand you correct.
The rolling time is defined as the approx. amount of time (in seconds) for shutter to close or open completely. So when you say moveByPercentage(50) and the rolling time is set to 20 seconds, then the shutter opens or closes and after 10 seconds (which is 50% of 20 seconds) it calls stop().
Please explain more precise what you want to achieve.

Okay, I understand. The rolling time is only related to move in percent.
What I am looking for is a possibility to execute a stop command after manually (by UI) move a shutter (up/down) to avoid a permanent pressed button on the UI. Shortly if rolling time is 20, then the button (up/down) should be released after 20 seconds (100%). Perfectly would be a seperate runtime for up and down but this will bite the current concept.

Currently I have rules for each shutter like this for UP:

when position of jalousiemodul-wz is up then stop jalousiemodul-wz after 30000 ms

and a seperate one for DOWN:

when position of jalousiemodul-wz is down then stop jalousiemodul-wz after 18000 ms

The idea is that the shutter gets completely opened when I want to move it up, but it should not close completely when I move them down.

Why so quiet, still not clear?

@ortin No, not really clear. I’m wondering if you are using the new feature moveByPercentage at all? I don’t understand what this has to do with the feature?

Hi,
No I am not using the moveByPercentage feature. But with the plugin update which provides this new feature the rollingTime found its way to the homeduine shutterDevice config.
Once more my problem. When I press a rolling button on the UI the button stays in this mode always:
It will not be released automatically.

For this I create a rule for each shutterDevice to get the buttons released.
Example:
when position of jalousiemodul-wz is up then stop jalousiemodul-wz after 30000 ms
This kind of rule ensures that the button gets released and stops the shutter after 30 seconds in case of the UP button of jalousiemodul-wz was pressed.

My idea is to use the provided parameter rollingTime to send a stop command after the rollingTime ends (starting from the manual press action on the UI).

To clarify this, if a roller shutters is operated by a rule, e.g. to drive up in the morning or down in the evening, the corresponding button is released at the end of the specified time (see rule -> after 30000 ms). The rollingTime function or the moveByPercentage feature is not necessary for this. This works since years.

I hope now its more clear to you. Otherwise my english seems to be too bad to express my idea.

@ortin Now I got it! Please create a feature request in the pimatic project: https://github.com/pimatic/pimatic/issues

I think this could be done easily.

One thing I mentioned before but I think it was not considered. My shutter need more time to open as to close. My wish would be to have a separate rollingTime for UP and an other time for DOWN.

@ortin I‘m sorry to say that but I don’t think it makes sense to add another rolling time value as this makes it even more confusing.
You could create your own custom plugin that „listens“ to the movement of your shutters and call stop then.
That should be pretty easy. See pimatic-echo or pimatic-hap for examples how to implement such plugins that react on events.
Alternatively you could also change the pimatic code itself, as this would be a change of the core in my opinion.

@ortin said in "rollingTime" option for HomeduinoRFShutter:

rollingTime

If I understand this correctly the following will do:

• a device configuration flag like topOnRollingTime
• a stopAfterRollingTime() function which needs to be called as part of movePosition() in each device type supporting it. The function handles a timer to calling stop after rollingTime has reached.

It might also be possible to make to generalize the feature by implementing as part of _setPosition(). However, I am not yet sure about the implication this may have.