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

[chris (Chris Jackson)]

At the moment I’ve not merged this while I look at some other changes. The reason is it’s a breaking change and I’d like to avoid multiple sets of breaking changes to avoid upsetting everyone…

[Chri46 (Christian Berndt)]

Alright - seems like I am stuck with OH2.1, since you did not answer the question if the 2.1 dev build would work with OH2.2(snaphot).
Which is far from ideal, due to stability issues in OH2.1 and lack of homekit support for new accessories.
I guess I need to search for alternatives to OpenHab to handle my requirements

[sihui]

@Chri46

if the 2.1 dev build would work with OH2.2(snaphot).

I have used this combination for a couple of months without any problems.
As an alternative you may use the 2.2 dev zwave binding with 2.2 snapshot runtime:

OH2 Z-Wave refactoring and testing... and SECURITY

I’ve put a new version of the binding here. This is a 2.2 version as mentioned a few days ago - this version also has a change to initialisation sequence. There’s now a new step that will check the Z-Wave Plus configuration and set the lifeline association group. Hopefully this doesn’t cause any issues . If you spot any problems, please let me know and provide a log (I’m sure you all know the routine ). One point to note is that this lifeline setting will remove any other lifelin…

[chris (Chris Jackson)]

@Chri46

seems like I am stuck with OH2.1, since you did not answer the question if the 2.1 dev build would work with OH2.2(snaphot).

Sorry - I missed this, but yes, it will work with the current runtime. 2.1 and 2.2 are just the name really, and the latest dev binding is also named 2.2.

[steinerl (Lukas)]

Hello,

my OH is currently on 2.2 snapshot with the 2.2 snapshot zwave binding.
I can control shutter and lamella position via the OH interface, but if I change the position of my blinds via the hardware switches, OH doesn’t get back any status updates of the current position.

Should this work in the current 2.2 binding?

The FGRM222 are configured to “Venetian Blind Mode” and “Blind position via Fibar Command”.

Thanks!

[Chri46 (Christian Berndt)]

+1 for current position/tilt angle reflected in OH

Manual changes are not reflected in OH2.1 and to my understanding the OH2.2 dev binding is (very) similar to OH2.1 dev binding for the venetian blind support.

My guess is that the currently unsupported proprietary messages are used for feedback of tilt angle (among other things).

@steinerl are you seeing that as well: https://community.openhab.org/t/z-wave-binding-fibaro-fgr-222-spontaneous-change-of-blindscontrol-state/33860

[chris (Chris Jackson)]

@Chri46

to my understanding the OH2.2 dev binding is (very) similar to OH2.1 dev binding for the venetian blind support.

No - it’s quite different. The dev version implements the Fibaro specific command class for lamella control. I’m not sure if it handles any status messages.

@Chri46

the currently unsupported proprietary messages

Again, this is supported in the dev binding.

[preuni (Marius)]

hey all,

i also have the problem, that i cannot see the channels "lamella position"
i’m running OH 2.2 with Z-Wave Binding 2.20 snapshot.

do i have to update something or did i miss configure something?
thanks for the help

[sihui]

@preuni

with Z-Wave Binding 2.20 snapshot.

That function is supported in the development branch, not the snapshot:

OH2 Z-Wave refactoring and testing... and SECURITY

The latest version of the development binding dated 8th Sep 2018 is here. Toward the end of last year I spent some time doing some initial refactoring of the ZWave binding in OH2. This focussed on rewriting the way transactions work as this is an enabler for other areas of the code. At the same time I also restructured the different layers of the binding to make things cleaner, and done some changes to support a system of autocoding the command classes directly from the Z-Wave standard which s…

[preuni (Marius)]

thanks a lot, i could manage it and it works! thanks for that
another quesiton, does anyone have an example how to use this channel now? i would like to make a rule that the lamella position will be 50% after receiving being on the bottom

[mstormi (Markus Storm)]

Just define it to be a dimmer.

[preuni (Marius)]

thanks for the great idea

but when i do it, nothing happen. do i have to chane my settings ?

Dimmer LivingRoom_RollerShutter_Left_Switch “Wohnzimmer Raffstore Links” (gEG) {
channel=“zwave:device:bcee5ca7:node2:switch_lamella”
}

[mstormi (Markus Storm)]

blinds_lamella (not switch_lamella)

[preuni (Marius)]

thanks again, you are my santa clause
i read that, i have to set the parameter3 to 1(fibar command) and 10 to 2. but when i change the parameter3 to 1 i get always an error 500 internal server error .

i already turned off my items but it still appears

[preuni (Marius)]

solved with the habmin now i got the parameter 3 to 1.
but when i slide the dimmer to 0% nothing happens the same when i slide to 100% is the calibration wrong?

[Kellermeister (Marcel)]

actually i have define the items in paper ui. now i try to define the items in the *.item file.
the functions up, down and stop works with this definition.

Rollershutter EgWz_JalousieLinks_Control "Jalousie Links [%s]" <rollershutter>  {channel="zwave:device:Razberry2:node15:blinds_control,command=switch_multilevel,invert_state=false,invert_percent=true"}

But i can’t invers the percent value with parameter “invert_percent”. i can set it to true or false, but it is always the same result. Is there something wrong in this item definition?

i use openhab 2.1.0 and z-wave snapshot 2.3.0

[mstormi (Markus Storm)]

