Warning: Fibaro switch 2 energy reporting interval bug can flood your network!

Configuration Z-Wave
1

Hi,

I am having a lot of trouble with my fibaro single/double switch 2, which are node 19, 23 and 25 in my log below.
They spam my z-wave network every second, and makes it slow to use.
I have tried to change parameter 50, 51, 53, 54, 55, 57, 58 og 59 to 0, and that does not help.
I have also tried to change parameter 50 & 54 t0 100, 51 & 55 to 120 and 53, 57, 58 & 59 to 32000, but neither that helps.
I don’t need to read the energy of these switches. Not having this problem with my fibaro dimmer 2.

Does anyone have any suggestion?

Firmware 3.3, all included unsecure.

These two values that spams my network. 50-1-value-65537, 50-2-value-65537.
image
image

2021-12-25 12:27:13.898 INFO ZWAVE: Node 25: value updated: 50-1-value-65537 0.13 => 0.13
2021-12-25 12:27:14.475 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 0.15 => 0.15
2021-12-25 12:27:14.683 INFO ZWAVE: Node 23: value updated: 50-1-value-65537 0.02 => 0.02
2021-12-25 12:27:14.761 INFO ZWAVE: Node 23: value updated: 50-2-value-65537 0 => 0
2021-12-25 12:27:14.898 INFO ZWAVE: Node 25: value updated: 50-1-value-65537 0.13 => 0.13
2021-12-25 12:27:15.473 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 0.15 => 0.15
2021-12-25 12:27:15.684 INFO ZWAVE: Node 23: value updated: 50-1-value-65537 0.02 => 0.02
2021-12-25 12:27:15.763 INFO ZWAVE: Node 23: value updated: 50-2-value-65537 0 => 0
2021-12-25 12:27:15.899 INFO ZWAVE: Node 25: value updated: 50-1-value-65537 0.13 => 0.13
2021-12-25 12:27:16.473 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 0.15 => 0.15
2021-12-25 12:27:16.683 INFO ZWAVE: Node 23: value updated: 50-1-value-65537 0.02 => 0.02
2021-12-25 12:27:16.763 INFO ZWAVE: Node 23: value updated: 50-2-value-65537 0 => 0
2021-12-25 12:27:16.897 INFO ZWAVE: Node 25: value updated: 50-1-value-65537 0.13 => 0.13
2021-12-25 12:27:17.474 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 0.15 => 0.15
2021-12-25 12:27:17.685 INFO ZWAVE: Node 23: value updated: 50-1-value-65537 0.02 => 0.02
2021-12-25 12:27:17.763 INFO ZWAVE: Node 23: value updated: 50-2-value-65537 0 => 0
2021-12-25 12:27:17.897 INFO ZWAVE: Node 25: value updated: 50-1-value-65537 0.13 => 0.13
2021-12-25 12:27:18.474 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 0.15 => 0.15
2021-12-25 12:27:18.683 INFO ZWAVE: Node 23: value updated: 50-1-value-65537 0.02 => 0.02
2021-12-25 12:27:18.762 INFO ZWAVE: Node 23: value updated: 50-2-value-65537 0 => 0
2021-12-25 12:27:18.899 INFO ZWAVE: Node 25: value updated: 50-1-value-65537 0.13 => 0.13
2021-12-25 12:27:19.473 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 0.15 => 0.15
2021-12-25 12:27:19.683 INFO ZWAVE: Node 23: value updated: 50-1-value-65537 0.02 => 0.02
2021-12-25 12:27:19.764 INFO ZWAVE: Node 23: value updated: 50-2-value-65537 0 => 0
2021-12-25 12:27:19.897 INFO ZWAVE: Node 25: value updated: 50-1-value-65537 0.13 => 0.13
2021-12-25 12:27:20.473 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 0.15 => 0.15
2021-12-25 12:27:20.683 INFO ZWAVE: Node 23: value updated: 50-1-value-65537 0.02 => 0.02
2021-12-25 12:27:20.763 INFO ZWAVE: Node 23: value updated: 50-2-value-65537 0 => 0
2021-12-25 12:27:20.899 INFO ZWAVE: Node 25: value updated: 50-1-value-65537 0.13 => 0.13
2021-12-25 12:27:21.474 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 0.15 => 0.15
2021-12-25 12:27:21.683 INFO ZWAVE: Node 23: value updated: 50-1-value-65537 0.02 => 0.02
2021-12-25 12:27:21.763 INFO ZWAVE: Node 23: value updated: 50-2-value-65537 0 => 0
2021-12-25 12:27:21.897 INFO ZWAVE: Node 25: value updated: 50-1-value-65537 0.13 => 0.13
2021-12-25 12:27:22.475 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 0.15 => 0.15
2021-12-25 12:27:22.685 INFO ZWAVE: Node 23: value updated: 50-1-value-65537 0.02 => 0.02
2021-12-25 12:27:22.762 INFO ZWAVE: Node 23: value updated: 50-2-value-65537 0 => 0
2021-12-25 12:27:22.897 INFO ZWAVE: Node 25: value updated: 50-1-value-65537 0.13 => 0.13
2021-12-25 12:27:23.474 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 0.15 => 0.15
2021-12-25 12:27:23.683 INFO ZWAVE: Node 23: value updated: 50-1-value-65537 0.02 => 0.02
2021-12-25 12:27:23.762 INFO ZWAVE: Node 23: value updated: 50-2-value-65537 0 => 0
2021-12-25 12:27:23.899 INFO ZWAVE: Node 25: value updated: 50-1-value-65537 0.13 => 0.13
2021-12-25 12:27:24.475 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 0.15 => 0.15
2021-12-25 12:27:24.684 INFO ZWAVE: Node 23: value updated: 50-1-value-65537 0.02 => 0.02
2021-12-25 12:27:24.762 INFO ZWAVE: Node 23: value updated: 50-2-value-65537 0 => 0
2021-12-25 12:27:24.897 INFO ZWAVE: Node 25: value updated: 50-1-value-65537 0.13 => 0.13
2021-12-25 12:27:25.473 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 0.15 => 0.15
2021-12-25 12:27:25.684 INFO ZWAVE: Node 23: value updated: 50-1-value-65537 0.02 => 0.02
2021-12-25 12:27:25.761 INFO ZWAVE: Node 23: value updated: 50-2-value-65537 0 => 0
2021-12-25 12:27:25.897 INFO ZWAVE: Node 25: value updated: 50-1-value-65537 0.13 => 0.13
2021-12-25 12:27:26.473 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 0.15 => 0.15
2021-12-25 12:27:26.683 INFO ZWAVE: Node 23: value updated: 50-1-value-65537 0.02 => 0.02
2021-12-25 12:27:26.761 INFO ZWAVE: Node 23: value updated: 50-2-value-65537 0 => 0
2021-12-25 12:27:26.897 INFO ZWAVE: Node 25: value updated: 50-1-value-65537 0.13 => 0.13
2021-12-25 12:27:27.475 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 0.15 => 0.15
2021-12-25 12:27:27.684 INFO ZWAVE: Node 23: value updated: 50-1-value-65537 0.02 => 0.02
2021-12-25 12:27:27.763 INFO ZWAVE: Node 23: value updated: 50-2-value-65537 0 => 0
2021-12-25 12:27:27.897 INFO ZWAVE: Node 25: value updated: 50-1-value-65537 0.13 => 0.13
2

