[weewx-user] ddwrt, acurite smarthub and interceptor

[Keith T]

I'd like to use weewx for an acurite temp sensor.  I have my home network 
setup with a netgear router.  The sensor signal will be picked up by an 
acurite smarthub, which is plugged into a router running dd-wrt in another 
building.  The dd-wrt is setup in bridge mode with my netgear router in my 
house.  

Things were initially going pretty smooth.  I was able to get weewx 
installed from source, it would run and spit out weather looking data every 
2-3 seconds.  Downloading, installing and configuring the weewx-interceptor 
driver seemed to go well also.  When I ran weewx after that, it would just 
drop back to the command prompt, no errors or other output.  This was in 
listen mode and I hadn't fooled the smarthub with a dns record yet.

I don't see any way I can easily override a dns record with my current 
setup.  The dd-wrt would normally be able to do it, but it doesn't allow 
dhcp to run on dd-wrt when used in bridge mode.  

I figured I'd just switch to using sniffer mode, and tried installing 
pypcap but it's throwing an error:

 pip install pypcap
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 
2020. Please upgrade your
 Python as Python 2.7 won't be maintained after that date. A future version 
of pip will drop sup
port for Python 2.7.
Collecting pypcap
  Downloading 
https://files.pythonhosted.org/packages/33/21/d1f24d8a93e4e11bf604d77e04080c05ecb0
308a5606936a051bd2b2b5da/pypcap-1.2.2.tar.gz (130kB)
100% || 133kB 1.3MB/s
Complete output from command python setup.py egg_info:
pcap.h not found

Anyone have suggestions on how to deal with either of these issues?  





-- 
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: weewx-realtime_gauge-data not working

[gjr80]

Ok, I am a little confused here, but I am guessing it is just a typo in 
your last post. The RTGD extension currently produces a version 13 
gauge-data.txt. Your gauge-data.txt at 
http://www.romaeurmeteo.it/weewx/ss/gauge-data.txt is version 13. The 
current SteelSeries Weather Gauges gauges.js is version 2.7.3 and for WeeWX 
is requires a minimum version 14 gauge-data.txt. So I would expect the 
current SteelSeries Weather Gauges would indeed not work with the current 
RTGD extension. When I look at your gauges.js 
(http://www.romaeurmeteo.it/weewx/ss/scripts/gauges.js) you have changed it 
to require version 12 (the typo? - your post says 13). The changes from 
version 12 to 13 to 14 are such that they have no real impact whether you 
are using a gauges.js that supports version 12, 13 or 14 - there may be 
some javascript errors in the web console but hte gauges will still work.

It looks like the SteelSeries Weather Gauges author has made some minor 
changes to the gauge-data.txt template file (gauge-data.txt.tmpl) to 
include min/max inside temperatures and that has caused the bump to version 
14. I missed that change and have not updated the RTGD extension to version 
14. I also maintain a separate repo 
 with the SteelSeries Weather 
Gauges packaged as a WeeWX extension which is still at verion 13, if folks 
have installed the SteelSeries Weather Gauges from that repo they would 
have version 13 templates and 2.6.3 scripts which support the version 13 
gauge-data.txt - bottom line is it would work fine.

I will update RTGD to version 14 and also update the weewx-steelseries 
extension to version 14/2.7.3. For you it shoudl be a simple change of 
rtgd.py and returning gauges.js back to its orignal (version 14) state.

As for the FTP upload of gauge-data.txt. disabling the gauge-data.txt.tmpl 
template in ss/skin.conf merely stops WeeWX from generating gauge-data.txt 
from the template every archive interval. The FTP still occurs every 
archive interval and the FTP uploads everything below HTML_ROOT (nominally 
public_html). So if the RTGD extension saves gauge-data.txt somewhere under 
HTML_ROOT then it will be uploaded every archive interval by the FTP 
uploader. It will not cause any problems unless the FTP uploader and the 
HTTP POST code try to write the file at the same time on your web server. 
To fix it you have two choices, change the location that the RTGD extension 
saves gauge-data.txt (using the [RealtimeGaugeData] rtgd_path config 
option) or change your FTP upload settings - I suspect that the former will 
be easier :)

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: sftp

[WindnFog]

Thanks!  That''ll do the trick. :-)

On Tuesday, March 26, 2019 at 5:17:58 PM UTC-3, WindnFog wrote:
>
> Hi guys,
>
> I am pondering switiching providers and hosting my web page on another 
> server that doesn't support SSH, just sftp.  I am currently transferring 
> the contents of /home/weewx/public_html/ to it as a test using sftp in a 
> cron job that runs 1 minute after the standart weewx upload.  I notice the 
> documentation says weewx suppots FTPS (which I'm using with my current 
> provider), add then goes on to say "*not* to be confused with SFTP, which 
> uses a Secure Socket Shell protocol."  
>
> I don't think I can convince the potential new host to allow me to do it 
> via FTPS.  They seem fairly rigid about sftp only.  Does weewx support 
> sftp, and if not, are there any plans to implement it?  If the answer is 
> no, I'll stay with my current provider and use FTPS.
>
> - Paul VE1DX
>

-- 
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: Import from a csv-file

