Grabbed the driver and installed – works like a champ!
Thanks, Matt! From: [email protected] [mailto:[email protected]] On Behalf Of Clay Jackson Sent: Friday, March 10, 2017 9:24 AM To: 'mwall' <[email protected]>; 'weewx-development' <[email protected]> Subject: RE: [weewx-development] Re: New Parser in SDR Hey, Matt – thanks! Will grab the driver in a little bit. The sensor ID does NOT change and it actually matches an “ID” tag on the physical sensor; so I think we’re good to go! Clay From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of mwall Sent: Thursday, March 9, 2017 5:43 PM To: weewx-development <[email protected] <mailto:[email protected]> > Subject: [weewx-development] Re: New Parser in SDR On Thursday, March 9, 2017 at 8:01:26 PM UTC-5, Clay Jackson wrote: I just picked up an Acurite 275M outdoor temp/humidity sensor that has an external probe – I want to set up at least one, and maybe 2 or 3 for Soil Temp recorders. RTL_433 will read them and produce this – all I need is a parser in sdr.py does the id change when you power cycle the sensor? the json output is a little odd - i would have expected "Acurite 00275RM" for the model, and that is the first crc i've seen for any acurite hardware. most acurite sensors have a fixed hardware id, but a few change each time they are power cycled. the latter are a pita, because either you can have only one of a sensor model, or you have to keep re-entering the identifier in the weewx config whenever the sensor batteries are replaced. 1. For all the other sensors, I see a TEXT parser and a JSON parser. Are both required, or, if I do just JSON, can I do just the JSON parser? the driver first tries text, then falls back to json, so only one or the other is required. json is preferred. hopefully all of the text parsers will go away at some point. 1. For testing, could I do something like --cmd=”cat <filename>” and then see whatever results I got from debug print statements? (I have a running WeeWx that I don’t want to stop until I get it “close” and don’t yet have a full (waiting on the SDR) dev hardware setup)? i had not considered testing without hardware. the weewx-sdr driver just grabs stdout and stderr from whatever you specify in cmd, so as long as your command spits out some json packets, you should be able to run weewx-sdr. install weewx-sdr in your existing weewx installation, then run weewx-sdr directly. that will not interfere with whatever weewx instances you already have running. if you run weewx-sdr via weewxd, be sure to use a separate config with database and HTML_ROOT different from those of your existing weewx instance(s). based on the json you posted, i added Acurite00275RMPacket in weewx-sdr at commit 923e696 m