I found a solution now.
I can set parameter 50, 51, 58 and 59 on the single switch to 0, but I have to set parameter 53 to 31999.
Found the solution here:

When I change parameter 53 to 0, node 19 spams every second

2021-12-30 00:28:25.989 INFO ZWAVE: Calling api writeValue with args: [
{ nodeId: 19, commandClass: 112, endpoint: 0, property: 53 },
0,
{},
[length]: 3
]
2021-12-30 00:28:25.991 INFO ZWAVE: Writing 0 to 19-112-0-53
2021-12-30 00:28:26.082 INFO ZWAVE: Node 19: value updated: 112-0-53 31999 => 0
2021-12-30 00:28:26.083 INFO ZWAVE: Success zwave api call writeValue true
2021-12-30 00:28:26.735 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:27.224 INFO ZWAVE: Node 19: value updated: 112-0-53 0 => 0
2021-12-30 00:28:27.734 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:28.735 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:29.735 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:30.734 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:31.735 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:32.734 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:33.734 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:34.734 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:35.736 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:36.527 INFO ZWAVE: Node 9: metadata updated: 49-2-Air temperature
2021-12-30 00:28:36.528 INFO ZWAVE: Node 9: value updated: 49-2-Air temperature 21.2 => 21.2

If I change parameter 53 to 32000, node 19 spams every second

