Fibaro nodes not supporting ZWavePlusInfoCmd_Get and ZWavePlusInfoCmd_Get command classes, how to disable them permanently

Configuration Z-Wave
1

Yesterday I installed a Fibaro Dimmer and 5 Fibaro Wall Plugs.
The dimmer has two switches: S1 and S2. S2 is associated with the 5 wall plugs, to switch the lights in the living room. S2 switches al the 5 wall plugs nicely via this assocation. All the lights turn on or off together.

A Raspberry Pi 4, with 2Gb memory and Z Wave me UZB stick is running Home Assistant core (docker) and acts as my Z Wave controller. It’s also located in the living room. I can switch the plugs indivudually, use the the dimmer (S1), create associations, etc.
Switching the wall plugs individually works ok.

The problem I have is when I’d like to switch the 5 wall plugs at once (like the S2 assocation). The result is that 3 or 4 of the plugs will switch, the others after a long time. I tried a scene, a group, an automation with 5 entities.

An example of this problem, only switching 3 nodes to off:

2020-05-05 14:06:29.818 Info, Node007, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - False
2020-05-05 14:06:29.818 Info, Node007, SwitchBinary::Set - Setting node 7 to Off
2020-05-05 14:06:29.818 Detail, Node007, Queuing (Send) SwitchBinaryCmd_Set (Node=7): 0x01, 0x0a, 0x00, 0x13, 0x07, 0x03, 0x25, 0x01, 0x00, 0x25, 0x94, 0x77
2020-05-05 14:06:29.818 Detail, Node007, Queuing (Send) SwitchBinaryCmd_Get (Node=7): 0x01, 0x09, 0x00, 0x13, 0x07, 0x02, 0x25, 0x02, 0x25, 0x95, 0x77
2020-05-05 14:06:29.818 Detail, 
2020-05-05 14:06:29.819 Info, Node007, Sending (Send) message (Callback ID=0x94, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=7): 0x01, 0x0a, 0x00, 0x13, 0x07, 0x03, 0x25, 0x01, 0x00, 0x25, 0x94, 0x77
2020-05-05 14:06:29.821 Info, Node010, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - False
2020-05-05 14:06:29.821 Info, Node010, SwitchBinary::Set - Setting node 10 to Off
2020-05-05 14:06:29.821 Detail, Node010, Queuing (Send) SwitchBinaryCmd_Set (Node=10): 0x01, 0x0a, 0x00, 0x13, 0x0a, 0x03, 0x25, 0x01, 0x00, 0x25, 0x96, 0x78
2020-05-05 14:06:29.821 Detail, Node010, Queuing (Send) SwitchBinaryCmd_Get (Node=10): 0x01, 0x09, 0x00, 0x13, 0x0a, 0x02, 0x25, 0x02, 0x25, 0x97, 0x78
2020-05-05 14:06:29.824 Info, Node009, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - False
2020-05-05 14:06:29.825 Info, Node009, SwitchBinary::Set - Setting node 9 to Off
2020-05-05 14:06:29.825 Detail, Node009, Queuing (Send) SwitchBinaryCmd_Set (Node=9): 0x01, 0x0a, 0x00, 0x13, 0x09, 0x03, 0x25, 0x01, 0x00, 0x25, 0x98, 0x75
2020-05-05 14:06:29.825 Detail, Node009, Queuing (Send) SwitchBinaryCmd_Get (Node=9): 0x01, 0x09, 0x00, 0x13, 0x09, 0x02, 0x25, 0x02, 0x25, 0x99, 0x75
2020-05-05 14:06:29.826 Detail, Node007,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-05-05 14:06:29.826 Detail, Node007,   ZW_SEND_DATA delivered to Z-Wave stack
2020-05-05 14:06:29.846 Detail, Node007,   Received: 0x01, 0x05, 0x00, 0x13, 0x94, 0x00, 0x7d
2020-05-05 14:06:29.846 Detail, Node007,   ZW_SEND_DATA Request with callback ID 0x94 received (expected 0x94)
2020-05-05 14:06:29.846 Info, Node007, Request RTT 27 Average Request RTT 32
2020-05-05 14:06:29.846 Detail,   Expected callbackId was received
2020-05-05 14:06:29.846 Detail,   Expected reply was received
2020-05-05 14:06:29.846 Detail,   Message transaction complete
2020-05-05 14:06:29.846 Detail, 
2020-05-05 14:06:29.846 Detail, Node007, Removing current message
2020-05-05 14:06:29.846 Detail, 
2020-05-05 14:06:29.846 Info, Node007, Sending (Send) message (Callback ID=0x95, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=7): 0x01, 0x09, 0x00, 0x13, 0x07, 0x02, 0x25, 0x02, 0x25, 0x95, 0x77
2020-05-05 14:06:29.854 Detail, Node007,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-05-05 14:06:29.854 Detail, Node007,   ZW_SEND_DATA delivered to Z-Wave stack
2020-05-05 14:06:29.872 Detail, Node007,   Received: 0x01, 0x05, 0x00, 0x13, 0x95, 0x00, 0x7c
2020-05-05 14:06:29.872 Detail, Node007,   ZW_SEND_DATA Request with callback ID 0x95 received (expected 0x95)
2020-05-05 14:06:29.872 Info, Node007, Request RTT 25 Average Request RTT 28
2020-05-05 14:06:29.872 Detail,   Expected callbackId was received
2020-05-05 14:06:29.886 Detail, Node007,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x07, 0x03, 0x25, 0x03, 0x00, 0xc1, 0x00, 0x13
2020-05-05 14:06:29.886 Detail, 
2020-05-05 14:06:29.886 Info, Node007, Response RTT 39 Average Response RTT 39
2020-05-05 14:06:29.886 Info, Node007, Received SwitchBinary report from node 7: level=Off
2020-05-05 14:06:29.886 Detail, Node007, Refreshed Value: old value=true, new value=false, type=bool
2020-05-05 14:06:29.887 Detail, Node007, Changes to this value are not verified
2020-05-05 14:06:29.887 Detail, Node007,   Expected reply and command class was received
2020-05-05 14:06:29.887 Detail, Node007,   Message transaction complete
2020-05-05 14:06:29.887 Detail, 
2020-05-05 14:06:29.887 Detail, Node007, Removing current message
2020-05-05 14:06:29.887 Detail, Node007, Notification: ValueChanged
2020-05-05 14:06:29.894 Detail, 
2020-05-05 14:06:29.894 Info, Node010, Sending (Send) message (Callback ID=0x96, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=10): 0x01, 0x0a, 0x00, 0x13, 0x0a, 0x03, 0x25, 0x01, 0x00, 0x25, 0x96, 0x78
2020-05-05 14:06:29.901 Detail, Node010,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-05-05 14:06:29.901 Detail, Node010,   ZW_SEND_DATA delivered to Z-Wave stack
2020-05-05 14:06:29.944 Detail, Node010,   Received: 0x01, 0x05, 0x00, 0x13, 0x96, 0x00, 0x7f
2020-05-05 14:06:29.944 Detail, Node010,   ZW_SEND_DATA Request with callback ID 0x96 received (expected 0x96)
2020-05-05 14:06:29.944 Info, Node010, Request RTT 49 Average Request RTT 196
2020-05-05 14:06:29.944 Detail,   Expected callbackId was received
2020-05-05 14:06:29.944 Detail,   Expected reply was received
2020-05-05 14:06:29.944 Detail,   Message transaction complete
2020-05-05 14:06:29.944 Detail, 
2020-05-05 14:06:29.944 Detail, Node010, Removing current message
2020-05-05 14:06:29.944 Detail, 
2020-05-05 14:06:29.944 Info, Node010, Sending (Send) message (Callback ID=0x97, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=10): 0x01, 0x09, 0x00, 0x13, 0x0a, 0x02, 0x25, 0x02, 0x25, 0x97, 0x78
2020-05-05 14:06:29.953 Detail, Node010,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-05-05 14:06:29.953 Detail, Node010,   ZW_SEND_DATA delivered to Z-Wave stack
2020-05-05 14:06:30.159 Detail, Node010,   Received: 0x01, 0x05, 0x00, 0x13, 0x97, 0x00, 0x7e
2020-05-05 14:06:30.159 Detail, Node010,   ZW_SEND_DATA Request with callback ID 0x97 received (expected 0x97)
2020-05-05 14:06:30.159 Info, Node010, Request RTT 215 Average Request RTT 205
2020-05-05 14:06:30.159 Detail,   Expected callbackId was received
2020-05-05 14:06:30.609 Detail, Node007,   Received: 0x01, 0x0e, 0x00, 0x04, 0x00, 0x07, 0x06, 0x31, 0x05, 0x04, 0x22, 0x00, 0x00, 0xbf, 0x00, 0x59
2020-05-05 14:06:30.609 Detail, 
2020-05-05 14:06:30.609 Info, Node007, Received SensorMultiLevel report from node 7, instance 1, Power: value=0.0W
2020-05-05 14:06:30.609 Detail, Node007, Refreshed Value: old value=15.9, new value=0.0, type=decimal
2020-05-05 14:06:30.609 Detail, Node007, Changes to this value are not verified
2020-05-05 14:06:30.609 Detail, Node007, Notification: ValueChanged
2020-05-05 14:06:30.727 Detail, Node010,   Received: 0x01, 0x0e, 0x00, 0x04, 0x00, 0x0a, 0x06, 0x31, 0x05, 0x04, 0x22, 0x00, 0x00, 0xcd, 0x00, 0x26
2020-05-05 14:06:30.727 Detail, 
2020-05-05 14:06:30.727 Info, Node010, Response RTT 783 Average Response RTT 644
2020-05-05 14:06:30.727 Info, Node010, Received SensorMultiLevel report from node 10, instance 1, Power: value=0.0W
2020-05-05 14:06:30.727 Detail, Node010, Refreshed Value: old value=12.1, new value=0.0, type=decimal
2020-05-05 14:06:30.727 Detail, Node010, Changes to this value are not verified
2020-05-05 14:06:30.727 Detail, Node010, Notification: ValueChanged
2020-05-05 14:06:39.944 Error, Node010, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-05-05 14:06:39.944 Detail, Node010, Removing current message
2020-05-05 14:06:39.944 Detail, Node010, Notification: Notification - TimeOut
2020-05-05 14:06:39.947 Detail, 
2020-05-05 14:06:39.947 Info, Node009, Sending (Send) message (Callback ID=0x98, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=9): 0x01, 0x0a, 0x00, 0x13, 0x09, 0x03, 0x25, 0x01, 0x00, 0x25, 0x98, 0x75
2020-05-05 14:06:39.955 Detail, Node009,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-05-05 14:06:39.955 Detail, Node009,   ZW_SEND_DATA delivered to Z-Wave stack
2020-05-05 14:06:39.997 Detail, Node009,   Received: 0x01, 0x05, 0x00, 0x13, 0x98, 0x00, 0x71
2020-05-05 14:06:39.997 Detail, Node009,   ZW_SEND_DATA Request with callback ID 0x98 received (expected 0x98)
2020-05-05 14:06:39.997 Info, Node009, Request RTT 49 Average Request RTT 223
2020-05-05 14:06:39.997 Detail,   Expected callbackId was received
2020-05-05 14:06:39.997 Detail,   Expected reply was received
2020-05-05 14:06:39.997 Detail,   Message transaction complete
2020-05-05 14:06:39.997 Detail, 
2020-05-05 14:06:39.997 Detail, Node009, Removing current message
2020-05-05 14:06:39.997 Detail, 
2020-05-05 14:06:39.997 Info, Node009, Sending (Send) message (Callback ID=0x99, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=9): 0x01, 0x09, 0x00, 0x13, 0x09, 0x02, 0x25, 0x02, 0x25, 0x99, 0x75
2020-05-05 14:06:40.007 Detail, Node009,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-05-05 14:06:40.007 Detail, Node009,   ZW_SEND_DATA delivered to Z-Wave stack
2020-05-05 14:06:40.221 Detail, Node009,   Received: 0x01, 0x05, 0x00, 0x13, 0x99, 0x00, 0x70
2020-05-05 14:06:40.221 Detail, Node009,   ZW_SEND_DATA Request with callback ID 0x99 received (expected 0x99)
2020-05-05 14:06:40.221 Info, Node009, Request RTT 224 Average Request RTT 223
2020-05-05 14:06:40.221 Detail,   Expected callbackId was received
2020-05-05 14:06:40.759 Detail, Node009,   Received: 0x01, 0x0e, 0x00, 0x04, 0x00, 0x09, 0x06, 0x31, 0x05, 0x04, 0x22, 0x00, 0x00, 0xcf, 0x00, 0x27
2020-05-05 14:06:40.759 Detail, 
2020-05-05 14:06:40.759 Info, Node009, Response RTT 762 Average Response RTT 684
2020-05-05 14:06:40.759 Info, Node009, Received SensorMultiLevel report from node 9, instance 1, Power: value=0.0W
2020-05-05 14:06:40.759 Detail, Node009, Refreshed Value: old value=14.7, new value=0.0, type=decimal
2020-05-05 14:06:40.759 Detail, Node009, Changes to this value are not verified
2020-05-05 14:06:40.759 Detail, Node009, Notification: ValueChanged
2020-05-05 14:06:49.997 Error, Node009, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-05-05 14:06:49.998 Detail, Node009, Removing current message
2020-05-05 14:06:49.998 Detail, Node009, Notification: Notification - TimeOut

