Indigo Domotics

Please add support for this as soon as possible.

thank you

btw. is there a way to make it work for me now? It is a bit difficult because I can't use the door behind this roller...

Z-Wave Indigo Device "112 - Mulitlevel Switch" Z-Wave Properties:
Indigo Z-Wave Version: 7.4.1
Node ID: 112
Model: Motor Control Class B
Model ID: 03031000
Manufacturer: Fibaro System
Manufacturer ID: 010F
Protocol Version: 6.02
Application Version: 5.01
Model Definition Version: 0
Library Type: 3
Class Name: Motor Control Class B
Class Hierarchy: 04 : 11 : 06
Command Class Base: 26
Command Versions: 20v1 85v1 86v1 8Ev1 55v1 56v1 98v1 59v1 5Av1 5Bv1 5Ev1 9Fv1 60v4 22v1 25v1 26v4 6Cv1 32v3 70v1 71v1 72v1 73v1 75v1 7Av1
Encryption Status: Supported but not Enabled
Multi-Endpoint Types: 1:(11 : 06), 2:(11 : 06)
Multi-Endpoint Classes: 1:[5E 26 85 8E 59 98 9F 6C 32 71 22], 2:[5E 26 85 8E 59 98 9F 6C 22]
Multi-Instance Counts: - none -
Features: routing, beaming, security, energyMeter
Neighbors: 4, 5, 6, 11, 12, 27, 29, 31, 32, 40, 57, 58, 59, 60, 61, 66, 67, 68, 69, 71, 73, 74
Associations: 1:[1] 2:[] 3:[]
Config Values: - none -

Yes, this one is on the request list. It has been for a while, so I'll bump up its priority. From the other thread it sounds like you figured out how to get it working.

We know you don't give a timeline for updates and we have to respect that and we understand that too but
it would be great if the Fibaro Roller Shutter 3 would be fully supported before the sun starts to shine again

It'll be supported in the next version, which we hope to have released very soon.

Indigo 7.5 is now available and includes preliminary (untested) support for the Fibaro Roller Shutter 3 (FGR223). Let me know if the 3 devices Indigo defines after sync work correctly. Note you might have to edit your Triggers/Schedules or other logic to select the correct devices after you re-sync (the device order created during the sync may be different).

