Z-Wave Binding: Fibaro FGR-222 Rollershutter UP command not fully raising Blind

When issuing following command from rule:

gUpStairsBlinds.members.forEach[BlindsControl | BlindsControl.sendCommand(BlindsUp)]

or for a single blind:

sendCommand(ZWaveNode12FGRM222RollerShutter_BlindsControl, BlindsUp)

the blinds are raised, but lowered again for a split second.

2017-09-02 13:43:07.177 [ItemCommandEvent          ] - Item 'ZWaveNode10FGRM222RollerShutter_BlindsControl' received command UP
2017-09-02 13:43:07.179 [ItemStateChangedEvent     ] - ZWaveNode10FGRM222RollerShutter_BlindsControl changed from 100.0 to 0
2017-09-02 13:43:08.397 [ItemStateChangedEvent     ] - ZWaveNode10FGRM222RollerShutter_SensorPower changed from NULL to 109.6
2017-09-02 13:44:07.563 [ItemStateChangedEvent     ] - ZWaveNode10FGRM222RollerShutter_SensorPower changed from 109.6 to 0
2017-09-02 13:44:08.585 [ItemStateChangedEvent     ] - ZWaveNode10FGRM222RollerShutter_SensorPower changed from 0 to 106.3
2017-09-02 13:44:10.290 [ItemStateChangedEvent     ] - ZWaveNode10FGRM222RollerShutter_SensorPower changed from 106.3 to 0

From completion: variable BlindsUp is defined:

var BlindsUp = "UP"
var BlindsDown = "DOWN"

Calibration of the FGR-222 did not improve the situation.
Raising the blind from Paper UI does have the same effect.

2017-09-02 14:10:41.627 [ItemCommandEvent          ] - Item 'ZWaveNode11FGRM222RollerShutter_BlindsControl' received command UP
2017-09-02 14:10:42.821 [ItemStateChangedEvent     ] - ZWaveNode11FGRM222RollerShutter_SensorPower changed from 0 to 111.1
2017-09-02 14:11:41.898 [ItemStateChangedEvent     ] - ZWaveNode11FGRM222RollerShutter_SensorPower changed from 111.1 to 0
2017-09-02 14:11:42.917 [ItemStateChangedEvent     ] - ZWaveNode11FGRM222RollerShutter_SensorPower changed from 0 to 107.9
2017-09-02 14:11:44.350 [ItemStateChangedEvent     ] - ZWaveNode11FGRM222RollerShutter_SensorPower changed from 107.9 to 0

Using the manual switches allows raising the blind completely.
I am observing the same behaviour on all FGR-222 I am using and all are version 25.25
The configuration of one FGR-222 is attached

Please advise how to raise the blinds completely from rules and paper UI.

Same here. What’s ultimately your hw, binding version and item config.
Check (and try changing) parameters 3 (you likely don’t have a OH to understand Fibaro commands) and 13 (read it up in the Fibaro manual if you don’t know what it does).

Answering your questions one by one:
OH version: openHAB 2.1.0 release build with Z-Wave Dev build 2.1.0.201708201145 for lamella positioning support
items: All Zwave things and items were defined in Paper-UI
Did it ever work: yes,
Changes: no SW upgrades, did initial install after 2.1.0 was released, HW changes added more FGR-222 and refined the rules controlling the blinds.
Blinds type: All blinds are venetian blinds and I am not refering to tilt angle.
Calibration: Yes, via switch connected to S2 and via HABadmin

All blinds are configured identical parameter #3: “Blind Positioning with FIBAR Command” and #13: “default - controller+switchlimit” and all blinds behaving the same.

The zwave binding for FIBAR command support is from: Fibaro Roller Shutter FGRM-222 with Venetian Blinds - Lamellas Position

Find the logs with “log:set debug org.openhab.binding.zwave” here.

Since raising the blind via Paper UI as the same effect the UP command below was triggered via Paper-UI.
Also important there is no impact of the tilt angle in which the lamellas where positioned before UP command was issued.
openhab2_debug.log.xml (31.1 KB)

To demonstrate the difference between UP command and physical switch:
with UP command:
blind_raised_with_UP!
With physical switch:
blind_raised_with_switch|320x240

