The Coda Bell

Oleg Vaskevich
Nov 8, 2017 · 4 min read

A few weeks ago, I got to be part of something special: the launch of Coda. To add a little ceremony to the occasion (it’s not every day you get to launch a company!), my coworker Chris Eck and I rigged up an old call bell to ring every time someone signed up. Here’s what it looked like:

One of our product managers, Matt Hudson, actually deserves credit for the whole idea. He had a call bell lying around, so we just needed to pick up a few extra parts and go from there. This post goes into how we built the Coda Bell.

Parts and Equipment

The most important part of a project like this is the brains — the microcontroller. I’ve personally used a bunch, ranging from a Raspberry Pi (one of the smallest Linux boxes out there) to an ESP8266 (awesome cheap WiFi chip!), but for the purpose of this project, we decided to go with a Particle Photon, for its excellent out-of-the-box cloud integration (we didn’t have a lot of time to mess with the TCP stack).

There wasn’t too much hardware complexity in the remaining parts: we just used an SG90 servo, an enclosure off Amazon, some wires and spare electronics parts, and a breadboard. No soldering necessary!

From Cloud to Device

When we noticed that Particle supported IFTTT (IF This Then That), we knew there was no chance we’d bother with polling our servers or dealing with interrupts for something like this. Instead, we went on IFTTT and configured the Webhooks service, linked our Particle account, and created a simple applet to publish a private signup event to the Particle Cloud every time the webhook URL was hit, which we’d set up to happen when someone signed up.

Image for post

The Webhooks service supports passing in a few values, so we set the data of the Particle event to:


Testing the IFTTT Applet

Now, to test that it worked, we used the particle-cli Node package to listen to the event:

$ particle subscribe signup mine
Subscribing to "signup" from my personal stream (my devices only)
Listening to: /v1/devices/events/signup

We then got the webhook URL from the Webhook service settings in IFTTT (e.g.,, and fired up Postman to POST to that URL with {“value1”: “123”}. A few seconds later, the message showed up.

Putting the Circuit Together

The whole project ended up being relatively straightforward with these components.

Image for post
Coda Bell schematic. Components connected by a dotted line are in practice optional.

When powering the Photon via USB, pin 1 supplies 4.8 V, which is in line with the operating voltage of the servo. The bypass capacitor C1 and bleeder resistor R2 in parallel with the servo act as a reservoir of energy for the power-hungry motor, which may otherwise behave erratically and draw too much current, while the D1 and R1 at the bottom are there for blinking a status LED.

Making the Bell Ring

The servo came with a few attachments, which we jerry-rigged to create a lever that swings to knock the clapper of the bell into the metal bowl. We then used epoxy to secure the servo in place.

Image for post
Underside of the bell, showing the mechanics of the servo ringing it.

Writing the Firmware

With the hardware out of the way, it was time to actually hook this thing up! Here’s the code:

This was mostly straightforward, but there are a couple things worth pointing out:

Servo Library

Particle ships with a servo library, which handled sending a pulse-width modulation (PWM) signal to the motor for us. We just tell it what position (in degrees) to go to, delay as needed, and it does the rest.


Thanks to Particle Cloud, listening to the webhook was as easy as calling Particle.subscribe(“signup”, onIfttt, MY_DEVICES). Our handler here assumes that the second line of the message contains an integer with the number of signups that have occurred since the last event, and the main loop handles consuming this count and ringing that number of times.

Since user signups can be viewed as a Poisson process, we wanted to make sure that the bell is able to cope with sudden bursts of people signing up, and this approach established a queue of sorts for ringing the bell. We put the counting logic in a critical section (via ATOMIC_BLOCK()) to make sure there weren’t any race conditions between writing and reading the count.

Finishing Touches

The last part of the puzzle was getting the server to hit the webhook URL when users signed up. We decided to throttle to 5 seconds to avoid overwhelming the IFTTT API. So, after a signup, we essentially deferred POSTing for that amount of time, and then batched together signups into a count that we then passed through as value1 in the request body to IFTTT.

Image for post
Not winning any design awards with this one, but it works great tucked away in a corner!

And there you have it! We had a blast making the Coda Bell, and I hope you enjoyed reading this. Feel free to adopt it yourself, and tweet at us if you do! Lastly, reach out to me if you have any questions, and P.S., we’re hiring. :)

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch

Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore

Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store