Mailbox sensor

Simple PLEG. Roughly if tripped twice within 12 hours send alert.

(Tripped; NotTripped; Tripped < 12:00)

Edit: Corrected below.

@Z-Waver

(Tripped; NotTripped; Tripped < 12:00)

That will always return FALSE! There is only one timestamp for the Tripped state … so it can’t be both before and after the NotTripped state.

The correct syntax is:

(Tripped @ 2 < 12:00)

Doh. Thanks Richard!

Sorry guys; still slowing learning PLEG. this is what I have, but I keep getting an invalid key token: @

Trigger
MailBoxNotTripped
MailBoxTripped

Conditions
MailRetrieved (MailBoxTripped; MailBoxNotTripped; MailBoxTripped @ 2 < 12:00)

Actions
MailRetrieved — I have this turn on a light right now to test

Sorry guys; still slowing learning PLEG. this is what I have, but I keep getting an invalid key token: @

Yes you have combined a Sequence Expression with a Multiple Trigger one. They don’t mix. I think you just need this:

MailRetrieved MailBoxTripped @ 2 < 12:00

This will fire if MailBoxTripped becomes true twice in less than 12 minutes. Is that what you wanted?

Maybe this is better?

MailRetrieved MailBoxTripped @ 2 < 12:00:00

This will fire if MailBoxTripped becomes true twice in less than 12 hours.

Thanks Rex… was just looking over the basics guide as well a few examples, and came to the same conclusion. Even laughed at the 12 minute part, as I took your example earlier too literal :slight_smile:

I’m glad to hear the guide is helping.

I’m glad to hear the guide is helping.[/quote]

it does!

so… in testing this, it seems to fire at first instance, not when it’s tripped twice? Is there an easy way to reset everything in PLEG to test again?

Is there an easy way to reset everything in PLEG to test again?

If you define a new Trigger - same device but different name - it will have no history.

[quote=“RexBeckett, post:29, topic:185724”]

Is there an easy way to reset everything in PLEG to test again?

If you define a new Trigger - same device but different name - it will have no history.[/quote]

Ohh… that might be tough if I want to try a bunch of times to get it right. maybe I change the expression to be 2 < 5:00 so it resets every 5 minutes and I can try again?

[quote=“tomgru, post:20, topic:185724”]So i’m thinking something that records the first time the sensor is tripped (mail delivered), then a condition that send an alert if when it’s tripped a second time (someone got mail). that way, if driving by I don’t have the second notification, I know that there is still mail waiting.

thoughts?[/quote]

I’m going to do something similar…it’s my daughter’s “job” to get the mail when she comes home from school. So when she unlocks the door to come in, she will either be greeted with a “Hello (name), the mail was delivered at XX:XX today.” or (if she already got the mail on her way in), “Hello (name), thanks for getting the mail!”. I’ll do this by monitoring the “trip count” for the day.

I’ll reset a “trip count” every day probably around 9:00 AM. Up the count to 1 the first time it is tripped. I’ll allow several opens / closes during the first minuteor so immediately following the first trip (for those times the mail-main opens/ closes several times for whatever reason), and that will count as “trip 1.” Then I’ll up the trip count every time the mailbox opens.

Played with this today… doesn’t look good. :cry: i’m probably right at the limits of range from my outdoor GE appliance module, which has great line of site. But interestingly, when I check the neighbors on Schlage sensor, the GE is not listed as one. I wonder if they don’t have forwarding capabilities?

The GE 45604 Outdoor Module does support routing(“forwarding”). Though it is a n unrelated feature, it supports Beaming as well.

You’re not placing the sensor inside a metal box, are you? If not, you’re probably just outside the range.

are you american ? …
sorry just saw that post … and my troll-gen kicked in :stuck_out_tongue:

I am American.

A few years ago I had an issue with mail delivery, and was sent a packet of info from local post office on reasons for refusal for the mailman for delivering the mail.

One of the reasons listed was modified the mailbox in an unusual way.

Sent from my SAMSUNG-SM-N915A using Tapatalk

[quote=“kirkla79, post:35, topic:185724”]I am American.

A few years ago I had an issue with mail delivery, and was sent a packet of info from local post office on reasons for refusal for the mailman for delivering the mail.

One of the reasons listed was modified the mailbox in an unusual way.

Sent from my SAMSUNG-SM-N915A using Tapatalk[/quote]

One of the advantages of living in a free country, even the Post Office tells us what to do :slight_smile:

[quote=“Z-Waver, post:33, topic:185724”]The GE 45604 Outdoor Module does support routing(“forwarding”). Though it is a n unrelated feature, it supports Beaming as well.

You’re not placing the sensor inside a metal box, are you? If not, you’re probably just outside the range.[/quote]

Yep… big metal box. Guess I could put it on top just to test range. Wonder why I’m not seeing the GE in the routing table?

The door sensors I tried did not work inside the mailbox, but just holding them in my hands (outside) the range was fine. I am going to try a garage door tilt sensor, since the sensor is on the door and when the door opens it might be “outside” enough to send a signal. I’m not particularly confident though.

Joey, do you have a metal mailbox or a plastic one?

[quote=“kirkla79, post:35, topic:185724”]I am American.

A few years ago I had an issue with mail delivery, and was sent a packet of info from local post office on reasons for refusal for the mailman for delivering the mail.

One of the reasons listed was modified the mailbox in an unusual way.

Sent from my SAMSUNG-SM-N915A using Tapatalk[/quote]

What modification had you done, was it a sensor?