problem with newly included battery device

Discussions about Z-Way software and Z-Wave technology in general
Post Reply
piet66
Posts: 267
Joined: 04 Feb 2017 17:00

problem with newly included battery device

Post by piet66 »

Hi,
I'm using some Fibaro Door/window sensors FGK-10x for long time. Now I had to exclude and include one of them again (security S0).

It works, it sends data, but I have some problems:

1. the device doesn't react on any Configuration Set. On Configuration Get it sends the old/default values.
I noticed that Zway uses 86/1=CRC16 Encapsulation instead of 152/129=Security Message Encapsulation for this command. The device uses CRC16 only for Sensor Reports.

Code: Select all

nodeInfoFrame: {
    value: [
        "34 Application Status",
        "49 Sensor Multilevel",
        "86 CRC16 Encap",
        "89 Association Group Info",
        "94 Z-Wave+ Info",
        "114 Manufacturer Specific",
        "115 Powerlevel",
        "122 Firmware Update Md",
        "128 Battery",
        "134 Version",
        "152 Security"
    ],
    type: "binary",
    invalidateTime: 1688665514,
    updateTime: "1688665521 2023-07-06 19:45:21"
},
2. Force interview doesn't work:
It seems to me that the commands stay in the job queue and are not forwarded to the device, even if I woke it up manually

Code: Select all

[[0.20000000298023224,[0,1,1,0,0,1,0,1,0,1,0,0,1,0,0,1,0,1,0,1,0,0,1,128,0,0,0],93,"Secure NIF Get",null,[93,2,152,2,5],1908423816,[\]],
[0.20000000298023224,[1,1,0,0,0,1,0,1,0,1,0,0,1,0,0,1,0,1,0,1,0,0,1,0,0,0,0],93,"Nonce Get","Not delivered to recipient",[93,2,152,64,5],1868655136,[\]],
[17.392953872680664,[1,0,0,0,1,1,1,1,1,0,0,0,0,0,1,0,0,0,0,0,0,0,1,0,0,0,1],0,"Get background noise level","RSSI Ch#1: -106 dBm, Ch#2: -111 dBm, Ch#3: -111 dBm",[],1904330680,[]]]

Code: Select all

    {
        "updateTime": "1689145443=2023-07-12 09:04:03, delivered=false",
        "nodeId": "93=EN-Bad Fibaro Door/Window Sensor G5",
        "speed": "40 kbps",
        "route": "[1,93]",
        "rssi": "[]",
        "classCommand": "152=Security, 64=Security Nonce Get",
        "index": "<3827>",
    },
    {
        "duplicate": 0,
        "updateTime": "1689145461=2023-07-12 09:04:21, frameType=singlecast",
        "nodeId": "93=EN-Bad Fibaro Door/Window Sensor G5",
        "route": "[93,6,1]",
        "rssi": "-81 dBm",
        "classCommand": "152=Security, 64=Security Nonce Get",
        "index": "<3829>",
    },
    {
        "updateTime": "1689145462=2023-07-12 09:04:22, delivered=true",
        "nodeId": "93=EN-Bad Fibaro Door/Window Sensor G5",
        "speed": "9.6 kbps",
        "route": "[1,6,93]",
        "rssi": "[-82 dBm,]",
        "classCommand": "152=Security, 128=Security Nonce Report",
        "value": "[152,128,82,181,113,32,138,252,202,42]",
        "index": "<3830>",
    },
    {
        "duplicate": 0,
        "updateTime": "1689145462=2023-07-12 09:04:22, frameType=singlecast",
        "nodeId": "93=EN-Bad Fibaro Door/Window Sensor G5",
        "route": "[93,6,1]",
        "rssi": "-81 dBm",
        "classCommand": "152=Security, 129=Security Message Encapsulation, 132=Wake Up, 7=Wake Up Notification",
        "index": "<3831>",
    },
    {
        "duplicate": 0,
        "updateTime": "1689145936=2023-07-12 09:12:16, frameType=singlecast",
        "nodeId": "93=EN-Bad Fibaro Door/Window Sensor G5",
        "route": "[93,6,1]",
        "rssi": "-82 dBm",
        "classCommand": "152=Security, 64=Security Nonce Get",
        "index": "<3844>",
    },
    {
        "updateTime": "1689145941=2023-07-12 09:12:21, delivered=true",
        "nodeId": "93=EN-Bad Fibaro Door/Window Sensor G5",
        "speed": "40 kbps",
        "route": "[1,39,45,93]",
        "rssi": "[-59 dBm,,not available]",
        "classCommand": "152=Security, 128=Security Nonce Report",
        "value": "[152,128,185,30,33,220,213,227,17,205]",
        "index": "<3845>",
    }
{

    "duplicate": 0,
    "updateTime": "1689147199=2023-07-12 09:33:19, frameType=singlecast",
    "nodeId": "93=EN-Bad Fibaro Door/Window Sensor G5",
    "route": "[93,45,39,1]",
    "rssi": "-58 dBm",
    "classCommand": "152=Security, 64=Security Nonce Get",
    "index": "<3869>",

},
{

    "updateTime": "1689147200=2023-07-12 09:33:20, delivered=true",
    "nodeId": "93=EN-Bad Fibaro Door/Window Sensor G5",
    "speed": "40 kbps",
    "route": "[1,39,45,93]",
    "rssi": "[-58 dBm,,not available]",
    "classCommand": "152=Security, 128=Security Nonce Report",
    "value": "[152,128,51,133,232,172,141,143,209,235]",
    "index": "<3870>",

},
{

    "duplicate": 0,
    "updateTime": "1689147200=2023-07-12 09:33:20, frameType=singlecast",
    "nodeId": "93=EN-Bad Fibaro Door/Window Sensor G5",
    "route": "[93,45,39,1]",
    "rssi": "-58 dBm",
    "classCommand": "152=Security, 129=Security Message Encapsulation, 132=Wake Up, 7=Wake Up Notification",
    "index": "<3871>",

}
Upgrade to z-way-4.1.0-27 didn't help.

