Ring Alarm Keypad (2ng Generation) : how to get it to work ? #4743

candrea77 · 2022-06-24T07:02:37Z

candrea77
Jun 24, 2022

Hi guys,
I'm trying to make a RIng Alarm Keypad to work.

As by now, device is paired in S2 with my zwave system, I can use zwave to program any settings (key press volume , light intensity and so on) , but I'm unable to get any "data" from the keypad itself.

Some information :
zwavejs2mqtt: 6.12.0
zwave-js: 9.4.0
FW: v1.18
SDK: v7.12.4

I've noticed that Zwave Group association is empty .... and if I try to setup the association EndPoint_0 Node_1 I get timeout error in zwave log.
NodeID of Ring Alarm Keypad is 156

__2022-06-24T06:58:03.631Z SERIAL « 0x010e00040058063105042200c2b800c3                                  (16 bytes)
2022-06-24T06:58:03.631Z CNTRLR   [Node 088] [Multilevel Sensor] Power: metadata updated            [Endpoint 0]
2022-06-24T06:58:03.632Z CNTRLR   [Node 088] [~] [Multilevel Sensor] Power: 143.5 => 19.4           [Endpoint 0]
2022-06-24T06:58:03.634Z SERIAL » [ACK]                                                                   (0x06)
2022-06-24T06:58:03.634Z DRIVER « [Node 088] [REQ] [ApplicationCommand]
                                  └─[MultilevelSensorCCReport]
                                      type:  Power
                                      scale: Watt
                                      value: 19.4
2022-06-24T06:58:04.630Z SERIAL « 0x010e00040058063105042201bfb600b1                                  (16 bytes)
2022-06-24T06:58:04.630Z CNTRLR   [Node 088] [Multilevel Sensor] Power: metadata updated            [Endpoint 0]
2022-06-24T06:58:04.631Z CNTRLR   [Node 088] [~] [Multilevel Sensor] Power: 19.4 => 44.7            [Endpoint 0]
2022-06-24T06:58:04.631Z SERIAL » [ACK]                                                                   (0x06)
2022-06-24T06:58:04.632Z DRIVER « [Node 088] [REQ] [ApplicationCommand]
                                  └─[MultilevelSensorCCReport]
                                      type:  Power
                                      scale: Watt
                                      value: 44.7
2022-06-24T06:58:05.975Z SERIAL « 0x01120004000a0a320221440002884a0000bf00c3                          (20 bytes)
2022-06-24T06:58:05.976Z CNTRLR   [Node 010] [~] [Meter] value[65537]: 1659.62 => 1659.62           [Endpoint 0]
2022-06-24T06:58:05.976Z SERIAL » [ACK]                                                                   (0x06)
2022-06-24T06:58:05.977Z DRIVER « [Node 010] [REQ] [ApplicationCommand]
                                  └─[MeterCCReport]
                                      type:       Electric
                                      scale:      kWh
                                      rate type:  Consumed
                                      value:      1659.62
                                      time delta: 0 seconds
2022-06-24T06:58:14.109Z SERIAL » 0x011900139c129f032700688edf95688ef0f4f6ce1cc26799253586            (27 bytes)
2022-06-24T06:58:14.110Z DRIVER » [Node 156] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      53
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 39
                                    └─[MultiChannelAssociationCCSet]
                                        group id:  1
                                        node ids:
                                        endpoints: 1:0
2022-06-24T06:58:14.111Z SERIAL « [ACK]                                                                   (0x06)
2022-06-24T06:58:14.118Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-06-24T06:58:14.118Z SERIAL » [ACK]                                                                   (0x06)
2022-06-24T06:58:14.119Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-06-24T06:58:14.586Z SERIAL « 0x011800133500002f00bb7f7f7f7f010103000000002204000070              (26 bytes)
2022-06-24T06:58:14.586Z SERIAL » [ACK]                                                                   (0x06)
2022-06-24T06:58:14.587Z DRIVER « [REQ] [SendData]
                                    callback id:            53
                                    transmit status:        OK, took 470 ms
                                    routing attempts:       4
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    ACK RSSI:               -69 dBm
                                    ACK channel no.:        1
                                    TX channel no.:         1
                                    beam:                   250 ms
