I’ve been pretty pleased with my Tempest, but miss having a usable console like Davis systems. I’ve been using the Tempest app grid as a “console” on an older iPad. IMHO it isn’t really suitable for that purpose. I want to be able to read the relevant readings from 6-8 feet away. It is also not very pleasing to look at. So I decided to write my own app. It is currently using UDP to get its readings, but I am adding API support as well so it will work away from home. This is a screenshot of the macOS version. A lot of Apple users have “retired” devices laying around like I do, and I’ll install it on an iPad Mini and display 24/7.
13 Likes
How does one get this app on the various platforms???
1 Like
They will be available in the Apple iiOS and macOS App Stores. I may make the macOS version also downloadable directly from a website, but can’t do that with iOS versions.
3 Likes
This looks likes like a great app. Unless you are charging for the app, is there any possibility you could share your code? Or at a minimum the UDP communication code?
Thanks
1 Like
Beautiful. I would love to know how to cook up an app like this. I’m thinking a little tweaking under the hood and it would make a fabulous Home Assistant dashboard.
PLEASE share the sources so we can learn from this one. It’s that good.
@peter’s wfpiconsole is in danger if this one keeps moving in this look+feel direction 
1 Like
Just noticed the name at the top of the screenshot. Makes it even better !!!
1 Like
There is a good example on Github here: https://github.com/hrbrmstr/weatherflow-local. It uses CocoaAsyncSocket here: https://github.com/robbiehanson/CocoaAsyncSocket. That was a better choice than the way I was grabbing the data originally.
There are native SwiftUI gauges that look like mine, but they are only supported by iOS 16+ and macOS 13+. The purpose was to let this work on older, often unused devices, so I had to create the gauges from scratch. Apples gauges are also primarily designed for watchOS. They do not scale well for larger displays. They are just png’s and scaling them introduces a lot of pixelation. That was another reason for developing my own.
I’m adding a small live, but non interactive radar display for the device location, or pre-defined lat/lon. I also still need to add API support, so the user can choose between UDP or API. API will allow it to work anywhere, while UDP is better for local use.
2 Likes
I certainly appreciate your pointers to code and your suggestions for implementation. But, believe it or not, I have designed and am in the process of implementing a sort of “antique” looking display. It’s going to have Nixie numeric displays, Nixie linear displays, analog meters with old looking dial faces and a stepper motor driven “hand” to indicate wind direction on a 360 degree display. I will use either a laser engraved or CNC routed panel holding the displays.
I’m going to use one or more ESP32-3 feather boards to collect the information and drive the displays. Am I crazy about this whole idea?More likely than not. But I’m a retired electronic engineer, looking for some fun. I have messed around with some code, but I got bogged down trying sort out and parsing all the information that the base station is capable of shucking out.
Thanks Again,
Phil
“The past can hurt. But the way I see it, you can either run from it, or learn from it.” ― Rafiki (The Lion King)
Tried looking for your app on the MacOS App Store, but couldn’t find it. Is it available yet?
Ian.
1 Like
Echoing the request to be able to use this nice-looking app! 