I just wanted to shout out TRMNL.
They have an interesting product, and they’re trying to build a business that includes a lot of open source aspects.
The device that they sell is proprietary, but it’s also just an ESP32, screen, enclosure, and battery, with a custom PCB for convenience. They plan to add instructions to build your own device, and their firmware is open source under a GPLv3 license.
By default, their device connects to their servers, and they have a slick web configuration tool for people who don’t care about having smart devices call home, but you can easily modify the firmware to connect to your own self-hosted server instead. As of this evening, both the Phoenix and Sinatra server implementations are open source under an MIT license after I pointed out that they had no license in an issue, and they pretty much immediately updated the repositories.
There are two other repositories that they have not added a license to, but given their swift response, I’ll give them the benefit of the doubt, and I would expect them to be updated shortly.
They have not shared all of the plugins that are available on their hosted service for use on a self-hosted instance, but a few are available for use and there are many plugins made by others available as well!
As soon as they update those last two repositories, I plan to pre-order one (unlike the conceptually cool VU Dials who’s creators still have not added a license even after being called out by the co-creator of Rocky Linux).
You must log in or register to comment.
$20 to unlock the API killed it for me. If it has a built in way yo lock it down, it’s not an open platform and is a great way for bugs to brick a device.
Damn. I would really love one of these, to show off books, show my daily tasks, etc. Really unfortunate its locked down.
Charging a one time fee for the API seems like a decent way to ensure continued operation.
But if you don’t like it, you can run your own server
This is very similar to what Home Assistant offers as a paid service. I don’t see this complaint thrown at them, though. Also, any system that uses authentication has “a built in way to lock it down”.
Most apps if not all are closed source
Their guide still implies that you need to pay a fee to unlock an API key before you can flash a new firmware.
How they plan to enforce that fee to unlock an API key when the firmware is supposedly open source I don’t know. When I looked over the source code it looked like it was being written to a log.
I agree that the guide is VERY unclear. The documentation here is a bit better, but still bad and mentions a monthly cost for DIY devices instead of a one-time dev-level API key cost.
The gist is that if you want to use their servers and you bought their device, they have an API key built in to the device for their non-dev-level API access, and it’s not supported (maybe also against API TOS, but I’m not sure) to extract the API key and use it when you flash custom firmware. Getting the dev-level API key doesn’t have this issue, though, because they give that to you when you pay for it.
When modifying the firmware to use on your own server, you don’t have to pay them anything because you won’t be using their API.
Ah. Can’t really complain too much about them wanting people who are putting load on their servers to pay for it. Ideally, that should mean that the end user is not the actual product. Good to see more options joining Inkplate.
When does this ship to India?
There’s paperd.ink introduced some years back at IndiaFOSS
Thanks for sharing.
Probably never.
Looks really neat. I have an old Kindle e-ink screen I scavenged, but I have no clue how to actually interface with it. Being able to hack around with one would be nice.
I think this is designed for that https://github.com/vroland/epdiy
Hey, thanks! That’s really cool. I’ve never gotten a PCB made, but maybe this is a good first time to try it
Thats something I could be interested in…
Nice!
