dbwarner5 Posted March 12, 2022 Posted March 12, 2022 Have noticed that the NS brings over two pieces of lightning data.... I think its distance and strikes. The tempest has three pieces of data: Last detected in time, distance and # of strikes in the last three hours. The data doesn't seem to match See screen shots below.
bpwwer Posted March 12, 2022 Posted March 12, 2022 You're lucky I saw this, it was in the wrong section. I've moved it to the WeatherFlow section for you. Lightning will never match with the app if you are using local data with the node server. WeatherFlow uses your stations local data plus other stations and other sources to calculate the lighting data it displays on their app. The node server is only using your stations local data**. The same can be true for rain data where they manipulate that in the servers to provide more accurate than what they get from the sensor data alone. The ISY doesn't currently deal with time data very well. Is there a specific use case where knowing that data would be useful over # strikes and distance? The local sensor is reporting real-time data for this, not accumulative or historical. I.E. # of strikes is reported like:1 0:00:00 - 0 strikes, 0 distance 10:01:00 - 1 strike, 5 miles 10:02:00 - 0 strikes, 0 distance ** The node server can be configured to pull the data from the server instead of the direct local sensor data. In this mode, it should match.
dbwarner5 Posted March 13, 2022 Author Posted March 13, 2022 @bpwwer Thanks Bob for moving the thread and the response. Am not sure what would be the best solution. The goal would be for the isy to alert me if lightning is a) within a certain range, b) it is moving closer (done through calculations and variables from the distance data, as it changes). I didnt realize that the lightning data on the app isn't coming directly from just my tempest, but from the server. Is the configuration for the NS to pull from the server vs the local tempest a user choice or a programming choice you would make / modify in the NS? If its the first, then I can play with it to see what makes sense, just let me know how. If its the latter, then that would probably be a large group discussion / consensus based on what others might be doing with the data. I just have never really seen any data on the NS yet, but its winter so we aren't really having any lightning! Thanks again for all you are doing to move Polisy forward!
bpwwer Posted March 13, 2022 Posted March 13, 2022 The choice is yours. When you configure the node server the station ID is marked as either "local" or "remote". Local means direct from the hub on your local network, remote means from the server in cloud. The 'remote' option was intended for people that have a weatherflow at a second, remote, location that they want to monitor. But it works fine for a single/primary location as well. Originally, the Tempest (or maybe it was just a subset of them) wasn't reporting any lightning data yet the app would still display info. This caused many node server/plug-in bug reports. And as you've noticed, WeatherFlow doesn't really make it obvious that they do massage the data from the sensors before sending it the app.
dbwarner5 Posted March 13, 2022 Author Posted March 13, 2022 54 minutes ago, bpwwer said: The choice is yours. When you configure the node server the station ID is marked as either "local" or "remote". Local means direct from the hub on your local network, remote means from the server in cloud. So if I change it to remote, will all the data be from the server or is it a mix of data from local vs the server? But I guess it will match whatever is in the app so it really doesnt matter as that is what I see now whenever I look? thanks
dbwarner5 Posted March 13, 2022 Author Posted March 13, 2022 Update.. I changed it to remote, and am still getting 0 and 0 for distanced and strikes, all other data is updating as expected. ill give it some more time to see if it changes.
bpwwer Posted March 13, 2022 Posted March 13, 2022 I think you're seeing the difference between historical data and current data. The node server is always showing current data and only current data with the exception of rain accumulation (month, year, etc). I believe both remote and local get the same data over the last 1 minute interval. So the node server is only reporting data obtained over that 1 minute interval. I don't have any insider knowledge about how their app works, but they very well could be showing the last lightning strike detected vs. any detected in the last 1 minute. The node server is designed to allow you to trigger off of and make decisions on the current data. Where something like the app is designed to show what's happened/happening. Different goals. When configured for 'remote' data, all data comes from the WeatherFlow servers.
Recommended Posts