Z-wave Fibaro FGS223 disable energy reporting

[idserda (Jeroen)]

In an effort to reduce the traffic on my z-wave network by disabling all power/energy reports from the Fibaro FGS223’s (Double Switch 2) I have I seemed to have reached the opposite: every node is sending its energy consumption (meter_kwh1 and meter_kwh2) a few times a second now. All relevant parameters (51 up to 59) are set to 0. I’ve tried setting to the maximum values but that also does not seem to help. Configuration for the node and z-wave debug logs are attached. Any ideas?

node21.xml (28.3 KB)
zwave-node21.log.xml (44 KB)

[sihui]

Workaround:

Partly long reaction times for switches over z-wave

i think i habe solve the problem … it is probably a problem of the device “fibaro fgs223”. if i set parameter 53 & 57 to 0 (disable of energy report, like describded in the manual), then the energy will be send serveral times per second. if i set parameter 53 & 57 to 1000, the problem is no longer there. (i’ve write this problem to the support team of fibaro)

Not nice but better than nothing

[sihui]

@idserda

FGS223

Just to proove that it’s not a general problem:

2018-04-10 19:37:46.718 [GroupItemStateChangedEvent] - gEnergyW changed from 10.8 to 13.4 through FibFGS223_1_watt2
2018-04-10 19:37:46.721 [vent.ItemStateChangedEvent] - FibFGS223_1_watt2 changed from 0 to 2.6
2018-04-10 22:12:48.445 [vent.ItemStateChangedEvent] - FibFGS223_1_watt2 changed from 2.6 to 0
2018-04-10 22:12:48.447 [GroupItemStateChangedEvent] - gEnergyW changed from 5.8 to 3.2 through FibFGS223_1_watt2
2018-04-11 19:57:01.118 [vent.ItemStateChangedEvent] - FibFGS223_1_watt2 changed from 0 to 2.7
2018-04-11 19:57:01.121 [GroupItemStateChangedEvent] - gEnergyW changed from 3.2 to 5.9 through FibFGS223_1_watt2
2018-04-11 20:57:00.930 [vent.ItemStateChangedEvent] - FibFGS223_1_watt2 changed from 2.7 to 2.6
2018-04-11 20:57:00.932 [GroupItemStateChangedEvent] - gEnergyW changed from 16.4 to 16.3 through FibFGS223_1_watt2
2018-04-11 23:13:58.001 [vent.ItemStateChangedEvent] - FibFGS223_1_watt2 changed from 2.6 to 0
2018-04-11 23:13:58.005 [GroupItemStateChangedEvent] - gEnergyW changed from 5.8 to 3.2 through FibFGS223_1_watt2
2018-04-11 23:14:19.239 [GroupItemStateChangedEvent] - gEnergyW changed from 10.6 to 13.2 through FibFGS223_1_watt2
2018-04-11 23:14:19.244 [vent.ItemStateChangedEvent] - FibFGS223_1_watt2 changed from 0 to 2.6
2018-04-11 23:14:33.300 [vent.ItemStateChangedEvent] - FibFGS223_1_watt2 changed from 2.6 to 0
2018-04-11 23:14:33.305 [GroupItemStateChangedEvent] - gEnergyW changed from 13.2 to 10.6 through FibFGS223_1_watt2

[idserda (Jeroen)]

Thanks, that seems to work for now!

So you think this is a bug in the Fibaro firmware? Have you heard anything from them?

[sihui]

@idserda

So you think this is a bug in the Fibaro firmware?

I am on firmware 3.2 and don’t have that problem (that’s the reason I posted the events log from a whole day)

@idserda

Have you heard anything from them?

You need to ask @Kellermeister