Fibaro Roller Shutter FGRM-222 with Venetian Blinds - Lamellas Position

Not yet - I extracted the information to look from your log but didn’t get to look at it last night - hopefully tonight…

Hey Christian

Did you set the configuration parameter number 3 to value 1 (using Fibar command class) and parameter number 10 to value 2 (Venetian Blind Mode, with positioning). Just to make sure the setup is correct.

@RobZe89

Yes, both values are set.

As mentioned before all other operations are working just fine - UP/STOP/DOWN (Blinds Control) as well as Switch to open/close.

Tried calibration no help.
When moving the slide for lamella control from e.g. 0 to 24 this is the result in openhab.log (DEBUG):
2017-06-21 12:50:30.994 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Command received zwave:device:3359c755:node2:blinds_lamella --> 24
2017-06-21 12:50:30.995 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occurred while calling handler: java.lang.NullPointerException
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at org.eclipse.smarthome.core.common.SafeMethodCaller.executeDirectly(SafeMethodCaller.java:220)[98:org.eclipse.smarthome.core:0.9.0.201706191632]
at org.eclipse.smarthome.core.common.SafeMethodCaller.callAsynchronous(SafeMethodCaller.java:189)[98:org.eclipse.smarthome.core:0.9.0.201706191632]
at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:83)[98:org.eclipse.smarthome.core:0.9.0.201706191632]
at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:67)[98:org.eclipse.smarthome.core:0.9.0.201706191632]
at org.eclipse.smarthome.core.thing.internal.ThingManager.receiveCommand(ThingManager.java:374)[105:org.eclipse.smarthome.core.thing:0.9.0.201706191632]
at org.eclipse.smarthome.core.items.events.AbstractItemEventSubscriber.receive(AbstractItemEventSubscriber.java:47)[98:org.eclipse.smarthome.core:0.9.0.201706191632]
at org.eclipse.smarthome.core.internal.events.OSGiEventManager$1.call(OSGiEventManager.java:192)[98:org.eclipse.smarthome.core:0.9.0.201706191632]
at org.eclipse.smarthome.core.internal.events.OSGiEventManager$1.call(OSGiEventManager.java:1)[98:org.eclipse.smarthome.core:0.9.0.201706191632]
at org.eclipse.smarthome.core.common.SafeMethodCaller$CallableWrapper.call(SafeMethodCaller.java:181)[98:org.eclipse.smarthome.core:0.9.0.201706191632]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_131]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_131]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_131]
at java.lang.Thread.run(Thread.java:748)[:1.8.0_131]
Caused by: java.lang.NullPointerException
at org.openhab.binding.zwave.handler.ZWaveThingHandler.handleCommand(ZWaveThingHandler.java:968)[204:org.openhab.binding.zwave:2.1.0.201706182030]
at org.eclipse.smarthome.core.thing.internal.ThingManager$4.call(ThingManager.java:377)[105:org.eclipse.smarthome.core.thing:0.9.0.201706191632]
at org.eclipse.smarthome.core.thing.internal.ThingManager$4.call(ThingManager.java:1)[105:org.eclipse.smarthome.core.thing:0.9.0.201706191632]
at org.eclipse.smarthome.core.common.SafeMethodCaller.executeDirectly(SafeMethodCaller.java:218)[98:org.eclipse.smarthome.core:0.9.0.201706191632]
… 12 more

@chris
If you need additional logs, just let me know.

@steinerl:

Are you able to share bundle:list?

Sure,

