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

I don’t think so. Certainly there was nothing automatic in OH1 to enable this. OH1 had a very similar initialisation as OH2.

I guess the question is how to enable this? It seems a pretty strange thing for Fibaro to remove it.

I’ll also look to add this to the database to force this class - I’ll probably add that tomorrow when I’m home.

@sihui so everything is working ok for you or are there still some issues?

That would be great!

Unfortunately there is one small issue left:

I’m using the “invert percent” option for my FGRM222 and the actual percent value in the GUI is constantly changing although the rollershutters are not moving … it’s doing this for all six FGRM222 I have, below I concentrated on node 33 (item name=FibFGR222_Living_West_L):

events.log:

2017-06-18 22:03:54.816 [ItemStateChangedEvent     ] - FibFGR222_Living_West_L changed from 82 to 83
2017-06-18 22:07:10.511 [ItemStateChangedEvent     ] - FibFGR222_Living_West_L changed from 83 to 17
2017-06-18 22:37:10.187 [ItemStateChangedEvent     ] - FibFGR222_Living_West_L changed from 17 to 83
2017-06-19 00:51:45.613 [ItemStateChangedEvent     ] - FibFGR222_Living_West_L changed from 83 to 17
2017-06-19 01:31:48.493 [ItemStateChangedEvent     ] - FibFGR222_Living_West_L changed from 17 to 83
2017-06-19 01:31:48.550 [ItemStateChangedEvent     ] - FibFGR222_Living_West_L changed from 83 to 17
2017-06-19 02:51:50.625 [ItemStateChangedEvent     ] - FibFGR222_Living_West_L changed from 17 to 83
2017-06-19 02:51:50.680 [ItemStateChangedEvent     ] - FibFGR222_Living_West_L changed from 83 to 17
2017-06-19 07:37:21.814 [ItemStateChangedEvent     ] - FibFGR222_Living_West_L changed from 17 to 83
2017-06-19 07:37:21.871 [ItemStateChangedEvent     ] - FibFGR222_Living_West_L changed from 83 to 17
2017-06-19 08:07:10.433 [ItemStateChangedEvent     ] - FibFGR222_Living_West_L changed from 17 to 83
2017-06-19 08:37:26.747 [ItemStateChangedEvent     ] - FibFGR222_Living_West_L changed from 83 to 17
2017-06-19 08:45:20.161 [ItemCommandEvent          ] - Item 'FibFGR222_Living_West_L' received command 0
2017-06-19 08:45:20.165 [ItemStateChangedEvent     ] - FibFGR222_Living_West_L changed from 17 to 0

I grabbed the debug log from around 08:15 to 08:46 to catch the last events:

-file deleted -

or

zwave.zip.xml (179.6 KB)

I have no idea if one of my rollershutter rules is causing this issue, but because the shutters are not physically moving I expect the percent value not to change.

rollershutter.rules (excerpt):

...
//shading positions
val Number ShadingLivingWest_L_Position = 70
val Number ShadingLivingWest_R_Position = 70

//closing positions
val Number ClosedLivingWest_L_Position = 70
val Number ClosedLivingWest_R_Position = 70

...

    rule "move shutters living west to shading position = main execution"
    	when
    		Item Shading_Shutter_LivingWest_Autoshade received update
    	then
    		if (Shading_Shutter_LivingWest_Autoshade.state==ON && ShutterOverrideTimerLiving_West.state==OFF && ShutterAutoOpenCloseLiving_Lock.state==OFF) {
      			if (FibFGR222_Living_West_L.state != ShadingLivingWest_L_Position) {
    			Thread::sleep(20000)
    			FibFGR222_Living_West_L.sendCommand(ShadingLivingWest_L_Position)
    			}
    			if (FibFGR222_Living_West_R.state != ShadingLivingWest_R_Position) {
    			Thread::sleep(20000)
    			FibFGR222_Living_West_R.sendCommand(ShadingLivingWest_R_Position)
    			logInfo("SHUTTER", "shutter living west in shading position")
    			}
    		}
    		else if (Shading_Shutter_LivingWest_Autoshade.state==OFF && ShutterOverrideTimerLiving_West.state==OFF && ShutterAutoOpenCloseLiving_Lock.state==OFF && ShutterDelayTimerLiving_West.state==OFF) {
    		  	if (FibFGR222_Living_West_L.state > 3) {
    		  	Thread::sleep(20000)
    		  	FibFGR222_Living_West_L.sendCommand(0)
    		  	logInfo("SHUTTER", "shutter living west left in 0 position")
    		  	}
    		  	if (FibFGR222_Living_West_R.state > 3) {
    			Thread::sleep(20000)
    			FibFGR222_Living_West_R.sendCommand(0)
    			logInfo("SHUTTER", "shutter living west right in 0 position")
    			}
    		}
