MomBoard: E-ink display for a parent with amnesia

What a beautiful use of technology to uphold someone's personhood, and let them know they are loved, despite (and with regard to) a profound injury.

This reminds me of a desire I've had for a long time: a simple, wall-mountable eInk device that could be configured with a URL (+wifi creds) and render a markdown file, refreshing once every hour or so. It would be so useful for so many applications – I'm a parish priest and so I could use it to let people know what events are on, if a service is cancelled, the current prayer list, ... the applications would be endless. I'd definitely pay a couple of hundred dollars per device for a solid version of such a thing, if it could be mounted and then recharged every month or two.

I'm a backer, but this would probably fit your bill https://www.kickstarter.com/projects/usetrmnl/trmnl-the-e-in...

I wanted the same kind of general eink device, but this is also supposedly super hackable!

hackable indeed :) https://docs.usetrmnl.com

no longer a Kickstarter btw, shipping same-day now (see homepage)

> Most IoT products support SSH-ing directly into peripheral devices. We've heard too many horror stories about how this can go wrong, and decided to invert the paradigm.

> Your TRMNL device pings our server, never the other way around.

> Each request made to our /api/display endpoint includes only the minimum details needed to support customers -- an API key, device mac address, firmware version, battery voltage, and wifi signal strength.

Super hackable but it pings their hosted server and nothing else?! Is there a way to run your own server?

The docs aren't super encouraging either. https://docs.usetrmnl.com/go/diy/byod-s

> Purchase a TRMNL from our home page: https://usetrmnl.com

> Then follow the instructions on BYOD/S > Server.

> More TBD.

They seem to have the api base url hardcoded in their firmware[1]. The repo seems to have pretty clear instructions for compiling and flashing modified firmware. From there, it's just a matter of writing a decent server to implement the calls documented in BYOD/S[2] and Private API.[3]

[1]: https://github.com/usetrmnl/firmware/blob/e3db8c37990c2333ec...

[2]: https://docs.usetrmnl.com/go/diy/byod-s

[3]: https://docs.usetrmnl.com/go/private-api/introduction