Re: [weewx-user] Wunderground reporting "missing wind data"

[Paul Weber]

Thanks that did it :D  I had it below in the section with "perfer_hardware" 
etc.  Much appreciated 

On Wednesday, November 16, 2016 at 10:12:43 PM UTC+1, Tom Keffer wrote:
>
> It should look something like this when you're done.
>
> [StdWXCalculate]
>
> ignore_zero_wind = false
>
> [[Calculations]]
> # Derived quantities are calculated by this service. Possible values 
> are:
> #  hardware- use the value provided by hardware
> #  software- use the value calculated by weewx
> #  prefer_hardware - use value provide by hardware if available,
> #  otherwise use value calculated by weewx
> 
> pressure = prefer_hardware
> barometer = prefer_hardware
> altimeter = prefer_hardware
> windchill = prefer_hardware
> heatindex = prefer_hardware
> dewpoint = prefer_hardware
> inDewpoint = prefer_hardware
> rainRate = prefer_hardware
>
>
> If that doesn't solve the problem, then we need to see more of the log. 
> You only included one second's worth. We need at least an archive period 
> (generally 5 to 10 minutes).
>
> -tk
>
> On Wed, Nov 16, 2016 at 12:01 PM, Paul Weber  > wrote:
>
>> Not sure if this is what you want.  I did notice however that my insert 
>> of "ignore_zero_wind" is at the beginning of the list and not at the end so 
>> may 
>> be getting canceled?  Anyway if this is not what you want let me know.  
>> Thanks for your help.
>>
>>
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service weewx.engine
>> .StdTimeSynch
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>> weewx.engine.StdTimeSynch
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service weewx.engine
>> .StdConvert
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: StdConvert target unit is 
>> 0x1
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>> weewx.engine.StdConvert
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service weewx.engine
>> .StdCalibrate
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>> weewx.engine.StdCalibrate
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service weewx.engine
>> .StdQC
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>> weewx.engine.StdQC
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
>> weewx.wxservices.StdWXCalculate
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: wxcalculate: The following values 
>> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
>> dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=hardware, 
>> windrun=prefer_hardware, heatindex=prefer_hardware, 
>> maxSolarRad=prefer_hardware, humidex=prefer_hardware, 
>> pressure=prefer_hardware, inDewpoint=prefer_hardware, ET=prefer_hardware, 
>> altimeter=prefer_hardware, cloudbase=prefer_hardware
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: wxcalculate: The following 
>> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>> weewx.wxservices.StdWXCalculate
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
>> weewx.engine.StdArchive
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Archive will use data 
>> binding wx_binding
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Record generation will be 
>> attempted in 'hardware'
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Using archive interval of 
>> 300 seconds (specified in weewx configuration)
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Use LOOP data in hi/low 
>> calculations: 1
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Using binding 'wx_binding' 
>> to database 'weewx.sdb'
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: manager: Starting backfill of daily 
>> summaries
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: manager: Daily summaries up to date
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>> weewx.engine.StdArchive
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
>> weewx.restx.StdStationRegistry
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: StationRegistry: Station will 
>> not be registered: no station_url specified.
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>> weewx.restx.StdStationRegistry
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
>> weewx.restx.StdWunderground
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: Wunderground-PWS: Data for 
>> station ILOGONEO2 will be posted
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>> weewx.restx.StdWunderground
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
>> weewx.restx.StdPWSweather
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: PWSweather: Posting not 
>> enabled.
>> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
>> weewx.restx.StdPWSweather
>> Nov 16 20:30:50 Mobil-1

[weewx-user] Re: UV data not reporting in Standard skin

[mwall]

sam,

the database field names are case sensitive.

the default mapping for the oregon scientific lw30x is UV = uvh.?:*.*

which version of the driver are you using?

did you define your own sensor map?

m

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

[weewx-user] Re: Interceptor using bridge new Accurate firmware

[Jerome Helbert]

port 80 basically implies http, so that extra bit ought to be pretty 
redundant...

On Wednesday, November 16, 2016 at 8:20:16 PM UTC-6, Radar wrote:
>
> looks like its not going to die again, the only things i can find are 
> changed the 
>
> pcap_filter = "src 192.168.2.14 and dst port 80"
> to
> pcap_filter = "src 192.168.2.14 and dst port 80 and http"
>
> and don't know if this had any thing to do with but the bridge was asking 
> dhcpd for a new address and it shouldn't have been i found 3 times in a 
> quick glance at the log
> and i have it set to 1 day lease it was like the bridge was rebooting
>
> On Tuesday, November 15, 2016 at 6:21:43 PM UTC-6, Radar wrote:
>>
>> interceptor v0.7a it's been running for 23 hours now
>>
>> On Monday, November 14, 2016 at 10:47:16 AM UTC-6, mwall wrote:
>>>
>>> radar,
>>>
>>> could you try interceptor v0.7a (commit 5d0fe66)
>>>
>>> this logs more details about what is actually being parsed from the pcap 
>>> sniffs
>>>
>>> m
>>>
>>

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

[weewx-user] Re: UV data not reporting in Standard skin

[Sam Roza]

Packets from syslog:

