Armed (stay) (away)

ka7gzr · #1 February 2nd, 2006, 03:00 PM

I have noticed an old problem resurface in 3.0. The Homseer Staus page indicates Armed (Stay) when it's actually in the "Away" mode. The last 2.8 had fixed this problem.
Thanks,
Jim

jpape · #2 February 3rd, 2006, 09:41 AM

I'm seeing this also.

Judd

Bkphillips · #3 March 3rd, 2006, 11:17 AM

Is there via scripting to determine if the alarm is set to [Away] or [Stay] in the armed state? I'd like to fire different actions based on this type of arming.

BraveSirRobbin · #4 March 3rd, 2006, 12:33 PM

Quote:

Originally Posted by Bkphillips

Is there via scripting to determine if the alarm is set to [Away] or [Stay] in the armed state? I'd like to fire different actions based on this type of arming.

Might be what you want:

http://www.cocoontech.com/index.php?showtopic=3780

Did it quickly, wouldn't mind if you tested it out.

Bkphillips · #5 March 3rd, 2006, 01:01 PM

I have created the devices and dropped in the script - it seems to have run OK and updated the devices properly. I'll do more testing over the weekend by triggering events. Overall - I think this will work just fine.

Thanks.

BraveSirRobbin · #6 March 3rd, 2006, 01:09 PM

Quote:

Originally Posted by Bkphillips

I have created the devices and dropped in the script - it seems to have run OK and updated the devices properly. I'll do more testing over the weekend by triggering events. Overall - I think this will work just fine.

Thanks.

