@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?
-
"rollingTime" option for HomeduinoRFShutter
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@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 asthe approx. amount of time (in seconds) for shutter to close or open completely
. So when you saymoveByPercentage(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 callsstop()
.
Please explain more precise what you want to achieve.pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
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?pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
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.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
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.pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
@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 ofmovePosition()
in each device type supporting it. The function handles a timer to calling stop afterrollingTime
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."It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
- a device configuration flag like