[OBSOLETE] Fibaro Roller Shutter 2 - FGRM-222 (DTH in post 24) (UK Device)

Do u know if it´s possibel to connect 2 shutters in 1 fibaro roller shutter? Tks!

Has anyone tried to use the Device Handler in the new SmartThings app? It doesn’t seem to be able to grab the device status. However in the old classic app, everything works fine.

1 Like

I finally take some time to fix the activation in scene. You can download the new code from

@julbmann
Is it possible to add support for the new module version 3 ?
There are different parameter numbers and i’m not sure if it will be stable using your version 2 DH.

I would be happy to do it but I don’t have a version 3 for now. I will have a look on documentation of version 3 and see if I can implement something but without any real testing.

1 Like

Thanks a lot .
Waiting for your update :slight_smile:

Hi
I’m also waiting for an update for shutter 3.
we are counting on you…
thanks a lot for all of your amazing work!!!

@julbmann
Did you look at the fibaro documentation already ?
It will help a lot if I will be able to change specifically parameter 20 which in version 3 is the switch type (default is 2 and I need to set it to 0 ).

Thanks again

you can try to use this new version here:

I only implement the parameter 20 and 151. But I didn’t test the code neither try to see if the code compile. So let me know if it works.

@julbmann
Thanks a lot .
I tried it with no success .
First I tried connected the module again and changing the current device type to your version 3 DH .
I changed the 20 parameter to 0 and 151 parameter to 1 pressed sync and refreshed but still
Only S1 button works (first up then down )
When I tried to use the ST fibaro thing from the app it didn’t do anything :frowning:
I Then tried to remove the device and pair it again . same results.
Then I tried to do factory reset to the device and pair it , same results.

I copied the live log :

1375baaa-b2e7-481c-91a8-7ed028028a4d 7:35:22 AM: debug other event SecurityMessageEncapsulation(secondFrame: false, commandIdentifier: 2, commandClassIdentifier: 50, commandByte: [33, 50, 0, 0, 0, 0, 0, 0], sequenceCounter: 0, sequenced: false, reserved13: 0)
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:35:22 AM: debug parse zw device: 04, command: 9881, payload: 00 32 02 21 32 00 00 00 00 00 00
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:35:11 AM: debug stop
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:34:24 AM: debug other event SecurityMessageEncapsulation(secondFrame: false, commandIdentifier: 2, commandClassIdentifier: 50, commandByte: [33, 50, 0, 0, 0, 0, 0, 0], sequenceCounter: 0, sequenced: false, reserved13: 0)
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:34:24 AM: debug parse zw device: 04, command: 9881, payload: 00 32 02 21 32 00 00 00 00 00 00
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:34:24 AM: debug parse zw device: 04, command: 9881, payload: 00 32 02 21 32 00 00 00 00 00 00
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:34:16 AM: debug refresh
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:34:16 AM: debug refresh
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:33:46 AM: debug stop
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:33:38 AM: debug send CMD: [200100, 2602]
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:33:38 AM: debug close
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:33:35 AM: debug other event SecurityMessageEncapsulation(secondFrame: false, commandIdentifier: 3, commandClassIdentifier: 32, commandByte: [254], sequenceCounter: 0, sequenced: false, reserved13: 0)
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:33:35 AM: debug parse zw device: 04, command: 9881, payload: 00 20 03 FE
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:33:24 AM: debug other event SecurityMessageEncapsulation(secondFrame: false, commandIdentifier: 2, commandClassIdentifier: 50, commandByte: [33, 50, 0, 0, 0, 0, 0, 0], sequenceCounter: 0, sequenced: false, reserved13: 0)
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:33:24 AM: debug parse zw device: 04, command: 9881, payload: 00 32 02 21 32 00 00 00 00 00 00
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:33:24 AM: debug parse zw device: 04, command: 9881, payload: 00 32 02 21 32 00 00 00 00 00 00
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:33:09 AM: debug other event SecurityMessageEncapsulation(secondFrame: false, commandIdentifier: 2, commandClassIdentifier: 50, commandByte: [33, 50, 0, 0, 0, 0, 0, 0], sequenceCounter: 0, sequenced: false, reserved13: 0)
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:33:09 AM: debug parse zw device: 04, command: 9881, payload: 00 32 02 21 32 00 00 00 00 00 00
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:33:05 AM: debug other event SecurityMessageEncapsulation(secondFrame: false, commandIdentifier: 2, commandClassIdentifier: 50, commandByte: [33, 50, 0, 0, 0, 0, 0, 0], sequenceCounter: 0, sequenced: false, reserved13: 0)
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:33:05 AM: debug parse zw device: 04, command: 9881, payload: 00 32 02 21 32 00 00 00 00 00 00
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:32:54 AM: debug Synced
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:32:41 AM: debug send cmds [7004970101, 700597, 7004140100, 700514]
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:32:41 AM: debug sync roller shutter
1375baaa-b2e7-481c-91a8-7ed028028a4d 7:32:41 AM: debug sync roller shutter

I attached the switch I’m using
When The module is not attached every button move up or down but when the module is connected then only S1 button (Left one) is active for both p and down .

It seems that the parameter didn’t change anything at the module .
How can I verify the value of a parameter in the module ?
I’m out of ideas :frowning:

Hi Alwas … could i ask what curtain motor you are using please? want to try something similar

Many thanks!

Sure, I know buying from Aliexpress can be quite bewildering with the choice they have, specifically I got this model…


It comes with either wall or ceiling mounts, I wrote to them to ask for both which they included. It doesn’t come with a physical switch, that I sourced locally to match what I had already. One neat feature is the motor can be mounted either on the left or right of the track, as required. I chose this regular 4 wire model instead of a fancy Aqara Zigbee model because I was sure I could get it to work with the Fibaro Roller Shutter. And strangely it only took 6 days to arrive, I must of pressed the wrong button at checkout.

@julbmann
I found something that may help
I still cannot operate my roller shutter :frowning:

Hi @zvika77,

I’m sorry but I think I won’t be able to debug this. I think they have changed how the controller work and so the device handler for model 2 does not work for model 3. So I think you will have to wait that someone write a device handler for this new roller shutter 3.

Sorry for that.

@julbmann
Ok. Thanks for trying .

People do you think that the module 3 are too much better than the 2? Which are the main differences?

Alwas Did you find a solution to the refresh issue where it’s only stating “opening” and “closing”?

D_Gjorgjievski Can you explain the ST routine you had?

I’m hoping to have this work. It was magically working fine but now it doesn’t refresh again…

That particular issue of perpetual “opening” and “closing” I mentioned 6 months ago was fixed very quickly by @julbmann, I do think these modules are particularly finicky though, you may need to factory reset the device. I did have a strange issue develop a month ago whereby I needed to press the physical toggle switch twice to get a reaction, I put a 5 second wait then refresh command with webCoRE to fix that, and last week I took the refresh command away and everything is back to normal!

1 Like

Perhaps I have an older code, I see the new one has a few small changes. Or I’ll try a reset, worst case I’ll ask you for a webcore guide :smile:

Thanks!

In ST I named all my roller shutters starting with “Shutter …”, then I made 2 routines in ST called “Open all shutters” and “Close all shutters” which are opening or closing all my shutters.
In google home I also used the same name of the devices, but I also made 2 routines “Open all shutters” and “Close all shutters” which have as action activation of the ST routine.
By doing this when I say “Open all shutters” or “Close all shutters” google home is activating the routine on ST.
Also I assume that because I use the name shutter; I dot see my roller shutters opening or closing when I order to google to turn on/of the lights and I didn’t notice such behaviour in the last 4 months I am using the functionality.