Ring Alarm - Retrofit Alarm Kit

Posted on
Thu Feb 03, 2022 7:21 am
whmoorejr offline
User avatar
Posts: 763
Joined: Jan 15, 2013
Location: Houston, TX

Re: Ring Alarm - Retrofit Alarm Kit

Not sure if this will help you or not....

Dual and I noticed some inclusion weirdness with Ring Contact sensors, specifically the 2nd generation ones. To get them to include required some form luck (insert battery, press buttons, include, remove battery, replace battery, repeat if necessary) I'm not positive, but I may of had to factory reset the contact sensors after a failed inclusion? but I don't remember. If you aren't using it already, the Z-Wave Watcher plugin is good for troubleshooting a z-wave device through the process.

Here is the last discussion we had on the ring contact sensor:
https://forums.indigodomo.com/viewtopic.php?f=136&t=24881&p=199616&hilit=ring+battery#p199616

Bill
My Plugin: My People

Posted on
Thu Feb 03, 2022 11:28 am
jenwill1 offline
Posts: 185
Joined: Mar 22, 2009
Location: Boerne, Texas

Re: Ring Alarm - Retrofit Alarm Kit

Certainly worth a try.... different inclusion process than I used. Thanks !

Posted on
Thu Feb 03, 2022 1:48 pm
Dual offline
Posts: 267
Joined: Feb 05, 2019

Re: Ring Alarm - Retrofit Alarm Kit

Jay had mentioned before that the Ring Keypad version 2 would not work with Indigo since it uses a newer form of encryption IIRC or some reason like that. Perhaps your device has the same issue? If it’s to a newer standard than it may not be compatible.


Sent from my iPhone using Tapatalk

Posted on
Thu Feb 03, 2022 2:50 pm
matt (support) offline
Site Admin
User avatar
Posts: 21429
Joined: Jan 27, 2003
Location: Texas

Re: Ring Alarm - Retrofit Alarm Kit

Anytime you see the NAK error it most likely means the module has gone to sleep again. I suspect if we can figure out how to keep it awake long enough we'll be able to figure out how to get it to send useful commands.

It is possible it has to be included with encryption, but based on the sync results (which look pretty good) I don't think it is. So let's continue the troubleshooting without encryption for now.

Image

Posted on
Fri Feb 04, 2022 6:26 pm
jenwill1 offline
Posts: 185
Joined: Mar 22, 2009
Location: Boerne, Texas

Re: Ring Alarm - Retrofit Alarm Kit

This device will not behave ! I tried the contact sensor inclusion method from whmoorejr/dual without success, same behavior. I could not get the LED's to react, fast blinking green, etc.. Still all it does it the alternating 3 blinks, about 5 sets, then an alternating green/red twice, alternating three blinks and goes to sleep...

When I try to exclude it by hitting the activity button, nothing happens, nor with the reset button. Just the same same pattern of led's on the activity button, no Led response hitting the reset for 10 seconds either. Maybe I got a bad device ? who knows.

I stopped the Indigo Server and restarted it. Saw the message below.. Not sure if it is the control responding or the device talking here.


SENT getNodeProtocolInfo: 01 04 00 41 43 F9
Z-Wave Debug RCVD getNodeProtocolInfo: 01 09 01 41 53 9C 01 04 07 01 7A (no inbound callback)
Z-Wave Debug . . getNodeProtocolInfo: node 067, class name: Notification Sensor
Z-Wave Debug . . getNodeProtocolInfo: class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01)
Z-Wave Debug . . getNodeProtocolInfo: base class command: 00
Z-Wave Debug . . getNodeProtocolInfo: supported class commands: 20
Z-Wave Debug . . getNodeProtocolInfo: encrypt class commands:
Z-Wave Debug . . getNodeProtocolInfo: features: routing, beaming
Z-Wave Debug starting node healing thread

I can't exclude it with the activity button, or taking the batteries out as suggested and also in the manual.

When I run remove failed devices... I get this error Z-Wave Error cannot remove failed module 067 from controller until device "067 - Notification Sensor" is deleted

Leading me to believe it's never finishes the inclusion process.

Thanks for any suggestions.

Will

Posted on
Fri Feb 04, 2022 6:49 pm
jenwill1 offline
Posts: 185
Joined: Mar 22, 2009
Location: Boerne, Texas

Re: Ring Alarm - Retrofit Alarm Kit

I was trying to remove the failed module, wasn't successful, tried to sync a new device to the old node to fail and then remove it. During that sync I hit the activity button and it blinked red and it said I excluded a node 000. Weird. Here is the activity log for it.

2022-02-04 18:27:40.190 Z-Wave Error Syncing - failed
2022-02-04 18:27:40.196 Z-Wave Error Timeout waiting for "067 - Notification Sensor". Module might be asleep, or is unreachable.
2022-02-04 18:27:41.880 Z-Wave Debug RCVD requestNodeInfo: 01 06 00 49 81 00 00 31
2022-02-04 18:27:41.880 Z-Wave Debug RCVD requestNodeInfo: failed (module asleep or doesn't support command)
2022-02-04 18:27:43.058 Z-Wave Debug RCVD exclusionMode node found: 01 07 00 4B 06 02 00 00 B7
2022-02-04 18:27:43.552 Z-Wave Debug RCVD exclusionMode removing slave node: 01 1B 00 4B 06 03 00 14 04 07 01 5E 55 9F 85 59 8E 60 80 70 5A 72 71 73 6C 86 84 7A D4
2022-02-04 18:27:43.553 Z-Wave Debug RCVD exclusionMode finished: 01 1B 00 4B 06 06 00 14 04 07 01 5E 55 9F 85 59 8E 60 80 70 5A 72 71 73 6C 86 84 7A D1
2022-02-04 18:27:43.553 Z-Wave Debug . . exclusionMode node removed: 000
2022-02-04 18:27:43.554 Z-Wave controller excluded module
2022-02-04 18:27:43.554 Z-Wave Debug SENT exitExclusionMode: 01 04 00 4B 05 B5
2022-02-04 18:27:43.555 Z-Wave Debug RCVD exitExclusionMode: 06 (ACK)
2022-02-04 18:27:43.555 Z-Wave stopped controller exclusion mode

I restarted the server, checked to see if node 67 was a gone.....yep so I did another include and sync no encryption, all seemed ok. the led's were still blinking so I went to the device and issued a "get device status" button press. The include and get status event log is below. Anyway I think I have a clean include and not going to touch anything until I get a suggestion ! Thanks

Feb 4, 2022 at 6:32:10 PM
Z-Wave Debug intiatingSyncUI (timeout in 1500 seconds)
Z-Wave Debug SENT enterInclusionMode: 01 04 00 4A C1 70
Z-Wave Debug RCVD enterInclusionMode: 06 (ACK)
Z-Wave started controller inclusion mode
Z-Wave Debug RCVD inclusionMode ready: 01 07 00 4A 01 01 00 00 B2
Z-Wave Debug RCVD inclusionMode node found: 01 07 00 4A 01 02 00 00 B1
Z-Wave Debug RCVD inclusionMode adding slave node: 01 1B 00 4A 01 03 44 14 04 07 01 5E 55 9F 85 59 8E 60 80 70 5A 72 71 73 6C 86 84 7A 96
Z-Wave Debug RCVD inclusionMode node respondCmds: 5E 55 9F 85 59 8E 60 80 70 5A 72 71 73 6C 86 84 7A
Z-Wave Debug RCVD inclusionMode node added: 01 07 00 4A 01 05 44 00 F2
Z-Wave Debug SENT exitInclusionMode: 01 04 00 4A 05 B4
Z-Wave Debug RCVD exitInclusionMode: 06 (ACK)
Z-Wave Debug RCVD inclusionMode finished: 01 07 00 4A 01 06 44 00 F1
Z-Wave Debug SENT getNodeProtocolInfo: 01 04 00 41 44 FE
Z-Wave Debug RCVD getNodeProtocolInfo: 01 09 01 41 53 9C 01 04 07 01 7A (no inbound callback)
Z-Wave Debug . . getNodeProtocolInfo: node 068, class name: Notification Sensor
Z-Wave Debug . . getNodeProtocolInfo: class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01)
Z-Wave Debug . . getNodeProtocolInfo: base class command: 00
Z-Wave Debug . . getNodeProtocolInfo: supported class commands: 20 60 84 85 86 80 6C 8E 70 71 72 73 55 59 5A 7A 5E 9F
Z-Wave Debug . . getNodeProtocolInfo: encrypt class commands:
Z-Wave Debug . . getNodeProtocolInfo: features: routing, battery, beaming, waking
Z-Wave controller included module: 068 - Notification Sensor
Z-Wave stopped controller inclusion mode
Z-Wave Syncing - started for "068 - Notification Sensor"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 44 01 01 3D
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 06 00 00 00 00 08 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 51 (no inbound callback)
Z-Wave Debug . . getNodeNeighbors: nodeId 068, neighbors: 2, 3, 44, 65
Z-Wave Syncing - retrieved module neighbors list: 2, 3, 44, 65
Z-Wave Syncing - assigning return route to "068 - Notification Sensor"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 44 01 F9
Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD (no inbound callback)
Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 00 BD
Z-Wave Debug . . assignReturnRoute: node 068, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 44 24 F1 08
Z-Wave Debug RCVD nodeInfoFrame: 01 1A 00 49 84 44 14 04 07 01 5E 55 9F 85 59 8E 60 80 70 5A 72 71 73 6C 86 84 7A 12
Z-Wave Debug . . nodeInfoFrame: node 068, combined class list: 80v1 20v1 84v1 85v1 86v1 8Ev1 55v1 59v1 5Av1 5Ev1 9Fv1 60v1 6Cv1 70v1 71v1 72v1 73v1 7Av1
Z-Wave Debug RCVD nodeInfoFrame: 01 1A 00 49 84 44 14 04 07 01 5E 55 9F 85 59 8E 60 80 70 5A 72 71 73 6C 86 84 7A 12
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 44 02 72 04 25 F2 02
Z-Wave Debug RCVD requestManufactureInfo: 01 07 00 13 F2 00 00 02 1B (node ACK)
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 44 08 72 05 03 46 0B 01 01 01 81
Z-Wave Debug . . requestManufactureInfo: node 068, manufacturerId 0346, productId 0B010101
Z-Wave Debug . . requestManufactureInfo: Ring, Notification Sensor
Z-Wave Syncing - retrieved manufacture and model names: Ring - 0346, Notification Sensor - 0B010101
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 44 02 86 11 25 F3 E2
Z-Wave Debug RCVD requestVersInfoGen: 01 07 00 13 F3 00 00 02 1A (node ACK)
Z-Wave Debug RCVD requestVersInfoGen: 01 11 00 04 00 44 0B 86 12 03 06 04 01 06 01 01 01 06 30
Z-Wave Debug . . requestVersInfoGen: node 068, protoVers 6.04, appVers 1.06
Z-Wave Syncing - retrieved protocol version 6.04, app version 1.06
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 44 03 86 13 84 25 F4 61
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 07 00 13 F4 00 00 02 1D (node ACK)
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0A 00 04 00 44 04 86 14 84 02 A5
Z-Wave Debug . . requestVersInfoCmdClass: node 068, class command 84 using version 2
Z-Wave Debug . . requestVersInfoCmdClass: node 068, combined class list: 80v1 20v1 84v2 85v1 86v1 8Ev1 55v1 59v1 5Av1 5Ev1 9Fv1 60v1 6Cv1 70v1 71v1 72v1 73v1 7Av1
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 44 03 86 13 60 25 F5 84
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 07 00 13 F5 00 00 02 1C (node ACK)
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0A 00 04 00 44 04 86 14 60 04 47
Z-Wave Debug . . requestVersInfoCmdClass: node 068, class command 60 using version 4
Z-Wave Debug . . requestVersInfoCmdClass: node 068, combined class list: 80v1 20v1 84v2 85v1 86v1 8Ev1 55v1 59v1 5Av1 5Ev1 9Fv1 60v4 6Cv1 70v1 71v1 72v1 73v1 7Av1
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01, base 00)
Z-Wave Syncing - retrieved command classes: 80v1 20v1 84v2 85v1 86v1 8Ev1 55v1 59v1 5Av1 5Ev1 9Fv1 60v4 6Cv1 70v1 71v1 72v1 73v1 7Av1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, battery, beaming, waking
Z-Wave Debug SENT requestWakeInterval: 01 09 00 13 44 02 84 05 25 F6 F1
Z-Wave Debug RCVD requestWakeInterval: 01 07 00 13 F6 00 00 02 1F (node ACK)
Z-Wave Debug RCVD requestWakeInterval: 01 0C 00 04 00 44 06 84 06 00 70 80 00 C7
Z-Wave Debug . . requestWakeInterval: node 068, interval 480 minutes, wakeTarget 000
Z-Wave Syncing - retrieved wake interval of 480 minutes
Z-Wave Debug SENT setWakeInterval: 01 0D 00 13 44 06 84 04 00 0E 10 01 25 F7 EE
Z-Wave Debug RCVD setWakeInterval: 01 07 00 13 F7 00 00 02 1E (node ACK)
Z-Wave Syncing - device "068 - Notification Sensor" wake interval changed to 60 minutes
Z-Wave Debug SENT requestMultiEndPointInfo: 01 09 00 13 44 02 60 07 25 F8 19
Z-Wave Debug RCVD requestMultiEndPointInfo: 01 07 00 13 F8 00 00 02 11 (node ACK)
Z-Wave Debug RCVD requestMultiEndPointInfo: 01 0B 00 04 00 44 05 60 08 40 08 00 91
Z-Wave Debug . . requestMultiEndPointInfo: node 068, numEndPoints 8, sameClass True, notStatic False
Z-Wave Debug SENT requestMultiEndPointDetails: 01 0A 00 13 44 03 60 09 01 25 F9 15
Z-Wave Debug RCVD requestMultiEndPointDetails: 01 07 00 13 F9 00 00 03 11 (node ACK)
Z-Wave Debug RCVD requestMultiEndPointDetails: 01 0F 00 04 00 44 09 60 0A 01 07 01 5E 6C 98 9F E1
Z-Wave Debug . . requestMultiEndPointDetails: node 068, endPoint 1, notStatic False, class hierarchy 07 : 01
Z-Wave Debug . . requestMultiEndPointDetails: node 068, combined multi-endpoint types: 1:(07 : 01)
Z-Wave Debug . . requestMultiEndPointDetails: node 068, combined multi-endpoint classes: 1:[5E 6C 98 9F]
Z-Wave Debug . . requestMultiEndPointDetails: node 068, combined multi-endpoint types: 1:(07 : 01), 2:(07 : 01)
Z-Wave Debug . . requestMultiEndPointDetails: node 068, combined multi-endpoint classes: 1:[5E 6C 98 9F], 2:[5E 6C 98 9F]
Z-Wave Debug . . requestMultiEndPointDetails: node 068, combined multi-endpoint types: 1:(07 : 01), 2:(07 : 01), 3:(07 : 01)
Z-Wave Debug . . requestMultiEndPointDetails: node 068, combined multi-endpoint classes: 1:[5E 6C 98 9F], 2:[5E 6C 98 9F], 3:[5E 6C 98 9F]
Z-Wave Debug . . requestMultiEndPointDetails: node 068, combined multi-endpoint types: 1:(07 : 01), 2:(07 : 01), 3:(07 : 01), 4:(07 : 01)
Z-Wave Debug . . requestMultiEndPointDetails: node 068, combined multi-endpoint classes: 1:[5E 6C 98 9F], 2:[5E 6C 98 9F], 3:[5E 6C 98 9F], 4:[5E 6C 98 9F]
Z-Wave Debug . . requestMultiEndPointDetails: node 068, combined multi-endpoint types: 1:(07 : 01), 2:(07 : 01), 3:(07 : 01), 4:(07 : 01), 5:(07 : 01)
Z-Wave Debug . . requestMultiEndPointDetails: node 068, combined multi-endpoint classes: 1:[5E 6C 98 9F], 2:[5E 6C 98 9F], 3:[5E 6C 98 9F], 4:[5E 6C 98 9F], 5:[5E 6C 98 9F]
Z-Wave Debug . . requestMultiEndPointDetails: node 068, combined multi-endpoint types: 1:(07 : 01), 2:(07 : 01), 3:(07 : 01), 4:(07 : 01), 5:(07 : 01), 6:(07 : 01)
Z-Wave Debug . . requestMultiEndPointDetails: node 068, combined multi-endpoint classes: 1:[5E 6C 98 9F], 2:[5E 6C 98 9F], 3:[5E 6C 98 9F], 4:[5E 6C 98 9F], 5:[5E 6C 98 9F], 6:[5E 6C 98 9F]
Z-Wave Debug . . requestMultiEndPointDetails: node 068, combined multi-endpoint types: 1:(07 : 01), 2:(07 : 01), 3:(07 : 01), 4:(07 : 01), 5:(07 : 01), 6:(07 : 01), 7:(07 : 01)
Z-Wave Debug . . requestMultiEndPointDetails: node 068, combined multi-endpoint classes: 1:[5E 6C 98 9F], 2:[5E 6C 98 9F], 3:[5E 6C 98 9F], 4:[5E 6C 98 9F], 5:[5E 6C 98 9F], 6:[5E 6C 98 9F], 7:[5E 6C 98 9F]
Z-Wave Debug . . requestMultiEndPointDetails: node 068, combined multi-endpoint types: 1:(07 : 01), 2:(07 : 01), 3:(07 : 01), 4:(07 : 01), 5:(07 : 01), 6:(07 : 01), 7:(07 : 01), 8:(07 : 01)
Z-Wave Debug . . requestMultiEndPointDetails: node 068, combined multi-endpoint classes: 1:[5E 6C 98 9F], 2:[5E 6C 98 9F], 3:[5E 6C 98 9F], 4:[5E 6C 98 9F], 5:[5E 6C 98 9F], 6:[5E 6C 98 9F], 7:[5E 6C 98 9F], 8:[5E 6C 98 9F]
Z-Wave Syncing - retrieved multi-endpoint types: 1:(07 : 01), 2:(07 : 01), 3:(07 : 01), 4:(07 : 01), 5:(07 : 01), 6:(07 : 01), 7:(07 : 01), 8:(07 : 01)
Z-Wave Syncing - retrieved multi-endpoint classes: 1:[5E 6C 98 9F], 2:[5E 6C 98 9F], 3:[5E 6C 98 9F], 4:[5E 6C 98 9F], 5:[5E 6C 98 9F], 6:[5E 6C 98 9F], 7:[5E 6C 98 9F], 8:[5E 6C 98 9F]
Z-Wave Debug SENT requestAssociationGroupCount: 01 09 00 13 44 02 85 05 25 FA FC
Z-Wave Debug RCVD requestAssociationGroupCount: 01 07 00 13 FA 00 00 02 13 (node ACK)
Z-Wave Debug RCVD requestAssociationGroupCount: 01 09 00 04 00 44 03 85 06 02 34
Z-Wave Debug . . requestAssociationGroupCount: node 068, group count: 2
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 44 03 85 02 01 25 FB F9
Z-Wave Debug RCVD requestAssociations: 01 07 00 13 FB 00 00 02 12 (node ACK)
Z-Wave Debug RCVD requestAssociations: 01 0B 00 04 00 44 05 85 03 01 01 00 37
Z-Wave Debug . . requestAssociations: node 068, group: 1, num associations: 0, max associations: 1, replies left: 0
Z-Wave Debug . . requestAssociations: node 068, group: 1, associations: []
Z-Wave Syncing - retrieved group 1 associations: []
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 44 03 85 02 02 25 FC FD
Z-Wave Debug RCVD requestAssociations: 01 07 00 13 FC 00 00 02 15 (node ACK)
Z-Wave Debug RCVD requestAssociations: 01 0B 00 04 00 44 05 85 03 02 01 00 34
Z-Wave Debug . . requestAssociations: node 068, group: 2, num associations: 0, max associations: 1, replies left: 0
Z-Wave Debug . . requestAssociations: node 068, group: 2, associations: []
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Debug SENT addInterfaceAssociation: 01 0B 00 13 44 04 85 01 01 01 25 FD FB
Z-Wave Debug RCVD addInterfaceAssociation: 01 07 00 13 FD 00 00 02 14 (node ACK)
Z-Wave Syncing - added group 1 association to interface
Z-Wave Debug . . addInterfaceAssociation: node 068, group: 1, associations: [1]
Z-Wave Debug SENT requestBatteryLevel2: 01 09 00 13 44 02 80 02 25 FE FA
Z-Wave Debug RCVD requestBatteryLevel2: 01 07 00 13 FE 00 00 06 13 (node ACK)
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 44 03 80 03 63 55
Z-Wave Debug . . requestBatteryLevel: node 068, level 99
Z-Wave Syncing - retrieved battery level of 99%
Z-Wave Syncing - created device "068 - Notification Sensor"
Z-Wave Syncing - created device "068 - Notification Sensor 2"
Z-Wave Syncing - created device "068 - Notification Sensor 3"
Z-Wave Syncing - created device "068 - Notification Sensor 4"
Z-Wave Syncing - created device "068 - Notification Sensor 5"
Z-Wave Syncing - created device "068 - Notification Sensor 6"
Z-Wave Syncing - created device "068 - Notification Sensor 7"
Z-Wave Syncing - created device "068 - Notification Sensor 8"
Z-Wave Syncing - created device "068 - Notification Sensor 9"
Z-Wave Syncing - complete
Z-Wave Debug terminatingSyncUI

