-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lightning_hour clarification #45
Comments
What is the delta time/transmit interval between each row of data? EDIT: or if you can dump the table with the timestamps from the transmits, that works, too. |
Here are CSVs for yesterday (image above) and some data from today (today.csv) |
So far, from the patterns that I can pick out, it looks like this is roughly calculated as:
Logically, this doesn't make much sense to me. It seems like an arbitrary doubling of the number of strikes that have happened in the last hour. What does make sense to me, however is the following:
That deduces the number of strikes that happened in the last hour, which is what I think the sensor value is trying to communicate. For now, the latter equation is what I'll use to deduce the number of strikes for |
you may have found a bug! we'll look into it |
@themoosman would you mind providing your stations mac address so we can look into this further? @tlskinneriv to answer your original question, lightning_hour is calculated on the server and should use the general logic you suggested. we ran some internal tests and the lightning_hour calculations appear to be working correctly. are you seeing the same strange "doubling" phenomena as well? if so would you mind providing your mac address? |
@owise1 Unfortunately, I do not have a lightning sensor yet, so even if I was sending data, I wouldn't have any lightning data. |
I can, but I'd need a secure way to transmit the MAC. |
@themoosman you can send it to dev@ambientweather.net |
Sent. |
@owise1 Did you find anything in your investigation? |
Ambient weather devices do not seem to send this as a value to custom endpoints with the Ambient Weather API style communication. Is this field calculated server side? If so, what is the formula for calculation? Thanks!
The text was updated successfully, but these errors were encountered: