[weewx-user] weewx.sdb backups

[Scott Grayban]

How is everyone doing backups for weewx.sdb ?

I thought about doing a aws backup using a fuse setup.

Are there easier ways to do this ?

-- 
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: Beta testers for v3.9.0 needed

[mwall]

On Tuesday, January 22, 2019 at 10:41:54 PM UTC-5, vince wrote:
>
> On Tuesday, January 22, 2019 at 12:05:24 PM UTC-8, Thomas Keffer wrote:
>>
>> It's been well over a year since the last "dot" release, but the V3.9 
>> release is finally in sight!
>>
>
> Seasons skin has two different looks on the images for a debian:latest 
> (9.6) docker container clean installation.
> Current looks nice and crisp.  Others are bolder and very fuzzy.
> Install was setup.py of course.
>

vince,

are you sure that was a *really* clean install?  when you uninstall weewx, 
the reports (nominally /var/www/html/weewx) and data (nominally 
/var/lib/weewx) will not be removed.  you have to delete those manually.

perhaps the non-current plots are left over from a previous installation?

m 

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

[weewx-user] Re: Beta testers for v3.9.0 needed

[vince]

On Tuesday, January 22, 2019 at 12:05:24 PM UTC-8, Thomas Keffer wrote:
>
> It's been well over a year since the last "dot" release, but the V3.9 
> release is finally in sight!
>
>
Seasons skin has two different looks on the images for a debian:latest 
(9.6) docker container clean installation.
Current looks nice and crisp.  Others are bolder and very fuzzy.
Install was setup.py of course.

Dockerfile 
is https://github.com/vinceskahan/weewx-docker/blob/master/weebian/Dockerfile 
lightly edited to install the 3.9b1 tgz file



-- 
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: Beta testers for v3.9.0 needed

[mercurystorm]

Thanks that fixed it

On Wednesday, 23 January 2019 01:05:59 UTC, Thomas Keffer wrote:
>
> Yup. It looks like wee_database lost executable permission somewhere along 
> the way. I've corrected it in commit 1e9b0 
> 
> .
>
> You can fix your installation with
>
> *sudo chmod +x /usr/share/weewx/wee_database*
>
> -tk
>
>
> On Tue, Jan 22, 2019 at 4:53 PM mercurystorm  > wrote:
>
>> root@raspberrypi:/usr/share/weewx# ls -l `which wee_database`
>> total 172
>> -rw-r--r-- 1 root root  2891 Jan 22 17:47 daemon.py
>> -rw-r--r-- 1 root root  2715 Jan 23 00:32 daemon.pyc
>> drwxr-xr-x 2 root root  4096 Jan 23 00:32 schemas
>> drwxr-xr-x 3 root root  4096 Jan 23 00:36 user
>> drwxr-xr-x 2 root root  4096 Jan 23 00:32 weecfg
>> -rwxr-xr-x 1 root root  5414 Jan 22 17:47 wee_config
>> -rw-r--r-- 1 root root 36533 Jan 22 17:47 wee_database
>> drwxr-xr-x 2 root root  4096 Jan 23 00:32 weedb
>> -rwxr-xr-x 1 root root 16154 Jan 22 17:47 wee_debug
>> -rwxr-xr-x 1 root root  1924 Jan 22 17:47 wee_device
>> -rwxr-xr-x 1 root root  3016 Jan 22 17:47 wee_extension
>> drwxr-xr-x 2 root root  4096 Jan 23 00:32 weeimport
>> -rwxr-xr-x 1 root root 31175 Jan 22 17:47 wee_import
>> drwxr-xr-x 2 root root  4096 Jan 23 00:35 weeplot
>> -rwxr-xr-x 1 root root  2171 Jan 22 17:47 wee_reports
>> drwxr-xr-x 2 root root  4096 Jan 23 00:36 weeutil
>> drwxr-xr-x 3 root root  4096 Jan 23 00:35 weewx
>> -rwxr-xr-x 1 root root  2566 Jan 22 17:47 weewxd
>> -rwxr-xr-x 1 root root 21132 Jan 22 17:47 wunderfixer
>> root@raspberrypi:/usr/share/weewx#
>>
>>
>> On Wednesday, 23 January 2019 00:49:55 UTC, Thomas Keffer wrote:
>>>
>>> Francis, can you check the permissions on the executables.
>>>
>>> For example,
>>>
>>> *ls -l `which wee_database`*
>>>
>>> -tk
>>>
>>>
>>> On Tue, Jan 22, 2019 at 4:45 PM Francis Yates  
>>> wrote:
>>>
 root@raspberrypi:~/software/weewx# systemctl stop weewx
 root@raspberrypi:~/software/weewx# wee_database --drop-daily
 Using configuration file /etc/weewx/weewx.conf
 Using database binding 'wx_binding', which is bound to database 
 'archive_mysql'
 Proceeding will delete all your daily summaries from database 'weewx'
 Are you sure you want to proceed (y/n)? y
 Dropping daily summary tables from 'weewx' ...
 Daily summary tables dropped from database 'weewx' in 2.84 seconds
 root@raspberrypi:~/software/weewx# dpkg -i weewx
 weewx_3.8.2-1_all.debweewx_3.9.0b1-1_all.deb  weewx-sdr-master/
 root@raspberrypi:~/software/weewx# dpkg -i weewx_3.9.0b1-1_all.deb
 (Reading database ... 45970 files and directories currently installed.)
 Preparing to unpack weewx_3.9.0b1-1_all.deb ...
 Unpacking weewx (3.9.0b1-1) over (3.8.2-1) ...
 Setting up weewx (3.9.0b1-1) ...

 Configuration file '/etc/weewx/weewx.conf'
  ==> Modified (by you or by a script) since installation.
  ==> Package distributor has shipped an updated version.
What would you like to do about it ?  Your options are:
 Y or I  : install the package maintainer's version
 N or O  : keep your currently-installed version
   D : show the differences between the versions
   Z : start a shell to examine the situation
  The default action is to keep your current version.
 *** weewx.conf (Y/I/N/O/D/Z) [default=N] ?
 Installing new version of config file /etc/weewx/weewx.conf.dist ...
 Installing new version of config file
 /etc/weewx/logwatch/scripts/services/weewx ...
 Installing new version of config file /etc/weewx/skins/Rsync/skin.conf 
 ...
 Installing new version of config file
 /etc/weewx/skins/Standard/index.html.tmpl ...
 Installing new version of config file 
 /etc/weewx/skins/Standard/skin.conf ...
 Installing new version of config file /etc/weewx/skins/Ftp/skin.conf ...
 Installing new version of config file /etc/weewx/import/wu-example.conf 
 ...
 Installing new version of config file 
 /etc/weewx/import/cumulus-example.conf ...
 Installing new version of config file 
 /etc/weewx/import/csv-example.conf ...
 saving previous config file as /etc/weewx/weewx.conf-3.8.2
 saving distribution config file as /etc/weewx/weewx.conf-3.9.0b1
 merging previous and distribution into /etc/weewx/weewx.conf
 Using configuration file /etc/weewx/weewx.conf-3.8.2
 Saved configuration to /etc/weewx/weewx.conf
 Processing triggers for systemd (232-25+deb9u8) ...
 root@raspberrypi:~/software/weewx# wee_database --rebuld-daily
 -su: /usr/bin/wee_database: Permission denied
 root@raspberrypi:~/software/weewx# wee_database --rebuld-daily
 -su: /usr/bin/wee_database: Permission denied
 root@raspberrypi:~/software/weewx# wee_database
 -su: /usr/bin/wee_database: Permission denied
 root@raspberrypi:~/software/weewx# systemctl status weewx
 ● weewx.service - LSB: we

Re: [weewx-user] Ambient Weather WS-2902A

[steeple ian]

Adnan,

Yes I can confirm that you can run weather34 alongside any other skin. The 
install process is slightly different from a regular weeWX skin but it works 
just fine with any other skin alongside.

Ian

> On 22 Jan 2019, at 21:39, Adnan Mumtaz  wrote:
> 
> Thanks Scott, you are so helpful. Ever tried Weather34 template using weewx ? 
> Is it possible to run 2 templates? 
> 
> On Tue, Jan 22, 2019 at 10:50 PM Scott Grayban  > wrote:
> There are a few ways to do this...
> 
> https://www.raspberrypi.org/documentation/linux/filesystem/backup.md 
> 
> 
> On Monday, January 21, 2019 at 8:24:40 PM UTC-8, Adnan Mumtaz wrote:
> Wonder how can I take a backup of all what I did.
> 
> 
> -- 
> 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 
> .

