Rehearsal Notes from Bell House #1: The Mailbox

I taught band for 32 years. Every concert we played was rehearsed for weeks, wrong notes and all, before anyone heard it. That is how my wife and I run our house in rural Georgia, too.

Our home runs on Home Assistant, kept local wherever we can: about 500 devices, cameras, sensors, and a few hundred automations. I build it with an AI assistant (Claude) as a working partner. Nothing goes live in our house until it has been tested, watched for a week, and argued about.

Rehearsal Notes from Bell House is a series about what we built, why, and what we got wrong on the way. Post #1 is the mailbox, because it is finished, it works, and everyone has one.

The problem: a mailbox that cried wolf

Our mailbox sits at the end of a long driveway, right on the highway. We had a vibration sensor in it that pushed “Mail may have been delivered” to both our phones whenever the box moved.

The trouble is that a mailbox moves for a lot of reasons. Wind moves it. A sprinkler hits it. We walk down and get the mail ourselves. In one week of watching, 3 of 8 “mail delivered” alerts were not deliveries at all, and all three came on the same Sunday.

Two more things bothered me. The sensor sits at the edge of its radio range, so it drops out now and then. And it reports through its maker’s hub and cloud, so if the internet goes down, the mailbox goes quiet.

What we built: let the camera look

The idea came from watching the footage myself. I could see the carrier’s car stopped at the mailbox without zooming in. So the question was never “did the box move?” It was “is a vehicle stopped at the end of the driveway?”

Here is what happens now when the mailbox moves:

  1. Two UniFi cameras that already look down the driveway each take three pictures, 3 seconds apart. Six pictures, not one, so a car driving past does not look like a car stopped.
  2. Home Assistant sends the six pictures to Claude (Anthropic’s AI) through Home Assistant’s AI Task feature, with plain instructions: is a vehicle stopped at the mailbox, how sure are you, and what do you see, including any person on foot and what they are wearing.
  3. The answer comes back as a verdict: “mail stop” or “no vehicle,” a confidence level, and one sentence of description.
  4. Both our phones get a push with that sentence and one of the pictures attached. A long-press on the notification shows the full picture. My wife’s verdict: she loves seeing the carrier’s car right there in the notification.
  5. Nothing pushes between 9 PM and 7 AM.

The whole thing takes 40 seconds to a little over 2 minutes from the box moving to the phone buzzing. For a mailbox, that is plenty fast.

The wrong notes, and how we fixed them

This is the rehearsal part. We ran the camera check for a full week next to the old alert before trusting it.

  • It saw a car that wasn’t there. At sunset on the first Sunday, the AI said a “dark-colored vehicle” was stopped at the mailbox in all six photos, with high confidence. Both phones buzzed. I walked down: no mail. The footage showed no vehicle, just long pine shadows across the end of the driveway. We switched from the small, fast AI model to the top one with its thinking turned all the way up. It is slower, about 1 to 2 minutes instead of 20 seconds, and in the week that followed it never invented a vehicle again.
  • It got the details wrong. Early on it called a silver SUV “dark” and left out the carrier standing beside it. We rewrote the instructions: always mention a person on foot, describe the vehicle’s real color, and only say “high confidence” when the same vehicle sits in the same spot in at least two pictures.
  • It couldn’t tell the mail carrier from us. When one of us parked at the end of the driveway with the car door open, the AI correctly said “a vehicle is stopped,” which read on the phone as a mail delivery. The AI answered the question we asked. We had asked the wrong question for that case, so we closed that gap before the camera check replaced the old alert.
  • The sprinklers kept checking the mail. One sprinkler zone hits the mailbox post at night, so the box “moved” on watering nights. The check now ignores movement while that zone is running.
  • The assistant’s assumption was wrong, too. While judging that Sunday false alarm, it assumed “no mail on Sundays” and used that as evidence. Our mail runs on Sundays. We threw that rule out: judge the pictures, not the calendar.

Where it stands, and the next rehearsal

