After weeks of delay I finally wanted to actually use my FGR-223. As I had them updated to FW5.1, inclusion worked well some time ago and I knew about the trouble of positioning I didn’t expect further issues.
So I could control the blinds by wall switches connected to the included FGR-223, started calibration and…
A few “click” sounds, no movement, wall switch also won’t work anymore.
Same behaviour for all three FGR-223 I have here, no matter how calibration is started (wall switch, B button, parameter). Factory reset gets it back to where I came from.
I also tried the latest snapshot binding but of course that didn’t help.
The motor is a 3T45-10E with calibrated end switches.
Contacted Intuitech but still waiting for response.
Any idea what else I could try?
Frankly speaking I am really considering to send them back and pick another manufacturer’s controller even if they have a worse form factor.
I am quite happy with my FGR-222 but these devices drive me crazy. How can a product become so bad with the next generation…
I used Paper UI to force calibration. Parameter 150 set to 2 (force calibration). It is best to have them fully closed using the wall switches if possible. The blinds will do a full Up-down-up cycle. After that you need to again in Paper UI set Parameter 150 to 1 (device is calibrated).
After that they should work as desired. They did in my case.
Did you check the correct physical wiring?
Thanks for the info, but didn’t work for me.
As I said when I started calibration, even through parameter 150, the FGR-223 would just make a clicking noise (so I guess its relais are switched actually) but won’t move the blinds. I’ve also tried to start the procedure fully open / fully closed / in between.
As I switched between the three devices over and over again I re-confirmed the wiring multiple times. And also as they can be controlled by the wall switch prior to the calibration and after factory reset makes it quite obvious that wiring is not the issue.
Not yet but sure worth a try. Thank you for the hint.
I’m really close to replace them with some better designed product but it would be super annoying as I spent additional money on the FW update (which should be covered by the manufacturer anyway as they sold unfinished products)…
Do u have try to change the order of cable?
Try to invert the q1 and q2.
Hmm, no, didn’t see the point in that as the cables seem okay when operating with a wall switch (up = move up, down = move down).
If Q1/Q2 were wrong, it would just invert the movement direction but still the roller shutter should move during calibration.
Ok. I had your problem with fgr 223. This is my opinio but automatic calibration don t work. If you see the settings after calibration the time of up movment and down is the same as the default. You have to set on the setting device is calibrated and you can try to set the right time of up and down manually. I saw you to change the wire beacouse i rember that one time i had a similar issues with one rs2 and i resolve reversing the wire. But i think that you have problems with calibration. Try to set device is calibrated in settings.
Thank you for sharing your experience! I think this might actually work. I’ll have a try with manual setting, it will take a couple of days until I have time for that though.
Anyway still no feedback from Intuitech.
If you force calibration, I think the device stores the correct values internally. I have some RS3 that worked correctly after forced calibration and after I set parameter 150 back to “device calibrated”. For others I also had to store the up/down times in openHAB (and the device) through Paper UI.
Finally I got back to the FGR-223 and got them going by your help and the Intuitech FAQs. However I had to change the parameter 154 “Delay motor stop after reaching end switch” to 40 (4 seconds, default is 1 second) and parameter 155 “Motor operation detection” to 80 (default is 10 Watt, the motor I use draws up to 125 Watt), then run the calibration.
It didn’t work default values, neither with p154=30 and p155=50 in my case.
So now I am really keen on the next milestone release to controls of the roller shutter, not the dimmer. 
Hi!
I also have the problem with the status updates from the fibaro device. Do you think this is an issue on the fibaro device itself?
Thanks,
Stefan
I only get status-updates when it’s fully open or closed…I’ve shutters, but I have to set Parameter 151 to 2 to get open and closed states…everything in-between shows UNDEF…
If I use it with 151 set on 1, I get completely weird states…am I doing wrong something?
I resolved it =) There is no need for setting the operation mode, you have to set the command_poll_period correctly to become correct values =) → Follow this guide:
- Set the desired operation mode (Parameter 151) (in my case it was 1)
- Enter calibration mode by setting Parameter 150 to 2
- IMPORTANT → Wait for the calibration to be done, and then set Parameter 150 to 1! Otherwise you get UNDEF states when the shutter is “in between” endpositions) DO NOT TOUCH ANY CONTROL UNTIL THIS PARAMETER IS SET TO ONE! Ignore the Fibaro Docs here, as they state that the rollershutter would set it back itself…it does not XD
- Determine the longest movement-time (stored in parameter 156 and 157), add 2-5 seconds to it, and make this your command polling period. IMPORTANT → If your movement-time is longer than 15000 ms, you have to do that in the code-tab of your thing, because otherwise it always set back to 15000…
- Additionally I added the metadata “force auto update” on the shutter items (channel 1, right UNDER the one marked as deprecated) I’m not sure if this has any effect, but as I worked hours on this, I’m not gonna touch ANYTHING XD
- Enjoy =)
The shutters are working pretty well when ones figure out how…the fibaro documentation is “not very good” to keep it family friendly 