ISY not seeing ELK zone change from "violated" to "normal" until manual query

[cwagner2401]

I have an ISY994i/IR PRO.  

  

I had the ELK module working fine but, then I upgraded ISY from 4.2.5 to 4.2.18 . Now I have zones on the ISY thatwill  immediately change from "Normal" to "Violated" fine but, won't update when the zone goes from "violated" back to "normal".  If I "Query all zones", the status will then change to "normal".

 

This issue has broken a number of important programs I have on the ISY.

 

Any help is much appreciated.

 

Thank You.

 

 

 

 

[cwagner2401]

Update:

 

The issue actually is happening both ways - "violated" to "normal"  and "normal" to "violated".  I loaded ELKM!.net on a computer to monitor the traffic between the ELK and ISY and then toggled the zone. I see the traffic on ELKM1.net  but, only occasionally see it on the ISY Event Viewer.

 

It appears that since upgrading ISY to 4.2.18, it's dropping ELK events.

 

I also notice that when I click on the ELK tab in the ISY console or try to toggle outputs, it takes a very long time to respond.

[Michel Kohanim]

Hi cwagner2401,

 

Would you be kind enough to check your error log. There seems to be some networking issues between ELK and ISY. Please note that in 4.2.18, we removed SSL in favor of TLS1.0. If you are using SSL communications with ELK, that might be one reason.

 

With kind regards,

Michel

[cwagner2401]

Hi Michel,

 

I see this error:

 

Sun 2014/12/21 10:58:18 PM System -170001 [uDSockets] HTTP:24 error:6

 

There are a lot of them and the HTTP: ranges from 24 thru 32.  error is always 6

 

Thanks.

[cwagner2401]

Michel,

 

FYI - I'm using a non-secure port on the ELK (2101), the ELK and the ISY are on the same subnet and the ISY is configured to use 2101.

[Michel Kohanim]

Hi cwagner2401,

 

Thank you.

 

Please do make sure you have configured the correct access code. Error 6 means that the other side (ELK) closed the connection. This happens if ELK does not like what's being sent.

 

With kind regards,

Michel

[cwagner2401]

Hi Michel,

 

The access code configured in ELK matches the code configured in ISY.  I read the ELK doc and endured that the access box isn't checked and that the six options are selected,

 

I do notice that although I see options for arm, disarm, etc, the list box to the left is empty.  The interface for the ISY is very slow on the ELK tab and it shows the zones are in area 0 (there is no area zero).

 

Thanks.

[Michel Kohanim]

Hi cwagner2401,

 

I do very much suspect network connectivity errors. Can you please do a Refresh Topology and then post the last entries in your Error Log?

 

With kind regards,

Michel

[cwagner2401]

Hi Michel,

 

I hit the "Refresh Topology" button in the ELK configuration tab.  The button "highlights" to indicate that its been pressed but, no dialog box pops up indicating that anything has happened.

 

Error Log Attached.

 

Thanks again.

 

 

ISY Error Log.v4.2.18__Wed 2014.12.24 12.39.17 PM.txt

[Michel Kohanim]

Hi cwagner2401,

 

Thank you. I see too many socket connections that are prematurely being closed by the client. I am not sure whether or not this has any impacts.

 

Can you please open Tools | Event Viewer, change the level to 3, redo Refresh Topology, wait for it fo fail, and then save and send me the contents of the event viewer.

 

With kind regards,

Michel

[cwagner2401]

Hi Michel,

 

Contents of event view after failed "refresh topology" is attached.

 

Thanks.

 

 

[Michel Kohanim]

Hi cwagner2401,

 

Nothing was attached. But, if it fails refreshing topology then it's certainly networking issues. Have you recently modified and/or changed your ELK firmware/bootloader/configuration?

 

With kind regards,

Michel

[cwagner2401]

Hi cwagner2401,

 

Nothing was attached. But, if it fails refreshing topology then it's certainly networking issues. Have you recently modified and/or changed your ELK firmware/bootloader/configuration?

 

With kind regards,

Michel

 

_{Hi Michel,}

 

_{This time log is attached.} 

 

_{No.  I haven't changed anything on the ELK. The problems started happening after upgrading the ISY from 4.2.5 to 4.2.18}

ISY-Events-Log.v4.2.18__Thu 2014.12.25 12.16.48 PM.txt

[cwagner2401]

Hi Michel,

 

I went back and read this document http://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:ELK_Security_Module

 

I found that my M1XEP (1.2.1.4) and My M1G (5.2.2) were not at the minimum revs.  I updated the M1XEP to 1.3.28 and the M1G to 5.3.0.

 

Now I can't connect to ELK at all and not only is the ELK module not working but, the things that were working before are not working now (the ELK could still control lighting via the ISY but, now it can't).  I saw a confusing part of that doc where it initially says the ISY needs to use the non-secure port but, then later on says if you have an ISY PRO, use the secure port and set the ISY client to TLS1.0/medium.  That doesn't work either.

 

The M1G is also refusing connections from my eKeypad.now.

 

I'm in a bit of trouble here. Do you have any ideas?

 

Thanks again.

[cwagner2401]

Hi Michel,

 

Ok.  I have it all working now.  The last issue was the M1XEP.  After upgrade, the non-secure port wasn't responding so, I went into ELKRP and unchecked/rechecked the enable non-secure port box and sent it to the system. After rebooting the M1XEP, the ISY connected and I can see all zones.

 

Thanks.

[Michel Kohanim]

Hi cwagner2401,

 

Sincere apologies for tardy reply. I am so very glad you got it working again.

 

With kind regards,

Michel