[weewx-user] Re: Importing other data

[gjr80]

Hi,

The short answer to your question is yes, but it really depends on how much 
massaging of your data/customising WeeWX you are prepared to do.

Firstly the importing. The WeeWX utility wee_import 
 can import data 
from WeatherUnderground, Cumulus monthly log files and files containing 
comma separated values (CSV). Provided you can get your data into a 
suitable format there should be no reason why wee_import cannot import your 
data via CSV.

But (there is always a but), you would need to work out how you will store 
your data in WeeWX. For example, the default WeeWX schema consists of a 
number of weather related fields, there is no field call dust_particle so 
where would you store your dust particle data. You could make use of an 
existing unused field say extraTemp1, you would then access your dust 
particle data in reports etc with tags such as $day.extraTemp1.sum. 
Assuming dust particles are not measured in degree C or F you would need to 
change the units associated with extraTemp1. Easy enough done but something 
you would need to take care of. I should point out the linkage between 
extraTemp1 and dust particles is all within WeeWX, it will be transparent 
to anyone viewing report/plots of dust particle data. 

Another approach would to create a custom schema with a field called 
dust_particle and whatever units dust particles come in. You could then 
import your dust particle data straight into the dust_particle field and 
produce reports with tags such as $day.dust_particle.sum. Again, easily 
doable and transparent to those viewing your report/plots.

The section Customizing the Database 
 in the Customization 
Guide  may be of interest.

One other thing you might want to think about if you have not done so 
already is how you might continue to get your additional data into WeeWX on 
an ongoing basis. Running regular wee_import sessions is rather kludgy, you 
might be best served by coming up with a driver or WeeWX service for your 
additional data so that WeeWX can automatically pick it up and insert it 
into the database. Of course you can skip this if it is not 
required/relevant.

Gary

On Tuesday, 9 October 2018 00:58:08 UTC+10, Andre Rieth wrote:
>
>
> Hello Besides weewx, I have an environmental station based on easyesp. Is 
> there a way to import the data from there and output it by graphics. In 
> addition to temperature and humidity, I also have dust particles and 
> radioactive radiation. I would be happy if it is possible. greetings André
>

-- 
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 I change what shows up in my Weewx RSS feed?

[gjr80]

Hi,

When you refer to the 'RSS feed' I presume you are referring to the 
weewx_rss.xml file that appears in public_html/RSS ?

You can control what appears in weewx_rss.xml through the 
skins/Standard/RSS/weewx_rss.xml.tmpl template file. `Wind: 6 km/h from 
106°` will likely be produced by the following:

$current.windSpeed from $current.windDir

though it really depends on what you are picking up and tweeting from 
weewx_rss.xml. In this case the tag $current.windDir will give you a 
numeric direction with degree sign (the default format). If you change that 
to use $current.windDir.ordinal_compass instead of just $current.windDir 
you will get an ordinal direction like ESE. If you wan to include both you 
could use $current.windDir ($current.windDir.ordinal_compass) or 
$current.windDir.ordinal_compass 
($current.windDir) to get 106° (ESE) or ESE (106°) respectively.

You might want to have a read through the Tags section 
 of the Customization Guide 
 or if you are really adventurous 
the Wind section .

Any changes you do make to weewx_rss.xml.tmpl should be safe across WeeWX 
upgrades but you may wish to make a copy of your modified weewx_rss.xml.tmpl 
just in case.

Gary

PS. You may also want to have a look at the twitter extension 
, might save you a bit of 
double handling.

-- 
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: Belchertown Skin and MQTT With Username Not Working

[Gary Hammer]

The publishing is not a problem, but that is not in the skin.

As I said, I have tried nearly any combination of config, all to no avail.

 

I may have to look at a different MQTT host, one that does not require username 
and password for all connections as it seems that is not working in the 
Belchertown skin.

 

 

From: weewx-user@googlegroups.com  On Behalf Of 
Philip Kutzenco
Sent: Monday, October 8, 2018 5:53 PM
To: weewx-user 
Subject: Re: [weewx-user] Re: Belchertown Skin and MQTT With Username Not 
Working

 

The answer to that question is no. I've attached a file with sanitized excerpts 
of my weewx.conf file showing the stanzas related to:

 

1. MQTT (publishing) - which specifies a username and password but not 
websocket (port 8883 - SSL not websocket)

2. Belchertown Highcharts

3. Belchertown (subscribing) - which specifies websockets but no 
username/password (port 9001 - SSL and websocket)

 

You'll need to check with Pat, but I expect he saw no reason to lock down the 
subscriptions with username/password when programming his skin, only locking 
down the publishing (which is done by MWall's MQTT extension). I think the 
rationale is you don't care who sees the output (after all, it's being 
published on an open web site), but you don't want any unauthorized uploading 
of data which you'll be outputting and displaying to others.

 

So, if the MQTT broker requires a username/password for subscribing over 
websockets, I don't know if the skin provides for that. I assume you've tried 
to prepend :@ to the host name in the Belchertown Extras 
stanza without success.

 

Hopefully Pat can weigh in here.

 

phil

 


On Monday, October 8, 2018 at 4:54:41 PM UTC-4, G Hammer wrote:

Do you connect the client (skin) via websockets or any other way using a 
username and password?

That is the question.

 

From:   weewx...@googlegroups.com <  
weewx...@googlegroups.com> On Behalf Of Philip Kutzenco
Sent: Monday, October 8, 2018 3:32 PM
To: weewx-user <  weewx...@googlegroups.com>
Subject: [weewx-user] Re: Belchertown Skin and MQTT With Username Not Working

 

I have it working on my own externally hosted Mosquitto server (on Digital 
Ocean). My Mosquiutto MQTT broker is set up requiring a username and password 
for publishing. Additionally it has TLS/SSL implemented (with Let's Encrypt 
certificates). It allows subscribing anonymously and also runs Websockets so 
that it can feedthe Belchertown skin. I used Pat's MQTT  
 "tutorial" to do 
this. My website is https://wx.kutzenco.com.

 

phil


On Monday, October 8, 2018 at 10:21:50 AM UTC-4, G Hammer wrote:

 

Does anyone have the Belchertown skin working with MQTT using a server that 
requires a username and password such as CloudMQTT?

 

I have tried several different ways of configuring the skin and it fails to 
connect or it shows 'Connecting to weather station real time data' forever 
without connecting.

The data is being sent to the server fine and I have subscribed to it using 
client software (see below).

 

Thanks for any input, I'm at a loss here.

 



 

-- 
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/5Qn_6oZjLP4/unsubscribe.
To unsubscribe from this group and all its topics, 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 a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/5Qn_6oZjLP4/unsubscribe.
To unsubscribe from this group and all its topics, 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] how I change what shows up in my Weewx RSS feed?

[Kevin Lloyd]

Hello everyone,

I have been using Weewx for a couple of months on a two Raspberry Pi 3's, 
each connected to a weather station. That being said, I'm using dlvr.it to 
pull the most recent post from one of the Weewx's RSS feed, and publish 
those posts to Twitter every 15 minutes, or at often as a new post shows up.

How do I change what shows up in the RSS feed?

Case in point, a recent tweet (from Twitter.com/ComoxWeather):
"Time: 08/10/18 02:40:00 PM Outside Temperature: 11.9°C Inside Temperature: 
22.8°C Wind Chill: 11.9°C Heat Index: 11.9°C Dewpoint: 11.2°C Humidity: 95% 
Barometer: 1012.1 hPa Wind: 6 km/h from 106° Rain Rate: 0.0 mm/hr"

I find it interesting that my weather station (Acurite) and my Weewx site 
shows the Wind Direction as km/h from ENE (for example), but in the RSS 
feed and tweets, it's showing up as "Wind: 6 kmh from 106°", for example. 
How do I change that to show up as ENE or whatever?

I spent a couple of hours this weekend researching online, but so far 
haven't found a solution. Hopefully someone here can help me figure this 
out?

It's important to note that I'm *very* new at scripting, and the Raspberry 
Pi. The only reason I got this far is because people have been kind enough 
to post step by step setup guides, including each command line instruction, 
and of course I followed the guides on weewx.com, and Meteotemplate.com.

Any help is very much appreciated! :)

-- 
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: WMR300 - intermittent and partial loss of loop data

[Ruben Navarro Huedo]

After 48 hours weewx lost connection with wmr300:

Oct  8 20:40:14 meteo weewx[20330]: manager: Added record 2018-10-08 
20:40:00 CEST (1539024000) to daily summary in 'weewx.sdb'
Oct  8 20:40:15 meteo weewx[20330]: restx: CWOP: Published record 
2018-10-08 20:40:00 CEST (1539024000)
Oct  8 20:40:15 meteo weewx[20330]: restx: AWEKAS: Published record 
2018-10-08 20:40:00 CEST (1539024000)
Oct  8 20:40:15 meteo weewx[20330]: restx: PWSWeather: Published record 
2018-10-08 20:40:00 CEST (1539024000)
Oct  8 20:40:15 meteo weewx[20330]: restx: Wunderground-PWS: Published 
record 2018-10-08 20:40:00 CEST (1539024000)
Oct  8 20:40:15 meteo weewx[20330]: restx: WeatherCloud: Published record 
2018-10-08 20:40:00 CEST (1539024000)
Oct  8 20:40:19 meteo weewx[20330]: wmr300x: read counts; Loop: 135; TH_0: 
11; TH_1: 16; TH_2: 10; TH_3: 10; TH_4: 10; TH_5: 10; TH_6: 10; TH_7: 10; 
TH_8: 10; barom: 10; forecast: 10; rain: 12; wind: 16
Oct  8 20:40:19 meteo weewx[20330]: wmr300x: write counts;
Oct  8 20:40:36 meteo weewx[20330]: cheetahgenerator: Generated 10 files 
for report StandardReport in 20.88 seconds
Oct  8 20:40:39 meteo weewx[20330]: wmr300x: read counts; Loop: 135; TH_0: 
10; TH_1: 16; TH_2: 10; TH_3: 10; TH_4: 10; TH_5: 10; TH_6: 10; TH_7: 10; 
TH_8: 10; barom: 11; forecast: 10; rain: 12; wind: 16; x57: 1
Oct  8 20:40:39 meteo weewx[20330]: wmr300x: write counts; xa6: 1
Oct  8 20:40:49 meteo weewx[20330]: imagegenerator: Generated 9 images for 
StandardReport in 13.02 seconds
Oct  8 20:40:49 meteo weewx[20330]: copygenerator: copied 0 files to 
/var/www/html/weewx
Oct  8 20:40:50 meteo weewx[20330]: cheetahgenerator: Generated 1 files for 
report TiempoElche in 0.53 seconds
Oct  8 20:40:56 meteo weewx[20330]: imagegenerator: Generated 8 images for 
TiempoElche in 6.80 seconds
Oct  8 20:40:56 meteo weewx[20330]: copygenerator: copied 0 files to 
/var/www/html/weewx/TiempoElche
Oct  8 20:41:00 meteo weewx[20330]: wmr300x: read counts; Loop: 49; TH_0: 
3; TH_1: 6; TH_2: 4; TH_3: 3; TH_4: 4; TH_5: 4; TH_6: 4; TH_7: 4; TH_8: 3; 
barom: 3; forecast: 4; rain: 5; wind: 6; x57: 1
Oct  8 20:41:00 meteo weewx[20330]: wmr300x: write counts; xa6: 1
Oct  8 20:41:10 meteo weewx[20330]: ftpgenerator: ftp'd 28 files in 13.77 
seconds
Oct  8 20:41:20 meteo weewx[20330]: wmr300x: read counts;
Oct  8 20:41:20 meteo weewx[20330]: wmr300x: write counts;
Oct  8 20:41:29 meteo weewx[20330]: wmr300x: Loop data packets in heartbeat 
interval = 0
Oct  8 20:41:30 meteo weewx[20330]: wmr300x: No loop data in heartbeat 
interval,  restarting
Oct  8 20:41:40 meteo weewx[20330]: wmr300x: read counts;
Oct  8 20:41:40 meteo weewx[20330]: wmr300x: write counts;
Oct  8 20:41:54 meteo weewx[20330]: wmr300x: Loop data packets in heartbeat 
interval = 0
Oct  8 20:41:54 meteo weewx[20330]: wmr300x: No loop data in heartbeat 
interval,  restarting
Oct  8 20:42:00 meteo weewx[20330]: wmr300x: read counts;
Oct  8 20:42:00 meteo weewx[20330]: wmr300x: write counts;
Oct  8 20:42:18 meteo weewx[20330]: wmr300x: Loop data packets in heartbeat 
interval = 0
Oct  8 20:42:18 meteo weewx[20330]: wmr300x: No loop data in heartbeat 
interval,  restarting
Oct  8 20:42:20 meteo weewx[20330]: wmr300x: read counts;
Oct  8 20:42:20 meteo weewx[20330]: wmr300x: write counts;

And a lot of log lines like these.

pi@meteo:~ $ lsusb
Bus 001 Device 002: ID 0fde:ca08 Oregon Scientific
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@meteo:~ $

Then trying to restart weewx:

Oct  8 21:51:57 meteo weewx[8577]: wmr300x: history limit is 6% at index 
1994
Oct  8 21:51:57 meteo weewx[8577]: wmr300x: using PyUSB backend: libusb1
Oct  8 21:51:57 meteo kernel: [337451.298735] Indeed it is in host mode 
hprt0 = 00021501
Oct  8 21:51:58 meteo kernel: [337451.505449] usb 1-1: reset full-speed USB 
device number 2 using dwc_otg
Oct  8 21:51:58 meteo kernel: [337451.505671] Indeed it is in host mode 
hprt0 = 00021501
Oct  8 21:52:15 meteo weewx[8577]: import of driver failed: Init comm 
failed after 3 tries ()
Oct  8 21:52:15 meteo weewx[8577]: engine: Unable to load driver: Init comm 
failed after 3 tries
Oct  8 21:52:15 meteo weewx[8577]:   Exiting...

I have had to reboot the raspberry and after that weewx went up again.

Thank's

-- 
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: Belchertown Skin and MQTT With Username Not Working

[Philip Kutzenco]

 I have it working on my own externally hosted Mosquitto server (on Digital 
Ocean). My Mosquitto MQTT broker is set up requiring a username and 
password for publishing. Additionally it has TLS/SSL implemented (with 
Let's Encrypt certificates). It allows subscribing anonymously and also 
runs Websockets so that it can feedthe Belchertown skin. I used Pat's MQTT 
"tutorial"  to 
do this. My website is https://wx.kutzenco.com.

phil

On Monday, October 8, 2018 at 10:21:50 AM UTC-4, G Hammer wrote:
>
>
> Does anyone have the Belchertown skin working with MQTT using a server 
> that requires a username and password such as CloudMQTT?
>
> I have tried several different ways of configuring the skin and it fails 
> to connect or it shows 'Connecting to weather station real time data' 
> forever without connecting.
> The data is being sent to the server fine and I have subscribed to it 
> using client software (see below).
>
> Thanks for any input, I'm at a loss here.
>
> [image: wxmqtt.png]
>
>

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

[weewx-user] Re: Belchertown Skin and MQTT With Username Not Working

[Philip Kutzenco]

I have it working on my own externally hosted Mosquitto server (on Digital 
Ocean). My Mosquiutto MQTT broker is set up requiring a username and 
password for publishing. Additionally it has TLS/SSL implemented (with 
Let's Encrypt certificates). It allows subscribing anonymously and also 
runs Websockets so that it can feedthe Belchertown skin. I used Pat's MQTT 
"tutorial"  to 
do this. My website is https://wx.kutzenco.com.

phil

On Monday, October 8, 2018 at 10:21:50 AM UTC-4, G Hammer wrote:
>
>
> Does anyone have the Belchertown skin working with MQTT using a server 
> that requires a username and password such as CloudMQTT?
>
> I have tried several different ways of configuring the skin and it fails 
> to connect or it shows 'Connecting to weather station real time data' 
> forever without connecting.
> The data is being sent to the server fine and I have subscribed to it 
> using client software (see below).
>
> Thanks for any input, I'm at a loss here.
>
> [image: wxmqtt.png]
>
>

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

Re: [weewx-user] Re: Useing wlink and archive interval

[Ruben Navarro Huedo]

It is weatherlink and it is uploading to weatherlink.com each minute.
I am using weatherlink 2.0.

El lunes, 8 de octubre de 2018, 18:16:53 (UTC+2), Thomas Keffer escribió:
>
> For Vantage stations, WeeWX uses the archive interval you have set in the 
> wlink logger. If you want to change it, either change it through your 
> console, or use the utility wee_device with the --set-interval 
>  option.
>
> -tk
>
> On Mon, Oct 8, 2018 at 8:41 AM Ruben Navarro Huedo  > wrote:
>
>> I think is is downloading only archive data and not instant data.
>>
>>
>> El lunes, 8 de octubre de 2018, 17:09:43 (UTC+2), Ruben Navarro Huedo 
>> escribió:
>>>
>>> Hello friends:
>>>
>>> Using wlink with last 3.8.2 weewx.
>>> Why archive interval is 1800?
>>> weatherlink.com is updated very each seconds... whey can't i have data 
>>> using wlink with a lower interval?
>>>
>>> Thank's
>>>
>>> Oct  8 17:06:35 working weewx[5849]: wxcalculate: The following 
>>> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>>> Oct  8 17:06:35 working weewx[5849]: engine: Finished loading service 
>>> weewx.wxservices.StdWXCalculate
>>> Oct  8 17:06:35 working weewx[5849]: engine: Loading service 
>>> weewx.engine.StdArchive
>>> Oct  8 17:06:35 working weewx[5849]: engine: Archive will use data 
>>> binding wx_binding
>>> Oct  8 17:06:35 working weewx[5849]: engine: Record generation will be 
>>> attempted in 'hardware'
>>> Oct  8 17:06:35 working weewx[5849]: wlink: downloading archive interval
>>> Oct  8 17:06:36 working weewx[5849]: wlink: found archive interval: 
>>> ArchiveInt=30
>>> Oct  8 17:06:36 working weewx[5849]: engine: The archive interval in the 
>>> configuration file (300) does not match the station hardware interval 
>>> (1800).
>>> Oct  8 17:06:36 working weewx[5849]: engine: Using archive interval of 
>>> 1800 seconds (specified by hardware)
>>> Oct  8 17:06:36 working weewx[5849]: engine: Use LOOP data in hi/low 
>>> calculations: 1
>>> Oct  8 17:06:36 working weewx[5849]: manager: Daily summary version is 
>>> 2.0
>>> Oct  8 17:06:36 working weewx[5849]: engine: Using binding 'wx_binding' 
>>> to database 'cabo.sdb'
>>> Oct  8 17:06:36 working weewx[5849]: manager: Starting backfill of daily 
>>> summaries
>>> Oct  8 17:06:36 working weewx[5849]: engine: Finished loading service 
>>> weewx.engine.StdArchive
>>> Oct  8 17:06:36 working weewx[5849]: engine: Loading service 
>>> weewx.restx.StdStationRegistry
>>> Oct  8 17:06:36 working weewx[5849]: restx: StationRegistry: 
>>> Registration not requested.
>>> Oct  8 17:06:36 working weewx[5849]: engine: Finished loading service 
>>> weewx.restx.StdStationRegistry
>>> Oct  8 17:06:36 working weewx[5849]: engine: Loading service 
>>> weewx.engine.StdPrint
>>> Oct  8 17:06:36 working weewx[5849]: engine: Finished loading service 
>>> weewx.engine.StdPrint
>>> Oct  8 17:06:36 working weewx[5849]: engine: Loading service 
>>> weewx.engine.StdReport
>>> Oct  8 17:06:36 working weewx[5849]: engine: Finished loading service 
>>> weewx.engine.StdReport
>>> Oct  8 17:06:36 working weewx[5849]: engine: Starting up weewx version 
>>> 3.8.2
>>>
>>> -- 
>> 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] SFTP extension problem

[Thomas Keffer]

Matthew's version of sftp.py has a typo. Go to line 62 and add a closing
parenthesis to the end of the line. Instead of this:

logdbg("remote_root=%s" % self.remote_root)
logdbg("server=%s port=%s user=%s" % (server, port, user)

def run(self):

you want this:

logdbg("remote_root=%s" % self.remote_root)
logdbg("server=%s port=%s user=%s" % (server, port, user))

def run(self):

-tk

On Mon, Oct 8, 2018 at 11:09 AM  wrote:

> Hi
>
> I am trying to use SFTP to upload my files to a domain hosted at 1&1,
> which seems to use SFTP, so the old FTP process doesn't work.  I installed
> pysftp, successfully, as required.
>
> I am trying to use Matthew Wall's SFTP extension, but get the following
> errors:
>
> Oct  8 18:55:20 raspberrypi weewx[17094]: cheetahgenerator: Generated 14
> files for report StandardReport in 3.58 seconds
> Oct  8 18:55:20 raspberrypi weewx[17094]: manager: Daily summary version
> is 2.0
> Oct  8 18:55:21 raspberrypi weewx[17094]: imagegenerator: Generated 12
> images for StandardReport in 0.67 seconds
> Oct  8 18:55:21 raspberrypi weewx[17094]: copygenerator: copied 9 files to
> /var/www/html/weewx
> Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Running report sftp
> Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Found
> configuration file /etc/weewx/skins/sftp/skin.conf for report sftp
> Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Unable to
> instantiate generator user.sftp.SFTPGenerator
> Oct  8 18:55:21 raspberrypi weewx[17094]:   invalid syntax
> (sftp.py, line 64)
> Oct  8 18:55:21 raspberrypi weewx[17094]:   Traceback (most
> recent call last):
> Oct  8 18:55:21 raspberrypi weewx[17094]: File
> "/usr/share/weewx/weewx/reportengine.py", line 220, in run
> Oct  8 18:55:21 raspberrypi weewx[17094]:   obj =
> weeutil.weeutil._get_object(generator)(
> Oct  8 18:55:21 raspberrypi weewx[17094]: File
> "/usr/share/weewx/weeutil/weeutil.py", line 1132, in _get_object
> Oct  8 18:55:21 raspberrypi weewx[17094]:   mod =
> __import__(module)
> Oct  8 18:55:21 raspberrypi weewx[17094]: File
> "/usr/share/weewx/user/sftp.py", line 64
> Oct  8 18:55:21 raspberrypi weewx[17094]:   def run(self):
> Oct  8 18:55:21 raspberrypi weewx[17094]: ^
> Oct  8 18:55:21 raspberrypi weewx[17094]:   SyntaxError:
> invalid syntax
> Oct  8 18:55:21 raspberrypi weewx[17094]:   Generator ignored
> Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Running report FTP
> Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Found
> configuration file /etc/weewx/skins/Ftp/skin.conf for report FTP
> Oct  8 18:55:21 raspberrypi weewx[17094]: ftpgenerator: FTP upload not
> requested. Skipped.
> Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Running report
> RSYNC
> Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Found
> configuration file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
> Oct  8 18:55:21 raspberrypi weewx[17094]: rsyncgenerator: rsync upload not
> requested. Skipped.
>
> The sftp content of weewx conf is as follows (confidential details
> removed):
>
> [[sftp]]
> server = xxx
> user = x
> skin = sftp
> path = /weather
> password = xx  [I put this in single quotes, as the default
> content seemed to suggest that]
> port = 22
>
> Anyone have any ideas what is going wrong please?
>
> Thanks
>
> David.
>
> --
> 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] SFTP extension problem

[dhindley]

Hi

I am trying to use SFTP to upload my files to a domain hosted at 1&1, which 
seems to use SFTP, so the old FTP process doesn't work.  I installed 
pysftp, successfully, as required.

I am trying to use Matthew Wall's SFTP extension, but get the following 
errors:

Oct  8 18:55:20 raspberrypi weewx[17094]: cheetahgenerator: Generated 14 
files for report StandardReport in 3.58 seconds
Oct  8 18:55:20 raspberrypi weewx[17094]: manager: Daily summary version is 
2.0
Oct  8 18:55:21 raspberrypi weewx[17094]: imagegenerator: Generated 12 
images for StandardReport in 0.67 seconds
Oct  8 18:55:21 raspberrypi weewx[17094]: copygenerator: copied 9 files to 
/var/www/html/weewx
Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Running report sftp
Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Found configuration 
file /etc/weewx/skins/sftp/skin.conf for report sftp
Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Unable to 
instantiate generator user.sftp.SFTPGenerator
Oct  8 18:55:21 raspberrypi weewx[17094]:   invalid syntax 
(sftp.py, line 64)
Oct  8 18:55:21 raspberrypi weewx[17094]:   Traceback (most 
recent call last):
Oct  8 18:55:21 raspberrypi weewx[17094]: File 
"/usr/share/weewx/weewx/reportengine.py", line 220, in run
Oct  8 18:55:21 raspberrypi weewx[17094]:   obj = 
weeutil.weeutil._get_object(generator)(
Oct  8 18:55:21 raspberrypi weewx[17094]: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1132, in _get_object
Oct  8 18:55:21 raspberrypi weewx[17094]:   mod = 
__import__(module)
Oct  8 18:55:21 raspberrypi weewx[17094]: File 
"/usr/share/weewx/user/sftp.py", line 64
Oct  8 18:55:21 raspberrypi weewx[17094]:   def run(self):
Oct  8 18:55:21 raspberrypi weewx[17094]: ^
Oct  8 18:55:21 raspberrypi weewx[17094]:   SyntaxError: 
invalid syntax
Oct  8 18:55:21 raspberrypi weewx[17094]:   Generator ignored
Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Running report FTP
Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Found configuration 
file /etc/weewx/skins/Ftp/skin.conf for report FTP
Oct  8 18:55:21 raspberrypi weewx[17094]: ftpgenerator: FTP upload not 
requested. Skipped.
Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Running report RSYNC
Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Found configuration 
file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
Oct  8 18:55:21 raspberrypi weewx[17094]: rsyncgenerator: rsync upload not 
requested. Skipped.

The sftp content of weewx conf is as follows (confidential details removed):

[[sftp]]
server = xxx
user = x
skin = sftp
path = /weather
password = xx  [I put this in single quotes, as the default 
content seemed to suggest that]
port = 22

Anyone have any ideas what is going wrong please?

Thanks

David.

-- 
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] Belchertown Skin and MQTT With Username Not Working

[Colin Larsen]

Not working yet as far as I know.

On Tue, 9 Oct 2018, 03:21 G Hammer,  wrote:

>
> Does anyone have the Belchertown skin working with MQTT using a server
> that requires a username and password such as CloudMQTT?
>
> I have tried several different ways of configuring the skin and it fails
> to connect or it shows 'Connecting to weather station real time data'
> forever without connecting.
> The data is being sent to the server fine and I have subscribed to it
> using client software (see below).
>
> Thanks for any input, I'm at a loss here.
>
> [image: wxmqtt.png]
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> 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: Useing wlink and archive interval

[Thomas Keffer]

For Vantage stations, WeeWX uses the archive interval you have set in the
wlink logger. If you want to change it, either change it through your
console, or use the utility wee_device with the --set-interval
 option.

-tk

On Mon, Oct 8, 2018 at 8:41 AM Ruben Navarro Huedo 
wrote:

> I think is is downloading only archive data and not instant data.
>
>
> El lunes, 8 de octubre de 2018, 17:09:43 (UTC+2), Ruben Navarro Huedo
> escribió:
>>
>> Hello friends:
>>
>> Using wlink with last 3.8.2 weewx.
>> Why archive interval is 1800?
>> weatherlink.com is updated very each seconds... whey can't i have data
>> using wlink with a lower interval?
>>
>> Thank's
>>
>> Oct  8 17:06:35 working weewx[5849]: wxcalculate: The following
>> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>> Oct  8 17:06:35 working weewx[5849]: engine: Finished loading service
>> weewx.wxservices.StdWXCalculate
>> Oct  8 17:06:35 working weewx[5849]: engine: Loading service
>> weewx.engine.StdArchive
>> Oct  8 17:06:35 working weewx[5849]: engine: Archive will use data
>> binding wx_binding
>> Oct  8 17:06:35 working weewx[5849]: engine: Record generation will be
>> attempted in 'hardware'
>> Oct  8 17:06:35 working weewx[5849]: wlink: downloading archive interval
>> Oct  8 17:06:36 working weewx[5849]: wlink: found archive interval:
>> ArchiveInt=30
>> Oct  8 17:06:36 working weewx[5849]: engine: The archive interval in the
>> configuration file (300) does not match the station hardware interval
>> (1800).
>> Oct  8 17:06:36 working weewx[5849]: engine: Using archive interval of
>> 1800 seconds (specified by hardware)
>> Oct  8 17:06:36 working weewx[5849]: engine: Use LOOP data in hi/low
>> calculations: 1
>> Oct  8 17:06:36 working weewx[5849]: manager: Daily summary version is 2.0
>> Oct  8 17:06:36 working weewx[5849]: engine: Using binding 'wx_binding'
>> to database 'cabo.sdb'
>> Oct  8 17:06:36 working weewx[5849]: manager: Starting backfill of daily
>> summaries
>> Oct  8 17:06:36 working weewx[5849]: engine: Finished loading service
>> weewx.engine.StdArchive
>> Oct  8 17:06:36 working weewx[5849]: engine: Loading service
>> weewx.restx.StdStationRegistry
>> Oct  8 17:06:36 working weewx[5849]: restx: StationRegistry: Registration
>> not requested.
>> Oct  8 17:06:36 working weewx[5849]: engine: Finished loading service
>> weewx.restx.StdStationRegistry
>> Oct  8 17:06:36 working weewx[5849]: engine: Loading service
>> weewx.engine.StdPrint
>> Oct  8 17:06:36 working weewx[5849]: engine: Finished loading service
>> weewx.engine.StdPrint
>> Oct  8 17:06:36 working weewx[5849]: engine: Loading service
>> weewx.engine.StdReport
>> Oct  8 17:06:36 working weewx[5849]: engine: Finished loading service
>> weewx.engine.StdReport
>> Oct  8 17:06:36 working weewx[5849]: engine: Starting up weewx version
>> 3.8.2
>>
>> --
> 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: memory is full

[Thomas Keffer]

WeeWX uses the system log, generally /var/log/syslog

See the documentation for *Where to find things
*.

-tk

On Mon, Oct 8, 2018 at 7:52 AM Andre Rieth  wrote:

>
> Hello I have now found out why the hard drive has become full. FHEM is
> still running parallel on the Banana PI. I have now deleted the log files
> from FHEM and won 37GB. Where does Weewx store his log? greetings André
>
> Am Mittwoch, 26. September 2018 17:47:06 UTC+2 schrieb Andre Rieth:
>>
>> Hello
>>
>> I've run weewx on a banana pi.
>> There I connected a 60GB ssd which is now full.
>> How can I delete old files?
>> I have mysql set up.
>> greetings
>> André
>>
>> --
> 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: Useing wlink and archive interval

[Ruben Navarro Huedo]

I think is is downloading only archive data and not instant data.


El lunes, 8 de octubre de 2018, 17:09:43 (UTC+2), Ruben Navarro Huedo 
escribió:
>
> Hello friends:
>
> Using wlink with last 3.8.2 weewx.
> Why archive interval is 1800?
> weatherlink.com is updated very each seconds... whey can't i have data 
> using wlink with a lower interval?
>
> Thank's
>
> Oct  8 17:06:35 working weewx[5849]: wxcalculate: The following algorithms 
> will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> Oct  8 17:06:35 working weewx[5849]: engine: Finished loading service 
> weewx.wxservices.StdWXCalculate
> Oct  8 17:06:35 working weewx[5849]: engine: Loading service 
> weewx.engine.StdArchive
> Oct  8 17:06:35 working weewx[5849]: engine: Archive will use data binding 
> wx_binding
> Oct  8 17:06:35 working weewx[5849]: engine: Record generation will be 
> attempted in 'hardware'
> Oct  8 17:06:35 working weewx[5849]: wlink: downloading archive interval
> Oct  8 17:06:36 working weewx[5849]: wlink: found archive interval: 
> ArchiveInt=30
> Oct  8 17:06:36 working weewx[5849]: engine: The archive interval in the 
> configuration file (300) does not match the station hardware interval 
> (1800).
> Oct  8 17:06:36 working weewx[5849]: engine: Using archive interval of 
> 1800 seconds (specified by hardware)
> Oct  8 17:06:36 working weewx[5849]: engine: Use LOOP data in hi/low 
> calculations: 1
> Oct  8 17:06:36 working weewx[5849]: manager: Daily summary version is 2.0
> Oct  8 17:06:36 working weewx[5849]: engine: Using binding 'wx_binding' to 
> database 'cabo.sdb'
> Oct  8 17:06:36 working weewx[5849]: manager: Starting backfill of daily 
> summaries
> Oct  8 17:06:36 working weewx[5849]: engine: Finished loading service 
> weewx.engine.StdArchive
> Oct  8 17:06:36 working weewx[5849]: engine: Loading service 
> weewx.restx.StdStationRegistry
> Oct  8 17:06:36 working weewx[5849]: restx: StationRegistry: Registration 
> not requested.
> Oct  8 17:06:36 working weewx[5849]: engine: Finished loading service 
> weewx.restx.StdStationRegistry
> Oct  8 17:06:36 working weewx[5849]: engine: Loading service 
> weewx.engine.StdPrint
> Oct  8 17:06:36 working weewx[5849]: engine: Finished loading service 
> weewx.engine.StdPrint
> Oct  8 17:06:36 working weewx[5849]: engine: Loading service 
> weewx.engine.StdReport
> Oct  8 17:06:36 working weewx[5849]: engine: Finished loading service 
> weewx.engine.StdReport
> Oct  8 17:06:36 working weewx[5849]: engine: Starting up weewx version 
> 3.8.2
>
>

-- 
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: Belchertown skin for weewx now available!

[Praveen Chandrasekaran]

Trying to embed rainviewr map into my belchertown page.

Here is the embed  link I got:

https://www.rainviewer.com/?loc=13.0026,77.8374,11=1=0=0=1=1=1=4=1=83=0=0;
 
width="100%" frameborder="0" style="border:0;height:50vh;" 
allowfullscreen>

I modified it to add appropriate height and width and removed 
allowfullscreen. However my radar image is still blank.

Link to my page:

http://bedi.co.in:15000/pc-aws/weather/belchertown/

What am I missing? Unfortunately windy doesnt have radars for India hence 
using rainviewr.


On Wednesday, 22 August 2018 00:15:13 UTC+5:30, Pat wrote:
>
> The Belchertown skin for weewx is now available. This skin is modeled 
> after https://belchertownweather.com 
>
> The skin features
>
>- Real time streaming updates on the front page without needing to 
>reload the site (weewx-mqtt extension required)
>- Forecast data updated every hour without needing to reload (a free 
>DarkSky API key required)
>- Information on your closest Earthquake updated automatically every 3 
>hours
>- Weather station observation graphs which update without needing to 
>reload
>- Weather records for the current year, and for all time
>- A mobile and iPad ready display. You could use an iPad as a "2nd 
>console". 
>
> There are dozens of options to configure within the skin. Please view the 
> readme on GitHub  for a 
> detailed explanation. 
>
> The GitHub page: https://github.com/poblabs/weewx-belchertown
>
> Direct download of v0.1: 
> https://github.com/poblabs/weewx-belchertown/archive/weewx-belchertown-0.1.tar.gz
>
> Quick install:
>
> wget https://
> github.com/poblabs/weewx-belchertown/archive/weewx-belchertown-0.1.tar.gz
>
> sudo wee_extension --install weewx-belchertown-0.1.tar.gz
>
> Configure weewx.conf with your options
>
> Restart weewx
>
> Out of the box, it is a very basic theme. Make sure to check out the readme 
> for all options available !
>
>
> This is my first skin, and I've done all I could to test it out in various 
> environments to iron out any initial bugs. If you do find something that's 
> a little off, or room for improvement, please let me know!
>
>

-- 
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] Useing wlink and archive interval

[Ruben Navarro Huedo]

Hello friends:

Using wlink with last 3.8.2 weewx.
Why archive interval is 1800?
weatherlink.com is updated very each seconds... whey can't i have data 
using wlink with a lower interval?

Thank's

Oct  8 17:06:35 working weewx[5849]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Oct  8 17:06:35 working weewx[5849]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Oct  8 17:06:35 working weewx[5849]: engine: Loading service 
weewx.engine.StdArchive
Oct  8 17:06:35 working weewx[5849]: engine: Archive will use data binding 
wx_binding
Oct  8 17:06:35 working weewx[5849]: engine: Record generation will be 
attempted in 'hardware'
Oct  8 17:06:35 working weewx[5849]: wlink: downloading archive interval
Oct  8 17:06:36 working weewx[5849]: wlink: found archive interval: 
ArchiveInt=30
Oct  8 17:06:36 working weewx[5849]: engine: The archive interval in the 
configuration file (300) does not match the station hardware interval 
(1800).
Oct  8 17:06:36 working weewx[5849]: engine: Using archive interval of 1800 
seconds (specified by hardware)
Oct  8 17:06:36 working weewx[5849]: engine: Use LOOP data in hi/low 
calculations: 1
Oct  8 17:06:36 working weewx[5849]: manager: Daily summary version is 2.0
Oct  8 17:06:36 working weewx[5849]: engine: Using binding 'wx_binding' to 
database 'cabo.sdb'
Oct  8 17:06:36 working weewx[5849]: manager: Starting backfill of daily 
summaries
Oct  8 17:06:36 working weewx[5849]: engine: Finished loading service 
weewx.engine.StdArchive
Oct  8 17:06:36 working weewx[5849]: engine: Loading service 
weewx.restx.StdStationRegistry
Oct  8 17:06:36 working weewx[5849]: restx: StationRegistry: Registration 
not requested.
Oct  8 17:06:36 working weewx[5849]: engine: Finished loading service 
weewx.restx.StdStationRegistry
Oct  8 17:06:36 working weewx[5849]: engine: Loading service 
weewx.engine.StdPrint
Oct  8 17:06:36 working weewx[5849]: engine: Finished loading service 
weewx.engine.StdPrint
Oct  8 17:06:36 working weewx[5849]: engine: Loading service 
weewx.engine.StdReport
Oct  8 17:06:36 working weewx[5849]: engine: Finished loading service 
weewx.engine.StdReport
Oct  8 17:06:36 working weewx[5849]: engine: Starting up weewx version 3.8.2

-- 
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] Importing other data

