ELK/Eisy: No arm/disarm functionality

[SteveBL]

eisy/Iox: 5.5.4 Pg3: 3.1.20, Elk NS: 3.5.8

I'm having a few issues with the Elk NS that I can't figure out.
After a successful install of the NS everything populated fine but the "Armed Status" is not working, I can't arm/disarm from the eisy. I also see no errors in the log.
On the "Main House" screen "arming status" shows the current state, "Arm Up State" is accurate, as is Last User Keypad" and "Last Triggered Zone". Also the "Last Violated Zone" is not accurate. As I walk around and trigger zones manually they all report accurately as do the various arming/disarming settings.

Edited January 23, 2023 by SLiss
Accuracy edits

[Jimbo.Automates]

On 1/22/2023 at 12:53 PM, SLiss said:

eisy/Iox: 5.5.4 Pg3: 3.1.20, Elk NS: 3.5.8

I'm having a few issues with the Elk NS that I can't figure out.
After a successful install of the NS everything populated fine but the "Armed Status" is not working, I can't arm/disarm from the eisy. I also see no errors in the log.
On the "Main House" screen "arming status" shows the current state, "Arm Up State" is accurate, as is Last User Keypad" and "Last Triggered Zone". Also the "Last Violated Zone" is not accurate. As I walk around and trigger zones manually they all report accurately as do the various arming/disarming settings.

Is your user code correct?  Although it should throw and error if it's not valid.

[SteveBL]

User code is fine. I can arm and disarm the M1 with UD Mobile, although it is slow to respond, however, I cannot arm or disarm from within the admin console.

[Jimbo.Automates]

5 hours ago, SLiss said:

User code is fine. I can arm and disarm the M1 with UD Mobile, although it is slow to respond, however, I cannot arm or disarm from within the admin console.

Well that is very odd because they do the same thing.  But the slow response was fixed in 3.5.8 so that concerns me.  Can you close and reopen the AC and try again to confirm?  And when you do it, watch the node server log in Debug mode and see that it says something is happening?

[SteveBL]

Hi Jim,

I've sent both the "info" and "debug" files.

Again, I can arm/disarm etc from UD Mobile and I see instant response in the logs but nothing happens when I trigger from the AC;  no errors or info... nada.
 

 

 

Edited January 30, 2023 by SLiss
Clarity

[DennisC]

Are you hitting the "Set Armed Status" button?

[SteveBL]

Yes I am hitting the "Set Armed Status" button. All of the options are listed "Armed Away, Armed Instant Mode" etc but they do nothing and there is no activity in the Elk NS logs. Yet I can arm/disarm etc from UD Mobile and of course the keypad, with activity showing up in the log file.

[Jimbo.Automates]

@bpwwer any idea what could be wrong? Command works through UD Mobile but not the AC.

Sent from my Pixel 6 Pro using Tapatalk

[SteveBL]

Hi guys, I'm still have no local control with the eisy from the AC in setting the "Armed Status" and no errors in the NS log. Yet I can control it from UD Mobile and see it in the log.

I also installed a recent copy of my Elk Lighting file to ElkRP and I'm getting no control of any devices through the M1. No devices have been changed from the switch to eisy.

I have done restarts of the AC and PG3 and even re-installed the Elk NS with no success. 

Another anomaly is with hardwired motion sensors; all parameters are set the same for both sensors, one living room and one Office. I have a pgm that turns on my Office lights if motion is detected, and another pgm for the Living room that turns on path lighting from sunset to sunrise. The Office works perfectly and shows in the NS Log, yet the Living room doesn't work at all and no errors in the NS Log. Both sensors are working and can be triggered when tripped or if there is an alarm condition.

Everything worked for years with 994i

[DennisC]

You indictated no errors in the Node Server log, but is anything logged when you select armed and use the set button in the Node Server admin console?

 

[SteveBL]

No, that's what strange. There is no error or info in the log at all with regards to any query or action when using the Admin Console. Yet when I use UD Mobile I see it instantly in the NS Log.

[DennisC]

If you arm your Elk from the Elk Keypad, does the Node Server update to show you are armed?

[SteveBL]

Just checked it again. The NS reports status changes when armed/disarmed from the Elk keypad and shows changes when armed/disarmed from the UD Mobile.

[Jimbo.Automates]

Does changing the chime mode work from the AC?

Sent from my Pixel 6 Pro using Tapatalk