~~~
ov 16 18:55:01 raspberrypi weewx[3492]: interceptor: ServerThread: POST: 
mac=0004a369e0d6&id=8e&rid=63&pwr=0&or=0&uvh=0&uv=365&ch=1&p=1
Nov 16 18:55:01 raspberrypi weewx[3492]: interceptor: MainThread: raw data: 
mac=0004a369e0d6&id=8e&rid=63&pwr=0&or=0&uvh=0&uv=365&ch=1&p=1
Nov 16 18:55:01 raspberrypi weewx[3492]: interceptor: MainThread: raw 
packet: {'uvh.163.0004a369e0d6': '0', 'ch.163.0004a369e0d6': '1', 
'pwr.163.0004a369e0d6': '0', 'p.163.0004a369e0d6': '1', 
'uv.163.0004a369e0d6': 365.0, 'dateTime': 1479351301, 
'mac.163.0004a369e0d6': '0004a369e0d6', 'id.163.0004a369e0d6': '8e', 
'rid.163.0004a369e0d6': '63', 'or.163.0004a369e0d6': '0', 'usUnits': 17}
Nov 16 18:55:01 raspberrypi weewx[3492]: interceptor: MainThread: mapped 
packet: {'uv': 365.0, 'usUnits': 17, 'dateTime': 1479351301}
~~~

>From skin.conf:

~~~
[[[dayuv]]]
yscale = 0, 16, 1
UV
UV_max
data_type = UV
aggregate_type = max
aggregate_interval = 3600
~~~

data_type is 'UV' and the mapped packet is 'uv'. Maybe that's the issue?

Will wait for others' assistance.

-SR


On Wednesday, November 16, 2016 at 6:54:29 PM UTC-8, Sam Roza wrote:
>
> Hello All,
>
> I have weewx 3.6.2 running. All is well, but I don't seem to have graphs 
> produced for UV data collected. Is there something that needs to be done? I 
> see the if statements in the skin.conf, and the data is collected by the 
> interceptor ( I can see the collected packets in syslog).
>
> Thanks!
>

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

[weewx-user] UV data not reporting in Standard skin

[Sam Roza]

Hello All,

I have weewx 3.6.2 running. All is well, but I don't seem to have graphs 
produced for UV data collected. Is there something that needs to be done? I 
see the if statements in the skin.conf, and the data is collected by the 
interceptor ( I can see the collected packets in syslog).

Thanks!

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

[weewx-user] Re: Interceptor using bridge new Accurate firmware

[Radar]

looks like its not going to die again, the only things i can find are 
changed the 

pcap_filter = "src 192.168.2.14 and dst port 80"
to
pcap_filter = "src 192.168.2.14 and dst port 80 and http"

and don't know if this had any thing to do with but the bridge was asking 
dhcpd for a new address and it shouldn't have been i found 3 times in a 
quick glance at the log
and i have it set to 1 day lease it was like the bridge was rebooting

On Tuesday, November 15, 2016 at 6:21:43 PM UTC-6, Radar wrote:
>
> interceptor v0.7a it's been running for 23 hours now
>
> On Monday, November 14, 2016 at 10:47:16 AM UTC-6, mwall wrote:
>>
>> radar,
>>
>> could you try interceptor v0.7a (commit 5d0fe66)
>>
>> this logs more details about what is actually being parsed from the pcap 
>> sniffs
>>
>> m
>>
>

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

[weewx-user] Re: Interceptor KeyError: 'dateTime'

[Pat Hayes]

So far, so good! Thank you, MWall!

Nov 16 19:59:30 weewx weewx[12887]: interceptor: MainThread: skipping rain 
measurement of 0.0: no last rain
Nov 16 20:00:26 weewx weewx[12887]: manager: added record 2016-11-16 
20:00:00 EST (1479344400) to database 'weewx.sdb'
Nov 16 20:00:26 weewx weewx[12887]: manager: added record 2016-11-16 
20:00:00 EST (1479344400) to daily summary in 'weewx.sdb'
Nov 16 20:00:27 weewx weewx[12887]: interceptor: MainThread: parse failed 
for 
dateutc=now&action=updateraw&realtime=1&windspeedmph=0.0&rainin=0.00&baromin=30.050&dewptf=36.9&dateutc=2016-11-17%2001%3A00%3A00
 
HTTP/1.1&rainin=0.00&baromin=30.050&dewptf=36.9&dateutc=2016-11-17%2001%3A00%3A00
 
