yfre
(eugen)
September 8, 2023, 2:46pm
7
yes, this is homekit specifics.
HomeKit home app does not send “Down” or “Up” commands, but always sends setPosition(percentage).
if your blinds do not support setPosition then you would need to write a rule to convert position to Down/Up + STOP
check these discussion for inspiration
It’s so frustrating …
I achieved the first goal, the blind is reacting to the Home App!
But so many things still don’t work … I was used to C++, not this
Can someone give me a hand? I have the following problems:
I need a variable as an argument for createTimer, but I can’t figure out the correct format!
I need a variable or something to remember the current percentage, but I don’t know how to do that elegantly. An option to set the initial value would be great!
I’m sure there are …
The counter has to start somewhere. Presumably it is a global variable? And it somehow maps to the current position of the shutter I’m assuming (e.g. if the shutter is 50% open the counter is 6).
With those assumptions:
This is a really dangerous implementation. It is a really bad idea to have long sleeps inside a Rule. You can only run 5 Rules at the same time. If something goes wrong or for some reason Arbeitszimmer_Rolladen changes a too much it will cause ALL your Rules to stop running un…
Hm, did it as proposed but the blind still moves based on calculated time when it receives the 0% or 100% command. Why the hell the rule doesn’t skip the calculation step in these two cases? Obviously there is still something wrong… Here’s the new rule again. Can someone find the “bug” in it?
val Number WZ_Rollo_01_100 = 30
var Number RolloTime_01
var Number RolloDifference = null
var String RolloDirection = null
var Timer timer = null
rule "WZ_Rollo_01_Alexa"
when
Item WZ_Rollo_01_Alex…