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

Would be awesome Chris :grinning:
That’s the only issue which keeps me from upgrading to openHAB 2.

This would help a lot! I’m on OH2 and on sunny days I cannot adjust the blinds position… my wife is not amused :wink:

She should move to the UK and avoid the sun all-together :wink:

I’ve been looking at it this morning so hopefully will have something to play with today, but let’s see…

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/413

1 Like

This is now added - however I’ve only tested against some test classes I’ve created, and not a real life device.

I also still need to create a database update - this should all be merged later today I hope.

Note that this is being merged into the development branch and not the master version, so it is a bit of WIP still.

1 Like

Thank you! Happy to see a progress. Is there a good howto to get this dev branch into a jar file for my addons folder? Or how long would it take until it will be on master branch? I could test it with my fibaro device.

There are some instructions in the link below, but it’s a significant change to the current OH2 so you need to reinstall all things…

I would guess it’s a month or two away from being in the master - my plan was to look at merging this after version 2.1 is released.

Thank you for the link. As I can see this is a up-to-date version of the jar file (regarding timestamp) but the current changes regarding this issue are not in this jar file. Can you support a current jar file for testing or am I missinderstanding something.

I think the only thing that needs to be added is the database entries. I’ve updated one of the FGRM222 versions already but will add the other in the next day or so.

I’ve updated the second version of the device now…

many thanks for the progress on this @chris, looking forward to this in the master so can implement on my QNAP Openhab install.

@chris
Thank you for your help. I did uninstall the z-wave binding (I already was on Snapshot 2.1), deleted all my zwave things and then updated to the latest version from your link. I then “reinstalled” all my zwave things and set up the config for use with lamella. Now the blinds control for up and down is working as before. When I want to use the blinds lamella position I get an error (Command for unknown channel).

2017-06-12 13:27:54.132 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Command received zwave:device:78d06d54:node10:blinds_control --> DOWN
2017-06-12 13:27:54.136 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Creating new message for command SWITCH_MULTILEVEL_START_LEVEL_CHANGE
2017-06-12 13:27:23.624 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Command received zwave:device:78d06d54:node10:blinds_lamella --> 80
2017-06-12 13:27:23.627 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Command for unknown channel zwave:device:78d06d54:node10:blinds_lamella with PercentType

I have to say, that I don’t see the channels blinds_lamella or blinds_shutter on my device overview site.

I guess the first thing is to double check that you’re definately running the right version - check using Karaf console.

If that’s ok, then can you provide the XML for your device and I’ll double check a few things.

This is from my Karaf console

228 | Resolved |  80 | 2.1.0.201706112324     | ZWave Binding

The channel in the items config looks like this

{ channel="zwave:device:78d06d54:node10:blinds_lamella" }

An here you finde the node.xml
network_df2fea7a__node_10.xml (8.7 KB)

Please try again now…

Your zwave binding is not active, try to manually start it through karaf.

Thank you for your fast reply. I have tested now and the good news is, that blinds_lamella is now working in general. Problem there is 100% which is not recognised, values between 0-99 are allowed, but I’m fine with that.

BUT the blinds_control with DOWN / UP / STOP is no more working.

2017-06-12 20:33:00.901 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Command received zwave:device:78d06d54:node10:blinds_control --> UP
2017-06-12 20:33:00.903 [DEBUG] [erter.ZWaveMultiLevelSwitchConverter] - NODE 10: Command class SWITCH_MULTILEVEL not found when processing command on endpoint 0
2017-06-12 20:33:00.904 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: No messages returned from converter
2017-06-12 20:33:01.537 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Command received zwave:device:78d06d54:node10:blinds_control --> STOP
2017-06-12 20:33:01.538 [DEBUG] [erter.ZWaveMultiLevelSwitchConverter] - NODE 10: Command class SWITCH_MULTILEVEL not found when processing command on endpoint 0
2017-06-12 20:33:01.541 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: No messages returned from converter
2017-06-12 20:33:01.927 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Command received zwave:device:78d06d54:node10:blinds_control --> DOWN
2017-06-12 20:33:01.932 [DEBUG] [erter.ZWaveMultiLevelSwitchConverter] - NODE 10: Command class SWITCH_MULTILEVEL not found when processing command on endpoint 0
2017-06-12 20:33:01.938 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: No messages returned from converter

network_df2fea7a__node_10.xml (12.3 KB)

Ok, we can sort of fix this. The issue here is zwave only allows 0-99 so we’ll simply make it 0-98 and 100.

Well, interestingly in the XML there is no switch_multilevel command class - this seems consistent in both the XML files and it’s also not in the NIF (so the device isn’t reporting it) and it’s also not in the manual -:

So, I’m a bit confused why it ever worked…

I can likely add the up/down options to the shutter control…

I have six of those devices and I can also see UP/STOP/DOWN through a rollershutter item linked to blinds_control.
But I’m still on the snapshot binding (but preparing for moving to the dev branch)

2017-06-12 21:37:42.762 [ItemCommandEvent          ] - Item 'FibFGR222_Living_South' received command DOWN
2017-06-12 21:37:43.681 [ItemCommandEvent          ] - Item 'FibFGR222_Living_South' received command STOP
2017-06-12 21:37:45.139 [ItemCommandEvent          ] - Item 'FibFGR222_Living_South' received command UP

Thank you for your fast help. It was defenetly working before

Creating new message for command SWITCH_MULTILEVEL_START_LEVEL_CHANGE

may you can explain which are the right commands for blinds_control

I still don’t understand why the device doesn’t report this class. I agree that it seems it should be implemented, but it’s not reporting it from what I can see from the above…

Does your device show the same?