2021-12-30 00:28:37.106 INFO ZWAVE: Calling api writeValue with args: [
{ nodeId: 19, commandClass: 112, endpoint: 0, property: 53 },
32000,
{},
[length]: 3
]
2021-12-30 00:28:37.107 INFO ZWAVE: Writing 32000 to 19-112-0-53
2021-12-30 00:28:45.068 INFO ZWAVE: Node 19: value updated: 112-0-53 0 => 32000
2021-12-30 00:28:45.069 INFO ZWAVE: Success zwave api call writeValue true
2021-12-30 00:28:49.119 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:49.287 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:51.640 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:52.832 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:53.571 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:53.730 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:53.809 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:54.002 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:54.519 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:54.705 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:55.734 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:56.735 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:57.734 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:58.224 INFO ZWAVE: Node 19: value updated: 112-0-53 32000 => 32000
2021-12-30 00:28:58.734 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:28:59.734 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:29:00.736 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:29:01.734 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:29:02.734 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:29:03.734 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:29:04.735 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:29:05.992 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:29:06.734 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05
2021-12-30 00:29:07.504 INFO ZWAVE: Node 34: metadata updated: 49-8-Air temperature
2021-12-30 00:29:07.506 INFO ZWAVE: Node 34: value updated: 49-8-Air temperature 38.3 => 39
2021-12-30 00:29:07.735 INFO ZWAVE: Node 19: value updated: 50-1-value-65537 1.05 => 1.05

If I change parameter 53 to 31999, the spam stops :slight_smile:

2021-12-30 00:29:07.787 INFO ZWAVE: Calling api writeValue with args: [
{ nodeId: 19, commandClass: 112, endpoint: 0, property: 53 },
31999,
{},
[length]: 3
]
2021-12-30 00:29:07.788 INFO ZWAVE: Writing 31999 to 19-112-0-53
2021-12-30 00:29:07.837 INFO ZWAVE: Node 19: value updated: 112-0-53 32000 => 31999
2021-12-30 00:29:07.838 INFO ZWAVE: Success zwave api call writeValue true
2021-12-30 00:29:08.892 INFO ZWAVE: Node 19: value updated: 112-0-53 31999 => 31999
2021-12-30 00:29:35.796 INFO ZWAVE: Node 33: metadata updated: 49-11-Air temperature
2021-12-30 00:29:35.798 INFO ZWAVE: Node 33: value updated: 49-11-Air temperature -106.2 => -106.76

Looks like there is a bug in the fibaro switch 2 firmware, not being able to turn off energy reporting. I have make a ticket to fibaro support, so lets see what they says.

3

Fibaro sent my findings to the programmers, and will probably make a new firmware.
Since I don’t have a fibaro gateway, I have to send my unit back to them to update it for me, which is not going to happen. Hate that they don’t release firmware updates… :rage:

4

Thanks for looking into this and reporting it! (Although I agree with your frustration about the impossibility of updates.)

This explains a really nasty situation I ran into: I have about 40 of these and I set them all to report times of 0 (since the manual says this should shut them off). However, I started getting continuous reports from them all. This flooded my Z-wave network to the point that I could not change the parameters any more. I had to shut off electricity to the whole house and then turn on the circuits 1-by-1 to get a usable network and reconfigure them…
-David

5

Come to think of it, maybe you should rename this thread as “Warning: Fibaro dimmer power reporting interval bug can flood your network!”

6

I can rename it, but I had the problem with fibaro switch 2. Have you had any problems with fibaro dimmer 2 also?
My Fibaro dimmer 2 works fine to turn off energy reporting

7

I have a mixture of both, so I don’t know which one (or if both) are a problem. I agree that the title should be clear!

8

If you use Z-wavejs2mqtt you can go to debug on the left side, and you see everything that is sendt on your network in realtime. Thats how I found out the fibaro switches was spamming my network.
You can also click on each node and open statistics, and see how many commands RX you have from the node.

9

Thanks. Unfortunately I’m just using the built-in zwave and there are so many nodes that it is really hard to figure out how many are coming from each with its logging.