d00gster Posted October 20, 2017 Posted October 20, 2017 Folks, I finally got my Elk professionally installed and I have the latest firmware on the XEP (2.0.34) and the did the following 1. I set up a user account on my Elk M1 with all access options checked. 2. Configured my ISY994pro Network for TLS 1.0 for the client side and Medium security level. 3. I bought the ELK module for full control 4. I run 5.0.10 on my ISY 5. in the ISY ELK config menu, I placed the IP, checked TLS, use secure port 2601, configured a username and password on XEP that I configured in the ISY ELK option and finally enabled and saved the config. My isy console interface becomes irresponsive and once it goes back to a responsive stage, the topology doesn't show on ISY. It is worth mentioning that I ran a new cat6 cable between my XEP and my switch and ensured my switch port does not show an errors or collisions. I captured the following log, seems that I keep getting disconnected and reconnected. any thoughts? Fri 10/20/2017 18:33:37 : [ELK 0 0 0] (157/1/0) Fri 10/20/2017 18:33:52 : [ELK ] Connect SSL Fri 10/20/2017 18:34:00 : [ELK ] Connect SSL Successful Fri 10/20/2017 18:34:00 : [ELK 0 0 0] (156/1/0) Fri 10/20/2017 18:34:30 : Elk Load Topology Fri 10/20/2017 18:34:50 : CLI-HAMW: No Response from api.aerisapi.com Fri 10/20/2017 18:34:50 : CLI-HAMW: No Response from api.aerisapi.com Fri 10/20/2017 18:34:50 : CLI-HAMW: No Response from api.aerisapi.com Fri 10/20/2017 18:35:04 : [ELK ] Disconnect SSL Fri 10/20/2017 18:35:04 : [ELK ] Connect SSL Fri 10/20/2017 18:35:06 : [ELK ] Connect SSL Successful Fri 10/20/2017 18:36:22 : [ELK ] Disconnect SSL Fri 10/20/2017 18:36:22 : [ELK ] Connect SSL Fri 10/20/2017 18:36:24 : [ELK-ERR ] Get Topology Fri 10/20/2017 18:37:10 : [ELK ] Connect SSL Successful Fri 10/20/2017 18:37:28 : [ 37 BB 4E 1] DON 1 Fri 10/20/2017 18:37:30 : [ 37 BB 4E 1] ST 255 (uom=100 prec=0) Fri 10/20/2017 18:37:30 : [ 2B F3 EE 1] DON 0 Fri 10/20/2017 18:37:30 : [ 2B F3 EE 1] ST 255 (uom=100 prec=0) Fri 10/20/2017 18:37:30 : [ 2B E9 53 1] ST 252 (uom=100 prec=0) Fri 10/20/2017 18:37:30 : [ 2B F3 EE 1] ST 252 (uom=100 prec=0) Fri 10/20/2017 18:37:43 : [ 30 9 6B 1] DOF 0 Fri 10/20/2017 18:37:43 : [ 30 B 37 1] ST 0 (uom=100 prec=0) Fri 10/20/2017 18:37:43 : [ 30 9 6B 1] ST 0 (uom=100 prec=0) Fri 10/20/2017 18:38:20 : [ELK ] Disconnect SSL Fri 10/20/2017 18:38:20 : [ELK ] Connect SSL Fri 10/20/2017 18:38:22 : [ELK ] Connect SSL Successful Elapsed 01:09:04.728 : [ 37 BB 4E 1] DOF 1 Elapsed 01:09:04.730 : [ 37 BB 4E 1] ST 0 (uom=100 prec=0) Elapsed 01:09:05.276 : [ 2B E9 53 1] ST 0 (uom=100 prec=0) Elapsed 01:09:05.277 : [ 2B F3 EE 1] ST 0 (uom=100 prec=0) Elapsed 01:09:27.681 : [ELK-ERR ] Get Topology Elapsed 01:10:13.777 : [ELK ] Disconnect SSL Elapsed 01:10:13.778 : [ELK ] Connect SSL Elapsed 01:10:15.239 : [ELK ] Connect SSL Successful Elapsed 01:11:11.029 : CLI-HAMW: No Response from api.aerisapi.com Elapsed 01:11:16.140 : CLI-HAMW: No Response from api.aerisapi.com Elapsed 01:11:34.776 : [ELK ] Disconnect SSL Elapsed 01:11:34.777 : [ELK ] Connect SSL Elapsed 01:11:36.934 : [ELK ] Connect SSL Successful Elapsed 01:11:51.775 : [ELK-ERR ] Get Topology Elapsed 01:11:51.776 : [ELK-TX ] Get All Status Elapsed 01:11:51.828 : [ELK-TX ] Get All Status Fri 10/20/2017 18:42:20 : [ELK ] Disconnect SSL Fri 10/20/2017 18:42:20 : [ELK ] Connect SSL Fri 10/20/2017 18:42:22 : [ELK ] Connect SSL Successful Fri 10/20/2017 18:42:58 : [ 37 BB 4E 1] DON 1 Fri 10/20/2017 18:42:58 : [ 37 BB 4E 1] ST 255 (uom=100 prec=0) Fri 10/20/2017 18:42:58 : [ 2B E9 53 1] ST 252 (uom=100 prec=0) Fri 10/20/2017 18:42:58 : [ 2B F3 EE 1] ST 252 (uom=100 prec=0) Fri 10/20/2017 18:43:37 : [ELK ] Disconnect SSL Fri 10/20/2017 18:43:37 : [ELK ] Connect SSL Fri 10/20/2017 18:43:39 : [ELK-ERR ] Get Topology Fri 10/20/2017 18:43:40 : [ELK ] Connect SSL Successful
DennisC Posted October 20, 2017 Posted October 20, 2017 Try using the unsecure port and see if it works. Also, make sure to disconnect Elk RP software before trying ISY994 communications. Dennis
d00gster Posted October 21, 2017 Author Posted October 21, 2017 That worked, thanks Dennis, I followed a video that suggested the secure port, didn't realize it's not stable. ISY imported all zones, areas ... etc, one thing I can't do from my initial testing is to arm the elk. even though the panel indicates it is ready to arm and the user permissions on the ELK allow the ISY user I created to ARM, I basically checked all the boxes. any thoughts ?
cheezit73 Posted October 21, 2017 Posted October 21, 2017 Make sure you did not check the access box in RP: "Please confirm that your ELK system doesn’t have the “Access” attribute (box) checked for the User Code that is associated with the ISY system. The “Access” attribute is intended to be used as a special flag for the ELK Rules."
Recommended Posts
Archived
This topic is now archived and is closed to further replies.