I bought a ring keypad to use with my alarmo set up and am having issues. Attached are layouts of my house. I had no other zwave items before this but added a couple to try and get this to work. The problem is I am getting slow response time, drop outs even though i went out and bought switches to use a repeaters.
Controller - zooZ S2 700 plugged into a powered usb 2 extension port
In Wall Plugs - enbrighten in wall zwave tamper resistant smart outlet x2
Smart Plug - New One N4013 (for testing, plan on sending back)
Integration - Zwave JS UI
Key
C - Controller
1 - Zwave Plug 1
2 - Zwave Plug 2
TP - Smart Plug
RT1 - Ring test 1 (more on below)
RT2 - Final resting place for ring keypad
RT3 - Ring test 3 (more on below)
If i take the Ring keypad in next to the zwave plug 1 (RT1) and its hooked up directly to the controller (not the zwave plug) I have no issues.
If i then update the priority route so it uses the Zwave plug to hop to the controller it has random response issues and drop outs.
I originally was doing my tests at RT2 since that is where it is going to live once we are done and had this issue so i figured i would move it up close to plug for a test.
While typing this I thought “I have this smart plug lets test this super close” and i had the same issue when i changed the route to go through that plug.
Everything is in the same room (controller, smart plug and ring keypad). I updated the keypad to go through the smart plug to the controller. Arm happens pretty quick but disarm has at least a 10 second delay.
hooked to the smart plug there is a
2023-08-15T15:07:54.927Z CNTRLR [Node 005] failed to decode the message, retrying with SPAN extension…
after the home and armed command
also you can see directly to the controller the whole thing takes 4 seconds to arm and disarm. connected to the plug it takes 9. Sometimes the disarm takes longer.
Keypad is S2 and plugs are not supposedly that does not matter.
2023-08-15 15:03:40.731 INFO Z-WAVE: [Node 005] CC Entry Control notification {
eventType: 6,
dataType: 0,
eventTypeLabel: 'Home',
dataTypeLabel: 'None'
}
2023-08-15T19:03:40.732Z CNTRLR [Node 005] [Notification] Entry Control
event type: Home
data type: None
2023-08-15T19:03:41.026Z CNTRLR [Node 005] failed to decode the message, retrying with SPAN extension...
2023-08-15 15:03:41.248 INFO Z-WAVE: [Node 005] Value updated: 135-0-10-1 100 => 100
2023-08-15 15:03:47.249 INFO APP: GET /health/zwave 200 0.658 ms - 2140
2023-08-15 15:04:02.336 INFO Z-WAVE: [Node 005] CC Entry Control notification {
eventType: 6,
dataType: 0,
eventTypeLabel: 'Home',
dataTypeLabel: 'None'
}
As you can see there are 2
[Node 005] CC Entry Control notification {
eventType: 6,
dataType: 0,
eventTypeLabel: 'Home',
dataTypeLabel: 'None'
}
calls with one button push. The first one goes though and alarmo turns on the alarm but for some reason it thinks it failed so it requests it again. I think its the requesting it again which is taking so long.
If its hooked directly to the controller it does not request again and all is well.
The ring keypad has entry control settings that you can configure. By default when you press a button it waits 5 secs before actually reporting it to the hub. In my setup I changed it to 1 secs.