On Thursday, September 8, 2016 at 5:56:42 PM UTC-4, Marco Tibaldi wrote:
>
> Sep  8 23:38:35 SDR weewx[1034]: sdr: MainThread: lines=[]
> Sep  8 23:38:41 SDR weewx[1034]: sdr: MainThread: lines=['2016-09-08 
> 23:38:41 :\tLaCrosse WS \t:\t9 \t:\t34\n', '\tTemperature:\t 25.3 C\n']
> Sep  8 23:38:41 SDR weewx[1034]: sdr: MainThread: ts=1473377921 
> payload=LaCrosse WS #011:#0119 #011:#01134
> Sep  8 23:38:41 SDR weewx[1034]: sdr: MainThread: 
> pkt={'temperature.9:34.LaCrossePacket': 25.3, 'usUnits': 17, 'dateTime': 
> 1473377921}
> Sep  8 23:38:41 SDR weewx[1034]: sdr: MainThread: 
> packet={'temperature.9:34.LaCrossePacket': 25.3, 'usUnits': 17, 'dateTime': 
> 1473377921}
>

your sensor cluster is emitting :9 and :34

what kind of hardware are you running on?  the driver is getting some of 
the rtl_433 output, but some of the output is getting split up.  rtl_433 
spits out lines of data without a standard format.  so the driver has to 
guess to figure out where output from one sensor ends and output from 
another begins.  this is complicated by the fact that it is done 
asynchronously - there is one thread that runs the rtl_433 binary and 
captures its output, while the weewx main thread waits on a queue for the 
output lines.

this is how to debug things.  at the lowest level you run rtl_433 directly:

sudo rtl_433

that will spit out data from sensors as the sdr hardware receives them.

next up is to run the driver directly:

PYTHONPATH=/home/weewx/bin python /home/weewx/bin/user/sdr.py

that will spit out the data with all recognized data tagged with 
identifiers ready for mapping to database fields.  it also flags any sensor 
output that is not recognized by the driver.

finally, you can run weewxd directly:

sudo weewxd weewx.conf

that will spit out the data mapped to the database fields in weewx.

m

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to