Stopping blinds movement
Posted: Tuesday 01 November 2016 11:32
I'd like to control my Blinds Percentage device with a remote control, but using the script api, as far as I can tell, only allows to open or close it fully. What would be the best approach to stop it halfway? Similar questions have been asked before here and here and apparently some remotes (somfy, z-wave remotes) can do it directly, circumventing domoticz. I'm using a cheap X10 RF remote (with RFLink).
The hardware is Fibaro FGRM-222. When I repeat an open or close command, unfortunately it is ignored or movement is reversed instead of stopped. The local switch does stop movement: if it is moving when you push either open or close it stops first, and you need to push again to resume or reverse movement. I'd like my remote control to work in the same way.
Probably I can get it to work by calling into ozwcp directly from a script (like this). I can use the 'native' open/close or inc/dec commands to stop movement, instead of the on/off commands exposed by domoticz. But I'd have to find a way to determine in my script if the screen is currently moving, perhaps by checking power usage? A more crude but hardware independent approach could be to mess around with timers, using periodic increments to keep the blinds moving, until a new signal is received that stops it but obviously this is inconvenient and probably not very precise/robust (cpu intensive).
Is there some kind of hidden feature, or future plans to achieve this in an elegant, reliable way?
The hardware is Fibaro FGRM-222. When I repeat an open or close command, unfortunately it is ignored or movement is reversed instead of stopped. The local switch does stop movement: if it is moving when you push either open or close it stops first, and you need to push again to resume or reverse movement. I'd like my remote control to work in the same way.
Probably I can get it to work by calling into ozwcp directly from a script (like this). I can use the 'native' open/close or inc/dec commands to stop movement, instead of the on/off commands exposed by domoticz. But I'd have to find a way to determine in my script if the screen is currently moving, perhaps by checking power usage? A more crude but hardware independent approach could be to mess around with timers, using periodic increments to keep the blinds moving, until a new signal is received that stops it but obviously this is inconvenient and probably not very precise/robust (cpu intensive).
Is there some kind of hidden feature, or future plans to achieve this in an elegant, reliable way?