[SteveBL]

No status change with chime mode from AC, yet I see a status change instantly on the AC when activated from UD Mobile.

 

[Jimbo.Automates]

Open the node server configuration in the AC and check the IP address. I think on eisy it should be 127.0.0.1 ?

Sent from my Pixel 6 Pro using Tapatalk

[SteveBL]

Yes that is what it shows

[DennisC]

This may be way off, but......

If you are selecting the armed/disarmed mode from the drop down field in the admin console and selecting the "set" button on the left side, do you have any other device open at the same time (Elk-RP, any other Elk app, ect)?

There can only be one item connected at a time.

[SteveBL]

It should be that "eisy"... No, just the AC and/or PG3. The AC is not fully communicating with the NS yet reflects changes.

[bpwwer]

When you arm/disarm from the AC do you see any messages in the PG3 log? 

Commands from AC first route to PG3 and then PG3 routes to node server so if PG3 isn't seeing anything, that would imply that the AC isn't sending or isn't sending to the correct IP/port.

[Jimbo.Automates]

Yes, good idea Bob. @SLiss please check the PG3 log, not the node server log. But it still baffles me that it works from UD Mobile.

Sent from my Pixel 6 Pro using Tapatalk

[SteveBL]

Here is a list of Elk only AC log data, the jpg file.
The first arm/disarm was done via UD Mobile and the second set was armed from the M1 Kaypad.

Before and after these arm/disarm via UD Mobile and the M1 Keypad exercise, I tried to trigger directly from the AC with no logging posted to the AC log. There was data in the NS log which I forgot to include or save.

The zip file is the NS log taken a few minutes ago using the same procedure so the times are different. The first batch of data in that log shows activity in the NS from changing setting in the AC; arm/disarm and Chime settings. Again nothing was triggered and no activity showed in the AC but there is data in the NS log that I don't know how to read or decipher.

If you scroll down farther you will see that arming/disarming was successful when I used UD Mobile and the status on in the AC appeared immediately .

My apologies but I'm not familiar with PG3 or NS coding/data. I much preferred the "eisy" way and simplicity of the 994i Elk plug-in which served me well for many years.

Thanks again for all your help.

 

 

 

ELK_1-29-2023_65516-PM.zip

 

Edited January 30, 2023 by SLiss
Clarity

[Jimbo.Automates]

Sorry but this does not show the PG3 log that we asked for, that is viewed from the "Log" button in the upper-right of the PG3 UI.  Please do it again and "Download Log Package" which will grab both the NS and PG3 logs.  Also, don't post them, please PM them to Bob and I.

The first set armed status in the log you sent is at 12:02 for disarm, then 12:03 stay instant, then 12:29 to stay instant, then quickly disarmed, then disarmed at 1:39, stay instant at 6:07 then disarmed, night instant at 6:43 and disarmed all by user number 1.  All of these looked to succeed as far as I can tell.

Also, I'm confused because earlier you had said when you push the "Set Armed Status" that nothing shows up in the node server log, but now you are saying messages do show up in the log?  If the messages are properly showing up in the Node Server log when you press set armed status, then please set log to Debug+Modules so I can see the interaction with the ELK.    Also, do different armed status from the AC and UD Mobile and let me know which is which.

As for the "eisy" way comment, remember this is a brand new system, I'm sure when you started using ISY & ELK together that was a much more mature environment. 

 

[SteveBL]

My apologies Jim, I meant no disrespect. This is a new learning process for me and a bit daunting.  I started with Michele's ISY-26, transitioning from Homeseer and X10 back when Insteon was a baby. What an amazing journey this has been.

With regards to all of the arming/disarming processes, all were done using either UD Mobile or the physical Elk Keypad and all were successful.  I also tried arm/disarm from the AC but it did not work and has never worked so far.

I will PM you and Bob the Download Package.

 

[Jimbo.Automates]

23 hours ago, SLiss said:

The zip file is the NS log taken a few minutes ago using the same procedure so the times are different. The first batch of data in that log shows activity in the NS from changing setting in the AC; arm/disarm and Chime settings. Again nothing was triggered and no activity showed in the AC but there is data in the NS log that I don't know how to read or decipher.

Thanks, I got your PM and I'll look thru it.  But, I'm still confused.  Previously you mention the NS log doesn't show anything, when running commands from the AC but in the statement above it seems to say that you do see activity?