Can not get disarm partition to work?

[Dafunktyfunk]

With all the developers tied up with HS3 it's going to be a while before this gets looked at. You may want to have a look at Blades DSC plugin to see if it works until the other one gets fixed.

I am having this same issue. It works just fine on the 1832 for me on hometrollers. We have one being interfaced into an 1864 and it seems to send the command but, it then rearms it right away, like it is sending the code twice.

Rupp,

Your comment about a delay due to HS3 and maybe we should use Blades is really not acceptable UNLESS, HS will be paying for that software. I am a PRO user and I bought PRO for all the additional Plugins it came with. So, suggesting I spend more money to fix a solution of HS's is really bad. You really can't expect users to accept that you have completely abandoned legacy users because you have ALL of your resources working on your new project. There needs to be at LEAST one person working on issues that come up like this.

I noticed that there is a bugzilla ticket assigned to Ryan that has not been touched in over a month.

This is a critical system component and needs immediate attention, please.

How is it that this can be escalated?

*** CONFIRMED *** HS TOUCH SENDS COMMAND TWICE!
I have confirmed that HSTouch is IN FACT sending the disarm function TWICE!

8/22/2013 3:12:32 PM - DSC Security - User 1 is disarming the panel
8/22/2013 3:12:32 PM - DSC DEBUG - Sending command to panel...
8/22/2013 3:12:32 PM - DSC DEBUG - Send Data: 0401****00FE
8/22/2013 3:12:32 PM - DSC DEBUG - Processing command:
Command_Acknowlege->50004029
8/22/2013 3:12:32 PM - DSC DEBUG - Command Acknowledge: Last Command Received:
040
8/22/2013 3:12:32 PM - DSC Security - User 1 is disarming the panel
8/22/2013 3:12:32 PM - DSC DEBUG - Sending command to panel...
8/22/2013 3:12:32 PM - DSC DEBUG - Send Data: 0401****00FE
8/22/2013 3:12:32 PM - DSC DEBUG - Processing command:
Command_Acknowlege->50004029
8/22/2013 3:12:32 PM - DSC DEBUG - Command Acknowledge: Last Command Received:
040
8/22/2013 3:12:33 PM - DSC DEBUG - Processing command: Beep_Status->90400633
8/22/2013 3:12:33 PM - DSC DEBUG - Processing command: LED_Status->90320FE
8/22/2013 3:12:33 PM - DSC DEBUG - Processing command: LED_Status->9034000
8/22/2013 3:12:33 PM - DSC DEBUG - Processing command:
LCD_Update->90100032System Disarmed No Alarm Memory 00
8/22/2013 3:12:33 PM - DSC DEBUG - Processing command:
Partition_Disarmed->6551D1
8/22/2013 3:12:34 PM - DSC DEBUG - Processing command: Beep_Status->90400633
8/22/2013 3:12:34 PM - DSC DEBUG - Processing command:
Exit_Delay_In_Progress->6561D2
8/22/2013 3:12:34 PM - DSC DEBUG - Processing command: LED_Status->90321FF
8/22/2013 3:12:34 PM - DSC DEBUG - Processing command: LED_Status->9034101
8/22/2013 3:12:34 PM - DSC DEBUG - Processing command:
LCD_Update->90100032Exit Delay in Progress E4
8/22/2013 3:12:34 PM - DSC DEBUG - Processing command: Tone_Status->905010160

So when the code is sent twice, it tells the panel to re-arm.

This does NOT happen from the WebGUI.

[Dafunktyfunk]

Re: Can not get disarm partition to work?

Greg(Rupp),

Can I please get a reply? This is a critical bug in HSTouch.

[jdntx]

Bugs reported

Both of the issues discussed here have been posted as bugs:
http://www.homeseer.com/bugzilla/show_bug.cgi?id=785
http://www.homeseer.com/bugzilla/show_bug.cgi?id=1244

[jdntx]

Good news, at least for the checksum bug (1244). HS responded to my ticket and fixed it as of version 3.0.0.18, which is available through the updater in HS3.

I tested and this fixes the disarm error for me. Not sure if they have updated the HS2 version of the plugin or whether you can upgrade to the new plugin and run it on v2.

[Sheriff]

I didnt even know...

Geeez, there I was all happy until I stumbled on this post; I had never tried to disarm Partition 2 via Homeseer and now I find that it doesnt work. Is the bugg fixed for HS2?

[jdntx]

Sheriff, I think they only updated the v3 plug-in. I made a patched version of the 2.0.0.14 DLL that I was using until I moved to v3 and they fixed it, but I'd rather not publish that to the public if there are better ways around it.

The easiest workaround for you would probably be if you were able to use a code where the digits add up to 25 or less, which should prevent the checksum bug. You might also try adding a comment to bug 1244 and see if HS will respond and fix it in v2 as well. I know they seem busy, but that seems like a reasonable request given the simplicity of the fix.

[Sheriff]

Solved with work around below.

Thanks. Solved with work around below.

[Dafunktyfunk]

Re: Can not get disarm partition to work?

Sheriff, I think they only updated the v3 plug-in. I made a patched version of the 2.0.0.14 DLL that I was using until I moved to v3 and they fixed it, but I'd rather not publish that to the public if there are better ways around it.

The easiest workaround for you would probably be if you were able to use a code where the digits add up to 25 or less, which should prevent the checksum bug. You might also try adding a comment to bug 1244 and see if HS will respond and fix it in v2 as well. I know they seem busy, but that seems like a reasonable request given the simplicity of the fix.

Thanks guys,

Can you please let me know if this workaround is for the double send in HSTouch or the checksum?

Also how do you lookup specific bugs by number in the bug tracker?

[Sheriff]

Sorry, I can't answer either question. However, changing my code numbers as suggested resolved my problem.