[gjr80]

Hans,

On Wednesday, 27 March 2019 09:22:18 UTC+10, Ha Ba wrote:
>
> Do you think, this is something a newbie can fix?
>

Of course, anybody can fix it but the trick is in knowing what is wrong 
first :) There is more than one error (most likely structure) in 
/home/weewx/csv.conf. You can try and locate and fix the errors yourself by 
comparing the format/structure of /home/weewx/csv.conf to the example csv 
import config file at /home/weewx/util/import/csv-example.conf. If you 
can't find the problems post a copy of /home/weewx/csv.conf.

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: Import from a csv-file

[Ha Ba]

Hi Gary,

Thank you for response.

I was able to restore the wee_import file and the errormessage changed.

Now I have this:

**3
al@xxx420:~$ sudo /home/weewx/bin/wee_import 
--config=/home/weewx/weewx.conf --import-config=/home/weewx/csv.conf
Starting wee_import...
Traceback (most recent call last):
  File "/home/weewx/bin/wee_import", line 703, in 
main()
  File "/home/weewx/bin/wee_import", line 652, in main
wlog)
  File "/home/weewx/bin/weeimport/weeimport.py", line 294, in sourceFactory
file_name=options.import_config_path)
  File "/home/weewx/bin/weecfg/__init__.py", line 175, in read_config
config_dict = configobj.ConfigObj(config_path, file_error=True)
  File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in 
__init__
self._load(infile, configspec)
  File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in _load
raise error
configobj.ConfigObjError: Parsing failed with several errors.
First error at line 183.


Do you think, this is something a newbie can fix?

Hans


When using wee_import the only file you should modify is the import config 
> file, and then the recommended approach is to take a copy of one of the 
> example import config files in the /home/weewx/util directory. The 
> wee_import instructions 
>  cover this 
> fairly thoroughly though if English is not your main language you might 
> find the instructions heavy going. Let us know if you are unsure and we can 
> help you out. If you prefer post your questions using your native language 
> and someone or Google translate will do the translation.
>
> Gary
>
> On Wednesday, 27 March 2019 04:18:32 UTC+10, Ha Ba wrote:
>>
>> Hello
>>
>> First, excuse my bad English. I hope you understand what I mean.
>>
>> Working with weewx 3.9.1. Driver is the te923.py. My archive-database is 
>> sqlite.
>>
>> I started with recording data a few days ago and I have a big file with 
>> csv-data, exported over many weeks with the original 
>> windows-stationsoftware.
>>
>> The csv.conf-file I created form the csv-example.conf.
>>
>> Now I will bring in this data to my archive-database with this command:
>>
>> *sudo /home/weewx/bin/wee_import --config=/home/weewx/weewx.conf 
>> --import-config=/home/weewx/csv.conf*
>>
>> and get this error:
>>
>> ***
>>   File "/home/weewx/bin/wee_import", line 76
>> file = /var/tmp/data.csv
>> ^
>> IndentationError: unexpected indent
>> ***
>>
>> I think, I know what "IndentationError" means, but I cannot see what is 
>> wrong in the csv.conf 
>>
>> * this is the part in my csv.conf, where I assume the error **
>>
>> # Specify the source. Available options are:
>> #   CSV - import obs from a single CSV format file
>> #   WU - import obs from a Weather Underground PWS history
>> #   Cumulus - import obs from a one or more Cumulus monthly log files
>> # Format is:
>> #   source = (CSV | WU | Cumulus)
>> source = CSV
>>
>>
>> ##
>>
>> [CSV]
>> # Parameters used when importing from a CSV file
>>
>> # Path and name of our CSV source file. Format is:
>> #   file = full path and filename
>> file = /var/tmp/data.csv
>>
>> # If there is no mapped interval field how will the interval field be
>> # determined for the imported records. Available options are:
>>
>> ** End part 
>>
>> I'm a absolte beginner in Python ;(
>>
>> regards, 
>> Hans
>>
>

-- 
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: Import from a csv-file

[gjr80]

Hi,

I suspect that what you have done is made modification to the file 
/home/weewx/bin/wee_import in an attempt to do a csv import (the chnages 
may be as simple as removing some comments around line 76 but it is 
impossible for me to tell). If you did not intentionally make changes to 
/home/weewx/bin/wee_import then it has been changed by some other means. 
Irrespective, these changes need to be removed and 
/home/weewx/bin/wee_import restored to its original state or you will not 
be able to run wee_import. If you cannot put the file back to its original 
state let me know and I will give you some detailed instructions for how to 
download a replacement copy.

When using wee_import the only file you should modify is the import config 
file, and then the recommended approach is to take a copy of one of the 
example import config files in the /home/weewx/util directory. The 
wee_import instructions 
 cover this fairly 
thoroughly though if English is not your main language you might find the 
instructions heavy going. Let us know if you are unsure and we can help you 
out. If you prefer post your questions using your native language and 
someone or Google translate will do the translation.

Gary