Did you test this with the latest plugin and HomeSeer 2.0? If so would you mind mentioning this (on CocoonTech) so others will know that [How-To] works with those versions (I'm only running the older versions of HomeSeer and this plugin presently).

For instance, does hs.waitsecs still work with HomeSeer 2.0?

Thanks,

BSR

Bkphillips · #7 March 3rd, 2006, 01:11 PM

Yes on HS2.0 and Caddx 3.0. I was able to disarm and rearm the alarm remotely and the staus' changed accordingly, so I think you have a winner on your hands.

Nitrox · #8 March 5th, 2006, 02:57 PM

Thanks Jim, not sure how this snuck back into v3.0 but the patch has been reapplied to fix it in v3.1.

-Nitrox

Quote:

Originally Posted by ka7gzr

I have noticed an old problem resurface in 3.0. The Homseer Staus page indicates Armed (Stay) when it's actually in the "Away" mode. The last 2.8 had fixed this problem.
Thanks,
Jim

ka7gzr · #9 March 6th, 2006, 01:14 AM

Dave,

Good to have you back, Man!!!

Jim

ka7gzr · #10 March 21st, 2006, 04:28 PM

Dave,

I'm running 3.1 and HS 2.1.8 and still see it indicating (stay) when it is armed (away).
Jim

Nitrox · #11 March 22nd, 2006, 02:08 PM

Quote:

Originally Posted by ka7gzr

Dave,

I'm running 3.1 and HS 2.1.8 and still see it indicating (stay) when it is armed (away).
Jim

Jim, Would you mind setting your log level to '3' and then performing and 'arm stay -> disarm -> arm away' and shipping me the logs? This is very odd that this bug keeps showing its face.

-Nitrox

ka7gzr · #12 March 23rd, 2006, 01:55 AM

Dave,

I have attached my log. I set the Armed (stay) @ 9:25:00, Armed (away) @ 9:26:30 and Disarmed @ 9:27:30. The HS status indicated Armed (stay) for both armed conditions (stay or away) and displays disarmed accurately.
Jim

Nitrox · #13 March 23rd, 2006, 10:16 AM

Quote:

Originally Posted by ka7gzr

Dave,

I have attached my log. I set the Armed (stay) @ 9:25:00, Armed (away) @ 9:26:30 and Disarmed @ 9:27:30. The HS status indicated Armed (stay) for both armed conditions (stay or away) and displays disarmed accurately.
Jim

Wow! I'm counting 94 zones, that is quite a setup. I also notice that the zone names never get sent from the panel so I assume you have them disabled, which is probably a good things since there's a ton of comm traffic already.

In an upcoming release I'm adding the option to save the zone names to the config file and have the plugin read them in instead of requesting them from the panel everytime HS is restarted.

I'm going to parse through the log and see if anything looks amok. Be back soon.

-Nitrox

jpape · #14 March 26th, 2006, 12:30 AM

Nitrox,

Could you also set the status of each zone device to either open or closed? I think this is more understandable in an "alarm" environment then on or off.

Judd

ka7gzr · #15 March 31st, 2006, 01:13 PM

Dave,

Were you able to see what the issue was from my log?
Thanks,
Jim

Nitrox · #16 April 5th, 2006, 05:47 PM

Quote:

Originally Posted by ka7gzr

Dave,

Were you able to see what the issue was from my log?
Thanks,
Jim

Jim, In the HS2 "Device" view what 'type' are the Caddx virtual devices? Do your's show as 'Virtual.1' or 'Caddx Device'?

-Nitrox

ka7gzr · #17 April 7th, 2006, 02:47 AM

They are all "Caddx Device"

Jim

kevingib · #18 April 7th, 2006, 07:08 PM

I still cant get my stuff to arm with the latest release either and my devices are all "Virtual.1". Should I delete and recreate them.

Also any update on getting the script fix in the updater? I still dont see it and the wife is getting pretty wrestless.

Nitrox · #19 April 7th, 2006, 08:52 PM

Quote:

Originally Posted by kevingib

I still cant get my stuff to arm with the latest release either and my devices are all "Virtual.1". Should I delete and recreate them.

Also any update on getting the script fix in the updater? I still dont see it and the wife is getting pretty wrestless.

To get your system to arm make sure the passcode is correct in the config and that the panel is configured to allow operations with pin.

I sent an update for v3.1 to Rick earlier today. Once it's in the updater it'll fix your scripting issue.

-Nitrox

kevingib · #20 April 10th, 2006, 11:42 PM

I applied the update and my script is still not working.

This is what the HS log shows:

4/10/2006 10:35:00 PM	Info	Event Trigger "Nighttime Arming"
4/10/2006 10:35:00 PM	Debug	The nighttime sequence has run to put the alarm system in the armed stay mode. The occurred at 10:35:00 PM on 4/10/2006.
4/10/2006 10:35:00 PM	Debug	Mon, Apr 10, 200610:35:00 PM4/10/2006 10:35:00 PMN/AN/AN/AN/AN/AN/ANoN/A
4/10/2006 10:35:00 PM	Info	Running script in background: arm_stay.txt

Here is the debug log:
4/10/2006 10:33:31 PM CaddxComm::zone_snapshot(): OLE->set z6 status to 3
4/10/2006 10:35:25 PM CaddxComm:

artition_snapshot(): Partitions = 1102020202020202
4/10/2006 10:35:26 PM CaddxComm::zone_snapshot(): OLE->set z6 status to 2
4/10/2006 10:35:30 PM CaddxComm:

artition_snapshot(): Partitions = 1302020202020202
4/10/2006 10:35:31 PM CaddxComm::zone_snapshot(): OLE->set z6 status to 3
4/10/2006 10:35:32 PM CaddxComm:

artition_snapshot(): Partitions = 1102020202020202
4/10/2006 10:35:33 PM CaddxComm::zone_snapshot(): OLE->set z6 status to 2
4/10/2006 10:35:37 PM CaddxComm:

artition_snapshot(): Partitions = 1302020202020202
4/10/2006 10:35:38 PM CaddxComm::zone_snapshot(): OLE->set z6 status to 3

I have verified the pin is entered and I am using the following script to invoke this:

sub main()
hs.plugin("Caddx Plug-In").ScriptIFace "Arm Stay,1"
end sub