I am running Btstwx on two Galaxy Tab e tablets in the same room in my home, one near my wifes chair for her to view easily, and the other by my chair. One is a few years old and running Android 9, and the other is just a few days old and running Android 10. What I find strange is that, while all other readings match perfectly, the wind speed is always off by .2 mph to .4 mph on the Btstwx app, and the difference is even greater when running the Tempest app on both tablets simultaneously. Has anyone else noticed anything like this, or am I the only one crazy enough to have tow displays in the same room to notice it?
I will check how btstWx behaves in my test devices and let you know
–Sam
What’s the latest progress of the app rebuild @btst.online?
Still working on it. Been busy with ‘real’ work and other ‘life’ events (Hurricane Sally, DELTA!?, etc)!
But… it IS in the works!
Thanks to all for being patient!
Also… adding a new feature to the btstWx ecosystem… the btstWx Weather Box. Keep watching this thread for more details to come!
Is btstwx going into the kindle fire appstore? Noticed that there is another btst app in the store.
I plan on ensuring that it IS in the Fire Appstore with the next update.
–Sam
Question,
If you could have multiple data values on a graph, what would they be?
Temp vs Feels Like? Temp vs Dewpoint?
Wind Speed Vs Temp?
… gathering ideas for WeatherBox…
Lemme know!
–Sam
I only need wind and everything wind. My first priority are the maximum gust speeds because they are more representative of actual wind speeds when the anemometer is affected by poor siting. Next is the direction. Then comes average speed. Then comes the same set of data for another Sky or Tempest in my own station group. Then comes more Sky or Tempest or other type of wind readings from other stations. Currently I create myself a column of graphs on an html page of iframes displaying the wind graphs in order of their location along my coast where I paraglide.
I have not been able to use your App since my Skys began breeding and sprouting here there and everywhere.
Cheers Ian 
Temp/DP and Temp/feels like would be good. Temp/windspeed would be good for agriculture purposes.
I would love to see tempest lightning data because the sky lightning data is not as sensitive. Should be a way to tap into other users lightning data if they share it.
How about Temp/Feels Like/Dewpoint on the same graph?
Sounds like a winner to me!
In the end, I’ll make it user-selectable, just wanted some ideas on graphs to play with before fully integrating into my code.
–Sam
For Temp and Dewpoint display I also use humidity rather than feels like. I never use ‘feels like’ due to how it is never a true indicator and often exaggerates the cold etc.
When I am flying through the air or windsurfing the ‘feels like’ is not adjusted to my actual air speed or from the effect of evaporation on wet skin or wet suit or the water temp.
However humidity changes how the air moves up a hill and how much lift the air will generate so us paraglider pilots discuss humidity regularly.
cheers Ian 
WeatherBox is coming… Left display is local network, right is internet. Data is collected from UDP broadcast by a Raspberry Pi Zero W and distributed via a local webserver and an internet webserver.
Not 100% in sync, due to internet delays, etc. BUT, coming along quite nicely.
That looks great! Any rough ETA for its release?
I have a few people doing some beta testing the RPi setup now.
Planning on taking some time next week to ‘rebrand’ the app and allow it to connect to the WeatherBox data feed.
One thing to note… the weather data is ‘uncorrected’… it’s the raw data from the local UDP data, that is… WeatherBox never touches WeatherFlow’s servers. Data is stored on the RPi (one to several days worth) and my webserver (only 24 hours of data) for graphing purposes.
Currently WB allows you to select which data group you want to display (make public). That means you can view SKY data from your Tempest and AIR data from your AIR… or SKY data from your Sky and AIR data from your Tempest… so if you have multiple stations/devices, you can ‘cherry pick’ the public data.
My vision includes allowing the user to pick the specific data items to make public… like UV index from your Tempest, but Rain from your Sky… etc…
Even to the point of integrating data items from another WeatherBox station… for instance, if your Lightning sensor is dead, or misbehaving… then you could display Lightning from another public WeatherBox station.
A station owner will be able to make all data ‘public’, no data ‘public’, or hand-pick data items to make public from each device…
And… of course, integration with nearby NWS stations.
For demo purposes, I have WeatherBox running on 3 local systems:
Raspberry Pi Zero W:
Raspberry Pi 3B+:
CentOS Virtual Machine (VirtualBox):
