Samuel, I have downloaded and installed both the free and the Pro (paid for) versions on my Samsung Galaxy Tab A 2016 (10.1) (SM-T580). Every time I click on one of the bottom to see a different screen, the app crashes and the restart.
I have not yet tried the app on my Huawei Honor 6X Smartphone…
Ray.
Ray,
What version of Android are you running? What is your station number?
–Sam
Sam, my tablet is running Android 7.0 with Octa-Core CPU at 1.6GHz with 2 GB RAM and 64 GB MicroSD
My station ID is 4809
Unfortunately, I do not have any screen captor software on the tablet, so I cannot send you a screenshot of the app before the crash.
Here are the operations I have done before the crash (and the crash can be repeated as often as I need/want to):
Depending how often I have restarted the app, I can restart the app or close it down.
Ray
Ray,
So, to clarify, it ONLY crashes on the PolarWind graph. Correct?
For the local forecast, what is the UV index and what is your local time?
For WF stations, there will be only one “forecast” and the is the local conditions. I plan on adding the online forecast services for WF stations later.
–Sam
Not correct! I gave you that particular procedure but it does always happen on the PolarWind screen. For example, I just clicked on the digital screen icon, then on the compass icon, then on the PolarWind icon, then on the graph icon and that is when the app crashed - the app seems to crash after the third or the fourth click, no matter which icon I click.
For the local forecast, the UV index is 0.3 and illumination is 2050 - there is no local time within the SWS Local Conditions box and the forecast is showing a bunch of clouds when both outside and on the WeatherFlow weather screen both show clear sky.
I do not know where you get the local conditions - I do not think the WeatherFlow Smart Weather Station produces its own weather conditions - I think the weather conditions displayed on the WeatherFlow weather screen come from Weather Underground!
Ray,
Thanks for the info.
When clicking away from the Graphs or the PolarWind, is the screen fully loading before you move to another screen?
For the local conditions, I use the UV index and your local time (time as shown in the upper right of the app). I have been working on getting a rock-solid “prediction” of the local conditions based on that.
If you are showing a UV of 0.3, that corresponds to it being cloudy.
I will look at your data from WF and make sure I’m not messing it up when it comes in.
–Sam
Before I click on another icon (to go to another screen), indeed, I wait for the current screen to display its information. But, even so, the app should be ‘solid’ enough to handle the clicking to another screen before the current screen is fully displayed - that is how many users seem to behave nowadays - too long, can’t wait.
I do not think that using the UV index nor the time of day nor the illumination is a good way to create a forecast or even the sky conditions - I have had a weather station for some 10 years and I know from experience that neither the UV index nor the brightness/illumination nor the solar irradiance can be used to guess the sky conditions, even more so for ‘predict’ the forecast…
For my local forecasts (the forecast for my immediate area) I use WXSIM (Interactive Local Atmospheric Model/Forecast) - it is a complex software that compiles, four times a day, lots of data from manned and automated weather station and buoys in a radius of about 300 KM.
So, I know that solely using the UV index and the local time to ‘predict’ the sky conditions is not possible. You would be better off to use the forecast from Weather Underground or some similar organizations…
Ray
Ray,
Looking at your data from today, you did not have any high UV (nothing above 1.53) reported by your SKY unit.
Looks like your SKY has not seen anything over 2.5 since you installed it.
I have worked with another WF user here for about a month compiling data from two different parts of the US to come up with a good “summer” setting for UV to Local Conditions correlation… which works.
I will be modifying that formulae to account for time of year, to more accurately display the current conditions.
I have reviewed WXSIM in the recent past, and actually am using some of the code from that to do a ‘Sager’ forecast for non WF stations in my app. It works pretty well predicting the near-future local forecast, based on the local weather station historical data. I will be adding that soon to the WF portion of my app as well, along with the online service forecasts.
Looking into the crashes you are seeing. Thanks for the feedback.
Sam, you will not see much UV Index nor brightness/illumination nor solar irradiance coming from my SKY unit as the unit has not been installed at its proper location - the unit is at a temporary location until I get the part I need to attach the SKY unit to the same mast where the anemometer and the ISS from my Davis Instruments Vantage Pro2 weather station are located.
Well, a couple of years back, I worked with Tom, the designer behind the WXSIM software, and I know from that experience that the code for WXSIM is well guarded and not share with anyone. Thus, you cannot be using any of the source code from the WXSIM software to do a ‘Sager’ forecast as the WXSIM forecast is not created using the code from ‘Sager’.
Talking/writing about the ‘Sager’ forecast … I have ‘dug up’ some old PHP/JavaScript code (circa 2010) to produce a ‘Sager’ forecast, should you need some additional code.
Ray.
Ray,
Again, thanks for the feedback.
If your station is NOT correctly sited, then of course my app will not be able to show an accurate representation of what the local conditions are. Once you have your SKY in it’s correct location and you have been able to re-review my ‘predicted’ local conditions, then let’s revisit this topic.
About the Sager script, you are correct. I followed a link here on the forums, and was assuming it was part of the WxSim software since that was part of the topic of the discussion. My apologies for alluding to them being the same. They are not.
Sam,
I was not reporting about the accuracy of the app - I understand that the app would not give me proper readings because neither the AIR not the SKY have been installed at their proper siting. 
What I was reporting about the app was it reliability/stability when I was trying the app on my tablet. As I wrote previously, why does the app crashes (completely stops itself only restarting a few seconds later after displaying the message that the app had closed) after one of the bottom button (the options) is clicked (the app usually crashes after the third or fourth click). 
Indeed, WXSIM is a very complex software, downloading data from hundred of reporting stations, compiling everything, comparing the new data with previously recorder data to finally produce a very accurate complete forecast (including cloudiness, temperatures, amount of rain or snow, snow levels, etc.). Just to satisfy your curiosity, have a look at the reporting site on the ‘On-Line Forecasts Made with WXSIM’ page. 
Ray
Ray,
Still trying to figure out why you are seeing a crash. I (and my beta testers) cannot reproduce the crash.
–Sam
Mine crashes only when I exit the app not by switching layaouts etc , I’m talking about the free-app for Android (Phone Galaxy S5 with Android 6) It’s no problem for me because I leave the app . I wonder if Ray sends the crash reports (in-app) to you maybe these reports make sense ?
Yes indeed , well I use the backbutton for exit and than an error is throwed
Next update will have a fix for that.
–Sam
Hi there.
I’ve just downloaded the free version and I noticed a couple of bugs. When I select rain to show in mm, it still shows inches in the text.
The other problem (although this seems to be directed more toward the weatherflow output) You show station pressure on your app, whereas the WF app shows sea level pressure. This is exactly the problem I discussed in another thread.
Your app is correct in showing station pressure, that is the relevant data. WF showing sea level pressure on their app/dashboard makes no sense. I have to correct my pressure to get it to match my Davis station. However, by doing that, it is adjusting sea level pressure and not the station pressure, which means the station pressure measurement is wrong. With all that said, both measurements are actually back-to-front.
I have the correct pressure showing on the WF app/dashboard, but that value should be for station pressure, not sea level.
I have the wrong pressure showing on your app, but that value should be for sea level pressure, not station pressure.
Until they fix this, it’s going to cause problems.
I’m interested in your thinking here. Surely if WF showed station pressure, then comparing pressure between stations would be impossible without knowing the altitude of the different stations? The benefit of SLP is that this factor has been removed. Therefore differences between stations can be related solely to dynamical differences in the mass of the atmosphere above a station (i.e. high/low pressure systems).
v334, coming out soon, will fix a lot of the issues in 328.
As for Barometric pressure, I am displaying both. Currently, Sea Level pressure is the primary one shown, but will allow the user to choose which they prefer (in a near-future release).
–Sam
Sea level pressure is not the one that should be adjusted. That’s exactly what is happening when I change my elevation. And by doing that, I have to adjust my elevation to below sea level to get a value to match my Davis station. That is simply not correct.
Station pressure is the one that should be adjusted, it always has been. This is exactly what you do on Davis stations, not sea level pressure.
Sea level pressure is calculated after you’ve calibrated your station pressure, you do not calibrate sea level pressure.