On Wednesday, 27 March 2019 04:18:32 UTC+10, Ha Ba wrote:
>
> Hello
>
> First, excuse my bad English. I hope you understand what I mean.
>
> Working with weewx 3.9.1. Driver is the te923.py. My archive-database is 
> sqlite.
>
> I started with recording data a few days ago and I have a big file with 
> csv-data, exported over many weeks with the original 
> windows-stationsoftware.
>
> The csv.conf-file I created form the csv-example.conf.
>
> Now I will bring in this data to my archive-database with this command:
>
> *sudo /home/weewx/bin/wee_import --config=/home/weewx/weewx.conf 
> --import-config=/home/weewx/csv.conf*
>
> and get this error:
>
> ***
>   File "/home/weewx/bin/wee_import", line 76
> file = /var/tmp/data.csv
> ^
> IndentationError: unexpected indent
> ***
>
> I think, I know what "IndentationError" means, but I cannot see what is 
> wrong in the csv.conf 
>
> * this is the part in my csv.conf, where I assume the error **
>
> # Specify the source. Available options are:
> #   CSV - import obs from a single CSV format file
> #   WU - import obs from a Weather Underground PWS history
> #   Cumulus - import obs from a one or more Cumulus monthly log files
> # Format is:
> #   source = (CSV | WU | Cumulus)
> source = CSV
>
>
> ##
>
> [CSV]
> # Parameters used when importing from a CSV file
>
> # Path and name of our CSV source file. Format is:
> #   file = full path and filename
> file = /var/tmp/data.csv
>
> # If there is no mapped interval field how will the interval field be
> # determined for the imported records. Available options are:
>
> ** End part 
>
> I'm a absolte beginner in Python ;(
>
> regards, 
> Hans
>

-- 
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: Another database

[Thomas Keffer]

OK, and what is the problem?

On Tue, Mar 26, 2019 at 11:12 AM  wrote:

> Zahlreiche Datenbanken in WeeWX
>
> folge dem Link https://github.com/hes19073/hesweewx/blob/master/weewx.conf
>
> ich verwende 10 Datenbanken unter MySQL für Anzeigen unter
> www.wetter.hes61.de
>
>
> many databases in WeeWX
>
> follow the link  -->
> https://github.com/hes19073/hesweewx/blob/master/weewx.conf
>
> I use 10 databases "MySQL" and "SqLite"  by www.wetter.hes61.de
>
> --
> 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: How to change frequency of realtime.txt updates

[G400]

Yes, listing file realtime.txt with this command "ls --full-time 
realtime.txt" I can verify it is being generated around every 2.5 seconds
G400

On Tuesday, March 26, 2019 at 10:33:33 PM UTC+1, gjr80 wrote:
>
> So realtime.txt is now being generated every 2.5 odd seconds?
>
> 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: Add additional rain gauge via second data source

[engolling]

Hi Gary,

I tried to debug the system and therefore I built a "serial sniffer" in 
form of an Arduino Mega passing through the data between serial0 and 
serial1 and printing all messages out on serial2.
I used HTERM to display it and I will provide some screenshots for a better 
visibility.
Here we see a typical archive request:

1. DMPAFT\n - request of WeeWx
2. WeatherDuino acknowledge with 0x06
3. WeeWx sends Date, Time and Checksum
4. WeatherDuino acknowledge with 0x06
5. WeatherDuino sends number of pages and checksum
6. WeeWx acknowledge
7. WeatherDuino sends page and overhead - in sum 267 bytes as expected.
*8. WeeWx sends LineFeed, but should acknowledge, send a CRC failure or 
skip - that is strange...*

See documentation line 35 and 36
https://www.davisinstruments.com/support/weather/download/VantageSerialProtocolDocs_v261.pdf

1 Minute and 360ms later the next DMPAFT command is sent.

This example is starting today at 19:05:16 local time - this is written 
into the logfile.
Mar 26 19:05:17 WeatherDuinoPi weewx[17760]: manager: Added record 2019-03-
26 19:04:00 CET (1553623440) to database 'weewx.sdb'
Mar 26 19:05:17 WeatherDuinoPi weewx[17760]: manager: Added record 2019-03-
26 19:04:00 CET (1553623440) to daily summary in 'weewx.sdb'
Mar 26 19:05:19 WeatherDuinoPi weewx[17760]: manager: Unable to add record 
2019-03-26 19:00:00 CET (1553623200) to database 'weewx.sdb': UNIQUE 
constraint failed: archive.dateTime
Mar 26 19:05:21 WeatherDuinoPi weewx[17760]: manager: Unable to add record 
2019-03-26 19:01:00 CET (1553623260) to database 'weewx.sdb': UNIQUE 
constraint failed: archive.dateTime
Mar 26 19:05:31 WeatherDuinoPi weewx[17760]: cheetahgenerator: Generated 9 
files for report StandardReport in 10.25 seconds
Mar 26 19:06:19 WeatherDuinoPi weewx[17760]: manager: Added record 2019-03-
26 19:05:00 CET (1553623500) to database 'weewx.sdb'
Mar 26 19:06:20 WeatherDuinoPi weewx[17760]: manager: Added record 2019-03-
26 19:05:00 CET (1553623500) to daily summary in 'weewx.sdb'
Mar 26 19:06:23 WeatherDuinoPi weewx[17760]: manager: Unable to add record 
2019-03-26 19:01:00 CET (1553623260) to database 'weewx.sdb': UNIQUE 
constraint failed: archive.dateTime