bundle:list:

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
54 | Active    |  80 | 4.0.8                  | Apache Karaf :: Shell :: Core
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.201706211154     | Eclipse SmartHome Config Core
95 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Configuration Discovery
96 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Config Dispatcher
97 | Active    |  75 | 0.9.0.201706211154     | Eclipse SmartHome Config XML
98 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Core
99 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Core Audio
100 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome AutoUpdate Binding
101 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Core Binding XML
102 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Core ID
103 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Core Persistence
104 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Scheduler Service
105 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Core Thing
106 | Active    |  75 | 0.9.0.201706211154     | Eclipse SmartHome Core Thing XML
107 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Transformation Service
108 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Core Voice
109 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Console
110 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Console for OSGi runtime Karaf
111 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome JavaSound I/O, Fragments: 170
112 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Monitor
113 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Net I/O Bundle
114 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome REST Interface Bundle
115 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Core REST API
116 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome REST mDNS Announcer
117 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Sitemap REST API
118 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome SSE REST API
119 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Voice REST API
120 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Bonjour/MDS Service Discovery Bundle
121 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Web Audio Support
122 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Model Core
123 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Item Model
124 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Item Model Runtime
125 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Persistence Model
126 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Persistence Runtime
127 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Rule Model
128 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Rule Runtime
129 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Script
130 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Script Runtime
131 | Active    |  80 | 2.1.0.201706182030     | ZWave Binding
132 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Sitemap Model
133 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Sitemap Runtime
134 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Thing Model
135 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Thing Model Runtime
136 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Json Storage Service
137 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome UI
138 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome UI Icons
139 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Classic IconSet
140 | Active    |  80 | 2.9.2                  | Xtend Runtime Library
141 | Active    |  80 | 2.9.2                  | Xtend Macro Interfaces
142 | Active    |  80 | 2.9.2                  | Xtext
143 | Active    |  80 | 2.9.2                  | Xtext Common Types
144 | Active    |  80 | 2.9.2                  | JSR-45 Smap installer
145 | Active    |  80 | 2.9.2                  | Xtext Utility
146 | Active    |  80 | 2.9.2.v20160428-1452   | Xbase Model
147 | Active    |  80 | 2.9.2                  | Xbase Runtime Library
163 | Active    |  80 | 2.2.0                  | JUPnP Library
164 | Active    |  80 | 1.9.6                  | MIME streaming extension
165 | Active    |  80 | 5.0.2                  | Require-Bundle Fix :: org.objectweb.asm
167 | Active    |  90 | 2.1.0.201706211311     | openHAB Core
168 | Active    |  80 | 2.1.0.201706211311     | openHAB Karaf Integration
170 | Resolved  |  80 | 2.1.0.201706211311     | openHAB Sound Support, Hosts: 111
171 | Active    |  80 | 2.1.0.201706211311     | openHAB Dashboard UI
176 | Active    |  80 | 3.2.0                  | Commons Net
177 | Active    |  80 | 2.1.0.201706211311     | openHAB 1.x Compatibility Layer
178 | Active    |  80 | 1.1.1.201605111122     | Swagger Provider
179 | Active    |  80 | 2.4.5                  | Jackson-annotations
180 | Active    |  80 | 2.4.5                  | Jackson-core
181 | Active    |  80 | 2.4.5                  | jackson-databind
182 | Active    |  80 | 2.4.5                  | Jackson-dataformat-YAML
183 | Active    |  80 | 2.1.0                  | json-path
184 | Active    |  80 | 1.5.8                  | swagger-core
185 | Active    |  80 | 1.5.8                  | swagger-jaxrs
186 | Active    |  80 | 1.5.8                  | swagger-models
187 | Active    |  80 | 2.2                    | json-smart
188 | Active    |  80 | 3.4.0                  | Apache Commons Lang
189 | Active    |  75 | 0.9.0.201706211154     | Eclipse SmartHome Exec Transformation Service
190 | Active    |  75 | 0.9.0.201706211154     | Eclipse SmartHome JavaScript Transformation Service
191 | Active    |  75 | 0.9.0.201706211154     | Eclipse SmartHome JSonPath Transformation Service
192 | Active    |  75 | 0.9.0.201706211154     | Eclipse SmartHome Map Transformation Service
193 | Active    |  75 | 0.9.0.201706211154     | Eclipse SmartHome RegEx Transformation Service
194 | Active    |  75 | 0.9.0.201706211154     | Eclipse SmartHome Scale Transformation Service
195 | Active    |  75 | 0.9.0.201706211154     | Eclipse SmartHome XPath Transformation Service
196 | Active    |  75 | 0.9.0.201706211154     | Eclipse SmartHome Xslt Transformation Service
197 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Basic UI, Fragments: 201
198 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome WebApp UI
199 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome Paper UI, Fragments: 205
200 | Active    |  80 | 2.1.0.201706211311     | openHAB REST Documentation
201 | Resolved  |  75 | 2.1.0.201706211311     | openHAB Basic UI Fragment, Hosts: 197
202 | Active    |  75 | 2.1.0.201706211311     | openHAB Classic UI Fragment
203 | Active    |  80 | 2.1.0.201706211311     | HABmin User Interface
204 | Active    |  80 | 2.1.0.201706211311     | HABPanel User Interface
205 | Resolved  |  75 | 2.1.0.201706211311     | openHAB Paper UI Theme Fragment, Hosts: 199
206 | Active    |  80 | 0.9.10.v20160429-1435  | reflections (wrap)
207 | Active    |  80 | 1.5.8.v20160511-1038   | swagger-jersey2-jaxrs (wrap)
208 | Active    |  80 | 3.12.0.OH              | nrjavaserial
210 | Installed |  80 | 2.1.0.201706211311     | ZWave Binding
211 | Active    |  80 | 2.1.0.201706211311     | HomeKit Integration
212 | Active    |  80 | 0.9.0.201706211154     | Astro Binding
213 | Active    |  80 | 2.1.0.201706211311     | Netatmo Binding
214 | Active    |  80 | 0.9.0.201706211154     | Eclipse SmartHome UPnP Transport Bundle
215 | Active    |  80 | 2.1.0.201706211311     | Samsung Tv Binding
216 | Active    |  80 | 0.9.0.201706211154     | YahooWeather Binding
217 | Active    |  80 | 1.10.0.201706211218    | openHAB RRD4j Persistence Bundle

@steinerl thanks

@chris
Uplift to build #961 and systemctl stop/start instead of systemctl restart of openhab did improve

the [ERROR] messages are gone.
In openhab log (DEBUG) I do see the following.
Still not able to confirm if lamella are actually moving :wink: since I am connect remotely.
openhab_debug_build.log.xml (75.5 KB)

@chris

and verified working - lamella control is working :grinning:

I am pretty sure that stop/start of openhab service did the trick.

@chris
Hello
I saw you made an update on the database for commandClass:SWITCH_MULTILEVEL

And I got the newest version from here. Had to update the OH2 runtime as you mentioned here. After deleting node XML and restart the OH2 everything is working as before on 1.9! Yee-haw! Finally! Thank you so much!

I will do a donation soon and hopefully other members on this topic will do that too!

Only if you have met all requirements:

If not, perform the steps in this post (read carefully, it will break your current things setup!):

1 Like

thx, works now :smile:

as you said I was on wrong binding:
202 | Active | 80 | 2.1.0.201706222153 | ZWave Binding

right one:
211 | Active | 80 | 2.1.0.201706182030 | ZWave Binding

1 Like

Thanks - I’m glad we got there… (finally :rolling_eyes:).

In the latest dev branch from 2.1.0.201706242319 a fix is not included yet, so I thought I open an issue that it is not being forgotten:


:grin:

Good idea. This isn’t so simple to resolve though so it might not be super quick. I’m not sure if it’s possible to change some setting in the device, or change the association groups or something to stop the BASIC messages?

I tried different settings with each of my six FGRM, but unfortunately I could not get the BASIC messages to stop.

We could update the database to stop BASIC messages being interpreted in this way (i.e. uncheck the BASIC tick box in the ML switch)- I guess the question is if the device is sending enough other messages that it’s still useful? I think from the logs I saw that it is, but…….

I checked all six FGRM222 devices in that 90 min debug log for any incoming

NODE XX: Received COMMAND_CLASS_BASIC...

messages and I only found reports for the shutter position like

NODE XX: Basic report, value = YY, it seems no other values are reported through BASIC command class.

Because the shutter position is also coming through the MULTILEVEL command class (correctly inverted if that option is checked) I think disabling the BASIC command class could be a valid option.

BUT: I don’t know if my interpretation of the debug log is correct :grinning:

Sounds good. If there’s always a multilevel command at the same time as the basic command then I think we can expect this to work ok. Can you update the database and I’ll do an update as soon as I can - might be Wednesday as I’m travelling, but if VPN works I’ll do it sooner.

Checked that too (now), within around half of a second after the BASIC report the MULTILEVEL report is coming in.

Done.

No need to rush, I still have a physical switch to move the shutters. Otherwise my wife would already have killed me :grinning:

After working two days with the dev branch from 20170701 I can confirm that the database update (removing BASIC messages from SWITCH_MULTILEVEL command class) for the FGRM222 solved the issue.
Git issue updated.
Thx a lot.