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

[chris (Chris Jackson)]

@Chri46

So we are looking at minimum Openhab 2.2

Yes - wasn’t that effectively your question? When is 2.2 going to be available? Or maybe I’ve misunderstood?

@Chri46

Does the snapshot release available now include the lamella support?

No - it’s in the development version only.

[Chri46 (Christian Berndt)]

… was hoping for a bug-fix release in 2.1, which as lamella support…

any plans to merge the development release with snapshot release for 2.2?

[Chri46 (Christian Berndt)]

@chris

I would like to get clarification on the inclusion of the development binding enabling lamella support to the 2.2 snapshot release of zwave binding, before moving to OH2.2 snapshots.
Also would the 2.1 dev binding work with OH2.2 snapshots.

Are there plans to support proprietary messages for FGRM-222 in OH2.2 binding?

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

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.

[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.