SP6000 ip150 v1.39 disconnecting on arm/disarm

[vsidlu]

Hi, need help to figure out if my SP6000 or plugin drops connection with ip150. when I arm or disarm with homekit or keypad - connection is dropped and need to reconnect to get right status or arm/disarm.

Also if there is no arm/disarm I notice that connection is dropped and motion sensor status is not updating. Can not say what is reason for disconnect and how long is working without problems. Need help how to find out reason and fix it.

I can connect to SP6000 with BabyWare. Maybe there is options I need to turn on or off?!

[e-mcgee]

Hi,

I had a similar issue and yesterday updated the plugin yesterday. There was a bug in my code that in some instances closed the IP connection and then could not log back in because the connection was not recreated. I changed the code to always recreate the connection before login. I have been testing the last day and all seems to be stable. Please try the latest version 307.

[vsidlu]

Hi,

I update to 307. Right now I can not log in anymore! There is whats happening -

[Paradox] Mute : [false] [2/19/2018, 6:24:10 PM] [Paradox] Busy with alarm now - not getting status [2/19/2018, 6:24:10 PM] [Paradox] Busy with alarm - not getting status now. [2/19/2018, 6:24:14 PM] [Paradox] Alarmstate: [2/19/2018, 6:24:14 PM] [Paradox] 3 [2/19/2018, 6:24:15 PM] [Paradox] Mute : [false] [2/19/2018, 6:24:15 PM] [Paradox] Busy with alarm now - not getting status [2/19/2018, 6:24:15 PM] [Paradox] Busy with alarm - not getting status now. [2/19/2018, 6:24:16 PM] [Paradox] Changing connected state [2/19/2018, 6:24:20 PM] [Paradox] Mute : [false] [2/19/2018, 6:24:20 PM] [Paradox] Logging in [2/19/2018, 6:24:20 PM] [Paradox] Cannot get status - not logged in [2/19/2018, 6:24:20 PM] [Paradox] Got status [2/19/2018, 6:24:20 PM] [Paradox] Results: [2/19/2018, 6:24:20 PM] [Paradox] Zone 0 off (WC) [2/19/2018, 6:24:20 PM] [Paradox] Zone 1 off (Entrance) [2/19/2018, 6:24:20 PM] [Paradox] Zone 2 off (Guestroom) [2/19/2018, 6:24:20 PM] [Paradox] Zone 3 off (Bathroom) [2/19/2018, 6:24:20 PM] [Paradox] Zone 4 off (Kids room) [2/19/2018, 6:24:20 PM] [Paradox] Zone 8 off (Officeroom) [2/19/2018, 6:24:20 PM] [Paradox] Zone 9 off (Livingroom) [2/19/2018, 6:24:20 PM] [Paradox] Zone 11 off (Entrance Door) [2/19/2018, 6:24:20 PM] [Paradox] Alarmstatus :Disarmed [2/19/2018, 6:24:20 PM] [Paradox] Getting Status - Connected to alarm! [2/19/2018, 6:24:21 PM] [Paradox] Log in successfull [2/19/2018, 6:24:21 PM] [Paradox] Step 1 [2/19/2018, 6:24:21 PM] [Paradox] Step 2 [2/19/2018, 6:24:21 PM] [Paradox] Step 3 [2/19/2018, 6:24:22 PM] [Paradox] Special (Partition 1) [2/19/2018, 6:24:22 PM] [Paradox] Software log on [2/19/2018, 6:24:25 PM] [Paradox] Mute : [false] [2/19/2018, 6:24:25 PM] [Paradox] Logging in [2/19/2018, 6:24:25 PM] [Paradox] Cannot get status - not logged in [2/19/2018, 6:24:25 PM] [Paradox] Got status [2/19/2018, 6:24:25 PM] [Paradox] Results: [2/19/2018, 6:24:25 PM] [Paradox] Zone 0 off (WC) [2/19/2018, 6:24:25 PM] [Paradox] Zone 1 off (Entrance) [2/19/2018, 6:24:25 PM] [Paradox] Zone 2 off (Guestroom) [2/19/2018, 6:24:25 PM] [Paradox] Zone 3 off (Bathroom) [2/19/2018, 6:24:25 PM] [Paradox] Zone 4 off (Kids room) [2/19/2018, 6:24:25 PM] [Paradox] Zone 8 off (Officeroom) [2/19/2018, 6:24:25 PM] [Paradox] Zone 9 off (Livingroom) [2/19/2018, 6:24:25 PM] [Paradox] Zone 11 off (Entrance Door) [2/19/2018, 6:24:25 PM] [Paradox] Alarmstatus :Disarmed [2/19/2018, 6:24:25 PM] [Paradox] Getting Status - Connected to alarm! [2/19/2018, 6:24:26 PM] [Paradox] Error logging in [2/19/2018, 6:24:26 PM] [Paradox] Done logging in [2/19/2018, 6:24:30 PM] [Paradox] Mute : [false] [2/19/2018, 6:24:30 PM] [Paradox] Busy with alarm now - not getting status [2/19/2018, 6:24:30 PM] [Paradox] Busy with alarm - not getting status now.

Went back to 293 and no problem with logging but still problem with connection recreation.

Will appreciate help and thanks for your time!

[e-mcgee]

Hi, you may need to play with the delays in the config file. look at Issue#12 which had a similar problem in an earlier version that worked fine on my setup. I am convinced it is a timing issue you need to tune with the configurable delays ("logindelay" or "waitafterlogin"). I have an MG5050 with an IP100 and it works fine with 307 which is why I think yours is a timing issue. After issue #12 I enabled configurable delays in config.json to address this issue.

[vsidlu]

Hi, You were right! It took long time for me but I managed to find "logindelay" value and for me 400 worked. Now I see that I am connected. But still after arming/disarming I need to restart connection to get right status. If I do not do it then Alarm is trying to disarm or arm system forever. Log shows that I am connected but do not get right status. So I am back at square 1 - issue I had before. Do you have any other ideas what I am missing?

[e-mcgee]

You may need to also tune the other delays. There is a specific delay between command sent to the alarm. I use 250 but this may be too short for yours. Try changing that

[vsidlu]

Hi, My knowledge is to short to understand what thees delays do but right now seems changing "delaybetweencmds" to 550 works for me. Will test for couple of days and let you know. Thanks! Closing issue!

Using - raspberry pi 3 - Paradox SP6000 v4.94 - IP150s v1.39