HTTP/1.1&baromin=30.050&dewptf=36.9&dateutc=2016-11-17%2001%3A00%3A00 
HTTP/1.1: unconverted data remains:  HTTP/1.1
Nov 16 20:00:27 weewx weewx[12887]: restx: Wunderground-PWS: Published 
record 2016-11-16 20:00:00 EST (1479344400)
Nov 16 20:00:27 weewx weewx[12887]: cheetahgenerator: Generated 14 files 
for report StandardReport in 0.66 seconds
Nov 16 20:00:28 weewx weewx[12887]: genimages: Generated 24 images for 
StandardReport in 0.36 seconds
Nov 16 20:00:28 weewx weewx[12887]: reportengine: copied 9 files to 
/var/www/html/weewx
Nov 16 20:00:52 weewx weewx[12887]: restx: StationRegistry: Published 
record 2016-11-16 20:00:00 EST (1479344400)
Nov 16 20:01:01 weewx systemd: Started Session 129 of user root.
Nov 16 20:01:01 weewx systemd: Starting Session 129 of user root.
Nov 16 20:05:26 weewx weewx[12887]: manager: added record 2016-11-16 
20:05:00 EST (1479344700) to database 'weewx.sdb'
Nov 16 20:05:26 weewx weewx[12887]: manager: added record 2016-11-16 
20:05:00 EST (1479344700) to daily summary in 'weewx.sdb'
Nov 16 20:05:27 weewx weewx[12887]: cheetahgenerator: Generated 14 files 
for report StandardReport in 0.21 seconds
Nov 16 20:05:27 weewx weewx[12887]: interceptor: MainThread: parse failed 
for 
dateutc=now&action=updateraw&realtime=1&windspeedmph=0.5&rainin=0.00&baromin=30.056&dewptf=36.9&dateutc=2016-11-17%2001%3A05%3A00
 
HTTP/1.1&rainin=0.00&baromin=30.056&dewptf=36.9&dateutc=2016-11-17%2001%3A05%3A00
 
HTTP/1.1&baromin=30.056&dewptf=36.9&dateutc=2016-11-17%2001%3A05%3A00 
HTTP/1.1: unconverted data remains:  HTTP/1.1
Nov 16 20:05:27 weewx weewx[12887]: genimages: Generated 12 images for 
StandardReport in 0.09 seconds
Nov 16 20:05:27 weewx weewx[12887]: reportengine: copied 0 files to 
/var/www/html/weewx
Nov 16 20:05:27 weewx weewx[12887]: restx: Wunderground-PWS: Published 
record 2016-11-16 20:05:00 EST (1479344700)



On Wednesday, November 16, 2016 at 7:51:22 PM UTC-5, mwall wrote:
>
> pat,
>
> please try the latest interceptor v0.17b (commit 3c54744)
>
> it will now handle escaped colons, and if it encounters an unknown format 
> it will log it without exiting.
>
> m
>

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

[weewx-user] Re: Interceptor KeyError: 'dateTime'

[mwall]

pat,

please try the latest interceptor v0.17b (commit 3c54744)

it will now handle escaped colons, and if it encounters an unknown format 
it will log it without exiting.

m

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

[weewx-user] Re: Interceptor KeyError: 'dateTime'

[mwall]

On Wednesday, November 16, 2016 at 7:20:32 PM UTC-5, Pat Hayes wrote:
>
> Oh, BTW. Here is how I'm getting the data into the interceptor.
>
> tcpflow -C -i ens19 -s tcp dst port 80 | /root/combine-lines.pl | xargs -n 
> 1 curl http://192.168.1.42: -s -d
>
>
hard to say for certain without seeing debug log, but it looks like you're 
capturing http traffic other than that originating from the bridge.  a 
simple GET / will result in an empty packet, i.e., no dateTime.

try updating to the latest version of the interceptor - it should reject 
packets that have no dateTime.

also, you can prevent empty packets by being more restrictive with the pcap 
filter.  instead of

tcp dst port 80

try:

src host x.x.x.x and dst port 80

that will capture only traffic coming from the bridge.

m

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

[weewx-user] Re: Interceptor KeyError: 'dateTime'

[Pat Hayes]

Oh, BTW. Here is how I'm getting the data into the interceptor.

tcpflow -C -i ens19 -s tcp dst port 80 | /root/combine-lines.pl | xargs -n 1 
curl http://192.168.1.42: -s -d


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

[weewx-user] Interceptor KeyError: 'dateTime'

[Pat Hayes]

Hey guys,

Everything was running smoothly. I changed my weewx config to report to 
Wunderground and disabled Acurite from reporting. Then, the interceptor 
started shutting weewx down. I thought I was something about this before, 
but couldn't locate it.

Logs:

Nov 16 19:00:26 weewx weewx[12270]: manager: added record 2016-11-16 
19:00:00 EST (1479340800) to database 'weewx.sdb'
Nov 16 19:00:26 weewx weewx[12270]: manager: added record 2016-11-16 
19:00:00 EST (1479340800) to daily summary in 'weewx.sdb'
Nov 16 19:00:27 weewx weewx[12270]: interceptor: MainThread: parse failed 
for 
dateutc=now&action=updateraw&realtime=1&windspeedmph=0.4&rainin=0.00&baromin=30.030&dewptf=38.4&dateutc=2016-11-17%2000%3A00%3A00
 
HTTP/1.1&rainin=0.00&baromin=30.030&dewptf=38.4&dateutc=2016-11-17%2000%3A00%3A00
 
HTTP/1.1&baromin=30.030&dewptf=38.4&dateutc=2016-11-17%2000%3A00%3A00 
HTTP/1.1: time data '2016-11-17 00%3A00%3A00 HTTP/1.1' does not match 
format '%Y-%m-%d %H:%M:%S'
Nov 16 19:00:27 weewx weewx[12270]: engine: Shutting down StdReport thread
Nov 16 19:00:27 weewx weewx[12270]: cheetahgenerator: Generated 14 files 
for report StandardReport in 0.21 seconds
Nov 16 19:00:27 weewx weewx[12270]: restx: Wunderground-PWS: Published 
record 2016-11-16 19:00:00 EST (1479340800)
Nov 16 19:00:27 weewx weewx[12270]: genimages: Generated 24 images for 
StandardReport in 0.36 seconds
Nov 16 19:00:27 weewx weewx[12270]: reportengine: copied 0 files to 
/var/www/html/weewx
Nov 16 19:00:37 weewx weewx[12270]: restx: StationRegistry: Published 
record 2016-11-16 19:00:00 EST (1479340800)
Nov 16 19:00:37 weewx weewx[12270]: interceptor: MainThread: shutting down 
server thread
Nov 16 19:00:37 weewx weewx[12270]: engine: Caught unrecoverable exception 
in engine:
Nov 16 19:00:37 weewx weewx[12270]:  'dateTime'
Nov 16 19:00:37 weewx weewx[12270]:  Traceback (most recent call 
last):
Nov 16 19:00:37 weewx weewx[12270]:File 
"/usr/share/weewx/weewx/engine.py", line 844, in main
Nov 16 19:00:37 weewx weewx[12270]:  engine.run()
Nov 16 19:00:37 weewx weewx[12270]:File 
"/usr/share/weewx/weewx/engine.py", line 186, in run
Nov 16 19:00:37 weewx weewx[12270]:  for packet in 
self.console.genLoopPackets():
Nov 16 19:00:37 weewx weewx[12270]:File 
"/usr/share/weewx/user/interceptor.py", line 1859, in genLoopPackets
Nov 16 19:00:37 weewx weewx[12270]:  pkt = 
self._device.parser.parse(data)
Nov 16 19:00:37 weewx weewx[12270]:File 
"/usr/share/weewx/user/interceptor.py", line 623, in parse
Nov 16 19:00:37 weewx weewx[12270]:  pkt = self.parse_wu(s)
Nov 16 19:00:37 weewx weewx[12270]:File 
"/usr/share/weewx/user/interceptor.py", line 661, in parse_wu
Nov 16 19:00:37 weewx weewx[12270]:  return 
self.add_identifiers(pkt)
Nov 16 19:00:37 weewx weewx[12270]:File 
"/usr/share/weewx/user/interceptor.py", line 719, in add_identifiers
Nov 16 19:00:37 weewx weewx[12270]:  packet = {'dateTime': 
pkt['dateTime'], 'usUnits': pkt['usUnits']}
Nov 16 19:00:37 weewx weewx[12270]:  KeyError: 'dateTime'
Nov 16 19:00:37 weewx weewx[12270]:  Exiting.


Running the latest version of the interceptor.

Thanks,
Pat

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

Re: [weewx-user] archive_delay in version 3.6.2

[Thomas Keffer]

It is still supported (and documented), just no longer included in the
distribution weewx.conf file. It's an obscure setting that most users would
have no reason to mess with. Trying to simplify an already complicated
configuration file!

-tk

On Wed, Nov 16, 2016 at 2:52 PM, Tony Colley  wrote:

> When updating from 3.6.1 to 3.6.2, I noticed that the new weewx.conf no
> longer has the archive_delay setting (in StdArchive). I don't recall
> specifically adding this to my weewx.conf, but my memory is unreliable.
>
> Is archive_delay no longer supported?
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[weewx-user] archive_delay in version 3.6.2

[Tony Colley]

When updating from 3.6.1 to 3.6.2, I noticed that the new weewx.conf no 
longer has the archive_delay setting (in StdArchive). I don't recall 
specifically adding this to my weewx.conf, but my memory is unreliable.

Is archive_delay no longer supported?

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

Re: [weewx-user] Upgrade to 3.6.2 fails on loop problem (VP2)

[bgrattan]

Tom,

I'm using the Davis streaming data logger (6450) with serial output to a 
serial-->usb converter (PL2303) on ttyUSB0. This worked well with wview for 
about seven years until I moved to weewx almost two years ago. With weewx I saw 
the loop problem and found the solution suggested by someone on the web who was 
feeding weewx data to a ham radio setup with APRS. Davis makes another logger 
(non streaming, I think) which may not have this problem.
I'll run the debug log for you sometime this weekend. Thanks.

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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Wunderground reporting "missing wind data"

[Thomas Keffer]

It should look something like this when you're done.

[StdWXCalculate]

ignore_zero_wind = false

[[Calculations]]
# Derived quantities are calculated by this service. Possible values
are:
#  hardware- use the value provided by hardware
#  software- use the value calculated by weewx
#  prefer_hardware - use value provide by hardware if available,
#  otherwise use value calculated by weewx

pressure = prefer_hardware
barometer = prefer_hardware
altimeter = prefer_hardware
windchill = prefer_hardware
heatindex = prefer_hardware
dewpoint = prefer_hardware
inDewpoint = prefer_hardware
rainRate = prefer_hardware


If that doesn't solve the problem, then we need to see more of the log. You
only included one second's worth. We need at least an archive period
(generally 5 to 10 minutes).

-tk

On Wed, Nov 16, 2016 at 12:01 PM, Paul Weber  wrote:

> Not sure if this is what you want.  I did notice however that my insert
> of "ignore_zero_wind" is at the beginning of the list and not at the end so 
> may
> be getting canceled?  Anyway if this is not what you want let me know.
> Thanks for your help.
>
>
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service weewx.engine.
> StdTimeSynch
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service
> weewx.engine.StdTimeSynch
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service weewx.engine.
> StdConvert
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: StdConvert target unit is 0x1
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service
> weewx.engine.StdConvert
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service weewx.engine.
> StdCalibrate
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service
> weewx.engine.StdCalibrate
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service weewx.engine.
> StdQC
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service
> weewx.engine.StdQC
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service
> weewx.wxservices.StdWXCalculate
> Nov 16 20:30:50 Mobil-1 weewx[8411]: wxcalculate: The following values
> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware,
> dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=hardware,
> windrun=prefer_hardware, heatindex=prefer_hardware,
> maxSolarRad=prefer_hardware, humidex=prefer_hardware,
> pressure=prefer_hardware, inDewpoint=prefer_hardware, ET=prefer_hardware,
> altimeter=prefer_hardware, cloudbase=prefer_hardware
> Nov 16 20:30:50 Mobil-1 weewx[8411]: wxcalculate: The following algorithms
> will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service
> weewx.wxservices.StdWXCalculate
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service
> weewx.engine.StdArchive
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Archive will use data binding
> wx_binding
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Record generation will be
> attempted in 'hardware'
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Using archive interval of 300
> seconds (specified in weewx configuration)
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Use LOOP data in hi/low
> calculations: 1
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Using binding 'wx_binding' to
> database 'weewx.sdb'
> Nov 16 20:30:50 Mobil-1 weewx[8411]: manager: Starting backfill of daily
> summaries
> Nov 16 20:30:50 Mobil-1 weewx[8411]: manager: Daily summaries up to date
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service
> weewx.engine.StdArchive
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service
> weewx.restx.StdStationRegistry
> Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: StationRegistry: Station will
> not be registered: no station_url specified.
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service
> weewx.restx.StdStationRegistry
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service
> weewx.restx.StdWunderground
> Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: Wunderground-PWS: Data for
> station ILOGONEO2 will be posted
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service
> weewx.restx.StdWunderground
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service
> weewx.restx.StdPWSweather
> Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: PWSweather: Posting not
> enabled.
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service
> weewx.restx.StdPWSweather
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service
> weewx.restx.StdCWOP
> Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: CWOP: Posting not enabled.
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service
> weewx.restx.StdCWOP
> Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service
> weewx.restx.StdWOW
> Nov 16 20:30:50 Mobil-1 weewx[8411]: re

Re: [weewx-user] Wunderground reporting "missing wind data"

[Paul Weber]

Not sure if this is what you want.  I did notice however that my insert 
of "ignore_zero_wind" is at the beginning of the list and not at the end so 
may be getting canceled?  Anyway if this is not what you want let me know. 
 Thanks for your help.


Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
weewx.engine.StdTimeSynch
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
weewx.engine.StdConvert
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: StdConvert target unit is 0x1
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
weewx.engine.StdConvert
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
weewx.engine.StdCalibrate
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
weewx.engine.StdCalibrate
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
weewx.engine.StdQC
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
weewx.engine.StdQC
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Nov 16 20:30:50 Mobil-1 weewx[8411]: wxcalculate: The following values will 
be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=hardware, 
windrun=prefer_hardware, heatindex=prefer_hardware, 
maxSolarRad=prefer_hardware, humidex=prefer_hardware, 
pressure=prefer_hardware, inDewpoint=prefer_hardware, ET=prefer_hardware, 
altimeter=prefer_hardware, cloudbase=prefer_hardware
Nov 16 20:30:50 Mobil-1 weewx[8411]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
weewx.engine.StdArchive
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Archive will use data binding 
wx_binding
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Record generation will be 
attempted in 'hardware'
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Using archive interval of 300 
seconds (specified in weewx configuration)
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Use LOOP data in hi/low 
calculations: 1
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Using binding 'wx_binding' to 
database 'weewx.sdb'
Nov 16 20:30:50 Mobil-1 weewx[8411]: manager: Starting backfill of daily 
summaries
Nov 16 20:30:50 Mobil-1 weewx[8411]: manager: Daily summaries up to date
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
weewx.engine.StdArchive
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
weewx.restx.StdStationRegistry
Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: StationRegistry: Station will 
not be registered: no station_url specified.
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
weewx.restx.StdStationRegistry
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
weewx.restx.StdWunderground
Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: Wunderground-PWS: Data for 
station ILOGONEO2 will be posted
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
weewx.restx.StdWunderground
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
weewx.restx.StdPWSweather
Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: PWSweather: Posting not enabled.
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
weewx.restx.StdPWSweather
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
weewx.restx.StdCWOP
Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: CWOP: Posting not enabled.
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
weewx.restx.StdCWOP
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
weewx.restx.StdWOW
Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: WOW: Posting not enabled.
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
weewx.restx.StdWOW
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
weewx.restx.StdAWEKAS
Nov 16 20:30:50 Mobil-1 weewx[8411]: restx: AWEKAS: Posting not enabled.
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
weewx.restx.StdAWEKAS
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
weewx.engine.StdPrint
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
weewx.engine.StdPrint
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Loading service 
weewx.engine.StdReport
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Finished loading service 
weewx.engine.StdReport
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Starting up weewx version 3.6.2
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Station does not support 
reading the time
Nov 16 20:30:50 Mobil-1 weewx[8411]: engine: Starting main packet loop.

