A- I have one Tempest, one hub
1 Like
I hope you don’t mind that I added the Poll. Now if everyone will answer.
1 Like
One bourbon, one scotch, and one beer.
1 Like
If you voted in the Poll at the top AND you answered in a post, please edit your post and add the word Poll.
Two hubs, one w/Ground and Sky, The other w/Sky only.
I have a beta Tempest and a production Tempest on one hub and a SKY/AIR on another hub.
Cant wait to see what you come up with!
It’s really nothing all that dramatic. Based on the responses, I’ve added a pull down that auto-populates with a list of all Tempest devices discovered, and you select the one you want. If there’s only one, it just defaults to that one. Here are some screenshots:
5 Likes
It’s a clean dashboard with a wealth of data. I like it! 
1 Like
agreed! this looks great!
1 Like
Thanks! The one thing I want to add to the current conditions dashboard is “feels like” temperature. I’ve got a good Python script to calculate it, but Splunk doesn’t make it easy to just call a script and use the returned value. It’s doable, but I just need to work at it.
1 Like
Any chance you’d share the xml and scripts for these? I didn’t see much on splunkbase. I want to do something similar and it’s always nice to get a headstart 
I just got my first tempest yesterday and want to get going on tracking the data. I’m more of a splunk than weather type person, so much of this aspect is new to me.
I’m getting the raw data off the wire with the listen.py script on a pi zero - now I need to get it into my indexer.
If you want to share this, but not on splunkbase, consider gosplunk.com - this is a site my friend set up to share splunk stuff outside of splunkbase.
I’ve got the app packaged up and ready for release on Splunkbase, but the process Splunk employees have to go through to get things released there is changing so it’s a bit delayed. I’m happy send you a copy if you DM me your e-mail address.
Also, if you want to start getting data into Splunk now, follow these steps from my readme file:
Create an index named “tempest”. For sizing, assume about 25GB of index size for a year’s worth of data.
The Tempest weather sensor, via the Weatherflow WiFi hub, continously broadcasts weather observations and device status data over UDP port 50222. Configure a UDP input for that port on your indexer, with a source type of “tempest”. Select the “More settings” check box to set the destination index to “tempest”. The app doesn’t use the host field, so the host setting here isn’t important.
Wait a minute or two, then run a search for “index=tempest”, and you should see events coming in.
The field extractions that come with my app are built around the format of the data coming in directly via UDP and I don’t think will work with the data formatted by the listen.py script.
Thanks for the quick reply! I couldn’t find the dm option, maybe I’m too new. Just add gmail to my user name.
You work for Splunk? We probably have some mutual friends. Pam Sotnick is my account rep, I know most folks who work with her.
Yup, I know Pam! Stand by for an e-mail in a few minutes. I just need to package up the app one more time to make sure it has the latest changes.
I’d like to take a look at this as well. I’ll DM you my email. When setting up the source type, I assume that I’ll create a new source type, correct? (I’m mostly an end-user at work, but have my own dev instance and I’m still getting the hang of some of the admin functions).
Hey Eric- I know it’s been awhile but do you still have the Splunk app for tempest? I just got a tempest station and my Splunk instance set up!
Yes, I still have the app and I’ve been keeping it updated. Let me package up the latest version and I’ll send it to you as soon as I get a few minutes to login and do it.
1 Like
Awesome thbak you. Let me know and I can send you my email.