Slow response to/from ELK NS

[garybixler]

I installed the ELK NS on the new eisy platform and am finding that commands sent to the ELK are very sluggish. Just took 20 secs. for the arm command to get to the ELK. Zone changes however are seen in less that 2 secs. It seems to be related with sending to the ELK only. Everything is configured as it was on the Polisy.  Tried resetting the ELK ethernet interface but no difference. Thanks. 

eisy-  5.5.2

PG3-  3.1.17

ELK-  3.5.7

Edited January 3, 2023 by garybixler

[garybixler]

I attached the log from the time of arming from the AC to where it actually armed. It was a little quicker this time. Can take up to more that 20 seconds. I also reinstalled the NS before trying the arming. Also Area1 Armed Status always shows disarmed even if armed from a keypad.

ELK Text Document (2).txt

[garybixler]

After reinstalling the ELK NS none of the iTech NSs will connect. Seems to be some conflict between ELK and iTech. Tried rebooting and reinstalling iTech but no change. Even tried installing a new iTech NS but still can't connect. The attached is the problem with iTech. With the iTechs disconnected the ELK is performing better and the arm status is displayed correctly. Still not responding as fast as it did on the Polisy however.

 

 

ELK Text Document (2).txt

[Jimbo.Automates]

I had issues bringing up my eisy last weekend so I wasn't able to try it out. Hopefully this weekend I will have free time, it's been a busy few weeks at work and home so I'm way behind around here.

Sent from my SM-X808U using Tapatalk

[Jimbo.Automates]

I finally got my eisy working and I see the same issue, this looks to be a network issue with eisy sending data to the local ELK python library which then sends the data to the ELK.  I'm not sure what to do about this, will need to discuss with @Michel Kohanim

The log below shows the NS sending the arm command to the library at 12:37:52 but that library doesn't receive/send the data to the elk until 20:38:09.

2023-01-07 20:37:52,945 Command    udi_interface      INFO     Area:cmd_set_armed_status: area_1:Home: elk.arm(0,****
2023-01-07 20:38:09,114 ELK-5703   elkm1_lib.connection DEBUG    connection:write_msg: write_data '0Da010031960037'
2023-01-07 20:38:09,115 ELK-5703   elkm1_lib.connection DEBUG    connection:_read_stream: got_data '16XK24252070701230100072'
2023-01-07 20:38:09,115 ELK-5703   udi_interface      INFO     Controller:callback: ELK Controller: cs={'real_time_clock': '2425207070123010'}
2023-01-07 20:38:09,115 ELK-5703   udi_interface      INFO     Controller:callback: real_time_clock=2425207070123010
2023-01-07 20:38:09,132 ELK-5703   elkm1_lib.connection DEBUG    connection:_read_stream: got_data '1EAS2000000041111111000000000009'
2023-01-07 20:38:09,132 ELK-5703   udi_interface      INFO     Area:callback: area_1:Home: cs={'arm_up_state': <ArmUpState.FULLY_ARMED: '4'>}
2023-01-07 20:38:09,132 ELK-5703   udi_interface      INFO     Area:set_arm_up_state: area_1:Home: ArmUpState.FULLY_ARMED

What I am not sure of, is does the 'write_msg' debug line print when it starts the write_msg, or when it completes.  I'll look into that tomorro, and I will try pulling the NS out of the equation by just using the python library to send commands to the ELK.

 

[Jimbo.Automates]

This is taking a while to debug. It works fine outside of the node server, so I'll need to write some custom code that uses the library in the same was as the node server and see if that shows the issue. 

The 'write_msg' is displayed immediately before it tries to actually send the data to the ELK so I'm have no idea why it would take so long to print that message.

 

 

[AllDigital]

I have the same issue. I just migrated over to EISY from a 994i. When I send commands to the Elk it has a substantial delay. If I send a lot of commands, like speaking ten words in a program, it takes a lot longer (>30 seconds for ten words). If I send ten speak commands they all speak at once correctly, but there is a 30+ second delay to start speaking.

[Jimbo.Automates]

Please update to 3.5.8 and let me know if that helps.  I'm not home so I can't confirm.

 

[garybixler]

Thanks. The ELK is working as it should. No delays. 

[Jimbo.Automates]

Thanks. The ELK is working as it should. No delays. 

Awesome! Thanks.

Sent from my Pixel 6 Pro using Tapatalk

[AllDigital]

Awesome. Thank you @Jimbo.Automates Jim. Mine is also working correctly now. This is a great Node Server.