In my opinion the WeatherDuino is acting as described in the protocol 
description. It is also a bit strange that WeeWx tries to add the "older" 
records now to the database which are also saved in the same page of the 
flash. But as it does not acknowledge the received page something strange 
is going on at this point.

Maybe you or somebody else owning an original Davis station has an idea.

Regards,
engolling


Am Montag, 25. März 2019 14:47:08 UTC+1 schrieb gjr80:
>
> The vantage driver is somewhat complex. How the vantage driver operates 
> depends on whether hardware or software record generation is in use. If 
> software record generation is in use then the vantage driver obtains loop 
> packets from the console (using the LOOP command) and the loop packets are 
> then passed to WeeWX. This goes on continuously. WeeWX accumulates the loop 
> packets and at the end of each archive interval WeeWX synthesises an 
> archive record from the accumulated loop packets. This archive record is 
> then further processed by various services, saved to database and used as 
> necessary in report generation.
>
> If hardware record generation is in use then the same loop packet 
> processes occur as for software record generation (ie the driver passes 
> loop packets to WeeWX and WeeWX accumulates them) but at the end of the 
> archive interval instead of WeeWX synthesising an archive record from the 
> accumulated loop packets, WeeWX asks the driver to obtain an archive record 
> from the console. The driver uses the DMPAFT command to obtain the archive 
> record and this archive record is passed back to WeeWX. This hardware 
> archive record is further processed by various services, saved to database 
> and used as necessary in report generation.
>
> As far as I know the DMPAFT command is only used at the end of the archive 
> interval (eg every 5 minutes) and not very few seconds. I think to dig any 
> further into the issue would take some detailed analysis of how the 
> WeatherDuino responds to various commands. I suspect that somewhere the 
> behaviour when the WeatherDuino receives the DMPAFT command is slightly 
> different to the Davis console/logger. You should be able to instrument the 
> vantage driver to log anything from raw data from the console/logger 
> through to the decoded observations and packets/records. The good thing is 
> the Davis protocols are documented and in the public domain so it should be 
> easy to compare actual and expected responses.
>
> Gary
>
> On Sunday, 24 March 2019 09:03:28 UTC+10, engolling wrote:
>>
>> Hi Gary,
>> I checked the emulation of the WeatherDuino in the code and from my point 
>> of view it seems to be implemented as in the protocol description.
>> Nevertheless it might differ in any behaviour 

[weewx-user] Re: How to change frequency of realtime.txt updates

[gjr80]

So realtime.txt is now being generated every 2.5 odd seconds?

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: How to change frequency of realtime.txt updates

[G400]

I changed archive interval to 60 (s) to match hardware interval
Running sudo weewxd /etc/weewx/weewx.conf shows that loop is executing 
every 2 seconds:

LOOP:   2019-03-26 22:20:30 CET (1553635230) appTemp: 37.4554842831, 
barometer: 30.149, cloudbase: 237.017505581, consBatteryVoltage: 4.69, 
dateTime: 1553635230, dayET: 0.0, dayRain: 0.03, dewpoint: 44.6359229754, 
extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, 
extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, 
forecastIcon: 6, forecastRule: 44, heatindex: 44.9, humidex: 44.9359248133, 
inDewpoint: 45.7611363695, inHumidity: 31.0, insideAlarm: 0, inTemp: 79.0, 
leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: 3.44, 
outHumidity: 99.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 44.9, rain: 
None, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, 
soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.03, stormStart: 
1553554800, sunrise: 1553577600, sunset: 1553623500, trendIcon: -20, 
txBatteryStatus: 0, usUnits: 1, windchill: 39.3480188351, windDir: 343.0, 
windGust: 11.0, windGustDir: 343.0, windSpeed: 11.0, windSpeed10: 9.0, 
yearET: 0.0, yearRain: 7.21
LOOP:   2019-03-26 22:20:30 CET (1553635230) appTemp: 37.4554842831, 
barometer: 30.149, cloudbase: 237.017505581, consBatteryVoltage: 4.69, 
dateTime: 1553635230, dayET: 0.0, dayRain: 0.03, dewpoint: 44.6359229754, 
extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, 
extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, 
forecastIcon: 6, forecastRule: 44, heatindex: 44.9, humidex: 44.9359248133, 
inDewpoint: 45.7611363695, inHumidity: 31.0, insideAlarm: 0, inTemp: 79.0, 
leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: 3.44, 
outHumidity: 99.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 44.9, rain: 
0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, 
soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.03, stormStart: 
1553554800, sunrise: 1553577600, sunset: 1553623500, trendIcon: -20, 
txBatteryStatus: 0, usUnits: 1, windchill: 39.3480188351, windDir: 343.0, 
windGust: 11.0, windGustDir: 343.0, windSpeed: 11.0, windSpeed10: 9.0, 
yearET: 0.0, yearRain: 7.21
LOOP:   2019-03-26 22:20:32 CET (1553635232) appTemp: 38.0187532831, 
barometer: 30.149, cloudbase: 237.017505581, consBatteryVoltage: 4.69, 
dateTime: 1553635232, dayET: 0.0, dayRain: 0.03, dewpoint: 44.6359229754, 
extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, 
extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, 
forecastIcon: 6, forecastRule: 44, heatindex: 44.9, humidex: 44.9359248133, 
inDewpoint: 45.7611363695, inHumidity: 31.0, insideAlarm: 0, inTemp: 79.0, 
leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: 3.44, 
outHumidity: 99.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 44.9, rain: 
0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, 
soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.03, stormStart: 
1553554800, sunrise: 1553577600, sunset: 1553623500, trendIcon: -20, 
txBatteryStatus: 0, usUnits: 1, windchill: 39.7157332354, windDir: 336.0, 
windGust: 11.0, windGustDir: 343.0, windSpeed: 10.0, windSpeed10: 9.0, 
yearET: 0.0, yearRain: 7.21
LOOP:   2019-03-26 22:20:34 CET (1553635234) appTemp: 38.0187532831, 
barometer: 30.149, cloudbase: 237.017505581, consBatteryVoltage: 4.69, 
dateTime: 1553635234, dayET: 0.0, dayRain: 0.03, dewpoint: 44.6359229754, 
extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, 
extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, 
forecastIcon: 6, forecastRule: 44, heatindex: 44.9, humidex: 44.9359248133, 
inDewpoint: 45.7611363695, inHumidity: 31.0, insideAlarm: 0, inTemp: 79.0, 
leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: 3.44, 
outHumidity: 99.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 44.9, rain: 
0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, 
soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.03, stormStart: 
1553554800, sunrise: 1553577600, sunset: 1553623500, trendIcon: -20, 
txBatteryStatus: 0, usUnits: 1, windchill: 39.7157332354, windDir: 341.0, 
windGust: 11.0, windGustDir: 343.0, windSpeed: 10.0, windSpeed10: 9.0, 
yearET: 0.0, yearRain: 7.21
LOOP:   2019-03-26 22:20:36 CET (1553635236) appTemp: 38.0187532831, 
barometer: 30.149, cloudbase: 237.017505581, consBatteryVoltage: 4.69, 
dateTime: 1553635236, dayET: 0.0, dayRain: 0.03, dewpoint: 44.6359229754, 
extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, 
extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, 
forecastIcon: 6, forecastRule: 44, heatindex: 44.9, humidex: 44.9359248133, 
inDewpoint: 45.7611363695, inHumidity: 31.0, insideAlarm: 0, inTemp: 79.0, 
leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: 3.44, 
outHumidity: 99.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 44.9, rain: 
0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, 

[weewx-user] Re: How to Include Modern XTide in Forecasting Extension?

[mwall]

On Monday, March 25, 2019 at 11:22:28 AM UTC-4, V. Kelly Bellis wrote:
>
> One thought that keeps coming up, are any of your tests being done on a 
> system where the only xtide installation is v2.15.2?
>

i have been testing on a raspberry pi and an x64 box, both running some 
version of debian.  both have old and new xtide on them.

i'll try removing the debian xtide from the pi so see if that gives me 
results like yours (but it won't be for a few days - boats going in the 
water now, so lots of bottom painting and logistics to take care of)
 

-- 
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: How to change frequency of realtime.txt updates

[gjr80]

The following lines indicate CRT is loading correctly and binding to loop, so 
realtime.txt should be generated on every loop packet:

Mar 26 21:02:15 localhost weewx[7965]: crt: service version is 0.18
Mar 26 21:02:15 localhost weewx[7965]: crt: output goes to 
/home/weewx/realtime.txt
Mar 26 21:02:15 localhost weewx[7965]: crt: 'None' values will be displayed as 
NULL
Mar 26 21:02:15 localhost weewx[7965]: crt: units will be displayed as METRICWX
Mar 26 21:02:15 localhost weewx[7965]: crt: zambretti forecast: False
Mar 26 21:02:15 localhost weewx[7965]: crt: binding is loop

Is realtime.txt still only being generated each minute? If so I suggest you run 
weeWX directly (http://weewx.com/docs/usersguide.htm#Running_directly) for a 
few minutes so we can confirm that loop packets are being generated every 2.5 
odd seconds as they should.

The following connfirms my suspicions re your archive interval:

Mar 26 21:02:15 localhost weewx[7965]: engine: The archive interval in the 
configuration file (300) does not match the station hardware interval (60).

Options for fixing are as per my previous post.

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: sftp

[mwall]

On Tuesday, March 26, 2019 at 4:17:58 PM UTC-4, WindnFog wrote:
>
> Does weewx support sftp, and if not, are there any plans to implement it?
>

yes, but you must install the weewx-sftp extension:

https://github.com/matthewwall/weewx-sftp

 

-- 
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] sftp

[WindnFog]

Hi guys,

I am pondering switiching providers and hosting my web page on another 
server that doesn't support SSH, just sftp.  I am currently transferring 
the contents of /home/weewx/public_html/ to it as a test using sftp in a 
cron job that runs 1 minute after the standart weewx upload.  I notice the 
documentation says weewx suppots FTPS (which I'm using with my current 
provider), add then goes on to say "*not* to be confused with SFTP, which 
uses a Secure Socket Shell protocol."  

