[weewx-user] Re: use Weewx on raspberry
I am not sure if this is the right place to post this help request...please direct me elsewhere if not. 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? -- 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: use Weewx on raspberry
Thank you so much will start a new one and include this post and answer on it! On Sunday, 6 January 2019 14:26:43 UTC+13, gjr80 wrote: > > 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 > > PS. Would be appreciated if you started a new thread for new issues, > having multiple issues throughout one thread is confusing for everybody. > > On Sunday, 6 January 2019 11:06:32 UTC+10, monmul wrote: >> >> I am not sure if this is the right place to post this help >> request...please direct me elsewhere if not. 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? >> > -- 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] Getting the RPi 3 with Davis Vantage up and running
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] Re: Getting the RPi 3 with Davis Vantage up and running
OK, with the correct path!still no joy! pi@Weatherpi:/ $ sudo weewxd /etc/weewx/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 871, in main engine = engine_class(config_dict) File "/usr/share/weewx/weewx/engine.py", line 75, in __init__ self.preLoadServices(config_dict) File "/usr/share/weewx/weewx/engine.py", line 116, in preLoadServices self.stn_info = weewx.station.StationInfo(self.console, **config_dict['Station']) File "/usr/share/weewx/weewx/station.py", line 49, in __init__ self.latitude_f = float(stn_dict['latitude']) ValueError: invalid literal for float(): -45.060031 168.566948 pi@Weatherpi:/ $ 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] Re: Getting the RPi 3 with Davis Vantage up and running
Sorry my errorthe latitude and longitude were formatted incorrectly in the config file.works now! On Sunday, 6 January 2019 16:25:56 UTC+13, monmul wrote: > > OK, with the correct path!still no joy! > > > pi@Weatherpi:/ $ sudo weewxd /etc/weewx/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 871, in main > engine = engine_class(config_dict) > File "/usr/share/weewx/weewx/engine.py", line 75, in __init__ > self.preLoadServices(config_dict) > File "/usr/share/weewx/weewx/engine.py", line 116, in preLoadServices > self.stn_info = weewx.station.StationInfo(self.console, > **config_dict['Station']) > File "/usr/share/weewx/weewx/station.py", line 49, in __init__ > self.latitude_f = float(stn_dict['latitude']) > ValueError: invalid literal for float(): -45.060031 168.566948 > pi@Weatherpi:/ $ > > > 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] Re: Getting the RPi 3 with Davis Vantage up and running
Yes thank you all for your help I caught that error.but now I have a new set as I try and set up nginx! . . pi@Weatherpi:~ $ sudo mkdir -p /var/weewx/reports pi@Weatherpi:~ $ sudo mount -a mount: /etc/fstab: parse error: ignore entry at line 6. pi@Weatherpi:~ $ sudo sed -i -e ‘s%HTML_ROOT =.*%HTML_ROOT = /var/weewx/reports%’ /etc/weewx/weewx.conf sed: -e expression #1, char 1: unknown command: `�' pi@Weatherpi:~ $ sudo service weewx restart pi@Weatherpi:~ $ sudo ln -s /var/weewx/reports /var/www/html/weewx pi@Weatherpi:~ $ . . . On Sunday, 6 January 2019 16:46:33 UTC+13, Andrew Milner wrote: > > what have you set latitude and longitude to in weewx.conf?? The error > implies latitude is wrongly set > > > > On Sunday, 6 January 2019 05:25:56 UTC+2, monmul wrote: >> >> OK, with the correct path!still no joy! >> >> >> pi@Weatherpi:/ $ sudo weewxd /etc/weewx/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 871, in main >> engine = engine_class(config_dict) >> File "/usr/share/weewx/weewx/engine.py", line 75, in __init__ >> self.preLoadServices(config_dict) >> File "/usr/share/weewx/weewx/engine.py", line 116, in preLoadServices >> self.stn_info = weewx.station.StationInfo(self.console, >> **config_dict['Station']) >> File "/usr/share/weewx/weewx/station.py", line 49, in __init__ >> self.latitude_f = float(stn_dict['latitude']) >> ValueError: invalid literal for float(): -45.060031 168.566948 >> pi@Weatherpi:/ $ >> >> >> 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] Re: Getting the RPi 3 with Davis Vantage up and running
Great! I have managed to get my information through to Weather Underground! 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] Re: Getting the RPi 3 with Davis Vantage up and running
Is this normal?i.e. waking up a sleeping consolesee below! . . 241, dayET: 0.0, dayRain: 1.1496062995, dewpoint: 58.5620048927, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, forecastIcon: 3, forecastRule: 192, heatindex: 60.0, humidex: 66.8739411693, inDewpoint: 55.0283705113, inHumidity: 53.0, insideAlarm: 0, inTemp: 73.2, leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: 1.22047244125, outHumidity: 95.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 60.0, rain: 0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 1.1496062995, stormStart: 1544094000, sunrise: 1546702920, sunset: 1546758180, trendIcon: -20, txBatteryStatus: 0, usUnits: 1, windchill: 60.0, windDir: None, windGust: 0.0, windGustDir: None, windSpeed: 0.0, windSpeed10: 0.0, yearET: 0.0, yearRain: 34.85 Unable to wake up console... sleeping Unable to wake up console... retrying LOOP: 2019-01-06 17:00:46 NZDT (1546747246) appTemp: 62.7512992774, barometer: 29.609, cloudbase: 1376.81706984, consBatteryVoltage: 3.03, dateTime: 1546747246, dayET: 0.0, dayRain: 1.1496062995, dewpoint: 58.5620048927, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, forecastIcon: 3, forecastRule: 192, heatindex: 60.0, humidex: 66.8739411693, inDewpoint: 55.0283705113, inHumidity: 53.0, insideAlarm: 0, inTemp: 73.2, leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: 1.22047244125, outHumidity: 95.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 60.0, rain: 0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 1.1496062995, stormStart: 1544094000, sunrise: 1546702920, sunset: 1546758180, trendIcon: -20, txBatteryStatus: 0, usUnits: 1, windchill: 60.0, windDir: None, windGust: 0.0, windGustDir: None, windSpeed: 0.0, windSpeed10: 0.0, yearET: 0.0, yearRain: 34.85 Unable to wake up console... sleeping Unable to wake up console... retrying LOOP: 2019-01-06 17:00:51 NZDT (1546747251) appTemp: 62.7512992774, barometer: 29.609, cloudbase: 1376.81706984, consBatteryVoltage: 3.03, dateTime: 1546747251, dayET: 0.0, dayRain: 1.1496062995, dewpoint: 58.5620048927, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, forecastIcon: 3, forecastRule: 192, heatindex: 60.0, humidex: 66.8739411693, inDewpoint: 55.0283705113, inHumidity: 53.0, insideAlarm: 0, inTemp: 73.2, leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: 1.22047244125, outHumidity: 95.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 60.0, rain: 0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 1.1496062995, stormStart: 1544094000, sunrise: 154670292 On Sunday, 6 January 2019 16:56:39 UTC+13, monmul wrote: > > Great! I have managed to get my information through to Weather Underground! > > 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 i
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Hmmm! I would have to pass on that oneI am not sure I even know what it means.is it something I set up when following the instructions about installing nginx? One other thingI have not done anything about setting up the NTP Daemon thingdo I need to do that also? On Sunday, 6 January 2019 17:08:51 UTC+13, gjr80 wrote: > > Depends, are loop and archive records being properly (and regularly) > received/created ? If so it is fine, if not then we look deepre. > > Gary > > On Sunday, 6 January 2019 14:04:26 UTC+10, monmul wrote: >> >> Is this normal?i.e. waking up a sleeping consolesee below! >> . >> . >> 241, dayET: 0.0, dayRain: 1.1496062995, dewpoint: 58.5620048927, >> extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, >> extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, >> forecastIcon: 3, forecastRule: 192, heatindex: 60.0, humidex: >> 66.8739411693, inDewpoint: 55.0283705113, inHumidity: 53.0, insideAlarm: 0, >> inTemp: 73.2, leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: >> 1.22047244125, outHumidity: 95.0, outsideAlarm1: 0, outsideAlarm2: 0, >> outTemp: 60.0, rain: 0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, >> soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: >> 1.1496062995, stormStart: 1544094000, sunrise: 1546702920, sunset: >> 1546758180, trendIcon: -20, txBatteryStatus: 0, usUnits: 1, windchill: >> 60.0, windDir: None, windGust: 0.0, windGustDir: None, windSpeed: 0.0, >> windSpeed10: 0.0, yearET: 0.0, yearRain: 34.85 >> Unable to wake up console... sleeping >> Unable to wake up console... retrying >> LOOP: 2019-01-06 17:00:46 NZDT (1546747246) appTemp: 62.7512992774, >> barometer: 29.609, cloudbase: 1376.81706984, consBatteryVoltage: 3.03, >> dateTime: 1546747246, dayET: 0.0, dayRain: 1.1496062995, dewpoint: >> 58.5620048927, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: >> 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, >> forecastIcon: 3, forecastRule: 192, heatindex: 60.0, humidex: >> 66.8739411693, inDewpoint: 55.0283705113, inHumidity: 53.0, insideAlarm: 0, >> inTemp: 73.2, leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: >> 1.22047244125, outHumidity: 95.0, outsideAlarm1: 0, outsideAlarm2: 0, >> outTemp: 60.0, rain: 0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, >> soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: >> 1.1496062995, stormStart: 1544094000, sunrise: 1546702920, sunset: >> 1546758180, trendIcon: -20, txBatteryStatus: 0, usUnits: 1, windchill: >> 60.0, windDir: None, windGust: 0.0, windGustDir: None, windSpeed: 0.0, >> windSpeed10: 0.0, yearET: 0.0, yearRain: 34.85 >> Unable to wake up console... sleeping >> Unable to wake up console... retrying >> LOOP: 2019-01-06 17:00:51 NZDT (1546747251) appTemp: 62.7512992774, >> barometer: 29.609, cloudbase: 1376.81706984, consBatteryVoltage: 3.03, >> dateTime: 1546747251, dayET: 0.0, dayRain: 1.1496062995, dewpoint: >> 58.5620048927, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: >> 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, >> forecastIcon: 3, forecastRule: 192, heatindex: 60.0, humidex: >> 66.8739411693, inDewpoint: 55.0283705113, inHumidity: 53.0, insideAlarm: 0, >> inTemp: 73.2, leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: >> 1.22047244125, outHumidity: 95.0, outsideAlarm1: 0, outsideAlarm2: 0, >> outTemp: 60.0, rain: 0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, >> soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: >> 1.1496062995, stormStart: 1544094000, sunrise: 154670292 >> >> On Sunday, 6 January 2019 16:56:39 UTC+13, monmul wrote: >>> >>> Great! I have managed to get my information through to Weather >>> Underground! >>> >>> 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
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
This is all I could find on the syslogno errors given so I will ignore the LOOP etc Jan 6 18:25:20 Weatherpi weewx[831]: engine: Loading station type Vantage (weewx.drivers.vantage) Jan 6 18:25:20 Weatherpi weewx[831]: import of driver failed: [Errno 11] Resource temporarily unavailable () Jan 6 18:25:20 Weatherpi weewx[688]: vantage: No received from console Jan 6 18:25:20 Weatherpi weewx[831]: engine: Unable to load driver: [Errno 11] Resource temporarily unavailable Jan 6 18:25:20 Weatherpi weewx[831]: Exiting... Jan 6 18:25:20 Weatherpi ntpd_intres[684]: host name not found: 0.debian.pool.ntp.org Jan 6 18:25:20 Weatherpi ntpd_intres[684]: host name not found: 1.debian.pool.ntp.org Jan 6 18:25:20 Weatherpi ntpd_intres[684]: host name not found: 2.debian.pool.ntp.org Jan 6 18:25:20 Weatherpi ntpd_intres[684]: host name not found: 3.debian.pool.ntp.org Jan 6 18:25:20 Weatherpi weewx[688]: vantage: No received from console Jan 6 18:25:20 Weatherpi weewx[688]: vantage: No received from console Jan 6 18:25:20 Weatherpi avahi-daemon[468]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::1cc0:5dfe:d383:8c98. Jan 6 18:25:20 Weatherpi avahi-daemon[468]: New relevant interface eth0.IPv6 for mDNS. On Sunday, 6 January 2019 17:52:24 UTC+13, gjr80 wrote: > > On Sunday, 6 January 2019 14:20:09 UTC+10, monmul wrote: >> >> Hmmm! I would have to pass on that oneI am not sure I even know what >> it means.is it something I set up when following the instructions about >> installing nginx? >> >> Ok, you posted a screen capture with a couple of loop packets (the lines > starting with LOOP: ). This was part of the output you would have seen when > you ran weewx directly using sudo weewxd /etc/weewx/weewx.conf. Since you > only showed us a couple of loop packets things could be running fine, its > hard to say with such a small snapshot. The loop packets were 5 seconds > apart, if you station emits loop packets every 5 seconds then this is fine, > if it emits loop packets every 2 seconds then maybe there is an issue. > Having a look at a good couple of archive periods of output would give a > better feel for things rather than just a couple of loop packets. We would > also see some archive records (they occur once per archive period) and > start with REC: on screen. Would also be handy to know the station > type/model. > > You might want to have a read through Loop packets vs. archive records > <http://weewx.com/docs/customizing.htm#_LOOP_packets_vs._archive_records___> > > in the Customization Guide <http://weewx.com/docs/customizing.htm> - it > will give you a bit of background. Also, have a look at your log (likely > /var/log/syslog) from when you start weeWX, you will see a whole pile of > info there as to how your station and weeWX are configured. teh log is good > for seeing startup config and events as they happen (including errors). > Screen output from running weeWX directly is handy for seeing the actual > data weeWX gets off the station. > > nginx will have nothing to do it, nginx is purely serving web pages/data > to your browser, the sleeping/retrying etc is weeWX interacting with your > weather station. > > >> One other thingI have not done anything about setting up the NTP >> Daemon thingdo I need to do that also? >> > > Horses for courses. If it were me I would get NTP setup and working > properly. Correct time is critical for weeWX to operate trouble free, some > really bad and unusual things happen if weeWX and your station have > significantly different times. That being said, once you have the correct > time set all will likely be well until you have to reboot or turn your RPi > off or there is a power interruption. RPis (as distinct from a desktop type > PC or laptop) are a common source of concern as they have no battery backed > clock for when the power is off, they have a fake hardware clock that can > come up in the past. Various improvements have been applied to weeWX over > the years to make it better handle temporal displacements and it is > probably the best it has been but as a minimum I would get NTP up and > running and I would also consider an add-on battery backed RTC module, they > are just a couple of dollars on ebay or the like. > > 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: Getting the RPi 3 with Davis Vantage up and running
Is there a ¨How To¨ for setting up the NTP on the RPi? On Sunday, 6 January 2019 18:39:44 UTC+13, monmul wrote: > > This is all I could find on the syslogno errors given so I will ignore > the LOOP etc > > Jan 6 18:25:20 Weatherpi weewx[831]: engine: Loading station type Vantage > (weewx.drivers.vantage) > Jan 6 18:25:20 Weatherpi weewx[831]: import of driver failed: [Errno 11] > Resource temporarily unavailable () > Jan 6 18:25:20 Weatherpi weewx[688]: vantage: No received from > console > Jan 6 18:25:20 Weatherpi weewx[831]: engine: Unable to load driver: > [Errno 11] Resource temporarily unavailable > Jan 6 18:25:20 Weatherpi weewx[831]: Exiting... > Jan 6 18:25:20 Weatherpi ntpd_intres[684]: host name not found: > 0.debian.pool.ntp.org > Jan 6 18:25:20 Weatherpi ntpd_intres[684]: host name not found: > 1.debian.pool.ntp.org > Jan 6 18:25:20 Weatherpi ntpd_intres[684]: host name not found: > 2.debian.pool.ntp.org > Jan 6 18:25:20 Weatherpi ntpd_intres[684]: host name not found: > 3.debian.pool.ntp.org > Jan 6 18:25:20 Weatherpi weewx[688]: vantage: No received from > console > Jan 6 18:25:20 Weatherpi weewx[688]: vantage: No received from > console > Jan 6 18:25:20 Weatherpi avahi-daemon[468]: Joining mDNS multicast group > on interface eth0.IPv6 with address fe80::1cc0:5dfe:d383:8c98. > Jan 6 18:25:20 Weatherpi avahi-daemon[468]: New relevant interface > eth0.IPv6 for mDNS. > > > On Sunday, 6 January 2019 17:52:24 UTC+13, gjr80 wrote: >> >> On Sunday, 6 January 2019 14:20:09 UTC+10, monmul wrote: >>> >>> Hmmm! I would have to pass on that oneI am not sure I even know what >>> it means.is it something I set up when following the instructions about >>> installing nginx? >>> >>> Ok, you posted a screen capture with a couple of loop packets (the lines >> starting with LOOP: ). This was part of the output you would have seen when >> you ran weewx directly using sudo weewxd /etc/weewx/weewx.conf. Since >> you only showed us a couple of loop packets things could be running fine, >> its hard to say with such a small snapshot. The loop packets were 5 seconds >> apart, if you station emits loop packets every 5 seconds then this is fine, >> if it emits loop packets every 2 seconds then maybe there is an issue. >> Having a look at a good couple of archive periods of output would give a >> better feel for things rather than just a couple of loop packets. We would >> also see some archive records (they occur once per archive period) and >> start with REC: on screen. Would also be handy to know the station >> type/model. >> >> You might want to have a read through Loop packets vs. archive records >> <http://weewx.com/docs/customizing.htm#_LOOP_packets_vs._archive_records___> >> >> in the Customization Guide <http://weewx.com/docs/customizing.htm> - it >> will give you a bit of background. Also, have a look at your log (likely >> /var/log/syslog) from when you start weeWX, you will see a whole pile of >> info there as to how your station and weeWX are configured. teh log is good >> for seeing startup config and events as they happen (including errors). >> Screen output from running weeWX directly is handy for seeing the actual >> data weeWX gets off the station. >> >> nginx will have nothing to do it, nginx is purely serving web pages/data >> to your browser, the sleeping/retrying etc is weeWX interacting with your >> weather station. >> >> >>> One other thingI have not done anything about setting up the NTP >>> Daemon thingdo I need to do that also? >>> >> >> Horses for courses. If it were me I would get NTP setup and working >> properly. Correct time is critical for weeWX to operate trouble free, some >> really bad and unusual things happen if weeWX and your station have >> significantly different times. That being said, once you have the correct >> time set all will likely be well until you have to reboot or turn your RPi >> off or there is a power interruption. RPis (as distinct from a desktop type >> PC or laptop) are a common source of concern as they have no battery backed >> clock for when the power is off, they have a fake hardware clock that can >> come up in the past. Various improvements have been applied to weeWX over >> the years to make it better handle temporal displacements and it is >> probably the best it has been but as a minimum I would get NTP up and >> running and I would also consider an add-on battery backed RTC module, they >> are just a couple of dollars on ebay or the like. >> >> 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
# Configuration for resolvconf(8) # See resolvconf.conf(5) for details resolv_conf=/etc/resolv.conf # If you run a local name server, you should uncomment the below line and # configure your subscribers configuration files below. #name_servers=127.0.0.1 # Mirror the Debian package defaults for the below resolvers # so that resolvconf integrates seemlessly. dnsmasq_resolv=/var/run/dnsmasq/resolv.conf pdnsd_conf=/etc/pdnsd.conf unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf On Sunday, 6 January 2019 19:56:45 UTC+13, Scott Grayban wrote: > > Paste the contents of that file here > > On Saturday, January 5, 2019 at 10:43:45 PM UTC-8, monmul wrote: >> >> Yes it does! >> > -- 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
Duh! thanks Gary! 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] Re: Getting the RPi 3 with Davis Vantage up and running
herpi kernel: [ 4432.550855] hub 1-1:1.0: hub_ext_port_status failed (err = -71) Jan 7 15:04:24 Weatherpi kernel: [ 4432.550891] usb 1-1: USB disconnect, device number 58 Jan 7 15:04:24 Weatherpi kernel: [ 4432.750745] Indeed it is in host mode hprt0 = 00021501 Jan 7 15:04:24 Weatherpi kernel: [ 4432.950736] usb 1-1: new high-speed USB device number 59 using dwc_otg 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] Re: Getting the RPi 3 with Davis Vantage up and running
Ah! there seems to be a power problem with my WiFi dongle! I will try it headless and on the LAN. 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] Re: Getting the RPi 3 with Davis Vantage up and running
Ah! there seems to be a power problem with my WiF 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] Re: Getting the RPi 3 with Davis Vantage up and running
This is what I get headless and with the LAN as opposed to the wifi dongle! pi@Weatherpi:~ $ sudo systemctl status weewx ● weewx.service - LSB: weewx weather system Loaded: loaded (/etc/init.d/weewx) Active: active (running) since Mon 2019-01-07 18:50:45 NZDT; 50s ago Process: 510 ExecStart=/etc/init.d/weewx start (code=exited, status=0/SUCCESS) CGroup: /system.slice/weewx.service └─786 python /usr/bin/weewxd --daemon --pidfile=/var/run/weewx.pid... Jan 07 18:50:49 Weatherpi weewx[786]: restx: AWEKAS: Posting not enabled. Jan 07 18:50:49 Weatherpi weewx[786]: engine: Starting up weewx version 3.8.2 Jan 07 18:50:49 Weatherpi weewx[786]: engine: Clock error is -8.73 seconds ...t) Jan 07 18:50:49 Weatherpi weewx[786]: vantage: Clock set to 2019-01-07 18:5...0) Jan 07 18:50:51 Weatherpi weewx[786]: manager: Added record 2019-01-07 18:5...b' Jan 07 18:50:51 Weatherpi weewx[786]: manager: Added record 2019-01-07 18:5...b' Jan 07 18:50:51 Weatherpi weewx[786]: engine: Starting main packet loop. Jan 07 18:50:52 Weatherpi weewx[786]: restx: Wunderground-PWS: Published re...0) Jan 07 18:50:55 Weatherpi weewx[786]: vantage: LOOP try #1; error: Expected...ad Jan 07 18:51:32 Weatherpi weewx[786]: vantage: LOOP try #2; error: Expected...ad Hint: Some lines were ellipsized, use -l to show in full. pi@Weatherpi:~ $ 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] Re: Getting the RPi 3 with Davis Vantage up and running
...and this is what I get when I go back to the screen and the Laninstead of headless and through the wifi dongle! pi@Weatherpi:~ $ sudo systemctl status weewx ● weewx.service - LSB: weewx weather system Loaded: loaded (/etc/init.d/weewx) Active: active (running) since Mon 2019-01-07 18:31:04 NZDT; 6min ago Process: 538 ExecStart=/etc/init.d/weewx start (code=exited, status=0/SUCCESS) CGroup: /system.slice/weewx.service └─800 python /usr/bin/weewxd --daemon --pidfile=/var/run/weewx.pid... Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 14:3...b' Jan 07 18:38:01 Weatherpi weewx[800]: restx: Wunderground-PWS: Published re...0) Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 14:4...b' Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 14:4...b' Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 14:5...b' Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 14:5...b' Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 15:0...b' Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 15:0...b' Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 15:1...b' Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 15:1...b' Hint: Some lines were ellipsized, use -l to show in full. pi@Weatherpi:~ $ 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] Re: Getting the RPi 3 with Davis Vantage up and running
Yes, thank you Gary for your help..it is very much my problem and not yours! I have a new power supply and wifi dongle on order...that might help! Thanks for the digging on the WD data - will have a look at that in the next day or so! On Monday, 7 January 2019 19:00:56 UTC+13, gjr80 wrote: > > Ok, so on the face of it weeWX appears to be running fine. Not sure what > problem we are solving now? My post of about 2 hours ago was in an attempt > to work out if your headless RPi was running weeWX but it seems that is > down to a wifi/dongle issue. If weeWX is running OK then WU should be fine > as should your generated pages - checking syslog will show you what weeWX > is/is not doing. > > As an aside, I did a bit of digging on importing historical WD data. > Should be relatively straightforward, have started adding to wee_import. > Will let you know how it goes. > > Gary > > On Monday, 7 January 2019 15:54:22 UTC+10, monmul wrote: >> >> This is what I get headless and with the LAN as opposed to the wifi >> dongle! >> >> pi@Weatherpi:~ $ sudo systemctl status weewx >> ● weewx.service - LSB: weewx weather system >>Loaded: loaded (/etc/init.d/weewx) >>Active: active (running) since Mon 2019-01-07 18:50:45 NZDT; 50s ago >> Process: 510 ExecStart=/etc/init.d/weewx start (code=exited, >> status=0/SUCCESS) >>CGroup: /system.slice/weewx.service >>└─786 python /usr/bin/weewxd --daemon >> --pidfile=/var/run/weewx.pid... >> >> Jan 07 18:50:49 Weatherpi weewx[786]: restx: AWEKAS: Posting not enabled. >> Jan 07 18:50:49 Weatherpi weewx[786]: engine: Starting up weewx version >> 3.8.2 >> Jan 07 18:50:49 Weatherpi weewx[786]: engine: Clock error is -8.73 >> seconds ...t) >> Jan 07 18:50:49 Weatherpi weewx[786]: vantage: Clock set to 2019-01-07 >> 18:5...0) >> Jan 07 18:50:51 Weatherpi weewx[786]: manager: Added record 2019-01-07 >> 18:5...b' >> Jan 07 18:50:51 Weatherpi weewx[786]: manager: Added record 2019-01-07 >> 18:5...b' >> Jan 07 18:50:51 Weatherpi weewx[786]: engine: Starting main packet loop. >> Jan 07 18:50:52 Weatherpi weewx[786]: restx: Wunderground-PWS: Published >> re...0) >> Jan 07 18:50:55 Weatherpi weewx[786]: vantage: LOOP try #1; error: >> Expected...ad >> Jan 07 18:51:32 Weatherpi weewx[786]: vantage: LOOP try #2; error: >> Expected...ad >> Hint: Some lines were ellipsized, use -l to show in full. >> pi@Weatherpi:~ $ >> >> >> 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' suspe
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Ooops! one more thing.how do I do a wind offset? I cannot see it in the config file?! 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Very good questionthank you for pointing that out! I was totally unaware! On Tuesday, 8 January 2019 01:11:16 UTC+13, nine...@gmail.com wrote: > > Curious why you are using a Wi-Fi dongle? RPI 3 has Wi-Fi built in. > > > > Tom > > > > *From:* weewx...@googlegroups.com > *On Behalf Of *monmul > *Sent:* Monday, January 7, 2019 12:18 AM > *To:* weewx-user > > *Subject:* [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and > running > > > > Yes, thank you Gary for your help..it is very much my problem and not > yours! I have a new power supply and wifi dongle on order...that might help! > > > > Thanks for the digging on the WD data - will have a look at that in the > next day or so! > > On Monday, 7 January 2019 19:00:56 UTC+13, gjr80 wrote: > > Ok, so on the face of it weeWX appears to be running fine. Not sure what > problem we are solving now? My post of about 2 hours ago was in an attempt > to work out if your headless RPi was running weeWX but it seems that is > down to a wifi/dongle issue. If weeWX is running OK then WU should be fine > as should your generated pages - checking syslog will show you what weeWX > is/is not doing. > > > > As an aside, I did a bit of digging on importing historical WD data. > Should be relatively straightforward, have started adding to wee_import. > Will let you know how it goes. > > > > Gary > > > On Monday, 7 January 2019 15:54:22 UTC+10, monmul wrote: > > This is what I get headless and with the LAN as opposed to the wifi dongle! > > > > pi@Weatherpi:~ $ sudo systemctl status weewx > > ● weewx.service - LSB: weewx weather system > >Loaded: loaded (/etc/init.d/weewx) > >Active: active (running) since Mon 2019-01-07 18:50:45 NZDT; 50s ago > > Process: 510 ExecStart=/etc/init.d/weewx start (code=exited, > status=0/SUCCESS) > >CGroup: /system.slice/weewx.service > >└─786 python /usr/bin/weewxd --daemon > --pidfile=/var/run/weewx.pid... > > > > Jan 07 18:50:49 Weatherpi weewx[786]: restx: AWEKAS: Posting not enabled. > > Jan 07 18:50:49 Weatherpi weewx[786]: engine: Starting up weewx version > 3.8.2 > > Jan 07 18:50:49 Weatherpi weewx[786]: engine: Clock error is -8.73 seconds > ...t) > > Jan 07 18:50:49 Weatherpi weewx[786]: vantage: Clock set to 2019-01-07 > 18:5...0) > > Jan 07 18:50:51 Weatherpi weewx[786]: manager: Added record 2019-01-07 > 18:5...b' > > Jan 07 18:50:51 Weatherpi weewx[786]: manager: Added record 2019-01-07 > 18:5...b' > > Jan 07 18:50:51 Weatherpi weewx[786]: engine: Starting main packet loop. > > Jan 07 18:50:52 Weatherpi weewx[786]: restx: Wunderground-PWS: Published > re...0) > > Jan 07 18:50:55 Weatherpi weewx[786]: vantage: LOOP try #1; error: > Expected...ad > > Jan 07 18:51:32 Weatherpi weewx[786]: vantage: LOOP try #2; error: > Expected...ad > > Hint: Some lines were ellipsized, use -l to show in full. > > pi@Weatherpi:~ $ > > > > > 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 > <https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rsyslog.com%2Fe%2F2007&data=02%7C01%7C%7Cec7be512b46e483e42f208d67467efb5%7C84df9e7fe9f640afb435%7C1%7C0%7C636824387077922531&sdata=nb3iG0BxfDbMLD8LJld7FzFcu%2BJoWKokZTjsydL9DLY%3D&reserved=0> > ] > > Jan 6 13:41:06 Weather
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
I notice an error in the archival interval - see below. Is this important? Jan 8 11:07:08 Weatherpi weewx[750]: engine: Archive will use data binding wx_binding Jan 8 11:07:08 Weatherpi weewx[750]: engine: Record generation will be attempted in 'hardware' Jan 8 11:07:08 Weatherpi weewx[750]: engine: The archive interval in the configuration file (300) does not match the station hardware interval (600). Jan 8 11:07:08 Weatherpi weewx[750]: engine: Using archive interval of 600 seconds (specified by hardware) Jan 8 11:07:08 Weatherpi weewx[750]: engine: Using binding 'wx_binding' to database 'weewx.sdb' Jan 8 11:07:08 Weatherpi weewx[750]: manager: Starting backfill of daily summaries Jan 8 11:07:08 Weatherpi weewx[750]: restx: StationRegistry: Station will not be registered: no station_url specified. Jan 8 11:07:08 Weatherpi weewx[750]: restx: Wunderground-PWS: Data for station IOTAGOQU2 will be posted Jan 8 11:07:08 Weatherpi weewx[750]: restx: PWSweather: Posting not enabled. Jan 8 11:07:08 Weatherpi weewx[750]: restx: CWOP: Posting not enabled. Jan 8 11:07:08 Weatherpi weewx[750]: restx: WOW: Posting not enabled. Jan 8 11:07:08 Weatherpi weewx[750]: restx: AWEKAS: Posting not enabled. Jan 8 11:07:08 Weatherpi weewx[750]: engine: Starting up weewx version 3.8.2 Jan 8 11:07:08 Weatherpi weewx[750]: engine: Clock error is -7.50 seconds (positive is fast) Jan 8 11:07:08 Weatherpi weewx[750]: vantage: Clock set to 2019-01-08 11:07:09 NZDT (1546898829) Jan 8 11:07:09 Weatherpi weewx[750]: engine: Starting main packet loop. Jan 8 11:07:14 Weatherpi weewx[750]: vantage: LOOP try #1; error: Expected to read 99 chars; got 0 instead Jan 8 11:07:19 Weatherpi weewx[750]: vantage: LOOP try #2; error: Expected to read 99 chars; got 0 instead Jan 8 11:07:28 Weatherpi weewx[750]: vantage: LOOP try #3; error: Expected to read 99 chars; got 0 instead Jan 8 11:07:33 Weatherpi weewx[750]: vantage: LOOP try #4; error: Expected to read 99 chars; got 0 instead Jan 8 11:07:33 Weatherpi weewx[750]: vantage: LOOP max tries (4) exceeded. Jan 8 11:07:33 Weatherpi weewx[750]: engine: Caught WeeWxIOError: Max tries exceeded while getting LOOP data. Jan 8 11:07:33 Weatherpi weewx[750]: Waiting 60 seconds then retrying... 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? > > >
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Worked perfectly, thank you! On Monday, 7 January 2019 20:09:53 UTC+13, gjr80 wrote: > > Yes. That is a setting for the console rather than a weeWX config setting. > You have two choices; you can set it manually via buttons on the console or > you can set it using the wee_device > <http://weewx.com/docs/utilities.htm#wee_device_utility> utility. To do > the former you need to read the console manual :) For the latter have a > look through the wee_device Vantage notes > <http://weewx.com/docs/hardware.htm#vantage_notes>, you need to use the > --set-offset > action <http://weewx.com/docs/hardware.htm#vantage_setting_offsets>. > Something like: > > $ wee_device --set-offset=windDir,180 > > should do the trick, in fact that is one of the examples. Note you may or > may not need to prefix that with sudo. Just make sure you read through the > Vantage wee_device notes first, make sure you stop weeWX before using > wee_device (only one thing can talk to the console at once) and check the > setting afterwards with wee_device --info > > Gary > > On Monday, 7 January 2019 16:22:40 UTC+10, monmul wrote: > >> Ooops! one more thing.how do I do a wind offset? I cannot see it in >> the config file?! >> >> 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] Re: Getting the RPi 3 with Davis Vantage up and running
Great, thanks, it seems to be working ok now.and I will just stick with the 600 sec. On Tuesday, 8 January 2019 19:18:12 UTC+13, gjr80 wrote: > > > On Tuesday, 8 January 2019 08:14:28 UTC+10, monmul wrote: >> >> I notice an error in the archival interval - see below. Is this important? >> >> Jan 8 11:07:08 Weatherpi weewx[750]: engine: The archive interval in the >> configuration file (300) does not match the station hardware interval (600). >> Jan 8 11:07:08 Weatherpi weewx[750]: engine: Using archive interval of >> 600 seconds (specified by hardware) >> > > I presume you mean the 600/300 log entries above and not the LOOP errors > below. The two entries above mean that the archive interval set in your > console (600 seconds) does not match the archive interval under > [StdArchive] in weewx.conf. When such a disagreement occurs weeWX > defaults to using the console value, so in your case it uses 600 seconds > and you will find that you have archive records being saved to database > (and reports being generated) every 600 seconds (10 minutes). If you want > to change this to 300 seconds (5 minutes) you will need to change the > archive interval in your console. As with the wind direction offset this > can be done through the console buttons or using the wee_device utility. > For wee_device it's the same process as setting the wind direction > offset, but this time you would use the --set-interval action > <http://weewx.com/docs/hardware.htm#vantage_archive_interval46>. > > >> Jan 8 11:07:14 Weatherpi weewx[750]: vantage: LOOP try #1; error: >> Expected to read 99 chars; got 0 instead >> Jan 8 11:07:19 Weatherpi weewx[750]: vantage: LOOP try #2; error: >> Expected to read 99 chars; got 0 instead >> Jan 8 11:07:28 Weatherpi weewx[750]: vantage: LOOP try #3; error: >> Expected to read 99 chars; got 0 instead >> Jan 8 11:07:33 Weatherpi weewx[750]: vantage: LOOP try #4; error: >> Expected to read 99 chars; got 0 instead >> Jan 8 11:07:33 Weatherpi weewx[750]: vantage: LOOP max tries (4) >> exceeded. >> Jan 8 11:07:33 Weatherpi weewx[750]: engine: Caught WeeWxIOError: Max >> tries exceeded while getting LOOP data. >> Jan 8 11:07:33 Weatherpi weewx[750]: Waiting 60 seconds then >> retrying... >> > > As for the LOOP errors, that indicates that your RPi is not able to > communicate with your console. You have had it working and the vantage > stations tend to just work so go through some basic checking (is it plugged > in is something else interfering, unplug/plug in the station again, stop > then start weeWX). Remember monitor the log, it will tell you what is going > on. A useful approach can be to have two terminals open; one for issuing > commands and one for monitoring the log with the command: > > $ tail -f -n 20 /var/log/syslog > > This shows you the last 20 lines of syslog then automatically displays any > additional log entries as they occur. Makes it easy to see what happens > when you issue commands. > > 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: Getting the RPi 3 with Davis Vantage up and running
In trying to copy my sd card for back up purposes, I ended up screwing my ststem and had to start again. I thought I had followed all the steps to get it working like I had last time.but I get this error: pi@raspberrypi:~ $ sudo weewxd /etc/weewx/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 877, in main engine.run() File "/usr/share/weewx/weewx/engine.py", line 160, in run self.dispatchEvent(weewx.Event(weewx.STARTUP)) File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent callback(event) File "/usr/share/weewx/weewx/engine.py", line 509, in startup self._catchup(self.engine.console.genStartupRecords) File "/usr/share/weewx/weewx/engine.py", line 623, in _catchup origin='hardware')) File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent callback(event) File "/usr/share/weewx/weewx/engine.py", line 589, in new_archive_record dbmanager.addRecord(event.record, accumulator=self.old_accumulator) File "/usr/share/weewx/weewx/manager.py", line 245, in addRecord self._addSingleRecord(record, cursor, log_level) File "/usr/share/weewx/weewx/manager.py", line 1190, in _addSingleRecord super(DaySummaryManager, self)._addSingleRecord(record, cursor, log_level=log_level) File "/usr/share/weewx/weewx/manager.py", line 270, in _addSingleRecord self._check_unit_system(record['usUnits']) File "/usr/share/weewx/weewx/manager.py", line 671, in _check_unit_system self.std_unit_system)) weewx.UnitError: Unit system of incoming record (0x10) differs from 'archive' table in 'weewx.sdb' database (0x01) where have I gone wrong this time? On Tuesday, 8 January 2019 19:27:51 UTC+13, gjr80 wrote: > > Ok, if you are going to stick with a 600 second archive period then just > change archive_interval = 300 to archive_interval = 600 under [StdArchive] > in weewx.conf and you should not see that message again. > > Gary > > On Tuesday, 8 January 2019 16:24:17 UTC+10, monmul wrote: >> >> Great, thanks, it seems to be working ok now.and I will just stick >> with the 600 sec. >> >> On Tuesday, 8 January 2019 19:18:12 UTC+13, gjr80 wrote: >>> >>> >>> On Tuesday, 8 January 2019 08:14:28 UTC+10, monmul wrote: >>>> >>>> I notice an error in the archival interval - see below. Is this >>>> important? >>>> >>>> Jan 8 11:07:08 Weatherpi weewx[750]: engine: The archive interval in >>>> the configuration file (300) does not match the station hardware interval >>>> (600). >>>> Jan 8 11:07:08 Weatherpi weewx[750]: engine: Using archive interval of >>>> 600 seconds (specified by hardware) >>>> >>> >>> I presume you mean the 600/300 log entries above and not the LOOP errors >>> below. The two entries above mean that the archive interval set in your >>> console (600 seconds) does not match the archive interval under >>> [StdArchive] in weewx.conf. When such a disagreement occurs weeWX >>> defaults to using the console value, so in your case it uses 600 seconds >>> and you will find that you have archive records being saved to database >>> (and reports being generated) every 600 seconds (10 minutes). If you want >>> to change this to 300 seconds (5 minutes) you will need to change the >>> archive interval in your console. As with the wind direction offset this >>> can be done through the console buttons or using the wee_device >>> utility. For wee_device it's the same process as setting the wind >>> direction offset, but this time you would use the --set-interval action >>> <http://weewx.com/docs/hardware.htm#vantage_archive_interval46>. >>> >>> >>>> Jan 8 11:07:14 Weatherpi weewx[750]: vantage: LOOP try #1; error: >>>> Expected to read 99 chars; got 0 instead >>>> Jan 8 11:07:19 Weatherpi weewx[750]: vantage: LOOP try #2; error: >>>> Expected to read 99 chars; got 0 instead >>>> Jan 8 11:07:28 Weatherpi weewx[750]: vantage: LOOP try #3; error: >>>> Expected to read 99 chars; got 0 instead >>>> Jan 8 11:07:33 Weatherpi weewx[750]: vantage: LOOP try #4; error: >>>> Expected to read 99 chars; got 0 instead >>>> Jan 8 11:07:33 Weatherpi weewx[750]: vantage: LOOP max tries (4) >>>> exceeded. >>>> Jan 8 11:07:33 Weatherpi weewx[750]: engine: Caught WeeWxIOErro
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
As usual, Gary, spot on.all working nicely again now!.Thank you so much I really appreciate your help an advice. On Saturday, 12 January 2019 14:03:17 UTC+13, gjr80 wrote: > > On Saturday, 12 January 2019 07:12:04 UTC+10, monmul wrote: >> >> weewx.UnitError: Unit system of incoming record (0x10) differs from >> 'archive' table in 'weewx.sdb' database (0x01) >> > > This line is telling us that the unit system used by your database (in > this case 0x01 or US customary) does not match the unit system of the > record (in this case 0x10 or Metric) that is about to be saved to database. > When you rebuilt your system what did you put in weewx.conf for setting > target_unit under [StdConvert], it should match the units system of your > database (ie target_unit = US) but I am guessing it says target_unit = > METRIC? If so you have two options. Firstly, you can change target_unit > back to target_unit = US or secondly you can delete you database and let > weeWX build a new one when your restart weeWX. The advantage of the first > option is that you retain any existing data, for the second option you lose > any historical data and your database will now be in Metric units not the > default US. The unit system of your database does not really matter, weeWX > handles all conversions so you will still see your preferred (Metric ?) > units displayed in reports. It is just the underlying database data that is > in US customary units. Most folks never interact directly with their > databases anyway. > > You will find a bit of information about unit systems under [StdConvert] > <http://weewx.com/docs/usersguide.htm#StdConvert> in the User's Guide and > under Changing the unit system > <http://weewx.com/docs/customizing.htm#Changing_the_unit_system> and in > the Units appendix <http://weewx.com/docs/customizing.htm#units> in the > Customization Guide. > > Of course if target_unit actually is set to US then we have some other > issue going on. > > 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: Getting the RPi 3 with Davis Vantage up and running
I have managed to get the Standard skin loaded on my weather website www.wilsonbayweather.com...2 small adjustments I would like to make..how do I show the historical max and min for temp, wind, rain etcand how might I include a jpeg photo from webcam showing a picture every hour or so? Thanks in advance.you guys have been fabulous in helping a newbie! 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] Re: Getting the RPi 3 with Davis Vantage up and running
WOW! thank you so much, Gary, for the pointers.I will get on to that in the next few days! On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote: > > Hi, > > There are a few steps involved in achieving what you want to do. First the > historical max/min - by this I presume you mean all time statistics - those > that cover all of your weeWX data and not just the last day, month or year. > > If I have this right you need to extend weeWX so that you can access stats > from all of your data, this is most easily achieved by installing the > xstats example extension. You will find the xstats files are in the > /usr/share/doc/weewx/examples directory. I would install manually and > just follow step 1 in the readme.txt remembering later that you will need > to enable the alltime stats for your templates/reports by following step 2. > You can install xstats using wee_extension but that will also install the > example web page which you probably do not want. > > Now that you have xstats installed you can use tags like > $alltime.outTemp.max in report templates to display the maximum outside > temperature. The time it occurred will be $alltime.outTemp.maxtime. Just > like $day, $month and $year tags but you use $alltime. If you are not > familiar with weeWX tags it is worth reading the Tags section > <http://weewx.com/docs/customizing.htm#Tags> of the Customization Guide. > > To use the $alltime tags you will probably want to create a new page or > modify an existing one. It is really up to you want you want to do. To > modify an existing page have a look at the .tmpl files in you Standard > skin directory /etc/weewx/skins/Standard. These are the files weeWX uses > to generate a corresponding .html page. You will see how tags are used in a > template, in a nutshell where you place a tag weeWX will replace that with > the relevant data when the reports are generated. The process is a little > more involved if you want to create a new page as not only do you need to > modify/create a page but you also need to modify skin.conf to have weeWX > generate the new page. You may also need to modify other pages to include a > link to your new page. A good starting point may be to take a copy of > /etc/weewx/skins/Standard/year.html.tmpl, save it as alltime.html.tmpl > and start modifying. Have a good poke around the templates and skin.conf > (and [StdReport] in weewx.conf) to see how it comes together. > > Including an image in a weeWX generated page can be relatively > straightforward. If you have a look in index.html.tmpl you will see lines > such as: > > > > This line creates a HTML img tag that displays the daily temperature and > dewpoint plot. If whatever you use to generate your webcam image can create > a file named, say, webcam.jpg then that keeps it easy, you may be able to > create a new img tag but using webcam.jpg (rather than daytempdew.png), > you may need to add a path in front of the file name. If your webcam image > is timestamped like webcam201901131345.jpg then that gets a little more > complicated. If you can drop your webcam image into the weeWX directory > structure under /var/www/html/weewx then you can very easily use weeWX to > upload your webcam image to your web server if you wish. There are many > different ways to achieve this, I have outlined one and I am sure other > will have other ways. At the end of the day it will likely depend on your > setup. > > You have started on the slippery slope of customising your weeWX install, > the process can appear daunting but do persist and feel free to continue to > ask if not sure. > > Gary > > On Sunday, 13 January 2019 11:25:59 UTC+10, monmul wrote: >> >> I have managed to get the Standard skin loaded on my weather website >> www.wilsonbayweather.com...2 small adjustments I would like to >> make..how do I show the historical max and min for temp, wind, rain >> etcand how might I include a jpeg photo from webcam showing a picture >> every hour or so? Thanks in advance.you guys have been fabulous in >> helping a newbie! >> >> -- 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
Just BTW, the readme.txt is wrong about where wee_extension is
stored.as under a deb install it is stored in /usr/share/weewx/
When I run the suggested command, this is what I get.
pi@raspberrypi:~ $ wee_extension --install=/usr/share/weewx/wee_extension
Request to install '/usr/share/weewx/wee_extension'
Extracting from tar archive /usr/share/weewx/wee_extension
Traceback (most recent call last):
File "/usr/bin/wee_extension", line 83, in
main()
File "/usr/bin/wee_extension", line 75, in main
ext.install_extension(options.install)
File "/usr/share/weewx/weecfg/extension.py", line 110, in
install_extension
self.tmpdir, self.logger)
File "/usr/share/weewx/weecfg/__init__.py", line 1240, in extract_tar
tar_archive = tarfile.open(filename, mode='r')
File "/usr/lib/python2.7/tarfile.py", line 1680, in open
raise ReadError("file could not be opened successfully")
tarfile.ReadError: file could not be opened successfully
On Sunday, 13 January 2019 17:15:11 UTC+13, monmul wrote:
>
> WOW! thank you so much, Gary, for the pointers.I will get on to that
> in the next few days!
>
> On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote:
>>
>> Hi,
>>
>> There are a few steps involved in achieving what you want to do. First
>> the historical max/min - by this I presume you mean all time statistics -
>> those that cover all of your weeWX data and not just the last day, month or
>> year.
>>
>> If I have this right you need to extend weeWX so that you can access
>> stats from all of your data, this is most easily achieved by installing the
>> xstats example extension. You will find the xstats files are in the
>> /usr/share/doc/weewx/examples directory. I would install manually and
>> just follow step 1 in the readme.txt remembering later that you will
>> need to enable the alltime stats for your templates/reports by following
>> step 2. You can install xstats using wee_extension but that will also
>> install the example web page which you probably do not want.
>>
>> Now that you have xstats installed you can use tags like
>> $alltime.outTemp.max in report templates to display the maximum outside
>> temperature. The time it occurred will be $alltime.outTemp.maxtime. Just
>> like $day, $month and $year tags but you use $alltime. If you are not
>> familiar with weeWX tags it is worth reading the Tags section
>> <http://weewx.com/docs/customizing.htm#Tags> of the Customization Guide.
>>
>> To use the $alltime tags you will probably want to create a new page or
>> modify an existing one. It is really up to you want you want to do. To
>> modify an existing page have a look at the .tmpl files in you Standard
>> skin directory /etc/weewx/skins/Standard. These are the files weeWX uses
>> to generate a corresponding .html page. You will see how tags are used in a
>> template, in a nutshell where you place a tag weeWX will replace that with
>> the relevant data when the reports are generated. The process is a little
>> more involved if you want to create a new page as not only do you need to
>> modify/create a page but you also need to modify skin.conf to have weeWX
>> generate the new page. You may also need to modify other pages to include a
>> link to your new page. A good starting point may be to take a copy of
>> /etc/weewx/skins/Standard/year.html.tmpl, save it as alltime.html.tmpl
>> and start modifying. Have a good poke around the templates and skin.conf
>> (and [StdReport] in weewx.conf) to see how it comes together.
>>
>> Including an image in a weeWX generated page can be relatively
>> straightforward. If you have a look in index.html.tmpl you will see
>> lines such as:
>>
>>
>>
>> This line creates a HTML img tag that displays the daily temperature and
>> dewpoint plot. If whatever you use to generate your webcam image can create
>> a file named, say, webcam.jpg then that keeps it easy, you may be able
>> to create a new img tag but using webcam.jpg (rather than daytempdew.png),
>> you may need to add a path in front of the file name. If your webcam image
>> is timestamped like webcam201901131345.jpg then that gets a little more
>> complicated. If you can drop your webcam image into the weeWX directory
>> structure under /var/www/html/weewx then you can very easily use weeWX
>> to upload your webcam image to your web server if you wish. There are many
>> different ways to achieve this, I have outlined one and I am sure other
>> will have other ways. At the end of the day it will likely depend on your
&
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
I am searching for how to turn off showing the "internal temperature" graph but cannot see a anything in skin.conf or in weewx.conf.what am I missing? On Sunday, 13 January 2019 17:15:11 UTC+13, monmul wrote: > > WOW! thank you so much, Gary, for the pointers.I will get on to that > in the next few days! > > On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote: >> >> Hi, >> >> There are a few steps involved in achieving what you want to do. First >> the historical max/min - by this I presume you mean all time statistics - >> those that cover all of your weeWX data and not just the last day, month or >> year. >> >> If I have this right you need to extend weeWX so that you can access >> stats from all of your data, this is most easily achieved by installing the >> xstats example extension. You will find the xstats files are in the >> /usr/share/doc/weewx/examples directory. I would install manually and >> just follow step 1 in the readme.txt remembering later that you will >> need to enable the alltime stats for your templates/reports by following >> step 2. You can install xstats using wee_extension but that will also >> install the example web page which you probably do not want. >> >> Now that you have xstats installed you can use tags like >> $alltime.outTemp.max in report templates to display the maximum outside >> temperature. The time it occurred will be $alltime.outTemp.maxtime. Just >> like $day, $month and $year tags but you use $alltime. If you are not >> familiar with weeWX tags it is worth reading the Tags section >> <http://weewx.com/docs/customizing.htm#Tags> of the Customization Guide. >> >> To use the $alltime tags you will probably want to create a new page or >> modify an existing one. It is really up to you want you want to do. To >> modify an existing page have a look at the .tmpl files in you Standard >> skin directory /etc/weewx/skins/Standard. These are the files weeWX uses >> to generate a corresponding .html page. You will see how tags are used in a >> template, in a nutshell where you place a tag weeWX will replace that with >> the relevant data when the reports are generated. The process is a little >> more involved if you want to create a new page as not only do you need to >> modify/create a page but you also need to modify skin.conf to have weeWX >> generate the new page. You may also need to modify other pages to include a >> link to your new page. A good starting point may be to take a copy of >> /etc/weewx/skins/Standard/year.html.tmpl, save it as alltime.html.tmpl >> and start modifying. Have a good poke around the templates and skin.conf >> (and [StdReport] in weewx.conf) to see how it comes together. >> >> Including an image in a weeWX generated page can be relatively >> straightforward. If you have a look in index.html.tmpl you will see >> lines such as: >> >> >> >> This line creates a HTML img tag that displays the daily temperature and >> dewpoint plot. If whatever you use to generate your webcam image can create >> a file named, say, webcam.jpg then that keeps it easy, you may be able >> to create a new img tag but using webcam.jpg (rather than daytempdew.png), >> you may need to add a path in front of the file name. If your webcam image >> is timestamped like webcam201901131345.jpg then that gets a little more >> complicated. If you can drop your webcam image into the weeWX directory >> structure under /var/www/html/weewx then you can very easily use weeWX >> to upload your webcam image to your web server if you wish. There are many >> different ways to achieve this, I have outlined one and I am sure other >> will have other ways. At the end of the day it will likely depend on your >> setup. >> >> You have started on the slippery slope of customising your weeWX install, >> the process can appear daunting but do persist and feel free to continue to >> ask if not sure. >> >> Gary >> >> On Sunday, 13 January 2019 11:25:59 UTC+10, monmul wrote: >>> >>> I have managed to get the Standard skin loaded on my weather website >>> www.wilsonbayweather.com...2 small adjustments I would like to >>> make..how do I show the historical max and min for temp, wind, rain >>> etcand how might I include a jpeg photo from webcam showing a picture >>> every hour or so? Thanks in advance.you guys have been fabulous in >>> helping a newbie! >>> >>> -- 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
Thanks Tom, got that now!my jpg is appearing before and not after the ISS signal quality..I cannot find a ref to the signal quality in the Index file.how can I get the jpg to come after the signal quality graphs? On Monday, 14 January 2019 10:13:08 UTC+13, nine...@gmail.com wrote: > > Look towards the bottom of the index.html.temp file in the skins/standard > directory. You will see . > Comment out this line. > > > > Tom > > > > *From:* weewx...@googlegroups.com > *On Behalf Of *monmul > *Sent:* Sunday, January 13, 2019 2:48 PM > *To:* weewx-user > > *Subject:* [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and > running > > > > I am searching for how to turn off showing the "internal temperature" > graph but cannot see a anything in skin.conf or in weewx.conf.....what > am I missing? > > On Sunday, 13 January 2019 17:15:11 UTC+13, monmul wrote: > > WOW! thank you so much, Gary, for the pointers.I will get on to that > in the next few days! > > On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote: > > Hi, > > > > There are a few steps involved in achieving what you want to do. First the > historical max/min - by this I presume you mean all time statistics - those > that cover all of your weeWX data and not just the last day, month or year. > > > > If I have this right you need to extend weeWX so that you can access stats > from all of your data, this is most easily achieved by installing the > xstats example extension. You will find the xstats files are in the > /usr/share/doc/weewx/examples directory. I would install manually and > just follow step 1 in the readme.txt remembering later that you will need > to enable the alltime stats for your templates/reports by following step 2. > You can install xstats using wee_extension but that will also install the > example web page which you probably do not want. > > > > Now that you have xstats installed you can use tags like > $alltime.outTemp.max in report templates to display the maximum outside > temperature. The time it occurred will be $alltime.outTemp.maxtime. Just > like $day, $month and $year tags but you use $alltime. If you are not > familiar with weeWX tags it is worth reading the Tags section > <https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fweewx.com%2Fdocs%2Fcustomizing.htm%23Tags&data=02%7C01%7C%7C2fa0f5605abe40a0fa5908d679987943%7C84df9e7fe9f640afb435%7C1%7C0%7C636830093103704415&sdata=JlVtj%2FUmreXhF%2FZ%2FmGuwvzv%2F%2FM0LfMDZGGgws4chDu8%3D&reserved=0> > > of the Customization Guide. > > > > To use the $alltime tags you will probably want to create a new page or > modify an existing one. It is really up to you want you want to do. To > modify an existing page have a look at the .tmpl files in you Standard > skin directory /etc/weewx/skins/Standard. These are the files weeWX uses > to generate a corresponding .html page. You will see how tags are used in a > template, in a nutshell where you place a tag weeWX will replace that with > the relevant data when the reports are generated. The process is a little > more involved if you want to create a new page as not only do you need to > modify/create a page but you also need to modify skin.conf to have weeWX > generate the new page. You may also need to modify other pages to include a > link to your new page. A good starting point may be to take a copy of > /etc/weewx/skins/Standard/year.html.tmpl, save it as alltime.html.tmpl > and start modifying. Have a good poke around the templates and skin.conf > (and [StdReport] in weewx.conf) to see how it comes together. > > > > Including an image in a weeWX generated page can be relatively > straightforward. If you have a look in index.html.tmpl you will see lines > such as: > > > > > > > > This line creates a HTML img tag that displays the daily temperature and > dewpoint plot. If whatever you use to generate your webcam image can create > a file named, say, webcam.jpg then that keeps it easy, you may be able to > create a new img tag but using webcam.jpg (rather than daytempdew.png), > you may need to add a path in front of the file name. If your webcam image > is timestamped like webcam201901131345.jpg then that gets a little more > complicated. If you can drop your webcam image into the weeWX directory > structure under /var/www/html/weewx then you can very easily use weeWX to > upload your webcam image to your web server if you wish. There are many > different ways to achieve this, I have outlined one and I am sure other > will have other ways. At the end of the day it will li
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
OK, got the jpg after the ISS signal working it seemsnot sure how! On Monday, 14 January 2019 11:40:45 UTC+13, monmul wrote: > > Thanks Tom, got that now!my jpg is appearing before and not after > the ISS signal quality..I cannot find a ref to the signal quality in > the Index file.how can I get the jpg to come after the signal quality > graphs? > > On Monday, 14 January 2019 10:13:08 UTC+13, nine...@gmail.com wrote: >> >> Look towards the bottom of the index.html.temp file in the skins/standard >> directory. You will see . >> Comment out this line. >> >> >> >> Tom >> >> >> >> *From:* weewx...@googlegroups.com *On Behalf >> Of *monmul >> *Sent:* Sunday, January 13, 2019 2:48 PM >> *To:* weewx-user >> *Subject:* [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and >> running >> >> >> >> I am searching for how to turn off showing the "internal temperature" >> graph but cannot see a anything in skin.conf or in weewx.conf.what >> am I missing? >> >> On Sunday, 13 January 2019 17:15:11 UTC+13, monmul wrote: >> >> WOW! thank you so much, Gary, for the pointers.I will get on to that >> in the next few days! >> >> On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote: >> >> Hi, >> >> >> >> There are a few steps involved in achieving what you want to do. First >> the historical max/min - by this I presume you mean all time statistics - >> those that cover all of your weeWX data and not just the last day, month or >> year. >> >> >> >> If I have this right you need to extend weeWX so that you can access >> stats from all of your data, this is most easily achieved by installing the >> xstats example extension. You will find the xstats files are in the >> /usr/share/doc/weewx/examples directory. I would install manually and >> just follow step 1 in the readme.txt remembering later that you will >> need to enable the alltime stats for your templates/reports by following >> step 2. You can install xstats using wee_extension but that will also >> install the example web page which you probably do not want. >> >> >> >> Now that you have xstats installed you can use tags like >> $alltime.outTemp.max in report templates to display the maximum outside >> temperature. The time it occurred will be $alltime.outTemp.maxtime. Just >> like $day, $month and $year tags but you use $alltime. If you are not >> familiar with weeWX tags it is worth reading the Tags section >> <https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fweewx.com%2Fdocs%2Fcustomizing.htm%23Tags&data=02%7C01%7C%7C2fa0f5605abe40a0fa5908d679987943%7C84df9e7fe9f640afb435%7C1%7C0%7C636830093103704415&sdata=JlVtj%2FUmreXhF%2FZ%2FmGuwvzv%2F%2FM0LfMDZGGgws4chDu8%3D&reserved=0> >> >> of the Customization Guide. >> >> >> >> To use the $alltime tags you will probably want to create a new page or >> modify an existing one. It is really up to you want you want to do. To >> modify an existing page have a look at the .tmpl files in you Standard >> skin directory /etc/weewx/skins/Standard. These are the files weeWX uses >> to generate a corresponding .html page. You will see how tags are used in a >> template, in a nutshell where you place a tag weeWX will replace that with >> the relevant data when the reports are generated. The process is a little >> more involved if you want to create a new page as not only do you need to >> modify/create a page but you also need to modify skin.conf to have weeWX >> generate the new page. You may also need to modify other pages to include a >> link to your new page. A good starting point may be to take a copy of >> /etc/weewx/skins/Standard/year.html.tmpl, save it as alltime.html.tmpl >> and start modifying. Have a good poke around the templates and skin.conf >> (and [StdReport] in weewx.conf) to see how it comes together. >> >> >> >> Including an image in a weeWX generated page can be relatively >> straightforward. If you have a look in index.html.tmpl you will see >> lines such as: >> >> >> >> >> >> >> >> This line creates a HTML img tag that displays the daily temperature and >> dewpoint plot. If whatever you use to generate your webcam image can create >> a file named, say, webcam.jpg then that keeps it easy, you may be able >> to create a new img tag but using webcam.jpg (rather than day
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
In installing xstats manually, the read_me suggests the following for step 1: cp bin/user/xstats.py /home/weewx/bin/user I can find where xstats.py is located on the Rpi (hint - /usr/share/doc/weewx/examples/xstats/bin/usr/xstats.py)but where do I copy it to? On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote: > > Hi, > > There are a few steps involved in achieving what you want to do. First the > historical max/min - by this I presume you mean all time statistics - those > that cover all of your weeWX data and not just the last day, month or year. > > If I have this right you need to extend weeWX so that you can access stats > from all of your data, this is most easily achieved by installing the > xstats example extension. You will find the xstats files are in the > /usr/share/doc/weewx/examples directory. I would install manually and > just follow step 1 in the readme.txt remembering later that you will need > to enable the alltime stats for your templates/reports by following step 2. > You can install xstats using wee_extension but that will also install the > example web page which you probably do not want. > > Now that you have xstats installed you can use tags like > $alltime.outTemp.max in report templates to display the maximum outside > temperature. The time it occurred will be $alltime.outTemp.maxtime. Just > like $day, $month and $year tags but you use $alltime. If you are not > familiar with weeWX tags it is worth reading the Tags section > <http://weewx.com/docs/customizing.htm#Tags> of the Customization Guide. > > To use the $alltime tags you will probably want to create a new page or > modify an existing one. It is really up to you want you want to do. To > modify an existing page have a look at the .tmpl files in you Standard > skin directory /etc/weewx/skins/Standard. These are the files weeWX uses > to generate a corresponding .html page. You will see how tags are used in a > template, in a nutshell where you place a tag weeWX will replace that with > the relevant data when the reports are generated. The process is a little > more involved if you want to create a new page as not only do you need to > modify/create a page but you also need to modify skin.conf to have weeWX > generate the new page. You may also need to modify other pages to include a > link to your new page. A good starting point may be to take a copy of > /etc/weewx/skins/Standard/year.html.tmpl, save it as alltime.html.tmpl > and start modifying. Have a good poke around the templates and skin.conf > (and [StdReport] in weewx.conf) to see how it comes together. > > Including an image in a weeWX generated page can be relatively > straightforward. If you have a look in index.html.tmpl you will see lines > such as: > > > > This line creates a HTML img tag that displays the daily temperature and > dewpoint plot. If whatever you use to generate your webcam image can create > a file named, say, webcam.jpg then that keeps it easy, you may be able to > create a new img tag but using webcam.jpg (rather than daytempdew.png), > you may need to add a path in front of the file name. If your webcam image > is timestamped like webcam201901131345.jpg then that gets a little more > complicated. If you can drop your webcam image into the weeWX directory > structure under /var/www/html/weewx then you can very easily use weeWX to > upload your webcam image to your web server if you wish. There are many > different ways to achieve this, I have outlined one and I am sure other > will have other ways. At the end of the day it will likely depend on your > setup. > > You have started on the slippery slope of customising your weeWX install, > the process can appear daunting but do persist and feel free to continue to > ask if not sure. > > Gary > > On Sunday, 13 January 2019 11:25:59 UTC+10, monmul wrote: >> >> I have managed to get the Standard skin loaded on my weather website >> www.wilsonbayweather.com...2 small adjustments I would like to >> make..how do I show the historical max and min for temp, wind, rain >> etcand how might I include a jpeg photo from webcam showing a picture >> every hour or so? Thanks in advance.you guys have been fabulous in >> helping a newbie! >> >> -- 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
I presume that $rainyear.rain.sum will become $rainalltime.rain.sum? On Monday, 14 January 2019 22:21:01 UTC+13, monmul wrote: > > In installing xstats manually, the read_me suggests the following for step > 1: > > cp bin/user/xstats.py /home/weewx/bin/user > > I can find where xstats.py is located on the Rpi (hint - > /usr/share/doc/weewx/examples/xstats/bin/usr/xstats.py)but where do I > copy it to? > > > On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote: >> >> Hi, >> >> There are a few steps involved in achieving what you want to do. First >> the historical max/min - by this I presume you mean all time statistics - >> those that cover all of your weeWX data and not just the last day, month or >> year. >> >> If I have this right you need to extend weeWX so that you can access >> stats from all of your data, this is most easily achieved by installing the >> xstats example extension. You will find the xstats files are in the >> /usr/share/doc/weewx/examples directory. I would install manually and >> just follow step 1 in the readme.txt remembering later that you will >> need to enable the alltime stats for your templates/reports by following >> step 2. You can install xstats using wee_extension but that will also >> install the example web page which you probably do not want. >> >> Now that you have xstats installed you can use tags like >> $alltime.outTemp.max in report templates to display the maximum outside >> temperature. The time it occurred will be $alltime.outTemp.maxtime. Just >> like $day, $month and $year tags but you use $alltime. If you are not >> familiar with weeWX tags it is worth reading the Tags section >> <http://weewx.com/docs/customizing.htm#Tags> of the Customization Guide. >> >> To use the $alltime tags you will probably want to create a new page or >> modify an existing one. It is really up to you want you want to do. To >> modify an existing page have a look at the .tmpl files in you Standard >> skin directory /etc/weewx/skins/Standard. These are the files weeWX uses >> to generate a corresponding .html page. You will see how tags are used in a >> template, in a nutshell where you place a tag weeWX will replace that with >> the relevant data when the reports are generated. The process is a little >> more involved if you want to create a new page as not only do you need to >> modify/create a page but you also need to modify skin.conf to have weeWX >> generate the new page. You may also need to modify other pages to include a >> link to your new page. A good starting point may be to take a copy of >> /etc/weewx/skins/Standard/year.html.tmpl, save it as alltime.html.tmpl >> and start modifying. Have a good poke around the templates and skin.conf >> (and [StdReport] in weewx.conf) to see how it comes together. >> >> Including an image in a weeWX generated page can be relatively >> straightforward. If you have a look in index.html.tmpl you will see >> lines such as: >> >> >> >> This line creates a HTML img tag that displays the daily temperature and >> dewpoint plot. If whatever you use to generate your webcam image can create >> a file named, say, webcam.jpg then that keeps it easy, you may be able >> to create a new img tag but using webcam.jpg (rather than daytempdew.png), >> you may need to add a path in front of the file name. If your webcam image >> is timestamped like webcam201901131345.jpg then that gets a little more >> complicated. If you can drop your webcam image into the weeWX directory >> structure under /var/www/html/weewx then you can very easily use weeWX >> to upload your webcam image to your web server if you wish. There are many >> different ways to achieve this, I have outlined one and I am sure other >> will have other ways. At the end of the day it will likely depend on your >> setup. >> >> You have started on the slippery slope of customising your weeWX install, >> the process can appear daunting but do persist and feel free to continue to >> ask if not sure. >> >> Gary >> >> On Sunday, 13 January 2019 11:25:59 UTC+10, monmul wrote: >>> >>> I have managed to get the Standard skin loaded on my weather website >>> www.wilsonbayweather.com...2 small adjustments I would like to >>> make..how do I show the historical max and min for temp, wind, rain >>> etcand how might I include a jpeg photo from webcam showing a picture >>> every hour or so? Thanks in advance.you guys have been fabulous in >>> helping a newbie! >>> >>> -- 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
OK, thanks Garythe xstats.py is already in that directory i.e. /usr/share/weewx/user. On Monday, 14 January 2019 22:40:17 UTC+13, gjr80 wrote: > > Hi, > > The location of the different weeWX components depends on how you > installed weeWX. Have a look at Where to find things ( > http://www.weewx.com/docs/usersguide.htm#Where_to_find_things) in the > User's Guide. The de facto standard has been to refer to the setup.py > location if only one location is given. Your install is a .deb or dpkg so > you should put the xstats files in /usr/share/weewx/user. > > 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: Getting the RPi 3 with Davis Vantage up and running
OK thanks, I am trying to get the total rain over the calendar year..and show the maximum year of the series. On Monday, 14 January 2019 22:55:31 UTC+13, gjr80 wrote: > > Um, no. $rainyear is a special version of $year. $year gives stats from > midnight at the start of 1 January of the current year. $rainyear gives > stats from midnight at the start of the 1st of the month defined by the > rain_year_start config option under [Station] in weewx.conf. I believe > $rainyear was implemented to to cater for folks who keep yearly rainfall > stats over a period other than Jan -Dec. > > Exactly what statistic are you trying to obtain? > > Oh, and xstats.py may well have been there if you previously installed > xstats using wee_extenaion. > > 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: Getting the RPi 3 with Davis Vantage up and running
No, I only want a number for the full calendar year Jan 1 to Dec 31for the data that I havethen I want to find the maximum value in that series. I am not interested in a running total. Sorry, I did not make myself very clear. Very basic, old fashioned, total rain in each calendar year. On Monday, 14 January 2019 23:10:00 UTC+13, gjr80 wrote: > > If you mean say, total rainfall for the 1 year ending today (ie 14 Jan > 2018 to 14 Jan 2019), then $span($year_delta=1).rain.sum will give you what > you are after. Refer to the $span tag ( > http://weewx.com/docs/customizing.htm#_Tag_$span___) in the > Customization Guide. > > 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: Getting the RPi 3 with Davis Vantage up and running
Thank you so much for that.so John's suggestion of $alltime.rain.sum is
not going to work? Is there a tag for the day in the data series which had
the most rain? I am nearly finished and will leave you all in peace soon!
Thank again to all!
On Tuesday, 15 January 2019 00:36:47 UTC+13, gjr80 wrote:
>
> No problems, I think calendar year can be taken either way. In that case
> $year will do just fine. There is no simple tag to give you the may
> yearly rainfall over a number of years, to come up with this requires a
> little code. There are a few ways you could handle this, one of the easiest
> ways is to add a little inline python to to a template the iteration
> capabilities of the weeWX tags
> <http://weewx.com/docs/customizing.htm#Iteration>. In the template you
> wish to display the max annual rainfall add the following code somewhere
> before you want to display the annual rainfall data (near the top of the
> template is often convenient):
>
> #set $max_rain = 0
> #set $max_rain_year = None
> #for $y in $alltime.years
> #set $year_no = $y.start
> #set $year_rain = $y.rain.sum
> #if $year_rain.raw > $max_rain
> #set $max_rain = $year_rain.raw
> #set $max_rain_vh = $year_rain
> #set $max_rain_year = $year_no
> #end if
> #end for
>
> Provided you have the xstats extension installed and provided you have
> added search_list_extensions = user.xstats.ExtendedStatistics to skin.conf
> as per the xstats instructions, you can then use the tag $max_rain_vh to
> display the maximum annual rainfall and the tag $max_rain_year to display
> the year. $max_rain_vh is able to use the weeWX formatting and conversion
> options so $max_rain_vh.mm will display the rainfall in mm using default
> formatting and adding a label eg 1234.5 mm. For example, using the above
> code you could use something like:
>
> #if $max_rain_year is not None
> Maximum annual rainfall was $max_rain_vh.mm in $max_rain_year.format("%Y")
> #else
> No rainfall data available
> #end if
>
> to display something like:
>
> Maximum annual rainfall was 1326.4 mm in 2015
>
>
> The code between the #else and #end if is there to catch the case where
> there may have been no rainfall data.
>
> Hopefully something for you to experiment with.
>
> Gary
>
>
> On Monday, 14 January 2019 20:19:40 UTC+10, monmul wrote:
>>
>> No, I only want a number for the full calendar year Jan 1 to Dec
>> 31for the data that I havethen I want to find the maximum value in
>> that series. I am not interested in a running total. Sorry, I did not make
>> myself very clear. Very basic, old fashioned, total rain in each calendar
>> year.
>>
>> On Monday, 14 January 2019 23:10:00 UTC+13, gjr80 wrote:
>>>
>>> If you mean say, total rainfall for the 1 year ending today (ie 14 Jan
>>> 2018 to 14 Jan 2019), then $span($year_delta=1).rain.sum will give you what
>>> you are after. Refer to the $span tag (
>>> http://weewx.com/docs/customizing.htm#_Tag_$span___) in the
>>> Customization Guide.
>>>
>>> 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: Getting the RPi 3 with Davis Vantage up and running
As ever, thank you for your help and your patience! On Tuesday, 15 January 2019 11:39:26 UTC+13, gjr80 wrote: > > $alltime.rain.sum will certainly work, but I suspect it will not give you > what you seek. Hence the question about what you wanted to display. > $alltime says work out an aggregate over all records in the database, > .rain says work out the aggregate on the rain field and .sum means sum > the records. So $alltime.rain.sum will give you the total rainfall from > all records in your database, which I don't think is what you want. > > If you want to look at wettest days you can make use of the maxsum (the > value) and maxsumtime (when the value occurred) aggregates. So now that you > have $alltime available something like $alltime.rain.maxsum will give you > the highest alltime daily rainfall and $alltime.rain.maxsumtime will give > you when it occurred. Similarly, $year.rain.maxsum and > $year.rain.maxsumtime will give you the same statistics but for the year > to date. These aggregates are possible because weeWX stores (apart from the > archive records in the archive table) summary data for each observation and > this summary data is stored on a per day basis. Hence it is very easy to > get the wettest day, unfortunately weeWX does not record summary data on a > year (or month or week) basis so finding the wettest year, month or week > requires a bit of code. > > Gary > > On Tuesday, 15 January 2019 04:28:41 UTC+10, monmul wrote: >> >> Thank you so much for that.so John's suggestion of $alltime.rain.sum >> is not going to work? Is there a tag for the day in the data series which >> had the most rain? I am nearly finished and will leave you all in peace >> soon! Thank again to all! >> >> On Tuesday, 15 January 2019 00:36:47 UTC+13, gjr80 wrote: >>> >>> No problems, I think calendar year can be taken either way. In that case >>> $year will do just fine. There is no simple tag to give you the may >>> yearly rainfall over a number of years, to come up with this requires a >>> little code. There are a few ways you could handle this, one of the easiest >>> ways is to add a little inline python to to a template the iteration >>> capabilities of the weeWX tags >>> <http://weewx.com/docs/customizing.htm#Iteration>. In the template you >>> wish to display the max annual rainfall add the following code somewhere >>> before you want to display the annual rainfall data (near the top of the >>> template is often convenient): >>> >>> #set $max_rain = 0 >>> #set $max_rain_year = None >>> #for $y in $alltime.years >>> #set $year_no = $y.start >>> #set $year_rain = $y.rain.sum >>> #if $year_rain.raw > $max_rain >>> #set $max_rain = $year_rain.raw >>> #set $max_rain_vh = $year_rain >>> #set $max_rain_year = $year_no >>> #end if >>> #end for >>> >>> Provided you have the xstats extension installed and provided you have >>> added search_list_extensions = user.xstats.ExtendedStatistics to >>> skin.conf as per the xstats instructions, you can then use the tag >>> $max_rain_vh to display the maximum annual rainfall and the tag >>> $max_rain_year to display the year. $max_rain_vh is able to use the >>> weeWX formatting and conversion options so $max_rain_vh.mm will display >>> the rainfall in mm using default formatting and adding a label eg 1234.5 >>> mm. For example, using the above code you could use something like: >>> >>> #if $max_rain_year is not None >>> Maximum annual rainfall was $max_rain_vh.mm in $max_rain_year.format( >>> "%Y") >>> #else >>> No rainfall data available >>> #end if >>> >>> to display something like: >>> >>> Maximum annual rainfall was 1326.4 mm in 2015 >>> >>> >>> The code between the #else and #end if is there to catch the case where >>> there may have been no rainfall data. >>> >>> Hopefully something for you to experiment with. >>> >>> Gary >>> >>> >>> On Monday, 14 January 2019 20:19:40 UTC+10, monmul wrote: >>>> >>>> No, I only want a number for the full calendar year Jan 1 to Dec >>>> 31for the data that I havethen I want to find the maximum value in >>>> that series. I am not interested in a running total. Sorry, I did not make >>>> myself very clear. Very basic, old fashioned, total rain in each calenda
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
So, here is my first attempt at putting all the advice together into the all time template..how am I doing? 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. alltime.html.tmpl Description: Binary data
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Thank you again Gary,...now after I have made these changeshow do I
actually "run" or whatever this template file?
On Tuesday, 15 January 2019 20:03:21 UTC+13, gjr80 wrote:
>
> A few comments.
>
>- the python inline code I provided to calculate max annual rainfall
>needs to have a # at the start of each line
>- not sure you really want the following your template, I just
>included it in my example code to show how you would use the tags:
>
> #if $max_rain_year is not None
> Maximum annual rainfall was $max_rain_vh.mm in $max_rain_year.format("%Y")
> #else
> No rainfall data available
> #end if
>
>- $alltime.rain.maxsumm should be $alltime.rain.maxsum
>- you still have some $year tags in the file relating to UV, ET and
>radiation. though unless you have a UV or radiation sensor on your station
>they will do nothing.
>- you have $alltime.rain.sum in a cell labelled Max Rain Year Total.
>As previously discussed $alltime.rain.sum will give you the sum of all
>rainfall data in your archive, not just for a rain year.
>
> Best way is to try it. You will need to fix the missing # and maxsumm typo
> but otherwise it should work. But how it looks and does it display what you
> want will be another thing completely :)
>
> Gary
>
> On Tuesday, 15 January 2019 14:54:43 UTC+10, monmul wrote:
>>
>> So, here is my first attempt at putting all the advice together into the
>> all time template..how am I doing?
>>
>> 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] Re: Getting the RPi 3 with Davis Vantage up and running
So, here is what happenedthe report got ignored!! i@raspberrypi:~ $ sudo tail -f /var/log/syslog Jan 16 19:17:32 raspberrypi weewx[530]: cheetahgenerator: Generated 1 files for report xstats in 0.09 seconds Jan 16 19:17:32 raspberrypi weewx[530]: ftpgenerator: ftp'd 1 files in 0.62 seconds Jan 16 19:17:34 raspberrypi weewx[530]: reportengine: Failed to read skin configuration file /etc/weewx/skins/Standard/skin.conf for report StandardReport: Duplicate keyword name at line 229. Jan 16 19:17:34 raspberrypi weewx[530]: Report ignored Jan 16 19:17:34 raspberrypi weewx[530]: cheetahgenerator: Generated 1 files for report xstats in 0.07 seconds Jan 16 19:17:34 raspberrypi weewx[530]: engine: Launch of report thread aborted: existing report thread still running Jan 16 19:17:34 raspberrypi weewx[530]: ftpgenerator: ftp'd 1 files in 0.62 seconds Jan 16 19:17:52 raspberrypi kernel: [ 112.313399] Voltage normalised (0x) Jan 16 19:18:08 raspberrypi kernel: [ 128.953478] Under-voltage detected! (0x00050005) Jan 16 19:18:13 raspberrypi kernel: [ 133.113393] Voltage normalised (0x) On Wednesday, 16 January 2019 13:00:18 UTC+13, gjr80 wrote: > > WeeWX generates reports from template files through a skin. Each skin has > a skin config file, skin.conf, which, among other things, tells weeWX > which templates to process. To complete the picture each skin to be > processed by weeWX is listed in weewx.conf under [StdReport]. Now that > you are getting into customizing reports/templates it's probably worth your > while have a read through the The standard reporting service, StdReport > <http://weewx.com/docs/customizing.htm#_The_standard_reporting_service,_StdReport___> > > in the Customization Guide. > > You basically have two choices; create a new skin and add your template to > it or add your template to an existing skin. Since you are adding a new > page with similar look and feel to your existing site it makes sense to do > the latter and just add your template to the existing Standard skin. To > do this: > > 1. edit skins/Standard/skin.conf > 2. locate the [[ToDate]] stanza which is under [CheetahGenerator] > 3. you will see here all the other templates that weeWX is to process. > Just pick a spot and add in your template, I would put it after [[[year]]] > just to keep the pattern but it doesn't really matter. I will not tell you > what to enter, am sure you can work that out :) > 4. save skin.conf > 5. if you have not already done so make sure a copy of your template file > is in the skins/Standard directory > > That's it, weeWX should process your template on the next report cycle. > The proof will be your generated report (page/file) appearing in the same > directory as all the other Standard skin files. You can also monitor your > log for errors, if everything goes fine you will not see much in the log > just one extra file being generated for the Standard skin, if there are > errors you should see them in the log. > > I guess you will; let us know how you go! > > You might also want to have a read through the [CheetahGenerator] section > <http://weewx.com/docs/customizing.htm#[CheetahGenerator]> of the > Customization Guide. > > Gary > > On Wednesday, 16 January 2019 05:57:22 UTC+10, monmul wrote: >> >> Thank you again Gary,...now after I have made these changeshow do I >> actually "run" or whatever this template file? >> >> On Tuesday, 15 January 2019 20:03:21 UTC+13, gjr80 wrote: >>> >>> A few comments. >>> >>>- the python inline code I provided to calculate max annual rainfall >>>needs to have a # at the start of each line >>>- not sure you really want the following your template, I just >>>included it in my example code to show how you would use the tags: >>> >>> #if $max_rain_year is not None >>> Maximum annual rainfall was $max_rain_vh.mm in $max_rain_year.format( >>> "%Y") >>> #else >>> No rainfall data available >>> #end if >>> >>>- $alltime.rain.maxsumm should be $alltime.rain.maxsum >>>- you still have some $year tags in the file relating to UV, ET and >>>radiation. though unless you have a UV or radiation sensor on your >>> station >>>they will do nothing. >>>- you have $alltime.rain.sum in a cell labelled Max Rain Year Total. >>>As previously discussed $alltime.rain.sum will give you the sum of >>>all rainfall data in your archive, not just for a rain year. >>> >>> Best way is to try it. You will need to fix the missing # a
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
line 229..I added [[[alltime]]]?.and mirable dictu it worked! template = week.html.tmpl [[[month]]] template = month.html.tmpl [[[year]]] template = year.html.tmpl template = alltime.html.tmpl [[[RSS]]] template = RSS/weewx_rss.xml.tmpl [[[Mobile]]] template = mobile.html.tmpl On Wednesday, 16 January 2019 19:21:04 UTC+13, monmul wrote: > > So, here is what happenedthe report got ignored!! > > i@raspberrypi:~ $ sudo tail -f /var/log/syslog > Jan 16 19:17:32 raspberrypi weewx[530]: cheetahgenerator: Generated 1 > files for report xstats in 0.09 seconds > Jan 16 19:17:32 raspberrypi weewx[530]: ftpgenerator: ftp'd 1 files in > 0.62 seconds > Jan 16 19:17:34 raspberrypi weewx[530]: reportengine: Failed to read skin > configuration file /etc/weewx/skins/Standard/skin.conf for report > StandardReport: Duplicate keyword name at line 229. > Jan 16 19:17:34 raspberrypi weewx[530]: Report ignored > Jan 16 19:17:34 raspberrypi weewx[530]: cheetahgenerator: Generated 1 > files for report xstats in 0.07 seconds > Jan 16 19:17:34 raspberrypi weewx[530]: engine: Launch of report thread > aborted: existing report thread still running > Jan 16 19:17:34 raspberrypi weewx[530]: ftpgenerator: ftp'd 1 files in > 0.62 seconds > Jan 16 19:17:52 raspberrypi kernel: [ 112.313399] Voltage normalised > (0x) > Jan 16 19:18:08 raspberrypi kernel: [ 128.953478] Under-voltage detected! > (0x00050005) > Jan 16 19:18:13 raspberrypi kernel: [ 133.113393] Voltage normalised > (0x) > > On Wednesday, 16 January 2019 13:00:18 UTC+13, gjr80 wrote: >> >> WeeWX generates reports from template files through a skin. Each skin has >> a skin config file, skin.conf, which, among other things, tells weeWX >> which templates to process. To complete the picture each skin to be >> processed by weeWX is listed in weewx.conf under [StdReport]. Now that >> you are getting into customizing reports/templates it's probably worth your >> while have a read through the The standard reporting service, StdReport >> <http://weewx.com/docs/customizing.htm#_The_standard_reporting_service,_StdReport___> >> >> in the Customization Guide. >> >> You basically have two choices; create a new skin and add your template >> to it or add your template to an existing skin. Since you are adding a new >> page with similar look and feel to your existing site it makes sense to do >> the latter and just add your template to the existing Standard skin. To >> do this: >> >> 1. edit skins/Standard/skin.conf >> 2. locate the [[ToDate]] stanza which is under [CheetahGenerator] >> 3. you will see here all the other templates that weeWX is to process. >> Just pick a spot and add in your template, I would put it after >> [[[year]]] just to keep the pattern but it doesn't really matter. I will >> not tell you what to enter, am sure you can work that out :) >> 4. save skin.conf >> 5. if you have not already done so make sure a copy of your template file >> is in the skins/Standard directory >> >> That's it, weeWX should process your template on the next report cycle. >> The proof will be your generated report (page/file) appearing in the same >> directory as all the other Standard skin files. You can also monitor your >> log for errors, if everything goes fine you will not see much in the log >> just one extra file being generated for the Standard skin, if there are >> errors you should see them in the log. >> >> I guess you will; let us know how you go! >> >> You might also want to have a read through the [CheetahGenerator] section >> <http://weewx.com/docs/customizing.htm#[CheetahGenerator]> of the >> Customization Guide. >> >> Gary >> >> On Wednesday, 16 January 2019 05:57:22 UTC+10, monmul wrote: >>> >>> Thank you again Gary,...now after I have made these changeshow do I >>> actually "run" or whatever this template file? >>> >>> On Tuesday, 15 January 2019 20:03:21 UTC+13, gjr80 wrote: >>>> >>>> A few comments. >>>> >>>>- the python inline code I provided to calculate max annual >>>>rainfall needs to have a # at the start of each line >>>>- not sure you really want the following your template, I just >>>>included it in my example code to show how you would use the tags: >>>> >>>> #if $max_rain_year is not None >>>>
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
I changed it in skin.conf and everything is working fine now (well it will require a minor tweak or two :) )..thank you once again Gary for your patience and commitment...I have only one more part of the project to complete, if you could please guide me on how to import the historical data On Wednesday, 16 January 2019 20:35:42 UTC+13, monmul wrote: > > H.I thought the error was in skin.confbut you think it might > be in weewx.conf. > > On Wed, Jan 16, 2019 at 8:04 PM gjr80 wrote: > >> Jan 16 19:17:34 raspberrypi weewx[530]: reportengine: Failed to read skin >>> configuration file /etc/weewx/skins/Standard/skin.conf for report >>> StandardReport: Duplicate keyword name at line 229. >> >> >> And there is your clue... Have a look at line 229 (or thereabout) in >> weewx.conf, you have a duplicate config option name. Hard to say what it >> is without seeing weewx.conf. Under any given set of [] (or [[]], [[[]]] >> etc) each config option name must be unique, eg you cannot define template >> = twice under [[[year]]]. Similarly each child [[]], [[[]]] etc must be >> named uniquely. Have a look and see what you can find. If you can't find it >> post the offending part of weewx.conf (with any sensitive info removed >> of course). >> >> Gary >> >> >> On Wednesday, 16 January 2019 16:21:04 UTC+10, monmul wrote: >>> >>> So, here is what happenedthe report got ignored!! >>> >>> i@raspberrypi:~ $ sudo tail -f /var/log/syslog >>> Jan 16 19:17:32 raspberrypi weewx[530]: cheetahgenerator: Generated 1 >>> files for report xstats in 0.09 seconds >>> Jan 16 19:17:32 raspberrypi weewx[530]: ftpgenerator: ftp'd 1 files in >>> 0.62 seconds >>> Jan 16 19:17:34 raspberrypi weewx[530]: reportengine: Failed to read >>> skin configuration file /etc/weewx/skins/Standard/skin.conf for report >>> StandardReport: Duplicate keyword name at line 229. >>> Jan 16 19:17:34 raspberrypi weewx[530]: Report ignored >>> Jan 16 19:17:34 raspberrypi weewx[530]: cheetahgenerator: Generated 1 >>> files for report xstats in 0.07 seconds >>> Jan 16 19:17:34 raspberrypi weewx[530]: engine: Launch of report thread >>> aborted: existing report thread still running >>> Jan 16 19:17:34 raspberrypi weewx[530]: ftpgenerator: ftp'd 1 files in >>> 0.62 seconds >>> Jan 16 19:17:52 raspberrypi kernel: [ 112.313399] Voltage normalised >>> (0x) >>> Jan 16 19:18:08 raspberrypi kernel: [ 128.953478] Under-voltage >>> detected! (0x00050005) >>> Jan 16 19:18:13 raspberrypi kernel: [ 133.113393] Voltage normalised >>> (0x) >>> >>> On Wednesday, 16 January 2019 13:00:18 UTC+13, gjr80 wrote: >>>> >>>> WeeWX generates reports from template files through a skin. Each skin >>>> has a skin config file, skin.conf, which, among other things, tells >>>> weeWX which templates to process. To complete the picture each skin to be >>>> processed by weeWX is listed in weewx.conf under [StdReport]. Now that >>>> you are getting into customizing reports/templates it's probably worth >>>> your >>>> while have a read through the The standard reporting service, StdReport >>>> <http://weewx.com/docs/customizing.htm#_The_standard_reporting_service,_StdReport___> >>>> >>>> in the Customization Guide. >>>> >>>> You basically have two choices; create a new skin and add your template >>>> to it or add your template to an existing skin. Since you are adding a new >>>> page with similar look and feel to your existing site it makes sense to do >>>> the latter and just add your template to the existing Standard skin. >>>> To do this: >>>> >>>> 1. edit skins/Standard/skin.conf >>>> 2. locate the [[ToDate]] stanza which is under [CheetahGenerator] >>>> 3. you will see here all the other templates that weeWX is to process. >>>> Just pick a spot and add in your template, I would put it after >>>> [[[year]]] just to keep the pattern but it doesn't really matter. I >>>> will not tell you what to enter, am sure you can work that out :) >>>> 4. save skin.conf >>>> 5. if you have not already done so make sure a copy of your template >>>> file is in the skins/Standard directory >>>> >>>> That's it, weeWX should process your template on the next report cyc
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
AwesomeI thought that weeimport could only deal with csv files and so went and converted them allbut kept the txt files for backup! On Thursday, 17 January 2019 22:35:30 UTC+13, gjr80 wrote: > > Ok, that explains the csv file you provided having a different name > structure to what I had found. I believe that there was/is the ability for > WD to publish csv format log files and that is what I have. Weeimport will > happily work with the MMlg.txt files just as they are. No need to dig > anything out of an old machine. You will be the 1st so it will work with > your logs and I guess we see where it goes from there. Weeimport is fairly > flexible in structure and can easily be adapted. > > 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: Getting the RPi 3 with Davis Vantage up and running
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] Re: Getting the RPi 3 with Davis Vantage up and running
Jan 26 11:07:46 raspberrypi kernel: [ 495.038468] Voltage normalised (0x) Jan 26 11:07:48 raspberrypi kernel: [ 497.118527] Under-voltage detected! (0x00050005) Jan 26 11:08:15 raspberrypi kernel: [ 524.158906] Voltage normalised (0x) Jan 26 11:10:31 raspberrypi ntpd[461]: 202.78.240.38 local addr 10.1.1.7 -> Jan 26 11:10:33 raspberrypi weewx[501]: cheetahgenerator: Generated 15 files for report StandardReport in 11.88 seconds Jan 26 11:10:35 raspberrypi weewx[501]: imagegenerator: Generated 12 images for StandardReport in 1.65 seconds Jan 26 11:10:35 raspberrypi weewx[501]: copygenerator: copied 9 files to /var/www/html/weewx Jan 26 11:10:35 raspberrypi weewx[501]: cheetahgenerator: Generated 1 files for report xstats in 0.17 seconds Jan 26 11:10:42 raspberrypi weewx[501]: ftpgenerator: ftp'd 37 files in 6.99 seconds 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] Re: Getting the RPi 3 with Davis Vantage up and running
Is there a way to see whether the data is getting through from the Vantage to weewx, my Rpi has not undated the skins or WU since last night. I have tested all connectionsthere seems to be ftp happeningbut nothing gets updated!! 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] Re: Getting the RPi 3 with Davis Vantage up and running
Jan 26 11:18:35 raspberrypi kernel: [ 1144.006449] Voltage normalised (0x) Jan 26 11:20:23 raspberrypi weewx[501]: cheetahgenerator: Generated 15 files for report StandardReport in 1.69 seconds Jan 26 11:20:24 raspberrypi weewx[501]: imagegenerator: Generated 12 images for StandardReport in 1.46 seconds Jan 26 11:20:24 raspberrypi weewx[501]: copygenerator: copied 0 files to /var/www/html/weewx Jan 26 11:20:24 raspberrypi weewx[501]: cheetahgenerator: Generated 1 files for report xstats in 0.08 seconds Jan 26 11:20:30 raspberrypi weewx[501]: ftpgenerator: ftp'd 29 files in 5.78 seconds 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] Re: Getting the RPi 3 with Davis Vantage up and running
I seem to be getting a lot of these voltage issuesI am using the Rpi official power pack!! Jan 26 11:15:00 raspberrypi systemd[1]: Starting Cleanup of Temporary Directories... Jan 26 11:15:00 raspberrypi systemd[1]: Started Cleanup of Temporary Directories. Jan 26 11:16:16 raspberrypi kernel: [ 1004.644829] rpi_firmware_get_throttled: 6 callbacks suppressed Jan 26 11:16:16 raspberrypi kernel: [ 1004.644836] Under-voltage detected! (0x00050005) Jan 26 11:16:20 raspberrypi kernel: [ 1008.804876] rpi_firmware_get_throttled: 6 callbacks suppressed Jan 26 11:16:20 raspberrypi kernel: [ 1008.804883] Voltage normalised (0x) Jan 26 11:17:01 raspberrypi CRON[1883]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jan 26 11:17:03 raspberrypi kernel: [ 1052.485382] Under-voltage detected! (0x00050005) Jan 26 11:17:08 raspberrypi kernel: [ 1056.645441] Voltage normalised (0x) Jan 26 11:18:29 raspberrypi kernel: [ 1137.766503] Under-voltage detected! (0x00050005) Jan 26 11:18:35 raspberrypi kernel: [ 1144.006449] Voltage normalised (0x) 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] Re: Getting the RPi 3 with Davis Vantage up and running
pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf LOOP: 2019-01-26 11:35:35 NZDT (1548455735) appTemp: 61.9209615592, barometer: 29.7, cloudbase: 4921.41993274, consBatteryVoltage: 3.02, dateTime: 1548455735, dayET: 0.0, dayRain: 0.031496063, dewpoint: 47.665752296, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, forecastIcon: 3, forecastRule: 163, heatindex: 64.7, humidex: 65.9643612986, inDewpoint: 47.0050615695, inHumidity: 43.0, insideAlarm: 0, inTemp: 70.6, leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: 2.6929133865, outHumidity: 54.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 64.7, rain: None, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.031496063, stormStart: 1548414000, sunrise: 1548432420, sunset: 1548485400, trendIcon: -60, txBatteryStatus: 0, usUnits: 1, windchill: 64.7, windDir: 139.0, windGust: 4.0, windGustDir: 139.0, windSpeed: 4.0, windSpeed10: 2.0, yearET: 0.0, yearRain: 35.4724409537 LOOP: 2019-01-26 11: Well that appears to be working! On Saturday, 26 January 2019 11:24:16 UTC+13, gjr80 wrote: > > You can run WeeWX directly ( > http://weewx.com/docs/usersguide.htm#Running_directly) to see loop and > archive data on screen. The other thing to do is look at the logs over at > least a few archive periods, you will likely see reports being run but no > data being saved to archive. Quite possibly you have corrupt station > memory, especially if you have had a mains power outage, have a read > through this > http://weewx.com/docs/usersguide.htm#html_generated_but_not_updated > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
5,1V 2.5A - the official RPi power unit! On Saturday, 26 January 2019 11:42:00 UTC+13, Dave Webb wrote: > > What size power supply are using? Try at least a 2amp unit. > > Dave-KB1PVH > > > Sent from my Galaxy S9 > > On Fri, Jan 25, 2019, 5:22 PM monmul > wrote: > >> I seem to be getting a lot of these voltage issuesI am using the Rpi >> official power pack!! >> Jan 26 11:15:00 raspberrypi systemd[1]: Starting Cleanup of Temporary >> Directories... >> Jan 26 11:15:00 raspberrypi systemd[1]: Started Cleanup of Temporary >> Directories. >> Jan 26 11:16:16 raspberrypi kernel: [ 1004.644829] >> rpi_firmware_get_throttled: 6 callbacks suppressed >> Jan 26 11:16:16 raspberrypi kernel: [ 1004.644836] Under-voltage >> detected! (0x00050005) >> Jan 26 11:16:20 raspberrypi kernel: [ 1008.804876] >> rpi_firmware_get_throttled: 6 callbacks suppressed >> Jan 26 11:16:20 raspberrypi kernel: [ 1008.804883] Voltage normalised >> (0x) >> Jan 26 11:17:01 raspberrypi CRON[1883]: (root) CMD ( cd / && run-parts >> --report /etc/cron.hourly) >> Jan 26 11:17:03 raspberrypi kernel: [ 1052.485382] Under-voltage >> detected! (0x00050005) >> Jan 26 11:17:08 raspberrypi kernel: [ 1056.645441] Voltage normalised >> (0x) >> Jan 26 11:18:29 raspberrypi kernel: [ 1137.766503] Under-voltage >> detected! (0x00050005) >> Jan 26 11:18:35 raspberrypi kernel: [ 1144.006449] Voltage normalised >> (0x) >> >> >> >> 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+...@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: Getting the RPi 3 with Davis Vantage up and running
After removing batteries from Envoy console and unplugging itand then sudo reboot of Rpi this is what I get. pi@raspberrypi:~ $ sudo tail -f /var/log/syslog Jan 26 12:14:45 raspberrypi dhcpcd[334]: wlan0: no IPv6 Routers available Jan 26 12:14:50 raspberrypi weewx[494]: vantage: Unable to wake up console Jan 26 12:14:50 raspberrypi weewx[494]: import of driver failed: Unable to wake up Vantage console () Jan 26 12:14:50 raspberrypi weewx[494]: engine: Unable to load driver: Unable to wake up Vantage console Jan 26 12:14:50 raspberrypi weewx[494]: Exiting... Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: connected: 10.1.1.155::38928 (TCP) Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: authenticated: 10.1.1.155::38928 (TCP), as (anonymous) (d permissions) Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: SPrintConnMgr: Failed to add printer: server-error-service-unavailable Jan 26 12:14:54 raspberrypi kernel: [ 29.111831] Under-voltage detected! (0x00050005) Jan 26 12:15:01 raspberrypi kernel: [ 35.351863] Voltage normalised (0x) Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 103.242.68.68 Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 103.239.8.22 Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 103.106.65.219 Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 202.78.240.38 Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 103.242.68.69 Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 203.86.206.43 Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 202.46.185.18 Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 202.46.177.18 Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 202.46.179.18 Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 203.99.128.34 Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 2407:f100:0:4::3 Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 203.99.128.48 Jan 26 12:15:43 raspberrypi ntpd[460]: Soliciting pool server 130.217.226.51 Jan 26 12:15:54 raspberrypi systemd[1]: Time has been changed Jan 26 12:15:54 raspberrypi systemd[573]: Time has been changed Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin timestamp 0xdff61722.e1bd49e9 does not match aorg 00. from server@103.239.8.22 xmt 0xdff6172a.80071bf6 Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily.timer: Adding 3h 41min 59.082661s random time. Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin timestamp 0xdff61722.e1af360e does not match aorg 00. from server@202.46.185.18 xmt 0xdff6172a.80d85adc Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 27min 28.579939s random time. Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin timestamp 0xdff61722.d7adc312 does not match aorg 00. from server@130.217.226.51 xmt 0xdff6172a.7d37a242 Jan 26 12:17:01 raspberrypi CRON[1250]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Next should I try deleting future records as recommended in the "generated but not updated" section of the user guide. pi@raspberrypi:~ $ sudo /etc/init.d/weewx stop [ ok ] Stopping weewx (via systemctl): weewx.service. pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf pi@raspberrypi:~ $ sudo tail -f /var/log/syslog Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Initializing weewx version 3.8.2 Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Using Python 2.7.13 (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516] Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Platform Linux-4.14.79-v7+-armv7l-with-debian-9.6 Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Locale is 'en_NZ.UTF-8' Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Using configuration file /etc/weewx/weewx.conf Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Loading station type Vantage (weewx.drivers.vantage) Jan 26 12:25:05 raspberrypi weewx[1810]: vantage: Unable to wake up console Jan 26 12:25:05 raspberrypi weewx[1810]: import of driver failed: Unable to wake up Vantage console () Jan 26 12:25:05 raspberrypi weewx[1810]: engine: Unable to load driver: Unable to wake up Vantage console Jan 26 12:25:05 raspberrypi weewx[1810]: Exiting... Jan 26 On Saturday, 26 January 2019 11:51:41 UTC+13, gjr80 wrote: > > Yes, you appear to be getting loop packets. Corrupt station memory usually > results in loop packets continuing to come through but there are no archive > records coming from the logger. If you are using hardware record generation > then WeeWX gets no archive records, nothing is saved to database but > reports are still generated and anything 'loop based' still goes on. The > proof will be a longer console output (are there any archive records?) or a > longer log extract. > > If corrupt station memo
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Another log after reboot. On Saturday, 26 January 2019 13:08:16 UTC+13, monmul wrote: > > Here is 5 minutes of the console logis that long enough? I can do much > longer if required? > > On Saturday, 26 January 2019 12:26:06 UTC+13, monmul wrote: >> >> After removing batteries from Envoy console and unplugging itand then >> sudo reboot of Rpi this is what I get. >> >> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >> Jan 26 12:14:45 raspberrypi dhcpcd[334]: wlan0: no IPv6 Routers available >> Jan 26 12:14:50 raspberrypi weewx[494]: vantage: Unable to wake up console >> Jan 26 12:14:50 raspberrypi weewx[494]: import of driver failed: Unable >> to wake up Vantage console () >> Jan 26 12:14:50 raspberrypi weewx[494]: engine: Unable to load driver: >> Unable to wake up Vantage console >> Jan 26 12:14:50 raspberrypi weewx[494]: Exiting... >> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: >> connected: 10.1.1.155::38928 (TCP) >> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: >> authenticated: 10.1.1.155::38928 (TCP), as (anonymous) (d permissions) >> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: SPrintConnMgr: >> Failed to add printer: server-error-service-unavailable >> Jan 26 12:14:54 raspberrypi kernel: [ 29.111831] Under-voltage >> detected! (0x00050005) >> Jan 26 12:15:01 raspberrypi kernel: [ 35.351863] Voltage normalised >> (0x) >> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server >> 103.242.68.68 >> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 103.239.8.22 >> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server >> 103.106.65.219 >> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server >> 202.78.240.38 >> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server >> 103.242.68.69 >> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server >> 203.86.206.43 >> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server >> 202.46.185.18 >> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server >> 202.46.177.18 >> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server >> 202.46.179.18 >> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server >> 203.99.128.34 >> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server >> 2407:f100:0:4::3 >> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server >> 203.99.128.48 >> Jan 26 12:15:43 raspberrypi ntpd[460]: Soliciting pool server >> 130.217.226.51 >> Jan 26 12:15:54 raspberrypi systemd[1]: Time has been changed >> Jan 26 12:15:54 raspberrypi systemd[573]: Time has been changed >> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin >> timestamp 0xdff61722.e1bd49e9 does not match aorg 00. from >> server@103.239.8.22 xmt 0xdff6172a.80071bf6 >> Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily.timer: Adding 3h 41min >> 59.082661s random time. >> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin >> timestamp 0xdff61722.e1af360e does not match aorg 00. from >> server@202.46.185.18 xmt 0xdff6172a.80d85adc >> Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding >> 27min 28.579939s random time. >> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin >> timestamp 0xdff61722.d7adc312 does not match aorg 00. from >> server@130.217.226.51 xmt 0xdff6172a.7d37a242 >> Jan 26 12:17:01 raspberrypi CRON[1250]: (root) CMD ( cd / && run-parts >> --report /etc/cron.hourly) >> >> Next should I try deleting future records as recommended in the >> "generated but not updated" section of the user guide. >> >> pi@raspberrypi:~ $ sudo /etc/init.d/weewx stop >> [ ok ] Stopping weewx (via systemctl): weewx.service. >> pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf >> pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf >> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Initializing weewx >> version 3.8.2 >> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Using Python 2.7.13 >> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516] >> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Platform >> Linux-4.14.79-v7+-armv7l-with-debian-9.6 >> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Locale is 'en_NZ.UTF-8' >> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Using configuration file >> /etc/weewx/w
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
OK, we are back up after wee-device --clear-memory. Lost 12 hours of data though.maybe should have tried deleting the records with time stamp older than X. On Saturday, 26 January 2019 13:42:56 UTC+13, monmul wrote: > > Another log after reboot. > > On Saturday, 26 January 2019 13:08:16 UTC+13, monmul wrote: >> >> Here is 5 minutes of the console logis that long enough? I can do >> much longer if required? >> >> On Saturday, 26 January 2019 12:26:06 UTC+13, monmul wrote: >>> >>> After removing batteries from Envoy console and unplugging itand >>> then sudo reboot of Rpi this is what I get. >>> >>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >>> Jan 26 12:14:45 raspberrypi dhcpcd[334]: wlan0: no IPv6 Routers available >>> Jan 26 12:14:50 raspberrypi weewx[494]: vantage: Unable to wake up >>> console >>> Jan 26 12:14:50 raspberrypi weewx[494]: import of driver failed: Unable >>> to wake up Vantage console () >>> Jan 26 12:14:50 raspberrypi weewx[494]: engine: Unable to load driver: >>> Unable to wake up Vantage console >>> Jan 26 12:14:50 raspberrypi weewx[494]: Exiting... >>> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: >>> connected: 10.1.1.155::38928 (TCP) >>> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: >>> authenticated: 10.1.1.155::38928 (TCP), as (anonymous) (d permissions) >>> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: SPrintConnMgr: >>> Failed to add printer: server-error-service-unavailable >>> Jan 26 12:14:54 raspberrypi kernel: [ 29.111831] Under-voltage >>> detected! (0x00050005) >>> Jan 26 12:15:01 raspberrypi kernel: [ 35.351863] Voltage normalised >>> (0x) >>> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server >>> 103.242.68.68 >>> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server >>> 103.239.8.22 >>> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server >>> 103.106.65.219 >>> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server >>> 202.78.240.38 >>> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server >>> 103.242.68.69 >>> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server >>> 203.86.206.43 >>> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server >>> 202.46.185.18 >>> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server >>> 202.46.177.18 >>> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server >>> 202.46.179.18 >>> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server >>> 203.99.128.34 >>> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server >>> 2407:f100:0:4::3 >>> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server >>> 203.99.128.48 >>> Jan 26 12:15:43 raspberrypi ntpd[460]: Soliciting pool server >>> 130.217.226.51 >>> Jan 26 12:15:54 raspberrypi systemd[1]: Time has been changed >>> Jan 26 12:15:54 raspberrypi systemd[573]: Time has been changed >>> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin >>> timestamp 0xdff61722.e1bd49e9 does not match aorg 00. from >>> server@103.239.8.22 xmt 0xdff6172a.80071bf6 >>> Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily.timer: Adding 3h 41min >>> 59.082661s random time. >>> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin >>> timestamp 0xdff61722.e1af360e does not match aorg 00. from >>> server@202.46.185.18 xmt 0xdff6172a.80d85adc >>> Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding >>> 27min 28.579939s random time. >>> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin >>> timestamp 0xdff61722.d7adc312 does not match aorg 00. from >>> server@130.217.226.51 xmt 0xdff6172a.7d37a242 >>> Jan 26 12:17:01 raspberrypi CRON[1250]: (root) CMD ( cd / && run-parts >>> --report /etc/cron.hourly) >>> >>> Next should I try deleting future records as recommended in the >>> "generated but not updated" section of the user guide. >>> >>> pi@raspberrypi:~ $ sudo /etc/init.d/weewx stop >>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>> pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf >>> pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf >>> pi@raspberrypi:~ $ sudo t
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Thank you both for your help.I seem to be up and running now without any hitches apart from some lost data. Thanks again, I will know what to do now if happens again. On Saturday, 26 January 2019 15:04:13 UTC+13, Thomas Keffer wrote: > > The Envoy acts exactly like the regular Vantage console. > > On Fri, Jan 25, 2019 at 5:58 PM gjr80 > > wrote: > >> Ok, so archive records are being saved and pages being generated with >> current data? The log in your previous post still showed an archive record >> being skipped at 13:20:00. >> >> Annoying to lose data but sometimes it happens, doing the dump before you >> do anything destructive dumps all of the archive records out of the logger >> and any that are not in your archive are saved to archive, any that are >> already in your archiv are ignored (well you get a duplicate key error). >> From my limited experience a dump tends to result in loss of maybe one or >> two records only unless something catastrophic has occurred. It seems that >> the archive record is still saved in the logger it just doesn't send it to >> WeeWX when weeWX asks for it. Having an envoy may be slightly different, I >> don't have one, Tom may be able to shed some more light on it. >> >> Not sure what you meant about deleting records. Did you mean your archive >> or the logger/envoy? As far as I know it's all or nothing in terms of >> clearing the logger/envoy. And you weren't getting any records into your >> archive. >> >> 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+...@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
Not a problem, you pointed me in the right direction which was all I needed..thanks again! On Saturday, 26 January 2019 15:09:22 UTC+13, gjr80 wrote: > > My apologies if I lead you astray, I did mentioning dumping but did not > list the command. Was out at the time and on the mobile. > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
My Pi stopped reporting at 19.20 today and despite rebooting twice, it does not seem to be able to wake up the console..is there a way/log I can query to find out why it might have stopped at 19.10it was working fine for 2 or 3 days. Here is the syslog... pi@raspberrypi:~ $ sudo tail -f /var/log/syslog Jan 28 21:43:57 raspberrypi dhcpcd[350]: wlan0: no IPv6 Routers available Jan 28 21:44:02 raspberrypi weewx[510]: vantage: Unable to wake up console Jan 28 21:44:02 raspberrypi weewx[510]: import of driver failed: Unable to wake up Vantage console () Jan 28 21:44:02 raspberrypi weewx[510]: engine: Unable to load driver: Unable to wake up Vantage console Jan 28 21:44:02 raspberrypi weewx[510]: Exiting... Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: connected: 10.1.1.155::40108 (TCP) Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: authenticated: 10.1.1.155::40108 (TCP), as (anonymous) (d permissions) Jan 28 21:44:04 raspberrypi vncserver-x11[461,root]: SPrintConnMgr: Failed to add printer: server-error-service-unavailable Jan 28 21:44:04 raspberrypi kernel: [ 27.031827] Under-voltage detected! (0x00050005) Jan 28 21:44:10 raspberrypi kernel: [ 33.271789] Voltage normalised (0x) Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 88.191.250.97 Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 37.187.18.4 Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 103.106.66.123 Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 103.106.65.219 Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 203.159.70.33 Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 103.242.70.5 Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 203.86.206.43 Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 103.242.70.4 Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 185.242.56.3 Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 103.242.68.69 Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 130.217.226.49 Jan 28 21:44:56 raspberrypi ntpd[484]: Soliciting pool server 122.252.188.99 Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server 202.78.240.38 Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server 202.46.179.18 Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server 2407:f100:0:1::2 Jan 28 21:44:58 raspberrypi ntpd[484]: Soliciting pool server 130.217.226.51 Jan 28 21:45:08 raspberrypi systemd[589]: Time has been changed Jan 28 21:45:08 raspberrypi systemd[1]: Time has been changed Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily.timer: Adding 10h 7min 19.972590s random time. Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 37min 57.400920s random time. Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin timestamp 0xdff93f8c.e12c4d6d does not match aorg 00. from server@203.159.70.33 xmt 0xdff93f94.5a13b23a Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin timestamp 0xdff93f8c.e1319bed does not match aorg 00. from server@37.187.18.4 xmt 0xdff93f94.62dbcbad Jan 28 21:47:56 raspberrypi kernel: [ 251.674064] Under-voltage detected! (0x00050005) Jan 28 21:48:02 raspberrypi kernel: [ 257.914050] Voltage normalised (0x) On Saturday, 26 January 2019 15:12:12 UTC+13, monmul wrote: > > Not a problem, you pointed me in the right direction which was all I > needed..thanks again! > > On Saturday, 26 January 2019 15:09:22 UTC+13, gjr80 wrote: >> >> My apologies if I lead you astray, I did mentioning dumping but did not >> list the command. Was out at the time and on the mobile. >> >> 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
How can I find our (from the logs I presume) what caused the Pi to go down in the first place after running well for 2 or 3 days? On Monday, 28 January 2019 22:23:41 UTC+13, monmul wrote: > > I am using a powered hub and I am using the official RPi power source. > > On Mon, Jan 28, 2019 at 10:05 PM Andrew Milner < > andrew.s.r.mil...@gmail.com> wrote: > >> I would suggest you work on eliminating the under voltage errors before >> trying to work out why you cannot communicate with the weather station. >> The implication is that the RPi is having trouble coping with whatever you >> have got connected via usb and/or network. This is not unusual and >> indicates you may need either a larger power supply or a powered usb hub to >> cope with your usb loads. >> >> >> >> On Monday, 28 January 2019 10:52:28 UTC+2, monmul wrote: >>> >>> My Pi stopped reporting at 19.20 today and despite rebooting twice, it >>> does not seem to be able to wake up the console..is there a way/log I >>> can query to find out why it might have stopped at 19.10it was working >>> fine for 2 or 3 days. Here is the syslog... >>> >>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >>> Jan 28 21:43:57 raspberrypi dhcpcd[350]: wlan0: no IPv6 Routers available >>> Jan 28 21:44:02 raspberrypi weewx[510]: vantage: Unable to wake up >>> console >>> Jan 28 21:44:02 raspberrypi weewx[510]: import of driver failed: Unable >>> to wake up Vantage console () >>> Jan 28 21:44:02 raspberrypi weewx[510]: engine: Unable to load driver: >>> Unable to wake up Vantage console >>> Jan 28 21:44:02 raspberrypi weewx[510]: Exiting... >>> Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: >>> connected: 10.1.1.155::40108 (TCP) >>> Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: >>> authenticated: 10.1.1.155::40108 (TCP), as (anonymous) (d permissions) >>> Jan 28 21:44:04 raspberrypi vncserver-x11[461,root]: SPrintConnMgr: >>> Failed to add printer: server-error-service-unavailable >>> Jan 28 21:44:04 raspberrypi kernel: [ 27.031827] Under-voltage >>> detected! (0x00050005) >>> Jan 28 21:44:10 raspberrypi kernel: [ 33.271789] Voltage normalised >>> (0x) >>> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server >>> 88.191.250.97 >>> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 37.187.18.4 >>> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server >>> 103.106.66.123 >>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server >>> 103.106.65.219 >>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server >>> 203.159.70.33 >>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server >>> 103.242.70.5 >>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server >>> 203.86.206.43 >>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server >>> 103.242.70.4 >>> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server >>> 185.242.56.3 >>> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server >>> 103.242.68.69 >>> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server >>> 130.217.226.49 >>> Jan 28 21:44:56 raspberrypi ntpd[484]: Soliciting pool server >>> 122.252.188.99 >>> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server >>> 202.78.240.38 >>> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server >>> 202.46.179.18 >>> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server >>> 2407:f100:0:1::2 >>> Jan 28 21:44:58 raspberrypi ntpd[484]: Soliciting pool server >>> 130.217.226.51 >>> Jan 28 21:45:08 raspberrypi systemd[589]: Time has been changed >>> Jan 28 21:45:08 raspberrypi systemd[1]: Time has been changed >>> Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily.timer: Adding 10h 7min >>> 19.972590s random time. >>> Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding >>> 37min 57.400920s random time. >>> Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin >>> timestamp 0xdff93f8c.e12c4d6d does not match aorg 00. from >>> ser...@203.159.70.33 xmt 0xdff93f94.5a13b23a >>> Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin >>> timestamp 0xdff93f8c.e1319bed does not match aorg 00. from >>> ser...@37.187.18.4 xmt
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
To be honest, I don't think it is the voltage problemI think it is a time stamp problem, I had to go through the whole --dump and -- clear-memory again to get reporting restarted.less than a week since this last happened! On Monday, 28 January 2019 22:38:07 UTC+13, monmul wrote: > > How can I find our (from the logs I presume) what caused the Pi to go down > in the first place after running well for 2 or 3 days? > > On Monday, 28 January 2019 22:23:41 UTC+13, monmul wrote: >> >> I am using a powered hub and I am using the official RPi power source. >> >> On Mon, Jan 28, 2019 at 10:05 PM Andrew Milner < >> andrew.s.r.mil...@gmail.com> wrote: >> >>> I would suggest you work on eliminating the under voltage errors before >>> trying to work out why you cannot communicate with the weather station. >>> The implication is that the RPi is having trouble coping with whatever you >>> have got connected via usb and/or network. This is not unusual and >>> indicates you may need either a larger power supply or a powered usb hub to >>> cope with your usb loads. >>> >>> >>> >>> On Monday, 28 January 2019 10:52:28 UTC+2, monmul wrote: >>>> >>>> My Pi stopped reporting at 19.20 today and despite rebooting twice, it >>>> does not seem to be able to wake up the console..is there a way/log I >>>> can query to find out why it might have stopped at 19.10it was working >>>> fine for 2 or 3 days. Here is the syslog... >>>> >>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >>>> Jan 28 21:43:57 raspberrypi dhcpcd[350]: wlan0: no IPv6 Routers >>>> available >>>> Jan 28 21:44:02 raspberrypi weewx[510]: vantage: Unable to wake up >>>> console >>>> Jan 28 21:44:02 raspberrypi weewx[510]: import of driver failed: Unable >>>> to wake up Vantage console () >>>> Jan 28 21:44:02 raspberrypi weewx[510]: engine: Unable to load driver: >>>> Unable to wake up Vantage console >>>> Jan 28 21:44:02 raspberrypi weewx[510]: Exiting... >>>> Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: >>>> connected: 10.1.1.155::40108 (TCP) >>>> Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: >>>> authenticated: 10.1.1.155::40108 (TCP), as (anonymous) (d permissions) >>>> Jan 28 21:44:04 raspberrypi vncserver-x11[461,root]: SPrintConnMgr: >>>> Failed to add printer: server-error-service-unavailable >>>> Jan 28 21:44:04 raspberrypi kernel: [ 27.031827] Under-voltage >>>> detected! (0x00050005) >>>> Jan 28 21:44:10 raspberrypi kernel: [ 33.271789] Voltage normalised >>>> (0x) >>>> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server >>>> 88.191.250.97 >>>> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server >>>> 37.187.18.4 >>>> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server >>>> 103.106.66.123 >>>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server >>>> 103.106.65.219 >>>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server >>>> 203.159.70.33 >>>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server >>>> 103.242.70.5 >>>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server >>>> 203.86.206.43 >>>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server >>>> 103.242.70.4 >>>> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server >>>> 185.242.56.3 >>>> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server >>>> 103.242.68.69 >>>> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server >>>> 130.217.226.49 >>>> Jan 28 21:44:56 raspberrypi ntpd[484]: Soliciting pool server >>>> 122.252.188.99 >>>> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server >>>> 202.78.240.38 >>>> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server >>>> 202.46.179.18 >>>> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server >>>> 2407:f100:0:1::2 >>>> Jan 28 21:44:58 raspberrypi ntpd[484]: Soliciting pool server >>>> 130.217.226.51 >>>> Jan 28 21:45:08 raspberrypi systemd[589]: Time has been changed >>>> Jan 28 21:45:08 raspberrypi systemd[1]: Time has been changed >>>> Ja
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Thank you, yesbut where will I find this log that I needas in which folder and what will it be called? On Monday, 28 January 2019 22:57:50 UTC+13, gjr80 wrote: > > Hi, > > Yep the logs are your friend. Usually you are interested in what happened > in the lead up to the event. You mentioned 19:20 but your log extract is > from around 21:44, what do the logs show around 19:20? Try and find the > point where WeeWX exited and work backwards from time there, may 5 or 10 > minutes. The log extract you posted showed an issue at 21:44:02 but there > is only one unrelated entry before that, what else is in the log in the > lead up to 21:44:02? Maybe paste the log from reboot until error. > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Thank youI did not understand that is what I was doing..here from 19.10 last good report to when the next report was expected. Jan 28 19:10:19 raspberrypi weewx[531]: manager: Added record 2019-01-28 19:10:00 NZDT (1548655800) to database 'weewx.sdb' Jan 28 19:10:19 raspberrypi weewx[531]: manager: Added record 2019-01-28 19:10:00 NZDT (1548655800) to daily summary in 'weewx.sdb' Jan 28 19:10:19 raspberrypi weewx[531]: restx: Wunderground-PWS: Published record 2019-01-28 19:10:00 NZDT (1548655800) Jan 28 19:10:20 raspberrypi weewx[531]: cheetahgenerator: Generated 15 files for report StandardReport in 1.65 seconds Jan 28 19:10:21 raspberrypi weewx[531]: imagegenerator: Generated 12 images for StandardReport in 0.88 seconds Jan 28 19:10:21 raspberrypi weewx[531]: copygenerator: copied 0 files to /var/www/html/weewx Jan 28 19:10:21 raspberrypi weewx[531]: cheetahgenerator: Generated 1 files for report xstats in 0.04 seconds Jan 28 19:10:27 raspberrypi weewx[531]: ftpgenerator: ftp'd 28 files in 5.27 seconds Jan 28 19:12:01 raspberrypi kernel: [6.033449] rpi_firmware_get_throttled: 1 callbacks suppressed Jan 28 19:12:01 raspberrypi kernel: [6.033457] Under-voltage detected! (0x00050005) Jan 28 19:12:07 raspberrypi kernel: [77782.273481] rpi_firmware_get_throttled: 1 callbacks suppressed Jan 28 19:12:07 raspberrypi kernel: [77782.273487] Voltage normalised (0x) Jan 28 19:13:08 raspberrypi vncserver-x11[465,root]: Connections: disconnected: 10.1.1.155::33538 (TCP) ([IdleTimeout] This connection has timed out through inactivity.) Jan 28 19:15:53 raspberrypi weewx[531]: vantage: LOOP try #1; error: Expected to read 99 chars; got 0 instead Jan 28 19:16:00 raspberrypi kernel: [78015.235265] Under-voltage detected! (0x00050005) Jan 28 19:16:06 raspberrypi kernel: [78021.475297] Voltage normalised (0x) Jan 28 19:16:09 raspberrypi weewx[531]: vantage: Unable to wake up console Jan 28 19:16:09 raspberrypi weewx[531]: vantage: LOOP try #2; error: Unable to wake up Vantage console Jan 28 19:16:25 raspberrypi weewx[531]: vantage: Unable to wake up console Jan 28 19:16:25 raspberrypi weewx[531]: vantage: LOOP try #3; error: Unable to wake up Vantage console Jan 28 19:16:41 raspberrypi weewx[531]: vantage: Unable to wake up console Jan 28 19:16:41 raspberrypi weewx[531]: vantage: LOOP try #4; error: Unable to wake up Vantage console Jan 28 19:16:41 raspberrypi weewx[531]: vantage: LOOP max tries (4) exceeded. Jan 28 19:16:41 raspberrypi weewx[531]: engine: Shutting down StdReport thread Jan 28 19:16:41 raspberrypi weewx[531]: engine: Caught WeeWxIOError: Max tries exceeded while getting LOOP data. Jan 28 19:16:41 raspberrypi weewx[531]: Waiting 60 seconds then retrying... Jan 28 19:17:01 raspberrypi CRON[10729]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jan 28 19:17:41 raspberrypi weewx[531]: engine: retrying... Jan 28 19:17:41 raspberrypi weewx[531]: engine: Using configuration file /etc/weewx/weewx.conf Jan 28 19:17:41 raspberrypi weewx[531]: engine: Loading station type Vantage (weewx.drivers.vantage) Jan 28 19:17:57 raspberrypi weewx[531]: vantage: Unable to wake up console Jan 28 19:17:57 raspberrypi weewx[531]: import of driver failed: Unable to wake up Vantage console () Jan 28 19:17:57 raspberrypi weewx[531]: engine: Unable to load driver: Unable to wake up Vantage console Jan 28 19:17:57 raspberrypi weewx[531]: Exiting... Jan 28 19:23:12 raspberrypi kernel: [78447.878557] Under-voltage detected! (0x00050005) Jan 28 19:23:19 raspberrypi kernel: [78454.118624] Voltage normalised (0x) Jan 28 19:24:50 raspberrypi kernel: [78545.639346] Under-voltage detected! (0x00050005) Jan 28 19:24:54 raspberrypi kernel: [78549.799434] Voltage normalised (0x) Jan 28 19:40:26 raspberrypi kernel: [79481.646371] Under-voltage detected! (0x00050005) Jan 28 19:40:32 raspberrypi kernel: [79487.886450] Voltage normalised (0x) On Monday, 28 January 2019 23:11:24 UTC+13, gjr80 wrote: > > We you tailed it here: > > > pi@raspberrypi:~ $ sudo tail -f /var/log/syslog > > /var/log/syslog might be a good place to look :) > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
I do have a spare official power supply, so I will swap out that and test. I notice that after doing the -dump (after stopping weewx) and --clear-memory routine and then reboot, that the missing data does not appear in the graphs! The official power units supplies the official USB hub with power and the Pi is powered from this USB hub. The Vantage, which has its own power supply and battery backup) sends the data through the USB hub to the Pi..I have tried connecting it directly to the Pi also...does not seem to make any difference. I have a Pi3B+ on the way, so I can swap out the current SD card and try it in that.Nothing else, apart from a USB (for back up purposes via Deja Dup). I am running the power from a socket strip..so might try plugging the Pi directly into the mains. On Monday, 28 January 2019 23:41:14 UTC+13, gjr80 wrote: > > Hmm, not too much to pinpoint the culprit there. Could it be a power > supply issue, of course, official power supply or not it could still be the > culprit. You could check the output with a meter but will unlikely show any > transient fluctuations that could be causing a problem. Worth doing if you > can though. Swapping out the power supply or RPi itself is probably not > feasible unless you happen to have a spare. > > Could be an issue with the logger, can help by reseating it/making sure it > is inserted securely. Could be power to your console (you have an envoy if > I remember correctly), what is your mains like? Do you have an UPS from > which you can power both RPi and station. > > What is plugged into the RPi, powered hub, keyboard? monitor? Might sound > odd but can you run without the hub and plug the station into the RPi > direct. Are there any long cable runs, obvious one to look at is 5V to the > RPi but if that is the official power supply probably not much to be done > there. > > Sorry these are all a bit woolly but these sorts of issues can be > difficult to nail down. > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
No, Vantage has its own power supply. On Tuesday, 29 January 2019 06:01:14 UTC+13, vince wrote: > > > On Monday, January 28, 2019 at 1:56:14 AM UTC-8, monmul wrote: >> >> To be honest, I don't think it is the voltage problemI think it is a >> time stamp problem, I had to go through the whole --dump and -- >> clear-memory again to get reporting restarted.less than a week since >> this last happened! >> >> >> > Are you perhaps powering your Davis console off the same USB hub ? > -- 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
Apologies, you may well be right...it seems the most obvious culprit now! I don't have an RTC attached to my RPias I was told (much earlier in this thread) that the software changes I made to the resolv.conf files would suffice. On Tuesday, 29 January 2019 00:32:59 UTC+13, Andrew Milner wrote: > > I beg to differ regarding the voltage issue. If your RPi is suffering > from voltage going out of spec as the log implies then this will almost > definitely result in corruption over usb and possibly on the memory card > also. Any corruptions can then result in timestamp issues. Do you also > have a RTC installed on the RPi - this is almost an essential item. The > times on the RPi and the Vantage must remain almost in sync for things to > work seamlessly. If the volyage issue causes a reboot, for example, it is > possible for the rpi to get an erroneous time for a period which could > either get written to the database or prevent satisfactory restart and > catchup from the vantage befpre resuming normal operations. > > I'm sorry but I still think you need to solve the voltage issue first and > ensure that is 100% stable before starting to chase other issues such as > time stamps. I can virtually guarantee the issues you see are most > unlikely to be a result of anything wrong within weewx itself - and > especially with a Davis Vantage for which weewx was originally developed > many moons ago. > > > > > On Monday, 28 January 2019 12:08:56 UTC+2, monmul wrote: >> >> Thank you, yesbut where will I find this log that I needas in >> which folder and what will it be called? >> >> On Monday, 28 January 2019 22:57:50 UTC+13, gjr80 wrote: >>> >>> Hi, >>> >>> Yep the logs are your friend. Usually you are interested in what >>> happened in the lead up to the event. You mentioned 19:20 but your log >>> extract is from around 21:44, what do the logs show around 19:20? Try and >>> find the point where WeeWX exited and work backwards from time there, may 5 >>> or 10 minutes. The log extract you posted showed an issue at 21:44:02 but >>> there is only one unrelated entry before that, what else is in the log in >>> the lead up to 21:44:02? Maybe paste the log from reboot until error. >>> >>> 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
an 29 09:35:16 raspberrypi ntpd[467]: 103.106.65.219 local addr 10.1.1.7 -> Jan 29 09:38:17 raspberrypi kernel: [ 1316.645409] rpi_firmware_get_throttled: 12 callbacks suppressed Jan 29 09:38:17 raspberrypi kernel: [ 1316.645416] Under-voltage detected! (0x00050005) Jan 29 09:38:26 raspberrypi kernel: [ 1324.965452] rpi_firmware_get_throttled: 12 callbacks suppressed Jan 29 09:38:26 raspberrypi kernel: [ 1324.965457] Voltage normalised (0x) Jan 29 09:38:28 raspberrypi kernel: [ 1327.045547] Under-voltage detected! (0x00050005) Jan 29 09:38:32 raspberrypi kernel: [ 1331.205544] Voltage normalised (0x) Jan 29 09:38:36 raspberrypi kernel: [ 1335.365722] Under-voltage detected! (0x00050005) Jan 29 09:38:55 raspberrypi kernel: [ 1354.085857] Voltage normalised (0x) On Tuesday, 29 January 2019 08:51:01 UTC+13, vince wrote: > > On Monday, January 28, 2019 at 11:34:08 AM UTC-8, monmul wrote: >> >> I do have a spare official power supply, so I will swap out that and >> test. ... I have a Pi3B+ on the way >> > > Reminder, the pi3b+ need 'more' power and runs a little hotter than the > others, so definitely be certain you have a quality power supply. > > I have had great luck with > https://www.amazon.com/CanaKit-Raspberry-Power-Supply-Listed/dp/B07BC6WH7V > just as one example. Also like the nice on/off switch dongle that came > with 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
I have now replaced the old Envoy with a new envoy I had lying around. I have dug our the Vantage Pro 2 console from the basement and it is now up and running and displaying data. But this is what I get in my syslog!! Sigh! pi@raspberrypi:~ $ sudo tail -f /var/log/syslog Jan 29 09:44:48 raspberrypi kernel: [ 18.711659] Voltage normalised (0x) Jan 29 09:44:49 raspberrypi dhcpcd[327]: wlan0: no IPv6 Routers available Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: connected: 10.1.1.155::47050 (TCP) Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: authenticated: 10.1.1.155::47050 (TCP), as (anonymous) (d permissions) Jan 29 09:44:51 raspberrypi vncserver-x11[446,root]: SPrintConnMgr: Failed to add printer: server-error-service-unavailable Jan 29 09:44:52 raspberrypi kernel: [ 22.871779] Under-voltage detected! (0x00050005) Jan 29 09:44:54 raspberrypi weewx[495]: vantage: Unable to wake up console Jan 29 09:44:54 raspberrypi weewx[495]: import of driver failed: Unable to wake up Vantage console () Jan 29 09:44:54 raspberrypi weewx[495]: engine: Unable to load driver: Unable to wake up Vantage console Jan 29 09:44:54 raspberrypi weewx[495]: Exiting... Jan 29 09:45:00 raspberrypi kernel: [ 31.191813] Voltage normalised (0x) Jan 29 09:45:44 raspberrypi ntpd[466]: Soliciting pool server 103.106.66.123 Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server 202.46.185.18 Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server 130.217.226.51 Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 203.99.128.34 Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 202.46.177.18 Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 202.46.178.18 Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server 103.106.65.219 Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server 2407:f100:0:4::3 Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server 202.46.179.18 Jan 29 09:51:43 raspberrypi systemd[576]: Time has been changed Jan 29 09:51:43 raspberrypi ntpd[466]: receive: Unexpected origin timestamp 0xdff9e880.d9ce150e does not match aorg 00. from server@103.106.65.219 xmt 0xdff9e9de.fe39c8d9 Jan 29 09:51:43 raspberrypi systemd[1]: Time has been changed Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 37min 9.646374s random time. Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily.timer: Adding 8h 39min 10.183019s random time. On Tuesday, 29 January 2019 09:55:16 UTC+13, vince wrote: > > On Monday, January 28, 2019 at 12:41:15 PM UTC-8, monmul wrote: >> >> I have replaced the power unit, taken it off the power strip an plugged >> both it and the Vanatage into the mains. I have replaced the powered hub >> (official RPi one...with another official RPi one) ...and here is what I am >> getting...very dispirited! I have another Davis Weather Envoy which I >> will soon substitute for the one I am currently using.but nothing seems >> to make a difference and the Envoy just will not wake up! >> >> >> > Still sounds like you have insufficient power to me. > You might try measuring it. > > > https://raspberrypi.stackexchange.com/questions/2136/how-do-i-measure-the-current-power-consumption > > (there are many such devices) > -- 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
pi@raspberrypi:~ $ for id in core sdram_c sdram_i sdram_p ; do \ > echo -e "$id:\t$(vcgencmd measure_volts $id)" ; \ > done bash: : command not found core: volt=1.2000V bash: : command not found bash: : command not found sdram_c: volt=1.2000V bash: : command not found bash: : command not found sdram_i: volt=1.2000V bash: : command not found bash: : command not found sdram_p: volt=1.2250V bash: : command not found On Tuesday, 29 January 2019 10:04:38 UTC+13, monmul wrote: > > I have now replaced the old Envoy with a new envoy I had lying around. I > have dug our the Vantage Pro 2 console from the basement and it is now up > and running and displaying data. But this is what I get in my syslog!! Sigh! > > > pi@raspberrypi:~ $ sudo tail -f /var/log/syslog > Jan 29 09:44:48 raspberrypi kernel: [ 18.711659] Voltage normalised > (0x) > Jan 29 09:44:49 raspberrypi dhcpcd[327]: wlan0: no IPv6 Routers available > Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: > connected: 10.1.1.155::47050 (TCP) > Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: > authenticated: 10.1.1.155::47050 (TCP), as (anonymous) (d permissions) > Jan 29 09:44:51 raspberrypi vncserver-x11[446,root]: SPrintConnMgr: Failed > to add printer: server-error-service-unavailable > Jan 29 09:44:52 raspberrypi kernel: [ 22.871779] Under-voltage detected! > (0x00050005) > Jan 29 09:44:54 raspberrypi weewx[495]: vantage: Unable to wake up console > Jan 29 09:44:54 raspberrypi weewx[495]: import of driver failed: Unable to > wake up Vantage console () > Jan 29 09:44:54 raspberrypi weewx[495]: engine: Unable to load driver: > Unable to wake up Vantage console > Jan 29 09:44:54 raspberrypi weewx[495]: Exiting... > Jan 29 09:45:00 raspberrypi kernel: [ 31.191813] Voltage normalised > (0x) > Jan 29 09:45:44 raspberrypi ntpd[466]: Soliciting pool server > 103.106.66.123 > Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server 202.46.185.18 > Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server > 130.217.226.51 > Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 203.99.128.34 > Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 202.46.177.18 > Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 202.46.178.18 > Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server > 103.106.65.219 > Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server > 2407:f100:0:4::3 > Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server 202.46.179.18 > Jan 29 09:51:43 raspberrypi systemd[576]: Time has been changed > Jan 29 09:51:43 raspberrypi ntpd[466]: receive: Unexpected origin > timestamp 0xdff9e880.d9ce150e does not match aorg 00. from > server@103.106.65.219 xmt 0xdff9e9de.fe39c8d9 > Jan 29 09:51:43 raspberrypi systemd[1]: Time has been changed > Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding > 37min 9.646374s random time. > Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily.timer: Adding 8h 39min > 10.183019s random time. > > On Tuesday, 29 January 2019 09:55:16 UTC+13, vince wrote: >> >> On Monday, January 28, 2019 at 12:41:15 PM UTC-8, monmul wrote: >>> >>> I have replaced the power unit, taken it off the power strip an plugged >>> both it and the Vanatage into the mains. I have replaced the powered hub >>> (official RPi one...with another official RPi one) ...and here is what I am >>> getting...very dispirited! I have another Davis Weather Envoy which I >>> will soon substitute for the one I am currently using.but nothing seems >>> to make a difference and the Envoy just will not wake up! >>> >>> >>> >> Still sounds like you have insufficient power to me. >> You might try measuring it. >> >> >> https://raspberrypi.stackexchange.com/questions/2136/how-do-i-measure-the-current-power-consumption >> >> (there are many such devices) >> > -- 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
Nothing coming through! pi@raspberrypi:~ $ sudo /etc/init.d/weewx stop[ ok ] Stopping weewx (via systemctl): weewx.service. pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf pi@raspberrypi:~ $ lsusb Bus 001 Device 006: ID 13fe:4100 Kingston Technology Company Inc. Flash drive Bus 001 Device 005: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub pi@raspberrypi:~ $ On Tuesday, 29 January 2019 10:11:51 UTC+13, monmul wrote: > > pi@raspberrypi:~ $ for id in core sdram_c sdram_i sdram_p ; do \ > > echo -e "$id:\t$(vcgencmd measure_volts $id)" ; \ > done > bash: : command not found > core: volt=1.2000V > bash: : command not found > bash: : command not found > sdram_c: volt=1.2000V > bash: : command not found > bash: : command not found > sdram_i: volt=1.2000V > bash: : command not found > bash: : command not found > sdram_p: volt=1.2250V > bash: : command not found > > > On Tuesday, 29 January 2019 10:04:38 UTC+13, monmul wrote: >> >> I have now replaced the old Envoy with a new envoy I had lying around. I >> have dug our the Vantage Pro 2 console from the basement and it is now up >> and running and displaying data. But this is what I get in my syslog!! Sigh! >> >> >> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >> Jan 29 09:44:48 raspberrypi kernel: [ 18.711659] Voltage normalised >> (0x) >> Jan 29 09:44:49 raspberrypi dhcpcd[327]: wlan0: no IPv6 Routers available >> Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: >> connected: 10.1.1.155::47050 (TCP) >> Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: >> authenticated: 10.1.1.155::47050 (TCP), as (anonymous) (d permissions) >> Jan 29 09:44:51 raspberrypi vncserver-x11[446,root]: SPrintConnMgr: >> Failed to add printer: server-error-service-unavailable >> Jan 29 09:44:52 raspberrypi kernel: [ 22.871779] Under-voltage >> detected! (0x00050005) >> Jan 29 09:44:54 raspberrypi weewx[495]: vantage: Unable to wake up console >> Jan 29 09:44:54 raspberrypi weewx[495]: import of driver failed: Unable >> to wake up Vantage console () >> Jan 29 09:44:54 raspberrypi weewx[495]: engine: Unable to load driver: >> Unable to wake up Vantage console >> Jan 29 09:44:54 raspberrypi weewx[495]: Exiting... >> Jan 29 09:45:00 raspberrypi kernel: [ 31.191813] Voltage normalised >> (0x) >> Jan 29 09:45:44 raspberrypi ntpd[466]: Soliciting pool server >> 103.106.66.123 >> Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server >> 202.46.185.18 >> Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server >> 130.217.226.51 >> Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server >> 203.99.128.34 >> Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server >> 202.46.177.18 >> Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server >> 202.46.178.18 >> Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server >> 103.106.65.219 >> Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server >> 2407:f100:0:4::3 >> Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server >> 202.46.179.18 >> Jan 29 09:51:43 raspberrypi systemd[576]: Time has been changed >> Jan 29 09:51:43 raspberrypi ntpd[466]: receive: Unexpected origin >> timestamp 0xdff9e880.d9ce150e does not match aorg 00. from >> server@103.106.65.219 xmt 0xdff9e9de.fe39c8d9 >> Jan 29 09:51:43 raspberrypi systemd[1]: Time has been changed >> Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding >> 37min 9.646374s random time. >> Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily.timer: Adding 8h 39min >> 10.183019s random time. >> >> On Tuesday, 29 January 2019 09:55:16 UTC+13, vince wrote: >>> >>> On Monday, January 28, 2019 at 12:41:15 PM UTC-8, monmul wrote: >>>> >>>> I have replaced the power unit, taken it off the power strip an plugged >>>> both it and the Vanatage into the mains. I have replaced the powered hub >>>> (official RPi one...with another official RPi one) ...and here is what I >>>> am >>>> getting...very dispirited! I have another Davis Weather Envoy which I >>>> will soon substitute for the one I am currently
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Sorry, I think you are on the wrong thread! On Tuesday, 29 January 2019 10:20:30 UTC+13, ve2se wrote: > > May i have an url for a web page running weewx v3.9.0 with the new skin > to see what is look like > Jean-Pierre > > Le samedi 5 janvier 2019 20:37:27 UTC-5, monmul a écrit : >> >> 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] Re: Getting the RPi 3 with Davis Vantage up and running
pi@raspberrypi:~ $ wee_device --dumpUsing configuration file
/etc/weewx/weewx.conf
Using Vantage driver version 3.0.11 (weewx.drivers.vantage)
Traceback (most recent call last):
File "/usr/bin/wee_device", line 54, in
main()
File "/usr/bin/wee_device", line 51, in main
device.configure(config_dict)
File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
self.do_options(options, parser, config_dict, prompt)
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1970, in do_options
station = Vantage(**config_dict[DRIVER_NAME])
File "/usr/share/weewx/weewx/drivers/vantage.py", line 487, in __init__
self._setup()
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1278, in _setup
self.port.wakeup_console(max_tries=self.max_tries)
File "/usr/share/weewx/weewx/drivers/vantage.py", line 94, in
wakeup_console
raise weewx.WakeupError("Unable to wake up Vantage console")
weewx.WakeupError: Unable to wake up Vantage console
pi@raspberrypi:~ $
On Tuesday, 29 January 2019 10:25:31 UTC+13, monmul wrote:
>
> Sorry, I think you are on the wrong thread!
>
> On Tuesday, 29 January 2019 10:20:30 UTC+13, ve2se wrote:
>>
>> May i have an url for a web page running weewx v3.9.0 with the new
>> skin to see what is look like
>> Jean-Pierre
>>
>> Le samedi 5 janvier 2019 20:37:27 UTC-5, monmul a écrit :
>>>
>>> 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] Re: Getting the RPi 3 with Davis Vantage up and running
I guess the best thing to do now is to start all over from scratch!!
On Tuesday, 29 January 2019 10:27:59 UTC+13, monmul wrote:
>
> pi@raspberrypi:~ $ wee_device --dumpUsing configuration file
> /etc/weewx/weewx.conf
> Using Vantage driver version 3.0.11 (weewx.drivers.vantage)
> Traceback (most recent call last):
> File "/usr/bin/wee_device", line 54, in
> main()
> File "/usr/bin/wee_device", line 51, in main
> device.configure(config_dict)
> File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
> self.do_options(options, parser, config_dict, prompt)
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1970, in
> do_options
> station = Vantage(**config_dict[DRIVER_NAME])
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 487, in __init__
> self._setup()
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1278, in _setup
> self.port.wakeup_console(max_tries=self.max_tries)
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 94, in
> wakeup_console
> raise weewx.WakeupError("Unable to wake up Vantage console")
> weewx.WakeupError: Unable to wake up Vantage console
> pi@raspberrypi:~ $
>
> On Tuesday, 29 January 2019 10:25:31 UTC+13, monmul wrote:
>>
>> Sorry, I think you are on the wrong thread!
>>
>> On Tuesday, 29 January 2019 10:20:30 UTC+13, ve2se wrote:
>>>
>>> May i have an url for a web page running weewx v3.9.0 with the new
>>> skin to see what is look like
>>> Jean-Pierre
>>>
>>> Le samedi 5 janvier 2019 20:37:27 UTC-5, monmul a écrit :
>>>>
>>>> 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Tried both screen and minicom.no TEST echo backso must be hardwarebut totally flummoxed as all hardware (apart from Rpi) has been replaced.have another pi on orderbut in the meantime I guess I will go back to scratch and start all over againat least it has worked before with this set upmaybe something has become corrupted! On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote: > > Try to communicate directly with the Envoy, without going through WeeWX. > For how to do this, see the section *Establishing connectivity > <http://weewx.com/docs/usersguide.htm#Establishing_connectivity>* in the > User's Guide. If you are unable to do that, then this is definitely a > hardware problem. > > -tk > > On Mon, Jan 28, 2019 at 2:41 PM dunbrokin > > wrote: > >> Thanks, but no I don't I use VNC. >> >> On Tue, Jan 29, 2019 at 11:35 AM > wrote: >> >>> Just a quick question. Do you have a monitor (like the Pi 7 in touch >>> screen) attached that is running off the same power supply as the Pi? I had >>> a setup like that which used a splitter to power both the monitor and Pi >>> from one power pack. My setup kept complaining of undervolting until I >>> removed the splitter and plugged the monitor and pi each into their own >>> power supply. >>> >>> phil >>> >>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote: >>>> >>>> I have replaced the power unit, taken it off the power strip an plugged >>>> both it and the Vanatage into the mains. I have replaced the powered hub >>>> (official RPi one...with another official RPi one) ...and here is what I >>>> am >>>> getting...very dispirited! I have another Davis Weather Envoy which I >>>> will soon substitute for the one I am currently using.but nothing >>>> seems >>>> to make a difference and the Envoy just will not wake up! >>>> >>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >>>> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at >>>> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000 >>>> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr: >>>> Failed to add printer: server-error-service-unavailable >>>> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers >>>> available >>>> Jan 29 09:14:10 raspberrypi kernel: [ 22.871754] Voltage normalised >>>> (0x) >>>> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up >>>> console >>>> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: Unable >>>> to wake up Vantage console () >>>> Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load driver: >>>> Unable to wake up Vantage console >>>> Jan 29 09:14:12 raspberrypi weewx[506]: Exiting... >>>> Jan 29 09:14:27 raspberrypi kernel: [ 39.511958] Under-voltage >>>> detected! (0x00050005) >>>> Jan 29 09:14:31 raspberrypi kernel: [ 43.671921] Voltage normalised >>>> (0x) >>>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server >>>> 103.239.8.22 >>>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server >>>> 202.46.185.18 >>>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server >>>> 203.99.128.48 >>>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server >>>> 103.106.66.123 >>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server >>>> 103.242.68.69 >>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server >>>> 103.106.65.219 >>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server >>>> 103.242.70.5 >>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server >>>> 122.252.188.99 >>>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server >>>> 130.217.226.51 >>>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server >>>> 103.242.68.68 >>>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server >>>> 203.99.128.34 >>>> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server >>>> 202.46.177.18 >>>> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server >>>> 2407:f100:0:4::3 >>>> Jan 29 09:15:06 raspberrypi ntpd[467]:
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Welcome to minicom 2.7 OPTIONS: I18n Compiled on Apr 22 2017, 09:14:19. Port /dev/ttyUSB0, 13:15:39 Press CTRL-A Z for help on special keys Even after lots or s nothing happens on TEST Similarly for screen... On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote: > > The "establishing connectivity" instructions don't mention it, but be sure > to hit a few times before typing TEST. > > On Mon, Jan 28, 2019 at 4:11 PM monmul > > wrote: > >> Tried both screen and minicom.no TEST echo backso must be >> hardwarebut totally flummoxed as all hardware (apart from Rpi) has been >> replaced.have another pi on orderbut in the meantime I guess I will >> go back to scratch and start all over againat least it has worked >> before with this set upmaybe something has become corrupted! >> >> >> On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote: >>> >>> Try to communicate directly with the Envoy, without going through WeeWX. >>> For how to do this, see the section *Establishing connectivity >>> <http://weewx.com/docs/usersguide.htm#Establishing_connectivity>* in >>> the User's Guide. If you are unable to do that, then this is definitely a >>> hardware problem. >>> >>> -tk >>> >>> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin wrote: >>> >>>> Thanks, but no I don't I use VNC. >>>> >>>> On Tue, Jan 29, 2019 at 11:35 AM wrote: >>>> >>>>> Just a quick question. Do you have a monitor (like the Pi 7 in touch >>>>> screen) attached that is running off the same power supply as the Pi? I >>>>> had >>>>> a setup like that which used a splitter to power both the monitor and Pi >>>>> from one power pack. My setup kept complaining of undervolting until I >>>>> removed the splitter and plugged the monitor and pi each into their own >>>>> power supply. >>>>> >>>>> phil >>>>> >>>>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote: >>>>>> >>>>>> I have replaced the power unit, taken it off the power strip an >>>>>> plugged both it and the Vanatage into the mains. I have replaced the >>>>>> powered hub (official RPi one...with another official RPi one) ...and >>>>>> here >>>>>> is what I am getting...very dispirited! I have another Davis Weather >>>>>> Envoy which I will soon substitute for the one I am currently >>>>>> using.but >>>>>> nothing seems to make a difference and the Envoy just will not wake up! >>>>>> >>>>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >>>>>> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at >>>>>> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000 >>>>>> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr: >>>>>> Failed to add printer: server-error-service-unavailable >>>>>> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers >>>>>> available >>>>>> Jan 29 09:14:10 raspberrypi kernel: [ 22.871754] Voltage normalised >>>>>> (0x) >>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up >>>>>> console >>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: >>>>>> Unable to wake up Vantage console () >>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load >>>>>> driver: Unable to wake up Vantage console >>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: Exiting... >>>>>> Jan 29 09:14:27 raspberrypi kernel: [ 39.511958] Under-voltage >>>>>> detected! (0x00050005) >>>>>> Jan 29 09:14:31 raspberrypi kernel: [ 43.671921] Voltage normalised >>>>>> (0x) >>>>>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server >>>>>> 103.239.8.22 >>>>>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server >>>>>> 202.46.185.18 >>>>>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server >>>>>> 203.99.128.48 >>>>>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server >>>>&g
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
This is with debug set to 1 - see attached.does that give us any further information on the situation? On Tuesday, 29 January 2019 13:34:45 UTC+13, Thomas Keffer wrote: > > Then you definitely have a connectivity problem! > > -tk > > On Mon, Jan 28, 2019 at 4:32 PM monmul > > wrote: > >> Welcome to minicom 2.7 >> >> OPTIONS: I18n >> Compiled on Apr 22 2017, 09:14:19. >> Port /dev/ttyUSB0, 13:15:39 >> >> Press CTRL-A Z for help on special keys >> >> Even after lots or s nothing happens on TEST >> >> Similarly for screen... >> >> On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote: >>> >>> The "establishing connectivity" instructions don't mention it, but be >>> sure to hit a few times before typing TEST. >>> >>> On Mon, Jan 28, 2019 at 4:11 PM monmul wrote: >>> >>>> Tried both screen and minicom.no TEST echo backso must be >>>> hardwarebut totally flummoxed as all hardware (apart from Rpi) has >>>> been >>>> replaced.have another pi on orderbut in the meantime I guess I >>>> will >>>> go back to scratch and start all over againat least it has worked >>>> before with this set upmaybe something has become corrupted! >>>> >>>> >>>> On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote: >>>>> >>>>> Try to communicate directly with the Envoy, without going through >>>>> WeeWX. For how to do this, see the section *Establishing connectivity >>>>> <http://weewx.com/docs/usersguide.htm#Establishing_connectivity>* in >>>>> the User's Guide. If you are unable to do that, then this is definitely a >>>>> hardware problem. >>>>> >>>>> -tk >>>>> >>>>> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin wrote: >>>>> >>>>>> Thanks, but no I don't I use VNC. >>>>>> >>>>>> On Tue, Jan 29, 2019 at 11:35 AM wrote: >>>>>> >>>>>>> Just a quick question. Do you have a monitor (like the Pi 7 in touch >>>>>>> screen) attached that is running off the same power supply as the Pi? I >>>>>>> had >>>>>>> a setup like that which used a splitter to power both the monitor and >>>>>>> Pi >>>>>>> from one power pack. My setup kept complaining of undervolting until I >>>>>>> removed the splitter and plugged the monitor and pi each into their own >>>>>>> power supply. >>>>>>> >>>>>>> phil >>>>>>> >>>>>>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote: >>>>>>>> >>>>>>>> I have replaced the power unit, taken it off the power strip an >>>>>>>> plugged both it and the Vanatage into the mains. I have replaced the >>>>>>>> powered hub (official RPi one...with another official RPi one) ...and >>>>>>>> here >>>>>>>> is what I am getting...very dispirited! I have another Davis >>>>>>>> Weather >>>>>>>> Envoy which I will soon substitute for the one I am currently >>>>>>>> using.but >>>>>>>> nothing seems to make a difference and the Envoy just will not wake up! >>>>>>>> >>>>>>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >>>>>>>> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at >>>>>>>> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000 >>>>>>>> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr: >>>>>>>> Failed to add printer: server-error-service-unavailable >>>>>>>> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers >>>>>>>> available >>>>>>>> Jan 29 09:14:10 raspberrypi kernel: [ 22.871754] Voltage >>>>>>>> normalised (0x) >>>>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up >>>>>>>> console >>>>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: >>>>>>&
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
It is working again!.This time I used both official power units...one to power the Pi and one to power the hub. On Tuesday, 29 January 2019 13:34:45 UTC+13, Thomas Keffer wrote: > > Then you definitely have a connectivity problem! > > -tk > > On Mon, Jan 28, 2019 at 4:32 PM monmul > > wrote: > >> Welcome to minicom 2.7 >> >> OPTIONS: I18n >> Compiled on Apr 22 2017, 09:14:19. >> Port /dev/ttyUSB0, 13:15:39 >> >> Press CTRL-A Z for help on special keys >> >> Even after lots or s nothing happens on TEST >> >> Similarly for screen... >> >> On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote: >>> >>> The "establishing connectivity" instructions don't mention it, but be >>> sure to hit a few times before typing TEST. >>> >>> On Mon, Jan 28, 2019 at 4:11 PM monmul wrote: >>> >>>> Tried both screen and minicom.no TEST echo backso must be >>>> hardwarebut totally flummoxed as all hardware (apart from Rpi) has >>>> been >>>> replaced.have another pi on orderbut in the meantime I guess I >>>> will >>>> go back to scratch and start all over againat least it has worked >>>> before with this set upmaybe something has become corrupted! >>>> >>>> >>>> On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote: >>>>> >>>>> Try to communicate directly with the Envoy, without going through >>>>> WeeWX. For how to do this, see the section *Establishing connectivity >>>>> <http://weewx.com/docs/usersguide.htm#Establishing_connectivity>* in >>>>> the User's Guide. If you are unable to do that, then this is definitely a >>>>> hardware problem. >>>>> >>>>> -tk >>>>> >>>>> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin wrote: >>>>> >>>>>> Thanks, but no I don't I use VNC. >>>>>> >>>>>> On Tue, Jan 29, 2019 at 11:35 AM wrote: >>>>>> >>>>>>> Just a quick question. Do you have a monitor (like the Pi 7 in touch >>>>>>> screen) attached that is running off the same power supply as the Pi? I >>>>>>> had >>>>>>> a setup like that which used a splitter to power both the monitor and >>>>>>> Pi >>>>>>> from one power pack. My setup kept complaining of undervolting until I >>>>>>> removed the splitter and plugged the monitor and pi each into their own >>>>>>> power supply. >>>>>>> >>>>>>> phil >>>>>>> >>>>>>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote: >>>>>>>> >>>>>>>> I have replaced the power unit, taken it off the power strip an >>>>>>>> plugged both it and the Vanatage into the mains. I have replaced the >>>>>>>> powered hub (official RPi one...with another official RPi one) ...and >>>>>>>> here >>>>>>>> is what I am getting...very dispirited! I have another Davis >>>>>>>> Weather >>>>>>>> Envoy which I will soon substitute for the one I am currently >>>>>>>> using.but >>>>>>>> nothing seems to make a difference and the Envoy just will not wake up! >>>>>>>> >>>>>>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog >>>>>>>> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at >>>>>>>> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000 >>>>>>>> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr: >>>>>>>> Failed to add printer: server-error-service-unavailable >>>>>>>> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers >>>>>>>> available >>>>>>>> Jan 29 09:14:10 raspberrypi kernel: [ 22.871754] Voltage >>>>>>>> normalised (0x) >>>>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up >>>>>>>> console >>>>>>>> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: >>>>>>&
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Yes it was, apologies to those I doubted! On Tuesday, 29 January 2019 14:29:12 UTC+13, Thomas Keffer wrote: > > Congratulations! Looks like it was a power supply problem. > > USB power supplies fail. I had one that would show +5V under no load, but > it would sag to near nothing with just a modest load. > > On Mon, Jan 28, 2019 at 5:26 PM monmul > > wrote: > >> It is working again!.This time I used both official power units...one >> to power the Pi and one to power the hub. >> >> On Tuesday, 29 January 2019 13:34:45 UTC+13, Thomas Keffer wrote: >>> >>> Then you definitely have a connectivity problem! >>> >>> -tk >>> >>> On Mon, Jan 28, 2019 at 4:32 PM monmul wrote: >>> >>>> Welcome to minicom 2.7 >>>> >>>> OPTIONS: I18n >>>> Compiled on Apr 22 2017, 09:14:19. >>>> Port /dev/ttyUSB0, 13:15:39 >>>> >>>> Press CTRL-A Z for help on special keys >>>> >>>> Even after lots or s nothing happens on TEST >>>> >>>> Similarly for screen... >>>> >>>> On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote: >>>>> >>>>> The "establishing connectivity" instructions don't mention it, but be >>>>> sure to hit a few times before typing TEST. >>>>> >>>>> On Mon, Jan 28, 2019 at 4:11 PM monmul wrote: >>>>> >>>>>> Tried both screen and minicom.no TEST echo backso must be >>>>>> hardwarebut totally flummoxed as all hardware (apart from Rpi) has >>>>>> been >>>>>> replaced.have another pi on orderbut in the meantime I guess I >>>>>> will >>>>>> go back to scratch and start all over againat least it has worked >>>>>> before with this set upmaybe something has become corrupted! >>>>>> >>>>>> >>>>>> On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote: >>>>>>> >>>>>>> Try to communicate directly with the Envoy, without going through >>>>>>> WeeWX. For how to do this, see the section *Establishing >>>>>>> connectivity >>>>>>> <http://weewx.com/docs/usersguide.htm#Establishing_connectivity>* in >>>>>>> the User's Guide. If you are unable to do that, then this is definitely >>>>>>> a >>>>>>> hardware problem. >>>>>>> >>>>>>> -tk >>>>>>> >>>>>>> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin wrote: >>>>>>> >>>>>>>> Thanks, but no I don't I use VNC. >>>>>>>> >>>>>>>> On Tue, Jan 29, 2019 at 11:35 AM wrote: >>>>>>>> >>>>>>>>> Just a quick question. Do you have a monitor (like the Pi 7 in >>>>>>>>> touch screen) attached that is running off the same power supply as >>>>>>>>> the Pi? >>>>>>>>> I had a setup like that which used a splitter to power both the >>>>>>>>> monitor and >>>>>>>>> Pi from one power pack. My setup kept complaining of undervolting >>>>>>>>> until I >>>>>>>>> removed the splitter and plugged the monitor and pi each into their >>>>>>>>> own >>>>>>>>> power supply. >>>>>>>>> >>>>>>>>> phil >>>>>>>>> >>>>>>>>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote: >>>>>>>>>> >>>>>>>>>> I have replaced the power unit, taken it off the power strip an >>>>>>>>>> plugged both it and the Vanatage into the mains. I have replaced the >>>>>>>>>> powered hub (official RPi one...with another official RPi one) >>>>>>>>>> ...and here >>>>>>>>>> is what I am getting...very dispirited! I have another Davis >>>>>>>>>> Weather >>>>>>>>>> Envoy which I will soon substitute for the one I am currently >>>>>>>>>> using.but >>>>>>>>>> not
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
For those following on from me.the two power packs - 1 feeding the Rpi 3 and the other feeding the USB hub has made a tremendous difference.no problems shown in the log, no time problems, no voltage problemsit just flows and operates really well. I wish I had known this from the start it would have saved me so much grief! On Tuesday, 29 January 2019 15:27:46 UTC+13, monmul wrote: > > Yes it was, apologies to those I doubted! > > On Tuesday, 29 January 2019 14:29:12 UTC+13, Thomas Keffer wrote: >> >> Congratulations! Looks like it was a power supply problem. >> >> USB power supplies fail. I had one that would show +5V under no load, but >> it would sag to near nothing with just a modest load. >> >> On Mon, Jan 28, 2019 at 5:26 PM monmul wrote: >> >>> It is working again!.This time I used both official power >>> units...one to power the Pi and one to power the hub. >>> >>> On Tuesday, 29 January 2019 13:34:45 UTC+13, Thomas Keffer wrote: >>>> >>>> Then you definitely have a connectivity problem! >>>> >>>> -tk >>>> >>>> On Mon, Jan 28, 2019 at 4:32 PM monmul wrote: >>>> >>>>> Welcome to minicom 2.7 >>>>> >>>>> OPTIONS: I18n >>>>> Compiled on Apr 22 2017, 09:14:19. >>>>> Port /dev/ttyUSB0, 13:15:39 >>>>> >>>>> Press CTRL-A Z for help on special keys >>>>> >>>>> Even after lots or s nothing happens on TEST >>>>> >>>>> Similarly for screen... >>>>> >>>>> On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote: >>>>>> >>>>>> The "establishing connectivity" instructions don't mention it, but be >>>>>> sure to hit a few times before typing TEST. >>>>>> >>>>>> On Mon, Jan 28, 2019 at 4:11 PM monmul wrote: >>>>>> >>>>>>> Tried both screen and minicom.no TEST echo backso must be >>>>>>> hardwarebut totally flummoxed as all hardware (apart from Rpi) has >>>>>>> been >>>>>>> replaced.have another pi on orderbut in the meantime I guess I >>>>>>> will >>>>>>> go back to scratch and start all over againat least it has worked >>>>>>> before with this set upmaybe something has become corrupted! >>>>>>> >>>>>>> >>>>>>> On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote: >>>>>>>> >>>>>>>> Try to communicate directly with the Envoy, without going through >>>>>>>> WeeWX. For how to do this, see the section *Establishing >>>>>>>> connectivity >>>>>>>> <http://weewx.com/docs/usersguide.htm#Establishing_connectivity>* in >>>>>>>> the User's Guide. If you are unable to do that, then this is >>>>>>>> definitely a >>>>>>>> hardware problem. >>>>>>>> >>>>>>>> -tk >>>>>>>> >>>>>>>> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Thanks, but no I don't I use VNC. >>>>>>>>> >>>>>>>>> On Tue, Jan 29, 2019 at 11:35 AM wrote: >>>>>>>>> >>>>>>>>>> Just a quick question. Do you have a monitor (like the Pi 7 in >>>>>>>>>> touch screen) attached that is running off the same power supply as >>>>>>>>>> the Pi? >>>>>>>>>> I had a setup like that which used a splitter to power both the >>>>>>>>>> monitor and >>>>>>>>>> Pi from one power pack. My setup kept complaining of undervolting >>>>>>>>>> until I >>>>>>>>>> removed the splitter and plugged the monitor and pi each into their >>>>>>>>>> own >>>>>>>>>> power supply. >>>>>>>>>> >>>>>>>>>> phil >>>>>>>>>> >>>>>>>>>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote: >>>>>
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Is there anyway I can help in getting the WeatherDisplay csv data into the weewx database..I have been away for a while so might have missed any updates on this project. On Thursday, 17 January 2019 22:40:45 UTC+13, monmul wrote: > > AwesomeI thought that weeimport could only deal with csv files and so > went and converted them allbut kept the txt files for backup! > > On Thursday, 17 January 2019 22:35:30 UTC+13, gjr80 wrote: >> >> Ok, that explains the csv file you provided having a different name >> structure to what I had found. I believe that there was/is the ability for >> WD to publish csv format log files and that is what I have. Weeimport will >> happily work with the MMlg.txt files just as they are. No need to dig >> anything out of an old machine. You will be the 1st so it will work with >> your logs and I guess we see where it goes from there. Weeimport is fairly >> flexible in structure and can easily be adapted. >> >> 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: Getting the RPi 3 with Davis Vantage up and running
So this is the FTP section of my weewx.conf..I have not changed anything. It used to transfer across no problem until the camera needed replacingand the photo from the new camera appears on the internal website but not transferred across...weird! [[FTP]] # FTP'ing the results to a webserver is treated as just another report, # albeit one with an unusual report generator! skin = Ftp # If you wish to use FTP, uncomment and fill out the next four lines. # Use quotes around passwords to guard against parsing errors. user = abcdefgh password = 123456789 server = 43.245.53.39 path = /public_html # Set to True for an FTP over TLS (FTPS) connection. Not all servers # support this. secure_ftp = False # To upload files from something other than what HTML_ROOT is set # to above, specify a different HTML_ROOT here. #HTML_ROOT = /var/www/html/weewx # Most FTP servers use port 21 port = 21 # Set to 1 to use passive mode, zero for active mode passive = 1 On Monday, 4 March 2019 23:30:53 UTC+13, Andrew Milner wrote: > > you did not give us a directory listing from the external website - but > assuming the file has not been transferred there maybe you need to include > image.jpeg in the copy always list in weewx.conf > > > > On Monday, 4 March 2019 11:20:16 UTC+2, monmul wrote: >> >> I have run into a problem with posting a photo on my website. The photo >> shows on file:///var/www/html/weewx/index.html but not on >> www.wilsonbayweather.com - this shows an old photo that never changes! >> Attached are screenshots that may help. Why is it updating on one and not >> the other? >> >> On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote: >>> >>> Hi, >>> >>> There are a few steps involved in achieving what you want to do. First >>> the historical max/min - by this I presume you mean all time statistics - >>> those that cover all of your weeWX data and not just the last day, month or >>> year. >>> >>> If I have this right you need to extend weeWX so that you can access >>> stats from all of your data, this is most easily achieved by installing the >>> xstats example extension. You will find the xstats files are in the >>> /usr/share/doc/weewx/examples directory. I would install manually and >>> just follow step 1 in the readme.txt remembering later that you will >>> need to enable the alltime stats for your templates/reports by following >>> step 2. You can install xstats using wee_extension but that will also >>> install the example web page which you probably do not want. >>> >>> Now that you have xstats installed you can use tags like >>> $alltime.outTemp.max in report templates to display the maximum outside >>> temperature. The time it occurred will be $alltime.outTemp.maxtime. >>> Just like $day, $month and $year tags but you use $alltime. If you are >>> not familiar with weeWX tags it is worth reading the Tags section >>> <http://weewx.com/docs/customizing.htm#Tags> of the Customization Guide. >>> >>> To use the $alltime tags you will probably want to create a new page or >>> modify an existing one. It is really up to you want you want to do. To >>> modify an existing page have a look at the .tmpl files in you Standard >>> skin directory /etc/weewx/skins/Standard. These are the files weeWX >>> uses to generate a corresponding .html page. You will see how tags are used >>> in a template, in a nutshell where you place a tag weeWX will replace that >>> with the relevant data when the reports are generated. The process is a >>> little more involved if you want to create a new page as not only do you >>> need to modify/create a page but you also need to modify skin.conf to >>> have weeWX generate the new page. You may also need to modify other pages >>> to include a link to your new page. A good starting point may be to take a >>> copy of /etc/weewx/skins/Standard/year.html.tmpl, save it as >>> alltime.html.tmpl and start modifying. Have a good poke around the >>> templates and skin.conf (and [StdReport] in weewx.conf) to see how it >>> comes together. >>> >>> Including an image in a weeWX generated page can be relatively >>> straightforward. If you have a look in index.html.tmpl you will see >>> lines such as: >>> >>> >>> >>> This line creates a HTML img tag that displays the daily temperature and >>>
[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
I am thinking...maybe I accidentally updated to the latest version and that has broken something? How do I check what version I am running? On Tuesday, 5 March 2019 08:40:38 UTC+13, monmul wrote: > > So this is the FTP section of my weewx.conf..I have not changed > anything. It used to transfer across no problem until the camera needed > replacingand the photo from the new camera appears on the internal > website but not transferred across...weird! > > [[FTP]] > # FTP'ing the results to a webserver is treated as just another > report, > # albeit one with an unusual report generator! > skin = Ftp > > # If you wish to use FTP, uncomment and fill out the next four > lines. > # Use quotes around passwords to guard against parsing errors. > user = abcdefgh > password = 123456789 > server = 43.245.53.39 > path = /public_html > > # Set to True for an FTP over TLS (FTPS) connection. Not all > servers > # support this. > secure_ftp = False > > # To upload files from something other than what HTML_ROOT is set > # to above, specify a different HTML_ROOT here. > #HTML_ROOT = /var/www/html/weewx > > # Most FTP servers use port 21 > port = 21 > > # Set to 1 to use passive mode, zero for active mode > passive = 1 > > > On Monday, 4 March 2019 23:30:53 UTC+13, Andrew Milner wrote: >> >> you did not give us a directory listing from the external website - but >> assuming the file has not been transferred there maybe you need to include >> image.jpeg in the copy always list in weewx.conf >> >> >> >> On Monday, 4 March 2019 11:20:16 UTC+2, monmul wrote: >>> >>> I have run into a problem with posting a photo on my website. The photo >>> shows on file:///var/www/html/weewx/index.html but not on >>> www.wilsonbayweather.com - this shows an old photo that never changes! >>> Attached are screenshots that may help. Why is it updating on one and not >>> the other? >>> >>> On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote: >>>> >>>> Hi, >>>> >>>> There are a few steps involved in achieving what you want to do. First >>>> the historical max/min - by this I presume you mean all time statistics - >>>> those that cover all of your weeWX data and not just the last day, month >>>> or >>>> year. >>>> >>>> If I have this right you need to extend weeWX so that you can access >>>> stats from all of your data, this is most easily achieved by installing >>>> the >>>> xstats example extension. You will find the xstats files are in the >>>> /usr/share/doc/weewx/examples directory. I would install manually and >>>> just follow step 1 in the readme.txt remembering later that you will >>>> need to enable the alltime stats for your templates/reports by following >>>> step 2. You can install xstats using wee_extension but that will also >>>> install the example web page which you probably do not want. >>>> >>>> Now that you have xstats installed you can use tags like >>>> $alltime.outTemp.max in report templates to display the maximum >>>> outside temperature. The time it occurred will be >>>> $alltime.outTemp.maxtime. Just like $day, $month and $year tags but >>>> you use $alltime. If you are not familiar with weeWX tags it is worth >>>> reading the Tags section <http://weewx.com/docs/customizing.htm#Tags> >>>> of the Customization Guide. >>>> >>>> To use the $alltime tags you will probably want to create a new page >>>> or modify an existing one. It is really up to you want you want to do. To >>>> modify an existing page have a look at the .tmpl files in you Standard >>>> skin directory /etc/weewx/skins/Standard. These are the files weeWX >>>> uses to generate a corresponding .html page. You will see how tags are >>>> used >>>> in a template, in a nutshell where you place a tag weeWX will replace that >>>> with the relevant data when the reports are generated. The process is a >>>> little more involved if you want to create a new page as not only do you >>>> need to modify/create a page but you also need to modify skin.conf to >>>> have weeWX generate the new page. You may also need to modify other pages >>>> to include a link to your new pag
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
OK, so I seem to be on 3.9.1what has changed that would make the FTP keep working from the previous version but not carry the jpeg across? On Tuesday, 5 March 2019 10:19:24 UTC+13, Tom wrote: > > To determine the weewx version try: > > wee_config --version > > > -- > Tom > > > On Mon, Mar 4, 2019 at 1:54 PM monmul > > wrote: > >> I am thinking...maybe I accidentally updated to the latest version and >> that has broken something? How do I check what version I am running? >> >> On Tuesday, 5 March 2019 08:40:38 UTC+13, monmul wrote: >>> >>> So this is the FTP section of my weewx.conf..I have not changed >>> anything. It used to transfer across no problem until the camera needed >>> replacingand the photo from the new camera appears on the internal >>> website but not transferred across...weird! >>> >>> [[FTP]] >>> # FTP'ing the results to a webserver is treated as just another >>> report, >>> # albeit one with an unusual report generator! >>> skin = Ftp >>> >>> # If you wish to use FTP, uncomment and fill out the next four >>> lines. >>> # Use quotes around passwords to guard against parsing errors. >>> user = abcdefgh >>> password = 123456789 >>> server = 43.245.53.39 >>> path = /public_html >>> >>> # Set to True for an FTP over TLS (FTPS) connection. Not all >>> servers >>> # support this. >>> secure_ftp = False >>> >>> # To upload files from something other than what HTML_ROOT is set >>> # to above, specify a different HTML_ROOT here. >>> #HTML_ROOT = /var/www/html/weewx >>> >>> # Most FTP servers use port 21 >>> port = 21 >>> >>> # Set to 1 to use passive mode, zero for active mode >>> passive = 1 >>> >>> >>> On Monday, 4 March 2019 23:30:53 UTC+13, Andrew Milner wrote: >>>> >>>> you did not give us a directory listing from the external website - but >>>> assuming the file has not been transferred there maybe you need to include >>>> image.jpeg in the copy always list in weewx.conf >>>> >>>> >>>> >>>> On Monday, 4 March 2019 11:20:16 UTC+2, monmul wrote: >>>>> >>>>> I have run into a problem with posting a photo on my website. The >>>>> photo shows on file:///var/www/html/weewx/index.html but not on >>>>> www.wilsonbayweather.com - this shows an old photo that never >>>>> changes! Attached are screenshots that may help. Why is it updating on >>>>> one >>>>> and not the other? >>>>> >>>>> On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> There are a few steps involved in achieving what you want to do. >>>>>> First the historical max/min - by this I presume you mean all time >>>>>> statistics - those that cover all of your weeWX data and not just the >>>>>> last >>>>>> day, month or year. >>>>>> >>>>>> If I have this right you need to extend weeWX so that you can access >>>>>> stats from all of your data, this is most easily achieved by installing >>>>>> the >>>>>> xstats example extension. You will find the xstats files are in the >>>>>> /usr/share/doc/weewx/examples directory. I would install manually >>>>>> and just follow step 1 in the readme.txt remembering later that you >>>>>> will need to enable the alltime stats for your templates/reports by >>>>>> following step 2. You can install xstats using wee_extension but >>>>>> that will also install the example web page which you probably do not >>>>>> want. >>>>>> >>>>>> Now that you have xstats installed you can use tags like >>>>>> $alltime.outTemp.max in report templates to display the maximum >>>>>> outside temperature. The time it occurred will be >>>>>> $alltime.outTemp.maxtime. Just like $day, $month and $year tags but >>>>>> you use $alltime. If you are not familiar with weeWX tags it is worth >>>>>> re
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
It gets there via a cron hourly script #!/bin/sh # # Simple cron script sudo rm /var/www/html/weewx/image1.jpg #rm /var/www/html/weewx/640x480 sudo raspistill -w 640 -h 480 -o /var/www/html/weewx/image.jpg sudo mv /var/www/html/weewx/image.jpg /var/www/html/weewx/image1.jpg On Tuesday, 5 March 2019 18:41:47 UTC+13, gjr80 wrote: > > One thing 3.9.0 changed was the log_success and log_failure settings in > weewx.conf. Just to make sure nothing is being hidden from you edit > weewx.conf and under [StdReport] set log_failure = True. Also set debug = > 1, I don't think debug is going to tell us much more but let's give it a > go. Save weewx.conf. In the /vat/www/html/weewx directory find and delete > the file #FTPlast. Restart WeeWX. > > See what happens, if no change post the log from startup showing the > entire startup and at least a couple of complete report cycles. > > I don't see copy_always helping, that applies to the CopyGenerator only > and since the file concerned is already in /var/www/html/weewx we don't > need to copy it there. Just out of interest, can you give us an outline of > how image1.jpg arrives in /var/www/html/weewx ? > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Log file attached...at least one ftp cycleno difference on website...old photo still shows. On Tuesday, 5 March 2019 18:41:47 UTC+13, gjr80 wrote: > > One thing 3.9.0 changed was the log_success and log_failure settings in > weewx.conf. Just to make sure nothing is being hidden from you edit > weewx.conf and under [StdReport] set log_failure = True. Also set debug = > 1, I don't think debug is going to tell us much more but let's give it a > go. Save weewx.conf. In the /vat/www/html/weewx directory find and delete > the file #FTPlast. Restart WeeWX. > > See what happens, if no change post the log from startup showing the > entire startup and at least a couple of complete report cycles. > > I don't see copy_always helping, that applies to the CopyGenerator only > and since the file concerned is already in /var/www/html/weewx we don't > need to copy it there. Just out of interest, can you give us an outline of > how image1.jpg arrives in /var/www/html/weewx ? > > 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. Mar 5 21:26:42 WeatherPi weewx[19404]: manager: Daily summary version is 2.0 Mar 5 21:26:42 WeatherPi weewx[19404]: vantage: Gentle wake up of console successful Mar 5 21:26:42 WeatherPi weewx[19404]: engine: Clock error is 1.30 seconds (positive is fast) Mar 5 21:26:42 WeatherPi weewx[19404]: vantage: Getting archive packets since 2019-03-05 21:20:00 NZDT (1551774000) Mar 5 21:26:42 WeatherPi weewx[19404]: vantage: Gentle wake up of console successful Mar 5 21:26:42 WeatherPi weewx[19404]: vantage: Retrieving 0 page(s); starting index= 0 Mar 5 21:26:42 WeatherPi weewx[19404]: engine: Starting main packet loop. Mar 5 21:26:42 WeatherPi weewx[19404]: vantage: Gentle wake up of console successful Mar 5 21:26:42 WeatherPi weewx[19404]: vantage: Requesting 200 LOOP packets. Mar 5 21:26:42 WeatherPi weewx[19404]: vantage: Gentle wake up of console successful Mar 5 21:30:15 WeatherPi weewx[19404]: vantage: Getting archive packets since 2019-03-05 21:20:00 NZDT (1551774000) Mar 5 21:30:18 WeatherPi weewx[19404]: vantage: Retry #0 failed Mar 5 21:30:18 WeatherPi weewx[19404]: vantage: Rude wake up of console successful Mar 5 21:30:18 WeatherPi weewx[19404]: vantage: Retrieving 1 page(s); starting index= 4 Mar 5 21:30:19 WeatherPi weewx[19404]: manager: Added record 2019-03-05 21:30:00 NZDT (1551774600) to database 'weewx.sdb' Mar 5 21:30:19 WeatherPi weewx[19404]: manager: Added record 2019-03-05 21:30:00 NZDT (1551774600) to daily summary in 'weewx.sdb' Mar 5 21:30:19 WeatherPi weewx[19404]: reportengine: Running reports for latest time in the database. Mar 5 21:30:19 WeatherPi weewx[19404]: vantage: Requesting 200 LOOP packets. Mar 5 21:30:19 WeatherPi weewx[19404]: reportengine: Running report 'StandardReport' Mar 5 21:30:19 WeatherPi weewx[19404]: vantage: Gentle wake up of console successful Mar 5 21:30:19 WeatherPi weewx[19404]: reportengine: Found configuration file /etc/weewx/skins/Standard/skin.conf for report 'StandardReport' Mar 5 21:30:19 WeatherPi weewx[19404]: cheetahgenerator: using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 'user.xstats.ExtendedStatistics'] Mar 5 21:30:19 WeatherPi weewx[19404]: manager: Daily summary version is 2.0 Mar 5 21:30:20 WeatherPi weewx[19404]: restx: Wunderground-PWS: Published record 2019-03-05 21:30:00 NZDT (1551774600) Mar 5 21:30:24 WeatherPi weewx[19404]: cheetahgenerator: Generated 15 files for report StandardReport in 5.16 seconds Mar 5 21:30:24 WeatherPi weewx[19404]: manager: Daily summary version is 2.0 Mar 5 21:30:25 WeatherPi weewx[19404]: imagegenerator: Generated 12 images for StandardReport in 1.04 seconds Mar 5 21:30:25 WeatherPi weewx[19404]: copygenerator: copied 14 files to /var/www/html/weewx Mar 5 21:30:25 WeatherPi weewx[19404]: reportengine: Running report 'xstats' Mar 5 21:30:25 WeatherPi weewx[19404]: reportengine: Found configuration file /etc/weewx/skins/xstats/skin.conf for report 'xstats' Mar 5 21:30:25 WeatherPi weewx[19404]: cheetahgenerator: using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 'user.xstats.ExtendedStatistics'] Mar 5 21:30:25 WeatherPi weewx[19404]: manager: Daily summary version is 2.0 Mar 5 21:30:26 WeatherPi weewx[19404]: cheetahgenerator: Generated 1 files for report xstats in 0.14 seconds Mar 5 21:30:26 WeatherPi weewx[19404]: reportengine: Report 'SeasonsRep
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
weewx.conf attached - passwords etc changed. On Tuesday, 5 March 2019 22:07:12 UTC+13, gjr80 wrote: > > Sorry I am a bit slow in this but I don't use ftp myself. I see files are > being uploaded from /public_html, just wondering if perhaps something is in > the wrong place. Can you post a copy of weewx.conf being careful to take > out any sensitive info, user names, passwords etc. > > 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 CONFIGURATION FILE # # Copyright (c) 2009-2015 Tom Keffer # See the file LICENSE.txt for your rights. ## # This section is for general configuration information. # Set to 1 for extra debug info, otherwise comment it out or set to zero debug = 1 # Root directory of the weewx data file hierarchy for this station WEEWX_ROOT = / # Whether to log successful operations log_success = True # Whether to log unsuccessful operations log_failure = True # How long to wait before timing out a socket (FTP, HTTP) connection socket_timeout = 20 # Do not modify this. It is used when installing and updating weewx. version = 3.9.1 ## # This section is for information about the station. [Station] # Description of the station location location = "Wilson Bay, Queenstown, NZ" # Latitude and longitude in decimal degrees latitude = -45.0595 longitude = 168.567 # Altitude of the station, with unit it is in. This is downloaded from # from the station if the hardware supports it. altitude = 320, meter # Set to type of station hardware. There must be a corresponding stanza # in this file with a 'driver' parameter indicating the driver to be used. station_type = Vantage # If you have a website, you may specify an URL #station_url = http://www.example.com # The start of the rain year (1=January; 10=October, etc.). This is # downloaded from the station if the hardware supports it. rain_year_start = 1 # Start of week (0=Monday, 6=Sunday) week_start = 6 ## [Vantage] # This section is for the Davis Vantage series of weather stations. # Connection type: serial or ethernet # serial (the classic VantagePro) # ethernet (the WeatherLinkIP or Serial-Ethernet bridge) type = serial # If the connection type is serial, a port must be specified: # Debian, Ubuntu, Redhat, Fedora, and SuSE: # /dev/ttyUSB0 is a common USB port name # /dev/ttyS0 is a common serial port name # BSD: # /dev/cuaU0 is a common serial port name port = /dev/ttyUSB0 # If the connection type is ethernet, an IP Address/hostname is required: host = 1.2.3.4 ## # The rest of this section rarely needs any attention. # You can safely leave it "as is." ## # Serial baud rate (usually 19200) baudrate = 19200 # TCP port (when using the WeatherLinkIP) tcp_port = 2 # TCP send delay (when using the WeatherLinkIP): tcp_send_delay = 0.5 # The id of your ISS station (usually 1). If you use a wind meter connected # to a anemometer transmitter kit, use its id iss_id = 1 # How long to wait for a response from the station before giving up (in # seconds; must be greater than 2) timeout = 4 # How long to wait before trying again (in seconds) wait_before_retry = 1.2 # How many times to try before giving up: max_tries = 4 # Vantage model Type: 1 = Vantage Pro; 2 = Vantage Pro2 model_type = 2 # The driver to use: driver = weewx.drivers.vantage ## # This section is for uploading data to Internet sites [StdRESTful] [[StationRegistry]] # To register this weather station with weewx, set this to true register_this_station = false [[AWEKAS]] # This section is for configuring posts to AWEKAS. # If you wish to do this, set the option 'enable' to true, # and specify a username and password. # To guard against parsing errors, put the password in quotes. enable = false username = replace_me password = replace_me [[CWOP]] # This section is for configuring posts to CWOP. # If you wish to do this, set the option 'enable' to true, # and
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
By "delete image1.jpg from your web server" do you mean from the www.wilsonbayweather.com web server on the net or do you you mean the /var/www/html/weewx/ folder where it resides on my Pi? If the formernot sure how I would even do that? On Tuesday, 5 March 2019 22:45:26 UTC+13, gjr80 wrote: > > Hang on, missed this in the log you posted: > > Mar 5 21:30:30 WeatherPi weewx[19404]: ftpupload: Uploaded file > /public_html/image1.jpg > > Looks like it is being uploaded. What happens if you delete image1.jpg > from your web server, does it get replaced (albeit with an old file) on the > next report cycle? > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Thanks I will give that a try tomorrowits late here. I am thinking that you are right...and the problem lies in the FTP server. I will investigate and get back to you. Thank you for all your help! On Tuesday, 5 March 2019 23:07:12 UTC+13, gjr80 wrote: > > Yes the former, your web host on the internet. Some folks can ssh into > their web server but I am gu swing you haven't done that. Do you have a > login that you can use via a browser to manage your hosting? That should > have some sort of file management tool. > > I am not convinced that the FTP is not working, I think it is. > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Actually, managed to do that nowI deleted all image1.jpg and image.jpg and image-1.jpg files from the web server. The image1.jpg was correctly uploadedso no idea why it is not showing on website! On Tuesday, 5 March 2019 23:12:18 UTC+13, monmul wrote: > > Thanks I will give that a try tomorrowits late here. I am thinking > that you are right...and the problem lies in the FTP server. I will > investigate and get back to you. Thank you for all your help! > > On Tuesday, 5 March 2019 23:07:12 UTC+13, gjr80 wrote: >> >> Yes the former, your web host on the internet. Some folks can ssh into >> their web server but I am gu swing you haven't done that. Do you have a >> login that you can use via a browser to manage your hosting? That should >> have some sort of file management tool. >> >> I am not convinced that the FTP is not working, I think it is. >> >> 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
So this was after I had gone to bedstill showing image1 uploadingand still getting a static image (the source of which I cannot find on the web server) on my web page. 6 01:20:22 WeatherPi weewx[19404]: ftpupload: Attempting connection to 43.245.53.39 Mar 6 01:20:22 WeatherPi weewx[19404]: ftpupload: Connected to 43.245.53.39 Mar 6 01:20:22 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/dayradiation.png Mar 6 01:20:22 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/index.html Mar 6 01:20:22 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/dayrain.png Mar 6 01:20:22 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/daywinddir.png Mar 6 01:20:23 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/daywindvec.png Mar 6 01:20:23 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/daywind.png Mar 6 01:20:23 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/daytempdew.png Mar 6 01:20:23 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/image1.jpg Mar 6 01:20:23 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/dayinside.png Mar 6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/dayuv.png Mar 6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/mobile.html Mar 6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/week.html Mar 6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/daybarometer.png Mar 6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/month.html Mar 6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/daytempchill.png Mar 6 01:20:25 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/dayrx.png Mar 6 01:20:25 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/dayhumidity.png Mar 6 01:20:25 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/year.html Mar 6 01:20:25 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/alltime.html Mar 6 01:20:25 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/xstats/index.html Mar 6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/smartphone/wind.html Mar 6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/smartphone/index.html Mar 6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/smartphone/radar.html Mar 6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/smartphone/rain.html Mar 6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/smartphone/barometer.html Mar 6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/smartphone/temp_outside.html Mar 6 01:20:27 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/NOAA/NOAA-2019.txt Mar 6 01:20:27 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/NOAA/NOAA-2019-03.txt Mar 6 01:20:27 WeatherPi weewx[19404]: ftpupload: Uploaded file /public_html/RSS/weewx_rss.xml Mar 6 01:20:27 WeatherPi weewx[19404]: ftpgenerator: ftp'd 29 files in 5.46 seconds Mar 6 01:20:27 WeatherPi weewx[19404]: reportengine: Running report 'RSYNC' Mar 6 01:20:27 WeatherPi weewx[19404]: reportengine: Found configuration file /etc/weewx/skins/Rsync/skin.conf for report 'RSYNC' Mar 6 01:20:27 WeatherPi weewx[19404]: rsyncgenerato On Tuesday, 5 March 2019 23:55:29 UTC+13, gjr80 wrote: > > Ok, but now when I look at your site image1.jpg does not the display. When > you deleted your jpg files you didn't touch anything on your WeeWX machine > did you? Your image is only produced every hour so if you did delete it on > the WeeWX machine then it could take up to an hour for it to be re-created > and subsequently uploaded to the web server. Keep an eye on your WeeWX log > to see if/when image1.jpg is uploaded. Guess it is getting late there now, > I will have a look later and see what is there. > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Curiouser and curiouser. Attached the image I see from my public website (staticJpg.jpg)...and also the weewx native output on the Pi (ChangeImage.jpg) file:///var/www/html/weewx/index.html On Wednesday, 6 March 2019 10:13:50 UTC+13, gjr80 wrote: > > So at 7:10 my time 10:10 (?) your time I am seeing a daytime photo of a > verandah with water and mountains in the background. That is quite > different to the night time image I first saw last night and the 'black > box' later last night. Give you image only updates on your WeeWX server > once an hour just wondering what basis you have for thinking it is not > working. > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
I am browsing from 2 different pcsone a chromebook using Chrome and one my desktop using Chromium. I have tried both www.wilsonbayweather.com and www.wilsonbayweather.com/index.html..both give the same image.this is weird!why would the various weather icons and data change but not the jpg.I will contact my web host and see if they can throw any light on it. Thanks again! On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote: > > So when I look at your site I see ChangeImage.jpg. Since that is what is > on your WeeWX server it sounds to me like FTP and your web site are working > as they should. Certainly Australia is seeing the correct page/image! It > sounds like when you are looking at a page locally that it is not working. > When you are browsing and seeing that wrong image what address are you > entering in your browser and what device are you browsing from? > > 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Hah! If I look it up on my phoneI get the correct jpg? On Wednesday, 6 March 2019 11:16:49 UTC+13, monmul wrote: > > I am browsing from 2 different pcsone a chromebook using Chrome and > one my desktop using Chromium. I have tried both www.wilsonbayweather.com > and www.wilsonbayweather.com/index.html..both give the same > image.this is weird!why would the various weather icons and data > change but not the jpg.I will contact my web host and see if they can > throw any light on it. Thanks again! > > On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote: >> >> So when I look at your site I see ChangeImage.jpg. Since that is what is >> on your WeeWX server it sounds to me like FTP and your web site are working >> as they should. Certainly Australia is seeing the correct page/image! It >> sounds like when you are looking at a page locally that it is not working. >> When you are browsing and seeing that wrong image what address are you >> entering in your browser and what device are you browsing from? >> >> 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Surely it cannot be something to do with clearing the cache on my browsersthat does not seem realistic! On Wednesday, 6 March 2019 11:24:44 UTC+13, monmul wrote: > > Hah! If I look it up on my phoneI get the correct jpg? > > On Wednesday, 6 March 2019 11:16:49 UTC+13, monmul wrote: >> >> I am browsing from 2 different pcsone a chromebook using Chrome and >> one my desktop using Chromium. I have tried both www.wilsonbayweather.com >> and www.wilsonbayweather.com/index.html..both give the same >> image.this is weird!why would the various weather icons and data >> change but not the jpg.I will contact my web host and see if they can >> throw any light on it. Thanks again! >> >> On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote: >>> >>> So when I look at your site I see ChangeImage.jpg. Since that is what is >>> on your WeeWX server it sounds to me like FTP and your web site are working >>> as they should. Certainly Australia is seeing the correct page/image! It >>> sounds like when you are looking at a page locally that it is not working. >>> When you are browsing and seeing that wrong image what address are you >>> entering in your browser and what device are you browsing from? >>> >>> 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
Yes it was!how freakin weird! Thanks for the help and the prompts! On Wednesday, 6 March 2019 11:27:18 UTC+13, monmul wrote: > > Surely it cannot be something to do with clearing the cache on my > browsersthat does not seem realistic! > > On Wednesday, 6 March 2019 11:24:44 UTC+13, monmul wrote: >> >> Hah! If I look it up on my phoneI get the correct jpg? >> >> On Wednesday, 6 March 2019 11:16:49 UTC+13, monmul wrote: >>> >>> I am browsing from 2 different pcsone a chromebook using Chrome and >>> one my desktop using Chromium. I have tried both >>> www.wilsonbayweather.com and >>> www.wilsonbayweather.com/index.html..both give the same >>> image.this is weird!why would the various weather icons and data >>> change but not the jpg.I will contact my web host and see if they can >>> throw any light on it. Thanks again! >>> >>> On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote: >>>> >>>> So when I look at your site I see ChangeImage.jpg. Since that is what >>>> is on your WeeWX server it sounds to me like FTP and your web site are >>>> working as they should. Certainly Australia is seeing the correct >>>> page/image! It sounds like when you are looking at a page locally that it >>>> is not working. When you are browsing and seeing that wrong image what >>>> address are you entering in your browser and what device are you browsing >>>> from? >>>> >>>> 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.
Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running
That worked a treatthank you! On Monday, 15 April 2019 15:20:37 UTC+12, gjr80 wrote: > > Hi, > > Chances are you have suffered corrupted station memory due to the power > outage. Have a read of the *Corrupt station memory* section under WeeWX > generates HTML pages, but it does not update them > <http://weewx.com/docs/usersguide.htm#html_generated_but_not_updated> in > the User's Guide. Before doing anything stop WeeWX and use wee-device to > dump the station memory > <http://weewx.com/docs/hardware.htm#vantage_dumping_the_logger_memory>, > this is your best bet at minimising any data loss. Once you have dumped the > station memory work through the two steps listed under *Corrupt station > memory*. > > It's worth making a note of this condition and it's symptoms, it is a > common occurrence for Davis stations that have a power interruption. > > Gary > > On Monday, 15 April 2019 12:32:46 UTC+10, monmul wrote: >> >> I have run into a problem. I have been overseas for some time and just >> got back today. There was a power failure yesterday and weewx is stuck on >> mid night. See attached details. The photo on my website updatesbut nor >> the weather information? www.wilsonbayweather.com. What am I missing? >> >> On Wednesday, 6 March 2019 17:07:01 UTC+13, Andrew Milner wrote: >>> >>> That's Chrome and Google for you!! >>> >>> I've got a pic of a nice sunny verandah now also ….. >>> >>> >>> >>> On Wednesday, 6 March 2019 00:30:07 UTC+2, monmul wrote: >>>> >>>> Yes it was!how freakin weird! Thanks for the help and the prompts! >>>> >>>> On Wednesday, 6 March 2019 11:27:18 UTC+13, monmul wrote: >>>>> >>>>> Surely it cannot be something to do with clearing the cache on my >>>>> browsersthat does not seem realistic! >>>>> >>>>> On Wednesday, 6 March 2019 11:24:44 UTC+13, monmul wrote: >>>>>> >>>>>> Hah! If I look it up on my phoneI get the correct jpg? >>>>>> >>>>>> On Wednesday, 6 March 2019 11:16:49 UTC+13, monmul wrote: >>>>>>> >>>>>>> I am browsing from 2 different pcsone a chromebook using Chrome >>>>>>> and one my desktop using Chromium. I have tried both >>>>>>> www.wilsonbayweather.com and >>>>>>> www.wilsonbayweather.com/index.html..both give the same >>>>>>> image.this is weird!why would the various weather icons and >>>>>>> data >>>>>>> change but not the jpg.I will contact my web host and see if they >>>>>>> can >>>>>>> throw any light on it. Thanks again! >>>>>>> >>>>>>> On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote: >>>>>>>> >>>>>>>> So when I look at your site I see ChangeImage.jpg. Since that is >>>>>>>> what is on your WeeWX server it sounds to me like FTP and your web >>>>>>>> site are >>>>>>>> working as they should. Certainly Australia is seeing the correct >>>>>>>> page/image! It sounds like when you are looking at a page locally that >>>>>>>> it >>>>>>>> is not working. When you are browsing and seeing that wrong image what >>>>>>>> address are you entering in your browser and what device are you >>>>>>>> browsing >>>>>>>> from? >>>>>>>> >>>>>>>> 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] Temp showing N/A
Around midnight last night - after months of operating properly my ststem
started recording N/A for temperature. I have tried dumping memory etc and
restartedit has restarted but the problem is the same. Here is the log.
What has happened and how do I fix it please.
base 'weewx.sdb'
Jun 16 10:24:37 WeatherPi weewx[583]: manager: Starting backfill of daily
summaries
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.engine.StdArchive
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdStationRegistry
Jun 16 10:24:37 WeatherPi weewx[583]: restx: StationRegistry: Registration
not requested.
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdStationRegistry
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdWunderground
Jun 16 10:24:37 WeatherPi weewx[583]: restx: WU essentials: {}
Jun 16 10:24:37 WeatherPi weewx[583]: restx: Wunderground-PWS: Data for
station IOTAGOQU2 will be posted
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdWunderground
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdPWSweather
Jun 16 10:24:37 WeatherPi weewx[583]: restx: PWSweather: Posting not
enabled.
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdPWSweather
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdCWOP
Jun 16 10:24:37 WeatherPi weewx[583]: restx: CWOP: Posting not enabled.
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdCWOP
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdWOW
Jun 16 10:24:37 WeatherPi weewx[583]: restx: WOW: Posting not enabled.
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdWOW
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.restx.StdAWEKAS
Jun 16 10:24:37 WeatherPi weewx[583]: restx: AWEKAS: Posting not enabled.
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.restx.StdAWEKAS
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.engine.StdPrint
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.engine.StdPrint
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
weewx.engine.StdReport
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
weewx.engine.StdReport
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting up weewx version
3.9.1
Jun 16 10:24:37 WeatherPi weewx[583]: manager: Daily summary version is 2.0
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
successful
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Clock error is 1.22 seconds
(positive is fast)
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Getting archive packets
since 2019-06-16 10:10:00 NZST (1560636600)
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
successful
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Retrieving 0 page(s);
starting index= 0
Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting main packet loop.
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
successful
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
successful
Jun 16 10:24:41 WeatherPi weewx[583]: vantage: LOOP try #1; error: Expected
to read 99 chars; got 0 instead
Jun 16 10:24:41 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Retry #0 failed
Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Rude wake up of console
successful
Jun 16 10:24:47 WeatherPi weewx[583]: vantage: LOOP try #2; error: Expected
to read 99 chars; got 0 instead
Jun 16 10:24:47 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Retry #0 failed
Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Rude wake up of console
successful
Jun 16 10:24:52 WeatherPi weewx[583]: vantage: LOOP try #3; error: Expected
to read 99 chars; got 0 instead
Jun 16 10:24:52 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
Jun 16 10:24:53 WeatherPi weewx[583]: vantage: Retry #0 failed
Jun 16 10:24:53 WeatherPi weewx[583]: vantage: Rude wake up of console
successful
Jun 16 10:24:58 WeatherPi weewx[583]: vantage: LOOP try #4; error: Expected
to read 99 chars; got 0 instead
Jun 16 10:24:58 WeatherPi weewx[583]: vantage: LOOP max tries (4) exceeded.
Jun 16 10:24:58 WeatherPi weewx[583]: engine: Main loop exiting. Shutting
engine down.
Jun 16 10:24:58 WeatherPi weewx[583]: restx: Shut down Wunderground-PWS
thread.
Jun 16 10:24:58 WeatherPi weewx[583]: engine: Caught WeeWxIOError: Max
tries exceeded while getting LOOP data.
Jun 16 10:24:58 WeatherPi weewx[583]: Waiting 60 seconds then
retrying...
Jun 16 10:25:58 Wea
[weewx-user] Re: Temp showing N/A
I notice the signal quality went from 100 to 0 at midnight also!!the
Barometer is still reading as normal and posting to the template!
On Sunday, 16 June 2019 10:47:36 UTC+12, monmul wrote:
>
> Around midnight last night - after months of operating properly my ststem
> started recording N/A for temperature. I have tried dumping memory etc and
> restartedit has restarted but the problem is the same. Here is the log.
> What has happened and how do I fix it please.
>
> base 'weewx.sdb'
> Jun 16 10:24:37 WeatherPi weewx[583]: manager: Starting backfill of daily
> summaries
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdArchive
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdStationRegistry
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: StationRegistry: Registration
> not requested.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdStationRegistry
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdWunderground
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: WU essentials: {}
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: Wunderground-PWS: Data for
> station IOTAGOQU2 will be posted
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdWunderground
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdPWSweather
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: PWSweather: Posting not
> enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdPWSweather
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdCWOP
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: CWOP: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdCWOP
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdWOW
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: WOW: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdWOW
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdAWEKAS
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: AWEKAS: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdAWEKAS
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.engine.StdPrint
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdPrint
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.engine.StdReport
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdReport
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting up weewx version
> 3.9.1
> Jun 16 10:24:37 WeatherPi weewx[583]: manager: Daily summary version is 2.0
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Clock error is 1.22 seconds
> (positive is fast)
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Getting archive packets
> since 2019-06-16 10:10:00 NZST (1560636600)
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Retrieving 0 page(s);
> starting index= 0
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting main packet loop.
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:41 WeatherPi weewx[583]: vantage: LOOP try #1; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:41 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Retry #0 failed
> Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Rude wake up of console
> successful
> Jun 16 10:24:47 WeatherPi weewx[583]: vantage: LOOP try #2; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:47 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Retry #0 failed
> Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Rude wake up of console
> successful
> Jun 16 10:24:52 WeatherPi weewx[583]: vantage: LOOP try #3; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:52 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:53 WeatherPi weewx[583]: vantage: Retry #0 failed
&g
[weewx-user] Re: Temp showing N/A
Oh! Mirabile Dictu!...it has started recording temp again.I am
wondering if the battery has run out and when the sun started hitting the
solar panel of the weather station, it started recording againbut why
would the pressure have continued recordinghmmm! more mysteries!
On Sunday, 16 June 2019 10:47:36 UTC+12, monmul wrote:
>
> Around midnight last night - after months of operating properly my ststem
> started recording N/A for temperature. I have tried dumping memory etc and
> restartedit has restarted but the problem is the same. Here is the log.
> What has happened and how do I fix it please.
>
> base 'weewx.sdb'
> Jun 16 10:24:37 WeatherPi weewx[583]: manager: Starting backfill of daily
> summaries
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdArchive
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdStationRegistry
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: StationRegistry: Registration
> not requested.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdStationRegistry
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdWunderground
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: WU essentials: {}
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: Wunderground-PWS: Data for
> station IOTAGOQU2 will be posted
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdWunderground
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdPWSweather
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: PWSweather: Posting not
> enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdPWSweather
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdCWOP
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: CWOP: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdCWOP
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdWOW
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: WOW: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdWOW
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.restx.StdAWEKAS
> Jun 16 10:24:37 WeatherPi weewx[583]: restx: AWEKAS: Posting not enabled.
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.restx.StdAWEKAS
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.engine.StdPrint
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdPrint
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Loading service
> weewx.engine.StdReport
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Finished loading service
> weewx.engine.StdReport
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting up weewx version
> 3.9.1
> Jun 16 10:24:37 WeatherPi weewx[583]: manager: Daily summary version is 2.0
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Clock error is 1.22 seconds
> (positive is fast)
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Getting archive packets
> since 2019-06-16 10:10:00 NZST (1560636600)
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Retrieving 0 page(s);
> starting index= 0
> Jun 16 10:24:37 WeatherPi weewx[583]: engine: Starting main packet loop.
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:37 WeatherPi weewx[583]: vantage: Gentle wake up of console
> successful
> Jun 16 10:24:41 WeatherPi weewx[583]: vantage: LOOP try #1; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:41 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Retry #0 failed
> Jun 16 10:24:43 WeatherPi weewx[583]: vantage: Rude wake up of console
> successful
> Jun 16 10:24:47 WeatherPi weewx[583]: vantage: LOOP try #2; error:
> Expected to read 99 chars; got 0 instead
> Jun 16 10:24:47 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets.
> Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Retry #0 failed
> Jun 16 10:24:48 WeatherPi weewx[583]: vantage: Rude wake up of console
> successful
> Jun 16 10:24:52 WeatherPi weewx[583]: vantage: LOOP try #3; error:
> Expected to read 99 chars; got 0 instead
> Jun 1
[weewx-user] Re: Temp showing N/A
Thank you Garyyour analysis was spot onas usual! On Sunday, 16 June 2019 14:10:21 UTC+12, gjr80 wrote: > > Hi, > > Mirabile Dictu! > > > Sort of guessed what that meant but had to look that one up to be sure! > > A few comments. Pressure comes from a sensor in the console as does inside > temperature so it is possible that if your ISS cannot be contacted by the > console WeeWX may still have communications with the console and pressure > and inside temperature may well still be recorded and posted to WU - > everything else will likely be None or N/A (or a WU default in the case of > WU). Since you mention a solar panel I presume you are referring to the > solar panel on your ISS meaning you have the wireless version. I don't have > one myself but I understand there was a super cap (high capacity capacitor) > in the ISS that stores solar energy to keep the ISS running overnight. If > that fails the ISS falls back to a non-rechargeable lithium battery. Could > be lack of sun or the super cap failing has meant it did not have enough > energy to keep your ISS running overnight and if your lithium battery > happens to be dead your ISS would die. It would then take until there was > enough solar power to get the ISS running (and maybe charging the super cap > to a certain extent) before things came back again. Given it's winter and > depending on your solar panel orientation/location/shielding, it could take > until around 11:30am before it had sufficient power to get the ISS running > again. Super caps do fail (Google replace Davis super cap) as do lithium > batteries. It could be a case of the super cap (largely) failing some time > ago and the lithium battery has been carrying the ISS overnight for a while > and now it is finally flat. > > If WeeWX was posting pressure data to WU overnight then WeeWX must have > had good comms with the console (which you would expect even if the ISS > failed). In the log extract you post there is a repeated and seemingly > continuous failure to obtain loop packets from the console: > > Jun 16 10:25:59 WeatherPi weewx[583]: vantage: Gentle wake up of console > successful > Jun 16 10:25:59 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets > . > Jun 16 10:25:59 WeatherPi weewx[583]: vantage: Gentle wake up of console > successful > Jun 16 10:26:03 WeatherPi weewx[583]: vantage: LOOP try #1; error: > Expected to read 99 chars; got 0 instead > Jun 16 10:26:03 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets > . > Jun 16 10:26:04 WeatherPi weewx[583]: vantage: Retry #0 failed > Jun 16 10:26:04 WeatherPi weewx[583]: vantage: Rude wake up of console > successful > Jun 16 10:26:08 WeatherPi weewx[583]: vantage: LOOP try #2; error: > Expected to read 99 chars; got 0 instead > Jun 16 10:26:08 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets > . > Jun 16 10:26:10 WeatherPi weewx[583]: vantage: Retry #0 failed > Jun 16 10:26:10 WeatherPi weewx[583]: vantage: Rude wake up of console > successful > Jun 16 10:26:14 WeatherPi weewx[583]: vantage: LOOP try #3; error: > Expected to read 99 chars; got 0 instead > Jun 16 10:26:14 WeatherPi weewx[583]: vantage: Requesting 200 LOOP packets > . > Jun 16 10:26:15 WeatherPi weewx[583]: vantage: Retry #0 failed > Jun 16 10:26:15 WeatherPi weewx[583]: vantage: Rude wake up of console > successful > Jun 16 10:26:19 WeatherPi weewx[583]: vantage: LOOP try #4; error: > Expected to read 99 chars; got 0 instead > Jun 16 10:26:19 WeatherPi weewx[583]: vantage: LOOP max tries (4) exceeded > . > Jun 16 10:26:19 WeatherPi weewx[583]: engine: Main loop exiting. Shutting > engine down. > Jun 16 10:26:19 WeatherPi weewx[583]: restx: Shut down Wunderground-PWS > thread. > Jun 16 10:26:19 WeatherPi weewx[583]: engine: Caught WeeWxIOError: Max > tries exceeded while getting LOOP data. > Jun 16 10:26:19 WeatherPi weewx[583]: Waiting 60 seconds then > retrying... > > Without a connection to the ISS there is no data to put in a loop packet > but I am not sure what the console does in this case, maybe if just refuses > to send loop packets but does send archive records (which would contain > pressure and inside temperature). Maybe those log entries are as a a result > of your efforts to get things working again in the morning and they did not > go on all night. > > I would be inclined to give it the benefit of the doubt for now, but I > expect it will happen again and it might then be a case of replacing one or > both of the super cap and lithium battery. If your ISS is easily accessible > it might be worth a look inside for any signs of leakage or bulging of the > super cap. > > Gary > > > On
[weewx-user] Booting existing RPi3b from USB rather than SD
I have weewx running, very happily and very successfully, (thanks to all here who helped me!) on a Rpi3B. The Pi is running Raspian and the standard SD card. Now, I got to thinking that this is probably not the most secure long tern setup - due to wear and tear on the SD card etc. So, I was thinking of setting up the Pi to run off a USB drive, I have all the Weewx folders backed up. What would be the most sensible way of transferring the whole boot and Home directory etc to the USB drive. As the system is running so well, I am a tad reluctant to go fiddling with it.but I know I will have to sooner or later. Your thoughts and suggestions would be 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/32cfbe26-20e1-4b7e-9dfc-b12cf385be52%40googlegroups.com.
