Hi, everyone. Long time Tempest and weatherflow pi console user here. I use this screen every day, and unfortunately I’ve reached a point where some things are annoying, the interface is old and outdated, so I decided to do something about it. I’m a firmware engineer by day, and a tinkerer otherwise. Have been developing software for over 30 years. I must give huge thanks to Pete Davis for his work on pi console over the years.
Thus, I present TempestLens. Based on weatherflow pi console, but is a complete rewrite. Gone is python (I hate python with a passion), replaced by a node backend and a much simpler modern frontend. This results in lower CPU usage on the pi, an easier install process, updates that install without console access, access to the interface remotely from your phone/pc, and ability to expand into different layouts/themes.
No subscriptions. No ads. No BS. I did most of this with Claude Code. I may be an engineer by day, but I’m also a family man and don’t have time to do this stuff manually. I’m also not a designer, so this is a huge help. My wife wants to make more designs to add, and I’d love some public feedback. I have designed this with the intent to have a ton of different designs and layouts added over time.
Very nice. Would it be possible to replace the need for anything WF (for forecast) with a more generic forecast provider ?
I’m thinking along the lines of this being a great weewx dashboard in the generic sense. A while back I wrote something to emit WF-compliant UDP from weewx so this would be fine as a listener and dashboard, but I’d need to replace the forecast part with something weewx-ish to remove any WF needs.
Curious why you’d want to do that since this is specifically for a Tempest station and the nearcast data their API provides. Is there something another specific API provides that WF can’t?
Because I no longer have any WF gear (crazy inaccurate for me) but your dashboard is beautiful and I’d love to port/fork/modify it to have no WF dependencies nor accounts required.
There are a variety of other forecast providers of course.
FWIW - I forked the nice ePaper display (link) similarly which is working great, but I definitely like your colorful dashboard.
Makes sense. Right now the web interface relies on the local service which collects UDP data from the Tempest and polls the Tempest API. That kind of setup would either require the frontend to be adapted to some other weather data api, or the server gets modified to pull the data to feed from a different API. At that point, without Tempest data, it’s worth questioning whether the local service is necessary because its entire purpose is to collect UDP data from the Tempest. It would be better to modify the web interface to support an additional API. I think that’s outside of the scope of this project, but certainly my repo could be forked to modify it accordingly. If done right, additional designs would be compatible.
As I said earlier, I wrote a weewx extension that emits WF-compliant UDP so I’m 99% sure I can get the live data without touching your code.
What I was asking about was relating to genericizing the forecast portion of the display so folks can use the weather forecast service of their choice. I did this without much pain for the ePaper display I mentioned in my previous reply.
But I speak python not javascript so this is a bigger lift for me. Thanks for the github repo which should make it doable.
(if it ever starts to rain again in the parched Seattle area - can’t waste the sunny days while they’re here)
Love the new style layout. Though i see in the center panel it has the +4.5/hr on the bottom, could it be possible on those appropriate panels lets say for this one next to the temp display (79.3) it would display an up or down arrow.
I live in Arizona and following the temps (and all the other data) is important to me. It allows me to adjust my hvac unit to hit the sweet spot of temp. Also the u/v tells me if my blinds are up or down.
Certainly possible. Is the +/- indicator not sufficient in the 3-HR trend?
A previous commenter mentioned a histogram, which I am planning to add to several of the panes. This would help with what you’re looking for.
But there’s an inconsistency here. 3-HR Trend uses +/- while the warmer/colder uses up/down arrows. I definitely need to use one or the other, but I was leaning more towards the +/-. I’m not sure I care which though.
if the +3.9F/hr was bigger. It just seems hidden to me. When I glance at it I have to search to find it, because the natural tendency for people is to see the “big” print first.