2022-06-24T06:58:14.592Z SERIAL » 0x011600139c0f9f032800674c7dfff7759c6f52debe253624                  (24 bytes)
2022-06-24T06:58:14.592Z DRIVER » [Node 156] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      54
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 40
                                    └─[MultiChannelAssociationCCGet]
                                        group id: 1
2022-06-24T06:58:14.594Z SERIAL « [ACK]                                                                   (0x06)
2022-06-24T06:58:14.600Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-06-24T06:58:14.600Z SERIAL » [ACK]                                                                   (0x06)
2022-06-24T06:58:14.601Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-06-24T06:58:14.622Z SERIAL « 0x011800133600000200b97f7f7f7f010103000000000201000079              (26 bytes)
2022-06-24T06:58:14.623Z SERIAL » [ACK]                                                                   (0x06)
2022-06-24T06:58:14.623Z DRIVER « [REQ] [SendData]
                                    callback id:            54
                                    transmit status:        OK, took 20 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    ACK RSSI:               -71 dBm
                                    ACK channel no.:        1
                                    TX channel no.:         1
2022-06-24T06:58:15.657Z CNTRLR   [Node 156] Timed out while waiting for a response from the node (ZW0201)_

_

Any one with the same device can help me ?

Answered by candrea77

Jun 26, 2022

Quick update.
Problem solved after device removal and reinstall.

Regards

View full answer

mundschenk-at · 2022-06-24T17:04:58Z

mundschenk-at
Jun 24, 2022

Did you pair it with Smart Start? For me it worked out of the box after pairing.

0 replies

candrea77 · 2022-06-24T19:01:15Z

candrea77
Jun 24, 2022
Author

Yes ... I've used smart start and now I've got a device paired with s2 security and zwave 2 Just a note : at the first moment it wasn't paired ok. But after a more few moments I got two devices .... one wrong ( now deleted) and one ok. Did you get group node association when included ? Il Ven 24 Giu 2022, 19:05 Der Mundschenk & Compagnie < ***@***.***> ha scritto:

…

Did you pair it with Smart Start? For me it worked out of the box after pairing. — Reply to this email directly, view it on GitHub <#4743 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGGSROP2XLWR7TVSTYBPGHDVQXTELANCNFSM5ZWYEVVQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

1 reply

mundschenk-at Jun 24, 2022

Only the lifeline association to the controller.

candrea77 · 2022-06-25T05:21:52Z

candrea77
Jun 25, 2022
Author

*Only the lifeline association to the controller.*

Ok ... it's the one that is missing in my system. That's good news for me ...... I've a hope to make it work. I'll try a complete remove and reinstall Thank you Crippa Andrea Il giorno ven 24 giu 2022 alle ore 23:22 Der Mundschenk & Compagnie < ***@***.***> ha scritto:

…

Only the lifeline association to the controller. — Reply to this email directly, view it on GitHub <#4743 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGGSROPUR33CXZ7D2B2W7Q3VQYRHPANCNFSM5ZWYEVVQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

0 replies

candrea77 · 2022-06-26T18:26:50Z

candrea77
Jun 26, 2022
Author

Quick update.
Problem solved after device removal and reinstall.

Regards

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Ring Alarm Keypad (2ng Generation) : how to get it to work ? #4743

{{title}}

Replies: 4 comments 1 reply

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Ring Alarm Keypad (2ng Generation) : how to get it to work ? #4743

candrea77 Jun 24, 2022

Replies: 4 comments · 1 reply

mundschenk-at Jun 24, 2022

candrea77 Jun 24, 2022 Author

mundschenk-at Jun 24, 2022

candrea77 Jun 25, 2022 Author

candrea77 Jun 26, 2022 Author

candrea77
Jun 24, 2022

Replies: 4 comments 1 reply

mundschenk-at
Jun 24, 2022

candrea77
Jun 24, 2022
Author

candrea77
Jun 25, 2022
Author

candrea77
Jun 26, 2022
Author