Skip to content
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

Negative Wind Gust #190

Closed
elji-lennart opened this issue Sep 27, 2024 · 20 comments · Fixed by #196
Closed

Negative Wind Gust #190

elji-lennart opened this issue Sep 27, 2024 · 20 comments · Fixed by #196
Labels
bug Something isn't working

Comments

@elji-lennart
Copy link

elji-lennart commented Sep 27, 2024

The problem

On some of the weatherstations there is a negative value of wind gust (-0.4 m/s). The wind speed an wind direction i ok.

Version of Weatherlink integration having the issue?

2024.4.0b0

Version of Home Assistant Core having the issue?

2024.9.3

Anything in the logs that might be useful for us?

I have 36 stations. 10 of them show -0.4 m/s. 9 of them is 6555 WLIP, 1 is 06558. But I have other 6555 WL IP working.

Diagnostic data file

No response

Additional information

No response

@elji-lennart elji-lennart added the bug Something isn't working label Sep 27, 2024
@astrandb
Copy link
Owner

Please get a diagnostic download from the device page when gust is displaying -0.4

@elji-lennart
Copy link
Author

elji-lennart commented Sep 27, 2024 via email

@astrandb
Copy link
Owner

Nothing was attached??

@elji-lennart
Copy link
Author

@elji-lennart
Copy link
Author

I sorry not closed

@elji-lennart elji-lennart reopened this Sep 28, 2024
@astrandb
Copy link
Owner

Weatherlink API reports:

"wind_gust_10_min": -1

The value is in mph and is displayed as -0.4 m/s
-1 is obviously an invalid value and should be reported to Davis/Weatherlink. I cannot say if the equipment is sending erroneous data or if the error occurs in the cloud servers.

@elji-lennart
Copy link
Author

elji-lennart commented Sep 28, 2024 via email

@astrandb
Copy link
Owner

Is this behaviour new or has it always been like this?
I can ask developers support how the -1 should be interpreted.

@elji-lennart
Copy link
Author

elji-lennart commented Sep 28, 2024 via email

@astrandb
Copy link
Owner

I have submitted the question. They usually answer same day or upcoming business day.

@astrandb
Copy link
Owner

astrandb commented Oct 3, 2024

What type of equipment is uploading the negative gust values?

@elji-lennart
Copy link
Author

elji-lennart commented Oct 3, 2024 via email

@astrandb
Copy link
Owner

astrandb commented Oct 4, 2024

My contact at developer support asks for a couple of station-id for stations that show negative values and a couble of correct stations. He got an id from the diagnostic file you posted but it was apparently not conclusive.

@elji-lennart
Copy link
Author

elji-lennart commented Oct 4, 2024 via email

@astrandb
Copy link
Owner

astrandb commented Oct 9, 2024

Got a reply from Davis. It is an inconsistency in the uploading devices. -1 represents no value available and should really be null instead.
I don’t think Davis will fix this bug. These negative values must therefore be handled in the integration.
Which is best? Zero or ”unavailable”? I vote for zero.

@elji-lennart
Copy link
Author

elji-lennart commented Oct 9, 2024 via email

@astrandb astrandb linked a pull request Oct 10, 2024 that will close this issue
@astrandb
Copy link
Owner

@elji-lennart A new beta version is released as v2024.10.0b0 . Can you please verify that the negative gust values are gone and that there are no obvious side-effects.

@elji-lennart
Copy link
Author

elji-lennart commented Oct 10, 2024 via email

@elji-lennart
Copy link
Author

elji-lennart commented Oct 10, 2024 via email

@astrandb
Copy link
Owner

After considering your thoughts and the answer from Davis I think it better to translate the negative value to None internally. It will then be displayed as "Unknown". Same as for all other observations where the API reports "null" or "None". I will prepare a new beta.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants