[weewx-user] Re: SDR and Acurite 5-in-1 not reporting wind speed

[mwall]

>
>
>
fixed at commit 1df6925


-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Acurite RTL_433 SDR packet changed

[mwall]

fixed at commit 1df6925

its kinda hard to maintain compatibility with all of the rtl433 changes - 
hopefully they will stabilize on naming conventions and do versioned 
releases at some point

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: SDR and Acurite 5-in-1 not reporting wind speed

[Greg Gowins]

Nice catch!  That indeed was it.  I added in that line with wind_speed_mph 
to sdr.py, then also changed the mapping to use wind_speed_mph in 
weewx.conf, and it is now reporting the speed.

Greg

On Sunday, December 31, 2017 at 10:32:09 PM UTC-6, Craig Thom wrote:
>
> I know enough just to screw things up, so I'm probably wrong, and I have 
> not updated sdr_433, but
>
> I just looked through sdr.py, and, for the 5n1 sensor, the parse_text 
> method has both "wind_speed" and "wind_speed_mph", but the parse_json 
> method, which is decoding msg_type 49, does not.
>
> I am not a programmer, but I bet adding it to this section of sdr.py would 
> do the trick.  It couldn't hurt much, anyway.
>
> if msg_type == 49: # 0x31
> pkt['wind_speed'] = Packet.get_float(obj, 'wind_speed') # mph?
> pkt['wind_dir'] = Packet.get_float(obj, 'wind_dir_deg')
> pkt['rain_counter'] = Packet.get_int(obj, 'raincounter_raw')
>   
> pkt['wind_speed_mph'] = Packet.get_float(obj, 'wind_speed_mph')
>
> On Sunday, December 31, 2017 at 10:28:32 PM UTC-5, Greg Gowins wrote:
>>
>> Hello everyone,
>>
>> I recently made the update to 3.8.0 and everything seems to be working 
>> except wind speed.  It looks like maybe there was a name change in the 
>> rtl_sdr (the -R number did also change from 39 to 40) but I've changed it 
>> in the weewx.conf mapping, but it doesn't seem to make a difference.
>>
>> Here's the changed weewx.conf mapping area:
>>
>> [SDR]
>> # This section is for the software-defined radio driver.
>>
>> # The driver to use
>> driver = user.sdr
>>
>> log_unknown_sensors = True
>> log_unmapped_sensors = True
>>
>> cmd = /usr/local/bin/rtl_433 -q -U -f433923000 -Fjson -R40
>>
>> [[sensor_map]]
>> windDir = wind_dir.0832.Acurite5n1Packet
>> windSpeed = wind_speed_mph.0832.Acurite5n1Packet
>> outTemp = temperature.0832.Acurite5n1Packet
>> outHumidity = humidity.0832.Acurite5n1Packet
>> rain_total = rain_total.0832.Acurite5n1Packet
>> strikes_total = strikes_total.56AF.AcuriteLightningPacket
>> distance = distance.56AF.AcuriteLightningPacket
>> #   extraTemp1 = temperature.566F.AcuriteLightningPacket
>> #   extraHumid1 = humidity.566F.AcuriteLightningPacket
>> [[deltas]]
>> strikes = strikes_total
>> rain = rain_total
>>
>> And here is what is in the log:
>>
>> Jan  1 03:21:35 raspberrypi weewx[18624]: sdr: MainThread: 
>> lines=['{"time" : "2018-01-01 03:21:34", "model" : "Acurite 5n1 sensor", 
>> "sensor_id" : 2098, "channel" : "A", "sequence_num" : 0, "battery" : "OK", 
>> "message_type" : 49, "wind_speed_mph" : 5.765, "wind_dir_deg" : 337.500, 
>> "wind_dir" : "NNW", "rainfall_accumulation_inch" : 0.000, "raincounter_raw" 
>> : 16}\n', '{"time" : "2018-01-01 03:21:34", "model" : "Acurite 5n1 sensor", 
>> "sensor_id" : 2098, "channel" : "A", "sequence_num" : 1, "battery" : "OK", 
>> "message_type" : 49, "wind_speed_mph" : 5.765, "wind_dir_deg" : 337.500, 
>> "wind_dir" : "NNW", "rainfall_accumulation_inch" : 0.000, "raincounter_raw" 
>> : 16}\n', '{"time" : "2018-01-01 03:21:34", "model" : "Acurite 5n1 sensor", 
>> "sensor_id" : 2098, "channel" : "A", "sequence_num" : 2, "battery" : "OK", 
>> "message_type" : 49, "wind_speed_mph" : 5.765, "wind_dir_deg" : 337.500, 
>> "wind_dir" : "NNW", "rainfall_accumulation_inch" : 0.000, "raincounter_raw" 
>> : 16}\n']
>> Jan  1 03:21:35 raspberrypi weewx[18624]: sdr: MainThread: 
>> packet={'windDir': 337.5, 'rain_total': 0.16, 'usUnits': 1, 'dateTime': 
>> 1514776894}
>> Jan  1 03:21:35 raspberrypi weewx[18624]: sdr: MainThread: 
>> packet={'windDir': 337.5, 'rain_total': 0.16, 'usUnits': 1, 'dateTime': 
>> 1514776894}
>> Jan  1 03:21:35 raspberrypi weewx[18624]: sdr: MainThread: 
>> packet={'windDir': 337.5, 'rain_total': 0.16, 'usUnits': 1, 'dateTime': 
>> 1514776894}
>>
>> If I change the weewx.conf mappings to use just the 
>> wind_speed.0832.Acurite5n1Packet, then this is what I see in the logs:
>>
>> Jan  1 03:25:56 raspberrypi weewx[19036]: sdr: MainThread: 
>> lines=['2018-01-01 03:25:51 Acurite lightning 0x56AF Ch A Msg Type 0x02: 
>> 24.8 F 91 % RH Strikes 31 Distance 22 L_status 0x00 - c0  56  af  db  4d  
>> d4  9f  96  f6 \n', '{"time" : "2018-01-01 03:25:53", "model" : "Acurite 
>> 5n1 sensor", "sensor_id" : 2098, "channel" : "A", "sequence_num" : 0, 
>> "battery" : "OK", "message_type" : 49, "wind_speed_mph" : 7.823, 
>> "wind_dir_deg" : 337.500, "wind_dir" : "NNW", "rainfall_accumulation_inch" 
>> : 0.000, "raincounter_raw" : 16}\n', '{"time" : "2018-01-01 03:25:53", 
>> "model" : "Acurite 5n1 sensor", "sensor_id" : 2098, "channel" : "A", 
>> "sequence_num" : 1, "battery" : "OK", "message_type" : 49, "wind_speed_mph" 
>> : 7.823, "wind_dir_deg" : 337.500, "wind_dir" : "NNW", 
>> "rainfall_accumulation_inch" : 0.000, "raincounter_raw" : 16}\n', '{"time" 
>> : "2018-01-01 03:25:53", "model" : "Acurite 5n1 se

[weewx-user] Re: SDR and Acurite 5-in-1 not reporting wind speed

[Craig Thom]

I know enough just to screw things up, so I'm probably wrong, and I have 
not updated sdr_433, but

I just looked through sdr.py, and, for the 5n1 sensor, the parse_text 
method has both "wind_speed" and "wind_speed_mph", but the parse_json 
method, which is decoding msg_type 49, does not.

I am not a programmer, but I bet adding it to this section of sdr.py would 
do the trick.  It couldn't hurt much, anyway.

if msg_type == 49: # 0x31
pkt['wind_speed'] = Packet.get_float(obj, 'wind_speed') # mph?
pkt['wind_dir'] = Packet.get_float(obj, 'wind_dir_deg')
pkt['rain_counter'] = Packet.get_int(obj, 'raincounter_raw')
  
pkt['wind_speed_mph'] = Packet.get_float(obj, 'wind_speed_mph')

On Sunday, December 31, 2017 at 10:28:32 PM UTC-5, Greg Gowins wrote:
>
> Hello everyone,
>
> I recently made the update to 3.8.0 and everything seems to be working 
> except wind speed.  It looks like maybe there was a name change in the 
> rtl_sdr (the -R number did also change from 39 to 40) but I've changed it 
> in the weewx.conf mapping, but it doesn't seem to make a difference.
>
> Here's the changed weewx.conf mapping area:
>
> [SDR]
> # This section is for the software-defined radio driver.
>
> # The driver to use
> driver = user.sdr
>
> log_unknown_sensors = True
> log_unmapped_sensors = True
>
> cmd = /usr/local/bin/rtl_433 -q -U -f433923000 -Fjson -R40
>
> [[sensor_map]]
> windDir = wind_dir.0832.Acurite5n1Packet
> windSpeed = wind_speed_mph.0832.Acurite5n1Packet
> outTemp = temperature.0832.Acurite5n1Packet
> outHumidity = humidity.0832.Acurite5n1Packet
> rain_total = rain_total.0832.Acurite5n1Packet
> strikes_total = strikes_total.56AF.AcuriteLightningPacket
> distance = distance.56AF.AcuriteLightningPacket
> #   extraTemp1 = temperature.566F.AcuriteLightningPacket
> #   extraHumid1 = humidity.566F.AcuriteLightningPacket
> [[deltas]]
> strikes = strikes_total
> rain = rain_total
>
> And here is what is in the log:
>
> Jan  1 03:21:35 raspberrypi weewx[18624]: sdr: MainThread: lines=['{"time" 
> : "2018-01-01 03:21:34", "model" : "Acurite 5n1 sensor", "sensor_id" : 
> 2098, "channel" : "A", "sequence_num" : 0, "battery" : "OK", "message_type" 
> : 49, "wind_speed_mph" : 5.765, "wind_dir_deg" : 337.500, "wind_dir" : 
> "NNW", "rainfall_accumulation_inch" : 0.000, "raincounter_raw" : 16}\n', 
> '{"time" : "2018-01-01 03:21:34", "model" : "Acurite 5n1 sensor", 
> "sensor_id" : 2098, "channel" : "A", "sequence_num" : 1, "battery" : "OK", 
> "message_type" : 49, "wind_speed_mph" : 5.765, "wind_dir_deg" : 337.500, 
> "wind_dir" : "NNW", "rainfall_accumulation_inch" : 0.000, "raincounter_raw" 
> : 16}\n', '{"time" : "2018-01-01 03:21:34", "model" : "Acurite 5n1 sensor", 
> "sensor_id" : 2098, "channel" : "A", "sequence_num" : 2, "battery" : "OK", 
> "message_type" : 49, "wind_speed_mph" : 5.765, "wind_dir_deg" : 337.500, 
> "wind_dir" : "NNW", "rainfall_accumulation_inch" : 0.000, "raincounter_raw" 
> : 16}\n']
> Jan  1 03:21:35 raspberrypi weewx[18624]: sdr: MainThread: 
> packet={'windDir': 337.5, 'rain_total': 0.16, 'usUnits': 1, 'dateTime': 
> 1514776894}
> Jan  1 03:21:35 raspberrypi weewx[18624]: sdr: MainThread: 
> packet={'windDir': 337.5, 'rain_total': 0.16, 'usUnits': 1, 'dateTime': 
> 1514776894}
> Jan  1 03:21:35 raspberrypi weewx[18624]: sdr: MainThread: 
> packet={'windDir': 337.5, 'rain_total': 0.16, 'usUnits': 1, 'dateTime': 
> 1514776894}
>
> If I change the weewx.conf mappings to use just the 
> wind_speed.0832.Acurite5n1Packet, then this is what I see in the logs:
>
> Jan  1 03:25:56 raspberrypi weewx[19036]: sdr: MainThread: 
> lines=['2018-01-01 03:25:51 Acurite lightning 0x56AF Ch A Msg Type 0x02: 
> 24.8 F 91 % RH Strikes 31 Distance 22 L_status 0x00 - c0  56  af  db  4d  
> d4  9f  96  f6 \n', '{"time" : "2018-01-01 03:25:53", "model" : "Acurite 
> 5n1 sensor", "sensor_id" : 2098, "channel" : "A", "sequence_num" : 0, 
> "battery" : "OK", "message_type" : 49, "wind_speed_mph" : 7.823, 
> "wind_dir_deg" : 337.500, "wind_dir" : "NNW", "rainfall_accumulation_inch" 
> : 0.000, "raincounter_raw" : 16}\n', '{"time" : "2018-01-01 03:25:53", 
> "model" : "Acurite 5n1 sensor", "sensor_id" : 2098, "channel" : "A", 
> "sequence_num" : 1, "battery" : "OK", "message_type" : 49, "wind_speed_mph" 
> : 7.823, "wind_dir_deg" : 337.500, "wind_dir" : "NNW", 
> "rainfall_accumulation_inch" : 0.000, "raincounter_raw" : 16}\n', '{"time" 
> : "2018-01-01 03:25:53", "model" : "Acurite 5n1 sensor", "sensor_id" : 
> 2098, "channel" : "A", "sequence_num" : 2, "battery" : "OK", "message_type" 
> : 49, "wind_speed_mph" : 7.823, "wind_dir_deg" : 337.500, "wind_dir" : 
> "NNW", "rainfall_accumulation_inch" : 0.000, "raincounter_raw" : 16}\n']
> Jan  1 03:25:56 raspberrypi weewx[19036]: sdr: MainThread: 
> packet={'distance': 22.0, 'dateTime': 1514777151, 'usUnits': 1,

[weewx-user] SDR and Acurite 5-in-1 not reporting wind speed

[Greg Gowins]

Hello everyone,

I recently made the update to 3.8.0 and everything seems to be working 
except wind speed.  It looks like maybe there was a name change in the 
rtl_sdr (the -R number did also change from 39 to 40) but I've changed it 
in the weewx.conf mapping, but it doesn't seem to make a difference.

Here's the changed weewx.conf mapping area:

[SDR]
# This section is for the software-defined radio driver.

# The driver to use
driver = user.sdr

log_unknown_sensors = True
log_unmapped_sensors = True

cmd = /usr/local/bin/rtl_433 -q -U -f433923000 -Fjson -R40

[[sensor_map]]
windDir = wind_dir.0832.Acurite5n1Packet
windSpeed = wind_speed_mph.0832.Acurite5n1Packet
outTemp = temperature.0832.Acurite5n1Packet
outHumidity = humidity.0832.Acurite5n1Packet
rain_total = rain_total.0832.Acurite5n1Packet
strikes_total = strikes_total.56AF.AcuriteLightningPacket
distance = distance.56AF.AcuriteLightningPacket
#   extraTemp1 = temperature.566F.AcuriteLightningPacket
#   extraHumid1 = humidity.566F.AcuriteLightningPacket
[[deltas]]
strikes = strikes_total
rain = rain_total

And here is what is in the log:

Jan  1 03:21:35 raspberrypi weewx[18624]: sdr: MainThread: lines=['{"time" 
: "2018-01-01 03:21:34", "model" : "Acurite 5n1 sensor", "sensor_id" : 
2098, "channel" : "A", "sequence_num" : 0, "battery" : "OK", "message_type" 
: 49, "wind_speed_mph" : 5.765, "wind_dir_deg" : 337.500, "wind_dir" : 
"NNW", "rainfall_accumulation_inch" : 0.000, "raincounter_raw" : 16}\n', 
'{"time" : "2018-01-01 03:21:34", "model" : "Acurite 5n1 sensor", 
"sensor_id" : 2098, "channel" : "A", "sequence_num" : 1, "battery" : "OK", 
"message_type" : 49, "wind_speed_mph" : 5.765, "wind_dir_deg" : 337.500, 
"wind_dir" : "NNW", "rainfall_accumulation_inch" : 0.000, "raincounter_raw" 
: 16}\n', '{"time" : "2018-01-01 03:21:34", "model" : "Acurite 5n1 sensor", 
"sensor_id" : 2098, "channel" : "A", "sequence_num" : 2, "battery" : "OK", 
"message_type" : 49, "wind_speed_mph" : 5.765, "wind_dir_deg" : 337.500, 
"wind_dir" : "NNW", "rainfall_accumulation_inch" : 0.000, "raincounter_raw" 
: 16}\n']
Jan  1 03:21:35 raspberrypi weewx[18624]: sdr: MainThread: 
packet={'windDir': 337.5, 'rain_total': 0.16, 'usUnits': 1, 'dateTime': 
1514776894}
Jan  1 03:21:35 raspberrypi weewx[18624]: sdr: MainThread: 
packet={'windDir': 337.5, 'rain_total': 0.16, 'usUnits': 1, 'dateTime': 
1514776894}
Jan  1 03:21:35 raspberrypi weewx[18624]: sdr: MainThread: 
packet={'windDir': 337.5, 'rain_total': 0.16, 'usUnits': 1, 'dateTime': 
1514776894}

If I change the weewx.conf mappings to use just the 
wind_speed.0832.Acurite5n1Packet, then this is what I see in the logs:

Jan  1 03:25:56 raspberrypi weewx[19036]: sdr: MainThread: 
lines=['2018-01-01 03:25:51 Acurite lightning 0x56AF Ch A Msg Type 0x02: 
24.8 F 91 % RH Strikes 31 Distance 22 L_status 0x00 - c0  56  af  db  4d  
d4  9f  96  f6 \n', '{"time" : "2018-01-01 03:25:53", "model" : "Acurite 
5n1 sensor", "sensor_id" : 2098, "channel" : "A", "sequence_num" : 0, 
"battery" : "OK", "message_type" : 49, "wind_speed_mph" : 7.823, 
"wind_dir_deg" : 337.500, "wind_dir" : "NNW", "rainfall_accumulation_inch" 
: 0.000, "raincounter_raw" : 16}\n', '{"time" : "2018-01-01 03:25:53", 
"model" : "Acurite 5n1 sensor", "sensor_id" : 2098, "channel" : "A", 
"sequence_num" : 1, "battery" : "OK", "message_type" : 49, "wind_speed_mph" 
: 7.823, "wind_dir_deg" : 337.500, "wind_dir" : "NNW", 
"rainfall_accumulation_inch" : 0.000, "raincounter_raw" : 16}\n', '{"time" 
: "2018-01-01 03:25:53", "model" : "Acurite 5n1 sensor", "sensor_id" : 
2098, "channel" : "A", "sequence_num" : 2, "battery" : "OK", "message_type" 
: 49, "wind_speed_mph" : 7.823, "wind_dir_deg" : 337.500, "wind_dir" : 
"NNW", "rainfall_accumulation_inch" : 0.000, "raincounter_raw" : 16}\n']
Jan  1 03:25:56 raspberrypi weewx[19036]: sdr: MainThread: 
packet={'distance': 22.0, 'dateTime': 1514777151, 'usUnits': 1, 
'strikes_total': 31.0}
Jan  1 03:25:56 raspberrypi weewx[19036]: sdr: MainThread: 
packet={'windDir': 337.5, 'windSpeed': None, 'rain_total': 0.16, 'usUnits': 
1, 'dateTime': 1514777153}
Jan  1 03:25:56 raspberrypi weewx[19036]: sdr: MainThread: 
packet={'windDir': 337.5, 'windSpeed': None, 'rain_total': 0.16, 'usUnits': 
1, 'dateTime': 1514777153}
Jan  1 03:25:56 raspberrypi weewx[19036]: sdr: MainThread: 
packet={'windDir': 337.5, 'windSpeed': None, 'rain_total': 0.16, 'usUnits': 
1, 'dateTime': 1514777153}


This time it puts the windSpeed in the packet, but has the speed as 'None', 
but I see the speed listed in the raw data as 7.823.Any ideas?

Greg Gowins
Driftwood, TX

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/o

[weewx-user] Re: Help weewx.conf for station registry

[gjr80]

Hi,

If I understand your first post correctly you have a functioning weeWX 
install and you would like to add your station to the station registry and 
post your data to WU. If so you are correct in that you need to make 
changes to weewx.conf but the wee_config utility will not do this for you. 
wee_config  allows 
you to (among other things) change driver, location (aka station name), 
lat/long, altitude and units. If you want to change station registry and WU 
settings in weewx.conf then you really need to manually edit weewx.conf. 
Given you experience with you RPi you really should get some basic linux 
skills under your belt, at the very least you need to be able to navigate 
around the directory tree of your system, understand and be able to manage 
file/directory permissions and of course edit text files. There are many 
other skills that will help but these basics will get you started with what 
you want to do. How you do these tasks will really depend on your system, 
for example, do you work from the command line or a GUI? Google is your 
friend.

Once you have these skills have a look at the User's Guide 
, in particular the following 
sections that cover various parts of the config file weewx.conf [Station] 
, [[Stationregistry]] 
 and [[Wunderground]] 
.

By all means come back for more help if you need it but make sure your get 
those basic linux skills first.

Gary

PS. One other word of advice, baby steps to start with. Get one thing 
working before moving onto the next, don't try the big bang approach of 
doing everything at once unless you really know what you are doing. You 
will get frustrated and it will make it harder for those that try to help 
you.

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Help weewx.conf for station registry

[torresb1160]

Thanks Craig, any advise on how to get the conf commands to work?
Brandon

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Help weewx.conf for station registry

[Craig Thom]

That station registry is just a collection of people running weewx.  That 
is independent of Weather Underground or any other site.

The section you want for Weather Underground is this one.  The station ID 
and station key (which you enter here as password) you from Weather 
Underground after you register your PWS.

[[Wunderground]]
# This section is for configuring posts to the Weather Underground.

# If you wish to do this, set the option 'enable' to true,
# and specify a station (e.g., 'KORHOODR3') and password.
enable = true
station = KKYLOUIS186
# To guard against parsing errors, put your password in quotes:
password = "xxx"

# Set the following to True to have weewx use the WU "Rapidfire"
# protocol. Not all hardware can support it. See the User's Guide.
rapidfire = False


On Sunday, December 31, 2017 at 3:25:18 PM UTC-5, torre...@gmail.com wrote:
>
> Sorry l’m a total newbee. Got weewx going no problems from the DEB 
> package. Would like to register the station and post the data to Weather 
> Underground. I don’t understand how to get  weewx.conf to work. I have 
> changed directory to: 
> $ cd /etc/weewx 
> But now what? sudo wee_congif —reconfigure does not bring anything in the 
> following section of the user guide: [StdRESTful] 
>
> This is my first Raspberry Pi project, and don’t understand permissions 
> and the directories yet. Any basic references would be appreciated. I 
> bought “Exploring Raspberry Pi” by Derek Molly. This book isn’t really 
> helping too much, I think I need it dumbed down to start. 
> Thanks, Brandon 
>
> User Guide Section: 
> [StdRESTful] 
> This section is for configuring the StdRESTful services, which upload to 
> simple RESTful servers such as the Weather Underground, PWSweather.com, or 
> CWOP. 
>
> [[StationRegistry]] 
> A registry of weeWX weather stations is maintained at weewx.com. Stations 
> are displayed on a map and a list at http://weewx.com/stations.html 
>
> How does the registry work? Individual weather stations periodically 
> contact the registry. Each station provides a URL to identify itself, plus 
> other information such as the station type and weeWX version. No personal 
> information, nor any meteorological data, is sent. 
>
> To add your station to this list, you must do two things: 
>
> Enable the StationRegistry in weewx.conf by setting the option 
> register_this_station to True. Your station will contact the registry once 
> per week. If your station does not contact the registry for about a month, 
> it will be removed from the list. 
> Provide a station_url, either in section [Station], or in the 
> [[StationRegistry]] section. 
> The station_url is used to uniquely identify each station, so choose it 
> carefully before you set register_this_station to True. 
>
> [StdRestful] 
> [[StationRegistry]] 
> register_this_station = True 
> register_this_station 
> Set this to True to register the weather station.

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Error 110 timeout on Raspbian 9

[gjr80]

Hi,

The wmr300 driver is still being developed,  I believe the latest version is 
detailed in this thread 
(https://groups.google.com/forum/m/#!topic/weewx-user/teVxjoRMOb8). You might 
want to use that version if not already. Also, if you place an updated wmr300 
driver in usr/share/weewx/user you will need to make a change to weewx.conf, 
under [WMR300] you will need to change the driver config option to point to the 
new driver:

[WMR300]

driver = user.wmr300

You will need to restart weeWX for the change to take effect.

Gary

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Error 110 timeout on Raspbian 9

[Cycle London]

Hi.   
I have a Pi3 and an Oregon Scientific WM300 and when I try to start up the 
weewx process, I get the following errors:

Dec 31 22:38:41 weather weewx[2163]: engine: Using configuration file 
/etc/weewx/weewx.conf
Dec 31 22:38:41 weather weewx[2163]: engine: Loading station type WMR300 
(weewx.drivers.wmr300)
Dec 31 22:38:41 weather weewx[2163]: wmr300: driver version is 0.18
Dec 31 22:38:41 weather weewx[2163]: wmr300: usb info: pyusb_version=1.0.0
Dec 31 22:38:41 weather weewx[2163]: wmr300: sensor map is {'outHumidity': 
'humidity_1', 'extraDewpoint6': 'dewpoint_7', 'windchill': 'windchill', 
'extraDewpoint4': 'dewpoint_5', 'rainRate': 'rain_rate', 'heatindex': 
'heatindex_1', 'inTemp': 'temperature_0', 'windGustDir': 'wind_gust_dir', 
'extraDewpoint2': 'dewpoint_3', 'extraDewpoint3': 'dewpoint_4', 
'extraDewpoint1': 'dewpoint_2', 'barometer': 'barometer', 'extraDewpoint7': 
'dewpoint_8', 'dewpoint': 'dewpoint_1', 'extraDewpoint5': 'dewpoint_6', 
'extraHumid6': 'humidity_7', 'pressure': 'pressure', 'extraHumid4': 
'humidity_5', 'extraHumid5': 'humidity_6', 'extraHumid2': 'humidity_3', 
'extraHumid3': 'humidity_4', 'extraHumid1': 'humidity_2', 'extraTemp6': 
'temperature_7', 'extraTemp7': 'temperature_8', 'extraTemp4': 
'temperature_5', 'extraTemp5': 'temperature_6', 'extraTemp2': 
'temperature_3', 'extraTemp3': 'temperature_4', 'extraTemp1': 
'temperature_2', 'extraHeatindex3': 'heatindex_4', 'extraHeatindex2': 
'heatindex_3', 'extraHeatindex1': 'heatindex_2', 'extraHeatindex7': 
'heatindex_8', 'extraHeatindex6': 'heatindex_7', 'extraHeatindex5': 
'heatindex_6', 'extraHumid7': 'humidity_8', 'extraHeatindex4': 
'heatindex_5', 'windDir': 'wind_dir', 'outTemp': 'temperature_1', 
'windSpeed': 'wind_avg', 'inHumidity': 'humidity_0', 'windGust': 
'wind_gust'}
Dec 31 22:38:42 weather kernel: [ 1875.571823] usb 1-1.5: reset full-speed 
USB device number 4 using dwc_otg
Dec 31 22:38:42 weather weewx[2163]: engine: StdConvert target unit is 0x1
Dec 31 22:38:42 weather weewx[2163]: wxcalculate: The following values will 
be calculated: barometer=prefer_hardware, windchill=hardware, 
dewpoint=hardware, appTemp=prefer_hardware, rainRate=hardware, 
windrun=prefer_hardware, heatindex=hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Dec 31 22:38:42 weather weewx[2163]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Dec 31 22:38:42 weather weewx[2163]: engine: Archive will use data binding 
wx_binding
Dec 31 22:38:42 weather weewx[2163]: engine: Record generation will be 
attempted in 'hardware'
Dec 31 22:38:42 weather weewx[2163]: engine: Using archive interval of 300 
seconds (specified in weewx configuration)
Dec 31 22:38:42 weather weewx[2163]: engine: Using binding 'wx_binding' to 
database 'weewx.sdb'
Dec 31 22:38:42 weather weewx[2163]: manager: Starting backfill of daily 
summaries
Dec 31 22:38:42 weather weewx[2163]: restx: StationRegistry: Registration 
not requested.
Dec 31 22:38:42 weather weewx[2163]: restx: Wunderground: Posting not 
enabled.
Dec 31 22:38:42 weather weewx[2163]: restx: PWSweather: Posting not enabled.
Dec 31 22:38:42 weather weewx[2163]: restx: CWOP: Posting not enabled.
Dec 31 22:38:42 weather weewx[2163]: restx: WOW: Posting not enabled.
Dec 31 22:38:42 weather weewx[2163]: restx: AWEKAS: Posting not enabled.
Dec 31 22:38:42 weather weewx[2163]: engine: Starting up weewx version 3.8.0
Dec 31 22:38:42 weather weewx[2163]: wmr300: reading records since *** 
N/A *** (N/A   )
Dec 31 22:38:42 weather weewx[2163]: wmr300: usb failure: [Errno 110] 
Operation timed out
Dec 31 22:38:42 weather weewx[2163]: engine: Caught WeeWxIOError: [Errno 
110] Operation timed out
Dec 31 22:38:42 weather weewx[2163]:   Waiting 60 seconds then 
retrying...


I've spent a while googling and came across a thread advising us to 
download wmr300x.py and place it into /usr/share/weewx/user.  This I did. 
 No change.  Should that file be placed somewhere else?   Should it be 
renamed to remove the 'x'?   

My config file is below. 

*
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2015 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 0 

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 3.8.0

##

#   This section is for information about the station.

[Station]

# Description of 

Re: [weewx-user] Whats the best way to extract windrun data for display ??

[Thomas Keffer]

When you use a tag that specifies an aggregation period, like $day, then
you have to specify an aggregation type, like max. See the Customizing
Guide, section *Aggregation periods
*. So,
if you say $day.windrun, you're using an incomplete tag, one which has no
conversion operator to a string. Only the complete tags, such as
$day.windrun.max, has this.

Incidentally, this shows the hazards of defining windrun as the total
windrun since midnight. This makes it a monotonically increasing series,
starting each day at midnight.  A tag like $day.windrun.max is not as
useful as it could be, as it will always just be the last value in this
series. I wish it was treated more like rain, where the windrun is just the
run over the archive period. You'd have to do the sum to get the total run
since midnight ($day.windrun.sum), but then a tag like $day.windrun.max
would be more meaningful and useful.

But, that was an algorithmic mistake made a while ago. I think it would be
tough to redefine it now. Matthew, I'd be interested in your opinion.

-tk

On Sun, Dec 31, 2017 at 1:34 PM, Michael Hornsby <
michael.d.horn...@gmail.com> wrote:

>
>
> Hi
>
> Can I get some advice on how to extract the windrun data for display ?
>
> This gives me spaces
> $day.windrun
> $week.windrun
> $month.windrun
> $year.windrun
>
>
> This gives me the same number for day and week (below)
> $day.windrun.max
> $week.windrun.max
> $month.windrun.max
> $year.windrun.max
>
> Day: 54.1 km
> Week: 54.1 km
> Month: 684.8 km
> Year: 829.6 km
>
> Cheers
> Michael
>
> --
> 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 weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Incorrect wind data

[Thomas Keffer]

Since WeeWX v2.4, LOOP packets have included windGust and windGustDir. They
are set by the driver to the max values seen since the last archive record.

If you set loop_hilo to False, then they will not be used to calculate max
and min values.

What gets recorded in the database depends on what kind of record
generation you are using. If record_generation=hardware (the default), then
what gets recorded will be whatever your Vantage supplies from the archive
records in the logger. If record_generation=software, then no value of
windGust will be recorded. From your symptoms, I suspect you are using
software record generation.

If there is nothing in the database, then WeeWX does a "catch up," which
always uses the archive records from the logger.

So, the behavior you are getting is consistent with loop_hilo=False and
record_generation=software. If I'm wrong in my analysis and you're using
hardware generation, let me know.

Which begs the question: why not stick with the defaults? These two options
are for hardware that are not as capable as the Vantage. Leave them at the
defaults, and I'm betting your problems will go away.

-tk


-tk


On Sun, Dec 31, 2017 at 9:27 AM, stefano siega 
wrote:

>
> I think I have found a problem concerning wind gusts.
> I have a Davis Vantage Pro2 and Weewx 3.7.1.
> I select loop_hilo=False and the windgust are not recorder in database!
> But, if I restart WEEWX with a new database, the old entries that are
> added to the database, contain the correct wingust data.
> I think weewx ignores the wingust data read from the station at each
> archive interval.
> If weewx reads old data from the station's memory, then these contain the
> correct windgust data.
>
> Il giorno lunedì 6 ottobre 2014 16:35:46 UTC+2, Tom Keffer ha scritto:
>>
>> If you have loop_hilo=False, then LOOP records are not used to record the
>> wind high and low. This means that on weather stations that do not emit
>> windGust in their archive records (nearly every station except Vantage),
>> there will be no windGust field.
>>
>> We could change this behavior so that the windGust is set to the average
>> wind speed (that is, set it to windSpeed), but I'm reluctant to do this.
>> That's not really what windGust is intended to capture. It would solve your
>> display problems, but introduce semantic problems.
>>
>> Changing the archive interval will not make any difference in all of this.
>>
>> Fundamentally, you need to figure out why the rain rate is incorrect. I
>> know you have a separate thread going on that.,
>>
>> -tk
>>
>> On Sat, Oct 4, 2014 at 8:02 AM, Steve2Q  wrote:
>>
>>> Is it possible that too short of an archive interval could cause
>>> incorrect wind data?
>>>
>>> I presently have loop_hilo = False in order to keep the rain rate
>>> correct.
>>>
>>> This setting keeps the High Wind table value and Wind Speed graph to be
>>> incorrect (too low and wrong date/time)
>>>
>>> My archive interval is presently 120. Would it make a difference to set
>>> it back to the default of 300?
>>>
>>> Thanks, Steve
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Weewx user's group" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx-user+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> 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 weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Whats the best way to extract windrun data for display ??

[Michael Hornsby]

Hi

Can I get some advice on how to extract the windrun data for display ?

This gives me spaces
$day.windrun
$week.windrun
$month.windrun
$year.windrun


This gives me the same number for day and week (below)
$day.windrun.max
$week.windrun.max
$month.windrun.max
$year.windrun.max

Day: 54.1 km
Week: 54.1 km
Month: 684.8 km
Year: 829.6 km

Cheers
Michael

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Incorrect wind data

[gjr80]

Hi,

WeeWX 3.7.0 saw changes to the Vantage driver such that driver now only emits 
obs that the hardware emits. This had an effect on windGust, field windGust 
only exists in Vantage archive records not loop packets. Previously (IIRC), the 
Vantage driver emitted windGust in both loop packets and archive records. When 
you delete your database weeWX will download all available records from the 
logger memory, these records are essentially the previously generated archive 
records (not loop packets).

So what, well depending on your settings you could see the behaviour you 
describe or there could be a bug. It is not possible to say much more without 
knowing details of your config. Could you post a sanitised copy of your 
weewx.conf. You can do his directly or by using the wee_debug utility 
(http://weewx.com/docs/utilities.htm#wee_debug_utility)

Gary

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Sun altitude in graph

[Thomas Keffer]

The best approach would be to write a simple WeeWX service that uses the
almanac module to calculate the altitude of the sun, then add that to the
archive record.

Then add altitude to the database schema.

You would then be able to use it for graphs.

-tk


On Sun, Dec 31, 2017 at 9:41 AM, stefano siega 
wrote:

> Unfortunately I'm not a programmer :( , but I experiment a lot.
> What can be the best approach? Add almanac data to a new database or edit
> imagegenerator to use non-database data?
>
> --
> 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 weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Help weewx.conf for station registry

[torresb1160]

Sorry l’m a total newbee. Got weewx going no problems from the DEB package. 
Would like to register the station and post the data to Weather Underground. I 
don’t understand how to get  weewx.conf to work. I have changed directory to:
$ cd /etc/weewx 
But now what? sudo wee_congif —reconfigure does not bring anything in the 
following section of the user guide: [StdRESTful]

This is my first Raspberry Pi project, and don’t understand permissions and the 
directories yet. Any basic references would be appreciated. I bought “Exploring 
Raspberry Pi” by Derek Molly. This book isn’t really helping too much, I think 
I need it dumbed down to start.
Thanks, Brandon

User Guide Section:
[StdRESTful]
This section is for configuring the StdRESTful services, which upload to simple 
RESTful servers such as the Weather Underground, PWSweather.com, or CWOP.

[[StationRegistry]]
A registry of weeWX weather stations is maintained at weewx.com. Stations are 
displayed on a map and a list at http://weewx.com/stations.html

How does the registry work? Individual weather stations periodically contact 
the registry. Each station provides a URL to identify itself, plus other 
information such as the station type and weeWX version. No personal 
information, nor any meteorological data, is sent.

To add your station to this list, you must do two things:

Enable the StationRegistry in weewx.conf by setting the option 
register_this_station to True. Your station will contact the registry once per 
week. If your station does not contact the registry for about a month, it will 
be removed from the list.
Provide a station_url, either in section [Station], or in the 
[[StationRegistry]] section.
The station_url is used to uniquely identify each station, so choose it 
carefully before you set register_this_station to True.

[StdRestful]
[[StationRegistry]]
register_this_station = True
register_this_station
Set this to True to register the weather station.

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Sun altitude in graph

[vince]

On Sunday, December 31, 2017 at 9:41:30 AM UTC-8, stefano siega wrote:
>
> Unfortunately I'm not a programmer :( , but I experiment a lot. 
> What can be the best approach? Add almanac data to a new database or edit 
> imagegenerator to use non-database data?
>

Add whatever additional data you want to a new database.  Many examples 
have been discussed here over the years.  Use the google group search. 

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Sun altitude in graph

[stefano siega]

Unfortunately I'm not a programmer :( , but I experiment a lot. 
What can be the best approach? Add almanac data to a new database or edit 
imagegenerator to use non-database data?

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Incorrect wind data

[stefano siega]

I think I have found a problem concerning wind gusts.
I have a Davis Vantage Pro2 and Weewx 3.7.1.
I select loop_hilo=False and the windgust are not recorder in database!
But, if I restart WEEWX with a new database, the old entries that are added 
to the database, contain the correct wingust data.
I think weewx ignores the wingust data read from the station at each 
archive interval.
If weewx reads old data from the station's memory, then these contain the 
correct windgust data.

Il giorno lunedì 6 ottobre 2014 16:35:46 UTC+2, Tom Keffer ha scritto:
>
> If you have loop_hilo=False, then LOOP records are not used to record the 
> wind high and low. This means that on weather stations that do not emit 
> windGust in their archive records (nearly every station except Vantage), 
> there will be no windGust field.
>
> We could change this behavior so that the windGust is set to the average 
> wind speed (that is, set it to windSpeed), but I'm reluctant to do this. 
> That's not really what windGust is intended to capture. It would solve your 
> display problems, but introduce semantic problems. 
>
> Changing the archive interval will not make any difference in all of this.
>
> Fundamentally, you need to figure out why the rain rate is incorrect. I 
> know you have a separate thread going on that.,
>
> -tk
>
> On Sat, Oct 4, 2014 at 8:02 AM, Steve2Q > 
> wrote:
>
>> Is it possible that too short of an archive interval could cause 
>> incorrect wind data?
>>
>> I presently have loop_hilo = False in order to keep the rain rate correct.
>>
>> This setting keeps the High Wind table value and Wind Speed graph to be 
>> incorrect (too low and wrong date/time)
>>
>> My archive interval is presently 120. Would it make a difference to set 
>> it back to the default of 300?
>>
>> Thanks, Steve
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Weewx user's group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Anyone using the La Crosse 330-2315 Professional Weather Station with weewx

[mwall]

On Saturday, December 30, 2017 at 8:06:45 PM UTC-5, Ron Springer wrote:
>
> I also bought one of these (the S84060 which is just a different name 
> according to LaCrosse). This is to replace my WS2810 that uses the USB 
> dongle. I'm willing to provide any help that I can in getting a driver for 
> this unit. - RonS
>

is there any way to modify settings on the weather station?  if so, what 
are the settings that you can modify, and how does one change them?

please try the weewx-interceptor driver.  you will probably want to start 
with this configuration:

[Interceptor]
device_type = observer
driver = user.interceptor

you will have to figure out whether you listen or sniff mode (listen is the 
default).

listen mode requires that you get the weather station to send data to the 
computer running weewx.  that means one of (1) modify the weather station 
configuration so that its proxy is the weewx computer, (2) use a local web 
proxy to receive traffic from the weather station and redirect it to the 
computer running weewx, or (3) make a dns entry in your router so that the 
weather station thinks that the weewx computer is weather underground.

sniff mode requires that the computer running weewx can see traffic from 
the weather station.  that means one of (1) using a hub, (2) using a switch 
with port mirroring, (3) bridging on the computer running weewx, or (4) 
sniffing on the edge router and sending that to the compute running weewx.

i find that listen mode with change to weather station config is the 
easiest, assuming that you can modify the station config.

sniffing mode with the weewx computer bridging (e.g., on a raspberry pi3 
with wifi and ethernet) is a bit harder to set up, but is the most 
maintenance free.

details for all of these are in the interceptor readme.

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Sun altitude in graph

[Thomas Keffer]

On Sun, Dec 31, 2017 at 9:01 AM, stefano siega 
wrote:

> Is it possible to use non-database data to create charts in weewx?
>

Unfortunately, no.

-tk​

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Sun altitude in graph

[stefano siega]

Hi all,
I search a lot but I did not find anything.

Is it possible to use non-database data to create charts in weewx?

I want to use the almanac data to draw the graph of the altitude of the sun 
in the last 24 hours.

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Try to Unistall weewx

[Andrew Milner]

You say you are giving the command

sudo apt-get purge weewx

was weewx installed using apt-get, or did you use the setup.py method of 
installation??

did weewx install correctly without errors in the first place?

Was it running successfully??

Are you sure you have not previously deleted the installation??

Otherwise - not a lot for us to work with!!



On Saturday, 30 December 2017 14:41:17 UTC+2, peppe.9...@live.it wrote:

> I get this error
>
> "E: Unable to locate package weewx"
>
> why ?
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Oregon scientific WMR300 issues

[mwall]

On Tuesday, December 26, 2017 at 1:06:24 PM UTC-5, Alberto Sánchez wrote:
>
> Thanks!!! I will test as soon as possible and I will inform here.


wmr300 version 0.19rc2 has been running reliably now on armhf ubuntu 
16.04.03


dpkg --list | grep usb
ii  libusb-0.1-4:armhf 2:0.1.12-28 armhf   userspace USB programming library
ii  libusb-1.0-0:armhf 2:1.0.20-1 armhfuserspace USB programming library
ii  python-usb 1.0.0~b2-2 all  USB interface for Python
ii  usbutils   1:007-4armhfLinux USB utilities


feedback from users with these systems would be helpful:


any x86_64 systems
any armel systems
python-usb 0.4.x
libusb-0.1 (no libusb-1.x installed) 

libusb-1.0.11 (ships with debian 7) 

you can download the driver directly from github:

https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/wmr300.py

this incorporates cameron's history flushing and handles usb non-errors and 
timeouts.  there is not yet any known method for automatically resetting 
the rain counter, but this driver will make a log entry once each day if 
the rain counter has reached its maximum value.

if anyone has been able to use software to reset the rain counter, please 
do some usb captures of the process and post them to weewx-user so that we 
can incorporate that into the driver.

thanks to all of the wmr300 owners who have helped make this driver 
possible!

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Try to Unistall weewx

[peppe . 94thebest]

i'm on raspberry 3 

" sudo apt-get purge weewx "

Il giorno sabato 30 dicembre 2017 13:41:17 UTC+1, peppe.9...@live.it ha 
scritto:
>
> I get this error
>
> "E: Unable to locate package weewx"
>
> why ?
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Try to Unistall weewx

[peppe . 94thebest]

I'm on raspberry 3. 

" sudo apt-get purge weewx "


Il giorno sabato 30 dicembre 2017 14:18:48 UTC+1, Andrew Milner ha scritto:
>
> Probably because you gave the wrong command.
>
> What are you trying to do?
>
> What command did you give??
>
> Without the basic information from you it is impossible to answer your 
> question.
>
>
>
> On Saturday, 30 December 2017 14:41:17 UTC+2, peppe.9...@live.it wrote:
>
>> I get this error
>>
>> "E: Unable to locate package weewx"
>>
>> why ?
>>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Some possible helps for anyone running an old Davis Vantage Pro2 console

[Doug Bo]

Sounds good.  Will figure out how to add my comments to the Wiki.  :)

Doug B.


On Wednesday, December 27, 2017 at 5:13:14 AM UTC-8, Tom Keffer wrote:
>
> Thanks, Doug
>
> Could you put your comments in the Wiki? That way it will be easier for 
> someone to find, rather than search through the nearly 5,000 topics in 
> weewx-user.
>
> Perhaps something in the hardware 
>  section?
>
> -tk
>
> On Tue, Dec 26, 2017 at 7:53 PM, Doug Bo > 
> wrote:
>
>> I'm running an older Vantage Pro2 console, vintage 2007, firmware 1.90  
>> (can't update firmware due to console hardware changes)
>> My WeatherlinkIP is running current firmware but console seems to be very 
>> slow to respond.  I disabled the upload to weatherlink.
>>
>> I had to tweak the conf file to get it to run more than 24 hours.  The 
>> parameter adjustments below are based on threads I found in this forum.  
>> Hopefully my discoveries will help someone.  Although I doubt anyone (other 
>> than me) is running old consoles.  LOL
>>
>> Any other tips are appreciated.  Thanks.
>>
>> I'm currently discussing my options with Davis on updating my consoles.  
>> Maybe newer hardware.  :)
>>
>> Doug B.
>>
>> 
>>
>> loop_on_init = True
>>
>>   
>> # TCP send delay (when using the WeatherLinkIP):
>> tcp_send_delay = 0.5
>>
>>
>>
>> *# experimentcommand_delay = 1.0*
>> # The id of your ISS station (usually 1). If you use a wind meter 
>> connected
>> # to a anemometer transmitter kit, use its id
>> iss_id = 2
>> 
>> # How long to wait for a response from the station before giving up 
>> (in
>> # seconds; must be greater than 2)
>> # timeout = 4
>>
>> *timeout = 8*
>> # How long to wait before trying again (in seconds)
>> # wait_before_retry = 1.2
>>
>> *wait_before_retry = 3.5*
>> # How many times to try before giving up:
>> max_tries = 4
>> 
>> # Vantage model Type: 1 = Vantage Pro; 2 = Vantage Pro2
>> model_type = 2
>> 
>> # The driver to use:
>> driver = weewx.drivers.vantage
>>
>> -- 
>> 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 weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.