Feb 4, 2022 at 6:32:59 PM
Z-Wave Debug SENT requestAlarmSensorStatus: 01 09 00 13 44 02 71 04 25 FF 0C
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 07 00 13 FF 00 00 02 16 (node ACK)
Z-Wave Debug waiting up to 3.0 seconds for module reply after sending request
Z-Wave Debug timeout waiting for module reply after sending request (not critical)
Z-Wave sent "068 - Notification Sensor" status request
Z-Wave Debug SENT requestBatteryLevel1: 01 09 00 13 44 02 80 02 25 01 05
Z-Wave Debug RCVD requestBatteryLevel1: 01 07 00 13 01 00 00 02 E8 (node ACK)
Z-Wave Debug waiting up to 3.0 seconds for module reply after sending request
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 44 03 80 03 63 55
Z-Wave Debug . . requestBatteryLevel: node 068, level 99
Z-Wave received "068 - Notification Sensor" status update battery level 99%
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 44 03 80 03 63 55
Z-Wave Debug . . requestBatteryLevel: node 068, level 99
Z-Wave received "068 - Notification Sensor" status update battery level 99%
Z-Wave Debug RCVD requestReply1: 01 08 00 04 00 44 02 5A 01 EE (hex)

Posted on
Sat Feb 05, 2022 12:32 pm
matt (support) offline
Site Admin
User avatar
Posts: 21429
Joined: Jan 27, 2003
Location: Texas

Re: Ring Alarm - Retrofit Alarm Kit

I assume it isn't sending out commands when you trip the inputs? If not, see if you can get the raw configuration commands to sent through without NAKs.

Image

Posted on
Sun Feb 06, 2022 8:14 am
jenwill1 offline
Posts: 185
Joined: Mar 22, 2009
Location: Boerne, Texas

Re: Ring Alarm - Retrofit Alarm Kit

Just NAK's still when sending previous raw commands... bummer

Does not respond to opening the top, tamper switch or when I trip the inputs.

Seems the root device won't wake up so I can't associate group two in each endpoint with the controller to receive the trips.

Thanks !

Posted on
Tue Feb 08, 2022 7:22 pm
matt (support) offline
Site Admin
User avatar
Posts: 21429
Joined: Jan 27, 2003
Location: Texas

Re: Ring Alarm - Retrofit Alarm Kit

In the UI when you specify the raw commands to be sent you should see a Send Mode popup control appear after selecting the device. Try selecting the 2nd option: Send immediately, If Failure Retry on Awake Notification. That will add the command to a queue (presuming it NAKs) and Indigo will try to send the command the next time the module wakes up (hopefully within an hour; adjust your wake time UI as low as possible).

Image

Posted on
Mon Feb 14, 2022 8:36 am
jenwill1 offline
Posts: 185
Joined: Mar 22, 2009
Location: Boerne, Texas

Re: Ring Alarm - Retrofit Alarm Kit

Matt, The device never wakes to receive the commands.... The device is listed in the event log when I reload Zwave. Think they are using the Ring application to finish the inclusion process ? I looked up the Zwave certification data but didn't find anything interesting.

https://products.z-wavealliance.org/pro ... quencyId=2

I'm about ready to punt this one.

Thanks

Who is online

Users browsing this forum: No registered users and 5 guests

cron