Fibaro FGR-222 EU2.5 XML needed

[djandibParticipant]

Hi,
today I got the new Rollo Shutter FGR-222 EU 2.5
It`s the new one (former was FGRM-222 2.4)
I already have installed 4 old ones working correctly.
The new FGR-222 knows only 2 positions (0 or 99).
I looked in the manufacturer_specific.xml and saw, that I don`t have a fgr-222.xml
Where can I get this one?
Or do you have any Ideas, why it does not work?

Thanx
Andi

[coldbringerParticipant]

Hey Andi,

the new 2.5 version works with the old fgrm222.xml file – but the link is missing. Add the following line in the Fibaro section of the manufacturer_specific.xml (somewhere around line 300):

<Product type=”0302″ id=”1000″ name=”FGRM222 Roller Shutter Controller 2″ config=”fibaro/fgrm222.xml”/>

Should work fine.

Cheers
Carlos

[djandibParticipant]

Hi Carlos,
thanx for support.
Unfortunately problem is still the same.
Only 2 postitions are known…

If I try to make autocalibration the shutter works in a loop…. up-down-up-down-up-down.
I can stop only by pressing S1 and S2 the same time….

Pressing B-Button blue and a short pressing again makes the same (wrong?) calibration.
Auto-Calibration with pulsestation makes the same (wrong?) calibration.

I already delete the shutter eprom some times (B-Button yellow and short pressing again), but no chance.

Any idea or shutter is defect?

[K.RensAdmin bbPress]

After you added the line, did you clear the zwave config file and restart zwave service?

Kind regards,
K.Rens

[djandibParticipant]

Hi Koen, yes I did so, but problem was still actual.

Finally I started the autocalibration with in zwave-Service for the shutter and went for a beer ;-). When I came back all functions are ok.

Normal the autocalibration is only up-down-up. Yesterday it took abaut 5 minutes for calibration.
up-down partial-up-down complete-up partial and so on.

I think my neighbours thought I was crazy 😉
But now it works, why ever 🙂

Thanx
Andi

[K.RensAdmin bbPress]

Ah, did I forget to tell you Fibaro decided you just have to wait and it will fix itself – oops 😉
That’s indeed the correct solution, we noticed that with other clients as well.

Kind regards,
K.Rens

[Auteur]

Messages