Hi, I\u2019m the problem, it\u2019s me.<\/p>\n
Some people can leave well enough alone, but not us nerds! You may recall a few years ago, I detailed my creation of a smart On Air sign<\/a> using a color e-ink display.<\/p>\n While I feel that project was largely a success, one major obstacle has kept it from being as useful as I\u2019d hoped: the long battery life.<\/p>\n What? How is long<\/em> battery life a problem, I can hear you asking. The issue is that the battery life is just long enough that I forget to recharge it until I happen to check and see that it\u2019s dead, invariably right before I start recording a podcast.<\/p>\n Now, I could just set a reminder to go off every few days to plug in the sign and recharge it, but simple solutions aren\u2019t how we ended up here in the first place, are they? Time for some OverEngineering\u2122!<\/p>\n The idea that came to me one day was sheer elegance in its simplicity: what if I built a system that let me know what the current battery level was so that I could charge it when it was getting low but before it had died?<\/p>\n Yep: here we go again.<\/p>\n As long as I was about to embark upon revising my code, I figured I might as well go whole hog. Back when I first set up my Inkplate e-ink display, I opted to use the standard firmware and write my code in the Arduino IDE. As I noted at the time, my expertise with the language wasn\u2019t high, but I figured I could muddle through with some help.<\/p>\n However, I knew that the other available option was to flash the board with the MicroPython firmware and I have spent more time working with Python in recent months, so it seemed like a good opportunity to take a crack at that as well. Fortunately, the instructions for installing the firmware on the Inkplate are fairly straightforward<\/a>, though I did have to do the usual amount of tweaking and looking up details to get it working.<\/p>\n The switch to MicroPython also meant I would be relying on command line tools instead of Arduino\u2019s GUI IDE, but as someone who\u2019s spent a fair amount of his life in Terminal, this wasn\u2019t really a drawback.<\/p>\n The next step was translating my existing code to run in Python. And while I probably could have done so myself, checking references as I went like I was moving text from English to French, it struck me that this is exactly the kind of task where an AI actually excels.<\/p>\n Enter ChatGPT. I fed it my Arduino script and asked it to convert it to Python, making sure to specify I was using MicroPython. That\u2019s important because, though MicroPython is<\/em> Python, it is more limited in the availability of modules and has some of its own particular quirks. I was even able to point the AI directly to Inkplate\u2019s MicroPython GitHub repository so it could see exactly what it was working with. And, of course, I made sure to read it all through to make sure everything seemed correct. But my code was pretty simple, so it was quick work to confirm that it did what I wanted; I was even able to remove a few little quirks that had been required by the strictures of the Arduino code.<\/p>\n The one big challenge I had to duplicate my existing functionality was in encoding of the images. As I mentioned in my previous piece, Inkplate provided a handy online tool to convert bitmap images to bytecode so the display could render them, but it turns out that Python\u2019s formatting of bytecode wasn\u2019t close enough that I could easily just reuse the existing versions. Instead, I spent quite some time working with ChatGPT to try and create a script that would convert bitmaps into compatible images\u2014this is one of those places where I quickly ran up against my own knowledge and limitations.<\/p>\n Much of that happened later in the process, but the important point was that I basically had the display up and running on MicroPython and doing everything it did before. Now for the fun part: adding new functionality.<\/p>\n My idea to monitor battery life meant having the charge level available online somewhere, which in turn required the board to send that information periodically. Good news: it\u2019s basic functionality already involved waking up every five minutes to check if it needed to change the graphic; I figured I could just piggyback on that cycle and have it send out the battery level when finished.<\/p>\n The first step, though, was figuring out the battery level, which is itself more art than science as the Inkplate doesn\u2019t calculate its own battery percentage. But thanks to the Inkplate code examples I knew that I could access the current level of battery voltage<\/em>, and based on checking the voltage both when the display was dead as well as after it had been charging long enough to presumably be full, I could come up with a very rough calculation of its current percentage\u2014enough to handle my situation of simply needing to know when it was getting low enough that I should charge it.<\/p>\n Once I had a way to calculate the battery level on device, I had to send it to my server. For this I turned to a different technology entirely: PHP. As a language that\u2019s designed to interact with a web server, this turned out to be the best option for collecting the information sent by the Inkplate. I had it send a small payload to my server with the current voltage, calculated percentage, and timestamp as a JSON file.<\/p>\n Now I just had to read it.<\/p>\n If I needed to display some arbitrary data in my menu bar, SwiftBar<\/a> was, of course, my first stop. I ran into a challenge, though, when I tried to use Python to build a plugin for it: due to macOS\u2019s handling of Python versions, it\u2019s a pain to use anything that requires modules or<\/em> to use virtual environments. I debated using PHP for this as well, but then stumbled across a simpler solution: SwiftBar recently added support for running plugins created in Shortcuts.<\/p>\n This actually turned out to be ideal for my solution. I wrote a simple Shortcut that grabbed the JSON file from my server and piped it out. I even went ahead and used SwiftBar\u2019s support for SF Symbols to add some a battery icon, complete with color coding: a full green battery for 50% and above, a yellow partially full battery for below that, and a red empty battery when it dropped beneath 10%.<\/p>\n I also added the calculated percentage and timestamp in the dropdown part of the plugin so I could get more information if I needed it.<\/p>\n As long as I was making changes, I dabbled with some other possible enhancements.<\/p>\n The biggest weakness of my On Air sign is that it only refreshes every five minutes. Ideally, I\u2019d like it to be instant, which would require some way to essentially ping it when to update. Unfortunately, my attempts along this line have remained fruitless.<\/p>\n While it is possible to connect wirelessly to the Inkplate and issue commands via a feature called webrepl<\/a>, there are two issues here: one, the Wi-Fi support in the ESP32 chip at the heart of the Inkplate can be finicky, taking a long time to connect or occasionally not connecting at all. Second, and more importantly, there appears to be no way to put the device to sleep and have it wake via the network, which means that it would have to be on all the time, drastically reducing the overall battery life.<\/p>\n I also experimented with having it sleep for just a minute between checks, but that proved so short an interval as to still take a big toll on the battery. It then occurred to me that I could have it sleep longer at times when I knew I wouldn\u2019t need it\u2014say, overnight.<\/p>\n Unfortunately, determining what \u201covernight\u201d is turns out to be a fraught pursuit. The Inkplate itself does not innately know the current time, so I have to use the That\u2019s not without its own problems. For one thing, the package\u2019s functionality is basic. Most critically, it has no way to account for daylight saving time which means, yes, I had to write my own function for figuring out whether it\u2019s DST or not, since the difference does impact when it\u2019s \u201covernight.\u201d<\/p>\n Moreover, the default So, for the moment, I\u2019ve stuck with using the built-in The battery life in this mode continues to be outstanding, and now that I have the information in the menu bar of my Mac, I can more easily track when I need to plug in the sign to charge it. While it may be a little ways off from my ideal version of this project, it\u2019s taken a small step forward that at least makes it more usable.<\/p>\n [Dan Moren<\/strong> is the East Coast Bureau Chief of Six Colors. You can find him on Mastodon at @dmoren@zeppelin.flights<\/a> or reach him by email at dan@sixcolors.com. His latest novel, the sci-fi spy thriller The Armageddon Protocol, is out now<\/a>.<\/em>]<\/p>\n![\"\"](\"https:\/\/i0.wp.com\/sixcolors.com\/wp-content\/uploads\/2025\/04\/onair-sign-2025-6c.jpg?ssl=1\")
Easy as Python<\/h2>\n
Battery of tests<\/h2>\n
![\"\"](\"https:\/\/i0.wp.com\/sixcolors.com\/wp-content\/uploads\/2025\/04\/onair-php-battery-6c.png?ssl=1\")
Swiftly now<\/h2>\n
![\"\"](\"https:\/\/i0.wp.com\/sixcolors.com\/wp-content\/uploads\/2025\/04\/onair-swiftbar-plugin-6c.png?ssl=1\")
It\u2019s all in the timing<\/h2>\n
ntptime<\/code> package baked into the MicroPython firmware to sync with a network time server.<\/p>\nntptime<\/code> package can fail with a timeout that kills the entire running program. There is the option to drop in a replacement package<\/a> which allows for more graceful failures, but I was unable to get that package to work with the NTP server that I deployed on my Synology.<\/p>\nntptime<\/code> functionality to add in long sleeps overnight in addition to checking every five minutes. I also updated my SwiftBar plugin to throw an alert if it\u2019s been more than 10 minutes since the battery status has been updated, which will help me track how often timeout errors become a problem. If it ends up recurring too often, I can always revert back to just the five minute check or figure out how to use that replacement module.<\/p>\n