forum

Hi guys,

i am using FGRM-222 for a at least 10 roller shutters in my house. now i extended the installation and i bought additionally 3 roller shutters. nowadays they called FGR-222 (without M) and they have a little bit different casing and a new firmware. find more here: http://manuals.fibaro.com/roller-shutter-2/

now my question/problem.

these FGR-222 wont work as multilevel switches. i can see the option in z-way to set a value between 0-99 but if i enter e.g. 50% the roller shutter drives round about a second and then drives back to previous position.

does someone has an idea?
thanks for help.

dk00000

HI!

I can't help but I experience exactly the same behaviour with the FGR-222.
But I noticed something strange: In Expert UI or via html request i can set the exact position without any problems. So it seems to be a Problem in the Smarthome UI.
I hope anybody can help us!

I have the same problems with Version 2.2.1 and FGR 222.
Also i have Problems to close the shutter with value 0 in some apps.
The scheduler app sets the value to 99 in the morning, mostly that works ok and the shutter opening.
But i use a logical app and after that a condition switch to check the solar altitude, when the vlaue is smaller than 5 i set the value from to shutter to "0". This option doens't work, Sinde 5 days i habe noch rule that closed the shutter in the evening.
When i use the Up/Down Button in Smarthome UI thats work perfectly, but not Level "0".

In the expert UI i can set the value to "0" and it works.

Very crazy.

Did you find a solution for this problem?

I have additionally the problem that I want to set the angle of the laminate of the blind. There are controls in Z-way I think (Circle and four buttons) but the blinds move for a second and then move back to the point where they started from.

I can move the blinds completely up and down without any problem.

Hi all together!

Any solutions found?? !

Hi,

i think this is an issue with the control element on the dashboard.
If i choose some value e.g. 50, then the blind moves.
Now the dashboard element receives a new value from the blind (e.g. 28), which is the current position.
After that, the blind wants to move to the new value (28), so the engine stop and moves in the other direction.
a second later, the interface reads the new value (e.g. 35) and the blind drives to 35... and so on...

But i have no idea to solve this...

maybe someone from the admin / development team can help???

Just updated to Firmware Version 2.2.5, now i can use the interface and can control the blinds as excepted.
Currently, there is no changelog available.

Can someone confirm this?