What people are actually building with NotifyBridge, two weeks in
Since launch, the most common first project hasn't been what I expected. I assumed smart home sensors. It's 3D printers.
The pattern: an ESP32 wired to the printer, one HTTP POST when the print finishes, a notification on the phone at 2am. Total firmware footprint is about a dozen lines, and the sketch is in our public examples repo.
A few other builds that came through the delivery logs and community submissions:
A garage door that complains after ten minutes open. A mailbox with a magnetic contact switch that pings when real mail arrives.
If you tried NotifyBridge after the launch here, I'd genuinely like to know what your first notification was. And if you built something worth sharing, the NotifyBridge-Devices repo on GitHub takes PRs — best examples get added with credit.
Still the same deal as launch day: 3,000 free notifications a month, credits that never expire, no subscription.
Replies
hest freezer door sensor would be perfect for this, ours never fully closes.
mailbox pinger is such a good idea.
does the esp32 sketch handle wifi reconnects on its own, or is that on me to write?
ny plans for a "battery low" style built-in trigger, or is everything expected to come from the device side?
battery-low trigger as a built-in trigger would be really useful, would save people from writing that logic separately for every device