end

rule "shutter livingroom auto close west"
when
	Channel 'astro:sun:shutterlivingroom:set#event' triggered END
then
	if (AutoOpenClose_Shutter_Proxy.state==ON) {
	ShutterAutoOpenCloseLiving_Lock.sendCommand(ON)
    FibFGR222_Living_West_L.sendCommand(ClosedLivingWest_L_Position)
	Thread::sleep(20000)
	FibFGR222_Living_West_R.sendCommand(ClosedLivingWest_R_Position)
	}
	else if (AutoOpenClose_Shutter_Proxy.state==OFF) {
		ShutterAutoOpenCloseLiving_Lock.sendCommand(OFF)
		}
end

...

Apart from this the migration from the snapshot to the development branch was pretty straight forward, all devices were initialized quickly, even the battery devices and also including one new device did work well.

There is no information at all in the log regarding node 33 :confused: . Did you use a different node?

Yes, I see. Very strange, maybe a copy and paste error. Let’s try it again:

https://gist.githubusercontent.com/sihui62/7cbe987807684a2687f6cbc2a50eca03/raw/72b458cd4bc4a32c2c037f80b796651a204c7543/zwave_node33.log

Sorry about that.

Here is another example for node 32 with some more “changing” events:

2017-06-19 11:13:33.966 [ItemStateChangedEvent     ] - FibFGR222_Living_South changed from 65 to 35
2017-06-19 11:13:34.228 [ItemStateChangedEvent     ] - FibFGR222_Living_South changed from 35 to 65
2017-06-19 11:44:04.374 [ItemStateChangedEvent     ] - FibFGR222_Living_South changed from 65 to 35
2017-06-19 11:44:04.492 [ItemStateChangedEvent     ] - FibFGR222_Living_South changed from 35 to 65
2017-06-19 12:45:04.537 [ItemStateChangedEvent     ] - FibFGR222_Living_South changed from 65 to 35
2017-06-19 12:45:05.331 [ItemStateChangedEvent     ] - FibFGR222_Living_South changed from 35 to 65

debug:

zwave_node32.zip.xml (261.6 KB)

or

https://gist.githubusercontent.com/sihui62/8173f08da9335c36a66c9fe6023157df/raw/d0790a1fd1d166934e31f34eb9721d6071664695/zwave_node32.log

Got it. One is coming through the BASIC command class - this is not being inverted. The other is then coming through the MULTILEVEL command class, and this is being inverted…

I’ll take a look…

1 Like

Hi Chris,

Finally managed to try out new binding as well, but with rather limited success.
I did upgrade to the latest openhab 2.1 snapshot in combination with zwave binding 2.1.0.20170618203.

I am able to add my test fibaro FGRM-222 Rev.25.25 with no issue - adding in paper UI.
I am able to control the blinds just fine - again from paperUI BlindsControl (UP/STOP/DOWN) as well as Switch are working just fine.

But Lamella position slider/dimmer has no impact - it seems that no command is sent to FGRM-222.
In openhab.log I am getting loads of “[ERROR] [ome.core.thing.internal.ThingManager] - Exception occurred while calling handler: java.lang.NullPointerException java.util.concurrent.ExecutionException: java.lang.NullPointerException” whenever I am moving the lamella slider in paperUI

Attached in logs.zip.xml
bundle_list.txt
event.log
openhab.log with INFO
openhab_debug.log with DEBUG

logs.zip.xml (4.4 KB)

Hi guys,

I tried openHAB 2.1.0 Build #961 with the corresponding 2.1.0.SNAPSHOT Z-Wave Binding today, but there is no lamella channel on any of the two FGRM222.

Controlling the blinds works fine.

Node XML & Log:
node2.xml (12.6 KB)
node3.xml (12.6 KB)

openhab.log prints this all over:

2017-06-22 08:59:33.091 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 3: Unknown command class 0x91
2017-06-22 08:59:40.284 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Unknown command class 0x91

Am I doing something wrong?
Any hints?

Thanks for your work btw!

This doesn’t have these changes for the FGRM222. The changes described here are only available in the development binding which needs to be manually installed.

Ah, thanks Chris, it works now! :smiley:

1 Like

Hi Lukas,

are you able to actually control lamella positioning with your setup?
I am not :frowning: - see my previous post.

@chris: any hint on how to fix my issue?

Hi Christian,

yes, works perfectly fine.

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)