Hi,
I’ve been experimenting with some own build hardware for my rollershutters. So far I have a few rules to open and close them. However what I am not getting to work is driving them to an intermediate state.
According to my research it should be possible to send a value like 80 to them and then they will be set to 80% closed (or opened?)
Anyhow, when using
shutter_XYZ.sendCommand(80)
it is throwing an exception. It only accepts UP, DOWN, STOP as possible comands. Are there some sample rules how to implement this? Or does this need to be implemented by the hardware controller? I am using http during the development phase for now.
Thank you and best Regards,
SJ
one workaround could be using a stop watch 
use a rule:
shutter_XYZ.sendCommand(DOWN)
Thread::sleep(10000) // whereas 100000 is the milisecond time it should wait
shutter_XYZ.sendCommand(STOP)
cheers
Karsten
1 Like
Hi Karsten,
thank you. I saw this and sure that works. it this only stopping this particular thread or doing some harm to the whole system?
Thanks,
Steffen
no just the Thread. i use ist e.g in a rule like this one:
rule "React to sunset - ASTRO"
when
Item Twilight_Event received update ON
then
logInfo("Sunset","reacted on SUNSET_Event")
postUpdate(SunsetActivated, ON)
{
sendCommand(Shutter_OG_Flur_Sued, DOWN)
sendCommand(Shutter_OG_Flur_Ost, DOWN)
sendCommand(Shutter_EG_Ki_S, DOWN)
sendCommand(Shutter_EG_Ki_W, DOWN)
sendCommand(Shutter_EG_WZ_West_window, DOWN)
sendCommand(Shutter_EG_WZ_West_door, DOWN)
Thread::sleep(19000)
sendCommand(Shutter_EG_WZ_West_door, STOP)
}
end
which lets all shutters going down completly besides the Shutter_EG_WZ_West_door which stops after 19seconds.
all other rules run still as expected.
Cheers
Karsten