I don't think I can convince the potential new host to allow me to do it 
via FTPS.  They seem fairly rigid about sftp only.  Does weewx support 
sftp, and if not, are there any plans to implement it?  If the answer is 
no, I'll stay with my current provider and use FTPS.

- Paul VE1DX

-- 
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] Import from a csv-file

[Ha Ba]

Hello

First, excuse my bad English. I hope you understand what I mean.

Working with weewx 3.9.1. Driver is the te923.py. My archive-database is 
sqlite.

I started with recording data a few days ago and I have a big file with 
csv-data, exported over many weeks with the original 
windows-stationsoftware.

The csv.conf-file I created form the csv-example.conf.

Now I will bring in this data to my archive-database with this command:

*sudo /home/weewx/bin/wee_import --config=/home/weewx/weewx.conf 
--import-config=/home/weewx/csv.conf*

and get this error:

***
  File "/home/weewx/bin/wee_import", line 76
file = /var/tmp/data.csv
^
IndentationError: unexpected indent
***

I think, I know what "IndentationError" means, but I cannot see what is 
wrong in the csv.conf 

* this is the part in my csv.conf, where I assume the error **

# Specify the source. Available options are:
#   CSV - import obs from a single CSV format file
#   WU - import obs from a Weather Underground PWS history
#   Cumulus - import obs from a one or more Cumulus monthly log files
# Format is:
#   source = (CSV | WU | Cumulus)
source = CSV

##

[CSV]
# Parameters used when importing from a CSV file

# Path and name of our CSV source file. Format is:
#   file = full path and filename
file = /var/tmp/data.csv

# If there is no mapped interval field how will the interval field be
# determined for the imported records. Available options are:

** End part 

I'm a absolte beginner in Python ;(

regards, 
Hans

-- 
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: Another database

[hesfrrkr]

Zahlreiche Datenbanken in WeeWX

folge dem Link https://github.com/hes19073/hesweewx/blob/master/weewx.conf

ich verwende 10 Datenbanken unter MySQL für Anzeigen unter 
www.wetter.hes61.de


many databases in WeeWX

follow the link  --> 
https://github.com/hes19073/hesweewx/blob/master/weewx.conf

I use 10 databases "MySQL" and "SqLite"  by www.wetter.hes61.de

-- 
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: Another database

[Thomas Keffer]

phpmyadmin is an administrative tool, not a database. What is the database?

Why not write your question in your native language? Please avoid jargon
and idioms. Use full, natural sentences. There is probably someone here who
speaks it, or we can use Google translate.

-tk

On Tue, Mar 26, 2019 at 8:44 AM rimas petronis  wrote:

>
> database  phpmyadmin   local
>
> I can't find a way to connect
>
>
>
>
>
> 2019 m. kovas 19 d., antradienis 16:10:50 UTC+2, rimas petronis rašė:
>>
>> good day
>>
>> sorry my weak english translated with google
>> i really liked the program not only watching the weather but watching
>> other devices i would like to connect to weewx data in another database
>>
>> database and other composition
>>
>> [image: image.png]
>>
>>
>> can be connected
>>
> --
> 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: Another database

[rimas petronis]

database  phpmyadmin   local

I can't find a way to connect





2019 m. kovas 19 d., antradienis 16:10:50 UTC+2, rimas petronis rašė:
>
> good day
>
> sorry my weak english translated with google
> i really liked the program not only watching the weather but watching 
> other devices i would like to connect to weewx data in another database
>
> database and other composition
>
> [image: image.png]
>
>
> can be connected
>

-- 
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: Another database

[Thomas Keffer]

You will need to give us much more information before we can help you. To
start:

What kind of database?
is it remote, or local?
What is the problem when you connect?

-tk

On Tue, Mar 26, 2019 at 7:51 AM rimas petronis  wrote:

> Hello.
>
> help needed
> I'm trying to connect such a database to weewx
> after a long online search and the test failed
> maybe you have a suggestion or reference where to look
>
>
> 2019-03-19, an, 16:18 rimas petronis  rašė:
>
>> [image: duom baze..png]
>>
>>
>> 2019 m. kovas 19 d., antradienis 16:10:50 UTC+2, rimas petronis rašė:
>>>
>>> good day
>>>
>>> sorry my weak english translated with google
>>> i really liked the program not only watching the weather but watching
>>> other devices i would like to connect to weewx data in another database
>>>
>>> database and other composition
>>>
>>> [image: image.png]
>>>
>>>
>>> can be connected
>>>
>> --
>> 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.
>>
>
>
> --
> Pagarbiai,
> Rimas Petronis
>
> --
> 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] Re: Another database

[rimas petronis]

Hello.

help needed
I'm trying to connect such a database to weewx
after a long online search and the test failed
maybe you have a suggestion or reference where to look


2019-03-19, an, 16:18 rimas petronis  rašė:

> [image: duom baze..png]
>
>
> 2019 m. kovas 19 d., antradienis 16:10:50 UTC+2, rimas petronis rašė:
>>
>> good day
>>
>> sorry my weak english translated with google
>> i really liked the program not only watching the weather but watching
>> other devices i would like to connect to weewx data in another database
>>
>> database and other composition
>>
>> [image: image.png]
>>
>>
>> can be connected
>>
> --
> 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.
>


-- 
Pagarbiai,
Rimas Petronis

-- 
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: weewx-realtime_gauge-data not working

[gjr80]

Have just been looking at your web server and I am confident that it is 
correctly configured and I suspect the issue lies in your 
[RealtimeGaugeData] settings. Will wait for you to post the wee_debug 
report which will show us the [RealtimeGaugeData] stanza contents.

Gary

On Tuesday, 26 March 2019 08:53:11 UTC+10, gjr80 wrote:
>
> I've had a look at your logs and site and it appears that an error is 
> occurring on your web server when the http post is attempted. I can see 
> post_gauge-data.php on your website so I suspect the issue may well be 
> one of permissions on your web server. Unfortunately I am pushed for time 
> at the moment and won't be able to get back to this until later today. In 
> the meantime it may help to have some details of your WeeWX config. Could 
> you please use the wee_debug utility 
>  to produce a 
> wee_debug report and post the report here. Before posting just check the 
> output for any sensitive info, wee_debug will attempt to mask sensitive 
> data such as passwords, user names etc but it is not perfect.
>
> One other thing, you will note that your gauges will be updating every 5 
> minutes, that is because whilst the http post using post_gauge-data.php 
> is failing gauge-data.txt is still being uploaded every 5 minutes via 
> FTP. We can fix that once we get the http post working.
>
> Gary
>
> On Tuesday, 26 March 2019 07:55:45 UTC+10, Andrea Cecilia wrote:
>>
>> it is already set in debug=1 mode!
>>
>> Il giorno lunedì 25 marzo 2019 22:09:57 UTC+1, Tom Robertson ha scritto:
>>
>> We will need to wait for Gary.  I suggest you set debug=1 in the weewx 
>> config file, restart weewx and then post the results.
>>
>> -
>> Tom
>>
>> On Mar 25, 2019, at 3:50 PM, Andrea Cecilia  wrote:
>>
>> Hi Tom,
>> I didn't make the HTTP POST configuration, because it is written that it 
>> is optional. Anyway, now I have followed the instructions 
>>  
>> for setting it, but it's still not working. You can see the attached log. 
>> In particular, I put the post_gauge-data.php in weewx/ss path on my web 
>> server, id est the steel series directory, ensuring that it has read/write 
>> permissions.  I also commented out the [CheetahGenerator] [[ToDate]] 
>> lines in $SKIN_ROOT/ss/skin.conf, so that steel series driver won't 
>> generate gauge-data.txt file. 
>>
>>
>> Mar 25 21:45:15 raspberrypi-romaeur weewx[11030]: vantage: Getting 
>> archive packets since 2019-03-25 21:40:00 CET (1553546400)
>> Mar 25 21:45:15 raspberrypi-romaeur weewx[11030]: rtgdthread: Failed to 
>> post data: Unexpected response
>> Mar 25 21:45:15 raspberrypi-romaeur weewx[11030]: vantage: Gentle wake up 
>> of console successful
>> Mar 25 21:45:17 raspberrypi-romaeur weewx[11030]: vantage: Retrieving 1 
>> page(s); starting index= 0
>> Mar 25 21:45:17 raspberrypi-romaeur weewx[11030]: manager: Added record 
>> 2019-03-25 21:45:00 CET (1553546700) to database 'weewx.sdb'
>> Mar 25 21:45:17 raspberrypi-romaeur weewx[11030]: manager: Added record 
>> 2019-03-25 21:45:00 CET (1553546700) to daily summary in 'weewx.sdb'
>> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: vantage: Empty record 
>> page 0; index 1
>> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: reportengine: Running 
>> reports for latest time in the database.
>> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: vantage: Requesting 200 
>> LOOP packets.
>> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: reportengine: Running 
>> report 'StandardReport'
>> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: reportengine: Found 
>> configuration file /home/weewx/skins/Standard/skin.conf for report 
>> 'StandardReport'
>> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: cheetahgenerator: using 
>> search list ['weewx.cheetahgenerator.Almanac', 
>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
>> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
>> 'weewx.cheetahgenerator.Extras']
>> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: manager: Daily summary 
>> version is 2.0
>> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: vantage: Gentle wake up 
>> of console successful
>> Mar 25 21:45:20 raspberrypi-romaeur weewx[11030]: restx: 
>> Wunderground-PWS: Published record 2019-03-25 21:45:00 CET (1553546700)
>> Mar 25 21:45:21 raspberrypi-romaeur weewx[11030]: rtgdthread: Failed to 
>> post data: Unexpected response
>> Mar 25 21:45:21 raspberrypi-romaeur weewx[11030]: rtgdthread: Failed to 
>> post data: Unexpected response
>> Mar 25 21:45:22 raspberrypi-romaeur weewx[11030]: cheetahgenerator: 
>> Generated 15 files for report StandardReport in 1.54 seconds
>> Mar 25 21:45:22 raspberrypi-romaeur weewx[11030]: manager: Daily summary 
>> version is 2.0
>> Mar 25 21:45:25 raspberrypi-romaeur weewx[11030]: rtgdthread: Failed to 
>> post data: Unexpected response
>> Mar 25 21:45:25 

[weewx-user] Re: How to change frequency of realtime.txt updates

[gjr80]

OK, you are running with a one minute archive interval so I am wondering if 
the crt extension is bound to loop or not. If not that would explain the 
one minute update interval for realtime.txt. You did not post the WeeWX 
startup so we missed the log entry that tells us what is binding is being 
used. Suggest you either post the log from WeeWX startup (recommended) or 
post the [CumulusRealTime] stanza from weewx.conf. 

You might want to look into your archive interval as well, if you have 
weewx.conf set to use a five minute archive interval (your second post) and 
WeeWX is actually using  a one minute archive interval (as per the log 
extract) it would indicate that the envoy is set to a one minute archive 
interval. If the console/envoy is set to a given archive interval and a 
different interval is specified in weewx.conf then the weewx.conf setting 
is ignored and the console/envoy setting issued. Again the WeeWX startup 
log would show us what is going on. Up to you what you want to use, if one 
minute then I suggest you change weewx.conf, if five minutes then i suggest 
you use wee_device --set-interval 
 to change 
the envoy archive interval to five minutes.

Gary

On Tuesday, 26 March 2019 17:53:22 UTC+10, G400 wrote:
>
> Thank you a lot for assisting and helping me!
>
> Attached is my weewx.log file (logging to a separate file)
>
> I check realtime.txt file time stamp in the file system on the locale 
> computer where weewx is running (no transfer to another server or anything 
> else)
>
> Also note that Belchertown skin files updates are ftp-ed across network to 
> a remote server and are not related to realtime.txt update frequency as I'm 
> trying to figure out now.
> G400
>
> On Monday, March 25, 2019 at 11:25:01 PM UTC+1, gjr80 wrote:
>>
>> Hi,
>>
>> If you are using a Davis Vantage station and the crt extension is bound 
>> to loop then you should be seeing realtime.txt being generated every 2.5 
>> odd seconds. If you have changed the binding to archive then based on the 
>> weewx.conf extract you provided it should be generated every 5minutes. I 
>> am not sure where the one minute update you mention comes from, it should 
>> not be happening. How are you checking how often realtime.txt is 
>> generated? Are you checking the file on the WeeWX machine or are you 
>> checking on a web server or some other server? If you are checking on a 
>> machine other than the WeeWX machine remember that there must be some 
>> mechanism to transfer realtime.txt from the WeeWX machine to the remote 
>> server and it may be that transfer mechanism that is only occurring every 
>> minute.
>>
>> Unfortunately the crt extension does not give us too much extra debug 
>> info but it may help to get a clearer picture of what is going on if you 
>> post a debug log extract. To do this edit weewx.conf, set debug=1, save 
>> weewx.conf and then restart WeeWX. Let WeeWX run for at least 10 minutes 
>> and then take a log extract showing the entire WeeWX startup and the 
>> following 10 minutes of log activity. The log should be in 
>> /var/log/syslog unless you have changed it. Post the log extract without 
>> any changes.
>>
>> At the end of the day though you will have two choices in terms of 
>> realtime.txt update period, either on every loop packet (2.5 odd 
>> seconds) or every archive interval (currently 5 minutes).
>>
>> Gary
>>
>> On Tuesday, 26 March 2019 06:16:32 UTC+10, G400 wrote:
>>>
>>> Davis Vantage2 getting data from Weather Envoy USD->Serial
>>>
>>> This is my current setting:
>>> StdArchive]
>>> 
>>> # If the station hardware supports data logging then the archive 
>>> interval
>>> # will be downloaded from the station. Otherwise, specify it (in 
>>> seconds).
>>> archive_interval = 300
>>>
>>>
>>> Currently realtime.txt is created every 60s.
>>> How do I relate this to archive interval?
>>>
>>> I want realtime.txt to be updated every 10s.
>>>
>>>
>>> On Monday, March 25, 2019 at 8:41:25 PM UTC+1, Andrew Milner wrote:

 according to the wiki the generation can be tied to loop or archive - 
 which is yours tied to?  It should be to loop (which is the default) if 
 you 
 want it creating more often than the archive interval.

 if to loop then it depends on your station type - what kind of station 
 do you have?  Some stations (eg FineOffset) cannot produce loop data any 
 faster than say  every 48 seconds

 if to archive then changing the archive interval will also change the 
 frequency of creating the file.

 On Monday, 25 March 2019 21:34:37 UTC+2, G400 wrote:
>
> How can I modify the frequency of Cumulus formatted raltime.txt output 
> file using crt plugin (https://github.com/weewx/weewx/wiki/crt)?
> G400
>


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this 

[weewx-user] Re: How to change frequency of realtime.txt updates

[gjr80]

As does the standard wireless/wired consoles. As far as I am aware the envoy is 
for all intents and purposes a console without the human interface. In the 
Davis serial reference document says it applies to the consoles and the envoy.

Simple way to check is to run WeeWX directly, the LOOP: lines will show the 
loop interval.

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.