Strange issues with Fibaro FGD212 dimmer 2 on OH 2.4-snapshot

Hi all,

Since my OH 2.4 upgrade (from 2.3), I have an strange issue with my two FGD212 devices. On this FGD212 device (node 56), OH2 doesn’t detect the ON/OFF return state.
Indeed when I turn ON or OFF the physical switch linked to this FGD212 device, OH2 get no events (no events in events.log file and no UI updates).
On the other hand, OH2 get correctly the “Power meter” values (sensor_power channel) when I turn ON/OFF the physical switch.
I thought this issue was due to a hardware problem on my FGD212 device (node 56). But when I run another Smart home software (Home Assistant), the return state on my node 56 is OK.

With my second FGD212 device (node 51), OH2 get inconsistent “Power meter” values (sensor_power channel) after turn on/off the switch or dimming (dim 77% -> 111 watts, 38% -> 153 watts, 0% -> 19,7 watts, 38% -> 20,7 watts, 0% -> 20,4 watts, etc.) and return state is OK.

Can you help me please ?


  • Synology DS415+ / DSM 6.2.1-23824 Update 1
  • Docker 17.05.0-ce / Image ‘openhab/openhab:2.4.0-snapshot-amd64-debian’
  • OH 2.4.0 build #1407
  • Zwave binding

The database entry for that device has changed, so if you upgraded to the snapshot but did not delete and readd your device thing and adopted the new channels you may see that behaviour.
The channel for switch and dimmer itemtype is now switch_dimmer1 and is instantly updated through the binding and through the pyhsical switch.
Actually it is working 100% correct for the first time since I have this device :grinning:

Switch FibFGD212_1_Sw  { channel="zwave:device:uzb:node37:switch_dimmer1" }
Dimmer FibFGD212_1_Dim  { channel="zwave:device:uzb:node37:switch_dimmer1" }
1 Like

Hi @sihui,

I just deleted my FGD212 things from PaperUI (Configuration > Things > Trash/Bin icon) and after I ran a Zwave things scan in Paper UI (Inbox > Scan icon > Zwave binding) to (re)add my Zwave 51 and 56 nodes.

My items configuration is:

Dimmer  Dimmer_SalonPlafonnier    "Plafonnier salon" <light>  (groupDimmerSalonPlafonnier)  [ "Lighting" ]    { channel = "zwave:device:AEO_ZW090_C:node51:switch_dimmer1", homekit="Lighting" }
Switch  Dimmer_SalonPlafonnier_Switch    "Plafonnier - On/Off" <light> (groupDimmerSalonPlafonnier)              { channel = "zwave:device:AEO_ZW090_C:node51:switch_dimmer1" }
Number  Dimmer_SalonPlafonnier_Energy_Power    "Conso [%.1f W]"  <heating> (groupDimmerSalonPlafonnier)               { channel = "zwave:device:AEO_ZW090_C:node51:sensor_power" }
Number  Dimmer_SalonPlafonnier_Energy_Total    "Conso totale [%.2f KWh]"  <heating> (groupDimmerSalonPlafonnier)               { channel = "zwave:device:AEO_ZW090_C:node51:meter_kwh" }
Group groupOutdoorLights "Lampes exterieures" <light> (groupExterieur)
Dimmer  DimmerOutdoorLights    "Lampes exterieures" <light>  (groupOutdoorLights)   [ "Lighting" ]           { channel = "zwave:device:AEO_ZW090_C:node56:switch_dimmer1" }
Switch  DimmerOutdoorLights_Switch    "Lampes exterieures - On/Off" <light> (groupOutdoorLights)              { channel = "zwave:device:AEO_ZW090_C:node56:switch_dimmer1" }
Number  DimmerOutdoorLights_Energy_Power    "Conso [%.1f W]"  <heating> (groupOutdoorLights)               { channel = "zwave:device:AEO_ZW090_C:node56:sensor_power" }
Number  DimmerOutdoorLights_Energy_Total    "Conso totale [%.2f KWh]"  <heating> (groupOutdoorLights)               { channel = "zwave:device:AEO_ZW090_C:node56:meter_kwh" }

My Dimmer and Switch items are well linked to the switch_dimmer1 channel. But I have always the sames issues.
What is wrong ?


Don’t know :smiley:

This is my log for updates from the GUI:

2018-11-17 10:07:07.065 [ome.event.ItemCommandEvent] - Item 'FibFGD212_1_Sw' received command ON
2018-11-17 10:07:07.737 [nt.ItemStatePredictedEvent] - FibFGD212_1_Sw predicted to become ON
2018-11-17 10:07:07.760 [vent.ItemStateChangedEvent] - FibFGD212_1_Sw changed from OFF to ON
2018-11-17 10:07:08.591 [vent.ItemStateChangedEvent] - FibFGD212_1_Dim changed from 0 to 100
2018-11-17 10:07:10.504 [ome.event.ItemCommandEvent] - Item 'FibFGD212_1_Sw' received command OFF
2018-11-17 10:07:11.019 [nt.ItemStatePredictedEvent] - FibFGD212_1_Sw predicted to become OFF
2018-11-17 10:07:11.042 [vent.ItemStateChangedEvent] - FibFGD212_1_Sw changed from ON to OFF
2018-11-17 10:07:11.602 [vent.ItemStateChangedEvent] - FibFGD212_1_Dim changed from 100 to 0
2018-11-17 10:07:29.869 [ome.event.ItemCommandEvent] - Item 'FibFGD212_1_Dim' received command 54
2018-11-17 10:07:29.891 [nt.ItemStatePredictedEvent] - FibFGD212_1_Dim predicted to become 54
2018-11-17 10:07:29.913 [vent.ItemStateChangedEvent] - FibFGD212_1_Dim changed from 0 to 54
2018-11-17 10:07:30.501 [vent.ItemStateChangedEvent] - FibFGD212_1_Sw changed from OFF to ON
2018-11-17 10:07:33.501 [ome.event.ItemCommandEvent] - Item 'FibFGD212_1_Dim' received command 100
2018-11-17 10:07:33.525 [nt.ItemStatePredictedEvent] - FibFGD212_1_Dim predicted to become 100
2018-11-17 10:07:33.547 [vent.ItemStateChangedEvent] - FibFGD212_1_Dim changed from 54 to 100
2018-11-17 10:07:36.067 [ome.event.ItemCommandEvent] - Item 'FibFGD212_1_Dim' received command 0
2018-11-17 10:07:36.354 [nt.ItemStatePredictedEvent] - FibFGD212_1_Dim predicted to become 0
2018-11-17 10:07:36.376 [vent.ItemStateChangedEvent] - FibFGD212_1_Dim changed from 100 to 0
2018-11-17 10:07:37.147 [vent.ItemStateChangedEvent] - FibFGD212_1_Sw changed from ON to OFF

Those are from the physical switch:

2018-11-17 10:07:47.084 [vent.ItemStateChangedEvent] - FibFGD212_1_Sw changed from OFF to ON
2018-11-17 10:07:47.106 [vent.ItemStateChangedEvent] - FibFGD212_1_Dim changed from 0 to 100
2018-11-17 10:07:50.628 [vent.ItemStateChangedEvent] - FibFGD212_1_Sw changed from ON to OFF
2018-11-17 10:07:50.650 [vent.ItemStateChangedEvent] - FibFGD212_1_Dim changed from 100 to 0
2018-11-17 10:07:52.631 [vent.ItemStateChangedEvent] - FibFGD212_1_Num changed from 16 to 12
2018-11-17 10:07:53.230 [vent.ItemStateChangedEvent] - FibFGD212_1_Num changed from 12 to 13
2018-11-17 10:07:53.694 [vent.ItemStateChangedEvent] - FibFGD212_1_Sw changed from OFF to ON
2018-11-17 10:07:54.208 [vent.ItemStateChangedEvent] - FibFGD212_1_Dim changed from 0 to 60
2018-11-17 10:07:56.241 [vent.ItemStateChangedEvent] - FibFGD212_1_Num changed from 13 to 12
2018-11-17 10:07:56.843 [vent.ItemStateChangedEvent] - FibFGD212_1_Dim changed from 60 to 1
2018-11-17 10:07:56.945 [vent.ItemStateChangedEvent] - FibFGD212_1_Num changed from 12 to 13
2018-11-17 10:08:00.179 [vent.ItemStateChangedEvent] - FibFGD212_1_Num changed from 13 to 16
2018-11-17 10:08:00.872 [vent.ItemStateChangedEvent] - FibFGD212_1_Sw changed from ON to OFF
2018-11-17 10:08:00.894 [vent.ItemStateChangedEvent] - FibFGD212_1_Dim changed from 1 to 0

Everything is reflected properly in the GUI.

This device has a lot of config parameters, so make sure those are set properly, for example


(No. 20 of course only if you have a momentary switch connected)

Also make sure you have the Lifeline association group set to your controller.

I don’t think the configuration parameters are wrong because all was fine with OH 2.3. The upgrade can’t have updated the configuration parameters.

What is your OH version ?

