Fibaro FGRM 222 - Roller Shutter

[maoten (Mjahed .O)]

think better to use rule machine Smart app.

[tekne (João Ferrão)]

Hi guys,

I’m really new to ST world so, sorry for the repeat question. Since this thread is very very old and some of you have already mixed the Fibaro Dimmer into the conversation, could any confirm that adding the Roller Shutter from Fibaro as a “generic device” works with SmartThings?

If not and if we need specific code, since there is a lot of it in this thread, could any of you please point out to the most complete code in here and indicate if there is any parameter we need to be cautious of?

Thanks a lot in advance,
João

[tekne (João Ferrão)]

Hi Tony_Orr, did you mean you added the Shutters Module or you used a Fibaro Dimmer to control the shutters?

Thanks,
Joao

[Tony_Orr]

@tekne, hi, I use the Fibaro FGM222 modules. Its just ST that doesn’t recognise them as shutter controllers.

[tekne (João Ferrão)]

@Tony_Orr so basically all you had to do was add the Shutter Control from Fibaro as a “Dimmer” in SmartThings (instead of Generic Device) and it worked perfecly, right? Meaning… you did not have to do any coding costumization?

Thanks
João

[Tony_Orr]

Yep. Worked off the bat.

[Formig]

I am reading here that the Fibaro roller shutter works nicely when adding it is a dimmer. It just doesn’t work for me. All I can do is turn on (shutter opens) and off (shutter closes). Percentage values all results in full open (I.e. On).

Notably, when I look up events, opening results in 99% dimmed. Turning off results in 254%.

I have five fibaro roller shutter 2 installed. same issue with all of them. What could be wrong?

I would love to have percentage values. The ability to stop mid-movement would be great.

Also I wonder how % would work for anyone without some kind of calibration routine.

[CristianGM]

You need jut to calibrate it, it’s simple. Click & hold for 3 seconds, 3 times the button up ( or down, it doesn’t matter, but 3 times the same ). It will go fully down and up and it’s done.

[CristianGM]

I just did some changes into the dimmer device to.improve the UI and, more important, to add a configure and modify the value of the parameter 14. By default is configured to momentary switches ( value 0 ) but mines are Toggle Switches ( value 1 ).

[Formig]

Interesting. do I have to remove the device first? I tried calibrating it this morning, with no prior removal. When I hold three seconds and after that click three times, I don’t get the calibration motion you are describing. It just moves cause I clicked…

[CristianGM]

Hola 3 seconds, release, hold 3 seconds, release, hold 3 seconds…
And that’s all. No need to remove the device or anything else.

[Formig]

THAKS SO MUCH, ChristianGM. Perfect.

[dan.negrau]

Hello,
I’m new to this and my Fibaro Shutter is recognized as Z-Wave Metering Switch with only 2 options ON/OFF.
How can I enrolled’ it as dimmer or make’ it work as it is ?

[rickymohan]

Hello

is the FGR-222 Roller Shutter 2 and FGRM -222 Roller Shutter 2 the same.

There is an M in the version discussed above, but i cant seem to find them to purchase most stores only have the version without the <

Will the above mentioned trick work for FGR-222 Roller Shutter 2 as well.

Regards
Ricky

[spdestounis]

Hi,
i am new in smartthings and i would like some help please.
I setup correctly the motor device as dimmer also i calibrate it,everything works well open and close button and the % but not so well the problem is that i slide the bar until 1% and the blinds goes a little bit after the middle of height also i have toggle buttons as yours is any way to help me to change the settings on mine also?

[Tommy_Stromme (Tommy Strømme)]

I’ve got the Fgrm-222 running with the Device Handler called “(MC: Fibaro Rollers Blinds FGRM-222)”. The curtain is a big and heavy thing running on a tilted rail. On the device I can click open and close + stop, works fine… the “dimming-slider” does nothing. However I got this strange problem that I never quite figured out which has been there since I was on Vera. If I drag the curtains to a 100% the curtain drops/falls down to about 70%. The solution at the Vera was to create a scene that stopped at approx 95%. I am trying to re-create that with Core. I am able to send “open” and “close” commands using actions…but the “Stop” command in Core does not issue the “Stop” command. Nothing happens. Can anyone shed some light on this?

[danielbelemduarte (Daniel)]

Hi @duncan

Can you please confirm that this issue is already solved?

I still cannot connect my fibaro roller shutter to Smartthings HUB (I have created a discussion topic here) to simplify a response as this thread is getting bigger and bigger.

Thank you.
Daniel Duarte

[Bee_Jay (Benjamin J)]

@maoten

