I've bought and correctly installed a fibaro roller shutter 3. I've installed the custom driver found here in the forum.
Everything works inside the device page, but I've a problem within a rule. I'm not able to send a stop command.
I explain it better: I've a device with a set of buttons. I've planned to use two of them to control the curtains. Push and release opens/closes them. But, hold allows to control how much the curtains are open/closed. The rules works correctly, except for the fact that the command to stop the movement (started before) is totally ignored. Hence, whenever the close/open commands are sent, the curtains move up to the end point.
The rule is right, because it resets the value of a variable that informs is the buttons are hold or just pushed.
I am not sure why your rules does not stop the movement but are you sure all device parameters (Fibaro for-223 parameters) configured to support your buttons?
There are parameters that specify what kind of switch you are using.
Also, why not use the button controller app which looks more suitable for this scenario?
Normally yes. I've tried all the commands in the device and they work.
The only one that looks doing nothing, is the 'start position change' with parameters open or close. But, actually, given that I don't know what it should do, I suppose I'll not need it.
What's strange, the fibaro device to control the curtains has 4 children devices: a button controller; 2 buttons; a temperature sensor. The first 3 offer some commands, but they're ignored if fired. The temperature is useless, it shows always 20 degrees.
About the button controller, I've to say that I've not thought about it. I've also didn't know about it.
Now I try to configure one.
I have never used for-223 with buttons, only toggle and momentary switch. Never saw child devices for this device as well. Can you please attach a screenshot?
It's just the default name that is given to it. Anyway, as device is set Fibaro FGR-223.
Anyway, when it's recognized, it's a smart implant with some sub-devices. This I can't change.
Solved by using the 'Custom Action' and from there sending the command to 'stop' the movement of the curtains.
It's anyway strage, because it looks exactly the same command. Maybe it's a bug in the driver (but it works, so I suppose not) or in the way the Rule interacts with it (this could be).