Update: gone back to 4.1.0, cause on 4.1.0-27 my apps don't run any more (sockets undefined). :(
Raspberry Pi 3 Model B Rev 1.2
Raspbian GNU/Linux 10 (buster, 32bit)
RaZberry by Z-Wave.Me ZW0700 7.20.00 07.38/1766938484 1025/257
Z-Way version v4.1.2 from 2023-10-18 03:34:26 +0300
User avatar
PoltoS
Posts: 7579
Joined: 26 Jan 2011 19:36

Re: problem with newly included battery device

Post by PoltoS »

Try to set devices[N].Configuration.data.security=true
piet66
Posts: 267
Joined: 04 Feb 2017 17:00

Re: problem with newly included battery device

Post by piet66 »

Try to set devices[N].Configuration.data.security=true
I can't test this, cause of the failed interview the command class 112 is no more existing.
I must wait, till the interview problem is solved.

But I think it should have been set true after the including was done completely.
Raspberry Pi 3 Model B Rev 1.2
Raspbian GNU/Linux 10 (buster, 32bit)
RaZberry by Z-Wave.Me ZW0700 7.20.00 07.38/1766938484 1025/257
Z-Way version v4.1.2 from 2023-10-18 03:34:26 +0300
piet66
Posts: 267
Joined: 04 Feb 2017 17:00

Re: problem with newly included battery device

Post by piet66 »

PoltoS wrote:
15 Jul 2023 06:07
Try to set devices[N].Configuration.data.security=true
The Configuration section I can't check anymore. But the secureNodeInfoFrame array in Security section is empty.
Raspberry Pi 3 Model B Rev 1.2
Raspbian GNU/Linux 10 (buster, 32bit)
RaZberry by Z-Wave.Me ZW0700 7.20.00 07.38/1766938484 1025/257
Z-Way version v4.1.2 from 2023-10-18 03:34:26 +0300
piet66
Posts: 267
Joined: 04 Feb 2017 17:00

Re: problem with newly included battery device

Post by piet66 »

Moved back to 3.2.3 and tried to force an interview again. But the same as on 4.1.0: the commands are not forwarded to the device. Seems there's a state where zway blocks itself.
I had to exclude and include the device again. Now it works properly.
Raspberry Pi 3 Model B Rev 1.2
Raspbian GNU/Linux 10 (buster, 32bit)
RaZberry by Z-Wave.Me ZW0700 7.20.00 07.38/1766938484 1025/257
Z-Way version v4.1.2 from 2023-10-18 03:34:26 +0300
Manisoa
Posts: 1
Joined: 28 Aug 2023 06:37

Re: problem with newly included battery device

Post by Manisoa »

Relocated to version 3.2.3 and made another attempt to schedule an interview. However, just like in 4.1.0, the gadget will not receive the commands. It appears that zway can obstruct itself in some circumstances. only up
Amelia Bailey
Posts: 2
Joined: 04 Oct 2023 12:05

Re: problem with newly included battery device

Post by Amelia Bailey »

To start, make sure your siren device is properly added and recognized in Home Assistant.
Post Reply