/** * fingerprint inClusters: “0x72,0x86,0x70,0x85,0x25,0x73,0x32,0x31,0x7a,0x25,0x91,0x75,0xef,0x32,0x31,0x91,0x2b,0x26,0x25” * * 0x72 V1 0x72 Manufacturer Specific * 0x86 V1 0x86 Version * 0x70 XX 0x70 Configuration * 0x85 V2 0x85 Association * 0x25 V1 0x25 Switch Binary * 0x73 V1 COMMAND_CLASS_POWERLEVEL * 0x32 V2 0x32 Meter * 0x31 V2 0x31 Sensor Multilevel * 0x7a V1 COMMAND_CLASS_FIRMWARE_UPDATE_MD * 0x25 V1 0x25 Switch Binary * 0x91 V1 COMMAND_CLASS_MANUFACTURER_PROPRIETARY * 0x75 V2 COMMAND_CLASS_PROTECTION_V2 * 0xef XX COMMAND_CLASS_MARK * 0x32 V2 0x32 Meter * 0x31 V2 0x31 Sensor Multilevel * 0x91 V1 COMMAND_CLASS_MANUFACTURER_PROPRIETARY * 0x2b V1 COMMAND_CLASS_SCENE_ACTIVATION * 0x26 V3 0x26 Switch Multilevel * 0x25 V1 0x25 Switch Binary * 0x20 V1 UNKNOWN * * References : * https://graph.api.smartthings.com/ide/doc/zwave-utils.html * pepper1.net - This website is for sale! - pepper1 Resources and Information. * * */metadata { definition (name: “Fibaro Rollers Blinds FGRM-222”, namespace: “MC”, author: “MC”) { capability “Actuator” capability “Switch Level” capability “Switch” capability “Door Control” capability “Contact Sensor” capability “Refresh” capability “Sensor” capability “Configuration” capability “Polling”
fingerprint inClusters: “0x72,0x86,0x70,0x85,0x25,0x73,0x32,0x31,0x7A,0x25,0x91,0x75,0xEF,0x32,0x31,0x91,0x2B,0x26,0x25”

command “open”
command “stop”
command “close”
command “setposition”
command “resetParams2StDefaults”
command “listCurrentParams”
command “updateZwaveParam”
command “test”, [“number”,“number”,“number”]

}
}
tiles { standardTile(“open”, “device.switch”, inactiveLabel: false, decoration: “flat”) { state “default”, label:‘open’, action:“open”, icon:“st.doors.garage.garage-open” } standardTile(“stop”, “device.switch”, inactiveLabel: false, decoration: “flat”) { state “default”, label:‘stop’, action:“stop”, icon:“st.doors.garage.garage-opening” } standardTile(“close”, “device.switch”, inactiveLabel: false, decoration: “flat”) { state “default”, label:‘close’, action:“close”, icon:“st.doors.garage.garage-closed” } controlTile(“levelSliderControl”, “device.level”, “slider”, height: 1, width: 2, inactiveLabel: false) { state “level”, action:“setposition” }
standardTile(“refresh”, “device.switch”, inactiveLabel: false, decoration: “flat”) {
state “default”, label:‘’, action:“refresh.refresh”, icon:“st.secondary.refresh”
}

details(["open", "stop", "close", "levelSliderControl", "refresh"])

}
def parse(String description) { log.debug “Parsing ‘${description}’”
def result = null
def cmd = zwave.parse(description, [0x20: 1, 0x25: 1, 0x31: 2, 0x32: 2, 0x85: 2, 0x75: 2, 0x26: 3])
log.debug “Parsed ${cmd}”

if (cmd ) {
result = createEvent(zwaveEvent(cmd))
return result
} else {
log.debug “Non-parsed event: ${description}”
}
}
def zwaveEvent(physicalgraph.zwave.commands.switchmultilevelv3.SwitchMultilevelSet cmd) { log.debug “Report SwitchMultilevelSet:${cmd}”
}
def init(){log.debug “oo”}
def zwaveEvent(physicalgraph.zwave.commands.switchbinaryv1.SwitchBinaryGet cmd) { log.debug “Report SwitchBinaryGet:${cmd}”
}
def zwaveEvent(physicalgraph.zwave.commands.switchbinaryv1.SwitchBinaryReport cmd) { log.debug “Report SwitchBinaryReport:${cmd}”
}
def zwaveEvent(physicalgraph.zwave.commands.switchmultilevelv3.SwitchMultilevelReport cmd) { log.debug “Report SwitchMultilevelReport:${cmd}”
}
def zwaveEvent(physicalgraph.zwave.commands.switchbinaryv1.SwitchBinarySet cmd) { log.debug “Report SwitchBinarySet:${cmd}”
}
def zwaveEvent(physicalgraph.zwave.commands.configurationv1.ConfigurationReport cmd) { def value = “when off” if (cmd.configurationValue[0] == 1) {value = “when on”} if (cmd.configurationValue[0] == 2) {value = “never”} [name: “indicatorStatus”, value: value, display: false]}
def zwaveEvent(physicalgraph.zwave.commands.versionv1.VersionCommandClassReport cmd) {def rcc = ""rcc = Integer.toHexString(cmd.requestedCommandClass.toInteger()).toString()
if (cmd.commandClassVersion > 0) {log.debug “0x${rcc}_V${cmd.commandClassVersion}”}}
def open() { delayBetween([ zwave.basicV1.basicSet(value: 0xFF).format(), zwave.switchBinaryV1.switchBinaryGet().format() ],500)}
def stop() { delayBetween([ zwave.switchBinaryV1.switchBinarySet(switchValue: 0xFF).format() ],500)}
def close() { delayBetween([ zwave.basicV1.basicSet(value: 0x00).format(), zwave.switchBinaryV1.switchBinaryGet().format() ],500)}
//“test” button for for parameter changes in IDE//1 and 2 byte parameters onlydef test(param ,value, size) { def hByte = (value / 256).toInteger() def lByte = value.toInteger() % 256 //mod def pv //log.debug “lb:${lByte} hb:${hByte}” if (size == 1) { pv = [lByte] } else { pv = [hByte,lByte] } def params = [paramNumber:param.toInteger(),value:pv,size:size.toInteger()]
//log.debug “test:${params.inspect()}”
updateZwaveParam(params)
}
/** * This method will allow the user to update device parameters (behavior) from an app. * A “Zwave Tweaker” app will be developed as an interface to do this. Or the user can * write his/her own app to envoke this method. No type or value checking is done to * compare to what device capability or reaction. It is up to user to read OEM * documentation prio to envoking this method. * *
THIS IS AN ADVANCED OPERATION. USE AT YOUR OWN RISK! READ OEM DOCUMENTATION! * * @param List[paramNumber:80,value:10,size:1] * * * @return none /def updateZwaveParam(params) { // if ( params ) { def pNumber = params.paramNumber def pSize = params.size //def pValue = [params.value] def pValue = params.value log.debug “Make sure device is awake and in recieve mode” log.debug “Updating ${device.displayName} parameter number ‘${pNumber}’ with value ‘${pValue}’ with size of ‘${pSize}’”
def cmds = []
cmds << zwave.configurationV1.configurationSet(configurationValue: pValue, parameterNumber: pNumber, size: pSize).format()
cmds << zwave.configurationV1.configurationGet(parameterNumber: pNumber).format()
delayBetween(cmds, 1000)
}
}
/* * Sets all of available Fibaro parameters back to the device defaults except for what * SmartThings needs to support the stock functionality as released. This will be * called from the “Fibaro Tweaker” or user’s app. * *
THIS IS AN ADVANCED OPERATION. USE AT YOUR OWN RISK! READ OEM DOCUMENTATION! * * @param none * * @return none /def resetParams2StDefaults() { log.debug “Resetting Sensor Parameters to Defaults” def cmds = [] cmds << zwave.configurationV1.configurationSet(configurationValue: [0], parameterNumber: 2, size: 1).format() cmds << zwave.configurationV1.configurationSet(configurationValue: [0], parameterNumber: 3, size: 2).format() cmds << zwave.configurationV1.configurationSet(configurationValue: [1], parameterNumber: 10, size: 1).format() cmds << zwave.configurationV1.configurationSet(configurationValue: [0], parameterNumber: 12, size: 2).format() cmds << zwave.configurationV1.configurationSet(configurationValue: [1], parameterNumber: 13, size: 1).format() cmds << zwave.configurationV1.configurationSet(configurationValue: [0], parameterNumber: 14, size: 1).format() cmds << zwave.configurationV1.configurationSet(configurationValue: [0], parameterNumber: 18, size: 1).format()
delayBetween(cmds, 500)
}
/* * Lists all of available Fibaro parameters and thier current settings out to the * logging window in the IDE This will be called from the “Fibaro Tweaker” or * user’s own app. * *
THIS IS AN ADVANCED OPERATION. USE AT YOUR OWN RISK! READ OEM DOCUMENTATION! * * @param none * * @return none */def listCurrentParams() { log.debug “Listing of current parameter settings of ${device.displayName}” def cmds = cmds << zwave.configurationV1.configurationGet(parameterNumber: 10).format() cmds << zwave.configurationV1.configurationGet(parameterNumber: 12).format() cmds << zwave.configurationV1.configurationGet(parameterNumber: 17).format()
delayBetween(cmds, 500)
}

Hi CristianGM: which button do I need to press 3 times? you mean the button on the fibaro device or in the software? I am not able to calibrate my device…

[Bee_Jay (Benjamin J)]

Hi guys,

I have the Fibaro FGRM 222 and used the code from maoten to set up the device.

The UP and down features work but my problem is that I want to turn the roller shutter up (starting from completely closed) and then stop the movement after approx. 1800 milliseconds so that the shutters stop in a half open position… if I set up a routine for that in rule machine it seems like the fibaro device does not get the second signal or maybe misses it since it is too fast? (1800 ms after the first UP I am clicking UP again).

How can I get this done? Using the slider to go to a certain % of opening does not work since calibrating the slider did not work for me.

Thank you so much! I am working on this since months and could not solve it…

[Bee_Jay (Benjamin J)]

The problem is that I think calibration only works if the device is connected directly to a motor that sends a signal back to the fibaro device once it arrived all the way up/down.

In my case the fibaro device is connected to a bus and on the bus I have all the roller shutters of the house… that means that the device does not get a signal back once the motors arrived all the way up/down and therefore I am not able to calibrate the slider…

Any ideas on how I can manually calibrate the slider and define the min and max values for the slider so that it knows where all the way up/down are?