Since October 1 the camera check has been our only mail alert. The old “mail may have been delivered” push is retired. When the phone says the mail came, it shows us the car that brought it.

One piece still leans on the cloud: the sensor in the box that starts it all. So today I put an Aqara P100 sensor on the ceiling inside the mailbox, joined straight to our own Zigbee network, no hub and no cloud. It reached the house from the road on the first try, with a solid signal. For the next week it runs side by side with the old sensor, writing down every bump it feels. If it catches every delivery without crying wolf at the wind, the old sensor and its hub come out. That will be a future note.

Your turn

How have you solved mailbox detection? A sensor, a camera, a smart mailbox, or the mail carrier’s own notices? And if you use AI on your camera pictures, how do you keep it from seeing cars in the shadows? I would love to hear what worked for you, and what didn’t.

Next in the series: whatever we finish rehearsing next at Bell House.

Hang on, you got a reliable sensor which supports tilt/orientation detection & you’re still using it as a common vibration sensor instead of sticking it to the mail flap? Just switch it to detect tilt & you can do away with both the old sensor & the AI detection.

Yeah I’m kinda with Shadow here Andy.

You pulled in the Phantom Regiment horn line to play a scale and didn’t do Space Chords. May be a little overkill and missed the meat.

Same reason I don’t let an AI in on my leak detection. I report on it with AI but I don’t need it to tell me boss, water is wet.

Maybe cut the percussion feature back and let the guard do thier thing? (I wouldn’t toss it just rejigger to act onthe tilt sensor)

Now. One more time!

@ShadowFist @NathanCu Thanks, both of you, good ideas. Nathan, as an old band director, I felt that one.

I did think about putting the P100 on the door and using tilt. The catch is our carriers. We get different ones, and they all deliver from the driver’s seat, stretching out the window to reach in. Anything on the door sits right where their hand goes, and I’d rather not find the sensor in the ditch. So it’s on the ceiling of the box, out of reach.

On the AI being overkill, fair point. But the box opening only says someone opened it, not who. One of our three false alerts was us walking down for the mail ourselves. The camera is what tells the carrier’s car from us. If the ceiling sensor turns out clean enough by itself, the AI just becomes the “was it the carrier?” check.

I’m running the P100 side by side with the old sensor for a week and will post what it shows.

Ok you can keep the mellos.

That’s ok, I’m partial to counter melodies anyway.

Andy

I put a Yolink door sensor on my mailbox that detects when the mailbox door has been opened. The mailbox is at the end of the driveway, about 150 yards away from the main home structure. The device comms via LoRa has no problem sending signal back to the house. I track and display when mailbox door was last opened via Home Assistant, and also play an audio alert when the mailbox door has been opened (during typical delivery hours).

If you want local processing only, you have to use the Yolink Local Hub, which is somewhat pricey and a bit difficult to catch in stock, but Yolink is well supported in Home Assistant via multiple options, including a custom integration that keeps the comms local if you use the Yolink Local Hub. Their cloud-based solution is also pretty reliable, and the hub for that is significantly cheaper. I have a lot of Yolink sensors, and I also wanted local processing, so I use their Local Hub.

The system has been simple and rock solid for me. The sensor is affordable, has great battery life, and has been very reliable. Could it be fooled? Perhaps … but I can’t remember the last time I had a false alert for mail delivery.

Thanks, Dave, that’s a great setup, and 150 yards over LoRa is impressive. Funny enough, my original mailbox sensor is a YoLink too, on their cloud hub, and it has been reliable for me as well. My only itch was the cloud. The Local Hub is a fair answer to that, and I may end up there.

For now I’m giving the Aqara P100 a week beside the YoLink to see if it catches every delivery straight over Zigbee with no hub at all. I mounted it on the box ceiling rather than the door, since our carrier reaches in from the driver’s seat. If the P100 misses deliveries the YoLink catches, the Local Hub goes on my list. I’ll report back after the week.