Howdy doodie.. So I've felt up to doing a little bit of HA catching up the last few days and I've finally got around to fitting a roller shutter 3 (v5.1) to a window motor - I currently have other window motors controlled by roller shutter 2 modules and they work fine... however this one.. doesn't... and I don't think it's the module but I suppose it's possible! Setting it to force calibration mode does nothing, and setting manual values for the opening and closing times seem to be completely ignored. Also when it creates a new device it creates 3 linked devices, one for energy, one for shutter position and one for slats, but it makes the energy meter the main one which means every time I edit the shutter position device I have to click on the tab then click edit which is damn annoying! (actually.. why does energy have its own tab anyway? can't it just go on the energy values on the shutter position device?).

So far to fix I've tried:
Including as encrypted device
Excluding
Including as a non encrypted device
Excluding
Deleting device from list
Re-including as a non encrypted device.
Manually sending parameters.

Any other ideas?

No ideas? ¯\_(ツ)_/¯


Sent from my iPhone using Tapatalk Pro

I'm not sure what is going wrong with this one. Definitely do not include with encryption while we are troubleshooting, as that adds a lot of complexity. In particular we are aware that the FGR223 doesn't work well with Indigo currently when using encryption. You might checkout the manual to see if there is a way to factory reset it besides just excluding it; it is possible it is in a funny state from being included with encryption and needs a full reset before you include it without encryption.

Re-sync it in Indigo and copy/paste the Event Log results into a reply for me. Also include Event Log of you trying to control the position and configuration parameters.

The energy device is a side effect of how the module supports the different command classes. In this case the energy reports come in on different endpoints than the commands to report/control the position and tilt so we needed to break it out into 3 different devices. We should have put the energy reporting on the last panel though.

Hmm I will have a look see if there's a way to manually reset it - I'd have thought excluding and inclusion would have that effect but ¯\_(ツ)_/¯

Here's the device dump in case it's of use:

Indigo Z-Wave Version: 7.5.0
Node ID: 130
Model: Shutter Controller (FGR223)
Model ID: 03031000
Manufacturer: Fibaro System
Manufacturer ID: 010F
Protocol Version: 6.02
Application Version: 5.01
Model Definition Version: 1
Library Type: 3
Class Name: Motor Control Class B
Class Hierarchy: 04 : 11 : 06
Command Class Base: 26
Command Versions: 20v1 85v1 86v1 8Ev1 55v1 56v1 98v1 59v1 5Av1 5Bv1 5Ev1 9Fv1 60v4 22v1 25v1 26v4 6Cv1 32v3 70v1 71v1 72v1 73v1 75v1 7Av1
Encryption Status: Supported but not Enabled
Multi-Endpoint Types: 1:(11 : 06), 2:(11 : 06)
Multi-Endpoint Classes: 1:[5E 26 85 8E 59 98 9F 6C 32 71 22], 2:[5E 26 85 8E 59 98 9F 6C 22]
Multi-Instance Counts: - none -
Features: routing, beaming, security, energyMeter
Neighbors: 5, 6, 7, 10, 11, 12, 15, 16, 17, 18, 27, 28, 29, 31, 32, 33, 35, 50, 51, 61, 78, 82, 84, 87, 88, 90, 95, 99, 100, 101, 102, 104, 107, 115, 122, 125, 128, 129
Associations: 1:[1] 2:[] 3:[]
Config Values: 152:0 20:0 150:0 151:1 24:0 25:0 154:10 155:10 156:1000 157:1000 40:0 41:0 60:1 61:15 62:3600 65:10 66:3600 153:0


As for the resync:

Z-Wave Syncing - retrieved module neighbors list: 5, 6, 7, 10, 11, 12, 15, 16, 17, 18, 27, 28, 29, 31, 32, 33, 35, 50, 51, 61, 78, 82, 84, 87, 88, 90, 95, 99, 100, 101, 102, 104, 107, 115, 122, 125, 128, 129
Z-Wave Syncing - assigning return route to "130 - ZZ - Unused 130a"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Fibaro System - 010F, Shutter Controller (FGR223) - 03031000
Z-Wave Syncing - retrieved protocol version 6.02, app version 5.01
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Mulitlevel Switch : Motor Control Class B (04 : 11 : 06, base 26)
Z-Wave Syncing - retrieved command classes: 85v1 86v1 8Ev1 98v1 9Fv1 20v1 22v1 25v1 26v4 32v3 55v1 56v1 59v1 5Av1 5Bv1 5Ev1 60v4 6Cv1 70v1 71v1 72v1 73v1 75v1 7Av1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming, security
Z-Wave Syncing - retrieved multi-endpoint types: 1:(11 : 06), 2:(11 : 06)
Z-Wave Syncing - retrieved multi-endpoint classes: 1:[5E 26 85 8E 59 98 9F 6C 32 71 22], 2:[5E 26 85 8E 59 98 9F 6C 22]
Z-Wave Syncing - retrieved group 1 associations: []
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Syncing - retrieved group 3 associations: []
Z-Wave Syncing - added group 1 multi association to interface
Z-Wave Syncing - retrieved parameter 151 "Operating mode" is 1 "Roller with Position"
Z-Wave Syncing - retrieved parameter 150 "Force calibration" is 1 "Calibrated"
Z-Wave Syncing - device "130 - ZZ - Unused 130a" parameter 150 "Force calibration" changed to 0 "Not Calibrated" (was 1 "Calibrated")
Z-Wave Syncing - retrieved parameter 156 "Up movement duration" is 1000 * 10 milliseconds
Z-Wave Syncing - retrieved parameter 157 "Down movement duration" is 1000 * 10 milliseconds
Z-Wave Syncing - retrieved parameter 152 "Slats duration and gate close timer" is 150 * 10 milliseconds
Z-Wave Syncing - device "130 - ZZ - Unused 130a" parameter 152 "Slats duration and gate close timer" changed to 0 * 10 milliseconds (was 150 * 10 milliseconds)
Z-Wave Syncing - retrieved parameter 153 "Slats position return to previous" is 0 "Only When Indigo Controlled"
Z-Wave Syncing - retrieved parameter 154 "Motor stop delay after end switch" is 10 * 100 milliseconds
Z-Wave Syncing - retrieved parameter 155 "Motor operation detection" is 10 watts
Z-Wave Syncing - retrieved parameter 20 "Switch type" is 0 "Momentary"
Z-Wave Syncing - retrieved parameter 40 "Switch 1 scenes" is 0 "Disabled"
Z-Wave Syncing - retrieved parameter 41 "Switch 2 scenes" is 0 "Disabled"
Z-Wave Syncing - retrieved parameter 24 "Reverse S1 and S2 input operation" is false
Z-Wave Syncing - retrieved parameter 25 "Reverse Q1 and Q2 output operation" is false
Z-Wave Syncing - retrieved parameter 61 "Power report threshold" is 15 %
Z-Wave Syncing - retrieved parameter 62 "Periodic power reports" is 3600 seconds
Z-Wave Syncing - retrieved parameter 60 "Include internal usage in power reports" is true
Z-Wave Syncing - retrieved parameter 65 "Energy report threshold" is 10 * 0.01 kWh
Z-Wave Syncing - retrieved parameter 66 "Periodic energy reports" is 3600 seconds
Z-Wave Syncing - complete
Z-Wave sent "Mike's Study - Window Opener" status request
Z-Wave sent "Mike's Study - Window Opener" energy status request
Z-Wave sent "ZZ - Unused 130b" status request
Z-Wave received "ZZ - Unused 130b" status update brightness 100
Z-Wave received "050 - Temperature 1" sensor update to 1

And changing a parameter, in this case the "Up movement duration":
Z-Wave device "130 - ZZ - Unused 130a" parameter 156 "Up movement duration" changed to 100 * 10 milliseconds

And setting 'force calibration: force calibration now' (which outwardly doesn't seem to do anything:

Z-Wave device "130 - ZZ - Unused 130a" parameter 150 "Force calibration" changed to 2 "Force Calibration Now"

"We should have put the energy reporting on the last panel though. "

oh and any chance of that changing in the next release? it's super annoying.. almost as annoying as me!

Jumping in here. I bought one of these (running v5.1 firmware out of the box) and it's impossible to get Indigo to see it and sync to it. Any suggestions for what to try?

No news for this?

In the next (not yet available) release of Indigo we've modified the device definition which I believe will fix the problem causing device parameters to not changed correctly. Not positive that will fix all the issues, but we'll see. No ETA yet on when this new version of Indigo will be available; we are heads-down working on making the changes to Indigo so that it will run on mac OS 12.3 right now.

Indigo 2022.1.0 is now available and should let Indigo change this module's parameters.