Watchy

by Squarofumi

Image of Board

Watchy is an E-Ink watch with open source hardware and software. It has a barebones design utilizing the PCB as the watch body, allowing it to be worn as-is, or further customized with different 3D printed cases and watch straps. It is a unique timepiece that is also a wearable development platform, allowing users to create their own experience.

Watchy’s E-Ink display delivers an always-on, beautiful, crisp image clearly visible under bright sunlight, and requires no power between updates. At 200 x 200 pixels and monochrome, the display offers a distinctive aesthetic.

Watchy has both Wi-Fi and Bluetooth LE connectivity, allowing it to connect with internet APIs (e.g., weather, news, traffic, maps, Spotify, etc.), as well as Bluetooth LE enabled devices.

With makers/hackers/tinkerers in mind, we chose the ESP32 for its large community and support for a wide variety of development options, such as Arduino, Micropython, ESP-IDF, and Zephyr-RTOS.

Features & Specifications

  • Ultra-low-power e-paper 1.54” display with 200 x 200 resolution and wide viewing angle
  • Wi-Fi & Bluetooth LE connectivity
  • 3-axis accelerometer with gesture detection
  • Real-time clock for accurate time keeping with calendar and alarm functions
  • Built-in USB-to-serial adapter for programming on the go
  • Vibration motor for alerts
  • Four tactile buttons
  • Open source hardware & software
  • Tons of examples & cool watch faces
  • 3D case designs (stls) to customize your watchy (and watch straps)
  • Injection-molded plastic case

Purchase

Contribute

Have some info to add for this board? Edit the source for this page here.

CircuitPython 9.1.0-beta.1

This is the latest development release of CircuitPython that will work with the Watchy.

Alpha development releases are early releases. They are unfinished, are likely to have bugs, and the features they provide may change. Beta releases may have some bugs and unfinished features, but should be suitable for many uses. A Release Candidate (rc) release is considered done and will become the next stable release, assuming no further issues are found.

Please try alpha, beta, and rc releases if you are able. Your testing is invaluable: it helps us uncover and find issues quickly.

Release Notes for 9.1.0-beta.1

DOWNLOAD .BIN NOW

Built-in modules available: _asyncio, _pixelmap, adafruit_bus_device, adafruit_pixelbuf, aesio, alarm, analogbufio, analogio, array, atexit, audiobusio, audiocore, audiomixer, binascii, bitbangio, bitmaptools, board, builtins, builtins.pow3, busdisplay, busio, busio.SPI, busio.UART, canio, codeop, collections, countio, digitalio, displayio, dualbank, epaperdisplay, errno, espidf, espnow, espulp, fontio, fourwire, framebufferio, frequencyio, getpass, gifio, hashlib, i2cdisplaybus, io, ipaddress, jpegio, json, keypad, keypad.KeyMatrix, keypad.Keys, keypad.ShiftRegisterKeys, keypad_demux, keypad_demux.DemuxKeyMatrix, locale, math, mdns, memorymap, microcontroller, msgpack, neopixel_write, nvm, onewireio, os, os.getenv, paralleldisplaybus, ps2io, pulseio, pwmio, rainbowio, random, re, rotaryio, rtc, sdcardio, select, sharpdisplay, socketpool, ssl, storage, struct, supervisor, synthio, sys, terminalio, time, touchio, traceback, ulab, vectorio, warnings, watchdog, wifi, zlib

Absolute Newest

Every time we commit new code to CircuitPython we automatically build binaries for each board and language. The binaries are stored on Amazon S3, organized by board, and then by language. These releases are even newer than the development release listed above. Try them if you want the absolute latest and are feeling daring or want to see if a problem has been fixed.

Previous Versions of CircuitPython

All previous releases of CircuitPython are available for download from Amazon S3 through the button below. For very old releases, look in the OLD/ folder for each board. Release notes for each release are available at GitHub button below.

Older releases are useful for testing if you something appears to be broken in a newer release but used to work, or if you have older code that depends on features only available in an older release. Otherwise we recommend using the latest stable release.