Motion Sensor Low Battery Email Alert

[Kentinada]

I have 3 2420 Motion Sensors all running on battery and I'd like an email when the low battery indicator comes on. What is the best method to make this happen? Thanks for the help.

[oberkc]

A progam is the best (may be only) way, in my mind.

 

The logic, if not exact wording, is pretty simple

 

If

control motion sensor low battery is switched on

then

send email message

else

 

Of course, you have to initially configure the email message.

[Xathros]

Hi,

 

I have found the low batt notifications to be quite unreliable on these motion sensors. The major issue with these is that they will only turn on the low batt node once and if that event is missed, there won't be another sent. That said, there a a few approaches to this. First you will need to configure one or more custom notifications that can ben sent when a low batt condition is detected. Then a program like the following is the simplest:

 

If
       Control 'Basement / Shop / Shop Motion / Shop Motion-Low Bat' is switched On

Then
       Repeat Every  12 hours 
          Resource 'NOTIFY - UTLITY - Basement Motion - Low Battery'

Else
  - No Actions - (To add one, press 'Action')

 

In that example, I am using network resources to send a prowl notification to my iPhone. You could just as easily sent a text or email message instead (and not need the network module to do that). This will notify every 12 hrs once a low batt event has been detected but as I said above, if that event is missed, this won't be of any value.

 

Another approach would be to set countdown timers that reset each time there is motion detected and send a notification whenever a counter reaches zero. Start the counters with a high enough value that under normal conditions they will not reach zero unless the battery quits and they stop sending motion events. This works fairly well in higher traffic areas, will be rock solid reliable but does delay the notification until the counter expires.

 

Hope this helps.

 

-Xathros

[Kentinada]

Thank you!

[C Martin]

I am currently using the following program:

If
       Time is  7:00:00AM
   And Status  'Motion Sensors / Front Door / Front Door - Outside-Low Bat' is On

Then
       $i_FrontDoor_MS.lo_Battery  = 1
       Send Notification to 'Motion Sensor Alerts' content 'Front Door Motion Det battery Low'

Else
       $i_FrontDoor_MS.lo_Battery  = 0

 

I am using similar programs for other motion sensors also.

This will give you a daily reminder until the battery is changed.

Seems to be effective.

[Kentinada]

What is the purpose of the variable? It doesn't appear that you ever test it.

 

Thanks.

[C Martin]

That's a good question.

I am using integer Variables and I believe my thought process was for a future use of variables when I do a power-on restart, since integer variables maintain values.

I sometimes use creative programming schemes for triggering other programs. ie. the possibility to selectively send certain email messages or notifications via a particular variable.

Sorry if I've thrown a detour in my code that misleads people. I guess my lack of use of comments is a glaring problem.

Thanks for pointing this out.

[Xathros]

Clarance-

 

The integer (or State) variables do not maintain their values through a restart or power loss. You can fix this however by updating the Init value anytime you changes a variable's value.

 

$i.myinegerMvar =+1
$i.myintegerMvar Init to $i.myintegerMvar

 

The "Init To" sets the "Initial value" that the mvar will have on startup. Otherwise the mvar will be initialized to whatever you devined when you created the mvar (0 is the default).

 

-Xathros

[C Martin]

Xathros,

 

Thanks.

[johnnyt]

Not only do they only go on once, I've found they go on long before the battery really needs to be replaced. I've also found the status stays on for a few days then changes back to off. Don't know what makes it tick. I set up a counter that increments every time motion or light sensor does something. I recently replaced a battery after about 22000 "events" with close to 5000 of those happening after the low battery warning occurred (then disappeared). It's not perfect because not every motion event is sent out (at least I haven't configured my sensors that way).

 

I like the countdown idea but what would be really great is a "last changed" timestamp on devices that could be checked by programs. I did submit that feature request but I think more people would have to ask.

 

 

Sent from my iPad using Tapatalk