Unable to control Honeywell Panel with EVL4

[beninsteon]

Hi io_guy,

Writing to let you know that while I am able to get status from my Honeywell panel without any problems, I am unable to control it (arm/disarm). When I click any of the "Disarm" "Arm Away" "Arm Stay" or "Arm No Entry" buttons under the "partition 1" node, I get "Error TCP client read response failed [ISY]" (screenshot). Even when debug logging is selected for nodelink & the honeywell device I don't see anything in the log to reflect this button press. I've confirmed my disarm code is correctly entered in NodeLink.

Any suggestions you have would be appreciated. Thank you very much,

Ben

[io_guy]

I would guess you have the address configured wrong in the ISY for NodeLink.  

[beninsteon]

Thanks for getting back to me io_guy

 

13 hours ago, io_guy said:

address configured wrong in the ISY for NodeLink.

Not sure what you mean by that. Here's a screenshot of my nodelink config in the ISY (nodelink is running on 192.168.0.122), and the ISY config in nodelink points to the right IP address (192.168.0.111). Also, all other functions of nodelink are working. It's only arm/disarm functions of honeywell evl that aren't functioning.

 

[beninsteon]

Hi,

Just another piece of information with this problem: the first time after nodelink is started I try any of the disarm/arm away/arm stay/arm no entry buttons I get a different error message:

Subscriber didn't reply to event: 1 [90]

After that, I get the TCP client read response failed [ISY]

Screenshot attached.

Ben

[io_guy]

This'll have to wait till i get back from vacation.  Will look then. 

[beninsteon]

Thanks! Enjoy your time off

[skunkiechris]

Just an FYI, I also have an EVL4 with a Honeywell and those buttons work okay for me, so they're not universally broken - there must (obviously) be some sort of difference in our setups...

[beninsteon]

7 hours ago, skunkiechris said:

Just an FYI,

Thanks for letting me know. I'm not sure what could be wrong. I am getting info from V20p --> EVL -- > NodeLink --> ISY, but am unable to go in the other direction for some reason. Any suggestion would be appreciated!

[beninsteon]

OK, so I figured out part of the problem! The post above gave me hope I can fix this.

I discovered that nodelink was configured in the isy on port 8080 (instead of 8090). Not sure how that happened as this profile was installed automatically when I first installed nodelink.

When I updated the port to 8090, I no longer get those communication errors when clicking the buttons, and the Disarm button works. Unfortunately, the arm buttons do not work, but they do cause the backlight on my keypads to light up (so there is some message getting to the panel).

I had a look at my debug logs and there is nothing to reflect keypresses to the panel so I can't tell what nodelink is sending when I press the buttons.

Having a look at the EVL4 TPI Ademco documentation I think these are the commands in question:

disarm
^1,CODE1$

arm away
^1,CODE2$ 

arm stay
^1,CODE3$ 

arm max
^1,CODE4$ 

test
^1,CODE5$ 

bypass
^1,CODE6$ 

instant
^1,CODE7$ 

(where 1 is the partition being controlled, CODE is the 4 digit code and 1 through 7 is the actual command)

@skunkiechris, are you able to arm your panel with Nodelink? What panel are you using?

Thanks,

Ben

[skunkiechris]

I am able to...do you have one button arming enabled on the alarm panel?  (Where you just have to hit "Away" or whatever, you don't need a code first?)  I have a Vista 21iP, but the Honeywell/Ademco panels are all basically the same.  That's the only thing I can think of offhand that might be different...  

[beninsteon]

Aha, I've not enabled this. I will have a look at my manual to program. Thanks for the suggestion.

[beninsteon]

@skunkiechris

enabling field *21 fixed it!

Thanks,

Ben

[skunkiechris]

9 hours ago, beninsteon said:

@skunkiechris

enabling field *21 fixed it!

Thanks,

Ben

Glad to hear that worked!