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

Parser for WH1080/WH3080 not working #17

Closed
waded opened this issue Jun 8, 2017 · 2 comments
Closed

Parser for WH1080/WH3080 not working #17

waded opened this issue Jun 8, 2017 · 2 comments

Comments

@waded
Copy link

waded commented Jun 8, 2017

Running

PYTHONPATH=bin python bin/user/sdr.py --cmd "rtl_433 -q -U -F json -R 32"

with an Ambient Weather WS2080 in the area I'm seeing JSON output as follows:

out: ['{"time" : "2017-06-08 06:27:13", 
"model" : "Fine Offset Electronics WH1080/WH3080 Weather Station", 
"msg_type" : 0, "id" : 38, "temperature_C" : 20.400, "humidity" : 66, 
"direction_str" : "N", "direction_deg" : "0", "speed" : 0.000, "gust" : 1.224, 
"rain" : 407.400, "battery" : "OK"}\n']

(and occasionally a second msg_type:1 that seems to be WWVB)

I expected to get output like is discussed in Configuration in the readme; I took the above output to indicate something is wrong with the parser.

If I understand correctly it's intended weewx-sdr supports this device (class FOWHx080Packet) but it looks like the IDENTIFIER value is not an exact match (extra spaces), if not other parts of the mapping like id.

I'd be happy to fix support if you agree that's a starting point. This is the first day I've laid eyes on weewx, rtl-sdr, sdr_433, and weewx-sdr and don't want to take device support down the wrong path. I'd like to get this device working though!

@waded
Copy link
Author

waded commented Jun 16, 2017

It appears @eyesnz perhaps diagnosed a similar issue?

@matthewwall
Copy link
Owner

this is addressed in commit 7fe0e56

not a great solution, but hopefully robust enough until rtl_433 gets some proper versioning and/or better consistency in the packet identification and structure

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

No branches or pull requests

2 participants