[Andre Rieth]

Hello Besides weewx, I have an environmental station based on easyesp. Is 
there a way to import the data from there and output it by graphics. In 
addition to temperature and humidity, I also have dust particles and 
radioactive radiation. I would be happy if it is possible. greetings André

-- 
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: memory is full

[Andre Rieth]

Hello I have now found out why the hard drive has become full. FHEM is 
still running parallel on the Banana PI. I have now deleted the log files 
from FHEM and won 37GB. Where does Weewx store his log? greetings André

Am Mittwoch, 26. September 2018 17:47:06 UTC+2 schrieb Andre Rieth:
>
> Hello
>
> I've run weewx on a banana pi.
> There I connected a 60GB ssd which is now full.
> How can I delete old files?
> I have mysql set up.
> greetings
> André
>
>

-- 
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] Belchertown Skin and MQTT With Username Not Working

[G Hammer]

Does anyone have the Belchertown skin working with MQTT using a server that 
requires a username and password such as CloudMQTT?

I have tried several different ways of configuring the skin and it fails to 
connect or it shows 'Connecting to weather station real time data' forever 
without connecting.
The data is being sent to the server fine and I have subscribed to it using 
client software (see below).

Thanks for any input, I'm at a loss here.

[image: wxmqtt.png]

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

[weewx-user] Re: RainMachine API for weewx- Driver Wanted/Needed