You must set association group 1 and 2 to Controller.

But the config parameters in the database could have changed and for example if you had a parameter which is now out of bounds you need to set it to a proper value.

I’m always using snapshots, at the moment #1407.

Group 2 does not go to the controller at all, that one is for the world outside of openHAB.

Well, if you associate it to the controller it does, and viola, local state changes appear in OH2 again.
See this post.

I don’t have Group 2 set and it works :smiley:

Yah, it used to work without for me as well, but it broke in one of my SNAPSHOT updates in late October early November. Never found out why. It also happened to an Nexa/Everspring on/off wall switch I have. One nice side effect after setting AG1 and AG2 of that device to Controller was, beside that it started working again, that local state changes was sent to OH2 instantaneously without the usual 2s delay :slight_smile:

Hmm, never saw any delays greater than a couple of milliseconds.
Are you using PaperUI to update parameters? If yes, bad idea, use HABmin …

This 2s delay is particular to that device when you use it as a scene controller. (well, minimal value is actual 3s)

Routing AG2 to the controller bypassed that, probably because, as you were saying, that AG>1 is normally intended for devices outside of OH.
I don’t know exactly what, but there is something strange going on with the Lifeline/AG1 association group…
I thought that was what Zwave + brought to the table; Automatic Lifeline association?

Yes, and that was introduced with the rework of the zwave binding “development” version which is now in the main branch (at least for M4 and newer)

Hi All

I have this same issue on 2.5 snapshot, controller is set for Group 1. I get this predicted messaged also and my items now wont turn on when upgrading from 2.4 snapshot to 2.5 snapshot. All items were deleted and readded.
My Controllers are on, Lifeline set for AG1 and my things are also all online

Has something changed again in the way items are linked?

My items were defined like this in 2.4 snapshot

/*ZWave Dimmer 2 Kitchen Lights*/
Switch KitchenSw1  "Kitchen"                                           (gAllLights,gInsideLights)                [ "Lighting" ]     { channel="zwave:device:c5b08a5b:node5:switch_dimmer" }
Dimmer KitchenDim1 "Kitchen [%d %%]"                                                                             [ "Lighting" ]     { channel="zwave:device:c5b08a5b:node5:switch_dimmer" }
Number KitchenNum1 "Kitchen - Current Consumption [%.1f W]"            (gAllLightsUsage)                                            { channel="zwave:device:c5b08a5b:node5:meter_watts" }
Number KitchenNum2 "Kitchen - Usage [%.1f kW]"                         (gPowerUsage)                                                { channel="zwave:device:c5b08a5b:node5:meter_kwh" }

None of the items are switching on

13:10:15.350 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'KitchenDim1' received command 41
13:10:15.352 [INFO ] [arthome.event.ItemStatePredictedEvent] - KitchenDim1 predicted to become 0
13:10:17.376 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'KitchenSw1' received command ON
13:10:17.378 [INFO ] [arthome.event.ItemStatePredictedEvent] - KitchenSw1 predicted to become OFF
13:10:22.326 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'KitchenSw1' received command ON
13:10:22.328 [INFO ] [arthome.event.ItemStatePredictedEvent] - KitchenSw1 predicted to become OFF
13:10:23.071 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'KitchenSw1' received command ON
13:10:23.073 [INFO ] [arthome.event.ItemStatePredictedEvent] - KitchenSw1 predicted to become OFF
13:10:24.185 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'KitchenSw1' received command ON
13:10:24.187 [INFO ] [arthome.event.ItemStatePredictedEvent] - KitchenSw1 predicted to become OFF

This post fixed my issues with the 2.4 Stable release Zwave binding :smiley: that darn pesky 1!!!

1 Like

Hi guys!

I have the same issue on 2.4 and 2.5 OpenHab with all my FGD212 devices.
When I turn on/off the physical switch on ui I see only power updates.
Sometimes the switch on the ui changes, but very seldom.

I tried to set switch_dimmer/switch_dimmer1 but it doesn’t help.
In Paper UI I see strange model for dimmers

Dimmer Switch 1


Sensor (power) 1


Dimmer Switch 2


Sensor (power)


When I updated OH to 2.4
I removed all Z-wave devices, then removed binding then reinstalled binding then searched and added all things again.

Who can help me?


For me the following steps got the FGD212 working:

  • set the log level to debug for zwave
  • check the openhab log for updates with nodeXX:switch_dimmerX
  • if not make sure the zwave controller is set in the association group
  • check the events log for items updates
  • i had to remove profile=follow from the items configuration
  • finally after adding switchSupport parameter in the sitemap things started working.