On Wednesday, November 16, 2016 at 4:28:51 PM UTC+1, Tom Keffer wrote:
>
> ​Edit weewx.conf, setting debug=1, then restart weewx. Post th

Re: [weewx-user] Upgrade to 3.6.2 fails on loop problem (VP2)

[Thomas Keffer]

I would still like to see the log without your modifications to vantage.py.
I would like to see why it can't handle 200 LOOP packets at a time. Set
debug=1, then restart, with the original vantage.py.

What kind of logger do you have? The stock Davis serial logger? Is it
connected using a serial-to-usb converter? Or, to a real serial port?

-tk

On Wed, Nov 16, 2016 at 9:37 AM,  wrote:

> SOLVED!
>
> Thanks for the quick reply, Tom. My own stupid mistake. In rechecking
> everything, I found that my edit of vantage.py didn't take. Once the 200
> was actually changed to 2 then all worked well.
> Much appreciated for the great software and all who contribute!
>
> Bob
>
> http://grattans.org/wx
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [weewx-user] Upgrade to 3.6.2 fails on loop problem (VP2)

[bgrattan]

SOLVED!

Thanks for the quick reply, Tom. My own stupid mistake. In rechecking 
everything, I found that my edit of vantage.py didn't take. Once the 200 
was actually changed to 2 then all worked well.
Much appreciated for the great software and all who contribute!

Bob

http://grattans.org/wx


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

Re: [weewx-user] Upgrade to 3.6.2 fails on loop problem (VP2)

[Thomas Keffer]

Hello, Bob

Make sure there isn't a second weewx process running

ps aux | grep weewx

If that doesn't work, set debug=1, stop weewx, start weewx, wait a couple
minutes, send the log from startup.

-tk

On Wed, Nov 16, 2016 at 9:14 AM,  wrote:

> Hello,
>
> After running 3.5.0 with no problems (VP2+{serial} on Debian Jessie), I am
> getting the following loop error:
>
> root@n4mrv:/home/weewx# service weewx status
> ● weewx.service - LSB: weewx weather system
>Loaded: loaded (/etc/init.d/weewx)
>Active: active (running) since Wed 2016-11-16 11:54:58 EST; 3min 12s ago
>   Process: 4553 ExecStop=/etc/init.d/weewx stop (code=exited,
> status=0/SUCCESS)
>   Process: 4611 ExecStart=/etc/init.d/weewx start (code=exited,
> status=0/SUCCESS)
>CGroup: /system.slice/weewx.service
>└─4624 /usr/bin/python /home/weewx/bin/weewxd --daemon
> --pidfile=/var/run/weewx.pid /home/weewx/weewx.conf
>
> Nov 16 11:56:38 n4mrv weewx[4624]: engine: Starting up weewx version 3.6.2
> Nov 16 11:56:38 n4mrv weewx[4624]: engine: Clock error is -0.62 seconds
> (positive is fast)
> Nov 16 11:56:38 n4mrv weewx[4624]: engine: Starting main packet loop.
> Nov 16 11:56:48 n4mrv weewx[4624]: vantage: LOOP try #1; error: Expected
> to read 99 chars; got 0 instead
> Nov 16 11:56:58 n4mrv weewx[4624]: vantage: LOOP try #2; error: Expected
> to read 99 chars; got 0 instead
> Nov 16 11:57:08 n4mrv weewx[4624]: vantage: LOOP try #3; error: Expected
> to read 99 chars; got 0 instead
> Nov 16 11:57:18 n4mrv weewx[4624]: vantage: LOOP try #4; error: Expected
> to read 99 chars; got 0 instead
> Nov 16 11:57:18 n4mrv weewx[4624]: vantage: LOOP max tries (4) exceeded.
> Nov 16 11:57:18 n4mrv weewx[4624]: engine: Caught WeeWxIOError: Max tries
> exceeded while getting LOOP data.
> Nov 16 11:57:18 n4mrv weewx[4624]:   Waiting 60 seconds then
> retrying...
>
> I remember having this before and adjusting "for_loopPacket in
> self.genDavisLoopPackets(200)" from 200 to 2. I can't find this again
> except in vantage.py and it doesn't seem to help. All hardware is exactly
> the same and was working fine with 3.5.0.
>
> Can anyone help with this? I'm down until I can fix it.  Thanks in advance.
>
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

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

[weewx-user] Upgrade to 3.6.2 fails on loop problem (VP2)

[bgrattan]

Hello,

After running 3.5.0 with no problems (VP2+{serial} on Debian Jessie), I am 
getting the following loop error:

root@n4mrv:/home/weewx# service weewx status
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx)
   Active: active (running) since Wed 2016-11-16 11:54:58 EST; 3min 12s ago
  Process: 4553 ExecStop=/etc/init.d/weewx stop (code=exited, 
status=0/SUCCESS)
  Process: 4611 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)
   CGroup: /system.slice/weewx.service
   └─4624 /usr/bin/python /home/weewx/bin/weewxd --daemon 
--pidfile=/var/run/weewx.pid /home/weewx/weewx.conf

Nov 16 11:56:38 n4mrv weewx[4624]: engine: Starting up weewx version 3.6.2
Nov 16 11:56:38 n4mrv weewx[4624]: engine: Clock error is -0.62 seconds 
(positive is fast)
Nov 16 11:56:38 n4mrv weewx[4624]: engine: Starting main packet loop.
Nov 16 11:56:48 n4mrv weewx[4624]: vantage: LOOP try #1; error: Expected to 
read 99 chars; got 0 instead
Nov 16 11:56:58 n4mrv weewx[4624]: vantage: LOOP try #2; error: Expected to 
read 99 chars; got 0 instead
Nov 16 11:57:08 n4mrv weewx[4624]: vantage: LOOP try #3; error: Expected to 
read 99 chars; got 0 instead
Nov 16 11:57:18 n4mrv weewx[4624]: vantage: LOOP try #4; error: Expected to 
read 99 chars; got 0 instead
Nov 16 11:57:18 n4mrv weewx[4624]: vantage: LOOP max tries (4) exceeded.
Nov 16 11:57:18 n4mrv weewx[4624]: engine: Caught WeeWxIOError: Max tries 
exceeded while getting LOOP data.
Nov 16 11:57:18 n4mrv weewx[4624]:   Waiting 60 seconds then retrying...

I remember having this before and adjusting "for_loopPacket in 
self.genDavisLoopPackets(200)" from 200 to 2. I can't find this again 
except in vantage.py and it doesn't seem to help. All hardware is exactly 
the same and was working fine with 3.5.0.

Can anyone help with this? I'm down until I can fix it.  Thanks in advance.

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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Wunderground reporting "missing wind data"

[Thomas Keffer]

​Edit weewx.conf, setting debug=1, then restart weewx. Post the system log
from weewx startup through the first archive record --- usually 15 minutes
or so is long enough.​

-tk

On Wed, Nov 16, 2016 at 4:52 AM, Paul Weber  wrote:

> Yes I stop it before editing then restart it.
>
> On Tuesday, November 15, 2016 at 9:54:18 PM UTC+1, Tom Keffer wrote:
>>
>> Did you restart weewx after changing weewx.conf?
>>
>> -tk
>> ​
>>
>> On Tue, Nov 15, 2016 at 12:33 PM, Paul Weber  wrote:
>>
>>> Hi, I'm a newb here.  I installed weewx 3.6.2 yesterday and am very
>>> pleased with my success however I am experiencing this problem as well.
>>> (dotted lines on WU map indicating lack of data)  Also my weewx out put
>>> says 0 m/s from N/A (N/A)  My site is ILOGONEO2.  I made the change in my
>>> config to  ignore_zero_wind = false as suggested and there is no
>>> change.  I am using a WMR100NA weather station.
>>> Also my station does not appear on weewx map either even though I have
>>> set publish = true
>>>
>>>
>>> On Saturday, November 12, 2016 at 6:06:32 AM UTC+1, Denny Page wrote:

 A moment presented itself. It does appear that this is fixed in 3.6.2.
 I’ll have to double check tomorrow when wind comes and goes, but it
 looks good right now when everything is completely calm.

 Thank you so much for fixing this. Greatly appreciated.

 Denny


 On Nov 11, 2016, at 20:27, Denny Page  wrote:

 I haven’t checked 3.6, but in 3.5 setting ignore_zero_wind didn’t fix a
 Vantage with rapidfire updates. It seemed to be a “known” issue at the
 time, but I haven’t seen anything in the release notes about it.

 I’ll check 3.6.X as soon as I have a chance.

 Thanks,
 Denny


 On Nov 11, 2016, at 18:36, Thomas Keffer  wrote:

 OK, that's a different problem, one that is easily solved. Just set
 option ignore_zero_wind to 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+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [weewx-user] missing util folder

[Thomas Keffer]

If you installed following the Debian instructions
, the necessary init script should be
installed automatically. Check to make sure it's there: /etc/init.d/weewx.

Otherwise, you can download it from the repository and install in
/etc/init.d:

sudo wget -O /etc/init.d/weewx
https://raw.githubusercontent.com/weewx/weewx/master/util/init.d/weewx.debian


-tk

On Wed, Nov 16, 2016 at 5:51 AM, Ian Coates  wrote:

> i am trying to start weewx automatically and trying to follow the install
> instructions. there does not seem to be a util or init folder in my rasp pi
> installation on debian.
>
> the program has installed itself in a etc folder after following teh
> install instructions.
>
> Can anyone suggest how i can get this to auto run after a reboot?
>
> below are the details i am trying to follow
>
>
> Running as a daemon
>
> For unattended operations it is best to have weewx run as a daemon,
> started automatically when the server is rebooted.
>
> If you use a packaged install from a DEB or RPM distribution, this is done
> automatically. You can ignore this section.
>
> Start by selecting the appropriate run script. They can be found in the
> source or installation under util/init.d/.
> Debian/Ubuntu/Mint: util/init.d/weewx.debian
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[weewx-user] missing util folder

