3 ms·
Running a lot of javascript with npm and pupeteer just to render a small picture on a monochrome eink display seems extremely wasteful to me. You might as well
by csdvrx 4y ago
Running a lot of javascript with npm and pupeteer just to render a small picture on a monochrome eink display seems extremely wasteful to me.
You might as well have a ftp site (or equivalent) where you would just dump a YYYYMMDDHHMMSS.png (or jpg or whatever) and a script that just sends the latest to the display.
That would also let you run everything from initrd, so you can follow by a poweroff (and schedule a RTC wake in say 20 minutes)
- realharo 4y agoUsing a Raspberry Pi is very wasteful in the first place. If it's powered from USB, it doesn't really matter, but if you want to power it from batteries (especially something like AAA NiMH batteries) so that you can easily hang it on a wall somewhere and make it last a month or so (refresh every 10-15 minutes maybe), you pretty much have to use something much more low power (like an ESP8266, ESP32, etc.). Having pre-stored pictures is also unnecessary, just generate them on the fly. Unless generating the picture takes a long time (e.g. having to contact a lot of slow external services), you can just draw it on the server in memory with each request. In the same request, the device can also send its battery voltage to the server, where you can collect it as metrics.
- csdvrx 4y agoTotally this! I was just suggesting a slightly more efficient way that would not require the author to buy new hardware, but I agree: an ESP with direct IO to the "framebuffer" is better.