e40

I was seeing the same, rebooted the EVL and all is fine now.

This is the second EVL4, Vista 20p, and ISY 994 setup I'm doing for my second home. Mine at home is working great, but it's been a few months since I got it set up, so I must be missing something. The 'Disarm, Arm Stay' etc. buttons for partition 1 are there, but the ISY console gives a 'Request Failed' after about 10 seconds. Nodelink seems to have everything else in place with the ISY. All of my zones are visible, and report status as they open and close... I've compared Nodelink and ISY configs between both systems and all look good. All I can think of is that I missed something in the 20p configuration for the EVL4? *21 quick arm is already set, that tripped me up the last time. Thanks all.

OK, sounds about right. I've got about 25 Z-wave devices, so the Schlage's have plenty of company. I have two extenders installed, about 5' line of site from the Schlages, but only the one close to the ISY is reliable. I don't remember as much trouble on the older pre-5.0 ISY firmware. EDIT / Update : Ahh. So, turns out that I have a BE469 with firmware 8.0, and a BE469ZP with firmware 10.9. The older one was the one farthest from the ISY and slow to report. So I switched them around, putting the older device close to the ISY, and it's much better.

I am trying to get reliable status updates from my BE469 Schlage locks to the ISY. The one close to the ISY will report reliably off the Access Control node (manual lock, unlock, user number, etc) But the one at my front door, far from the ISY, does not report anything from Access Control, but it will report lock/unlocked. (Albeit, slow, and sometimes won't report a change at all) I bought the RE7's based on some other threads I was reading. And while I believe it's helped with my distant Schlage lock, it's still not 100%. (And, adding to Z-Wave 'secured' was the path I was looking toward) Maybe I'm not on the right path.. hmm.

Hello, I bought a couple of these range extenders, and I can get them added to the ISY 5.3.4 without issue, but they are not connecting in the secure mode. I have tried the 'double tap' when pairing, but according to the node info they are connecting non secure. I've excluded the device, factory reset, tried many times over and still get to the same place. (security=none with both extenders) Any tips or tricks for this? Thanks, Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] ---------------------------------------------- Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] ZW 040 Repeater Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] ZW040_1 uid=40 security=None type=4.15.1 mid=881 tid=260 pid=189 Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] - x5E V2 ZWAVEPLUS_INFO Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] - x85 V2 ASSOCIATION Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] - x8E V3 MULTI_CHANNEL_ASSOCIATION Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] - x59 V3 ASSOCIATION_GROUP_INFO Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] - x55 V2 TRANSPORT_SERVICE Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] - x86 V3 VERSION Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] - x72 V2 MANUFACTURER_SPECIFIC Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] - x5A V1 DEVICE_RESET_LOCALLY Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] - x87 V3 INDICATOR Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] - x73 V1 POWERLEVEL Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] - x9F V1 SECURITY_2 Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] - x6C V1 SUPERVISION Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] - x7A V5 FIRMWARE_UPDATE_MD Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] - Secure Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] Wed 10/13/2021 03:44:34 PM : [ZW-SHOW ] ----------------------------------------------

Thanks for the quick replies, everyone. That was exactly the fix. This is on menu *21. Then 1, 1. (Three chimes) Thanks again!

Hello - I am trying to integrate my Honeywell 20p / EVL4 setup with my ISY994 using NodeLink. I got NodeLink set up smoothly on a dedicated VM, and got the node server / isylink set up without issue. My Honeywell alarm shows up in the ISY, and the zones report their statuses A-ok. I can disarm the system from the Partition 1 screen. (I have the disarm code set up in the NodeLink config page) However the Arm Away / Arm Stay buttons do not work. I am certain I am missing a simple critical link here, like having to provide a user code for disarm? The green LCD on the keypads will light up when I click arm within the ISY, but nothing happens. Thanks,

Hello - The variable seems to work as expected in 5.0.11B, thanks. I rolled back to 4.6.2 for now, eK Pro was showing the thermostat temps as "730" instead of 73.0 and wouldn't allow adjustments.

Hello - Yes, if I send myself a test email message with variable ${sys.node.ZW008_143.ST.raw} it displays it just fine. Interesting. I'll take a look at the alpha...

Hi Michel, Yes, this network resource & variable is on the ISY itself. What I'm trying to do is read the value from the energy meter, place it in a variable that I can view in eKeyPad to show current power consumption. As a test, I changed the path to /rest/vars/set/2/1/12345 and it populated the variable to '12345' as expected.

Hello, I'm trying to set a variable using a network resource pointing at my Aeon Labs Z-Wave energy meter. Here is how the node shows up: <?xml version="1.0" encoding="UTF-8"?> <nodeInfo> <node flag="0"> <address>ZW008_143</address> <name>ZW 008 Energy Meter</name> <family>4</family> <parent type="3">54812</parent> <type>4.33.1.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZW008_1</pnode> <sgid>143</sgid> <devtype> <gen>4.33.1</gen> <mfg>134.2.9</mfg> <cat>143</cat> </devtype> <property id="ST" uom="73" formatted="2030.52 Watts" value="203052" prec="2"/> </node> <properties> <property id="ST" uom="73" formatted="2030.52 Watts" value="203052" prec="2"/> <property id="TPW" uom="33" formatted="9.63 kWh" value="963" prec="2"/> </properties> </nodeInfo> And this is how I set up my network resource. GET /rest/vars/set/2/1/${sys.node.ZW008_143.ST.raw} HTTP/1.1 Host: 192.168.5.10:80 User-Agent: Mozilla/4.0 Connection: Close Content-Type: application/x-www-form-urlencoded Authorization: Basic **************** I get a 404 when I test it... Thanks in advance,