Page 1 of 1

Error returned from _zway_cc_call_handler

Posted: 12 Sep 2018 10:16
by brianaker
Starting with the 5.32 firmware I have started to seeing the following error in my logs:

[E] [zway] Error returned from _zway_cc_call_handler(zway, command, controller->id, 0, data[4], &data[5]): Wrong packet from Z-Wave network or Discovery got bad data (stick communication failed) (-9)

Any ideas?

Re: Error returned from _zway_cc_call_handler

Posted: 14 Sep 2018 11:38
by PoltoS
We need more log output from above this line.

Re: Error returned from _zway_cc_call_handler

Posted: 15 Sep 2018 01:29
by brianaker
Here is one:

[2018-09-14 08:20:09.808] [D] [zway] RECEIVED: ( 01 0B 00 04 00 B9 03 31 05 04 A8 00 D2 )
[2018-09-14 08:20:09.808] [D] [zway] SENT ACK
[2018-09-14 08:20:09.808] [D] [zway] SETDATA devices.185.data.lastReceived = 0 (0x00000000)
[2018-09-14 08:20:09.808] [E] [zway] Packet CC::SENSOR_MULTILEVEL_REPORT is too short: required at least 5 bytes, got 3
[2018-09-14 08:20:09.808] [E] [zway] Error returned from _zway_cc_call_handler(zway, command, controller->id, 0, data[4], &data[5]): Wrong packet from Z-Wave network or Discovery got bad data (stick communication failed) (-9)


Another:

[2018-09-14 13:00:17.075] [D] [zway] SETDATA devices.79.data.lastReceived = 0 (0x00000000)
[2018-09-14 13:00:17.075] [E] [zway] Node 79:0 CC CRC16: Packet CRC error (expected 0x67a8, got 0x6728)
[2018-09-14 13:00:17.076] [E] [zway] Error returned from _zway_cc_call_handler(zway, command, controller->id, 0, data[4], &data[5]): Wrong packet from Z-Wave network or Discovery got bad data (stick communication failed) (-9)


Quite a few more CRC errors. Looking back at logs before the firmware upgrade, these errors were not common. The CRC errors come from GE switches and the multi sensor is an Aeotec Smart Switch ( I have wondered before about the Aeotec though ).

Re: Error returned from _zway_cc_call_handler

Posted: 15 Sep 2018 20:31
by PoltoS
This looks like errors in radio - poor radio quality leads to errors and in some cases it leads to CRC mismatch, while in others to wrong parsing

Re: Error returned from _zway_cc_call_handler

Posted: 16 Sep 2018 00:18
by brianaker
Are you saying there is something wrong with the radio physically or that it a location issue?

Here are some more.
[2018-09-15 14:05:11.029] [E] [zway] Packet CC::MANUFACTURER_SPECIFIC_REPORT is too short: required at least 8 bytes, got 3
[2018-09-15 14:05:11.029] [E] [zway] Error returned from _zway_cc_call_handler(zway, command, controller->id, 0, data[4], &data[5]): Wrong packet from Z-Wave network or Discovery got bad data (stick communication failed) (-9)
[2018-09-15 14:05:11.040] [zway] Node 117:0 CC Version: AssociationGroupInformation is v1
[2018-09-15 14:05:11.082] [zway] Node 117:0 CC Version: AssociationGroupInformation is v1
[2018-09-15 14:05:11.093] [E] [zway] Packet CC::MANUFACTURER_SPECIFIC_REPORT is too short: required at least 8 bytes, got 3
[2018-09-15 14:05:11.093] [E] [zway] Error returned from _zway_cc_call_handler(zway, command, controller->id, 0, data[4], &data[5]): Wrong packet from Z-Wave network or Discovery got bad data (stick communication failed) (-9)
[2018-09-15 14:05:11.112] [zway] Node 117:0 CC Version: AssociationGroupInformation is v1
[2018-09-15 14:05:11.175] [E] [zway] Packet CC::MANUFACTURER_SPECIFIC_REPORT is too short: required at least 8 bytes, got 3
[2018-09-15 14:05:11.175] [E] [zway] Error returned from _zway_cc_call_handler(zway, command, controller->id, 0, data[4], &data[5]): Wrong packet from Z-Wave network or Discovery got bad data (stick communication failed) (-9)

Re: Error returned from _zway_cc_call_handler

Posted: 16 Sep 2018 08:41
by PoltoS
You have a lot of RF errors (unless you do something else strange). Either it is RF noise (Background noise in the Expert UI) or this is a firmware error - downgrade back and check