[G Hammer]

It is posting at the correct time currently.
I'll check again after DST ends, but no reason to think it won't follow the 
change.


On Monday, October 8, 2018 at 2:06:01 AM UTC-4, nicu@rainmachine.com 
wrote:
>
>
>
> On Friday, October 5, 2018 at 6:05:50 PM UTC-7, G Hammer wrote:
>>
>> The Mini-8 is receiving and using the push data.
>> Seems it wanted to go past midnight to show proper status on the Mini-8.
>> In any event, all seems to be working well. No further Warnings in the 
>> Mini-8 logs and the 3 weather sources I have enabled all show a green 
>> Success on the dashboard.
>>
>
> Great, keep me posted if the data is correct at the right date/time.
>
> Thanks,
> Nicu 
>

-- 
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: Rsync vs FTP - which to choose/what are the pros and cons?

[Thomas Keffer]

Good suggestion. Done in commit 790715

.

On Mon, Oct 8, 2018 at 5:33 AM Philip Kutzenco  wrote:

> Thomas,
>
> Can I make a request that the Rsync block in the initially default
> weewx.conf file be updated (for the next version) to include the following
> lines (which are included in the default weewx.conf FTP block but not the
> default weewx.conf RSYNC block):
>
> # To upload files from something other than what HTML_ROOT is set
> # to above, specify a different HTML_ROOT here.
> #HTML_ROOT = public_html
>
> It may be obvious to others, but it wasn't to me initially, that you need
> to specify that variable in the block to upload files generated by a
> specific skin. If you don't add an explicit HTML_ROOT definition in that
> block, the default HTML_ROOT definition from the beginning of weewx.conf is
> used.
>
> By the way, I've gotten my external website set up and working great using
> Rsync to feed my weewx output files there. Thanks to everyone for weewx
> help and to you, in particular, for the terrific weewx software!!
>
> phil
>
> On Friday, October 5, 2018 at 5:26:09 PM UTC-4, Philip Kutzenco wrote:
>>
>> I am moving my weewx web server output to an outside hoster. What
>> considerations should I take into account to decide whether to use Rsync or
>> FTP (both should be available to me). I've looked at the user guide
>> sections for both options and (optimistically) believe I will be able to
>> set up either.
>>
>> What are the pros & cons of each method?
>>
>> Apologies if this question has been asked/answered before. If so, please
>> point me to the discussion or wiki topic.
>>
>> phil
>>
> --
> 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: Rsync vs FTP - which to choose/what are the pros and cons?

[Philip Kutzenco]

Thomas,

Can I make a request that the Rsync block in the initially default 
weewx.conf file be updated (for the next version) to include the following 
lines (which are included in the default weewx.conf FTP block but not the 
default weewx.conf RSYNC block):

# To upload files from something other than what HTML_ROOT is set
# to above, specify a different HTML_ROOT here.
#HTML_ROOT = public_html

It may be obvious to others, but it wasn't to me initially, that you need 
to specify that variable in the block to upload files generated by a 
specific skin. If you don't add an explicit HTML_ROOT definition in that 
block, the default HTML_ROOT definition from the beginning of weewx.conf is 
used.

By the way, I've gotten my external website set up and working great using 
Rsync to feed my weewx output files there. Thanks to everyone for weewx 
help and to you, in particular, for the terrific weewx software!!

phil

On Friday, October 5, 2018 at 5:26:09 PM UTC-4, Philip Kutzenco wrote:
>
> I am moving my weewx web server output to an outside hoster. What 
> considerations should I take into account to decide whether to use Rsync or 
> FTP (both should be available to me). I've looked at the user guide 
> sections for both options and (optimistically) believe I will be able to 
> set up either.
>
> What are the pros & cons of each method?
>
> Apologies if this question has been asked/answered before. If so, please 
> point me to the discussion or wiki topic.
>
> phil
>

-- 
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: RainMachine API for weewx- Driver Wanted/Needed

[nicu . pavel]

On Friday, October 5, 2018 at 6:05:50 PM UTC-7, G Hammer wrote:
>
> The Mini-8 is receiving and using the push data.
> Seems it wanted to go past midnight to show proper status on the Mini-8.
> In any event, all seems to be working well. No further Warnings in the 
> Mini-8 logs and the 3 weather sources I have enabled all show a green 
> Success on the dashboard.
>

Great, keep me posted if the data is correct at the right date/time.

Thanks,
Nicu 

-- 
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.