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

Add new wind parser: RFLINK R51 #75

Merged
merged 1 commit into from
Feb 8, 2024
Merged

Conversation

Minims
Copy link
Contributor

@Minims Minims commented Feb 5, 2024

Add wind as windspeed value. Seems new on RFLINK R51:

2024-02-05 13:37:21.286 DEBUG (MainThread) [rflink.protocol] received data: 20;70;TFA;ID=0ade0d;WIND=0011;
2024-02-05 13:37:21.287 DEBUG (MainThread) [rflink.protocol] got packet: 20;70;TFA;ID=0ade0d;WIND=0011;
2024-02-05 13:37:21.287 DEBUG (MainThread) [rflink.protocol] decoded packet: {'node': 'gateway', 'protocol': 'tfa', 'id': '0ade0d', 'wind': '0011'}

R51 links :
https://www.rflink.nl/changelog.php
https://www.rflink.nl/download.php

@javicalle
Copy link
Contributor

According with the RFLink "List of Data Fields: (LABEL=data)" this seems a RFLink bug:

The RFLink allowed labels (related to wind) should be:

WINSP=9999 => Wind speed in km. p/h (hexadecimal) needs division by 10
AWINSP=9999 => Average Wind speed in km. p/h (hexadecimal) needs division by 10
WINGS=9999 => Wind Gust in km. p/h (hexadecimal)
WINDIR=123 => Wind direction (integer value from 0-15) reflecting 0-360 degrees in 22.5 degree steps
WINCHL => wind chill (hexadecimal, see TEMP)
WINTMP=1234 => Wind meter temperature reading (hexadecimal, see TEMP)

IMHO that should be addressed in the RFLink side (now that it seems active again).

@aequitas
Copy link
Owner

aequitas commented Feb 8, 2024

The documentation does not always align with what you encounter in practice with RFLink is my experience. I removed Python 2.7 support in the master branch so the CI check should pass. After it passed I'll merge the PR.

@Minims
Copy link
Contributor Author

Minims commented Feb 8, 2024

I have also ask the RFLINK team to check if it'a bug or not.

@aequitas aequitas merged commit e65eea3 into aequitas:master Feb 8, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants