Page 1 of 1

wrong hops in incoming packets

Posted: 06 Jul 2023 11:14
by piet66
Hi,
I just installed my new Razberry 7 board. In this context, I checked everything again. In the process, I noticed an oddity.

In a lot of incoming packets (174 packets of 3636 single casts from originPackets) there are routes with unknown hops.

Example:

Code: Select all

{
    "updateTime": 1688621444,
    "nodeId": 39,
    "dstNodeId": 1,
    "RSSI": 193,
    "hops": "[252,212,249,94,185,108,38,222]",
    "frameType": "singlecast",
    "duplicate": 0,
    "value": "[152,129,252,212,249,94,185,108,38,222,105,232,23,3,33,250,161,148,139,193,13,103,20]",
}
In this example, only node 38 does exist.

Additionally in Expert UI/ Signal strength for many not existing nodes an entry 'nn Device_nn ...' is shown with signal strength.
Screenshot 2023-07-06 at 10-01-22 Z-Wave Expert UI.png
Screenshot 2023-07-06 at 10-01-22 Z-Wave Expert UI.png (55.13 KiB) Viewed 12508 times
I don't know whether this is new, but I haven't seen it before. What can be the reason for this?

Re: wrong hops in incoming packets

Posted: 06 Jul 2023 13:42
by PoltoS
Could you please find in the log the corresponding RECEIVED line?

You should search for

Code: Select all

98 81 FC D4 F9 5E B9 6C 26 DE 69 E8 17 03 21 FA A1 94 8B C1 0D 67 14
Clearly the hops array is a part of the packet, so it is a firmware issue or z-way issue. And we have a new firmware fixing some Zniffer features (7.38) that could be installed by using the token "all". I'm sure it should fix it.

Re: wrong hops in incoming packets

Posted: 08 Jul 2023 14:32
by piet66
Upgraded to 7.38. But it didn't help.

Example with 7.38:

Code: Select all

    {
        "updateTime": 1688814874,
        "nodeId": 39,
        "dstNodeId": 1,
        "RSSI": 193,
        "hops": "[62,186,5,1]",
        "frameType": "singlecast",
        "duplicate": 0,
        "value": "[152,64]",
        "index": "<4182>"
    },
    {
        "updateTime": 1688814874,
        "delivered": true,
        "deliveryTime": 10,
        "packetLength": 13,
        "nodeId": 39,
        "returnRSSI": [
            193
        ],
        "hops": "[]",
        "returnChannel": 0,
        "txChannel": 0,
        "speed": "100 kbps",
        "schemeState": 3,
        "tries": 1,
        "lastFailPath": "[0,0]",
        "value": "[0,19,39,10,152,128,190,64,165,35,95,205,236,72,37]",
        "index": "<4183>"
    },
    {
        "updateTime": 1688814874,
        "nodeId": 39,
        "dstNodeId": 1,
        "RSSI": 193,
        "hops": "[38,203,114,167,124,228,149,187]",
        "frameType": "singlecast",
        "duplicate": 0,
        "value": "[152,129,38,203,114,167,124,228,149,187,105,61,0,127,190,92,7,58,224,169,156,216,245]",
        "index": "<4184>"
    }

Code: Select all