using the log viewer (http://www.cd-jackson.com/index.php/openhab/zwave-log-viewer) created by @chris:

I think the question to answer is:
Why does the FGR-222 issue another measurement report at 15:55:50.166 and subsequently lower the blind a bit.

Fibaro FGR-222 in HABadmin:

and how are the items defined, what’s the channel name ?
Did you try using blinds_control and/or blinds_shutters channel ?

and what exactly was your change that did break it ?

First and foremost, the simple answer to your question of this thread is:
The ‘lower the blinds a bit’ is standard behavior to return to the lamella tilt angle that was set before the blinds started moving.

Your log is only showing a single Fibar message which likely is the state report, the others are ‘power’ reports and as such I believe them to be unrelated to positioning.
The message also keeps complaining about the unknown Fibar command class, but I’m not sure about the interpretation, you need to ask @chris for help here.
Either way, a single message is unlikely to be the origin of TWO consecutive state change events.
Are you sure your log is comprehensive ?
Did you try other settings of #13 ? I’m using “like 1 + with STOP control frame”.
Possibly an additional message is generated when your blinds hit the limit.

These are defined in PaperUI and you can see the name in PaperUI -:

I’ve not seen the message you refer, but if this is the Fibaro specific command, then it’s not supported in the current master version - only in the development version.

I’m referring to the last message in the log in post #4.
Christian said he IS using your dev binding in post #3.

I am using Blinds Control e.g.
zwave:device:99f8ebf5:node6:blinds_control
and Lamella position e.g.
zwave:device:99f8ebf5:node6:blinds_lamella
to control the venetian blinds.

I am not able to determine when it stopped working - we had loads of sunshine and the blinds were not raised for quiet some time. Now with summer ending I found out…

I might have encounter the same issue a couple of month back when testing with the first (and only fgr222) and might fixed it with reseting the device.
Testing was done on 2.1 snapshots and zwave dev build back then.
With all blinds now equipped with fgr222 and a couple additional zwave devices I would really like to avoid going back to square one

@chris - see below I am on the dev build

openhab> bundle:listSTART LEVEL 100 , List Threshold: 50
 ID | State    | Lvl | Version                | Name
------------------------------------------------------------------------------------------------------
  9 | Active   |  80 | 5.3.1.201602281253     | OSGi JAX-RS Connector
 10 | Active   |  80 | 2.3.1                  | Gson
 11 | Active   |  80 | 18.0.0                 | Guava: Google Core Libraries for Java
 12 | Active   |  80 | 3.0.0.v201312141243    | Google Guice (No AOP)
 13 | Active   |  80 | 1.5.8                  | swagger-annotations
 14 | Active   |  80 | 3.19.0.GA              | Javassist
 16 | Active   |  80 | 3.5.2                  | JmDNS
 19 | Active   |  80 | 1.1.0.Final            | Bean Validation API
 21 | Active   |  80 | 2.0.1                  | javax.ws.rs-api
 23 | Active   |  80 | 3.2.0.v201101311130    | ANTLR Runtime
 26 | Active   |  80 | 1.6.0                  | Commons Codec
 27 | Active   |  80 | 3.2.1                  | Commons Collections
 28 | Active   |  80 | 1.1                    | Commons Exec
 29 | Active   |  80 | 2.2.0                  | Commons IO
 30 | Active   |  80 | 2.6                    | Commons Lang
 35 | Active   |  80 | 4.2.3                  | Apache HttpClient OSGi bundle
 36 | Active   |  80 | 4.2.3                  | Apache HttpCore OSGi bundle
 57 | Active   |  80 | 4.0.8                  | Apache Karaf :: Wrapper :: Core
 58 | Active   |  80 | 3.1.0.7                | Apache ServiceMix :: Bundles :: commons-httpclient
 63 | Active   |  80 | 2.11.0.v20150805-0538  | EMF Common
 64 | Active   |  80 | 2.11.1.v20150805-0538  | EMF Ecore
 65 | Active   |  80 | 2.11.1.v20150805-0538  | EMF XML/XMI Persistence
 66 | Active   |  80 | 3.8.0.v20160509-1230   | Common Eclipse Runtime
 67 | Active   |  80 | 3.6.100.v20160223-2218 | Extension Registry Support
 94 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Config Core
 95 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Configuration Discovery
 96 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Config Dispatcher
 97 | Active   |  75 | 0.9.0.b5               | Eclipse SmartHome Config XML
 98 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Core
 99 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Core Audio
100 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome AutoUpdate Binding
101 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Core Binding XML
102 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Core ID
103 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Core Persistence
104 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Scheduler Service
105 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Core Thing
106 | Active   |  75 | 0.9.0.b5               | Eclipse SmartHome Core Thing XML
107 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Transformation Service
108 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Core Voice
109 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Console
110 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Console for OSGi runtime Karaf
111 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome JavaSound I/O, Fragments: 169
112 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Monitor
113 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Net I/O Bundle
114 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome REST Interface Bundle
115 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Core REST API
116 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome REST mDNS Announcer
117 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Sitemap REST API
118 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome SSE REST API
119 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Voice REST API
120 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Bonjour/MDS Service Discovery Bundle
121 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Web Audio Support
122 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Model Core
123 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Item Model
124 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Item Model Runtime
125 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Persistence Model
126 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Persistence Runtime
127 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Rule Model
128 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Rule Runtime
129 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Script
130 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Script Runtime
131 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Sitemap Model
132 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Sitemap Runtime
133 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Thing Model
134 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Thing Model Runtime
135 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Json Storage Service
136 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome UI
137 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome UI Icons
138 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Classic IconSet
139 | Active   |  80 | 2.9.2                  | Xtend Runtime Library
140 | Active   |  80 | 2.9.2                  | Xtend Macro Interfaces
141 | Active   |  80 | 2.9.2                  | Xtext
142 | Active   |  80 | 2.9.2                  | Xtext Common Types
143 | Active   |  80 | 2.9.2                  | JSR-45 Smap installer
144 | Active   |  80 | 2.9.2                  | Xtext Utility
145 | Active   |  80 | 2.9.2.v20160428-1452   | Xbase Model
146 | Active   |  80 | 2.9.2                  | Xbase Runtime Library
162 | Active   |  80 | 2.2.0                  | JUPnP Library
163 | Active   |  80 | 1.9.6                  | MIME streaming extension
164 | Active   |  80 | 5.0.2                  | Require-Bundle Fix :: org.objectweb.asm
166 | Active   |  90 | 2.1.0                  | openHAB Core
167 | Active   |  80 | 2.1.0                  | openHAB Karaf Integration
169 | Resolved |  80 | 2.1.0                  | openHAB Sound Support, Hosts: 111
170 | Active   |  80 | 2.1.0                  | openHAB Dashboard UI
175 | Active   |  80 | 3.2.0                  | Commons Net
176 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Basic UI, Fragments: 178
177 | Active   |  80 | 0.9.0.b5               | Eclipse SmartHome Paper UI, Fragments: 180
178 | Resolved |  75 | 2.1.0                  | openHAB Basic UI Fragment, Hosts: 176
179 | Active   |  80 | 2.1.0                  | HABPanel User Interface
180 | Resolved |  75 | 2.1.0                  | openHAB Paper UI Theme Fragment, Hosts: 177
181 | Active   |  80 | 0.9.0.b5               | Astro Binding
182 | Active   |  80 | 1.10.0                 | openHAB Pushover Action
183 | Active   |  80 | 2.1.0                  | openHAB 1.x Compatibility Layer
186 | Active   |  80 | 1.10.0                 | openHAB GPIO Binding
187 | Active   |  80 | 1.10.0                 | openHAB GPIO IO Module
188 | Active   |  80 | 2.1.0                  | Kostal Inverter Binding
189 | Active   |  80 | 2.1.0                  | Network Binding
190 | Active   |  80 | 3.12.0.OH              | nrjavaserial
192 | Active   |  80 | 1.10.0                 | openHAB InfluxDB Persistence bundle
194 | Active   |  80 | 2.1.0                  | HABmin User Interface
195 | Active   |  80 | 1.10.0                 | openHAB MQTT Binding
196 | Active   |  80 | 1.10.0                 | openHAB MQTT Transport Bundle
198 | Active   |  80 | 1.10.0                 | openHAB Weather Binding
210 | Active   |  80 | 2.1.0                  | HomeKit Integration
211 | Active   |  80 | 2.1.0.201708201145     | ZWave Binding
openhab> 

items definition:
(no way to share screenshots now)

openhab> smarthome:items list |grep -i node6
ZWaveNode6FGRM222RollerShutter_BlindsControl (Type=RollershutterItem, State=94, Label=Blinds Control, Category=Blinds, Groups=[gBlinds, gAllBlinds, gUpStairsBlinds])
ZWaveNode6FGRM222RollerShutter_SensorPower (Type=NumberItem, State=0, Label=Sensor (power), Category=Energy)
ZWaveNode6FGRM222RollerShutter_LamellaPosition (Type=DimmerItem, State=0, Label=Lamella position, Category=Blinds, Groups=[gBlindsLam, gAllBlindsLam, gUpStairsBlindsLam])
openhab>

I’m not sure why the proprietary command class wouldn’t be recognised. The only thing I can think of is that it was somehow missed during the device interrogation phase. You could try to reinitialise it (use advanced mode in HABmin and select “reinitialise device” in the top right menu of the thing).

“reinitialized device” and it made it worse (and stupid me did reinitialize all)

UP command is OK now, but DOWN command is now messed up

Attached are logs from node13:

  1. Parameter #13 set to default

    node13_debug_paratmeter13_default.xml (73.3 KB)

  2. Parameter #13 set to “like 1 + STOP”


    node13_debug_parameter13_1stop.xml (223.2 KB)

Can you describe what “messed up” means please?

Instead of stopping in fully closed position the blind is raised and the lamallas are in extreme position - pointing upwards.
Check mesurement reports…

BUT: after calibration the DOWN command is fine again.
DOWN lowers the blinds with lamellas fully closed
and UP is back to before.

The proprietary message still remains…


node13_debug_paratmeter13_default_aftercal.xml (64.5 KB)

I don’t think this sounds like it’s a binding issue. It sounds more like an issue with getting the device to work, so I hope someone else will be able to help you with that…

These messages are just not processed at the moment. Only commanding is supported.

So the question remains, why does FGR-222 lower the blinds again after they have been fully raised.
I might consider reseting one FGR-222 and re-add to zwave as new device.

I already answered: because that’s standard behavior. After positioning (incl. UP,DOWN), FGRMs re-adjust lamellas to the angle that they were set to before the positioning command was received.
It must be done like that because there’s just one single motor to do both mechanically, raise/lower and lamella tilt.

If down/up are reversed, you need to set the ‘invert control’ switch on the channel (well, or reverse the electrical wiring).

1 Like

Found a workaround to limit the impact of the standard behaviour: Tilting the lamellas to horizontal position before raising.
With this tilt angle the blinds are almost fully closed.