-- 
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: Beta testers for v3.9.0 needed

[Thomas Keffer]

Yup. It looks like wee_database lost executable permission somewhere along
the way. I've corrected it in commit 1e9b0

.

You can fix your installation with

*sudo chmod +x /usr/share/weewx/wee_database*

-tk


On Tue, Jan 22, 2019 at 4:53 PM mercurystorm  wrote:

> root@raspberrypi:/usr/share/weewx# ls -l `which wee_database`
> total 172
> -rw-r--r-- 1 root root  2891 Jan 22 17:47 daemon.py
> -rw-r--r-- 1 root root  2715 Jan 23 00:32 daemon.pyc
> drwxr-xr-x 2 root root  4096 Jan 23 00:32 schemas
> drwxr-xr-x 3 root root  4096 Jan 23 00:36 user
> drwxr-xr-x 2 root root  4096 Jan 23 00:32 weecfg
> -rwxr-xr-x 1 root root  5414 Jan 22 17:47 wee_config
> -rw-r--r-- 1 root root 36533 Jan 22 17:47 wee_database
> drwxr-xr-x 2 root root  4096 Jan 23 00:32 weedb
> -rwxr-xr-x 1 root root 16154 Jan 22 17:47 wee_debug
> -rwxr-xr-x 1 root root  1924 Jan 22 17:47 wee_device
> -rwxr-xr-x 1 root root  3016 Jan 22 17:47 wee_extension
> drwxr-xr-x 2 root root  4096 Jan 23 00:32 weeimport
> -rwxr-xr-x 1 root root 31175 Jan 22 17:47 wee_import
> drwxr-xr-x 2 root root  4096 Jan 23 00:35 weeplot
> -rwxr-xr-x 1 root root  2171 Jan 22 17:47 wee_reports
> drwxr-xr-x 2 root root  4096 Jan 23 00:36 weeutil
> drwxr-xr-x 3 root root  4096 Jan 23 00:35 weewx
> -rwxr-xr-x 1 root root  2566 Jan 22 17:47 weewxd
> -rwxr-xr-x 1 root root 21132 Jan 22 17:47 wunderfixer
> root@raspberrypi:/usr/share/weewx#
>
>
> On Wednesday, 23 January 2019 00:49:55 UTC, Thomas Keffer wrote:
>>
>> Francis, can you check the permissions on the executables.
>>
>> For example,
>>
>> *ls -l `which wee_database`*
>>
>> -tk
>>
>>
>> On Tue, Jan 22, 2019 at 4:45 PM Francis Yates 
>> wrote:
>>
>>> root@raspberrypi:~/software/weewx# systemctl stop weewx
>>> root@raspberrypi:~/software/weewx# wee_database --drop-daily
>>> Using configuration file /etc/weewx/weewx.conf
>>> Using database binding 'wx_binding', which is bound to database
>>> 'archive_mysql'
>>> Proceeding will delete all your daily summaries from database 'weewx'
>>> Are you sure you want to proceed (y/n)? y
>>> Dropping daily summary tables from 'weewx' ...
>>> Daily summary tables dropped from database 'weewx' in 2.84 seconds
>>> root@raspberrypi:~/software/weewx# dpkg -i weewx
>>> weewx_3.8.2-1_all.debweewx_3.9.0b1-1_all.deb  weewx-sdr-master/
>>> root@raspberrypi:~/software/weewx# dpkg -i weewx_3.9.0b1-1_all.deb
>>> (Reading database ... 45970 files and directories currently installed.)
>>> Preparing to unpack weewx_3.9.0b1-1_all.deb ...
>>> Unpacking weewx (3.9.0b1-1) over (3.8.2-1) ...
>>> Setting up weewx (3.9.0b1-1) ...
>>>
>>> Configuration file '/etc/weewx/weewx.conf'
>>>  ==> Modified (by you or by a script) since installation.
>>>  ==> Package distributor has shipped an updated version.
>>>What would you like to do about it ?  Your options are:
>>> Y or I  : install the package maintainer's version
>>> N or O  : keep your currently-installed version
>>>   D : show the differences between the versions
>>>   Z : start a shell to examine the situation
>>>  The default action is to keep your current version.
>>> *** weewx.conf (Y/I/N/O/D/Z) [default=N] ?
>>> Installing new version of config file /etc/weewx/weewx.conf.dist ...
>>> Installing new version of config file
>>> /etc/weewx/logwatch/scripts/services/weewx ...
>>> Installing new version of config file /etc/weewx/skins/Rsync/skin.conf
>>> ...
>>> Installing new version of config file
>>> /etc/weewx/skins/Standard/index.html.tmpl ...
>>> Installing new version of config file
>>> /etc/weewx/skins/Standard/skin.conf ...
>>> Installing new version of config file /etc/weewx/skins/Ftp/skin.conf ...
>>> Installing new version of config file /etc/weewx/import/wu-example.conf
>>> ...
>>> Installing new version of config file
>>> /etc/weewx/import/cumulus-example.conf ...
>>> Installing new version of config file /etc/weewx/import/csv-example.conf
>>> ...
>>> saving previous config file as /etc/weewx/weewx.conf-3.8.2
>>> saving distribution config file as /etc/weewx/weewx.conf-3.9.0b1
>>> merging previous and distribution into /etc/weewx/weewx.conf
>>> Using configuration file /etc/weewx/weewx.conf-3.8.2
>>> Saved configuration to /etc/weewx/weewx.conf
>>> Processing triggers for systemd (232-25+deb9u8) ...
>>> root@raspberrypi:~/software/weewx# wee_database --rebuld-daily
>>> -su: /usr/bin/wee_database: Permission denied
>>> root@raspberrypi:~/software/weewx# wee_database --rebuld-daily
>>> -su: /usr/bin/wee_database: Permission denied
>>> root@raspberrypi:~/software/weewx# wee_database
>>> -su: /usr/bin/wee_database: Permission denied
>>> root@raspberrypi:~/software/weewx# systemctl status weewx
>>> ● weewx.service - LSB: weewx weather system
>>>Loaded: loaded (/etc/init.d/weewx; generated; vendor preset: enabled)
>>>Active: active (running) since Wed 2019-01-23 00:25:44 GMT; 43s ago
>>>  Docs: man:systemd-sysv-generator(8)
>

Re: [weewx-user] Re: Beta testers for v3.9.0 needed

[mercurystorm]

root@raspberrypi:/usr/share/weewx# ls -l `which wee_database`
total 172
-rw-r--r-- 1 root root  2891 Jan 22 17:47 daemon.py
-rw-r--r-- 1 root root  2715 Jan 23 00:32 daemon.pyc
drwxr-xr-x 2 root root  4096 Jan 23 00:32 schemas
drwxr-xr-x 3 root root  4096 Jan 23 00:36 user
drwxr-xr-x 2 root root  4096 Jan 23 00:32 weecfg
-rwxr-xr-x 1 root root  5414 Jan 22 17:47 wee_config
-rw-r--r-- 1 root root 36533 Jan 22 17:47 wee_database
drwxr-xr-x 2 root root  4096 Jan 23 00:32 weedb
-rwxr-xr-x 1 root root 16154 Jan 22 17:47 wee_debug
-rwxr-xr-x 1 root root  1924 Jan 22 17:47 wee_device
-rwxr-xr-x 1 root root  3016 Jan 22 17:47 wee_extension
drwxr-xr-x 2 root root  4096 Jan 23 00:32 weeimport
-rwxr-xr-x 1 root root 31175 Jan 22 17:47 wee_import
drwxr-xr-x 2 root root  4096 Jan 23 00:35 weeplot
-rwxr-xr-x 1 root root  2171 Jan 22 17:47 wee_reports
drwxr-xr-x 2 root root  4096 Jan 23 00:36 weeutil
drwxr-xr-x 3 root root  4096 Jan 23 00:35 weewx
-rwxr-xr-x 1 root root  2566 Jan 22 17:47 weewxd
-rwxr-xr-x 1 root root 21132 Jan 22 17:47 wunderfixer
root@raspberrypi:/usr/share/weewx#


On Wednesday, 23 January 2019 00:49:55 UTC, Thomas Keffer wrote:
>
> Francis, can you check the permissions on the executables.
>
> For example,
>
> *ls -l `which wee_database`*
>
> -tk
>
>
> On Tue, Jan 22, 2019 at 4:45 PM Francis Yates  > wrote:
>
>> root@raspberrypi:~/software/weewx# systemctl stop weewx
>> root@raspberrypi:~/software/weewx# wee_database --drop-daily
>> Using configuration file /etc/weewx/weewx.conf
>> Using database binding 'wx_binding', which is bound to database 
>> 'archive_mysql'
>> Proceeding will delete all your daily summaries from database 'weewx'
>> Are you sure you want to proceed (y/n)? y
>> Dropping daily summary tables from 'weewx' ...
>> Daily summary tables dropped from database 'weewx' in 2.84 seconds
>> root@raspberrypi:~/software/weewx# dpkg -i weewx
>> weewx_3.8.2-1_all.debweewx_3.9.0b1-1_all.deb  weewx-sdr-master/
>> root@raspberrypi:~/software/weewx# dpkg -i weewx_3.9.0b1-1_all.deb
>> (Reading database ... 45970 files and directories currently installed.)
>> Preparing to unpack weewx_3.9.0b1-1_all.deb ...
>> Unpacking weewx (3.9.0b1-1) over (3.8.2-1) ...
>> Setting up weewx (3.9.0b1-1) ...
>>
>> Configuration file '/etc/weewx/weewx.conf'
>>  ==> Modified (by you or by a script) since installation.
>>  ==> Package distributor has shipped an updated version.
>>What would you like to do about it ?  Your options are:
>> Y or I  : install the package maintainer's version
>> N or O  : keep your currently-installed version
>>   D : show the differences between the versions
>>   Z : start a shell to examine the situation
>>  The default action is to keep your current version.
>> *** weewx.conf (Y/I/N/O/D/Z) [default=N] ?
>> Installing new version of config file /etc/weewx/weewx.conf.dist ...
>> Installing new version of config file
>> /etc/weewx/logwatch/scripts/services/weewx ...
>> Installing new version of config file /etc/weewx/skins/Rsync/skin.conf ...
>> Installing new version of config file
>> /etc/weewx/skins/Standard/index.html.tmpl ...
>> Installing new version of config file /etc/weewx/skins/Standard/skin.conf 
>> ...
>> Installing new version of config file /etc/weewx/skins/Ftp/skin.conf ...
>> Installing new version of config file /etc/weewx/import/wu-example.conf 
>> ...
>> Installing new version of config file 
>> /etc/weewx/import/cumulus-example.conf ...
>> Installing new version of config file /etc/weewx/import/csv-example.conf 
>> ...
>> saving previous config file as /etc/weewx/weewx.conf-3.8.2
>> saving distribution config file as /etc/weewx/weewx.conf-3.9.0b1
>> merging previous and distribution into /etc/weewx/weewx.conf
>> Using configuration file /etc/weewx/weewx.conf-3.8.2
>> Saved configuration to /etc/weewx/weewx.conf
>> Processing triggers for systemd (232-25+deb9u8) ...
>> root@raspberrypi:~/software/weewx# wee_database --rebuld-daily
>> -su: /usr/bin/wee_database: Permission denied
>> root@raspberrypi:~/software/weewx# wee_database --rebuld-daily
>> -su: /usr/bin/wee_database: Permission denied
>> root@raspberrypi:~/software/weewx# wee_database
>> -su: /usr/bin/wee_database: Permission denied
>> root@raspberrypi:~/software/weewx# systemctl status weewx
>> ● weewx.service - LSB: weewx weather system
>>Loaded: loaded (/etc/init.d/weewx; generated; vendor preset: enabled)
>>Active: active (running) since Wed 2019-01-23 00:25:44 GMT; 43s ago
>>  Docs: man:systemd-sysv-generator(8)
>>CGroup: /system.slice/weewx.service
>>├─26285 python /usr/bin/weewxd --daemon
>> --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf
>>└─26286 /usr/local/bin/rtl_433 -f 868.3M -R 119 -F json
>>
>> Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Finished loading
>> service weewx.engine.StdQC
>> Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Loading service
>> weewx.wxservices.StdWXCalculate
>> Jan 23 00:25:45 raspberrypi weewx[2

Re: [weewx-user] Re: Beta testers for v3.9.0 needed

[Thomas Keffer]

Francis, can you check the permissions on the executables.

For example,

*ls -l `which wee_database`*

-tk


On Tue, Jan 22, 2019 at 4:45 PM Francis Yates 
wrote:

> root@raspberrypi:~/software/weewx# systemctl stop weewx
> root@raspberrypi:~/software/weewx# wee_database --drop-daily
> Using configuration file /etc/weewx/weewx.conf
> Using database binding 'wx_binding', which is bound to database
> 'archive_mysql'
> Proceeding will delete all your daily summaries from database 'weewx'
> Are you sure you want to proceed (y/n)? y
> Dropping daily summary tables from 'weewx' ...
> Daily summary tables dropped from database 'weewx' in 2.84 seconds
> root@raspberrypi:~/software/weewx# dpkg -i weewx
> weewx_3.8.2-1_all.debweewx_3.9.0b1-1_all.deb  weewx-sdr-master/
> root@raspberrypi:~/software/weewx# dpkg -i weewx_3.9.0b1-1_all.deb
> (Reading database ... 45970 files and directories currently installed.)
> Preparing to unpack weewx_3.9.0b1-1_all.deb ...
> Unpacking weewx (3.9.0b1-1) over (3.8.2-1) ...
> Setting up weewx (3.9.0b1-1) ...
>
> Configuration file '/etc/weewx/weewx.conf'
>  ==> Modified (by you or by a script) since installation.
>  ==> Package distributor has shipped an updated version.
>What would you like to do about it ?  Your options are:
> Y or I  : install the package maintainer's version
> N or O  : keep your currently-installed version
>   D : show the differences between the versions
>   Z : start a shell to examine the situation
>  The default action is to keep your current version.
> *** weewx.conf (Y/I/N/O/D/Z) [default=N] ?
> Installing new version of config file /etc/weewx/weewx.conf.dist ...
> Installing new version of config file
> /etc/weewx/logwatch/scripts/services/weewx ...
> Installing new version of config file /etc/weewx/skins/Rsync/skin.conf ...
> Installing new version of config file
> /etc/weewx/skins/Standard/index.html.tmpl ...
> Installing new version of config file /etc/weewx/skins/Standard/skin.conf
> ...
> Installing new version of config file /etc/weewx/skins/Ftp/skin.conf ...
> Installing new version of config file /etc/weewx/import/wu-example.conf ...
> Installing new version of config file
> /etc/weewx/import/cumulus-example.conf ...
> Installing new version of config file /etc/weewx/import/csv-example.conf
> ...
> saving previous config file as /etc/weewx/weewx.conf-3.8.2
> saving distribution config file as /etc/weewx/weewx.conf-3.9.0b1
> merging previous and distribution into /etc/weewx/weewx.conf
> Using configuration file /etc/weewx/weewx.conf-3.8.2
> Saved configuration to /etc/weewx/weewx.conf
> Processing triggers for systemd (232-25+deb9u8) ...
> root@raspberrypi:~/software/weewx# wee_database --rebuld-daily
> -su: /usr/bin/wee_database: Permission denied
> root@raspberrypi:~/software/weewx# wee_database --rebuld-daily
> -su: /usr/bin/wee_database: Permission denied
> root@raspberrypi:~/software/weewx# wee_database
> -su: /usr/bin/wee_database: Permission denied
> root@raspberrypi:~/software/weewx# systemctl status weewx
> ● weewx.service - LSB: weewx weather system
>Loaded: loaded (/etc/init.d/weewx; generated; vendor preset: enabled)
>Active: active (running) since Wed 2019-01-23 00:25:44 GMT; 43s ago
>  Docs: man:systemd-sysv-generator(8)
>CGroup: /system.slice/weewx.service
>├─26285 python /usr/bin/weewxd --daemon
> --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf
>└─26286 /usr/local/bin/rtl_433 -f 868.3M -R 119 -F json
>
> Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Finished loading
> service weewx.engine.StdQC
> Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Loading service
> weewx.wxservices.StdWXCalculate
> Jan 23 00:25:45 raspberrypi weewx[26285]: wxcalculate: The following
> values will be calculated: barometer=software, windchill=software,
> dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=software,
> windrun=prefer_h
> Jan 23 00:25:45 raspberrypi weewx[26285]: wxcalculate: The following
> algorithms will be used for calculations: altimeter=aaNOAA,
> maxSolarRad=RS
> Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Finished loading
> service weewx.wxservices.StdWXCalculate
> Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Loading service
> weewx.engine.StdArchive
> Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Archive will use
> data binding wx_binding
> Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Record generation
> will be attempted in 'software'
> Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Using archive
> interval of 300 seconds (software record generation)
> Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Use LOOP data in
> hi/low calculations: 1
>
> root@raspberrypi:~/software/weewx# systemctl stop weewx
> root@raspberrypi:~/software/weewx# wee
> wee_config wee_debug  wee_device wee_extension  wee_import
> wee_reportsweewxd
> root@raspberrypi:~/software/weewx# wee_de
> wee_debug   wee_device
> root@raspber

Re: [weewx-user] Re: Beta testers for v3.9.0 needed

[Francis Yates]

root@raspberrypi:~/software/weewx# systemctl stop weewx
root@raspberrypi:~/software/weewx# wee_database --drop-daily
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 'archive_mysql'
Proceeding will delete all your daily summaries from database 'weewx'
Are you sure you want to proceed (y/n)? y
Dropping daily summary tables from 'weewx' ...
Daily summary tables dropped from database 'weewx' in 2.84 seconds
root@raspberrypi:~/software/weewx# dpkg -i weewx
weewx_3.8.2-1_all.debweewx_3.9.0b1-1_all.deb  weewx-sdr-master/
root@raspberrypi:~/software/weewx# dpkg -i weewx_3.9.0b1-1_all.deb
(Reading database ... 45970 files and directories currently installed.)
Preparing to unpack weewx_3.9.0b1-1_all.deb ...
Unpacking weewx (3.9.0b1-1) over (3.8.2-1) ...
Setting up weewx (3.9.0b1-1) ...

Configuration file '/etc/weewx/weewx.conf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** weewx.conf (Y/I/N/O/D/Z) [default=N] ?
Installing new version of config file /etc/weewx/weewx.conf.dist ...
Installing new version of config file
/etc/weewx/logwatch/scripts/services/weewx ...
Installing new version of config file /etc/weewx/skins/Rsync/skin.conf ...
Installing new version of config file
/etc/weewx/skins/Standard/index.html.tmpl ...
Installing new version of config file /etc/weewx/skins/Standard/skin.conf ...
Installing new version of config file /etc/weewx/skins/Ftp/skin.conf ...
Installing new version of config file /etc/weewx/import/wu-example.conf ...
Installing new version of config file /etc/weewx/import/cumulus-example.conf ...
Installing new version of config file /etc/weewx/import/csv-example.conf ...
saving previous config file as /etc/weewx/weewx.conf-3.8.2
saving distribution config file as /etc/weewx/weewx.conf-3.9.0b1
merging previous and distribution into /etc/weewx/weewx.conf
Using configuration file /etc/weewx/weewx.conf-3.8.2
Saved configuration to /etc/weewx/weewx.conf
Processing triggers for systemd (232-25+deb9u8) ...
root@raspberrypi:~/software/weewx# wee_database --rebuld-daily
-su: /usr/bin/wee_database: Permission denied
root@raspberrypi:~/software/weewx# wee_database --rebuld-daily
-su: /usr/bin/wee_database: Permission denied
root@raspberrypi:~/software/weewx# wee_database
-su: /usr/bin/wee_database: Permission denied
root@raspberrypi:~/software/weewx# systemctl status weewx
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; generated; vendor preset: enabled)
   Active: active (running) since Wed 2019-01-23 00:25:44 GMT; 43s ago
 Docs: man:systemd-sysv-generator(8)
   CGroup: /system.slice/weewx.service
   ├─26285 python /usr/bin/weewxd --daemon
--pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf
   └─26286 /usr/local/bin/rtl_433 -f 868.3M -R 119 -F json

Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Finished loading
service weewx.engine.StdQC
Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Loading service
weewx.wxservices.StdWXCalculate
Jan 23 00:25:45 raspberrypi weewx[26285]: wxcalculate: The following
values will be calculated: barometer=software, windchill=software,
dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=software,
windrun=prefer_h
Jan 23 00:25:45 raspberrypi weewx[26285]: wxcalculate: The following
algorithms will be used for calculations: altimeter=aaNOAA,
maxSolarRad=RS
Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Finished loading
service weewx.wxservices.StdWXCalculate
Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Loading service
weewx.engine.StdArchive
Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Archive will use
data binding wx_binding
Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Record generation
will be attempted in 'software'
Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Using archive
interval of 300 seconds (software record generation)
Jan 23 00:25:45 raspberrypi weewx[26285]: engine: Use LOOP data in
hi/low calculations: 1

root@raspberrypi:~/software/weewx# systemctl stop weewx
root@raspberrypi:~/software/weewx# wee
wee_config wee_debug  wee_device wee_extension  wee_import
wee_reportsweewxd
root@raspberrypi:~/software/weewx# wee_de
wee_debug   wee_device
root@raspberrypi:~/software/weewx# wee_database
-su: /usr/bin/wee_database: Permission denied
root@raspberrypi:~/software/weewx# updatedb
root@raspberrypi:~/software/weewx# wee_database
-su: /usr/bin/wee_database: Permission denied

On Wed, Jan 23, 2019 at 12:37 AM gjr80  wrote:
>
> Should be there. What type of a WeeWX install do you have and where have you 

Re: [weewx-user] Re: Beta testers for v3.9.0 needed

[Thomas Keffer]

Scott, that is the upgrade guide for v3.8. The new V3.9 guide is included
in the distribution. Just browse to (for example)
/home/weewx/docs/upgrading.htm.

-tk

On Tue, Jan 22, 2019 at 1:39 PM Scott Grayban  wrote:

> The upgrade guide is still http://weewx.com/docs/upgrading.htm ?
>
> On Tuesday, January 22, 2019 at 12:16:25 PM UTC-8, Thomas Keffer wrote:
>>
>> A clarification on skins:
>>
>>- If you are installing fresh (not an upgrade), both *Seasons* and
>>*Standard* will be installed, but only *Seasons* will be activated.
>>- If you are upgrading, *Seasons* will be installed, but not
>>activated. Your existing *Standard* will be left untouched and
>>activated. For most people, your website will continue to look as 
>> expected.
>>The exception is if you manually changed values in skin.conf, your units
>>might come out wrong. There is a simple fix, explained in the *Upgrade
>>Guide*.
>>
>> -tk
>>
>>
>> On Tue, Jan 22, 2019 at 12:04 PM Thomas Keffer  wrote:
>>
>>> It's been well over a year since the last "dot" release, but the V3.9
>>> release is finally in sight!
>>>
>>> We have a beta version, and can use some help testing it out. The
>>> biggest new feature is the new skin, *Seasons*, to replace the
>>> venerable *Standard*, which has shipped since v1.0! Using the new skin
>>> is entirely optional.
>>>
>>> There have also been some changes in how report options are chosen, the
>>> net effect being that you will be able to specify a unit system to be
>>> applied to *all* reports, or just to individual reports.
>>>
>>> I've been running v3.9 for 6 months on my home machine, so it appears to
>>> be very stable. We can just use some help to see if there are any sharp
>>> edges left.
>>>
>>> You can find the release candidate, v3.9.0b1 is the usual place:
>>> http://weewx.com/downloads/development_versions/
>>>
>>> Thanks, all!
>>>
>>> -tk
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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: Beta testers for v3.9.0 needed

[gjr80]

Should be there. What type of a WeeWX install do you have and where have you 
looked?

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: Beta testers for v3.9.0 needed

[mercurystorm]

wee_database seems to be gone in 3.9?

On Tuesday, 22 January 2019 20:05:24 UTC, Thomas Keffer wrote:
>
> It's been well over a year since the last "dot" release, but the V3.9 
> release is finally in sight!
>
> We have a beta version, and can use some help testing it out. The biggest 
> new feature is the new skin, *Seasons*, to replace the venerable 
> *Standard*, which has shipped since v1.0! Using the new skin is entirely 
> optional.
>
> There have also been some changes in how report options are chosen, the 
> net effect being that you will be able to specify a unit system to be 
> applied to *all* reports, or just to individual reports.
>
> I've been running v3.9 for 6 months on my home machine, so it appears to 
> be very stable. We can just use some help to see if there are any sharp 
> edges left.
>
> You can find the release candidate, v3.9.0b1 is the usual place: 
> http://weewx.com/downloads/development_versions/
>
> Thanks, all!
>
> -tk
>

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

[weewx-user] Major update weather34 skin template for weeWX

[steepleian]

The weather34 skin template for weeWX has received a major update. It 
includes a new CSS and graphics and new features. It optionally allows full 
use of your own weeWX database to generate data charts.

See the demo here: - https://claydonsweather.org.uk/WX-HWS-demo

As it is a significant update and will require a clean install. If you are 
an existing user, do not attempt to copy your settings1.php file across as 
it will not be compatible with the new version.

Full setup instructions are included.

You can download from https://github.com/steepleian/WX-HWS (please note 
that this a new location from the previous one).

-- 
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: Beta testers for v3.9.0 needed

[Scott Grayban]

Seems to working like a champ. http://www.nettletondistrict.com/

On Tuesday, January 22, 2019 at 1:39:54 PM UTC-8, Scott Grayban wrote:
>
> The upgrade guide is still http://weewx.com/docs/upgrading.htm ?
>
> On Tuesday, January 22, 2019 at 12:16:25 PM UTC-8, Thomas Keffer wrote:
>>
>> A clarification on skins:
>>
>>- If you are installing fresh (not an upgrade), both *Seasons* and 
>>*Standard* will be installed, but only *Seasons* will be activated. 
>>- If you are upgrading, *Seasons* will be installed, but not 
>>activated. Your existing *Standard* will be left untouched and 
>>activated. For most people, your website will continue to look as 
>> expected. 
>>The exception is if you manually changed values in skin.conf, your units 
>>might come out wrong. There is a simple fix, explained in the *Upgrade 
>>Guide*.
>>
>> -tk
>>
>>
>> On Tue, Jan 22, 2019 at 12:04 PM Thomas Keffer  wrote:
>>
>>> It's been well over a year since the last "dot" release, but the V3.9 
>>> release is finally in sight!
>>>
>>> We have a beta version, and can use some help testing it out. The 
>>> biggest new feature is the new skin, *Seasons*, to replace the 
>>> venerable *Standard*, which has shipped since v1.0! Using the new skin 
>>> is entirely optional.
>>>
>>> There have also been some changes in how report options are chosen, the 
>>> net effect being that you will be able to specify a unit system to be 
>>> applied to *all* reports, or just to individual reports.
>>>
>>> I've been running v3.9 for 6 months on my home machine, so it appears to 
>>> be very stable. We can just use some help to see if there are any sharp 
>>> edges left.
>>>
>>> You can find the release candidate, v3.9.0b1 is the usual place: 
>>> http://weewx.com/downloads/development_versions/
>>>
>>> Thanks, all!
>>>
>>> -tk
>>>
>>

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

Re: [weewx-user] Re: Ambient Weather WS-2902A

[Scott Grayban]

Yes you can run multiple skins and choose the one you like.

URL will change depending on the skin you test... just look at the html 
folder for the names.

On Tuesday, January 22, 2019 at 1:39:59 PM UTC-8, Adnan Mumtaz wrote:
>
> Thanks Scott, you are so helpful. Ever tried Weather34 template using 
> weewx ? Is it possible to run 2 templates? 
>
> On Tue, Jan 22, 2019 at 10:50 PM Scott Grayban  > wrote:
>
>> There are a few ways to do this...
>>
>> https://www.raspberrypi.org/documentation/linux/filesystem/backup.md
>>
>> On Monday, January 21, 2019 at 8:24:40 PM UTC-8, Adnan Mumtaz wrote:
>>>
>>> Wonder how can I take a backup of all what I did.
>>>

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

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

Re: [weewx-user] Re: Ambient Weather WS-2902A

[Adnan Mumtaz]

Thanks Scott, you are so helpful. Ever tried Weather34 template using weewx
? Is it possible to run 2 templates?

On Tue, Jan 22, 2019 at 10:50 PM Scott Grayban  wrote:

> There are a few ways to do this...
>
> https://www.raspberrypi.org/documentation/linux/filesystem/backup.md
>
> On Monday, January 21, 2019 at 8:24:40 PM UTC-8, Adnan Mumtaz wrote:
>>
>> Wonder how can I take a backup of all what I did.
>>
>>>
>>> --
> 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: Beta testers for v3.9.0 needed

[Scott Grayban]

The upgrade guide is still http://weewx.com/docs/upgrading.htm ?

On Tuesday, January 22, 2019 at 12:16:25 PM UTC-8, Thomas Keffer wrote:
>
> A clarification on skins:
>
>- If you are installing fresh (not an upgrade), both *Seasons* and 
>*Standard* will be installed, but only *Seasons* will be activated. 
>- If you are upgrading, *Seasons* will be installed, but not 
>activated. Your existing *Standard* will be left untouched and 
>activated. For most people, your website will continue to look as 
> expected. 
>The exception is if you manually changed values in skin.conf, your units 
>might come out wrong. There is a simple fix, explained in the *Upgrade 
>Guide*.
>
> -tk
>
>
> On Tue, Jan 22, 2019 at 12:04 PM Thomas Keffer  > wrote:
>
>> It's been well over a year since the last "dot" release, but the V3.9 
>> release is finally in sight!
>>
>> We have a beta version, and can use some help testing it out. The biggest 
>> new feature is the new skin, *Seasons*, to replace the venerable 
>> *Standard*, which has shipped since v1.0! Using the new skin is entirely 
>> optional.
>>
>> There have also been some changes in how report options are chosen, the 
>> net effect being that you will be able to specify a unit system to be 
>> applied to *all* reports, or just to individual reports.
>>
>> I've been running v3.9 for 6 months on my home machine, so it appears to 
>> be very stable. We can just use some help to see if there are any sharp 
>> edges left.
>>
>> You can find the release candidate, v3.9.0b1 is the usual place: 
>> http://weewx.com/downloads/development_versions/
>>
>> Thanks, all!
>>
>> -tk
>>
>

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

Re: [weewx-user] Building a new environment for Weewx - migration plan

[vince]

On Tuesday, January 22, 2019 at 12:25:46 PM UTC-8, Jarmo Seppänen wrote:

> Waiting for the next 4-5 trouble free years running WeeWX on the new 
> raspi. ;)



And somewhere  a SD card thought "hm - time to go bad"  :-)

Pretty easy migration to new gear isn't it ?   Very cool.

-- 
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] Building a new environment for Weewx - migration plan

[Jarmo Seppänen]

Well, that was easy. All done and new system running.
Waiting for the next 4-5 trouble free years running WeeWX on the new raspi. ;)

-- 
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: Beta testers for v3.9.0 needed

[Thomas Keffer]

A clarification on skins:

   - If you are installing fresh (not an upgrade), both *Seasons* and
   *Standard* will be installed, but only *Seasons* will be activated.
   - If you are upgrading, *Seasons* will be installed, but not activated.
   Your existing *Standard* will be left untouched and activated. For most
   people, your website will continue to look as expected. The exception is if
   you manually changed values in skin.conf, your units might come out wrong.
   There is a simple fix, explained in the *Upgrade Guide*.

-tk


On Tue, Jan 22, 2019 at 12:04 PM Thomas Keffer  wrote:

> It's been well over a year since the last "dot" release, but the V3.9
> release is finally in sight!
>
> We have a beta version, and can use some help testing it out. The biggest
> new feature is the new skin, *Seasons*, to replace the venerable
> *Standard*, which has shipped since v1.0! Using the new skin is entirely
> optional.
>
> There have also been some changes in how report options are chosen, the
> net effect being that you will be able to specify a unit system to be
> applied to *all* reports, or just to individual reports.
>
> I've been running v3.9 for 6 months on my home machine, so it appears to
> be very stable. We can just use some help to see if there are any sharp
> edges left.
>
> You can find the release candidate, v3.9.0b1 is the usual place:
> http://weewx.com/downloads/development_versions/
>
> Thanks, all!
>
> -tk
>

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

[weewx-user] Beta testers for v3.9.0 needed

[Thomas Keffer]

It's been well over a year since the last "dot" release, but the V3.9
release is finally in sight!

We have a beta version, and can use some help testing it out. The biggest
new feature is the new skin, *Seasons*, to replace the venerable *Standard*,
which has shipped since v1.0! Using the new skin is entirely optional.

There have also been some changes in how report options are chosen, the net
effect being that you will be able to specify a unit system to be applied
to *all* reports, or just to individual reports.

I've been running v3.9 for 6 months on my home machine, so it appears to be
very stable. We can just use some help to see if there are any sharp edges
left.

You can find the release candidate, v3.9.0b1 is the usual place:
http://weewx.com/downloads/development_versions/

Thanks, all!

-tk

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

Re: [weewx-user] Re: Ambient Weather WS-2902A

[Scott Grayban]

There are a few ways to do this...

https://www.raspberrypi.org/documentation/linux/filesystem/backup.md

On Monday, January 21, 2019 at 8:24:40 PM UTC-8, Adnan Mumtaz wrote:
>
> Wonder how can I take a backup of all what I did.
>
>>
>>

-- 
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] Direct reading day rain from the console

[Thomas Keffer]

Only the $current tag uses the last record received from the console.
Everything else comes from the database.

-tk

On Tue, Jan 22, 2019 at 10:16 AM Antonis Katsonis <
nafpaktia.weat...@gmail.com> wrote:

> I will test it in the next rainfall by turning off my computer manually.
> After that I will update it with version 3.8.2.
>
> Does the same apply for the following?
>
> $current.rainRate
> $day.rainRate.max
>
> Which of the above is calculated by the weewx and which by the console?
>
> --
> 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: Getting the RPi 3 with Davis Vantage up and running

[dunbrokin]

Thank you for that!

On Wed, Jan 23, 2019 at 1:38 AM Andrew Milner 
wrote:

> there are 'official' readings at LOOP intervals as well as REC (archive)
> intervals.
>
> You have the option in weewx.conf [StdArchive] section of saying whether
> to use loop value for max reading or archive value.  If you specify loop
> then $day.windGust.maxtime should correspond to the LOOP time of the high
> gust of the day.
>
>
>
> On Tuesday, 22 January 2019 11:54:55 UTC+2, monmul wrote:
>>
>> It would appear (from comparing the data to the gust speed actually
>> occurring) that, despite the wind speed recorder operating on a real time
>> basis, the record of the gust speed is the speed when the set reading
>> interval occurs rather than the max speed during the time  between
>> "official" readings. Is this the case? Is there a way I can get the live
>> gust speed?
>>
>> On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:
>>>
>>> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis
>>> Vantage weather station. I have a serial Envoy data logger attaced to my
>>> Rpi with a serial/usb converter. In following the set up instructions, I
>>> get these errors!
>>>
>>> sudo weewxd weewx.conf
>>> Traceback (most recent call last):
>>>   File "/usr/bin/weewxd", line 64, in 
>>> weewx.engine.main(options, args)
>>>   File "/usr/share/weewx/weewx/engine.py", line 835, in main
>>> sane = os.stat(config_path).st_ctime
>>> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
>>> pi@Weatherpi:~ $ tail -f /var/log/syslog
>>> Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered:
>>> sender=:1.16 path=/MediaEndpoint/A2DPSink
>>> Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
>>> Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
>>> Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
>>> Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
>>> Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>>> next retry is Sun Jan  6 13:41:35 2019 [try
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx
>>> version 3.8.2
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9
>>> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform
>>> Linux-4.9.35-v7+-armv7l-with-debian-8.0
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
>>> Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary
>>> Directories...
>>> Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>>> next retry is Sun Jan  6 13:53:04 2019 [try
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary
>>> Directories.
>>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group
>>> rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>> Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>>> next retry is Sun Jan  6 13:55:58 2019 [try
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group
>>> rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>>
>>> Please where have I gone wrong?
>>>
>>>
>>> .
>>>
>>> Hi,
>>>
>>> It appears that you are in the /home/pi directory and hence weewxd is
>>> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie:
>>>
>>> $ sudo weewxd /etc/weewx/weewx.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.
>

-- 
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] Direct reading day rain from the console

[Antonis Katsonis]

I will test it in the next rainfall by turning off my computer manually.
After that I will update it with version 3.8.2.

Does the same apply for the following?

$current.rainRate
$day.rainRate.max

Which of the above is calculated by the weewx and which by the console?

-- 
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: IWDL - Vorhersage

[Kalli]

Ich weis habe das im Auge ..
dachte das hier Jemand vileicht ein lösung hat.

cu. Kalli

Am Sonntag, 20. Januar 2019 13:25:30 UTC+1 schrieb Kalli:
>
> Hallo
> seit einiger zeit geht die Wettervorhersage bei IWDL nicht mehr.
> hat sich was geändert.
>
> mfg. Kalli
>

-- 
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] Building a new environment for Weewx - migration plan

[Jarmo Seppänen]

Yes, on the same machine. 
I will need to transfer the other databases as well so it’ll be done at the 
same go. 
I kind of figured that it could be as simple as option one but was not quite 
sure if there are something raspi gen spesific. 
Thanks

 

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

Re: [weewx-user] Re: Reliable Switch to MySQL?

[Cameron D]

It won't take you long at all.  I have done more complex transfers from 
sqlite3 to mysql and I haven't been trained in any IT system - sorry, I was 
taught Fortran IV, but I don't think that counts.

Mysql has a far richer function and capability set so if you intend doing 
anything more than what weewx can do already then I would think you will be 
better off with mysql/Mariadb.

If the command line syntax is a bit obscure, the DB Browser for sqlite 
(http://sqlitebrowser.org/) is a fine multiplatform gui.

Export the table definitions to file, check over and import into mysql.
then export data, check over and then import.

For the other database I converted, I needed to edit around several 
incompatibilities between the sql syntax, but a few cycles of import, 
crash, edit fixed that.  The weewx db is so simple I don't expect there 
will be any compatibility problems.

Cameron.

On Tuesday, 22 January 2019 00:13:01 UTC+10, Cycle London wrote:
>
> Apologies - by 'the GUI' I mean the weewx web frontend.  
>
> I reckon it's about time I moved to  MySQL.  That involves raising a 
> change - which in my case, means asking my wife if she has anything planned 
> the weekend after next.  :-) 
>
>
>

-- 
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] Building a new environment for Weewx - migration plan

[Thomas Keffer]

Option #1 would work, except your are using MySQL. Was it running on the
RPi? If so, you'll have to dump it, then restore on the new machine.

OTOH, if it was running on some other machine on your network and it will
be untouched, then you shouldn't have a problem.

-tk

On Tue, Jan 22, 2019 at 1:53 AM Jarmo Seppänen 
wrote:

> What would be forum’s suggestion for the steps when migrating between
> different Raspi generations.
>
> Basic info of the current env.:
> raspi rpi-1 (512MB), setup.py install method, mysql db, vantage pro
> new env.:
> raspi 3b+
>
> choices:
> 1. restore database to new env and copy /home/weewx to new and basically
> just start it
> 2. restore db, install clean weewx to new env and copy conf files, skins
> etc from old to new and start it
> 3. some other method?
>
> br,
> jaMO
>
> PS. the current env. has been running with the same 16gb sd card (Sandisk
> Extreme) since 11.5.2014. Stubborn little device for a person with a
> mindset of ”if it works don’t fix it” ;)
>
>
> --
> 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] My current would not update

[Thomas Keffer]

1. To change the archive interval, run wee_device with the --set-interval
 command.

2. Run weewxd from the command line
, and see what is
printed out. Are all fields there?

3. Let's check the database.

*sqlite3 /var/lib/weewx/weewx.sdb*
sqlite> *select dateTime, datetime(dateTime,'unixepoch','localtime'),
inTemp, outTemp, windSpeed, windDir from archive order by dateTime desc
limit 15;*

-tk
On Tue, Jan 22, 2019 at 1:03 AM Ole Hansen  wrote:

> Now I did a:
>
> "
> sudo wee_database --rebuild-daily
>
> "
>
> Prompt:
> "
> Rebuilding daily summaries in database 'weewx.sdb' ...
> Daily summaries up to date in 'weewx.sdb'
> "
>
> No change though:
>
> - Weewx ran overnight and my WH1080-station.
> - Now in the browser - When I look on the "current page" I just see logs
> of the "wind vector" and the "inside temperature" - all other fields are
> empty (no logs / no data).
> - When I though switch to the week or month-page-view all sensor-data
> appears fine(!) e.g. outside temperature, outside humidity a.s.o. - so it
> logs obviously all data in the background, but does not process the
> current-page correctly.
>
> Regarding the hardware-interval. Before all this happened I had an
> interval of 300 seconds (5 mins) and that worked fine! Can I force weewx
> back to 300 seconds interval?
>

-- 
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: Getting the RPi 3 with Davis Vantage up and running

[Andrew Milner]

there are 'official' readings at LOOP intervals as well as REC (archive) 
intervals.

You have the option in weewx.conf [StdArchive] section of saying whether to 
use loop value for max reading or archive value.  If you specify loop then 
$day.windGust.maxtime should correspond to the LOOP time of the high gust 
of the day.



On Tuesday, 22 January 2019 11:54:55 UTC+2, monmul wrote:
>
> It would appear (from comparing the data to the gust speed actually 
> occurring) that, despite the wind speed recorder operating on a real time 
> basis, the record of the gust speed is the speed when the set reading 
> interval occurs rather than the max speed during the time  between 
> "official" readings. Is this the case? Is there a way I can get the live 
> gust speed?
>
> On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:
>>
>> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis 
>> Vantage weather station. I have a serial Envoy data logger attaced to my 
>> Rpi with a serial/usb converter. In following the set up instructions, I 
>> get these errors!
>>
>> sudo weewxd weewx.conf
>> Traceback (most recent call last):
>>   File "/usr/bin/weewxd", line 64, in 
>> weewx.engine.main(options, args)
>>   File "/usr/share/weewx/weewx/engine.py", line 835, in main
>> sane = os.stat(config_path).st_ctime
>> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
>> pi@Weatherpi:~ $ tail -f /var/log/syslog
>> Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: 
>> sender=:1.16 path=/MediaEndpoint/A2DPSink
>> Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
>> Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
>> Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
>> Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
>> Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
>> next retry is Sun Jan  6 13:41:35 2019 [try http://www.rsyslog.com/e/2007
>>  ]
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version 
>> 3.8.2
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 
>> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform 
>> Linux-4.9.35-v7+-armv7l-with-debian-8.0
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
>> Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary 
>> Directories...
>> Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
>> next retry is Sun Jan  6 13:53:04 2019 [try http://www.rsyslog.com/e/2007
>>  ]
>> Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary 
>> Directories.
>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
>> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>> Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
>> next retry is Sun Jan  6 13:55:58 2019 [try http://www.rsyslog.com/e/2007
>>  ]
>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
>> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>
>> Please where have I gone wrong?
>>
>>
>> .
>>
>> Hi,
>>
>> It appears that you are in the /home/pi directory and hence weewxd is 
>> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie:
>>
>> $ sudo weewxd /etc/weewx/weewx.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] Major update weather34 skin template for weeWX

[steepleian]

The weather34 skin template for weeWX has received a major update. It 
includes a new CSS and graphics and new features. It optionally allows full 
use of your own weeWX database to generate data charts.

See the demo here: - https://claydonsweather.org.uk/WX-HWS-master

As it is a significant update and will require a clean install. If you are 
an existing user, do not attempt to copy your settings1.php file across as 
it will not be compatible with the new version.

Full setup instructions are included.

You can download from https://github.com/steepleian/WX-HWS-master (please 
note that this a new location from the previous one).

-- 
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: Adding a new object in the ephem database

[Paul Bartholdi]

>
> Dear Thomas, 
>

Just a line to say that now everything is perfect (see 
http://shire-bdi.gotdns.com/weewx ). ! Thank for all your help.Paul

-- 
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: Real Time Gauges (RTGD) for Steel Series

[Tom Robertson]

Thanks Gary.  Great explanation and help as always.  I had sorta came to the 
conclusion that you explained.

I never really noticed having two copies until I was trying to get the gauges 
working with the Saratoga template.  I inadvertently had the path wrong 
(something I still have trouble with in Linux) and it was pointing to the weewx 
vs weewx/ss  directory.  The gauges were working because they found a 
gauge-data.txt file in the weewx directory but the gauges were not updating 
every loop.  I'm a little slow but I eventually discovered the second copy of 
gauge-data.txt.  As you know you usually get an error:not found from the gauges 
when the path is wrong.

I followed your advice and used the var/tmp path.

Now back to working on the Alternate Saratoga script trying to emulate your 
site. 😊

Tom


From: weewx-user@googlegroups.com  on behalf of 
gjr80 
Sent: Tuesday, January 22, 2019 2:27 AM
To: weewx-user
Subject: [weewx-user] Re: Real Time Gauges (RTGD) for Steel Series

Tom,

Let's walk through what each is doing.

On Tuesday, 22 January 2019 09:39:18 UTC+10, nine...@gmail.com wrote:
I'm a little confused which is nothing new.  I have RTGD configured as

[RealtimeGaugeData]
date_format = %Y.%m.%d %H:%M
rtgd_path = /home/weewx/public_html
scroller_source = WU
remote_server_url = 
http://www.XXX.com/weewx/ss/post_gauge-data.php
rtgd_file_name = gauge-data.txt

With these settings RTGD will be producing a loop based gauge-data.txt in 
/home/weewx/public_html on your weeWX machine. Assuming the http post is 
occurring error free, RTGD will also place a copy of this loop based 
gauge-data.txt on your web server. Where this copy of gauge-data.txt will be 
saved on your web server will depend on (1) the location of the 
post_gauge-data.php file on your web server and (2) the value assigned to 
$json_file in post_gauge-data.php. post_gauge-data.php is located in the 
weewx/ss directory relative to the root directory of you web server. If 
post_gauge-data.php is unmodified $json_file is set to './gauge-data.txt' so 
post_gauge-data.php will be placing a copy of the loop based gauge-data.txt in 
weewx/ss on your web server.

In my 
skin.com
 for ss is have

[CheetahGenerator]
   # search_list_extensions = user.forecast.ForecastVariables
encoding = html_entities
[[ToDate]]
[[[index]]]
template = index.html.tmpl
  #  [[[data]]]
   # template = gauge-data.txt.tmpl

With these settings the SteelSeries skin will produce ss/index.html but no 
gauge-data.txt

I am getting the gauge-data.txt file created in the weewx/ss folder on my web 
site every loop but I am also getting the gauge-data.txt file upload to my weex 
folder at each archive interval.

As explained above the weewx/ss copy is due to the http post via 
post_gauge-data.txt. The gauge-data.txt in the weewx directory on your web 
server is likely due to the FTP or Rsync that is used to upload  your site to 
your web server. Since RTGD is placing a copy of gauge-data.txt in the 
/home/weewx/public_html directory on your WeeWX machine gauge-data.txt just 
gets caught up with the rest of your sites files that are uploaded to your web 
server. Assuming you use the WeeWX FTP or Rsync report to upload your web sites 
files every archive period that would explain why this copy of gauge-data.txt 
is uploaded every 5 minutes and not every loop period.

  I thought by commenting out the two lines in the ss skin that would prevent 
one file from being created.

Correct and it has. The SteelsSeries skin is not producing gauge-data.txt.

I thought the loop file, created by RTGD, would go in the weex directory but it 
seems as though it is in my ss directory since the ss directory is being 
updated every loop.

When I look at my public_html folder on my Raspi I see the gauge-data.txt file 
in the root (weewx/public_html) but do not see the file in the 
weewx/public_html/ss folder.

RTGD is the only thing creating gauge-data.txt but two copies appear on your 
web server; one copy is due to the http post via post_gauge-data.php and the 
second copy is due to the FTP/Rsync upload of your site.

So why am I getting two files and why is the loop going into the ss folder?

I have probably covered that sufficiently above. I guess the other unasked 
question is how to eliminate the confusion and have only one copy of 
gauge-data.txt appear on yo

[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[monmul]

It would appear (from comparing the data to the gust speed actually 
occurring) that, despite the wind speed recorder operating on a real time 
basis, the record of the gust speed is the speed when the set reading 
interval occurs rather than the max speed during the time  between 
"official" readings. Is this the case? Is there a way I can get the live 
gust speed?

On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:
>
> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis 
> Vantage weather station. I have a serial Envoy data logger attaced to my 
> Rpi with a serial/usb converter. In following the set up instructions, I 
> get these errors!
>
> sudo weewxd weewx.conf
> Traceback (most recent call last):
>   File "/usr/bin/weewxd", line 64, in 
> weewx.engine.main(options, args)
>   File "/usr/share/weewx/weewx/engine.py", line 835, in main
> sane = os.stat(config_path).st_ctime
> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
> pi@Weatherpi:~ $ tail -f /var/log/syslog
> Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: 
> sender=:1.16 path=/MediaEndpoint/A2DPSink
> Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
> Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
> Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
> Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
> Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:41:35 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version 
> 3.8.2
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 
> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform 
> Linux-4.9.35-v7+-armv7l-with-debian-8.0
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
> Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary 
> Directories...
> Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:53:04 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary 
> Directories.
> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
> Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:55:58 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>
> Please where have I gone wrong?
>
>
> .
>
> Hi,
>
> It appears that you are in the /home/pi directory and hence weewxd is 
> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie:
>
> $ sudo weewxd /etc/weewx/weewx.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] Building a new environment for Weewx - migration plan

[Jarmo Seppänen]

What would be forum’s suggestion for the steps when migrating between different 
Raspi generations.

Basic info of the current env.:
raspi rpi-1 (512MB), setup.py install method, mysql db, vantage pro
new env.:
raspi 3b+

choices:
1. restore database to new env and copy /home/weewx to new and basically just 
start it
2. restore db, install clean weewx to new env and copy conf files, skins etc 
from old to new and start it
3. some other method?

br,
jaMO

PS. the current env. has been running with the same 16gb sd card (Sandisk 
Extreme) since 11.5.2014. Stubborn little device for a person with a mindset of 
”if it works don’t fix it” ;)


-- 
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: Real Time Gauges (RTGD) for Steel Series

[gjr80]

Tom,

What you are seeing is a combination of things. Firstly, RTGD is generating 
and saving gauge-data.txt on your WeeWX machine. The rtgd_path and 
rtgd_file_name settings determine the location and name of this file. In 
your case RTGD saves the file to /home/weewx/public_html/gauge-data.txt. 
This file is updated every loop period. Since you have remote_server_url 
set RTGD uses this setting to try to http post the gauge-data.txt contents 
to a remote machine, in your case your web server. The location of the file 
created on your web server is a combination of the location of 
post_gauge-data.php on your web server and the $json_file variable in 
post_gauge-data.php. In your case post_gauge-data.php is located in weewx/ss 
and unless you have changed it $json_file will be set to './gauge-data.txt'. 
So when you put all this together post_gauge-data.php saves the contents to 
weewx/ss/gauge-data.txt on your web server. This file will be updated every 
loop period.

The SteelSeries skin is not generating gauge-data.txt at all. The copy of 
gauge-data.txt that you see in the weewx directory on your web server is  
most likely the copy that is being saved to /home/weewx/public_html on your 
WeeWX server. What is happening is that the FTP/Rsync that you use to 
upload your website files to your web server is picking up this 
/home/wee/public_html/gauge-data.txt and transferring it to your web server 
via FTP/Rsync along with the rest of your web site files. Whilst this file 
is generated every loop period on your WeeWX machine, it is only uploaded 
to your web server on completion of every archive period and hence it only 
changes on your web server every 5 minutes.

So what you see is expected for your settings. I guess the unasked question 
is how to eliminate the confusion and have only one copy of gauge-data.txt 
appear on your web server. Well I could alter RTGD so that you can 
optionally turn off the local (to the WeeWX machine) saving of 
gauge-data.txt and that way there would be no file to upload via FTP/Rsync 
so that would get rid of the copy in the weewx directory of your web 
server. I will look at doing that. Alternatively you could alter your 
FTP/Rsync settings so that gauge-data.txt is not uploaded via FTP/Rsync. 
But that would require a bit of messing around with FTP/Rsync settings and 
possibly upset the upload of your other website files. Thirdly, and 
probably the easiest, is for you to change the rtgd_path setting to put 
gauge-data.txt in some directory that will not cause it to be uploaded to 
your web server. Something like this would do the trick:

[RealtimeGaugeData]
date_format = %Y.%m.%d %H:%M
rtgd_path = /var/tmp

This will put gauge-data.txt in /var/tmp on your WeeWX machine, well out of 
the way of any FTP/Rsync. You would need to do a config reload or restart 
WeeWX after this change.

Of course the 4th option is to leave it as it is, it is not causing any ill 
effect other than confusion.

Gary

On Tuesday, 22 January 2019 09:39:18 UTC+10, nine...@gmail.com wrote:
>
> I'm a little confused which is nothing new.  I have RTGD configured as
>
> [RealtimeGaugeData]
> date_format = %Y.%m.%d %H:%M
> rtgd_path = /home/weewx/public_html
> scroller_source = WU
> remote_server_url = http://www.XXX.com/weewx/ss/post_gauge-data.php
> rtgd_file_name = gauge-data.txt
>
> In my skin.com for ss is have
>
> [CheetahGenerator]
># search_list_extensions = user.forecast.ForecastVariables
> encoding = html_entities
> [[ToDate]]
> [[[index]]]
> template = index.html.tmpl
>   #  [[[data]]]
># template = gauge-data.txt.tmpl
>
> I am getting the gauge-data.txt file created in the weewx/ss folder on my 
> web site every loop but I am also getting the gauge-data.txt file upload to 
> my weex folder at each archive interval.  I thought by commenting out the 
> two lines in the ss skin that would prevent one file from being created.  I 
> thought the loop file, created by RTGD, would go in the weex directory but 
> it seems as though it is in my ss directory since the ss directory is being 
> updated every loop.
>
> When I look at my public_html folder on my Raspi I see the gauge-data.txt 
> file in the root (weewx/public_html) but do not see the file in the 
> weewx/public_html/ss folder.
>
> So why am I getting two files and why is the loop going into the ss folder?
>
> Tom
>
>
>
>
>

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

[weewx-user] Re: Real Time Gauges (RTGD) for Steel Series

[gjr80]

Tom,

Let's walk through what each is doing.

On Tuesday, 22 January 2019 09:39:18 UTC+10, nine...@gmail.com wrote:
>
> I'm a little confused which is nothing new.  I have RTGD configured as
>
> [RealtimeGaugeData]
> date_format = %Y.%m.%d %H:%M
> rtgd_path = /home/weewx/public_html
> scroller_source = WU
> remote_server_url = http://www.XXX.com/weewx/ss/post_gauge-data.php
> rtgd_file_name = gauge-data.txt
>

With these settings RTGD will be producing a loop based gauge-data.txt in 
/home/weewx/public_html on your weeWX machine. Assuming the http post is 
occurring error free, RTGD will also place a copy of this loop based 
gauge-data.txt on your web server. Where this copy of gauge-data.txt will 
be saved on your web server will depend on (1) the location of the 
post_gauge-data.php file on your web server and (2) the value assigned to 
$json_file in post_gauge-data.php. post_gauge-data.php is located in the 
weewx/ss directory relative to the root directory of you web server. If 
post_gauge-data.php is unmodified $json_file is set to './gauge-data.txt' 
so post_gauge-data.php will be placing a copy of the loop based 
gauge-data.txt in weewx/ss on your web server.

In my skin.com for ss is have
>
> [CheetahGenerator]
># search_list_extensions = user.forecast.ForecastVariables
> encoding = html_entities
> [[ToDate]]
> [[[index]]]
> template = index.html.tmpl
>   #  [[[data]]]
># template = gauge-data.txt.tmpl
>

With these settings the SteelSeries skin will produce ss/index.html but no 
gauge-data.txt 

I am getting the gauge-data.txt file created in the weewx/ss folder on my 
> web site every loop but I am also getting the gauge-data.txt file upload to 
> my weex folder at each archive interval.
>

As explained above the weewx/ss copy is due to the http post via 
post_gauge-data.txt. The gauge-data.txt in the weewx directory on your web 
server is likely due to the FTP or Rsync that is used to upload  your site 
to your web server. Since RTGD is placing a copy of gauge-data.txt in the 
/home/weewx/public_html directory on your WeeWX machine gauge-data.txt just 
gets caught up with the rest of your sites files that are uploaded to your 
web server. Assuming you use the WeeWX FTP or Rsync report to upload your 
web sites files every archive period that would explain why this copy of 
gauge-data.txt is uploaded every 5 minutes and not every loop period.

  I thought by commenting out the two lines in the ss skin that would 
> prevent one file from being created.  
>

Correct and it has. The SteelsSeries skin is not producing gauge-data.txt.

I thought the loop file, created by RTGD, would go in the weex directory 
> but it seems as though it is in my ss directory since the ss directory is 
> being updated every loop.
>

> When I look at my public_html folder on my Raspi I see the gauge-data.txt 
> file in the root (weewx/public_html) but do not see the file in the 
> weewx/public_html/ss folder.
>

RTGD is the only thing creating gauge-data.txt but two copies appear on 
your web server; one copy is due to the http post via post_gauge-data.php 
and the second copy is due to the FTP/Rsync upload of your site.
 

> So why am I getting two files and why is the loop going into the ss folder?
>

I have probably covered that sufficiently above. I guess the other unasked 
question is how to eliminate the confusion and have only one copy of 
gauge-data.txt appear on your web server. Well I could alter RTGD so that 
you can optionally turn off the local (to the WeeWX machine) saving of 
gauge-data.txt and that way there would be no file to upload via FTP/Rsync 
so that would get rid of the copy in the weewx directory of your web 
server. I will look at doing that. Alternatively you could alter your 
FTP/Rsync settings so that gauge-data.txt is not uploaded via FTP/Rsync. 
But that would require a bit of messing around with FTP/Rsync settings and 
possibly upset the upload of your other website files. Thirdly, and 
probably the easiest, is for you to change the rtgd_path setting to put 
gauge-data.txt in some directory that will not cause it to be uploaded to 
your web server. Something like this would do the trick:

[RealtimeGaugeData]
date_format = %Y.%m.%d %H:%M
rtgd_path = /var/tmp

This will put gauge-data.txt in /var/tmp on your WeeWX machine, well out of 
the way of any FTP/Rsync. You would need to do a config reload or restart 
WeeWX after this change.

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.