These errors also occur on node 6, 7, etc.
Why does this happen? What can I do about it?
Restarted Home Assistant, did a heal network, etc.

And with trying I also stumbled upon another little issue: the button card does not change color when used with a group entity, also mentioned in another topic.

2

Looked at cpu usage, but it doesn’t get higher than 12%. Memory usage is around 90Mb, with over 800Mb free. So the Pi isn’t busy.
Reboot doesn’t change anything.
Where do I start to find the problem?

3

Seems like this problem: https://github.com/home-assistant/core/issues/33119

4

Slow Z-Wave topic: Long delays and switches getting out of sync - zwave

Suggestion add devices as non secure. Already did that.
Al devices are Z-Wave +.
Looked at the Z-Wave map. Don’t see problems there. Not a single node that has to do Al the routing.

Screenshot_20200505-171928
Screenshot_20200505-1719281440×2880 189 KB

Don’t know how to solve this.

5

Nodes 9 and 10 have a high latency, looks like signal issues.

6

Yes, latency is high. But why is the association of node 5 working swiftly? It also should have your with this high latency/signal issues, I would think.
The nodes 9 and 10 are only 3.5 metres from the Pi and are located in the same room. So what’s causing signal issues?

7

Could be anything, wall, beam, concrete blocks, etc. Improperly shielded microwave (I’ve had this disrupt wifi connections). They best way to resolve signal issues is to add additional nodes really. The latency isn’t the only indication of signal issues the bit from your log:

Is the key.

8

OK, but why is switching on /off from node 5 S2 giving me any problems?

And these errors also occur on node 6, for example:
2020-05-05 09:51:02.137 Error, Node006, ERROR: Dropping command, expected response not received after 1 attempt(s)

The living room has 6 nodes, pretty evenly layed out over the room. Node 6 is closest to the Pi, just 1.5 m away.

Maybe the problem is with the location of the Pi and Z Wave usb stick itself?

9

You could try moving it. May help.

10

With the help of an usb cable I was able to move my Z wave stick to the middle of the room. The result was dissapointing, still no reliable switching and definitely not fast. Also not after a heal network or reboot of the Pi.

With the stick back in the Pi, I stopped docker and installed openHAB. So no changes in hardware, no exclude or include of Z-Wave nodes, no other OS and the Pi at it’s original location

OpenHAB gives the performance I expect. Switching on or off the 5 wallplugs is fast and reliable. No hesitation, just switch as.fast as S2 on the dimmer.

So, this is no problem with my Z-Wave network,.but with open Z-Wave and/or Home.Assistant software or configuration.
How do I find the cause of my problem? I
like Home Assistant except the Z-Wave performance.

1 Like
11

Very odd as I understand OH uses OpenZwave just as Home Assistant does.
I couldn’t help you with this as I do not encounter these issues in my network/setup.