[2023-07-08 13:14:34.537] [D] [zway] RECEIVED: ( 01 0F 00 04 00 27 02 98 40 C1 00 04 3E BA 05 01 4C )
[2023-07-08 13:14:34.538] [D] [zway] SENT ACK
[2023-07-08 13:14:34.538] [D] [zway] SETDATA devices.39.data.lastReceived = 0 (0x00000000)
[2023-07-08 13:14:34.538] [I] [zway] Node 39:0 CC Security: sending Nonce Report
[2023-07-08 13:14:34.538] [I] [zway] Adding job: Nonce Report to node 39
[2023-07-08 13:14:34.539] [D] [zway] SENDING (cb 0x03): ( 01 11 00 13 27 0A 98 80 BE 40 A5 23 5F CD EC 48 25 03 A0 )
[2023-07-08 13:14:34.541] [D] [zway] RECEIVED ACK
[2023-07-08 13:14:34.543] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
[2023-07-08 13:14:34.543] [D] [zway] SENT ACK
[2023-07-08 13:14:34.543] [D] [zway] Delivered to Z-Wave stack
[2023-07-08 13:14:34.560] [D] [zway] RECEIVED: ( 01 1D 00 13 03 00 00 01 00 C1 7F 7F 7F 7F 00 00 03 00 00 00 00 03 01 00 00 7F 7F 7F 7F 7F 4C )
[2023-07-08 13:14:34.561] [D] [zway] SENT ACK
[2023-07-08 13:14:34.561] [I] [zway] Job 0x13 (Nonce Report to node 39): Delivered
[2023-07-08 13:14:34.561] [D] [zway] SendData Response with callback 0x03 received: received by recipient
[2023-07-08 13:14:34.561] [D] [zway] SETDATA devices.39.data.lastSendInternal = **********
[2023-07-08 13:14:34.561] [D] [zway] SETDATA devices.39.data.lastSend = 13324 (0x0000340c)
[2023-07-08 13:14:34.561] [D] [zway] Job 0x13 (Nonce Report to node 39): success
[2023-07-08 13:14:34.561] [I] [zway] Removing job: Nonce Report to node 39
[2023-07-08 13:14:34.573] [D] [zway] RECEIVED: ( 01 28 00 04 00 27 17 98 81 26 CB 72 A7 7C E4 95 BB 69 3D 00 7F BE 5C 07 3A E0 A9 9C D8 F5 C1 00 08 26 CB 72 A7 7C E4 95 BB 3F )
[2023-07-08 13:14:34.574] [D] [zway] SENT ACK
[2023-07-08 13:14:34.574] [D] [zway] SETDATA devices.39.data.lastReceived = 0 (0x00000000)
[2023-07-08 13:14:34.574] [I] [zway] Node 39:0 CC Security: Received a secure message
[2023-07-08 13:14:34.574] [D] [zway] SETDATA devices.39.instances.0.commandClasses.152.data.firstPart = **********
[2023-07-08 13:14:34.574] [I] [zway] Node 39:0 CC Security: passing decrypted packet to application level: [ 25 03 ff ]
[2023-07-08 13:14:34.574] [D] [zway] SETDATA devices.39.instances.0.commandClasses.37.data.level = True

Re: wrong hops in incoming packets

Posted: 10 Jul 2023 04:36
by PoltoS
Thanks, it is a clear bug, we will look on it.

Re: wrong hops in incoming packets

Posted: 19 Jul 2023 22:19
by amatilda
piet66 wrote:
08 Jul 2023 14:32
...
Hello.
I tried to repeat, but I failed. On which slave do you have this happening?
What firmware version do you currently have displayed in the "Controller Info" tab?

Re: wrong hops in incoming packets

Posted: 30 Jul 2023 19:10
by piet66
Gone back to zway 3.2.3.
The issue stays the same:

Code: Select all

{

        "updateTime": 1690729811,
        "nodeId": 23,
        "dstNodeId": 1,
        "RSSI": 197,
        "hops": [
              118,
              223,
              60,
              228,
              184,
              145,
              60,
              100
        ],
        "frameType": "singlecast",
        "duplicate": 0,
        "value": [
              152,
              129,
              118,
              223,
              60,
              228,
              184,
              145,
              60,
              100,
              72,
              140,
              205,
              232,
              228,
              158,
              59,
              79,
              205,
              159,
              214,
              248
        ]

  },
In this example, the contents of hops is complete nonsense. None of these hops does exist. Obviously, these data are taken from the value part.
These packets are coming from some but different nodes. I checked 1 day: They were of types Fibaro Door/Window Sensor G5 and Danalock V3. ALL singlecast packets from these device types are affected.
It seems, that all S0 included devices are affected, but none of the insecure included.

Another example, here nodeId is wrong:

Code: Select all

{

        "updateTime": 1690654624,
        "nodeId": 129,
        "dstNodeId": 255,
        "RSSI": 164,
        "hops": [ ],
        "frameType": "Explore Frame",
        "duplicate": 0,
        "value": [
              129,
              34,
              1,
              0
        ]

  },
Node 129 doesn't exist.

Re: wrong hops in incoming packets

Posted: 01 Aug 2023 01:56
by amatilda
piet66 wrote:
30 Jul 2023 19:10
Gone back to zway 3.2.3.
I asked to see the firmware version to be sure that you have it updated.
http://localhost:8083/expert/#/network/controller

Do you have such a line?
Serial API Version: 7.38

Re: wrong hops in incoming packets

Posted: 01 Aug 2023 08:55
by piet66
See my signature: 7.38

Re: wrong hops in incoming packets

Posted: 21 Sep 2023 15:21
by JasonJoel
PoltoS wrote:
10 Jul 2023 04:36
Thanks, it is a clear bug, we will look on it.
Just reporting that I am seeing the same thing. Sorry for not seeing this thread before making a new one.

I am running Serial API Version: 07.38.

https://forum.z-wave.me/viewtopic.php?f=3419&t=35943

Re: wrong hops in incoming packets

Posted: 30 Jul 2024 10:15
by piet66
It should be mentioned that an upgrade to the latest Razberry firmware 7.42 solved the problem.