Re: [weewx-user] data transmission error correction

[Sébastien F4GQK]

thanks

Sebastien

Le dimanche 15 novembre 2020 à 17:26:38 UTC+1, tke...@gmail.com a écrit :

> See the wiki article Cleaning up old 'bad' data 
> .
>
> *Wunderfixer * 
> can 
> fill in missing data, but there is no utility for changing data on the WU. 
> I doubt it would work.
>
> On Sun, Nov 15, 2020 at 8:17 AM Sébastien F4GQK  wrote:
>
>> Hello, 
>>
>>  my weather station had a calibration error for the atmospheric pressure 
>> and therefore I have errors which were transmitted to WU.  
>>
>> On WU can the transmitted values be modified ?
>>  On Weewx, can we modify the weewx.sdb file  
>>  if so with what software. 
>>
>>  Thank you 
>>
>> Sebastian  
>>
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/e7d48ca9-2c30-47f4-89fe-05cf9a76ed7fn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5cffee26-4371-401d-ba9f-e9aadd348bf4n%40googlegroups.com.

Re: [weewx-user] luftdaten.info - sensor.community air quality data to weewx

[steeple ian]

Google weewx-sds011. There is an extension for that sensor.

In my case I rsync data to my main server and then use weewx-filepile
extension to insert data into the new extended database. I then use a
custom .tmpl to aggregate the data for a rolling 24hr AQI.

Ian

On Sun, 15 Nov 2020 at 20:46, misk...@gmail.com  wrote:

> Hello,
> has anybody integrated the air quality API to WeeWX?
>
> It should be probably something easy, as the sensor firmware has API with
> custom server, path, port, username/password to entry.
>
> or there is also api for sensor.community service
>
> https://sensor.community/
> https://opensensemap.org/
>
> thanks for info,
> Michal, SVK
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/0171755b-7bd6-49f8-bc18-39261c278466n%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CADASSaRzWv6VJhL-6E81Zq2ucNjiDnZUj9LF4qBQdUU0G%2BPMOQ%40mail.gmail.com.

[weewx-user] Questions about weewx-loopdata

[Geni]

Hi john
since weewx 4.2.0 the loop-data.txt is no longer generated?
regards Geni


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3f89791f-c06b-43d1-beac-0afa58df59d6n%40googlegroups.com.
Nov 16 11:26:18 Wetter-Raspi weewx[5058] DEBUG user.loopdata: Created week 
accum in 0.036506 seconds (read 1 records).
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: unit_system
: 16
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: archive_interval   
: 600
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: loop_data_dir  
: /home/pi/wetter/loopdata
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: filename   
: loop-data.txt
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: target_report  
: LoopDataReport
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: loop_frequency 
: 2.5
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: specified_fields   
: ['current.dateTime.raw', 'current.windDir', 
'current.windDir.ordinal_compass', 'current.windchill', 'current.windSpeed', 
'current.windSpeed.formatted', 'current.windSpeed.raw', 'day.windGust.max', 
'day.windGust.max.formatted', '10m.windGust.max', '10m.windGust.max.formatted', 
'10m.wind.rms.formatted', 'day.wind.rms.formatted', 'week.wind.rms.formatted', 
'month.wind.rms.formatted', 'week.windGust.max.formatted', 
'month.windGust.max.formatted', 'current.barometer', 'trend.barometer', 
'trend.barometer.desc', 'trend.barometer.formatted', 'current.rain', 
'current.rainRate', 'current.rainRate.formatted', 'day.rain.sum', 
'day.rain.sum.formatted', 'week.rain.sum.formatted', 
'month.rain.sum.formatted', 'rain.sum', '10m.rain.sum.formatted', 
'current.appTemp', 'current.appTemp.formatted', 'current.outTemp', 
'current.outTemp.formatted', 'trend.outTemp', 'current.inTemp', 
'day.outTemp.avg.formatted', '10m.outTemp.max.formatted', 
'10m.outTemp.min.formatted', 'day.outTemp.max.formatted', 
'day.outTemp.min.formatted', 'week.outTemp.max.formatted', 
'week.outTemp.min.formatted', 'month.outTemp.max.formatted', 
'month.outTemp.min.formatted', 'current.dewpoint.formatted', 
'current.inHumidity', 'current.outHumidity', 'year.outTemp.max.formatted', 
'year.outTemp.min.formatted', 'year.wind.rms.formatted', 
'year.windGust.max.formatted', 'year.rain.sum.formatted', 'month.wind.rms.raw']
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: tmpname
: /tmp/LoopDataop2hf6bf
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: enable 
: 0
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: remote_server  
: www.foobar.com
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: remote_port
: None
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: remote_user
: root
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: remote_dir 
: /home/pi/wetter/loopdata
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: compress   
: 0
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: log_success
: 0
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: ssh_options
: -o ConnectTimeout=1
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: timeout
: 1
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: skip_if_older_than 
: 3
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: time_delta 
: 10800
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: week_start 
: 0
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: rainyear_start 
: 1
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: trend_obstypes 
: ['barometer', 'outTemp']
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: rainyear_obstypes  
: None
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: year_obstypes  
: ['outTemp', 'wind', 'windSpeed', 'windDir', 'windGust', 'windGustDir', 'rain']
Nov 16 11:26:18 Wetter-Raspi weewx[5058] INFO user.loopdata: month_obstypes 
: ['wind', 'windSpeed', 'windDir', 'windGust', 'windGustDir', 'rain', 'outTemp']
Nov 16 11:26:18 Wetter-Raspi weewx[5058] DEBUG user.loopdata: new_loop: event: 
Event type:  | packet: {'dateTime': 1605522378, 
'barometer': 1020.8944382384177, 'inTemp': 22.725, 'inHumidity': 
42.0, 'outTemp': 8.89, 'windSpeed': 3.218688, 'windSpeed10': 
1.609344, 'windDir': 74.0, 'outHumidity': 84.0, 'rainRate': 0.0, 'stormRain': 
0.479970723, 'stormStart': 1605394800, 'dayRain': 0.2999817, 
'monthRain': 1.579903620001, 'yearRain': 86.4947235, 'dayET': 0.0, 
'monthET': 0.0, 'yearET': 0.0, 'leafWet4': 0.0, 'insideAlarm': 0, 'rainAlar

Re: [weewx-user] Questions about weewx-loopdata

[John Kline]

I can duplicate this problem and will issue a fix.

In the meantime, you can add:
rainyear.outTemp.max
to the fields clause in the LoopData section of weewx.conf?

That will stop this problem.  If you get similar errors for other periods where 
you have no fields listed, you’ll have to temporarily add a field for those 
periods also.

I should have a fix shortly.  I don’t know that this is related to WeeWX 4.2, 
not that that really matters. 

> On Nov 16, 2020, at 2:45 AM, Geni  wrote:
> 
> 
> Hi john
> since weewx 4.2.0 the loop-data.txt is no longer generated?
> regards Geni
> 
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/3f89791f-c06b-43d1-beac-0afa58df59d6n%40googlegroups.com.
> 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/54DD3EFB-3691-4D44-8856-2C5699B93F29%40johnkline.com.

[weewx-user] html doesn't update (not DAVIS)

[ka6...@gmail.com]

I've searched through the archives in this group and scoured the 
documentation and can't figure out the search term I need to fix the 
database because of corruption due to rebooting and having incorrect time 
information (time went backwards like problems)

I've seen a thread (several years ago) but can't find it.

Sorry for the repost.

Tom

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/124ac0bb-2a33-47fc-9d6e-58cc2bf21730n%40googlegroups.com.

Re: [weewx-user] html doesn't update (not DAVIS)

[Tom Keffer]

See the section *Deleting unwanted records
*
in
the wiki article *Cleaning up old 'bad' data.*

On Mon, Nov 16, 2020 at 7:47 AM ka6...@gmail.com  wrote:

>
> I've searched through the archives in this group and scoured the
> documentation and can't figure out the search term I need to fix the
> database because of corruption due to rebooting and having incorrect time
> information (time went backwards like problems)
>
> I've seen a thread (several years ago) but can't find it.
>
> Sorry for the repost.
>
> Tom
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/124ac0bb-2a33-47fc-9d6e-58cc2bf21730n%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEDmFqWpdK6O-NtBCraq5CGd3L%2BEXgJfsO9X_CHbGwYytw%40mail.gmail.com.

Re: [weewx-user] Questions about weewx-loopdata

[Geni]

Ok, works
Thank you

jo...@johnkline.com schrieb am Montag, 16. November 2020 um 16:05:21 UTC+1:

> I can duplicate this problem and will issue a fix.
>
> In the meantime, you can add:
> rainyear.outTemp.max
> to the fields clause in the LoopData section of weewx.conf?
>
> That will stop this problem.  If you get similar errors for other periods 
> where you have no fields listed, you’ll have to temporarily add a field for 
> those periods also.
>
> I should have a fix shortly.  I don’t know that this is related to WeeWX 
> 4.2, not that that really matters. 
>
> On Nov 16, 2020, at 2:45 AM, Geni  wrote:
>
> 
>
>
> Hi john
> since weewx 4.2.0 the loop-data.txt is no longer generated?
> regards Geni
>
>
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/3f89791f-c06b-43d1-beac-0afa58df59d6n%40googlegroups.com
>  
> 
> .
> 
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0f6cb227-1cdd-4fbb-9cf9-6f4c59521262n%40googlegroups.com.

[weewx-user] Signal Strength vs Rainfall

[K1IW]

Has anyone else seen this behavior?  Is there an explanation?:


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/73b27956-a94b-4f8e-8ee4-47d4db37f7b6n%40googlegroups.com.

Re: [weewx-user] Signal Strength vs Rainfall

[Bob DeMattia]

Has anyone else seen this behavior?  Is there an explanation?:
[image: image.png]

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAMQUtR9GVR5gYmca-5jSSZZMjkOieGS0-NQXauUubRDCupVsfw%40mail.gmail.com.

Re: [weewx-user] Signal Strength vs Rainfall

[Kevin Davis]

Rain would certainly attenuate RF signals.

On Mon, Nov 16, 2020 at 10:50 AM Bob DeMattia  wrote:

> Has anyone else seen this behavior?  Is there an explanation?:
> [image: image.png]
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAMQUtR9GVR5gYmca-5jSSZZMjkOieGS0-NQXauUubRDCupVsfw%40mail.gmail.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAHiQ_B1bpDMc4EYdp2Qav6TTjaSLtURJ_4dsK8k2fEs-a_hbaQ%40mail.gmail.com.

Re: [weewx-user] Davis WeatherLink Live: Which driver is best?

[Karen K]

*Weatherlinkliveudp*
(https://github.com/grebleem/weewx-weatherlinkliveudp)

No I tested the driver "Weatherlinkliveudp". I installed and activated the 
driver yesterday. By now there were no problems at all. It seems, the 
Weatherlinkliveudp driver is more reliable in terms of rain than WLL. With 
this driver it is possible to stop WeeWX without the need to kill the 
process. 

Using the anemometer transmitter kit is possible. No special configuration 
is required to do so.

I have no additional sensors. So I cannot comment on restrictions there.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7cef0eb1-a1f0-4e21-a837-17b6c7e92ccdn%40googlegroups.com.

Re: [weewx-user] Signal Strength vs Rainfall

[Bob DeMattia]

Quite a bit of attenuation!   The sensor is located approximately 8 feet
horizontally and fifteen feet vertically
from the display.  It must be the wet roof!



On Mon, Nov 16, 2020 at 1:55 PM Kevin Davis  wrote:

> Rain would certainly attenuate RF signals.
>
> On Mon, Nov 16, 2020 at 10:50 AM Bob DeMattia  wrote:
>
>> Has anyone else seen this behavior?  Is there an explanation?:
>> [image: image.png]
>>
>> --
>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/CAMQUtR9GVR5gYmca-5jSSZZMjkOieGS0-NQXauUubRDCupVsfw%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/la8MFO_x9ec/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAHiQ_B1bpDMc4EYdp2Qav6TTjaSLtURJ_4dsK8k2fEs-a_hbaQ%40mail.gmail.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAMQUtR9SPp3sa77UcUEV_5hcVoorjGUczH2PhbzCbZiOOMuPtQ%40mail.gmail.com.

Re: [weewx-user] Signal Strength vs Rainfall

[Greg Troxel]

Bob DeMattia  writes:

> Quite a bit of attenuation!   The sensor is located approximately 8 feet
> horizontally and fifteen feet vertically
> from the display.  It must be the wet roof!

Not sure what you have for station hardware.  That graph suggests Davis
VP2 or Vue, and there I am pretty sure 'signal quality' is a recent
average of the fraction of packets successfully received vs what should
have been received.

Assuming Davis:

Davis at the 8'/15' should be very solid.  It's 915 MHz, and it is very
slow FH, AIUI one data packet on a frequency and a new frequency for the
next packet rotating among a set of 51 (US).  That protects against
narrowband interference.  So I am skeptical that this is just due to
increased path loss.

I don't look at signal strength on my VP2 often, but I used to see a dip
from 100 to 98% occasionally, and the time pattern was suggestive of
some other transmitter, but I haven't figured it out.  But it was a
brief dip to 98%, not hours at 25%.  I just checked and last night with
the temp peak/rain event it was mostly 99.1/99.9% with an occasional
97ish%.  I can perceive no patterns.  Console/sensor distance is
probably 20' horizontal, 10' vertical, so not so different.

Therefore, I would be suspicious of broadband noise happening because of
the rain, although I admit that at 900 the level needed to explain this
does not make a lot of sense.  Speculating wildly and beyond the point
of reason, it could be arcing of a powerline insulator when wet.
Perhaps listen at 450 MHz during the next rain, or at 900 if you have an
SDR set up that can function as a spectrum analyzer (rtlsdr/gqrx?).

You can also use rtldavis to listen to the packets:

  https://github.com/lheijst/rtldavis

with an RTL-SDR dongle.  That might be useful information.

Greg

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/rmia6vhf4rs.fsf%40s1.lexort.com.


signature.asc
Description: PGP signature

Re: [weewx-user] Signal Strength vs Rainfall

[Tom Keffer]

I've also seen signal strength drop inexplicably on my Davis Envoy,
although I've never correlated it with rain. Sometimes it doesn't come back
for days. In those cases, I reset the Envoy by taking the batteries out.
Here's one example:

[image: image.png]
I should note that I also have a VP2 console. I haven't noticed it
happening with the console, but then it only runs occasionally when I'm
working on WeeWX. There's definitely no correlation between the console and
the Envoy, so it must be a receive-side problem.

-tk



On Mon, Nov 16, 2020 at 12:03 PM Greg Troxel  wrote:

>
> Bob DeMattia  writes:
>
> > Quite a bit of attenuation!   The sensor is located approximately 8 feet
> > horizontally and fifteen feet vertically
> > from the display.  It must be the wet roof!
>
> Not sure what you have for station hardware.  That graph suggests Davis
> VP2 or Vue, and there I am pretty sure 'signal quality' is a recent
> average of the fraction of packets successfully received vs what should
> have been received.
>
> Assuming Davis:
>
> Davis at the 8'/15' should be very solid.  It's 915 MHz, and it is very
> slow FH, AIUI one data packet on a frequency and a new frequency for the
> next packet rotating among a set of 51 (US).  That protects against
> narrowband interference.  So I am skeptical that this is just due to
> increased path loss.
>
> I don't look at signal strength on my VP2 often, but I used to see a dip
> from 100 to 98% occasionally, and the time pattern was suggestive of
> some other transmitter, but I haven't figured it out.  But it was a
> brief dip to 98%, not hours at 25%.  I just checked and last night with
> the temp peak/rain event it was mostly 99.1/99.9% with an occasional
> 97ish%.  I can perceive no patterns.  Console/sensor distance is
> probably 20' horizontal, 10' vertical, so not so different.
>
> Therefore, I would be suspicious of broadband noise happening because of
> the rain, although I admit that at 900 the level needed to explain this
> does not make a lot of sense.  Speculating wildly and beyond the point
> of reason, it could be arcing of a powerline insulator when wet.
> Perhaps listen at 450 MHz during the next rain, or at 900 if you have an
> SDR set up that can function as a spectrum analyzer (rtlsdr/gqrx?).
>
> You can also use rtldavis to listen to the packets:
>
>   https://github.com/lheijst/rtldavis
>
> with an RTL-SDR dongle.  That might be useful information.
>
> Greg
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/rmia6vhf4rs.fsf%40s1.lexort.com
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEC_2nAs8x%2B8q1BJQgdyUAQKijSc68QcjOX%2BhjsCU0hf2w%40mail.gmail.com.

Re: [weewx-user] Signal Strength vs Rainfall

[Bob DeMattia]

Yes, I should have mentioned the hardware.

This is an Acurite 15036 which uses 433 MHz.  The batteries are brand new
lithium batteries installed
about one month ago.  The sensor is located in a rural area, in a summer
cottage
that is unoccupied, as are all the ones around except one house two doors
away.

I guess the good news is it seems to come back.  Hopefully it will make it
through the winter without
needing any attention.

Thanks,
Bob


On Mon, Nov 16, 2020 at 3:03 PM Greg Troxel  wrote:

>
> Bob DeMattia  writes:
>
> > Quite a bit of attenuation!   The sensor is located approximately 8 feet
> > horizontally and fifteen feet vertically
> > from the display.  It must be the wet roof!
>
> Not sure what you have for station hardware.  That graph suggests Davis
> VP2 or Vue, and there I am pretty sure 'signal quality' is a recent
> average of the fraction of packets successfully received vs what should
> have been received.
>
> Assuming Davis:
>
> Davis at the 8'/15' should be very solid.  It's 915 MHz, and it is very
> slow FH, AIUI one data packet on a frequency and a new frequency for the
> next packet rotating among a set of 51 (US).  That protects against
> narrowband interference.  So I am skeptical that this is just due to
> increased path loss.
>
> I don't look at signal strength on my VP2 often, but I used to see a dip
> from 100 to 98% occasionally, and the time pattern was suggestive of
> some other transmitter, but I haven't figured it out.  But it was a
> brief dip to 98%, not hours at 25%.  I just checked and last night with
> the temp peak/rain event it was mostly 99.1/99.9% with an occasional
> 97ish%.  I can perceive no patterns.  Console/sensor distance is
> probably 20' horizontal, 10' vertical, so not so different.
>
> Therefore, I would be suspicious of broadband noise happening because of
> the rain, although I admit that at 900 the level needed to explain this
> does not make a lot of sense.  Speculating wildly and beyond the point
> of reason, it could be arcing of a powerline insulator when wet.
> Perhaps listen at 450 MHz during the next rain, or at 900 if you have an
> SDR set up that can function as a spectrum analyzer (rtlsdr/gqrx?).
>
> You can also use rtldavis to listen to the packets:
>
>   https://github.com/lheijst/rtldavis
>
> with an RTL-SDR dongle.  That might be useful information.
>
> Greg
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAMQUtR-GzF_Kf_ANV5qp3cp%3D78%3DdKoHsgAtoUeXSGy5bt99Bbg%40mail.gmail.com.

Re: [weewx-user] Get external temperature from MQTT + rest from WMR200

[Invisible Man]

NB. The solution was solved here: 
https://github.com/bellrichm/WeeWX-MQTTSubscribe/issues/96 :)
Thanks!

On Wednesday, November 11, 2020 at 5:50:20 PM UTC+1 Invisible Man wrote:

> Sure. I'll post everything from the start.
>
>
> On Wednesday, November 11, 2020 at 5:26:04 PM UTC+1 bell...@gmail.com 
> wrote:
>
>>
>> Hard to say what is wrong from that snippet of log. Could you post the 
>> log from start up through an archive record creation?
>> rich
>> On Wednesday, 11 November 2020 at 11:09:00 UTC-5 axelle@gmail.com 
>> wrote:
>>
>>> I've shifted to using https://github.com/bellrichm/WeeWX-MQTTSubscribe 
>>> but it's still not working : I don't see my external tempeature on weewx.
>>>
>>> This is my logs (I grepped for outTemp). I wonder if the issue is coming 
>>> from the fact that WMR200 has an outTemp but it is faulty so I  have 
>>> outTempFault set to 1.
>>>
>>> Nov 11 16:39:42 vegan weewx[30478] INFO weewx.drivers.wmr200: sensor map 
>>> is {'outTempBatteryStatus': 'battery_status_out', 'outHumidity': 
>>> 'humidity_1', 'rainRate': 'rain_rate', 'heatindex4': 'heatindex_5', 
>>> 'rainTotal': 'rain_total', 'rainBatteryStatus': 'battery_status_rain', 
>>> 'heatindex6': 'heatindex_7', 'extraTemp5': 'temperature_6', 'uvFault': 
>>> 'uv_fault', 'extraTemp2': 'temperature_3', 'heatindex': 'heatindex_1', 
>>> 'extraTemp3': 'temperature_4', 'rain24': 'rain_24', 'inHeatindex': 
>>> 'heatindex_0', 'inTemp': 'temperature_0', 'extraTemp1': 'temperature_2', 
>>> 'hourRain': 'rain_hour', 'windFault': 'wind_fault', 'windchill': 
>>> 'windchill', 'clockUnsynchronized': 'clock_unsynchronized', 'extraTemp7': 
>>> 'temperature_8', 'rain': 'rain', 'forecastIcon': 'forecast_icon', 
>>> 'pressure': 'pressure', 'extraHumid4': 'humidity_5', 'extraHumid5': 
>>> 'humidity_6', 'extraHumid2': 'humidity_3', 'extraHumid3': 'humidity_4', 
>>> 'extraHumid1': 'humidity_2', 'extraTemp6': 'temperature_7', 'heatindex5': 
>>> 'heatindex_6', 'extraTemp4': 'temperature_5', 'heatindex7': 'heatindex_8', 
>>> 'altimeter': 'altimeter', 'heatindex1': 'heatindex_2', 'heatindex2': 
>>> 'heatindex_3', 'heatindex3': 'heatindex_4', 'extraHumid6': 'humidity_7', 
>>> 'extraHumid7': 'humidity_8', 'windBatteryStatus': 'battery_status_wind', 
>>> 'UV': 'uv', 'rainFault': 'rain_fault', 'windDir': 'wind_dir', 'outTemp': 
>>> 'temperature_1', 'windSpeed': 'wind_speed', 'inHumidity': 'humidity_0', 
>>> 'outTempFault': 'out_fault', 'windGust': 'wind_gust', 'uvBatteryStatus': 
>>> 'battery_status_uv'}
>>> Nov 11 16:41:46 vegan weewx[30694] INFO weewx.drivers.wmr200: sensor map 
>>> is {'outTempBatteryStatus': 'battery_status_out', 'outHumidity': 
>>> 'humidity_1', 'rainRate': 'rain_rate', 'heatindex4': 'heatindex_5', 
>>> 'rainTotal': 'rain_total', 'rainBatteryStatus': 'battery_status_rain', 
>>> 'heatindex6': 'heatindex_7', 'extraTemp5': 'temperature_6', 'uvFault': 
>>> 'uv_fault', 'extraTemp2': 'temperature_3', 'heatindex': 'heatindex_1', 
>>> 'extraTemp3': 'temperature_4', 'rain24': 'rain_24', 'inHeatindex': 
>>> 'heatindex_0', 'inTemp': 'temperature_0', 'extraTemp1': 'temperature_2', 
>>> 'hourRain': 'rain_hour', 'windFault': 'wind_fault', 'windchill': 
>>> 'windchill', 'clockUnsynchronized': 'clock_unsynchronized', 'extraTemp7': 
>>> 'temperature_8', 'rain': 'rain', 'forecastIcon': 'forecast_icon', 
>>> 'pressure': 'pressure', 'extraHumid4': 'humidity_5', 'extraHumid5': 
>>> 'humidity_6', 'extraHumid2': 'humidity_3', 'extraHumid3': 'humidity_4', 
>>> 'extraHumid1': 'humidity_2', 'extraTemp6': 'temperature_7', 'heatindex5': 
>>> 'heatindex_6', 'extraTemp4': 'temperature_5', 'heatindex7': 'heatindex_8', 
>>> 'altimeter': 'altimeter', 'heatindex1': 'heatindex_2', 'heatindex2': 
>>> 'heatindex_3', 'heatindex3': 'heatindex_4', 'extraHumid6': 'humidity_7', 
>>> 'extraHumid7': 'humidity_8', 'windBatteryStatus': 'battery_status_wind', 
>>> 'UV': 'uv', 'rainFault': 'rain_fault', 'windDir': 'wind_dir', 'outTemp': 
>>> 'temperature_1', 'windSpeed': 'wind_speed', 'inHumidity': 'humidity_0', 
>>> 'outTempFault': 'out_fault', 'windGust': 'wind_gust', 'uvBatteryStatus': 
>>> 'battery_status_uv'}
>>> Nov 11 16:46:29 vegan weewx[30993] INFO weewx.drivers.wmr200: sensor map 
>>> is {'outTempBatteryStatus': 'battery_status_out', 'outHumidity': 
>>> 'humidity_1', 'rainRate': 'rain_rate', 'heatindex4': 'heatindex_5', 
>>> 'rainTotal': 'rain_total', 'rainBatteryStatus': 'battery_status_rain', 
>>> 'heatindex6': 'heatindex_7', 'extraTemp5': 'temperature_6', 'uvFault': 
>>> 'uv_fault', 'extraTemp2': 'temperature_3', 'heatindex': 'heatindex_1', 
>>> 'extraTemp3': 'temperature_4', 'rain24': 'rain_24', 'inHeatindex': 
>>> 'heatindex_0', 'inTemp': 'temperature_0', 'extraTemp1': 'temperature_2', 
>>> 'hourRain': 'rain_hour', 'windFault': 'wind_fault', 'windchill': 
>>> 'windchill', 'clockUnsynchronized': 'clock_unsynchronized', 'extraTemp7': 
>>> 'temperature_8', 'rain': 'rain', 'forecastIcon': 'forecast_icon', 
>>> 'pressure': 'pressure', 'extraHumid4': 'humidity_5', 'extraH

[weewx-user] Davis VP2 can't open ttyUSB0

[bgra...@umw.edu]

I have a VP2 console that I am connecting to an RPI OS (latest). Weewx is 
latest using setup.py. This RPI was running weewx (jessie) with no problems 
and using ttyUSB0 from weewx.conf. The vantage driver seems ok and I 
actually moved the old one over to be sure.
I tried listening to the console with minicom but got no data. I swapped 
out the RS232/USB converter but got the same problem.  Not sure what I have 
done wrong, other than trying to fix something that wasn't broken...

Attached file of some debug info.

Thanks for any suggestions.

Bob

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/328d0e08-16f5-461c-8782-f6ee86e95008n%40googlegroups.com.
Linux raspberrypi 5.4.72-v7+ #1356 SMP Thu Oct 22 13:56:54 BST 2020 armv7l 
GNU/Linux

wee_device:
Using configuration file /home/weewx/weewx.conf
Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
Traceback (most recent call last):
  File "./wee_device", line 78, in 
main()
  File "./wee_device", line 74, in main
device.configure(config_dict)
  File "/home/weewx/bin/weewx/drivers/__init__.py", line 67, in configure
self.do_options(options, parser, config_dict, not options.noprompt)
  File "/home/weewx/bin/weewx/drivers/vantage.py", line 2056, in do_options
station = Vantage(**config_dict[DRIVER_NAME])
  File "/home/weewx/bin/weewx/drivers/vantage.py", line 515, in __init__
self._setup()
  File "/home/weewx/bin/weewx/drivers/vantage.py", line 1317, in _setup
self.port.wakeup_console(max_tries=self.max_tries)
  File "/home/weewx/bin/weewx/drivers/vantage.py", line 118, in wakeup_console
raise weewx.WakeupError("Unable to wake up Vantage console")
weewx.WakeupError: Unable to wake up Vantage console



dmesg:
364.269928] usb 1-1.5: new full-speed USB device number 7 using dwc_otg
[  364.427490] usb 1-1.5: New USB device found, idVendor=0403, idProduct=6001, 
bcdDevice= 6.00
[  364.427508] usb 1-1.5: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[  364.427520] usb 1-1.5: Product: FT232R USB UART
[  364.427533] usb 1-1.5: Manufacturer: FTDI
[  364.427545] usb 1-1.5: SerialNumber: A5052IYA
[  364.436085] usb 1-1.5: Detected FT232RL
[  364.437634] usb 1-1.5: FTDI USB Serial Device converter now attached to 
ttyUSB0
[  955.337038] usb 1-1.5: USB disconnect, device number 7
[  961.782001] usb 1-1.4: new full-speed USB device number 8 using dwc_otg
[  961.939483] usb 1-1.4: New USB device found, idVendor=0403, idProduct=6001, 
bcdDevice= 6.00
[  961.939501] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[  961.939512] usb 1-1.4: Product: FT232R USB UART
[  961.939522] usb 1-1.4: Manufacturer: FTDI
[  961.939532] usb 1-1.4: SerialNumber: A5052JQ7
[  961.948057] usb 1-1.4: Detected FT232RL
[  961.950936] usb 1-1.4: FTDI USB Serial Device converter now attached to 
ttyUSB0

syslog on service weewx restart:
Nov 16 17:30:15 raspberrypi systemd[1]: Stopping LSB: weewx weather system...
Nov 16 17:30:15 raspberrypi weewx[2103]: Stopping weewx weather system: weewx 
not running
Nov 16 17:30:15 raspberrypi systemd[1]: weewx.service: Succeeded.
Nov 16 17:30:15 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
Nov 16 17:30:15 raspberrypi systemd[1]: Starting LSB: weewx weather system...
Nov 16 17:30:15 raspberrypi weewx[2125] INFO __main__: Initializing weewx 
version 4.2.0
Nov 16 17:30:15 raspberrypi weewx[2125] INFO __main__: Using Python 3.7.3 
(default, Jul 25 2020, 13:03:44) #012[GCC 8.3.0]
Nov 16 17:30:15 raspberrypi weewx[2125] INFO __main__: Platform 
Linux-5.4.72-v7+-armv7l-with-debian-10.6
Nov 16 17:30:15 raspberrypi weewx[2125] INFO __main__: Locale is 'en_US.UTF-8'
Nov 16 17:30:15 raspberrypi weewx[2125] INFO __main__: PID file is 
/var/run/weewx.pid
Nov 16 17:30:15 raspberrypi weewx[2129] INFO __main__: Using configuration file 
/home/weewx/weewx.conf
Nov 16 17:30:15 raspberrypi weewx[2129] INFO __main__: Debug is 1
Nov 16 17:30:15 raspberrypi weewx[2129] DEBUG __main__: Initializing engine
Nov 16 17:30:15 raspberrypi weewx[2129] INFO weewx.engine: Loading station type 
Vantage (weewx.drivers.vantage)
Nov 16 17:30:15 raspberrypi weewx[2129] DEBUG weewx.drivers.vantage: Driver 
version is 3.2.1
Nov 16 17:30:15 raspberrypi weewx[2129] DEBUG weewx.drivers.vantage: Option 
loop_request=1
Nov 16 17:30:15 raspberrypi weewx[2114]: Starting weewx weather system: weewx.
Nov 16 17:30:15 raspberrypi systemd[1]: Started LSB: weewx weather system.
Nov 16 17:30:15 raspberrypi weewx[2129] DEBUG weewx.drivers.vantage: Opened up 
serial port /dev/ttyUSB0; baud 19200; timeout 4.00
Nov 16 17:30:20 raspberrypi weewx[2129] DEBUG weewx.drivers.vantage: Retry #0 
failed
Nov 16 17:30:24 raspberrypi weewx[2129] DEBUG weewx.drivers.vantage: Retry #1 

Re: [weewx-user] Questions about weewx-loopdata

[John Kline]

A fix is released (v2.7.2).  There is no hurry to install the new release; but 
once you’ve installed it, you can remove the field I asked you to add to 
weewx.conf.

> On Nov 16, 2020, at 9:04 AM, Geni  wrote:
> 
> Ok, works
> Thank you
> 
> jo...@johnkline.com schrieb am Montag, 16. November 2020 um 16:05:21 UTC+1:
>> I can duplicate this problem and will issue a fix.
>> 
>> In the meantime, you can add:
>> rainyear.outTemp.max
>> to the fields clause in the LoopData section of weewx.conf?
>> 
>> That will stop this problem.  If you get similar errors for other periods 
>> where you have no fields listed, you’ll have to temporarily add a field for 
>> those periods also.
>> 
>> I should have a fix shortly.  I don’t know that this is related to WeeWX 
>> 4.2, not that that really matters. 
>> 
 On Nov 16, 2020, at 2:45 AM, Geni  wrote:
 
>>> 
>> 
>>> 
>>> Hi john
>>> since weewx 4.2.0 the loop-data.txt is no longer generated?
>>> regards Geni
>>> 
>>> 
>> 
>>> -- 
>>> 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.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/3f89791f-c06b-43d1-beac-0afa58df59d6n%40googlegroups.com.
>>> 
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/0f6cb227-1cdd-4fbb-9cf9-6f4c59521262n%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1F79D9DD-276F-4A97-9E84-5F0E11E858B7%40johnkline.com.

Re: [weewx-user] Davis VP2 can't open ttyUSB0

[Graham Eddy]

from the log:
the USB/serial adapter seems okay and provides a port.
weewx has opened the port, written some data out, but received no data on read.
is the vp2 connected to the USB/serial adapter? (my DB9 plug sometimes comes 
adrift so i screwed it in…)

> On 17 Nov 2020, at 9:55 am, bgra...@umw.edu  wrote:
> 
> I have a VP2 console that I am connecting to an RPI OS (latest). Weewx is 
> latest using setup.py. This RPI was running weewx (jessie) with no problems 
> and using ttyUSB0 from weewx.conf. The vantage driver seems ok and I actually 
> moved the old one over to be sure.
> I tried listening to the console with minicom but got no data. I swapped out 
> the RS232/USB converter but got the same problem.  Not sure what I have done 
> wrong, other than trying to fix something that wasn't broken...
> 
> Attached file of some debug info.
> 
> Thanks for any suggestions.
> 
> Bob
> 
> -- 
> 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 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/328d0e08-16f5-461c-8782-f6ee86e95008n%40googlegroups.com
>  
> .
> 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5DFC411D-DE1A-4D56-A37D-1A529812BBD2%40gmail.com.

Re: [weewx-user] Davis VP2 can't open ttyUSB0

[Tom Keffer]

When you say  you "tried listening to the console with minicom but got no
data" what do you mean?

In particular, did you set the baudrate? And, did you type  a few
types before trying to type TEST?

-tk

On Mon, Nov 16, 2020 at 2:55 PM bgra...@umw.edu  wrote:

> I have a VP2 console that I am connecting to an RPI OS (latest). Weewx is
> latest using setup.py. This RPI was running weewx (jessie) with no problems
> and using ttyUSB0 from weewx.conf. The vantage driver seems ok and I
> actually moved the old one over to be sure.
> I tried listening to the console with minicom but got no data. I swapped
> out the RS232/USB converter but got the same problem.  Not sure what I have
> done wrong, other than trying to fix something that wasn't broken...
>
> Attached file of some debug info.
>
> Thanks for any suggestions.
>
> Bob
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/328d0e08-16f5-461c-8782-f6ee86e95008n%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEBrP18O9XOgDc7UztC_qVnkqzzN9xpiXssb8AHcda3AKQ%40mail.gmail.com.

Re: [weewx-user] Davis VP2 can't open ttyUSB0

[bgra...@umw.edu]

I don’t remember the minicom string but it was the one posted to test TEST. 
When I opened minicom it just sat there no echo on TEST or VER. No reply. 
Several reboots no results. /dev/ttyUSB0 is there but does not respond. 
Dmesg Seems to have found it.
I checked all plugs and connections. Removed batteries from console to 
reboot. Even tried new RS232/USB dongle. I have a main ubuntu linux pc 
running from the ISS so I know that’s working and sending data. The rpi is 
setup as a second console which was running weather34. Thanks Tom and 
Graham (you helped me in the days of wview).
Bob
Main setup: grattans.org/wx
On Monday, November 16, 2020 at 6:43:17 PM UTC-5 tke...@gmail.com wrote:

> When you say  you "tried listening to the console with minicom but got no 
> data" what do you mean?
>
> In particular, did you set the baudrate? And, did you type  a few 
> types before trying to type TEST?
>
> -tk
>
> On Mon, Nov 16, 2020 at 2:55 PM bgra...@umw.edu  wrote:
>
>> I have a VP2 console that I am connecting to an RPI OS (latest). Weewx is 
>> latest using setup.py. This RPI was running weewx (jessie) with no problems 
>> and using ttyUSB0 from weewx.conf. The vantage driver seems ok and I 
>> actually moved the old one over to be sure.
>> I tried listening to the console with minicom but got no data. I swapped 
>> out the RS232/USB converter but got the same problem.  Not sure what I have 
>> done wrong, other than trying to fix something that wasn't broken...
>>
>> Attached file of some debug info.
>>
>> Thanks for any suggestions.
>>
>> Bob
>>
>> -- 
>>
> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/328d0e08-16f5-461c-8782-f6ee86e95008n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4dea6744-d613-45ad-90f9-46fdf04ceb7an%40googlegroups.com.

Re: [weewx-user] Davis VP2 can't open ttyUSB0

[Tom Keffer]

OK, but did you hit  a few times before typing "TEST"? If so, you
have a connectivity problem, not a WeeWX problem.

But, you probably already knew that!

-tk

On Mon, Nov 16, 2020 at 4:57 PM bgra...@umw.edu  wrote:

>
> I don’t remember the minicom string but it was the one posted to test
> TEST. When I opened minicom it just sat there no echo on TEST or VER. No
> reply. Several reboots no results. /dev/ttyUSB0 is there but does not
> respond. Dmesg Seems to have found it.
> I checked all plugs and connections. Removed batteries from console to
> reboot. Even tried new RS232/USB dongle. I have a main ubuntu linux pc
> running from the ISS so I know that’s working and sending data. The rpi is
> setup as a second console which was running weather34. Thanks Tom and
> Graham (you helped me in the days of wview).
> Bob
> Main setup: grattans.org/wx
> On Monday, November 16, 2020 at 6:43:17 PM UTC-5 tke...@gmail.com wrote:
>
>> When you say  you "tried listening to the console with minicom but got no
>> data" what do you mean?
>>
>> In particular, did you set the baudrate? And, did you type  a few
>> types before trying to type TEST?
>>
>> -tk
>>
>> On Mon, Nov 16, 2020 at 2:55 PM bgra...@umw.edu  wrote:
>>
>>> I have a VP2 console that I am connecting to an RPI OS (latest). Weewx
>>> is latest using setup.py. This RPI was running weewx (jessie) with no
>>> problems and using ttyUSB0 from weewx.conf. The vantage driver seems ok and
>>> I actually moved the old one over to be sure.
>>> I tried listening to the console with minicom but got no data. I swapped
>>> out the RS232/USB converter but got the same problem.  Not sure what I have
>>> done wrong, other than trying to fix something that wasn't broken...
>>>
>>> Attached file of some debug info.
>>>
>>> Thanks for any suggestions.
>>>
>>> Bob
>>>
>>> --
>>>
>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/328d0e08-16f5-461c-8782-f6ee86e95008n%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/4dea6744-d613-45ad-90f9-46fdf04ceb7an%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEBgWKF%2BM-d9F8xSZtSohpiT-EJwGL%2BOp7gLJ3QqENFAfw%40mail.gmail.com.

Re: [weewx-user] Davis VP2 can't open ttyUSB0

[bgra...@umw.edu]

Yes, I did hit enter many times. Since dmesg said that the usb had attached 
to ttyUSB0 then I assumed (maybe incorrectly) the rpi had connected. I’m at 
a loss because everything was working...  Thanks.

On Monday, November 16, 2020 at 7:59:54 PM UTC-5 tke...@gmail.com wrote:

> OK, but did you hit  a few times before typing "TEST"? If so, you 
> have a connectivity problem, not a WeeWX problem.
>
> But, you probably already knew that!
>
> -tk
>
> On Mon, Nov 16, 2020 at 4:57 PM bgra...@umw.edu  wrote:
>
>>
>> I don’t remember the minicom string but it was the one posted to test 
>> TEST. When I opened minicom it just sat there no echo on TEST or VER. No 
>> reply. Several reboots no results. /dev/ttyUSB0 is there but does not 
>> respond. Dmesg Seems to have found it.
>> I checked all plugs and connections. Removed batteries from console to 
>> reboot. Even tried new RS232/USB dongle. I have a main ubuntu linux pc 
>> running from the ISS so I know that’s working and sending data. The rpi is 
>> setup as a second console which was running weather34. Thanks Tom and 
>> Graham (you helped me in the days of wview).
>> Bob
>> Main setup: grattans.org/wx
>> On Monday, November 16, 2020 at 6:43:17 PM UTC-5 tke...@gmail.com wrote:
>>
>>> When you say  you "tried listening to the console with minicom but got 
>>> no data" what do you mean?
>>>
>>> In particular, did you set the baudrate? And, did you type  a few 
>>> types before trying to type TEST?
>>>
>>> -tk
>>>
>>> On Mon, Nov 16, 2020 at 2:55 PM bgra...@umw.edu  wrote:
>>>
 I have a VP2 console that I am connecting to an RPI OS (latest). Weewx 
 is latest using setup.py. This RPI was running weewx (jessie) with no 
 problems and using ttyUSB0 from weewx.conf. The vantage driver seems ok 
 and 
 I actually moved the old one over to be sure.
 I tried listening to the console with minicom but got no data. I 
 swapped out the RS232/USB converter but got the same problem.  Not sure 
 what I have done wrong, other than trying to fix something that wasn't 
 broken...

 Attached file of some debug info.

 Thanks for any suggestions.

 Bob

 -- 

>>> 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.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/328d0e08-16f5-461c-8782-f6ee86e95008n%40googlegroups.com
  
 
 .

>>> -- 
>> 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.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/4dea6744-d613-45ad-90f9-46fdf04ceb7an%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8afb9f09-184c-4244-ab5a-1590174ab7c0n%40googlegroups.com.

Re: [weewx-user] Davis VP2 can't open ttyUSB0

[Tom Keffer]

The only thing I can think of to try is to reseat the logger.

Unless, you actually have the serial version of the VantagePro and are
using a serial-to-usb converter. They are notoriously flakey. If you have a
spare one, try that.

If none of that works, call Davis.

On Mon, Nov 16, 2020 at 5:04 PM bgra...@umw.edu  wrote:

> Yes, I did hit enter many times. Since dmesg said that the usb had
> attached to ttyUSB0 then I assumed (maybe incorrectly) the rpi had
> connected. I’m at a loss because everything was working...  Thanks.
>
> On Monday, November 16, 2020 at 7:59:54 PM UTC-5 tke...@gmail.com wrote:
>
>> OK, but did you hit  a few times before typing "TEST"? If so, you
>> have a connectivity problem, not a WeeWX problem.
>>
>> But, you probably already knew that!
>>
>> -tk
>>
>> On Mon, Nov 16, 2020 at 4:57 PM bgra...@umw.edu  wrote:
>>
>>>
>>> I don’t remember the minicom string but it was the one posted to test
>>> TEST. When I opened minicom it just sat there no echo on TEST or VER. No
>>> reply. Several reboots no results. /dev/ttyUSB0 is there but does not
>>> respond. Dmesg Seems to have found it.
>>> I checked all plugs and connections. Removed batteries from console to
>>> reboot. Even tried new RS232/USB dongle. I have a main ubuntu linux pc
>>> running from the ISS so I know that’s working and sending data. The rpi is
>>> setup as a second console which was running weather34. Thanks Tom and
>>> Graham (you helped me in the days of wview).
>>> Bob
>>> Main setup: grattans.org/wx
>>> On Monday, November 16, 2020 at 6:43:17 PM UTC-5 tke...@gmail.com wrote:
>>>
 When you say  you "tried listening to the console with minicom but got
 no data" what do you mean?

 In particular, did you set the baudrate? And, did you type  a
 few types before trying to type TEST?

 -tk

 On Mon, Nov 16, 2020 at 2:55 PM bgra...@umw.edu 
 wrote:

> I have a VP2 console that I am connecting to an RPI OS (latest). Weewx
> is latest using setup.py. This RPI was running weewx (jessie) with no
> problems and using ttyUSB0 from weewx.conf. The vantage driver seems ok 
> and
> I actually moved the old one over to be sure.
> I tried listening to the console with minicom but got no data. I
> swapped out the RS232/USB converter but got the same problem.  Not sure
> what I have done wrong, other than trying to fix something that wasn't
> broken...
>
> Attached file of some debug info.
>
> Thanks for any suggestions.
>
> Bob
>
> --
>
 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/328d0e08-16f5-461c-8782-f6ee86e95008n%40googlegroups.com
> 
> .
>
 --
>>> 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.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/4dea6744-d613-45ad-90f9-46fdf04ceb7an%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/8afb9f09-184c-4244-ab5a-1590174ab7c0n%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEDe8QV9y-AUhAxwUuEYZgrw11TicU4UYdmJJ9TinAvnPg%40mail.gmail.com.

Re: [weewx-user] Davis VP2 can't open ttyUSB0

[Greg from Oz]

Is the user running this in the dialout group? 

On Tuesday, 17 November 2020 at 12:30:14 UTC+11 tke...@gmail.com wrote:

> The only thing I can think of to try is to reseat the logger. 
>
> Unless, you actually have the serial version of the VantagePro and are 
> using a serial-to-usb converter. They are notoriously flakey. If you have a 
> spare one, try that.
>
> If none of that works, call Davis.
>
> On Mon, Nov 16, 2020 at 5:04 PM bgra...@umw.edu  wrote:
>
>> Yes, I did hit enter many times. Since dmesg said that the usb had 
>> attached to ttyUSB0 then I assumed (maybe incorrectly) the rpi had 
>> connected. I’m at a loss because everything was working...  Thanks.
>>
>> On Monday, November 16, 2020 at 7:59:54 PM UTC-5 tke...@gmail.com wrote:
>>
>>> OK, but did you hit  a few times before typing "TEST"? If so, you 
>>> have a connectivity problem, not a WeeWX problem.
>>>
>>> But, you probably already knew that!
>>>
>>> -tk
>>>
>>> On Mon, Nov 16, 2020 at 4:57 PM bgra...@umw.edu  wrote:
>>>

 I don’t remember the minicom string but it was the one posted to test 
 TEST. When I opened minicom it just sat there no echo on TEST or VER. No 
 reply. Several reboots no results. /dev/ttyUSB0 is there but does not 
 respond. Dmesg Seems to have found it.
 I checked all plugs and connections. Removed batteries from console to 
 reboot. Even tried new RS232/USB dongle. I have a main ubuntu linux pc 
 running from the ISS so I know that’s working and sending data. The rpi is 
 setup as a second console which was running weather34. Thanks Tom and 
 Graham (you helped me in the days of wview).
 Bob
 Main setup: grattans.org/wx
 On Monday, November 16, 2020 at 6:43:17 PM UTC-5 tke...@gmail.com 
 wrote:

> When you say  you "tried listening to the console with minicom but got 
> no data" what do you mean?
>
> In particular, did you set the baudrate? And, did you type  a 
> few types before trying to type TEST?
>
> -tk
>
> On Mon, Nov 16, 2020 at 2:55 PM bgra...@umw.edu  
> wrote:
>
>> I have a VP2 console that I am connecting to an RPI OS (latest). 
>> Weewx is latest using setup.py. This RPI was running weewx (jessie) with 
>> no 
>> problems and using ttyUSB0 from weewx.conf. The vantage driver seems ok 
>> and 
>> I actually moved the old one over to be sure.
>> I tried listening to the console with minicom but got no data. I 
>> swapped out the RS232/USB converter but got the same problem.  Not sure 
>> what I have done wrong, other than trying to fix something that wasn't 
>> broken...
>>
>> Attached file of some debug info.
>>
>> Thanks for any suggestions.
>>
>> Bob
>>
>> -- 
>>
> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/328d0e08-16f5-461c-8782-f6ee86e95008n%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
 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.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/4dea6744-d613-45ad-90f9-46fdf04ceb7an%40googlegroups.com
  
 
 .

>>> -- 
>> 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.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/8afb9f09-184c-4244-ab5a-1590174ab7c0n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1af9c85d-756c-47ed-a88b-53526b5e9ed5n%40googlegroups.com.

Re: [weewx-user] Davis VP2 can't open ttyUSB0

[Tom Keffer]

If it were a permissions problem, it would have said so. Same if
modemmanager controlled the port. Still, it doesn't hurt to try lsof and
see if anything else is using the port.

*lsof /dev/ttyUSB0*




On Mon, Nov 16, 2020 at 5:36 PM Greg from Oz  wrote:

> Is the user running this in the dialout group?
>
> On Tuesday, 17 November 2020 at 12:30:14 UTC+11 tke...@gmail.com wrote:
>
>> The only thing I can think of to try is to reseat the logger.
>>
>> Unless, you actually have the serial version of the VantagePro and are
>> using a serial-to-usb converter. They are notoriously flakey. If you have a
>> spare one, try that.
>>
>> If none of that works, call Davis.
>>
>> On Mon, Nov 16, 2020 at 5:04 PM bgra...@umw.edu  wrote:
>>
>>> Yes, I did hit enter many times. Since dmesg said that the usb had
>>> attached to ttyUSB0 then I assumed (maybe incorrectly) the rpi had
>>> connected. I’m at a loss because everything was working...  Thanks.
>>>
>>> On Monday, November 16, 2020 at 7:59:54 PM UTC-5 tke...@gmail.com wrote:
>>>
 OK, but did you hit  a few times before typing "TEST"? If so,
 you have a connectivity problem, not a WeeWX problem.

 But, you probably already knew that!

 -tk

 On Mon, Nov 16, 2020 at 4:57 PM bgra...@umw.edu 
 wrote:

>
> I don’t remember the minicom string but it was the one posted to test
> TEST. When I opened minicom it just sat there no echo on TEST or VER. No
> reply. Several reboots no results. /dev/ttyUSB0 is there but does not
> respond. Dmesg Seems to have found it.
> I checked all plugs and connections. Removed batteries from console to
> reboot. Even tried new RS232/USB dongle. I have a main ubuntu linux pc
> running from the ISS so I know that’s working and sending data. The rpi is
> setup as a second console which was running weather34. Thanks Tom and
> Graham (you helped me in the days of wview).
> Bob
> Main setup: grattans.org/wx
> On Monday, November 16, 2020 at 6:43:17 PM UTC-5 tke...@gmail.com
> wrote:
>
>> When you say  you "tried listening to the console with minicom but
>> got no data" what do you mean?
>>
>> In particular, did you set the baudrate? And, did you type  a
>> few types before trying to type TEST?
>>
>> -tk
>>
>> On Mon, Nov 16, 2020 at 2:55 PM bgra...@umw.edu 
>> wrote:
>>
>>> I have a VP2 console that I am connecting to an RPI OS (latest).
>>> Weewx is latest using setup.py. This RPI was running weewx (jessie) 
>>> with no
>>> problems and using ttyUSB0 from weewx.conf. The vantage driver seems ok 
>>> and
>>> I actually moved the old one over to be sure.
>>> I tried listening to the console with minicom but got no data. I
>>> swapped out the RS232/USB converter but got the same problem.  Not sure
>>> what I have done wrong, other than trying to fix something that wasn't
>>> broken...
>>>
>>> Attached file of some debug info.
>>>
>>> Thanks for any suggestions.
>>>
>>> Bob
>>>
>>> --
>>>
>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/328d0e08-16f5-461c-8782-f6ee86e95008n%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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.
>
 To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/4dea6744-d613-45ad-90f9-46fdf04ceb7an%40googlegroups.com
> 
> .
>
 --
>>> 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.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/8afb9f09-184c-4244-ab5a-1590174ab7c0n%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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...@g

[weewx-user] Re: New Router, New Fiber and 4.1 Weewx

[John S]

This didn't end as well as I thought it would. After running OK for a few 
weeks, things went wonky again. I do not have a good idea of why, I did 
upgrade to 4.2.0 but don't think that really had anything to do with it, in 
fact, I was hoping it would fix the ip-read errors I'm seeing.
The scenario is pretty much the same, the system chugs along well for a few 
hours then I see either the ip-read error or a broken pipe error message 
and the software doesn't recover nor does it finish its loops and publish 
data.
But, I have another work around that is working fine for the last 24 hours. 
While trouble shooting this, I noticed weewx will collect any old interval 
data and store it in the db, this is normal behaviour. The ip-read error or 
broken pipe error occurs later in the cycle.
So, if I run weewx_reports /etc/weewx/weewx.conf, that will pick up all the 
data and format the output then FTP it to my website. 
I added a few lines to the crontab to do this for me:
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# Example of job definition:
# . minute (0 - 59)
# |  .- hour (0 - 23)
# |  |  .-- day of month (1 - 31)
# |  |  |  .--- month (1 - 12) OR jan,feb,mar,apr ...
# |  |  |  |  . day of week (0 - 6) (Sunday=0 or 7) OR 
sun,mon,tue,wed,thu,fri,sat
# |  |  |  |  |
# *  *  *  *  * user-name command to be executed
0,15,30,45 ** * *  root  /etc/init.d/weewx restart 
10,25,40,55 *   * * *  root wee_reports /etc/weewx/weewx.conf > /dev/null

Now, I get an update pushed to web by the wee_reports containing the 
archive interval data at 15 minutes.
Let me know if you see any issues with this method.

Also, I have been using "nmap -p 2 192.168.42.66" to test if the Davis 
VP2 is alive and have rarely found it offline. Statistics returned by nmap 
are interesting, sometimes the query takes a milliseconds longer than other 
times, but seldom is it down. I'm not sure why the weewx vantage driver 
3.2.1 fails on this new router, but at least there is a workaround.

Also, I've upgraded to Ubuntu 20.04  Focal hoping for help but no cigar.

Cheers,
John

On Tuesday, September 1, 2020 at 10:12:36 PM UTC-7 John S wrote:

> Weewx 4.1.1 running on ubuntu 18.04 with a Vantage PRO station.
>INFO __main__: Initializing weewx version 4.1.1
>Using Python 2.7.17 (default, Jul 20 2020, 15:37:01) #012[GCC 7.5.0]
>Platform Linux-4.15.0-112-generic-x86_64-with-Ubuntu-18.04-bionic
>weewx.drivers.vantage: Driver version is 3.2.1
>
> I waited for a long time for fiber to be installed in the neighborhood and 
> when it happened I knew there would be a few challenges due to the new 
> modem.
> I documented all my firewall settings from the old router and after a bit 
> of twiddling was able to punch in the right setup on the new SMART/RG 
> SR516ac for all my needs.
> Or so I thought, weewx would intermittently fail with a driver load error 
> *ERROR weewx.drivers.vantage: ip-read error: timed out*
> and 
> *ERROR weewx.drivers.vantage: LOOP try #4; error: Expected 99 characters; 
> got zero instead*
> and
> *ERROR weewx.drivers.vantage: Socket error while opening port 2 to 
> ethernet host 192.168.42.66.*
> * CRITICAL __main__: Unable to load driver: [Errno 113] No route to host*
>
> I had set that Vantage to a static IP address from the pool on the router.
> So I upgraded to 4.1.1 just to see if there was any advantage there. It 
> reacted pretty much the same, unpredictable disconnects which required a 
> restart.
> I rechecked my router setup, I had opened port 22 and so I added 2. 
> That helped a little bit but I was still getting dropped.
>
> I finally changed a couple of things in the weewx.conf:
> # How long to wait before timing out a socket (FTP, HTTP) connection
> # was 60
> socket_timeout = 360
> and
> # How long to wait for a response from the station before giving up (in
> # seconds; must be greater than 2) (was 10)
> timeout = 100
>
> With these two changes my setup doesn't lose its connection and keeps 
> trying to connect. I can see in the signal quality graphic on line that 
> there are some burps but it seems to recover well, currently up and running 
> over 8 days. I'm hopeful that this is it, and will continue to function 
> properly.
>
> I also hope this might help others who can't maintain a good connection to 
> their Vantage PRO. 
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2a8f6ff2-8b44-4dd1-9bee-b3272c598debn%40googlegroups.com.

Re: [weewx-user] Re: New Router, New Fiber and 4.1 Weewx

[weather list]

You don’t mention if you are connection to the Vantage via wi-fi (Meteobridge 
NANO or similar) or a TP-link 3020 (or similar) flashed with Metoebridge, or 
something else.

If you are using a Meteobridge NANO that relies on wi-fi, set your router to 
use a specific channel. I had these troubles for a long time until I did that, 
and it *seems* to have fixed it, so far.

Otherwise, give the Vantage a fixed IP tied to the MAC address of the 
connection to the Vantage.

> On 16 Nov, 2020, at 21:26, John S  wrote:
> 
> This didn't end as well as I thought it would. After running OK for a few 
> weeks, things went wonky again. I do not have a good idea of why, I did 
> upgrade to 4.2.0 but don't think that really had anything to do with it, in 
> fact, I was hoping it would fix the ip-read errors I'm seeing.
> The scenario is pretty much the same, the system chugs along well for a few 
> hours then I see either the ip-read error or a broken pipe error message and 
> the software doesn't recover nor does it finish its loops and publish data.
> But, I have another work around that is working fine for the last 24 hours. 
> While trouble shooting this, I noticed weewx will collect any old interval 
> data and store it in the db, this is normal behaviour. The ip-read error or 
> broken pipe error occurs later in the cycle.
> So, if I run weewx_reports /etc/weewx/weewx.conf, that will pick up all the 
> data and format the output then FTP it to my website. 
> I added a few lines to the crontab to do this for me:
> SHELL=/bin/sh
> PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
> 
> # Example of job definition:
> # . minute (0 - 59)
> # |  .- hour (0 - 23)
> # |  |  .-- day of month (1 - 31)
> # |  |  |  .--- month (1 - 12) OR jan,feb,mar,apr ...
> # |  |  |  |  . day of week (0 - 6) (Sunday=0 or 7) OR 
> sun,mon,tue,wed,thu,fri,sat
> # |  |  |  |  |
> # *  *  *  *  * user-name command to be executed
> 0,15,30,45 ** * *  root  /etc/init.d/weewx restart 
> 10,25,40,55 *   * * *  root wee_reports /etc/weewx/weewx.conf > /dev/null
> 
> Now, I get an update pushed to web by the wee_reports containing the archive 
> interval data at 15 minutes.
> Let me know if you see any issues with this method.
> 
> Also, I have been using "nmap -p 2 192.168.42.66" to test if the Davis 
> VP2 is alive and have rarely found it offline. Statistics returned by nmap 
> are interesting, sometimes the query takes a milliseconds longer than other 
> times, but seldom is it down. I'm not sure why the weewx vantage driver 3.2.1 
> fails on this new router, but at least there is a workaround.
> 
> Also, I've upgraded to Ubuntu 20.04  Focal hoping for help but no cigar.
> 
> Cheers,
> John
> 
> On Tuesday, September 1, 2020 at 10:12:36 PM UTC-7 John S wrote:
> Weewx 4.1.1 running on ubuntu 18.04 with a Vantage PRO station.
>INFO __main__: Initializing weewx version 4.1.1
>Using Python 2.7.17 (default, Jul 20 2020, 15:37:01) #012[GCC 7.5.0]
>Platform Linux-4.15.0-112-generic-x86_64-with-Ubuntu-18.04-bionic
>weewx.drivers.vantage: Driver version is 3.2.1
> 
> I waited for a long time for fiber to be installed in the neighborhood and 
> when it happened I knew there would be a few challenges due to the new modem.
> I documented all my firewall settings from the old router and after a bit of 
> twiddling was able to punch in the right setup on the new SMART/RG SR516ac 
> for all my needs.
> Or so I thought, weewx would intermittently fail with a driver load error 
> ERROR weewx.drivers.vantage: ip-read error: timed out
> and 
> ERROR weewx.drivers.vantage: LOOP try #4; error: Expected 99 characters; got 
> zero instead
> and
> ERROR weewx.drivers.vantage: Socket error while opening port 2 to 
> ethernet host 192.168.42.66.
>  CRITICAL __main__: Unable to load driver: [Errno 113] No route to host
> 
> I had set that Vantage to a static IP address from the pool on the router.
> So I upgraded to 4.1.1 just to see if there was any advantage there. It 
> reacted pretty much the same, unpredictable disconnects which required a 
> restart.
> I rechecked my router setup, I had opened port 22 and so I added 2. That 
> helped a little bit but I was still getting dropped.
> 
> I finally changed a couple of things in the weewx.conf:
> # How long to wait before timing out a socket (FTP, HTTP) connection
> # was 60
> socket_timeout = 360
> and
> # How long to wait for a response from the station before giving up (in
> # seconds; must be greater than 2) (was 10)
> timeout = 100
> 
> With these two changes my setup doesn't lose its connection and keeps trying 
> to connect. I can see in the signal quality graphic on line that there are 
> some burps but it seems to recover well, currently up and running over 8 
> days. I'm hopeful that this is it, and will continue to function properly.
> 
> I also hope this might help others who can't maintain a good connection to 

[weewx-user] Pi Trials and Errors

[John S]

Just a warning if you are considering putting a Pi online with an existing 
weewx system, it might not end well if there is competition for the dataset.

I have a Davis Vantage Pro 2 and I have been using an Ubuntu system to run 
weewx 4.2.0 via a Davis ethernet data interface. Reading in the weewx docs 
that running weewx along with other stuff on a PC can be problematic, and 
because my install is problematic, I decided to try getting a Pi 3 B up and 
running weewx. 

I went through the system install and configuration so weewx would run and 
update the mariadb on the Pi. If the Pi was able to update the db 
correctly, I figured that's half the battle. 

I glossed over the warnings about time on the Pi and didn't notice that the 
Pi was off by two hours vs my linux box. 

... until I started getting this in my log:
Nov 16 12:45:28  weewx[37812] WARNING weewx.engine: Ignore historical 
record: {'windGust': 11.0, 'barometer': 30.083, 'lowOutTemp': 61.2, 
'outHumidity': 61.0, 'interval': 15, 'forecastRule': 44, 'rain': 0.0, 
'dateTime': 1605560400, ...  'windGustDir': 135.0}

Due to this, the old weewx on linux wasn't happy and wasn't updating 
interval data, it was in the error state and not able to reset. 

I shut down the Pi but that didn't fix the issue so rebooted linux machine 
and that seemed to bring things back into sync, weewx is running and 
updating as before.\

I thought I'd share the fact that two instances of weewx hitting the same 
source hardware did cause things to lose their sync. I've nothing other 
than the log to point to the weewx driver setting the clock so if you have 
two systems with differing times, only one will win the prize.

So, it appears that you can bring a Pi online to run weewx, just don't 
expect it to share the hardware nicely.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/955cde79-c4a1-40dc-8a63-454f64ecad44n%40googlegroups.com.

[weewx-user] ignore_zero_wind not working in 4.2.0?

[Bill Arthur]

I have three pi's running weewx, two have been moved up to 4.2.0, one is 
still on 4.1.1. All have ignore_zero_wind set to False. The two that are on 
4.2.0 no longer work as expected (zero wind shows wind direction) but the 
4.1.1 still works as expected.

Did something happen in 4.2.0 that changed the behavior of ignore_zero_wind 
= False?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/52177b9a-3039-42f7-a402-8d98b296706cn%40googlegroups.com.

Re: [weewx-user] Signal Strength vs Rainfall

[Greg Sinclair]

My Acurite does not do well on lithium batteries. It seems to prefer long 
lasting alkaline batteries.

Signal strength was an issue for me for a while after switching from a Pi3 
to a Pizero and upgrading weewx. They were both attached directly to the 
Acurite's base station. I eventually solved the problem by changing the 
channel used between sensors and the base station. My thought is changing 
the Pi caused an interference problem.

Greg


On Monday, November 16, 2020 at 2:53:36 PM UTC-6 K1IW wrote:

> Yes, I should have mentioned the hardware.
>
> This is an Acurite 15036 which uses 433 MHz.  The batteries are brand new 
> lithium batteries installed 
> about one month ago.  The sensor is located in a rural area, in a summer 
> cottage 
> that is unoccupied, as are all the ones around except one house two doors 
> away.  
>
> I guess the good news is it seems to come back.  Hopefully it will make it 
> through the winter without
> needing any attention.
>
> Thanks,
> Bob
>
>
> On Mon, Nov 16, 2020 at 3:03 PM Greg Troxel  wrote:
>
>>
>> Bob DeMattia  writes:
>>
>> > Quite a bit of attenuation!   The sensor is located approximately 8 feet
>> > horizontally and fifteen feet vertically
>> > from the display.  It must be the wet roof!
>>
>> Not sure what you have for station hardware.  That graph suggests Davis
>> VP2 or Vue, and there I am pretty sure 'signal quality' is a recent
>> average of the fraction of packets successfully received vs what should
>> have been received.
>>
>> Assuming Davis:
>>
>> Davis at the 8'/15' should be very solid.  It's 915 MHz, and it is very
>> slow FH, AIUI one data packet on a frequency and a new frequency for the
>> next packet rotating among a set of 51 (US).  That protects against
>> narrowband interference.  So I am skeptical that this is just due to
>> increased path loss.
>>
>> I don't look at signal strength on my VP2 often, but I used to see a dip
>> from 100 to 98% occasionally, and the time pattern was suggestive of
>> some other transmitter, but I haven't figured it out.  But it was a
>> brief dip to 98%, not hours at 25%.  I just checked and last night with
>> the temp peak/rain event it was mostly 99.1/99.9% with an occasional
>> 97ish%.  I can perceive no patterns.  Console/sensor distance is
>> probably 20' horizontal, 10' vertical, so not so different.
>>
>> Therefore, I would be suspicious of broadband noise happening because of
>> the rain, although I admit that at 900 the level needed to explain this
>> does not make a lot of sense.  Speculating wildly and beyond the point
>> of reason, it could be arcing of a powerline insulator when wet.
>> Perhaps listen at 450 MHz during the next rain, or at 900 if you have an
>> SDR set up that can function as a spectrum analyzer (rtlsdr/gqrx?).
>>
>> You can also use rtldavis to listen to the packets:
>>
>>   https://github.com/lheijst/rtldavis
>>
>> with an RTL-SDR dongle.  That might be useful information.
>>
>> Greg
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a143f426-083e-49c0-a2fb-bbc2b547becdn%40googlegroups.com.

Re: [weewx-user] Re: New Router, New Fiber and 4.1 Weewx

[John S]

I'm using the ethernet dongle for this device, the one Davis just 
discontinued - WeatherLinkIP datalogger. (I just noticed that Davis has a 
firmware update for this but haven't installed it as I don't use their 
cloud services.)
I do have a static IP assigned to the IP logger mac - that works fine and 
is why I use nmap to test if it is alive.
Cheers!

On Monday, November 16, 2020 at 7:55:50 PM UTC-8 Dan'l B wrote:

> You don’t mention if you are connection to the Vantage via wi-fi 
> (Meteobridge NANO or similar) or a TP-link 3020 (or similar) flashed with 
> Metoebridge, or something else.
>
> If you are using a Meteobridge NANO that relies on wi-fi, set your router 
> to use a specific channel. I had these troubles for a long time until I did 
> that, and it *seems* to have fixed it, so far.
>
> Otherwise, give the Vantage a fixed IP tied to the MAC address of the 
> connection to the Vantage.
>
> On 16 Nov, 2020, at 21:26, John S  wrote:
>
> This didn't end as well as I thought it would. After running OK for a few 
> weeks, things went wonky again. I do not have a good idea of why, I did 
> upgrade to 4.2.0 but don't think that really had anything to do with it, in 
> fact, I was hoping it would fix the ip-read errors I'm seeing.
> The scenario is pretty much the same, the system chugs along well for a 
> few hours then I see either the ip-read error or a broken pipe error 
> message and the software doesn't recover nor does it finish its loops and 
> publish data.
> But, I have another work around that is working fine for the last 24 
> hours. While trouble shooting this, I noticed weewx will collect any old 
> interval data and store it in the db, this is normal behaviour. The ip-read 
> error or broken pipe error occurs later in the cycle.
> So, if I run weewx_reports /etc/weewx/weewx.conf, that will pick up all 
> the data and format the output then FTP it to my website. 
> I added a few lines to the crontab to do this for me:
> SHELL=/bin/sh
> PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
>
> # Example of job definition:
> # . minute (0 - 59)
> # |  .- hour (0 - 23)
> # |  |  .-- day of month (1 - 31)
> # |  |  |  .--- month (1 - 12) OR jan,feb,mar,apr ...
> # |  |  |  |  . day of week (0 - 6) (Sunday=0 or 7) OR 
> sun,mon,tue,wed,thu,fri,sat
> # |  |  |  |  |
> # *  *  *  *  * user-name command to be executed
> 0,15,30,45 ** * *  root  /etc/init.d/weewx restart 
> 10,25,40,55 *   * * *  root wee_reports /etc/weewx/weewx.conf > /dev/null
>
> Now, I get an update pushed to web by the wee_reports containing the 
> archive interval data at 15 minutes.
> Let me know if you see any issues with this method.
>
> Also, I have been using "nmap -p 2 192.168.42.66" to test if the Davis 
> VP2 is alive and have rarely found it offline. Statistics returned by nmap 
> are interesting, sometimes the query takes a milliseconds longer than other 
> times, but seldom is it down. I'm not sure why the weewx vantage driver 
> 3.2.1 fails on this new router, but at least there is a workaround.
>
> Also, I've upgraded to Ubuntu 20.04  Focal hoping for help but no cigar.
>
> Cheers,
> John
>
> On Tuesday, September 1, 2020 at 10:12:36 PM UTC-7 John S wrote:
>
>> Weewx 4.1.1 running on ubuntu 18.04 with a Vantage PRO station.
>>INFO __main__: Initializing weewx version 4.1.1
>>Using Python 2.7.17 (default, Jul 20 2020, 15:37:01) #012[GCC 7.5.0]
>>Platform Linux-4.15.0-112-generic-x86_64-with-Ubuntu-18.04-bionic
>>weewx.drivers.vantage: Driver version is 3.2.1
>>
>> I waited for a long time for fiber to be installed in the neighborhood 
>> and when it happened I knew there would be a few challenges due to the new 
>> modem.
>> I documented all my firewall settings from the old router and after a bit 
>> of twiddling was able to punch in the right setup on the new SMART/RG 
>> SR516ac for all my needs.
>> Or so I thought, weewx would intermittently fail with a driver load error
>>  
>> *ERROR weewx.drivers.vantage: ip-read error: timed out*
>> and 
>> *ERROR weewx.drivers.vantage: LOOP try #4; error: Expected 99 characters; 
>> got zero instead*
>> and
>> *ERROR weewx.drivers.vantage: Socket error while opening port 2 to 
>> ethernet host 192.168.42.66.*
>> * CRITICAL __main__: Unable to load driver: [Errno 113] No route to host*
>>
>> I had set that Vantage to a static IP address from the pool on the router.
>> So I upgraded to 4.1.1 just to see if there was any advantage there. It 
>> reacted pretty much the same, unpredictable disconnects which required a 
>> restart.
>> I rechecked my router setup, I had opened port 22 and so I added 2. 
>> That helped a little bit but I was still getting dropped.
>>
>> I finally changed a couple of things in the weewx.conf:
>> # How long to wait before timing out a socket (FTP, HTTP) connection
>> # was 60
>> socket_timeout = 360
>> and
>> # How long to wait for a response from the station

[weewx-user] Re: Pi Trials and Errors

[John S]

I see in the Davis trouble shooting guide 
(https://github.com/weewx/weewx/wiki/Troubleshooting-the-Davis-Vantage-station#corrupt-station-memory)
 
mention of clock skew, which is what happened above. I just found a new way 
of doing an old trick!

On Monday, November 16, 2020 at 8:15:19 PM UTC-8 John S wrote:

>
> Just a warning if you are considering putting a Pi online with an existing 
> weewx system, it might not end well if there is competition for the dataset.
>
> I have a Davis Vantage Pro 2 and I have been using an Ubuntu system to run 
> weewx 4.2.0 via a Davis ethernet data interface. Reading in the weewx docs 
> that running weewx along with other stuff on a PC can be problematic, and 
> because my install is problematic, I decided to try getting a Pi 3 B up and 
> running weewx. 
>
> I went through the system install and configuration so weewx would run and 
> update the mariadb on the Pi. If the Pi was able to update the db 
> correctly, I figured that's half the battle. 
>
> I glossed over the warnings about time on the Pi and didn't notice that 
> the Pi was off by two hours vs my linux box. 
>
> ... until I started getting this in my log:
> Nov 16 12:45:28  weewx[37812] WARNING weewx.engine: Ignore historical 
> record: {'windGust': 11.0, 'barometer': 30.083, 'lowOutTemp': 61.2, 
> 'outHumidity': 61.0, 'interval': 15, 'forecastRule': 44, 'rain': 0.0, 
> 'dateTime': 1605560400, ...  'windGustDir': 135.0}
>
> Due to this, the old weewx on linux wasn't happy and wasn't updating 
> interval data, it was in the error state and not able to reset. 
>
> I shut down the Pi but that didn't fix the issue so rebooted linux machine 
> and that seemed to bring things back into sync, weewx is running and 
> updating as before.\
>
> I thought I'd share the fact that two instances of weewx hitting the same 
> source hardware did cause things to lose their sync. I've nothing other 
> than the log to point to the weewx driver setting the clock so if you have 
> two systems with differing times, only one will win the prize.
>
> So, it appears that you can bring a Pi online to run weewx, just don't 
> expect it to share the hardware nicely.
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/454e4d3d-7fec-4475-9bab-fe51bc600534n%40googlegroups.com.

[weewx-user] Re: ignore_zero_wind not working in 4.2.0?

[gjr80]

Bill,

There was a change to the StdWXCalculate service in 4.2.0 that has 
inadvertently changed the operation of ignore_zero_wind. Normal (expected) 
operation should resume if you change the ignore_zero_wind setting to be 
the opposite of its current value (ie if under 4.1.1 or earlier you 
had ignore_zero_wind = False change it to ignore_zero_wind = True or if you 
had ignore_zero_wind = True change it to ignore_zero_wind = False).

If you don’t use ignore_zero_wind you are not affected by the change and 
need do nothing.

Gary

On Tuesday, 17 November 2020 at 14:20:55 UTC+10 wa4...@gmail.com wrote:

> I have three pi's running weewx, two have been moved up to 4.2.0, one is 
> still on 4.1.1. All have ignore_zero_wind set to False. The two that are on 
> 4.2.0 no longer work as expected (zero wind shows wind direction) but the 
> 4.1.1 still works as expected.
>
> Did something happen in 4.2.0 that changed the behavior of 
> ignore_zero_wind = False?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/32a55d26-bddb-4303-b559-232ff36e9cf0n%40googlegroups.com.

[weewx-user] Re: Errors in log related to imagestackedwindrose3

[gjr80]

Sean,

Looking at your testtags.php I can see you are running WeeWX v4.2.0 but due 
to an error in the testtags.php template I cannot tell what WeeWX-WD 
version you are running. Though given that imageStackedWindRose3.py was 
renamed to stackedwindrose.py in WeeWX-WD v2.0.0 I suspect you are running 
WeeWX-WD v1.x. WeeWX v1.x may work under WeeWX 4.x/python2 but I expect it 
will have issues under python3. I suggest you update WeeWX-WD to the the 
latest version, currently v2.1.2. Upgrading is fairly straightforward 
though there are a few manual steps involved. The upgrade instructions 
 are in the 
WeeWX-WD wiki.

Gary
On Saturday, 14 November 2020 at 07:44:55 UTC+10 itsup...@gmail.com wrote:

> I don't know exactly how long this has been happening as my logs only go 
> back so many days, but I was messing around with my weather station today, 
> and noticed this:
>
> ERROR weewx.reportengine: Caught unrecoverable exception in generator 
> 'user.imageStackedWindRose3.ImageStackedWindRoseGenerator'
> ERROR weewx.reportengine:   decoding Unicode is not supported
> ERROR weewx.reportengine:   Traceback (most recent call last):
> ERROR weewx.reportengine: File 
> "/usr/share/weewx/weewx/reportengine.py", line 196, in run
> ERROR weewx.reportengine:   obj.start()
> ERROR weewx.reportengine: File 
> "/usr/share/weewx/weewx/reportengine.py", line 281, in start
> ERROR weewx.reportengine:   self.run()
> ERROR weewx.reportengine: File 
> "/usr/share/weewx/user/imageStackedWindRose3.py", line 75, in run
> ERROR weewx.reportengine:   self.genImages(self.gen_ts)
> ERROR weewx.reportengine: File 
> "/usr/share/weewx/user/imageStackedWindRose3.py", line 196, in genImages
> ERROR weewx.reportengine:   self.label = unicode(label, 
> 'utf8')
> ERROR weewx.reportengine:   TypeError: decoding Unicode is not 
> supported
> ERROR weewx.reportengine:   Generator terminated
>
>
> I thought maybe it was due to the update I did today, but goes back 
> further.  I don't really know or can't see if something is broken on my 
> site either.  
> https://weather.lavacrawlers.com
>
> Thanks!
> Sean
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/99d7b20f-ca96-40e8-9059-dd7d7062b25cn%40googlegroups.com.

Re: [weewx-user] luftdaten.info - sensor.community air quality data to weewx

[misk...@gmail.com]

thanks for guiding me!

1. I am able to install weewx-sds011, but i am not able to repeat all your 
steps.
2. how can i rsync data? just throught API in the web interface of 
luftdaten sensor?

3. how filepile works? it saves data to a plain text document? 
filename = /var/tmp/pond.txt
Or are you able to store it in the  new SDB database?

4. I will be probably able to create .tmpl and integrate it to my webpage. 
Only how the $parameters and formating looks like is the question

thanks for your help!

btw, my webpage: http://jastrabie.online/weewx/
 
Dátum: pondelok 16. novembra 2020, čas: 9:41:36 UTC+1, odosielateľ: 
steep...@gmail.com

> Google weewx-sds011. There is an extension for that sensor. 
>
> In my case I rsync data to my main server and then use weewx-filepile 
> extension to insert data into the new extended database. I then use a 
> custom .tmpl to aggregate the data for a rolling 24hr AQI.
>
> Ian
>
> On Sun, 15 Nov 2020 at 20:46, misk...@gmail.com  wrote:
>
>> Hello,
>> has anybody integrated the air quality API to WeeWX?
>>
>> It should be probably something easy, as the sensor firmware has API with 
>> custom server, path, port, username/password to entry.
>>
>> or there is also api for sensor.community service
>>
>> https://sensor.community/
>> https://opensensemap.org/
>>
>> thanks for info,
>> Michal, SVK
>>
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/0171755b-7bd6-49f8-bc18-39261c278466n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3f5f192a-541f-4918-ab85-1f91c612c429n%40googlegroups.com.

[weewx-user] Re: wee_import from Weather underground twice a day

[gjr80]

Hi,

There is presently no support in wee_import for 
suppressing/bypassing/automatically answering the y/n prompt in wee_import, 
we never envisioned wee_import being used in that manner. Implementing 
something like the --no-prompt command line option in wee_config should be 
possible and fairly straightforward to add. Let me do some homework.

Gary
On Monday, 16 November 2020 at 01:11:16 UTC+10 sc.lep...@gmail.com wrote:

> For the first question  I ve my own answer  : 
> 2 scripts bash 
>
> *For night and morning  : *
> #!/bin/bash  
> date_debut_jour_heure=`date +"%Y-%m-%dT00:00"` ;
> date_fin_jour_heure=`date +"%Y-%m-%dT12:00"` ;
>
> echo $date_debut_jour_heure;
> echo $date_fin_jour_heure;
>
> /home/pi/weewx-4.2.0/bin/wee_import --config=/home/weewx/FROGGIT.conf 
> --import-config=/home/weewx/wu-FROGGIT.conf --from=$date_debut_jour_heure 
> --to=$date_fin_jour_heure --dry-run
>
>
> *For afternoon and evening  : *
>
> #!/bin/bash
> date_debut_jour_heure=`date +"%Y-%m-%dT12:00"` ;
> date_fin_jour_heure=`date +"%Y-%m-%dT23:59"` ;
>
> echo $date_debut_jour_heure;
> echo $date_fin_jour_heure;
>
> /home/pi/weewx-4.2.0/bin/wee_import --config=/home/weewx/FROGGIT.conf 
> --import-config=/home/weewx/wu-FROGGIT.conf --from=$date_debut_jour_heure 
> --to=$date_fin_jour_heure --dry-run
>
>
>
> But how to suppress Y/N answer ? 
>
> thanks
>
> Le dimanche 15 novembre 2020 à 15:08:24 UTC+1, sc.lep...@gmail.com a 
> écrit :
>
>> Hello
>> I want to import twice a day ( for example 12h00 and  00h00) my data from 
>> Weather Underground.
>>
>> I want to write a script shell  to put it in a crontab.
>>
>> first question :
>>  I use this  : 
>> wee_import --config=/home/weewx/FROGGIT.conf 
>> --import-config=/home/weewx/wu-FROGGIT.conf --date=2020-11-14
>>
>> For midday  : .- -date is it possible to put - - date 
>> =2020-11-14T12:00 ?
>> For midnight : .- - from=2020-11-14T12:00   - -to=2020-11-14:23:59
>>
>>
>> Snd question  : I must answer by "y" to proceed  import , is is possible 
>> to overwrite this ?
>>
>> And if you want to see results , it 's here  :
>> https://meteo-pontscorff.fr/station-froggit-template-belchertown/
>>
>> Thanks a lot , best regards  
>> Stephane 
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/93bfab88-6eb4-4788-a8b9-1fa4c3221a57n%40googlegroups.com.