Maybe @Fishwaldo has some ideas?

12

OH has it’s own Z-Wave implementation (in Java).

13

:face_vomiting: :face_vomiting:

14

Well, the entire project is Java.

15

OH doesn’t use OpenZwave. That’s the reason I tried OH.
But except for the Z-Wave performance, I prefer Home Assistant. Nobody an idea what can be the problem?

16

Did a fresh install of HA. Did improve a little, but still not OK.
OZW log analyzer is warning about ZWavePlusInfoCmd_Get not acknowledged by all nodes.
Also all nodes, except the dimmer has warnings about the SwitchAllCmd_Get not acknowledged.

So all the nodes give timeouts in the OZW log and because of these, it’s taking a long time before all the nodes react.
But I stil don’t know why these happen.

17

More people have problems like mine, but I don’t find real solutions. Yes OH, or other controllers don’t have these problems with the Same setup (https://github.com/OpenZWave/open-zwave/issues/1949#issuecomment-562393169) and sometimes re-include nodes work.

There is also a help page http://www.openzwave.com/knowledge-base/msgdropped. But that’s not really helpful either.

It says something about failed nodes. So Al my brand new nodes all failed, although they work perfectly with a direct association and OH? No, I don’t think so.

RF interference: same as above. OH and direct associations work, OZW doesn’t.

FLiRS: I don’t even have battery powered Z-Wave nodes.

Incorrectly configured node: that would be the most likely option. The link to this page:
http://www.openzwave.com/knowledge-base/deviceconfigerror

Message ID 20000 says something about interference again. But if that would be true, OH and the association wouldn’t work well either, as I said before.

Otherwise search if the nodes really support the command class. They don’t always acknowledge the command out of the mentioned classes. The config XML: https://github.com/OpenZWave/open-zwave/blob/master/config/fibaro/fgwpe.xml
It’s last updated one year ago. Is this also the version HA uses?
But that XML doesn’t config nor exclude the command class ZWavePlusInfoCmd.
Don’t think this is a configuration error of these type of devices.

Hope OZW 1.6 will fix this.

18

Seems like an issue with OpenZwave (1.4) then unfortunately, hopefully they’re fixed in 1.6 the next version Home Assistant will be using soon-ish.

19

Tried Domoticz with OZW 1.6. Still dropped commands. So OZW 1.6 is not a fix.
Only one thing left: re-include all the nodes.

20

I’ve noticed Fibaro device seem to have a bad reputation (on these forums) a lot of that brand device seems to act weird with OpenZwave :man_shrugging: