tgutwin Posted March 8, 2016 Share Posted March 8, 2016 Hi, I have the Elk Module and ever since I updated my ISY firmware from 4.2.18 to 4.3.26 (back in December) The ISY will no longer ARM my elk system. I haver tried from the Admin console AND from the REST commands. I have also now also updated to firmware 4.4.2 and the failure to ARM error persists. Here is the Events from the event viewer: Notice it IS seeing the zone status changes and reporting everything else correctly. Below I open and then close a window Mon 03/07/2016 08:00:29 PM : [ELK-TX ] Get TopologyMon 03/07/2016 08:00:39 PM : [ELK-TX ] Get All StatusMon 03/07/2016 08:01:04 PM : [ELK-TX ] Zone Query StatusMon 03/07/2016 08:01:06 PM : [ELK 0 69 0] Zone : Laundry Room : 7.2 (53/72/0)Mon 03/07/2016 08:01:06 PM : [ELK 0 71 0] Zone : Spare Bedroom : 7.2 (53/72/0)Mon 03/07/2016 08:01:06 PM : [ELK 0 75 0] Zone : FamilyWestWindow : 7.2 (53/72/0)Mon 03/07/2016 08:01:06 PM : [ELK 0 81 0] Zone : UtilityRmWater : 7.1 (53/71/0)Mon 03/07/2016 08:01:06 PM : [ELK-TX ] Zone Query Voltage : [Zone 0]Mon 03/07/2016 08:01:53 PM : [ELK 0 77 0] Zone : FamilyEastWindow : Violated (51/2/0)Mon 03/07/2016 08:01:53 PM : [ELK 0 77 0] Zone : FamilyEastWindow : Open (52/1/0) <<--- window openMon 03/07/2016 08:01:53 PM : [ELK 1 0 0] Area : InsideHouse : Not Ready To Arm (2/0/0)Mon 03/07/2016 08:02:04 PM : [ELK 0 77 0] Zone : FamilyEastWindow : Normal (51/0/0) <<-- closed windowMon 03/07/2016 08:02:04 PM : [ELK 0 77 0] Zone : FamilyEastWindow : EOL (52/2/0)Mon 03/07/2016 08:02:04 PM : [ELK 1 0 0] Area : InsideHouse : Ready To Arm (2/1/0) I clicked Arm Stay... Mon 03/07/2016 08:04:12 PM : [ELK 0 0 3] Keypad : Front Entry : Access Code Valid (101/1/0)Mon 03/07/2016 08:04:20 PM : [ELK 0 0 3] Keypad : Front Entry : Access Code Valid (101/1/0)Mon 03/07/2016 08:04:29 PM : [ELK 0 0 3] Keypad : Front Entry : Access Code Valid (101/1/0)Mon 03/07/2016 08:04:36 PM : [ELK-ERR ] Arm Stay : InsideHouse Notice the last line error. I see the same when requesting through the REST calls or in my programs. As I said, everything else seems to working ok. This started after I updated from 4.2.18 to 4.3.26, without any other changes to my ELK or M1XEP. I am now running on 4.4.2.(did not fix it) I am NOT using SSL to the elk and using port 2101 Has anyone else seen this? What else can I do to troubleshoot this. Here is a screenshot of my rig 'about' box and xep settings: http://links.webarts.ca/isyElk The screengrab did not get accepted to embed in this post (?) tom Link to comment Share on other sites More sharing options...
jerlands Posted March 8, 2016 Share Posted March 8, 2016 There are a couple threads addressing this here and here and also the Wiki might provide a few pointers. If you follow the first link try re-entering username and password in ISY and disabling the "Access" attribute (Users/User Authorizations/Access.) Jon... Link to comment Share on other sites More sharing options...
elvisimprsntr Posted March 8, 2016 Share Posted March 8, 2016 When was the last time you updated the Elk and XEP firmware? Link to comment Share on other sites More sharing options...
tgutwin Posted March 9, 2016 Author Share Posted March 9, 2016 Thanks jerlands and elvisimprsntr to re-look at things. I got it solved. Somewhere in my initial debugging I borked my pre-defined user access code (fixed that) and while I was debugging recently, I always had RP connected (a no-no) The wiki steps highlighted the fact that it has to be disconnected. A major slap my forehead moment. Your tips forced me to look closer with fresh eyes. I am a couple steps back in terms of firmware, but within the ISY/Elk minimums. (elk=5.2.10 XEP=1.3.28) Thanks. tom Link to comment Share on other sites More sharing options...
jerlands Posted March 9, 2016 Share Posted March 9, 2016 Glad to hear you got it working! I'm looking into ELK and trying get a feel for it before the plunge Jon... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.