From: James Sentman <james-AT-sentman.com>
Date: 01 Jul 2009 07:16:07 UTC   (10:16:07 AM in author's locale)
To: xtensionlist-AT-shed.com

On Jun 30, 2009, at 9:28 PM, Robert Ladle wrote:

> I have one DS10A Security sensor of many whose periodic battery
> checks continue triggering the ON script for the device. The other
> security units show in the log but don't effect the ON/OFF scripts. I
> have been away from XTension for over a year and now back in again so
> I am rusty on the old stuff and missed a lot of the new stuff. I
> think I saw something in the email discussions but am having no luck
> finding the reference. Probably an easter egg but I don't know.
>
> Can the battery check for each device be separately captured and
> entered as it's own unit for follow-on monitoring/notification
> scripting? As I have it at the moment, several period battery check
> notifications from several units are just sliding right on by in the
> log and one is giving me false ON triggers. I'm not particularly
> looking for the scripts unless there are specific script(s) to use,
> but rather the mechanics/capturing of grabbing the battery check when
> it gets received.
>

Morning Bob,

The way the security sensors and the battery checks work is more or
less dictated by how the devices work. They send their status when you
open or close the door, but then they repeat the status every hour
even if it hasn't changed. There is no difference in the packet we get
from them if it's a change or a resend/battery check. So inside of
XTension if the new value is different from the old value then we
assume it's a real action and run the scripts and update the database.
If the state is a repeat of what is already in our database then it
will not run the scripts but it will save a unit property Last Message
Received date. This is updated for a real change, or a battery check
message so it will always contain the date of the last message
received from the unit.

If you're turning off the unit in XTension via some script or some
other way other than just waiting for the off from the device then
this would cause it to rerun the scripts the next battery check, but
apart from that it should not. When the message is received it will
run an on UnitPropertyChanged( TheName, The Value) handler that you
might have in the on script, so you can trap for last message date
there, but it should not run the on script as a whole. If you find
that it is I'd save off the scripts, delete and re-create the unit and
see if that clears things up. Let me know either way so I know if I
need to add something in there to my bug hunting list, but I've never
seen this happen.

Thanks,
James

James Sentman sentman.com MacHomeAutomation.com


_______________________________________________
XTensionlist mailing list
XTensionlist-AT-shed.com
lists.shed.com/mailman/listinfo/xtensionlist