In OH2, invert_control and invert_percent are defined at the thing level for the blinds control channel, i.e. not in the .items file and via PaperUI only.
Edit: yes you can introduce .things files, too, but I would refrain from doing so once you already have defined the things via autodiscovery/PaperUI.

[sihui]

Example for

@mstormi

are defined at the thing level

if you still want to configure it via text file:

Zwave detects things that are manually configured

Thx, that is what I already thought. No problem, back to GUI configured things now BTW, if anybody is still looking for changing the invert percent for rollershutter devices in the things file: Thing zwave:fibaro_fgrm222_24_024:controller:node11 "Z-Wave Node 11: FGRM222 Roller Shutter" (zwave:serial_zstick:controller) [ node_id=11 ] { Channels: Type blinds_control : blinds_control [ config_invert_percent=true ] }

[steinerl (Lukas)]

Im currently on version 2.3.0.201803271924 of the Z-Wave binding.

Controlling shutter und lamella position via OH works fine, but I still don’t get any responses when controlling my venetian blinds via the hardware switches.

The log file says Unsupported Z-Wave command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY (0x91) all the time.

Any tips?

@chris should this be working?

15:17:14.223 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 02 06 31 05 04 22 04 26 C3 
15:17:14.229 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 06 31 05 04 22 04 26 
15:17:14.238 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 06 31 05 04 22 04 26 
15:17:14.245 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 06 31 05 04 22 04 26 
15:17:14.252 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - lastTransaction null
15:17:14.256 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
15:17:14.260 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
15:17:14.264 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
15:17:14.269 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
15:17:14.272 [DEBUG] [otocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_SENSOR_MULTILEVEL V2 SENSOR_MULTILEVEL_REPORT
15:17:14.276 [DEBUG] [ass.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Type = Power(4), Scale = 0
15:17:14.280 [DEBUG] [ass.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Value = 106.2
15:17:14.283 [DEBUG] [ave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
15:17:14.286 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
15:17:14.290 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 106.2
15:17:14.294 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:89b1005d:node2:sensor_power to 106.2 [DecimalType]
15:17:14.298 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
15:17:14.301 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@6c0e8062.
15:17:14.304 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
15:17:14.307 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
15:17:14.309 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
15:17:14.312 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start
15:17:14.314 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction from controllerQueue
15:17:14.317 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage nothing
15:17:17.682 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0E 00 04 00 02 08 91 01 0F 26 03 03 5B 00 1D 
15:17:17.686 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 08 91 01 0F 26 03 03 5B 00 
15:17:17.693 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 08 91 01 0F 26 03 03 5B 00 
15:17:17.697 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 08 91 01 0F 26 03 03 5B 00 
15:17:17.701 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 02 06 31 05 04 22 00 00 E1 
15:17:17.704 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - lastTransaction null
15:17:17.710 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
15:17:17.714 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
15:17:17.714 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 06 31 05 04 22 00 00 
15:17:17.718 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY, endpoint 0
15:17:17.723 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 06 31 05 04 22 00 00 
15:17:17.729 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 2: Command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY not found, trying to add it.
15:17:17.736 [DEBUG] [otocol.commandclass.ZWaveCommandClass] - NODE 2: Unknown command class 0x91
15:17:17.739 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 2: Unsupported Z-Wave command class COMMAND_CLASS_MANUFACTURER_PROPRIETARY (0x91)
15:17:17.742 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
15:17:17.745 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@2eb48b93.
15:17:17.749 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
15:17:17.751 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
15:17:17.753 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 06 31 05 04 22 00 00 
15:17:17.756 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - lastTransaction null
15:17:17.758 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
15:17:17.760 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
15:17:17.762 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
15:17:17.764 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
15:17:17.765 [DEBUG] [otocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_SENSOR_MULTILEVEL V2 SENSOR_MULTILEVEL_REPORT
15:17:17.767 [DEBUG] [ass.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Type = Power(4), Scale = 0
15:17:17.769 [DEBUG] [ass.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Value = 0E+1
15:17:17.771 [DEBUG] [ave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
15:17:17.773 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
15:17:17.775 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 0E+1
15:17:17.779 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:89b1005d:node2:sensor_power to 0 [DecimalType]
15:17:17.781 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
15:17:17.783 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@143e337a.
15:17:17.785 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
15:17:17.786 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
15:17:17.788 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
15:17:17.790 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start
15:17:17.792 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction from controllerQueue
15:17:17.793 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage nothing

[Kellermeister (Marcel)]

I try to control the lamella position of my venetian blinds with a fibaro fgm222 … but it just does not work. up and down is no problem, but changing the position of lamellas doesn’t work.

item-file:

Rollershutter EgWz_JalousieTV_Control "Jalousie TV [%s]" <rollershutter>  {channel="zwave:device:Razberry2:node17:blinds_control"}
Dimmer EgWz_JalousieTV_Control_Lamella "Jalousie TV Lamella [%s]" <rollershutter> {channel="zwave:device:Razberry2:node17:blinds_lamella"}

sitemap:

	Slider item=EgWz_JalousieTV_Control
	Slider item=EgWz_JalousieTV_Control_Lamella

parameters:
10 is set to 2 -> venetian blind mode with positioning
3 is set to 1 -> Blind position via fibar command

when i move the 1st slider, the blind goes up and down. when i move the second slider for lamella, nothing happens.

I just can not find the problem