[Ian Coates]

i am trying to start weewx automatically and trying to follow the install 
instructions. there does not seem to be a util or init folder in my rasp pi 
installation on debian.

the program has installed itself in a etc folder after following teh 
install instructions.

Can anyone suggest how i can get this to auto run after a reboot?

below are the details i am trying to follow


Running as a daemon

For unattended operations it is best to have weewx run as a daemon, started 
automatically when the server is rebooted.

If you use a packaged install from a DEB or RPM distribution, this is done 
automatically. You can ignore this section.

Start by selecting the appropriate run script. They can be found in the 
source or installation under util/init.d/.
Debian/Ubuntu/Mint: util/init.d/weewx.debian

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

Re: [weewx-user] Wunderground reporting "missing wind data"

[Paul Weber]

Yes I stop it before editing then restart it.

On Tuesday, November 15, 2016 at 9:54:18 PM UTC+1, Tom Keffer wrote:
>
> Did you restart weewx after changing weewx.conf?
>
> -tk
> ​
>
> On Tue, Nov 15, 2016 at 12:33 PM, Paul Weber  > wrote:
>
>> Hi, I'm a newb here.  I installed weewx 3.6.2 yesterday and am very 
>> pleased with my success however I am experiencing this problem as well. (
>> dotted lines on WU map indicating lack of data)  Also my weewx out put 
>> says 0 m/s from N/A (N/A)  My site is ILOGONEO2.  I made the change in my 
>> config to  ignore_zero_wind = false as suggested and there is no 
>> change.  I am using a WMR100NA weather station.
>> Also my station does not appear on weewx map either even though I have 
>> set publish = true
>>
>>
>> On Saturday, November 12, 2016 at 6:06:32 AM UTC+1, Denny Page wrote:
>>>
>>> A moment presented itself. It does appear that this is fixed in 3.6.2. 
>>> I’ll have to double check tomorrow when wind comes and goes, but it 
>>> looks good right now when everything is completely calm.
>>>
>>> Thank you so much for fixing this. Greatly appreciated.
>>>
>>> Denny
>>>
>>>
>>> On Nov 11, 2016, at 20:27, Denny Page  wrote:
>>>
>>> I haven’t checked 3.6, but in 3.5 setting ignore_zero_wind didn’t fix a 
>>> Vantage with rapidfire updates. It seemed to be a “known” issue at the 
>>> time, but I haven’t seen anything in the release notes about it.
>>>
>>> I’ll check 3.6.X as soon as I have a chance.
>>>
>>> Thanks,
>>> Denny
>>>
>>>
>>> On Nov 11, 2016, at 18:36, Thomas Keffer  wrote:
>>>
>>> OK, that's a different problem, one that is easily solved. Just set 
>>> option ignore_zero_wind to 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+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

Re: [weewx-user] Re: Davis Vantage Vue

[Thomas Keffer]

Both the Davis console and the Envoy include a barometer. The ISS does not.

-tk

On Wed, Nov 16, 2016 at 4:12 AM, Ξ  wrote:

> Can somebody tell me if a Davis without the console can measure the
> pressure?
>
> I've also been thinking of a Davis ISS (integrated sensor suite) + Cabled
> Weather Envoy + Data logger combination (I believe that's the minimum
> combination) but I'm not sure if barometer is part of the ISS or the
> console.
>
> Thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[weewx-user] Re: Davis Vantage Vue

[Ξ]

Can somebody tell me if a Davis without the console can measure the 
pressure? 

I've also been thinking of a Davis ISS (integrated sensor suite) + Cabled 
Weather Envoy + Data logger combination (I believe that's the minimum 
combination) but I'm not sure if barometer is part of the ISS or the 
console. 

Thanks!

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

[weewx-user] update from 3.5.x to 3.6.x

[gjr80]

Hi,

If you have a deb install and have not modified the weewx configuration (eg 
weewx.conf or the Standard skin) then yes it should be that easy. If you have 
modified things then you likely need to make a few decisions during the upgrade 
as mentioned here: 
http://weewx.com/docs/upgrading.htm#Upgrading_using_DEB_package

Gary

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

[weewx-user] Re: Oregon PCR800

[martin swanepoel]

Ok I changed the mapping to the one you indicated (rain_total = 
rain_total.*.*) Will wait and see.


On Monday, November 14, 2016 at 5:55:46 PM UTC+2, martin swanepoel wrote:
>
> Any one else here on the forum that uses an oregon pcr800 rain meter ? I 
> get conflicting readings between debugs vs the graphics displayed.
>
> Thanks,
> Martin
>

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

[weewx-user] update from 3.5.x to 3.6.x

[Dennis slagers]

I am using 3.5.0 is it just dpkg -i for 3.6.0 to update the package ? 

3.5.0 is 'working' flawlessly after severe issues on the raspberry py now, 
changing the version could cause  me headaches again if the upgrade is not 
that 'easy' 

;-)

Normally it would be easy and I think it is, but would like to know some 
experience ;-)

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