Re: [weewx-user] Weewx fails to start

[David Hindley]

Tom - OK. Many thanks. Will try that suggestion.

David.

On Wed, 4 Sep 2024 at 21:32, Tom Keffer  wrote:

> I'm sorry, but there are too many moving parts here. The problem depends
> on your environment, /etc/default/weewx, what's in /usr/bin/weewxd, the
> location of the other weewx files, etc.
>
> Something changed on your system. You're going to have to track it down.
>
> Here's what I would do: get a second SD card (less than $10). Install the
> latest RPi OS on it. Install WeeWX v5 on it.
>
> Then copy over the database (located under /var/lib/weewx) and the skins
> (located under /etc/weewx) from the old card. Or, copy from your backup. No
> chance of losing any data.
>
> -tk
>
> On Wed, Sep 4, 2024 at 1:05 PM hind...@gmail.com 
> wrote:
>
>> OK.  No problem.  It is attached.  I renamed it to weewx_init. It is
>> called weewx on my Pi.
>>
>> Noted re upgrading.  Nervous about losing data etc.
>>
>> David.
>>
>> On Wednesday 4 September 2024 at 20:44:54 UTC+1 Tom Keffer wrote:
>>
>>> A favor. Please post the *entire* file. Don't cut and paste, just
>>> include the file. It's hard to get the full picture from the little pieces.
>>>
>>> I would also strongly advise that you upgrade from stretch. It hasn't
>>> been supported in years. Your RPi 3 is more than capable of running a
>>> modern version of RPi OS.
>>>
>>> On Wed, Sep 4, 2024 at 12:06 PM hind...@gmail.com 
>>> wrote:
>>>
 I should add, when I start weewx, I get:

 [] Starting weewx (via systemctl): weewx.service AUTHENTICATING
 FOR org.


   freedesktop.systemd1.manage-units ===
 Authentication is required to start 'weewx.service'.
 Multiple identities can be used for authentication:
  1.  ,,, (pi)
  2.  root
 Choose identity to authenticate as (1-2): 1
 Password:
  AUTHENTICATION COMPLETE ===
 Job for weewx.service failed because the control process exited with
 error code.
 See "systemctl status weewx.service" and "journalctl -xe" for details.
  failed!

 Does that helpo diagnose the problem.  I never remember being asked for
 identity before.  I am not sure I know the root password (dumb, I know).
 On Wednesday 4 September 2024 at 19:47:33 UTC+1 hind...@gmail.com
 wrote:

> No problem.
>
> Copied below.
>
> I don't think I modified anything,  My weather website stopped working
> when I was on holiday. The last valid graph entry is 20 August 2024 at 5pm
> -but not sure my syslog files go back that far to check what happened.
>
> . /lib/init/vars.sh
>
> # Define LSB log_* functions.
> # Depend on lsb-base (>= 3.0-6) to ensure that this file is present.
> . /lib/lsb/init-functions
>
> # start the daemon/service
> #   0 if daemon has been started
> #   1 if daemon was already running
> #   2 if daemon could not be started
> # check using ps not the pid file.  pid file could be leftover.
> do_start() {
> NPROC=$(count_procs)
> if [ $NPROC != 0 ]; then
> return 1
> fi
> start-stop-daemon --start --chuid $WEEWX_USER --pidfile $PIDFILE
> --exec $DAEMON -- $DAEMON_ARGS || return 2
> return 0
> }
>
> # stop the daemon/service
> #   0 if daemon has been stopped
> #   1 if daemon was already stopped
> #   2 if daemon could not be stopped
> #   other if a failure occurred
> do_stop() {
> # bail out if the app is not running
> NPROC=$(count_procs)
> if [ $NPROC = 0 ]; then
> return 1
> fi
> # bail out if there is no pid file
> if [ ! -f $PIDFILE ]; then
> return 1
> fi
> start-stop-daemon --stop --pidfile $PIDFILE
> # we cannot trust the return value from start-stop-daemon
> RETVAL=2
> c=0
> while [ $c -lt 24 -a "$RETVAL" = "2" ]; do
> c=`expr $c + 1`
> # process may not really have completed, so check it
> NPROC=$(count_procs)
> if [ $NPROC = 0 ]; then
> RETVAL=0
> else
> echo -n "."
> sleep 5
> fi
> done
> if [ "$RETVAL" = "0" -o "$RETVAL" = "1" ]; then
> # delete the pid file just in case
> rm -f $PIDFILE
> fi
> return "$RETVAL"
> }
>
> # send a SIGHUP to the daemon/service
> do_reload() {
> start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE
> return 0
> }
>
> count_procs() {
> NPROC=`ps ax | grep $WEEWX_BIN | grep $NAME.pid | wc -l`
> echo $NPROC
> }
>
> RETVAL=0
> case "$1" in
> start)
> log_daemon_msg "Starting $DESC" "$NAME"
> do_start
> case "$?" in
> 0) log_end_msg 0; RETVAL=0 ;;
> 1) log_action_cont_msg " a

Re: [weewx-user] Pipe errors etc

[David Hindley]

Many thanks, Vince. Much appreciated.

David.

On Wed, 27 Dec 2023 at 17:08, vince  wrote:

> "except KeyError, e:"  indicates that you are using python3 to run code
> that is only valid for python2.
> see https://github.com/weewx/weewx/wiki/faq-python-error
>
> Upgrade your MQTT extension to a current version.
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/2beac3b1-a0b4-4735-8943-5eb3f4a0e5d7n%40googlegroups.com
> 
> .
>

-- 
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/CAHtYHVKG2q9qq%2BZYptkA2SKUp3skZaY9ij7HNUvihQ_UbcofSg%40mail.gmail.com.

Re: [weewx-user] Pipe errors etc

[David Hindley]

Thanks for your reply Vince.  Completely understand re network. I am using
Ethernet rather than WiFi for both my Rpi which hosts weewx and my davis
weather station.

Does anyone have any input on my question about stopping weewx please?
Repeated here:

In the meantime, I am having trouble stopping weewx - not sure if this is
related to my ongoing pipe errors or not.  When I type

ps -aux|grep weewx

I get

root   535  5.6  6.1 117524 58128 ?Sl   10:16   2:42 python2
/usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid
/etc/weewx/weewx.conf
pi2130  0.0  0.0   4368   564 pts/0S+   11:04   0:00 grep
--color=auto weewx

And, then typing

sudo /etc/init.d/weewx stop

produces

 Stopping weewx (via systemctl): weewx.service.

but then repeating the grep command, still shows the 535 process still
running?

How do I stop weewx - do I have to use kill 535 perhaps?

Thanks

David.

On Sat, 16 Dec 2023 at 19:39, vince  wrote:

> Sorry - we can't fix your network.  Lots of legacy embedded type 2.4GHz
> wifi things have issues staying on the network and stable.   I'd suggest
> you try to see if your wifi is being interfered with from a neighbor
> perhaps.  Maybe you can switch which channel your wifi is on.
>
> FWIW, we have too many neighbors here with misconfigured wifi to even
> count, depending on who moves in/out and who visits them occasionally.
> What I eventually needed to do was (a) move everything in the house that
> could do it over to 5GHz wifi, and (b) buy a Unifi AcLite AP and basically
> try to out-radiate the neighbors.  Problem went away at that point.
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/b4ebe949-5ee5-4221-b91c-ba84e21d64f4n%40googlegroups.com
> 
> .
>

-- 
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/CAHtYHVLtTSA9rq-fKN%2BPaDMJazz41B1OdBVfxHxKJa%3DZ%2BRim4A%40mail.gmail.com.

Re: [weewx-user] Pipe errors etc

[David Hindley]

Perfect.  Thanks.

On Fri, 8 Dec 2023 at 12:12, Jacques Terrettaz  wrote:

> Yes, you should !
>
> The Meteo-Pi HAT card is providing an internal serial port t which weewx
> will connect to capture the data.
>
> Le 8 déc. 2023 à 12:45, David Hindley  a écrit :
>
> Many thanks. Can I have weewx running on the same RPi that the Meteo-Pi is
> connected to?
>
> David.
>
> On Fri, 8 Dec 2023 at 11:12, Jacques Terrettaz 
> wrote:
>
>> Since you have a RaspberryPi, you may also consider buying a "Meteo-pi"
>>  instead of a WifiLogger2 - see https://wifilogger.net/meteopi.html
>>
>> The datalogger card is plugged to the console and the HAT card is plugged
>> to the 40-pin header of the RPI and both are linked with a RJ11 cable : no
>> more network problems !
>>
>> I am using a Meteo-Pi since several years and I never had a single
>> problem of communication between the console and weewx
>>
>>
>>
>> Le 8 déc. 2023 à 11:04, hind...@gmail.com  a écrit :
>>
>>  the only thing I can think of doing next is to replace the davis
>> Ethernet datalogger with the WifiLogger2, but that is quite expensive so
>> I'd rather not do that unless I really have to.  I have also seen some
>> users having pipe errors with this wiflogger, so am a bit nervous about
>> buying it.
>>
>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/C8184E3C-8E77-4F14-9B2B-DCDDBA6108C8%40gmail.com
>> <https://groups.google.com/d/msgid/weewx-user/C8184E3C-8E77-4F14-9B2B-DCDDBA6108C8%40gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAHtYHVKJZtOFy1dQ-GpVoUOaNXqbxT-%2Bb3bw03VtBOAq16%2BSrQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAHtYHVKJZtOFy1dQ-GpVoUOaNXqbxT-%2Bb3bw03VtBOAq16%2BSrQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/53C447C0-D2EF-44B1-9E9A-09A998A7D070%40gmail.com
> <https://groups.google.com/d/msgid/weewx-user/53C447C0-D2EF-44B1-9E9A-09A998A7D070%40gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CAHtYHVLKDPd6AKEiJpu_65pb4PJ%2BajQr2M24ZxkMt0Kj-Hv%2Bmg%40mail.gmail.com.

Re: [weewx-user] Pipe errors etc

[David Hindley]

Tom - that is correct.  I don’t seem to be able to browse to the device. I
type its IP address into a browser on my Windows PC on the same network and
nothing happens.  I can access the console via the weatherlink software,
but don’t see anywhere where I can disable weatherlink uploads.

David.
On Fri, 8 Dec 2023 at 13:10, Tom Keffer  wrote:

> Just to clarify, you have a Davis 6555 WeatherlinkIP, right?
>
> Before buying new equipment, I'd focus on Jacque's suggestion to disable
> any transmissions to weatherlink.com from the device. You should be able
> to browse to the device and get an option to turn the transmissions off.
>
>
> On Fri, Dec 8, 2023 at 3:45 AM David Hindley  wrote:
>
>> Many thanks. Can I have weewx running on the same RPi that the Meteo-Pi
>> is connected to?
>>
>> David.
>>
>> On Fri, 8 Dec 2023 at 11:12, Jacques Terrettaz 
>> wrote:
>>
>>> Since you have a RaspberryPi, you may also consider buying a "Meteo-pi"
>>>  instead of a WifiLogger2 - see https://wifilogger.net/meteopi.html
>>>
>>> The datalogger card is plugged to the console and the HAT card is
>>> plugged to the 40-pin header of the RPI and both are linked with a RJ11
>>> cable : no more network problems !
>>>
>>> I am using a Meteo-Pi since several years and I never had a single
>>> problem of communication between the console and weewx
>>>
>>>
>>>
>>> Le 8 déc. 2023 à 11:04, hind...@gmail.com  a écrit
>>> :
>>>
>>>  the only thing I can think of doing next is to replace the davis
>>> Ethernet datalogger with the WifiLogger2, but that is quite expensive so
>>> I'd rather not do that unless I really have to.  I have also seen some
>>> users having pipe errors with this wiflogger, so am a bit nervous about
>>> buying it.
>>>
>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
>>> To unsubscribe from this group and all its topics, 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/C8184E3C-8E77-4F14-9B2B-DCDDBA6108C8%40gmail.com
>>> <https://groups.google.com/d/msgid/weewx-user/C8184E3C-8E77-4F14-9B2B-DCDDBA6108C8%40gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>
>>
>>> --
>> 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/CAHtYHVKJZtOFy1dQ-GpVoUOaNXqbxT-%2Bb3bw03VtBOAq16%2BSrQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/weewx-user/CAHtYHVKJZtOFy1dQ-GpVoUOaNXqbxT-%2Bb3bw03VtBOAq16%2BSrQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAPq0zEBUrpzUNiYs%3D7i_8uNCeV5NYZACvys95MJdjFxH_Hmniw%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEBUrpzUNiYs%3D7i_8uNCeV5NYZACvys95MJdjFxH_Hmniw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CAHtYHV%2BXD5Ekp-nqUL95v9u3rJs_qoOrY15L4f78GZ6PbY6Viw%40mail.gmail.com.

Re: [weewx-user] Pipe errors etc

[David Hindley]

Many thanks. Can I have weewx running on the same RPi that the Meteo-Pi is
connected to?

David.

On Fri, 8 Dec 2023 at 11:12, Jacques Terrettaz  wrote:

> Since you have a RaspberryPi, you may also consider buying a "Meteo-pi"
>  instead of a WifiLogger2 - see https://wifilogger.net/meteopi.html
>
> The datalogger card is plugged to the console and the HAT card is plugged
> to the 40-pin header of the RPI and both are linked with a RJ11 cable : no
> more network problems !
>
> I am using a Meteo-Pi since several years and I never had a single problem
> of communication between the console and weewx
>
>
>
> Le 8 déc. 2023 à 11:04, hind...@gmail.com  a écrit :
>
>  the only thing I can think of doing next is to replace the davis
> Ethernet datalogger with the WifiLogger2, but that is quite expensive so
> I'd rather not do that unless I really have to.  I have also seen some
> users having pipe errors with this wiflogger, so am a bit nervous about
> buying it.
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/C8184E3C-8E77-4F14-9B2B-DCDDBA6108C8%40gmail.com
> 
> .
>

-- 
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/CAHtYHVKJZtOFy1dQ-GpVoUOaNXqbxT-%2Bb3bw03VtBOAq16%2BSrQ%40mail.gmail.com.

Re: [weewx-user] Pipe errors etc

[David Hindley]

Thanks. I did that and I just get “This site can’t be reached”. My
datalogger is connected via Ethernet, and I think is no longer made by
davis.

On Thu, 7 Dec 2023 at 14:29, jterr...@gmail.com 
wrote:

> According to your weewx logs, the ip address of the datalogger is
> 192.168.0.25.
>
> So shut down weewx and open this URL  http://192.168.0.25  using your web
> browser
>
> Le jeudi 7 décembre 2023 à 13:25:20 UTC+1, hind...@gmail.com a écrit :
>
>> Many thanks for these suggestions. Regarding 1. how do I connect to the
>> datalogger in order to uncheck the "Upload to weatherlink" option?  If the
>> weatherlink upload is causing the conflict, I am not clear why this would
>> suddenly start being an issue, but certainly worth trying.
>> On 2, no, I don't have a static IP address for the datalogger, or any
>> other device configured with the same IP address.
>>
>> On Wednesday 6 December 2023 at 07:46:08 UTC jterr...@gmail.com wrote:
>>
>>> David,
>>>
>>> I have 2 suggestions about your network problems with your IP datalogger
>>> :
>>>
>>>1. By default, the IP datalogger will periodically send sensor
>>>real-time data and datalogger archive data to weatherlink.com
>>>servers. Weewx needs exclusive access to the IP datalogger. You may try 
>>> to
>>>disable the upload to weatherlink servers by connecting to the datalogger
>>>using a web browser and uncheck the "Upload to weatherlink.com"
>>>option.  Concerning the exclusive access needed by weewx, are you using 
>>> any
>>>other software (Weatherlink software or any other) that connects to the 
>>> IP
>>>datalogger and that may break the weewx-datalogger pipe ?
>>>2. Is the IP logger configured with  a static IP address ? If it is
>>>the case, check that you don't have any other network device configured
>>>statically with the same IP address. Check also that the address range of
>>>the DHCP server of your router does not overlap with the static IP 
>>> address
>>>of the datalogger.
>>>
>>>
>>> Le mardi 5 décembre 2023 à 18:58:12 UTC+1, hind...@gmail.com a écrit :
>>>
 Thanks.  I might end up having to try one of these options.

 On Tuesday 5 December 2023 at 15:19:35 UTC gary@gmail.com wrote:

> I went with a WiFiLogger2 which has performed without a hitch for a
> couple of years now.
> The maker also has an Ethernet unit if you don't want the added heat
> from a radio in your console.
>
> https://wifilogger.net/
>
> https://wifilogger.net/ethernet.html
>
> On Tuesday, December 5, 2023 at 6:54:14 AM UTC-5 hind...@gmail.com
> wrote:
>
>> I have recently moved a BT Wholehome Wifi disc a little closer to the
>> Console  (10cm now; was 100cm)  , so I guess that *might* be
>> "interfering" in some way  - I will try moving it further away again to 
>> see
>> if that solves the problem.  I have already re-seated the WLIP logger a 
>> few
>> times. Incidentally, if Davis no longer make the WLIP logger, does anyone
>> know what the the preferred method now is of getting the data from the
>> weather station to weewx etc?
>>
>> I may also try the different drive that was suggested in
>> https://groups.google.com/g/weewx-user/c/q67cvEsXtjQ/m/7difZtkUAgAJ.
>>
>> Regarding the question in
>> https://groups.google.com/g/weewx-user/c/q67cvEsXtjQ/m/J9W5KA7rAQAJ,
>> I haven't changed anything on my network, other than moving a few 
>> ethernet
>> cables for other devices around, due to an unstable Sky TV connection.
>>
>> Thanks to everyone that has commented on this to help me find a
>> solution.  Much appreciated.
>>
>> David.
>>
>> On Tuesday 5 December 2023 at 00:25:06 UTC Tom Keffer wrote:
>>
>>> That's certainly possible. I'd say ask Davis, but this logger has
>>> been so long out of production that I doubt David would get any
>>> satisfaction out of them.
>>>
>>> I'm also suspicious when electronic devices "just break." That's
>>> very rare. But, it does happen.
>>>
>>> One thing you could try: reseating the logger.
>>>
>>> Oh, and is there any new source of RF nearby? A new router?
>>> Satellite dish? 5 kW pirate radio?
>>>
>>> On Mon, Dec 4, 2023 at 4:17 PM Graham Eddy  wrote:
>>>
 the vantage IP device seems to accept a connection, work for a
 while, then stop responding, then connection is reset → sounds like on
 device side it seizes up and the ip protocol times out; establishing 
 new
 connection just repeats the cycle. the device apparently has been 
 working
 for years and is now failing → sounds like device has broken
 *⊣GE⊢*

 On 5 Dec 2023, at 9:23 am, vince  wrote:

 Just a thought, but when I see "weewx.drivers.vantage: ip-read
 error: timed out" that makes me think your networ

Re: [weewx-user] Settings to change after IP address of Vantage changes

[David Hindley]

Les

OK. Will turn the firewall off temporarily.

How do I only use the Ethernet interface? (ie disable the Wi-Fi).

David.
On Thu, 8 Jul 2021 at 17:57, Les Niles  wrote:

> Having both interfaces active isn’t a problem itself, but it doesn’t open
> up the potential for various isconfigurations that can make networking
> flaky. I’ve discovered a number of them myself. :)  Just want to eliminate
> that as the source of the problem.
>
> David, it would also be useful to turn off the firewall while debugging
> this. I don’t see evidence that the firewall is the problem, but turning it
> off would eliminate any possibility.
> “sudo disable ufw” should do it.
>
>   -Les
>
>
> On Jul 8, 2021, at 8:34 AM, vince  wrote:
>
> I have a wired pi that shows both wifi and ethernet interfaces up so that
> part is typical.
>
> A quick look at the logs show lots of DNS resolution errors (Temporary
> failure in name resolution) and a bouncy eth0 interface (carrier lost).
> Also some really bizarre hostnames ('home756219443.1and1-data.host')
>
> To me the network looks pretty confused at best.
>
>
> --
> 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/19ef35bc-df92-43f3-a8eb-08717f3fc8e7n%40googlegroups.com
> 
> .
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/9gG34XNbgDk/unsubscribe.
> To unsubscribe from this group and all its topics, 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/E8D77E3A-74AE-47B1-B622-597153F67E45%402pi.org
> 
> .
>

-- 
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/CAKbmhJSeXtCZU2-CfGPfz-WQx94049n21%2Br1rgi0Kw1B1hs0MQ%40mail.gmail.com.

Re: [weewx-user] Settings to change after IP address of Vantage changes

[David Hindley]

My Virgin router keeps rebooting for no apparent reason so that my internet
connection keeps dropping and eventually reconnecting - extremely
annoying.  I changed my network setup to use the Virgin router rather than
another router, to try to fix this issue and this change necessitated the
change the IP address of the Davis Weather station in the weewx conf file.

Just tried to do what you asked below and it crashed again before I had a
chance to run the commands.

My Pi is connected via an Ethernet cable to my router (directly) and my
Davis Vantage Pro2 is also connected via an Ethernet WPlogger (via an
Ethernet switch box to the Virgin router).

Will try the commands you suggested as soon as I can.

On Thu, 8 Jul 2021 at 16:03, Les Niles  wrote:

> This time it looks like you only have one instance of weewx running.
> That’s progress.
>
> What do you mean by your “network crashed”?
>
> I didn’t notice this before, but it looks like you’re using both the
> ethernet and wi-fi interfaces on the Pi.  How is the Davis connected to the
> Pi?
> Please run the commands “/sbin/ifconfig -a”, “sudo /sbin/route -n”, and
> “/usr/sbin/arp -n" and send the outputs.
>
>   -Les
>
>
>
> On 8 Jul 2021, at 4:40, David Hindley  wrote:
>
> Gary
>
> Many thanks for your reply.
>
> The log of what happened when I did as you suggest is below.  I have
> included my attempts to kill the weewx PIDs at the start.  There is less
> than 10mins, as my network crashed half way through (this intermitten
> crashing is what caused me to change my router set up and hence the IP
> address of the Davis Vantage Pro2 and hence the issues described here).  At
> least this now appears to only show one weewx PID, as far as I can see.
> Any further help you can give would be really appreciated.
>
> pi@raspberrypi:~ $ sudo systemctl stop weewx
>
> pi@raspberrypi:~ $ ps -aux|grep weewx
>
> pi6438  0.0  0.0   4368   552 pts/0S+   11:23   0:00 grep
> --color=au
>  to weewx
>
> pi@raspberrypi:~ $ kill -9 6438
>
> -bash: kill: (6438) - No such process
>
> pi@raspberrypi:~ $ kill -9 4368
>
> -bash: kill: (4368) - No such process
>
> pi@raspberrypi:~ $ ps -aux|grep weewx
>
> pi6457  0.0  0.0   4368   564 pts/0S+   11:26   0:00 grep
> --color=auto weewx
>
> pi@raspberrypi:~ $ kill -9 6457
>
> -bash: kill: (6457) - No such process
>
> pi@raspberrypi:~ $ sudo systemctl start weewx
>
> pi@raspberrypi:~ $ ps -aux|grep weewx
>
> root  6484  1.0  1.0  15452  9660 ?S11:27   0:00 python2
> /usr/share/weewx/weewxd --daemon
> --pidf
> ile=/var/run/weewx.pid
> /etc/weewx/weewx.conf
>
> pi6489  0.0  0.0   4368   544 pts/0S+   11:28   0:00 grep
> --color=auto weewx
>
> pi@raspberrypi:~ $ showlog
>
> Jul  8 11:28:07 raspberrypi weewx[6484] DEBUG weewx.drivers.vantage:
> Getting archive packets since 2021-07-08
> 06
>   :20:00 BST (1625721600)
>
> Jul  8 11:28:07 raspberrypi weewx[6484] DEBUG weewx.drivers.vantage:
> Gentle wake up of console successful
>
> Jul  8 11:28:09 raspberrypi weewx[6484] DEBUG weewx.drivers.vantage:
> Retrieving 12 page(s); starting index= 1
>
> Jul  8 11:28:09 raspberrypi weewx[6484] DEBUG weewx.drivers.vantage:
> DMPAFT complete: page timestamp
> 2021-07-07
>10:50:00 BST
> (1625651400) less than final timestamp 2021-07-08 06:20:00 BST (1625721600)
>
> Jul  8 11:28:09 raspberrypi weewx[6484] DEBUG weewx.drivers.vantage: Catch
> up complete.
>
> Jul  8 11:28:09 raspberrypi weewx[6484] INFO weewx.engine: Starting main
> packet loop.
>
> Jul  8 11:28:10 raspberrypi weewx[6484] DEBUG weewx.drivers.vantage:
> Gentle wake up of console successful
>
> Jul  8 11:28:11 raspberrypi weewx[6484] DEBUG weewx.drivers.vantage:
> Requesting 200 LOOP packets.
>
> Jul  8 11:28:11 raspberrypi weewx[6484] DEBUG weewx.drivers.vantage:
> Gentle wake up of console successful
>
> Jul  8 11:28:13 raspberrypi kernel: [12270.030958] [UFW BLOCK] IN=wlan0
> OUT= MAC=01:00:5e:00:00:fb:6e:a5:b7:f8:4
>   
>   
>  a:c3:08:00
> SRC=192.168.0.36 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=20067
> PROTO=2
>
> Jul  8 11:28:20 raspberrypi kernel: [12276.686821] [UFW BLOCK] IN=wlan0
> OUT=
> MAC=01:00:5e:00:00:01:e4:57:40:c2:d
>
> 3:72:08:00
> SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PR

Re: [weewx-user] Settings to change after IP address of Vantage changes

[David Hindley]

Gary

Many thanks for your reply.

The log of what happened when I did as you suggest is below.  I have
included my attempts to kill the weewx PIDs at the start.  There is less
than 10mins, as my network crashed half way through (this intermitten
crashing is what caused me to change my router set up and hence the IP
address of the Davis Vantage Pro2 and hence the issues described here).  At
least this now appears to only show one weewx PID, as far as I can see.
Any further help you can give would be really appreciated.

pi@raspberrypi:~ $ sudo systemctl stop weewx

pi@raspberrypi:~ $ ps -aux|grep weewx

pi6438  0.0  0.0   4368   552 pts/0S+   11:23   0:00 grep
--color=au
 to weewx

pi@raspberrypi:~ $ kill -9 6438

-bash: kill: (6438) - No such process

pi@raspberrypi:~ $ kill -9 4368

-bash: kill: (4368) - No such process

pi@raspberrypi:~ $ ps -aux|grep weewx

pi6457  0.0  0.0   4368   564 pts/0S+   11:26   0:00 grep
--color=auto weewx

pi@raspberrypi:~ $ kill -9 6457

-bash: kill: (6457) - No such process

pi@raspberrypi:~ $ sudo systemctl start weewx

pi@raspberrypi:~ $ ps -aux|grep weewx

root  6484  1.0  1.0  15452  9660 ?S11:27   0:00 python2
/usr/share/weewx/weewxd --daemon
--pidf
ile=/var/run/weewx.pid
/etc/weewx/weewx.conf

pi6489  0.0  0.0   4368   544 pts/0S+   11:28   0:00 grep
--color=auto weewx

pi@raspberrypi:~ $ showlog

Jul  8 11:28:07 raspberrypi weewx[6484] DEBUG weewx.drivers.vantage:
Getting archive packets since 2021-07-08
06
  :20:00 BST (1625721600)

Jul  8 11:28:07 raspberrypi weewx[6484] DEBUG weewx.drivers.vantage: Gentle
wake up of console successful

Jul  8 11:28:09 raspberrypi weewx[6484] DEBUG weewx.drivers.vantage:
Retrieving 12 page(s); starting index= 1

Jul  8 11:28:09 raspberrypi weewx[6484] DEBUG weewx.drivers.vantage: DMPAFT
complete: page timestamp
2021-07-07
   10:50:00 BST
(1625651400) less than final timestamp 2021-07-08 06:20:00 BST (1625721600)

Jul  8 11:28:09 raspberrypi weewx[6484] DEBUG weewx.drivers.vantage: Catch
up complete.

Jul  8 11:28:09 raspberrypi weewx[6484] INFO weewx.engine: Starting main
packet loop.

Jul  8 11:28:10 raspberrypi weewx[6484] DEBUG weewx.drivers.vantage: Gentle
wake up of console successful

Jul  8 11:28:11 raspberrypi weewx[6484] DEBUG weewx.drivers.vantage:
Requesting 200 LOOP packets.

Jul  8 11:28:11 raspberrypi weewx[6484] DEBUG weewx.drivers.vantage: Gentle
wake up of console successful

Jul  8 11:28:13 raspberrypi kernel: [12270.030958] [UFW BLOCK] IN=wlan0
OUT= MAC=01:00:5e:00:00:fb:6e:a5:b7:f8:4


   a:c3:08:00
SRC=192.168.0.36 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=20067
PROTO=2

Jul  8 11:28:20 raspberrypi kernel: [12276.686821] [UFW BLOCK] IN=wlan0
OUT=
MAC=01:00:5e:00:00:01:e4:57:40:c2:d

3:72:08:00
SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=15562
PROTO=2

Jul  8 11:28:22 raspberrypi kernel: [12278.325287] [UFW BLOCK] IN=wlan0
OUT=
MAC=01:00:5e:00:00:fb:78:3e:53:b8:e
8:3a:08:00 SRC=192.168.0.46 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0xC0 TTL=1
ID=0 DF PROTO=2

Jul  8 11:28:46 raspberrypi kernel: [12302.786362] [UFW BLOCK] IN=wlan0
OUT=
MAC=b8:27:eb:6b:80:28:9c:b6:d0:92:2

9:4d:08:00
SRC=192.168.0.55 DST=192.168.0.24 LEN=141 TOS=0x00 PREC=0x00 TTL=128
ID=61860 PROTO=UDP SPT=57456 DPT


  =161
LEN=121

Jul  8 11:28:56 raspberrypi kernel: [12312.939246] [UFW BLOCK] IN=wlan0
OUT=
MAC=01:00:5e:00:00:fb:6e:a5:b7:f8:4
a:c3:08:00 SRC=192.168.0.36 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1
ID=64763 PROTO=2

Jul  8 11:29:01 raspberrypi weewx[6484] ERROR weewx.drivers.vantage:
ip-read error: timed out

Jul  8 11:29:01 raspberrypi weewx[6484] ERROR weewx.drivers.vantage: LOOP
try #1; error: timed out

Jul  8 11:29:08 raspberrypi weewx[6484] DEBUG weewx.restx: Wunderground-RF:
Failed upload attempt 1: 

Jul  8 11:29:08 raspberrypi weewx[6484] ERROR weewx.restx: Wunderground-RF:
Failed to publish record
2021-07-08
  11:28:12 BST (1625740092): Failed upload after 1 tries

Jul  8 11:29:08 raspberrypi weewxd: restx: MQTT: Failed upload attempt 1:
[Errno -3] Temporary failure in name
r


esolution

Jul  8 11:29:27 raspberrypi kernel: [12343.247930] [UFW BLOCK] IN=wlan0
OUT= MAC=01:00:5e:00:00:01:e4:57:40:c2:d3:72:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=32 TOS=0x00
PR
EC=0xC0 TTL=1 ID=15565 PROTO=2

Jul  8 11:29:27 raspberrypi kernel: [12343.759989] [UFW BLOCK] IN=wlan0
OUT= MAC=01:00:5e:00:00:fb:00:90:a9:dd:b8:41:08:00 SRC=192.168.0.56
DST=224.0.0.251 LEN=32
TOS=0x00
  PREC=0xC0 TTL=1 ID=0 DF PROTO=2

Jul  8 11:29:42 raspberrypi kernel: [12358.096314] [UFW BLOCK] IN=wlan0
OUT= MAC=01:00:5e:00:00:fb:6e:a5:b7:f8:4a:c3:08:00 SRC=192.168.0

Re: [weewx-user] Settings to change after IP address of Vantage changes

[David Hindley]

Thanks for the suggestion.  Tried that and still getting the same error -
could it be something to do with my basic network setup, as getting a lot
of UFW from local IP addresses, as per below (192.168.0.24 is the IP
address I have reserved for my RPi in my router)?

Jul  7 10:41:09 raspberrypi kernel: [  481.832211] [UFW BLOCK] IN=wlan0
OUT= MAC=b8:27:eb:6b:80:28:9c:b6:d0:92:29:4d:08:00 SRC=192.168.0.21
DST=192.168.0.24 LEN=141 TOS=0x00 PREC=0x00 TTL=128 ID=40085 PROTO=UDP
SPT=57285 DPT=161 LEN=121
Jul  7 10:41:30 raspberrypi kernel: [  503.033320] [UFW BLOCK] IN=wlan0
OUT= MAC=01:00:5e:00:00:01:e4:57:40:c2:d3:72:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=20070 PROTO=2
Jul  7 10:41:30 raspberrypi kernel: [  503.100239] [UFW BLOCK] IN=wlan0
OUT= MAC=01:00:5e:00:00:fb:00:05:cd:7f:92:10:08:00 SRC=192.168.0.51
DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
Jul  7 10:41:39 raspberrypi kernel: [  511.985208] [UFW BLOCK] IN=wlan0
OUT= MAC=01:00:5e:00:00:fb:9c:b6:d0:92:29:4d:08:00 SRC=192.168.0.21
DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=37440 PROTO=2

Any help anyone can give would be much appreciated.

Thanks

On Wed, 7 Jul 2021 at 17:19, Les Niles  wrote:

> Do you have multiple instances of weewx running?  That number enclosed in
> ‘[]’ after ‘weewx’ in the log messages should be the process ID; there are
> 3 different PIDs intermixed in your log.  Run “ps uax | grep weewx” — there
> should be exactly one instance of python running weewxd.  A reboot will
> probably fix it.
>
>   -Les
>
>
>
> On 7 Jul 2021, at 7:09, Doug Jenkins  wrote:
>
> Have you tried to put the the new IP address in the [MQTT] section of the
> weewx.conf file? I see this error which leads me to believe your DNS is
> still pointed to the old IP address of your former network
>
> Jul  7 11:04:16 raspberrypi weewxd: restx: MQTT: Failed upload attempt 1:
> [Errno -3] Temporary failure in name resolution
>
> On Wednesday, July 7, 2021 at 8:06:52 AM UTC-4 david_h wrote:
>
>> Hi - I recently changed my home network set up, which meant the IP
>> address of my Davis Vantage Pro 2 changed.  I am using an IPlogger. I
>> changed the setting of "host" in weewx.conf to the new IP address, but my
>> system doesn't seem to be working.  Have I missed some other setting that I
>> need to change.  I use the Belchertown skin (with a MQTT broker on a remote
>> server), but can't see anything in the skin configuration file that
>> references the IP address. Am I missing something.  The log file is shown
>> below.  Any help in solving this would be much appreciated.
>>
>> Jul  7 11:03:26 raspberrypi weewx[1716] DEBUG weewx.drivers.vantage:
>> Driver
>> vers
>>  ion is 3.2.2
>>
>> Jul  7 11:03:26 raspberrypi weewx[1716] DEBUG weewx.drivers.vantage:
>> Option
>> loop
>>  _request=1
>>
>> Jul  7 11:03:26 raspberrypi weewx[1716] DEBUG weewx.drivers.vantage:
>> Opened up
>> e
>>  
>> thernet
>> host 192.168.0.28 on port 2. timeout=4.0, tcp_send_delay=0.5
>>
>> Jul  7 11:03:26 raspberrypi kernel: [ 1818.633379] [UFW BLOCK] IN=eth0
>> OUT=
>> MAC=
>>01:00:5e:00:00:fb:90:21:06:46:88:f9:08:00:46:c0:00:20:00:00:40:00
>> SRC=10.0.1.200
>>  
>> DST=224.0.0.251
>> LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
>>
>> Jul  7 11:03:26 raspberrypi weewx[1128] ERROR weewx.drivers.vantage:
>> ip-read err
>>  
>>  
>> or:
>> timed out
>>
>> Jul  7 11:03:26 raspberrypi weewx[1128] ERROR weewx.drivers.vantage: LOOP
>> try
>> #4
>>  ; error: timed out
>>
>> Jul  7 11:03:26 raspberrypi weewx[1128] ERROR weewx.drivers.vantage: LOOP
>> max
>> tr
>>  
>> ies
>> (4) exceeded.
>>
>> Jul  7 11:03:26 raspberrypi weewx[1128] INFO weewx.engine: Main loop
>> exiting. Sh
>>  
>>  
>>   utting
>> engine down.
>>
>> Jul  7 11:03:27 raspberrypi weewx[1716] DEBUG weewx.drivers.vantage: Rude
>> wake
>> u
>>  p of console successful
>>
>> Jul  7 11:03:28 raspberrypi weewx[1716] DEBUG weewx.drivers.vantage:
>> Hardware
>> ty
>>  
>>  pe
>> is 16
>>
>> Jul  7 11:03:29 raspberrypi weewx[1509] ERROR weewx.drivers.vantage:
>> ip-read
>> err
>>  

Re: [weewx-user] Re: Settings to change after IP address of Vantage changes

[David Hindley]

The MQTT section of the conf file doesn’t have any IP assesses listed, so
this doesn’t seem to be the problem. It has a server_url but I presume that
wouldn’t change as a result of the new IP address?

Thanks

David.

On Wed, 7 Jul 2021 at 15:09, Doug Jenkins  wrote:

> Have you tried to put the the new IP address in the [MQTT] section of the
> weewx.conf file? I see this error which leads me to believe your DNS is
> still pointed to the old IP address of your former network
>
> Jul  7 11:04:16 raspberrypi weewxd: restx: MQTT: Failed upload attempt 1:
> [Errno -3] Temporary failure in name resolution
>
> On Wednesday, July 7, 2021 at 8:06:52 AM UTC-4 david_h wrote:
>
>> Hi - I recently changed my home network set up, which meant the IP
>> address of my Davis Vantage Pro 2 changed.  I am using an IPlogger. I
>> changed the setting of "host" in weewx.conf to the new IP address, but my
>> system doesn't seem to be working.  Have I missed some other setting that I
>> need to change.  I use the Belchertown skin (with a MQTT broker on a remote
>> server), but can't see anything in the skin configuration file that
>> references the IP address. Am I missing something.  The log file is shown
>> below.  Any help in solving this would be much appreciated.
>>
>> Jul  7 11:03:26 raspberrypi weewx[1716] DEBUG weewx.drivers.vantage:
>> Driver
>> vers
>>  ion is 3.2.2
>>
>> Jul  7 11:03:26 raspberrypi weewx[1716] DEBUG weewx.drivers.vantage:
>> Option
>> loop
>>  _request=1
>>
>> Jul  7 11:03:26 raspberrypi weewx[1716] DEBUG weewx.drivers.vantage:
>> Opened up
>> e
>>  
>> thernet
>> host 192.168.0.28 on port 2. timeout=4.0, tcp_send_delay=0.5
>>
>> Jul  7 11:03:26 raspberrypi kernel: [ 1818.633379] [UFW BLOCK] IN=eth0
>> OUT=
>> MAC=
>>01:00:5e:00:00:fb:90:21:06:46:88:f9:08:00:46:c0:00:20:00:00:40:00
>> SRC=10.0.1.200
>>  
>> DST=224.0.0.251
>> LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
>>
>> Jul  7 11:03:26 raspberrypi weewx[1128] ERROR weewx.drivers.vantage:
>> ip-read err
>>  
>>  
>> or:
>> timed out
>>
>> Jul  7 11:03:26 raspberrypi weewx[1128] ERROR weewx.drivers.vantage: LOOP
>> try
>> #4
>>  ; error: timed out
>>
>> Jul  7 11:03:26 raspberrypi weewx[1128] ERROR weewx.drivers.vantage: LOOP
>> max
>> tr
>>  
>> ies
>> (4) exceeded.
>>
>> Jul  7 11:03:26 raspberrypi weewx[1128] INFO weewx.engine: Main loop
>> exiting. Sh
>>  
>>  
>>   utting
>> engine down.
>>
>> Jul  7 11:03:27 raspberrypi weewx[1716] DEBUG weewx.drivers.vantage: Rude
>> wake
>> u
>>  p of console successful
>>
>> Jul  7 11:03:28 raspberrypi weewx[1716] DEBUG weewx.drivers.vantage:
>> Hardware
>> ty
>>  
>>  pe
>> is 16
>>
>> Jul  7 11:03:29 raspberrypi weewx[1509] ERROR weewx.drivers.vantage:
>> ip-read
>> err
>>  
>>  
>>   or:
>> timed out
>>
>> Jul  7 11:03:29 raspberrypi weewx[1509] ERROR weewx.drivers.vantage: LOOP
>> try #1
>>  
>>  
>>  
>> ;
>> error: timed out
>>
>> Jul  7 11:03:31 raspberrypi weewx[1716] DEBUG weewx.drivers.vantage: ISS
>> ID is 1
>>
>> Jul  7 11:03:31 raspberrypi weewx[1716] DEBUG weewx.drivers.vantage:
>> Hardware name: Vantage Pro2
>>
>> Jul  7 11:03:31 raspberrypi weewx[1716] DEBUG weewx.engine: Loading
>> service weewx.engine.StdTimeSynch
>>
>> Jul  7 11:03:31 raspberrypi weewx[1716] DEBUG weewx.engine: Finished
>> loading service weewx.engine.StdTimeSynch
>>
>> Jul  7 11:03:31 raspberrypi weewx[1716] DEBUG weewx.engine: Loading
>> service weewx.engine.StdConvert
>>
>> Jul  7 11:03:31 raspberrypi weewx[1716] INFO weewx.engine: StdConvert
>> target unit is 0x1
>>
>> Jul  7 11:03:31 raspberrypi weewx[1716] DEBUG weewx.engine: Finished
>> loading service weewx.engine.StdConvert
>>
>> Jul  7 11:03:31 raspberrypi weewx[1716] DEBUG weewx.engine: Loading
>> 

Re: [weewx-user] Upgrade problems?

[David Hindley]

OK.  Thanks, anyway.

David.

On Mon, 30 Nov 2020 at 19:41, Tom Keffer  wrote:

> It was no tip: it was right there in the error message.
>
> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL __main__:
> Unable to load driver: [Errno 101] Network is unreachable
>
> -tk
>
> On Mon, Nov 30, 2020 at 9:45 AM David Hindley 
> wrote:
>
>> Solved!!  I had to disconnect the Davis Console from power, remove the
>> batteries, disconnect the Ethernet cable from the console, reconnect and
>> repower. Then the router found the logger again and restarting weewx got it
>> working again. Many thanks for your tip about the port.
>>
>> David.
>>
>> On Mon, 30 Nov 2020 at 17:30, David Hindley 
>> wrote:
>>
>>> When I go into the WeatherLink software, and select Comms Port, Find it
>>> cannot find the device, so something is obviously wrong wi TV the basic set
>>> up.  Any ideas please?
>>>
>>> Many Thanks
>>>
>>> David.
>>>
>>> On Mon, 30 Nov 2020 at 16:50, David Hindley 
>>> wrote:
>>>
>>>> Tom
>>>>
>>>> Many Thanks for your prompt reply.
>>>>
>>>> Yes, it’s a WeatherLinkIP. What port would have been closed and how do
>>>> I reopen it?
>>>>
>>>> Thanks.
>>>>
>>>> David.
>>>>
>>>> On Mon, 30 Nov 2020 at 16:36, Tom Keffer  wrote:
>>>>
>>>>> What kind of logger does your Vantage have? If it's a weatherlinkIP,
>>>>> it's a network issue. Perhaps your upgrade closed a port?
>>>>>
>>>>> On Mon, Nov 30, 2020 at 8:21 AM david_h 
>>>>> wrote:
>>>>>
>>>>>> Weewx has stopped working and I think it might be due to me recently
>>>>>> upgrading via DEB.
>>>>>>
>>>>>> When I look at the service status I get:
>>>>>>
>>>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>>>> weewx.engine:   return VantageService(engine, config_dict)
>>>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>>>> weewx.engine: File 
>>>>>> "/usr/share/weewx/weewx/drivers/vantage.py",
>>>>>> line 1898, in __init__
>>>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>>>> weewx.engine:   Vantage.__init__(self,
>>>>>> **config_dict[DRIVER_NAME])
>>>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>>>> weewx.engine: File 
>>>>>> "/usr/share/weewx/weewx/drivers/vantage.py",
>>>>>> line 512, in __init__
>>>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>>>> weewx.engine:   self.port.openPort()
>>>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>>>> weewx.engine: File 
>>>>>> "/usr/share/weewx/weewx/drivers/vantage.py",
>>>>>> line 344, in openPort
>>>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>>>> weewx.engine:   raise weewx.WeeWxIOError(ex)
>>>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>>>> weewx.engine:   WeeWxIOError: [Errno 101] Network is unreachable
>>>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>>>> __main__: Unable to load driver: [Errno 101] Network is unreachable
>>>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>>>> __main__:   Exiting...
>>>>>>
>>>>>> Any ideas what is causing the above please?  I opted to retain the
>>>>>> existing weewx.conf file, as I use the belchertown skin (an old version 
>>>>>> of
>>>>>> that, I think).
>>>>>>
>>>>>> Many thanks
>>>>>>
>>>>>> David.
>>>>>>
>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "weewx-user" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>> send an email to weewx-user+unsubscr...@googlegroups.com.
>>

Re: [weewx-user] Upgrade problems?

[David Hindley]

Solved!!  I had to disconnect the Davis Console from power, remove the
batteries, disconnect the Ethernet cable from the console, reconnect and
repower. Then the router found the logger again and restarting weewx got it
working again. Many thanks for your tip about the port.

David.

On Mon, 30 Nov 2020 at 17:30, David Hindley  wrote:

> When I go into the WeatherLink software, and select Comms Port, Find it
> cannot find the device, so something is obviously wrong wi TV the basic set
> up.  Any ideas please?
>
> Many Thanks
>
> David.
>
> On Mon, 30 Nov 2020 at 16:50, David Hindley 
> wrote:
>
>> Tom
>>
>> Many Thanks for your prompt reply.
>>
>> Yes, it’s a WeatherLinkIP. What port would have been closed and how do I
>> reopen it?
>>
>> Thanks.
>>
>> David.
>>
>> On Mon, 30 Nov 2020 at 16:36, Tom Keffer  wrote:
>>
>>> What kind of logger does your Vantage have? If it's a weatherlinkIP,
>>> it's a network issue. Perhaps your upgrade closed a port?
>>>
>>> On Mon, Nov 30, 2020 at 8:21 AM david_h  wrote:
>>>
>>>> Weewx has stopped working and I think it might be due to me recently
>>>> upgrading via DEB.
>>>>
>>>> When I look at the service status I get:
>>>>
>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>> weewx.engine:   return VantageService(engine, config_dict)
>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>> weewx.engine: File "/usr/share/weewx/weewx/drivers/vantage.py",
>>>> line 1898, in __init__
>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>> weewx.engine:   Vantage.__init__(self,
>>>> **config_dict[DRIVER_NAME])
>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>> weewx.engine: File "/usr/share/weewx/weewx/drivers/vantage.py",
>>>> line 512, in __init__
>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>> weewx.engine:   self.port.openPort()
>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>> weewx.engine: File "/usr/share/weewx/weewx/drivers/vantage.py",
>>>> line 344, in openPort
>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>> weewx.engine:   raise weewx.WeeWxIOError(ex)
>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>> weewx.engine:   WeeWxIOError: [Errno 101] Network is unreachable
>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL __main__:
>>>> Unable to load driver: [Errno 101] Network is unreachable
>>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>>> __main__:   Exiting...
>>>>
>>>> Any ideas what is causing the above please?  I opted to retain the
>>>> existing weewx.conf file, as I use the belchertown skin (an old version of
>>>> that, I think).
>>>>
>>>> Many thanks
>>>>
>>>> David.
>>>>
>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "weewx-user" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to weewx-user+unsubscr...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/weewx-user/a01bf34e-fd56-4e73-9e0b-92862eaa45f4n%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/weewx-user/a01bf34e-fd56-4e73-9e0b-92862eaa45f4n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/weewx-user/nhQtoByAgmQ/unsubscribe.
>>> To unsubscribe from this group and all its topics, 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/CAPq0zECyE4pRxnqxNVc3eB72X_NKUP5AVPLEjrpk_3n_2p9U9Q%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/weewx-user/CAPq0zECyE4pRxnqxNVc3eB72X_NKUP5AVPLEjrpk_3n_2p9U9Q%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
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/CAKbmhJQ5bj3LpkXBe1Q9i0GuO6b%2Bg1rvXyuAp1dK7HVyLVA-mA%40mail.gmail.com.

Re: [weewx-user] Upgrade problems?

[David Hindley]

When I go into the WeatherLink software, and select Comms Port, Find it
cannot find the device, so something is obviously wrong wi TV the basic set
up.  Any ideas please?

Many Thanks

David.

On Mon, 30 Nov 2020 at 16:50, David Hindley  wrote:

> Tom
>
> Many Thanks for your prompt reply.
>
> Yes, it’s a WeatherLinkIP. What port would have been closed and how do I
> reopen it?
>
> Thanks.
>
> David.
>
> On Mon, 30 Nov 2020 at 16:36, Tom Keffer  wrote:
>
>> What kind of logger does your Vantage have? If it's a weatherlinkIP, it's
>> a network issue. Perhaps your upgrade closed a port?
>>
>> On Mon, Nov 30, 2020 at 8:21 AM david_h  wrote:
>>
>>> Weewx has stopped working and I think it might be due to me recently
>>> upgrading via DEB.
>>>
>>> When I look at the service status I get:
>>>
>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>> weewx.engine:   return VantageService(engine, config_dict)
>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>> weewx.engine: File "/usr/share/weewx/weewx/drivers/vantage.py",
>>> line 1898, in __init__
>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>> weewx.engine:   Vantage.__init__(self,
>>> **config_dict[DRIVER_NAME])
>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>> weewx.engine: File "/usr/share/weewx/weewx/drivers/vantage.py",
>>> line 512, in __init__
>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>> weewx.engine:   self.port.openPort()
>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>> weewx.engine: File "/usr/share/weewx/weewx/drivers/vantage.py",
>>> line 344, in openPort
>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>> weewx.engine:   raise weewx.WeeWxIOError(ex)
>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>>> weewx.engine:   WeeWxIOError: [Errno 101] Network is unreachable
>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL __main__:
>>> Unable to load driver: [Errno 101] Network is unreachable
>>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL __main__:
>>>  Exiting...
>>>
>>> Any ideas what is causing the above please?  I opted to retain the
>>> existing weewx.conf file, as I use the belchertown skin (an old version of
>>> that, I think).
>>>
>>> Many thanks
>>>
>>> David.
>>>
>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx-user+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/a01bf34e-fd56-4e73-9e0b-92862eaa45f4n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/a01bf34e-fd56-4e73-9e0b-92862eaa45f4n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/weewx-user/nhQtoByAgmQ/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/CAPq0zECyE4pRxnqxNVc3eB72X_NKUP5AVPLEjrpk_3n_2p9U9Q%40mail.gmail.com
>> <https://groups.google.com/d/msgid/weewx-user/CAPq0zECyE4pRxnqxNVc3eB72X_NKUP5AVPLEjrpk_3n_2p9U9Q%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/CAKbmhJSYm4%2BUA7cf_19LWVVQW45H5KG3gS4y4xb%3DXkQ5yZYZ6Q%40mail.gmail.com.

Re: [weewx-user] Upgrade problems?

[David Hindley]

Tom

Many Thanks for your prompt reply.

Yes, it’s a WeatherLinkIP. What port would have been closed and how do I
reopen it?

Thanks.

David.

On Mon, 30 Nov 2020 at 16:36, Tom Keffer  wrote:

> What kind of logger does your Vantage have? If it's a weatherlinkIP, it's
> a network issue. Perhaps your upgrade closed a port?
>
> On Mon, Nov 30, 2020 at 8:21 AM david_h  wrote:
>
>> Weewx has stopped working and I think it might be due to me recently
>> upgrading via DEB.
>>
>> When I look at the service status I get:
>>
>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>> weewx.engine:   return VantageService(engine, config_dict)
>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>> weewx.engine: File "/usr/share/weewx/weewx/drivers/vantage.py",
>> line 1898, in __init__
>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>> weewx.engine:   Vantage.__init__(self,
>> **config_dict[DRIVER_NAME])
>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>> weewx.engine: File "/usr/share/weewx/weewx/drivers/vantage.py",
>> line 512, in __init__
>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>> weewx.engine:   self.port.openPort()
>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>> weewx.engine: File "/usr/share/weewx/weewx/drivers/vantage.py",
>> line 344, in openPort
>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>> weewx.engine:   raise weewx.WeeWxIOError(ex)
>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL
>> weewx.engine:   WeeWxIOError: [Errno 101] Network is unreachable
>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL __main__:
>> Unable to load driver: [Errno 101] Network is unreachable
>> Nov 30 15:27:12 raspberrypi python2[487]: weewx[487] CRITICAL __main__:
>>  Exiting...
>>
>> Any ideas what is causing the above please?  I opted to retain the
>> existing weewx.conf file, as I use the belchertown skin (an old version of
>> that, I think).
>>
>> Many thanks
>>
>> David.
>>
> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/a01bf34e-fd56-4e73-9e0b-92862eaa45f4n%40googlegroups.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/nhQtoByAgmQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAPq0zECyE4pRxnqxNVc3eB72X_NKUP5AVPLEjrpk_3n_2p9U9Q%40mail.gmail.com
> 
> .
>

-- 
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/CAKbmhJSWdnu2eSwJKWuUG3WVdSq2_YD-MPj-udeJT1U3H3HvEg%40mail.gmail.com.

Re: [weewx-user] Re: No updates since 2am start of British Summer Time

[David Hindley]

Not sure, but after using  —dump, the system updated itself to show the
current day as today (2 April) rather than 31 March.

David.

On Tue, 2 Apr 2019 at 19:28, Geoff Cusick  wrote:

> Do I infer that the —dump option failed immediately, and didn’t download
> any records?
>
> Geoff
>
> 17 Westcroft Road Holsworthy, EX22 6BY
> 
> Phone: +44 (0)1409 254330
> Mobile: +44 (0)7976 285950
> Web: http://www.cusick.org.uk
>
> On 2 Apr 2019, at 17:07, hindle...@gmail.com wrote:
>
> I had the same problem, but only noticed it today.  I used the solution
> suggested here, which correctly reset the system, so many thanks for the
> suggestion.  However, my NOAA reports are missing 1 April - which is
> strange, as I would presume that data would have been in the logger.  I
> also got the following errors when I did the wee_device dump command:
>
> root@raspberrypi:/home/pi# wee_device --dump
> Using configuration file /etc/weewx/weewx.conf
> Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
> Proceeding will dump all data in the logger.
> Are you sure you want to proceed (y/n)? y
> Starting dump ...
>  Traceback (most recent call last): 2019-03-25 05:10:00 GMT (1553490600)
>   File "/usr/bin/wee_device", line 66, in 
> main()
>   File "/usr/bin/wee_device", line 62, 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 2016, in
> do_options
> self.dump_logger(station, config_dict, options.noprompt)
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 2616, in
> dump_logger
> for record in converted_generator:
>   File "/usr/share/weewx/weewx/units.py", line 1247, in next
> _record = self.input_generator.next()
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 659, in
> genArchiveDump
> _page = self.port.get_data_with_crc16(267, prompt=_ack,
> max_tries=self.max_tries)
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 206, in
> get_data_with_crc16
> raise weewx.CRCError("Unable to pass CRC16 check while getting data")
> weewx.CRCError: Unable to pass CRC16 check while getting data
>
>
> I didn't do the wee_device clear, just in case I am able to get back the
> missing 1 April data from the logger.
>
> Any ideas on how I get back the missing 1 April data from the logger?
>
> Thanks
>
> David.
>
>
>
> On Tuesday, 2 April 2019 12:21:24 UTC+1, Phil Owers wrote:
>>
>> As an update, my second rpi although it failed clear memory and dump
>> commands must have done some good as it started working again shortly after
>> i did the dump command. Phil O
>>
>> On Mon, 1 Apr 2019, 16:55 Phil Green,  wrote:
>>
>>> Hi
>>> Why do you need to do a ‘dump’ command when you do the clear-memory?
>>>
>>> Yes would be interested in a cron script.
>>> I presume the same one to be run twice a year when the clocks change
>>> forwards & backwards?
>>> Regards
>>> Phil
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/F4w4LutBHLk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/F4w4LutBHLk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [weewx-user] Re: Showing message to weather website users when stopped working

[David Hindley]

Thanks for your reply, Tom - much appreciated.

I have removed the fake clock (pending purchase of a RTC) and made the
change to the file in init.d and restarted weewx with a working network and
all seems OK, but I guess I won't know fully until the Pi crashes again.

David.

On Thu, 28 Feb 2019 at 13:32, Thomas Keffer  wrote:

> 1. It looks like you're using the WeatherLinkIP logger in your Vantage.
> These are generally not as reliable as the serial and USB versions and, as
> you discovered, depend on the network being up before the Vantage is useful.
>
> I am not a boot expert, but try this: go into /etc/init.d/weewx and
> change this
>
> ### BEGIN INIT INFO
> # Provides:  weewx
> # Required-Start:$local_fs $remote_fs $syslog $time
> # Required-Stop: $local_fs $remote_fs $syslog
> # Default-Start: 2 3 4 5
> # Default-Stop:  0 1 6
> # Short-Description: weewx weather system
> # Description:   Manages the weewx weather system
> ### END INIT INFO
>
>
> to this
>
> ### BEGIN INIT INFO
> # Provides:  weewx
> # Required-Start:$local_fs $remote_fs $syslog $networking $time
> # Required-Stop: $local_fs $remote_fs $syslog
> # Default-Start: 2 3 4 5
> # Default-Stop:  0 1 6
> # Short-Description: weewx weather system
> # Description:   Manages the weewx weather system
> ### END INIT INFO
>
> This says that the system should not run WeeWX until the network is up.
> What I'm not sure of is how Debian defines "up." Worth a try.
>
> 2. The clock must also be set. Either use a hardware real time clock
> (RTC), or remove the "fake clock" by following these directions
> <https://github.com/weewx/weewx/wiki/Raspberry-Pi#b-remove-the-fake-clock>
> .
>
> On Thu, Feb 28, 2019 at 3:57 AM David Hindley  wrote:
>
>> Many Thanks.
>>
>> 1.  I will do as you suggest re separate log files.
>>
>> 3. The cron task was something I had to add after installing the
>> belchertown skin, just to copy some files from one directory to another, on
>> the Rpi, before then using sftp to upload to my website. It seems to work
>> most of the time, but, as you say, this seemed to be when the corruption
>> occurred.  The CRON job works every five minutes at 1,6,11... minutes past
>> each hour - on the basis that weewx should have updated the archive etc by
>> then - maybe that is something to do with it.
>>
>> 4. Further down the log file, I see:
>>
>> Feb 27 15:17:04 raspberrypi weewx[379]: Starting weewx weather system:
>> weewxerror: unexpectedly disconnected from boot status daemon
>>
>> and then...
>>
>> Feb 27 15:17:05 raspberrypi weewx[423]: engine: Initializing weewx
>> version 3.9.1
>> Feb 27 15:17:05 raspberrypi weewx[423]: engine: Using Python 2.7.13
>> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
>> Feb 27 15:17:05 raspberrypi weewx[423]: engine: Platform
>> Linux-4.14.79-v7+-armv7l-with-debian-9.6
>> Feb 27 15:17:05 raspberrypi weewx[423]: engine: Locale is 'en_GB.UTF-8'
>> Feb 27 15:17:05 raspberrypi weewx[423]: engine: pid file is
>> /var/run/weewx.pid
>> Feb 27 15:17:05 raspberrypi weewx[467]: engine: Using configuration file
>> /etc/weewx/weewx.conf
>> Feb 27 15:17:05 raspberrypi weewx[467]: engine: Debug is 1
>> Feb 27 15:17:05 raspberrypi weewx[379]: .
>> Feb 27 15:17:05 raspberrypi systemd[1]: Started LSB: weewx weather system.
>> Feb 27 15:17:05 raspberrypi weewx[467]: engine: Initializing engine
>> Feb 27 15:17:05 raspberrypi weewx[467]: engine: Loading station type
>> Vantage (weewx.drivers.vantage)
>> Feb 27 15:17:06 raspberrypi weewx[467]: vantage: Driver version is 3.1.1
>> Feb 27 15:17:06 raspberrypi weewx[467]: vantage: Socket error while
>> opening port 2 to ethernet host 10.0.1.83.
>> Feb 27 15:17:06 raspberrypi weewx[467]: import of driver failed: [Errno
>> 101] Network is unreachable ()
>> Feb 27 15:17:06 raspberrypi weewx[467]: engine: Unable to load driver:
>> [Errno 101] Network is unreachable
>> Feb 27 15:17:06 raspberrypi weewx[467]:   Exiting...
>>
>> So, looks like the internet connection went down perhaps? (I was away
>> when all this happened yesterday, so not sure)
>>
>> Good point re making sure weewx doesn't restart until it has a sensible
>> time via valid NTP connection - any idea how I do that?  I will order an
>> RTC anyway I think.
>>
>> Thanks
>>
>> David.
>>
>> On Thu, 28 Feb 2019 at 11:25, Andrew Milner 
>> wrote:
>>
>>> 1.  I recommend you put weewx log messages in their own log f

Re: [weewx-user] Re: Showing message to weather website users when stopped working

[David Hindley]

Many Thanks.

1.  I will do as you suggest re separate log files.

3. The cron task was something I had to add after installing the
belchertown skin, just to copy some files from one directory to another, on
the Rpi, before then using sftp to upload to my website. It seems to work
most of the time, but, as you say, this seemed to be when the corruption
occurred.  The CRON job works every five minutes at 1,6,11... minutes past
each hour - on the basis that weewx should have updated the archive etc by
then - maybe that is something to do with it.

4. Further down the log file, I see:

Feb 27 15:17:04 raspberrypi weewx[379]: Starting weewx weather system:
weewxerror: unexpectedly disconnected from boot status daemon

and then...

Feb 27 15:17:05 raspberrypi weewx[423]: engine: Initializing weewx version
3.9.1
Feb 27 15:17:05 raspberrypi weewx[423]: engine: Using Python 2.7.13
(default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Feb 27 15:17:05 raspberrypi weewx[423]: engine: Platform
Linux-4.14.79-v7+-armv7l-with-debian-9.6
Feb 27 15:17:05 raspberrypi weewx[423]: engine: Locale is 'en_GB.UTF-8'
Feb 27 15:17:05 raspberrypi weewx[423]: engine: pid file is
/var/run/weewx.pid
Feb 27 15:17:05 raspberrypi weewx[467]: engine: Using configuration file
/etc/weewx/weewx.conf
Feb 27 15:17:05 raspberrypi weewx[467]: engine: Debug is 1
Feb 27 15:17:05 raspberrypi weewx[379]: .
Feb 27 15:17:05 raspberrypi systemd[1]: Started LSB: weewx weather system.
Feb 27 15:17:05 raspberrypi weewx[467]: engine: Initializing engine
Feb 27 15:17:05 raspberrypi weewx[467]: engine: Loading station type
Vantage (weewx.drivers.vantage)
Feb 27 15:17:06 raspberrypi weewx[467]: vantage: Driver version is 3.1.1
Feb 27 15:17:06 raspberrypi weewx[467]: vantage: Socket error while opening
port 2 to ethernet host 10.0.1.83.
Feb 27 15:17:06 raspberrypi weewx[467]: import of driver failed: [Errno
101] Network is unreachable ()
Feb 27 15:17:06 raspberrypi weewx[467]: engine: Unable to load driver:
[Errno 101] Network is unreachable
Feb 27 15:17:06 raspberrypi weewx[467]:   Exiting...

So, looks like the internet connection went down perhaps? (I was away when
all this happened yesterday, so not sure)

Good point re making sure weewx doesn't restart until it has a sensible
time via valid NTP connection - any idea how I do that?  I will order an
RTC anyway I think.

Thanks

David.

On Thu, 28 Feb 2019 at 11:25, Andrew Milner 
wrote:

> 1.  I recommend you put weewx log messages in their own log file - see
> wiki for a) separate logfile and also logrotation.
> 2.  The ^@ rubbish looks like possible corruption whilst executing a cron
> task
> 3.  What cron task was it trying to execute
> 4.  I see the clock has gone backwards around the rubbish point - implying
> the rpi has rebooted itself.  If that is the case you need to ensure that
> weewx does not restart again until it has a sensible time - or fit an RTC
> to your rpi
>
> All looks like some form of corruption - power supply perhaps or memory
> card problem which is then causing a pi reboot and should cause a weewx
> restart - but the log portion you posted does not run long enough to give
> weewx restart details and ensure it held off until it had a valid time and
> ntp connection.
>
>
>
> On Thursday, 28 February 2019 13:10:57 UTC+2, David Hindley wrote:
>>
>> Thanks.  I agree that it is probably the Raspberry Pi, rather than
>> weewx.  My syslog file around the relevant time that it stopped working
>> yesterday is as follows.  Does anyone have any idea how to interpret this?
>> The "^@" is very puzzling to a linux novice such as me!
>>
>> David.
>>
>> Feb 27 15:30:28 raspberrypi weewx[9312]: sftp: uploaded file
>> /belchertown/graphs/index.html
>> Feb 27 15:30:28 raspberrypi weewx[9312]: sftp: create remote directory
>> /belchertown/records
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
>> /belchertown/records/index.html
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
>> /belchertown/reports
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
>> /belchertown/reports/index.html
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
>> /belchertown/about
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
>> /belchertown/about/index.html
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
>> /belchertown/images
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
>> /reports
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
>> /reports/index.html
>> Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
>> /about
>> Feb 27 15:30:29 raspberrypi weewx[9312]

Re: [weewx-user] Re: Showing message to weather website users when stopped working

[David Hindley]

Thanks.  I agree that it is probably the Raspberry Pi, rather than weewx.
My syslog file around the relevant time that it stopped working yesterday
is as follows.  Does anyone have any idea how to interpret this? The "^@"
is very puzzling to a linux novice such as me!

David.

Feb 27 15:30:28 raspberrypi weewx[9312]: sftp: uploaded file
/belchertown/graphs/index.html
Feb 27 15:30:28 raspberrypi weewx[9312]: sftp: create remote directory
/belchertown/records
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
/belchertown/records/index.html
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
/belchertown/reports
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
/belchertown/reports/index.html
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
/belchertown/about
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
/belchertown/about/index.html
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
/belchertown/images
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
/reports
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
/reports/index.html
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
/about
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: uploaded file
/about/index.html
Feb 27 15:30:29 raspberrypi weewx[9312]: sftp: create remote directory
/images
Feb 27 15:30:30 raspberrypi weewx[9312]: sftpgenerator: transferred 34
files in 7.72 seconds
Feb 27 15:30:30 raspberrypi weewx[9312]: reportengine: Running report
'Highcharts_Belchertown'
Feb 27 15:30:30 raspberrypi weewx[9312]: reportengine: Found configuration
file /etc/weewx/skins/Highcharts_Belchertown/skin.conf for report
'Highcharts_Belchertown'
Feb 27 15:30:30 raspberrypi weewx[9312]: cheetahgenerator: using search
list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station',
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats',
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras',
'user.belchertown_highchartsSearchX.$
Feb 27 15:30:30 raspberrypi weewx[9312]: manager: Daily summary version is
2.0
Feb 27 15:30:44 raspberrypi weewx[9312]: cheetahgenerator: Generated 4
files for report Highcharts_Belchertown in 14.36 seconds
Feb 27 15:30:44 raspberrypi weewx[9312]: copygenerator: copied 0 files to
/var/www/html/weewx/belchertown
Feb 27 15:30:44 raspberrypi weewx[9312]: reportengine: Running report
'Belchertown'
Feb 27 15:30:44 raspberrypi weewx[9312]: reportengine: Found configuration
file /etc/weewx/skins/Belchertown/skin.conf for report 'Belchertown'
Feb 27 15:30:44 raspberrypi weewx[9312]: cheetahgenerator: using search
list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station',
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats',
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras',
'user.belchertown.getData']
Feb 27 15:30:44 raspberrypi weewx[9312]: manager: Daily summary version is
2.0
Feb 27 15:30:47 raspberrypi weewx[9312]: cheetahgenerator: Generated 12
files for report Belchertown in 3.13 seconds
Feb 27 15:30:47 raspberrypi weewx[9312]: copygenerator: copied 1 files to
/var/www/html/weewx/belchertown
Feb 27 15:30:47 raspberrypi weewx[9312]: reportengine: Running report 'FTP'
Feb 27 15:30:47 raspberrypi weewx[9312]: reportengine: Found configuration
file /etc/weewx/skins/Ftp/skin.conf for report 'FTP'
Feb 27 15:30:47 raspberrypi weewx[9312]: ftpgenerator: FTP upload not
requested. Skipped.
Feb 27 15:30:47 raspberrypi weewx[9312]: reportengine: Running report
'RSYNC'
Feb 27 15:30:47 raspberrypi weewx[9312]: reportengine: Found configuration
file /etc/weewx/skins/Rsync/skin.conf for report 'RSYNC'
Feb 27 15:30:47 raspberrypi weewx[9312]: rsyncgenerator: rsync upload not
requested. Skipped.
Feb 27 15:31:01 raspberrypi CRON[12528]: (pi) CMD (sudo cp -f
/var/www/html/weewx/belchertown/json/day.json
/var/www/html/weewx/belchertown/json/week.json
/var/www/html/weewx/belchertown/json/month.json
/var/www/html/weewx/belchertown/json/year.json /var/www/html/weewx/json)
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@$
Feb 27 15:17:04 raspberrypi kernel: [0.00] Booting Linux on
physical CPU 0x0
Feb 27 15:17:04 raspberrypi kernel: [0.00] Linux version
4.14.79-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG
crosstool-ng-1.22.0-88-g8460611)) #1159 SMP Sun Nov 4 17:50:20 GMT 2018
Feb 27 15:17:04 raspberrypi kernel: [0.00] CPU: ARMv7 Processor
[410fd034] revision 4 (ARMv7), cr=10c5383d
Feb 27 15:17:04 raspberrypi kernel: [0.00] CPU: div instructions
available: patching division code
Feb 27 15:17:04 raspberrypi kernel: [0.00] CPU: PIPT / VI

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[David Hindley]

Colin - where are these instructions please?

Thanks.

On Mon, 12 Nov 2018 at 21:10, Colin Larsen  wrote:

> I found your instructions on integrating new items into the same menu line
> as the existing items easy to follow and it looks good with it all in the
> same line. Otherwise my vote would be above the temp/radar
>
> On Tue, 13 Nov 2018, 10:06 Pat 
>> I could do that.
>>
>> Where in index do you think? Above the temperature/radar bar? Or above
>> the forecast bar? or above the graphs? So many options, it'll be hard to
>> make everyone happy...
>>
>> On Monday, November 12, 2018 at 1:39:36 PM UTC-5, Jonis Maurin Ceará
>> wrote:
>>>
>>> One sugestion: create an index.top.inc and index.bottom.inc, so users
>>> can include code at top and bottom of index pageuser's choice!
>>> Edit index.tmpl os easyI'm just avoiding because of updates, that I
>>> really don't want to lose. If is the case, I'll wait for at least version
>>> 0.8 and then edit I just want to include my WebCam image for now.
>>>
>>> Em seg, 12 de nov de 2018 às 11:54, Pat  escreveu:
>>>
>>> Hi everyone, I'm planning on releasing a 0.8 version very shortly which
>>> should contain a lot of fixes you guys have been looking for. No doubt
>>> it'll introduce some more bugs, but we'll work on them as they come up.
>>>
>>> To answer some questions from the last few weeks:
>>>
>>> Q: Juan had an error using Xiaomi Mi6 to display a graphic
>>> A: This seems like a UTF-8 decoding error maybe? Juan, can you paste
>>> what character it's trying to use? Do you know?
>>>
>>> Q: From Juan: I have configured to use the METRIC target unit, so the
>>> rain data is in mm. But I see that in the graphics it appears in cm. Can
>>> this be changed without modifying target_unit section?
>>> A; I think that this should be fixed in 0.8
>>>
>>> Q: From Paul: Is there a procedure to update the running belchertown
>>> skin 0.7 to the last version on the github ?
>>> A: No "offi
>>>
>>> ...
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-user+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/GSrKZEiPqsc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

[David Hindley]

Phil - you are a genius. Thank you so much.  Three brackets did it, and
www.ashteadweather.com is now live!! Not sure how I managed to get only two
brackets!  For some bizarre reason, however, the temperature readings are
now way off after making this change - showing temperature as oscillating
between 66.6 degC (a tad high) and 19.2 deg c (correct) here in autumnal
England - must be a units issues somewhere, which I will explore, but if
anyone has seen this before and knows how to fix it, please advise.

David.

On Fri, 12 Oct 2018 at 12:26, Philip Kutzenco  wrote:

> I may have found it.
>
> in weewx.conf, you have a stanza:
>
> [[tls]]
> tls_version = tlsv1
> ca_certs = /etc/ssl/certs/ca-certificates.crt
>
> It should be:
>
> [[[tls]]]
> tls_version = tlsv1
> ca_certs = /etc/ssl/certs/ca-certificates.crt
>
> with 3 brackets.
>
> Try that.
>
> BTW: I do have the added lines in myconfig.conf that you do. I was in
> hurray when I posted last night.
>
> phil
>
>
> On Friday, October 12, 2018 at 6:42:41 AM UTC-4, David Hindley wrote:
>>
>> Not sure it will help solve this or not, but the Mosquitto log shows the
>> following:
>>
>>  New connection from 86.27.145.159 on port 8883.
>> 1539340809: OpenSSL Error: error:1408F10B:SSL
>> routines:ssl3_get_record:wrong version number
>> 1539340809: Socket error on client , disconnecting.
>> 1539340811: Client connection from 86.27.145.159 failed:
>> error:1408F10B:SSL routines:ssl3_get_record:wrong version number.
>> 1539340814: New connection from 86.27.145.159 on port 8883.
>>
>> So, it does seem to be SSL related, but I am not sure how to solve this.
>> Any ideas please anyone?
>>
>> David.
>>
>> On Fri, 12 Oct 2018 at 10:01, David Hindley 
>> wrote:
>>
>>> Phil/Pat
>>>
>>> Many Thanks for you reply.
>>>
>>> I did set up a password for Mosquitto and also the acl file, as per your
>>> email below.
>>>
>>> However, my myconfig.conf file is different to the one you listed below,
>>> as I am using Let's Encrypt SSL, so followed the format towards the end of
>>> Pat's post ( MQTT "tutorial"
>>> <https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/> ), as
>>> follows:
>>>
>>> persistence false
>>>
>>> allow_anonymous true
>>> password_file /etc/mosquitto/passwd
>>>
>>> acl_file /etc/mosquitto/acl
>>>
>>> #Insecure mqtt to localhost only and secure mqtt with ssl
>>> listener 1883 localhost
>>> listener 8883
>>> certfile /etc/letsencrypt/live/mqttdh.uk/cert.pem
>>> cafile /etc/letsencrypt/live/mqttdh.uk/chain.pem
>>> keyfile /etc/letsencrypt/live/mqttdh.uk/privkey.pem
>>> protocol mqtt
>>>
>>> # websockets
>>> listener 9001
>>> certfile /etc/letsencrypt/live/mqttdh.uk/cert.pem
>>> cafile /etc/letsencrypt/live/mqttdh.uk/chain.pem
>>> keyfile /etc/letsencrypt/live/mqttdh.uk/privkey.pem
>>> protocol websockets
>>>
>>> Did you not use SSL on your set up for  https://wx.kutzenco.com? Maybe
>>> I have done something wrong with trying to set this part up.  It is really
>>> frustrating, as the syslog reports that MQTT is sending records, as it
>>> contains several lines like:
>>>
>>> Oct 12 09:58:27 raspberrypi weewx[1147]: restx: MQTT: Published record
>>> 2018-10-12 09:58:28 BST (1539334708)
>>>
>>> Pat - if you see this, do you have any ideas what I might be doing wrong
>>> - my hunch is that it is something to do with the settings for SSL for MQTT
>>> in weewx.conf, which are shown below.  Do I need to create the
>>> ca-certificates.crt file?  Or I guess it could be some issue with my web
>>> host for www.ashteadweather.com which is 1&1 (with SSL).
>>>
>>> Thanks
>>>
>>> David.
>>>
>>> *weewx.conf file*
>>>
>>>   [[MQTT]]
>>> server_url = mqtt://x:...@mqttdh.uk:8883/
>>> topic = weather
>>> unit_system = METRIC
>>> aggregation = aggregate
>>> binding = archive,loop
>>> # log_success = False
>>> # log_failure = True
>>> [[tls]]
>>>tls_version = tlsv1
>>>ca_certs = /etc/ssl/certs/ca-certificates.crt
>>>
>>> The Belchertown skin.conf MQTT content is as follows:
>>>
>>>  # MQTT Def

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

[David Hindley]

Not sure it will help solve this or not, but the Mosquitto log shows the
following:

 New connection from 86.27.145.159 on port 8883.
1539340809: OpenSSL Error: error:1408F10B:SSL
routines:ssl3_get_record:wrong version number
1539340809: Socket error on client , disconnecting.
1539340811: Client connection from 86.27.145.159 failed: error:1408F10B:SSL
routines:ssl3_get_record:wrong version number.
1539340814: New connection from 86.27.145.159 on port 8883.

So, it does seem to be SSL related, but I am not sure how to solve this.
Any ideas please anyone?

David.

On Fri, 12 Oct 2018 at 10:01, David Hindley  wrote:

> Phil/Pat
>
> Many Thanks for you reply.
>
> I did set up a password for Mosquitto and also the acl file, as per your
> email below.
>
> However, my myconfig.conf file is different to the one you listed below,
> as I am using Let's Encrypt SSL, so followed the format towards the end of
> Pat's post ( MQTT "tutorial"
> <https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/> ), as follows:
>
> persistence false
>
> allow_anonymous true
> password_file /etc/mosquitto/passwd
>
> acl_file /etc/mosquitto/acl
>
> #Insecure mqtt to localhost only and secure mqtt with ssl
> listener 1883 localhost
> listener 8883
> certfile /etc/letsencrypt/live/mqttdh.uk/cert.pem
> cafile /etc/letsencrypt/live/mqttdh.uk/chain.pem
> keyfile /etc/letsencrypt/live/mqttdh.uk/privkey.pem
> protocol mqtt
>
> # websockets
> listener 9001
> certfile /etc/letsencrypt/live/mqttdh.uk/cert.pem
> cafile /etc/letsencrypt/live/mqttdh.uk/chain.pem
> keyfile /etc/letsencrypt/live/mqttdh.uk/privkey.pem
> protocol websockets
>
> Did you not use SSL on your set up for  https://wx.kutzenco.com? Maybe I
> have done something wrong with trying to set this part up.  It is really
> frustrating, as the syslog reports that MQTT is sending records, as it
> contains several lines like:
>
> Oct 12 09:58:27 raspberrypi weewx[1147]: restx: MQTT: Published record
> 2018-10-12 09:58:28 BST (1539334708)
>
> Pat - if you see this, do you have any ideas what I might be doing wrong -
> my hunch is that it is something to do with the settings for SSL for MQTT
> in weewx.conf, which are shown below.  Do I need to create the
> ca-certificates.crt file?  Or I guess it could be some issue with my web
> host for www.ashteadweather.com which is 1&1 (with SSL).
>
> Thanks
>
> David.
>
> *weewx.conf file*
>
>   [[MQTT]]
> server_url = mqtt://x:...@mqttdh.uk:8883/
> topic = weather
> unit_system = METRIC
> aggregation = aggregate
> binding = archive,loop
> # log_success = False
> # log_failure = True
> [[tls]]
>tls_version = tlsv1
>ca_certs = /etc/ssl/certs/ca-certificates.crt
>
> The Belchertown skin.conf MQTT content is as follows:
>
>  # MQTT Defaults
> mqtt_enabled = 1
> mqtt_host = mqttdh.uk
> mqtt_port = 9001
> mqtt_ssl = 1
> mqtt_topic = "weather/loop"
> disconnect_live_website_visitor = 0
>
>
> On Fri, 12 Oct 2018 at 00:59, Philip Kutzenco  wrote:
>
>> David,
>>
>> You don't need to specify a username/password to receive data if you have
>> sett up your broker as Pat detailed in his post
>> <https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/>. The
>> weewx.conf stanzas in the file I attached in my earlier post are working
>> fine at https://wx.kutzenco.com. One minor change is that I changed the
>> subscription to "weather/loop" instead of "weather/#". It works with #, but
>> I think best practice is to only subscribe to loop.
>>
>> Here are some things to look at:
>>
>> 1. Did you set up a password for Mosquitto? It is done as follows:
>> *sudo mosquitto_passwd -c /etc/mosquitto/passwd *
>> Note that the username is just for Mosquitto. It doesn't need to be a
>> linux account name.
>>
>> 1.  Did you set up an acl file (*/etc/mosquitto/acl)*? It should contain:
>>
>>
>>
>> *# Allow anonymous access to the systopic read $SYS/# # Allow anonymous
>> to read weathertopic read weather/#*
>>
>>
>> *# weewx readwrite to the loopuser topic
>> weather/#*
>>
>> 2. Does your Mosquitto myconfig.conf (*/etc/mosquitto/conf.d/myconfig.conf)
>> *file contain the following? It should have:
>>
>>
>>
>>
>>
>> *persistence falseallow_anonymous truepassword_file
>> /etc/mosquitto/passwdacl_file /etc/mosquitto/acllistener 1883protocol mqtt*
>>
>>
>>
>> *# websocketslistener 9001protocol websocket *

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

[David Hindley]

Phil/Pat

Many Thanks for you reply.

I did set up a password for Mosquitto and also the acl file, as per your
email below.

However, my myconfig.conf file is different to the one you listed below, as
I am using Let's Encrypt SSL, so followed the format towards the end of
Pat's post ( MQTT "tutorial"
 ), as follows:

persistence false

allow_anonymous true
password_file /etc/mosquitto/passwd

acl_file /etc/mosquitto/acl

#Insecure mqtt to localhost only and secure mqtt with ssl
listener 1883 localhost
listener 8883
certfile /etc/letsencrypt/live/mqttdh.uk/cert.pem
cafile /etc/letsencrypt/live/mqttdh.uk/chain.pem
keyfile /etc/letsencrypt/live/mqttdh.uk/privkey.pem
protocol mqtt

# websockets
listener 9001
certfile /etc/letsencrypt/live/mqttdh.uk/cert.pem
cafile /etc/letsencrypt/live/mqttdh.uk/chain.pem
keyfile /etc/letsencrypt/live/mqttdh.uk/privkey.pem
protocol websockets

Did you not use SSL on your set up for  https://wx.kutzenco.com? Maybe I
have done something wrong with trying to set this part up.  It is really
frustrating, as the syslog reports that MQTT is sending records, as it
contains several lines like:

Oct 12 09:58:27 raspberrypi weewx[1147]: restx: MQTT: Published record
2018-10-12 09:58:28 BST (1539334708)

Pat - if you see this, do you have any ideas what I might be doing wrong -
my hunch is that it is something to do with the settings for SSL for MQTT
in weewx.conf, which are shown below.  Do I need to create the
ca-certificates.crt file?  Or I guess it could be some issue with my web
host for www.ashteadweather.com which is 1&1 (with SSL).

Thanks

David.

*weewx.conf file*

  [[MQTT]]
server_url = mqtt://x:...@mqttdh.uk:8883/
topic = weather
unit_system = METRIC
aggregation = aggregate
binding = archive,loop
# log_success = False
# log_failure = True
[[tls]]
   tls_version = tlsv1
   ca_certs = /etc/ssl/certs/ca-certificates.crt

The Belchertown skin.conf MQTT content is as follows:

 # MQTT Defaults
mqtt_enabled = 1
mqtt_host = mqttdh.uk
mqtt_port = 9001
mqtt_ssl = 1
mqtt_topic = "weather/loop"
disconnect_live_website_visitor = 0


On Fri, 12 Oct 2018 at 00:59, Philip Kutzenco  wrote:

> David,
>
> You don't need to specify a username/password to receive data if you have
> sett up your broker as Pat detailed in his post
> . The
> weewx.conf stanzas in the file I attached in my earlier post are working
> fine at https://wx.kutzenco.com. One minor change is that I changed the
> subscription to "weather/loop" instead of "weather/#". It works with #, but
> I think best practice is to only subscribe to loop.
>
> Here are some things to look at:
>
> 1. Did you set up a password for Mosquitto? It is done as follows:
> *sudo mosquitto_passwd -c /etc/mosquitto/passwd *
> Note that the username is just for Mosquitto. It doesn't need to be a
> linux account name.
>
> 1.  Did you set up an acl file (*/etc/mosquitto/acl)*? It should contain:
>
>
>
> *# Allow anonymous access to the systopic read $SYS/# # Allow anonymous to
> read weathertopic read weather/#*
>
>
> *# weewx readwrite to the loopuser topic
> weather/#*
>
> 2. Does your Mosquitto myconfig.conf (*/etc/mosquitto/conf.d/myconfig.conf)
> *file contain the following? It should have:
>
>
>
>
>
> *persistence falseallow_anonymous truepassword_file
> /etc/mosquitto/passwdacl_file /etc/mosquitto/acllistener 1883protocol mqtt*
>
>
>
> *# websocketslistener 9001protocol websocket *
>
> I am far from an expert on this, but if you post copies of those files. I
> will look at them in addition to the weewx.conf stanzas you already
> published, ans see if I can spot a reason for it not working for you. (I
> probably won't get a chance to look until tomorrow).
>
> phil
>
> On Thursday, October 11, 2018 at 5:13:23 PM UTC-4, Colin Larsen wrote:
>>
>> You'll also need to supply the username and password to "receive" the
>> MQTT data (in skin.conf or Belchertown) but that is not yet supported as
>> far as I know.
>>
>> Colin
>>
>>
>> On Fri, 12 Oct 2018, 07:59 ,  wrote:
>>
>>> Hi
>>>
>>>
>>>
>>> I am trying to set up MQTT on the Belchertown skin, and just can't get
>>> it to work, but think I am very nearly there.  Like Philip Kutzenco, I
>>> am using Digital Ocean to host my MQTT broker, with my own domain name, and
>>> have followed Pat's guide to set up the MQTT broker with SSL using Let's
>>> Encrypt.   MQTT all seems to be working, as per Pat's guide.  My weather
>>> website (ashteadweather.com hosted at 1&1 with SSL certificate) says
>>> "Connected.  Waiting for data", which sounds promising, but it just stays
>>> at that message.  I copied the weewx.conf settings format for MQTT and the
>>> skin.conf format for Belchertown skin, as suggested by Philip Kutzenco, as
>>> per below:
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> weewx.conf:
>

Re: [weewx-user] SFTP extension problem

[David Hindley]

Excellent. Thank you. That worked.  Hurrah.

David.

On Mon, 8 Oct 2018 at 19:22, Thomas Keffer  wrote:

> Matthew's version of sftp.py has a typo. Go to line 62 and add a closing
> parenthesis to the end of the line. Instead of this:
>
> logdbg("remote_root=%s" % self.remote_root)
> logdbg("server=%s port=%s user=%s" % (server, port, user)
>
> def run(self):
>
> you want this:
>
> logdbg("remote_root=%s" % self.remote_root)
> logdbg("server=%s port=%s user=%s" % (server, port, user))
>
> def run(self):
>
> -tk
>
> On Mon, Oct 8, 2018 at 11:09 AM  wrote:
>
>> Hi
>>
>> I am trying to use SFTP to upload my files to a domain hosted at 1&1,
>> which seems to use SFTP, so the old FTP process doesn't work.  I installed
>> pysftp, successfully, as required.
>>
>> I am trying to use Matthew Wall's SFTP extension, but get the following
>> errors:
>>
>> Oct  8 18:55:20 raspberrypi weewx[17094]: cheetahgenerator: Generated 14
>> files for report StandardReport in 3.58 seconds
>> Oct  8 18:55:20 raspberrypi weewx[17094]: manager: Daily summary version
>> is 2.0
>> Oct  8 18:55:21 raspberrypi weewx[17094]: imagegenerator: Generated 12
>> images for StandardReport in 0.67 seconds
>> Oct  8 18:55:21 raspberrypi weewx[17094]: copygenerator: copied 9 files
>> to /var/www/html/weewx
>> Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Running report
>> sftp
>> Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Found
>> configuration file /etc/weewx/skins/sftp/skin.conf for report sftp
>> Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Unable to
>> instantiate generator user.sftp.SFTPGenerator
>> Oct  8 18:55:21 raspberrypi weewx[17094]:   invalid syntax
>> (sftp.py, line 64)
>> Oct  8 18:55:21 raspberrypi weewx[17094]:   Traceback (most
>> recent call last):
>> Oct  8 18:55:21 raspberrypi weewx[17094]: File
>> "/usr/share/weewx/weewx/reportengine.py", line 220, in run
>> Oct  8 18:55:21 raspberrypi weewx[17094]:   obj =
>> weeutil.weeutil._get_object(generator)(
>> Oct  8 18:55:21 raspberrypi weewx[17094]: File
>> "/usr/share/weewx/weeutil/weeutil.py", line 1132, in _get_object
>> Oct  8 18:55:21 raspberrypi weewx[17094]:   mod =
>> __import__(module)
>> Oct  8 18:55:21 raspberrypi weewx[17094]: File
>> "/usr/share/weewx/user/sftp.py", line 64
>> Oct  8 18:55:21 raspberrypi weewx[17094]:   def run(self):
>> Oct  8 18:55:21 raspberrypi weewx[17094]: ^
>> Oct  8 18:55:21 raspberrypi weewx[17094]:   SyntaxError:
>> invalid syntax
>> Oct  8 18:55:21 raspberrypi weewx[17094]:   Generator ignored
>> Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Running report FTP
>> Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Found
>> configuration file /etc/weewx/skins/Ftp/skin.conf for report FTP
>> Oct  8 18:55:21 raspberrypi weewx[17094]: ftpgenerator: FTP upload not
>> requested. Skipped.
>> Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Running report
>> RSYNC
>> Oct  8 18:55:21 raspberrypi weewx[17094]: reportengine: Found
>> configuration file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
>> Oct  8 18:55:21 raspberrypi weewx[17094]: rsyncgenerator: rsync upload
>> not requested. Skipped.
>>
>> The sftp content of weewx conf is as follows (confidential details
>> removed):
>>
>> [[sftp]]
>> server = xxx
>> user = x
>> skin = sftp
>> path = /weather
>> password = xx  [I put this in single quotes, as the default
>> content seemed to suggest that]
>> port = 22
>>
>> Anyone have any ideas what is going wrong please?
>>
>> Thanks
>>
>> David.
>>
> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-user+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/X_5g7D43uVU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [weewx-user] Re: Secure FTP from ftpupload call?

[David Hindley]

Thanks again Gary, for your response. Very helpful as always. Upgrade looks
a bit scary, but will give it a go.

On Fri, 5 Oct 2018 at 14:01, gjr80  wrote:

> On Friday, 5 October 2018 20:20:14 UTC+10, David Hindley wrote:
>>
>> Thanks, Gary.
>>
>> I think my problems with pysftp are something to do with using Wheezy on
>> a RPi and ver 2.7 of Python. That seems to have an old version of pip, so I
>> managed to update that to pip ver 18.0, but then pip shows several nasty
>> looking errors when I try to install pysftp.  The syslog is below, but I
>> suspect I am going to have to upgrade my Pi to raspbian stretch  - any tips
>> on making that process quick, allowing for a weewx install would be
>> appreciated.
>>
>>
> Am no great expert but the SSL warnings are exactly that, warnings. You do
> have the libffi error:
>
> Package libffi was not found in the pkg-config search path.
>>
>
> You could try to installing libffi-dev as I suggested, though maybe a bit
> mute if upgrading to Stretch.
>
> Regarding upgrading to Stretch. Its fairly straightforward, backing up
> your WeeWX config and data should make re-installing WeeWX fairly painless.
> The basic steps are:
>
>1. stop WeeWX
>2. backup you WeeWX data, assuming you are using SQLite you just need
>to backup any .sdb files in /var/lib/weewx
>3. backup up you WeeWX confg and skins, ie everything in /etc/weewx
>4. backup your bin/user directory, /usr/share/weewx/user in your case
>5. download your preferred raspbian stretch image, burn it to a SD
>card and boot your RPi from the new image
>6. setup RPi as required
>7. install WeeWX and get a minimal install running with the simulator
>8. stop WeeWX and copy your old database over the new one, restart
>WeeWX
>9. start adding in any extensions/customisations etc, refer back to
>your backup /etc/weewx/weewx.conf and skin.conf files for any config
>details/customisations
>
> Some folks might prefer to take a shorter approach, ie just copy all the
> WeeWX directories from the old to the new, that may work but it can also
> tangle you in knots if it goes awry.
>
> Gary
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/lC5wFBhg2g8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [weewx-user] Re: Secure FTP from ftpupload call?

[David Hindley]

Thanks, Gary.  Will explore both options and decide which looks easier.

On Fri, 5 Oct 2018 at 14:11, gjr80  wrote:

> Really up to you, I am sure some folks will say you are best having a
> daemon such as WeeWX run as a user other than root. I run WeeWX as root and
> I suspect most folks do too. I am happy that the risks are fairly minimal.
> The steps to change your system such that WeeWX is run as a user other than
> root are fairly straightforward and are covered here
> <https://github.com/weewx/weewx/wiki/Run-as-a-non-root-user> in the wiki
> <https://github.com/weewx/weewx/wiki>. Of course if you continue to run
> WeeWX as root you probably need to setup root with passwordless ssh,
> arguably that is more involved than changing the WeeWX user, but then again
> you have already done that once so I am sure it can be easily done again :)
>
> If I was doing things again I would do the same as I have now and leave
> WeeWX run as root and give root passwordless ssh. Not going to argue with
> anyone who disagrees though.
>
> Gary
>
> On Friday, 5 October 2018 20:25:20 UTC+10, David Hindley wrote:
>>
>> Gary - regarding the ssh point - which option would you recommend -
>> change the user that runs weewx to pi, or create ssh keys for the root user
>> (which I believe currently runs weewx)?
>>
>> David.
>>
>> On Fri, 5 Oct 2018 at 07:10, gjr80  wrote:
>>
>>> I presume that your working passwordless ssh is from your WeatherPi
>>> machine. Which user on WeatherPi has passwordless ssh? If it is, for
>>> example, user pi and WeeWX is being run as root then I expect WeeWX rsync
>>> will fail with the error shown. You need to make sure that the account that
>>> runs WeeWX has passwordless ssh access. So you may need to change the user
>>> that runs WeeWX or give the account that runs WeeWX (likely root unless you
>>> explicitly changed it) passwordless ssh access.
>>>
>>> Regarding pysftp, what did you do? what error did you come across? I
>>> just tried installing with pip on my RPI running raspbian stretch:
>>>
>>> $ sudo pip install pysftp
>>>
>>> and received a dependency error on package libffi. Installed libffi
>>> using:
>>>
>>> $ sudo ap-get install libffi-dev
>>>
>>> then ran the pysftp install again and it installed without error, it
>>> was slow but eventually it got there. If that does not solve your pysftp
>>> issue post the command you used to install it and the output you receive.
>>>
>>> Gary
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/lC5wFBhg2g8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [weewx-user] Re: Secure FTP from ftpupload call?

[David Hindley]

Gary - regarding the ssh point - which option would you recommend - change
the user that runs weewx to pi, or create ssh keys for the root user (which
I believe currently runs weewx)?

David.

On Fri, 5 Oct 2018 at 07:10, gjr80  wrote:

> I presume that your working passwordless ssh is from your WeatherPi
> machine. Which user on WeatherPi has passwordless ssh? If it is, for
> example, user pi and WeeWX is being run as root then I expect WeeWX rsync
> will fail with the error shown. You need to make sure that the account that
> runs WeeWX has passwordless ssh access. So you may need to change the user
> that runs WeeWX or give the account that runs WeeWX (likely root unless you
> explicitly changed it) passwordless ssh access.
>
> Regarding pysftp, what did you do? what error did you come across? I just
> tried installing with pip on my RPI running raspbian stretch:
>
> $ sudo pip install pysftp
>
> and received a dependency error on package libffi. Installed libffi using:
>
> $ sudo ap-get install libffi-dev
>
> then ran the pysftp install again and it installed without error, it was
> slow but eventually it got there. If that does not solve your pysftp
> issue post the command you used to install it and the output you receive.
>
> Gary
>
> On Friday, 5 October 2018 03:03:44 UTC+10, dhin...@djhindley.com wrote:
>>
>> I have recently signed up to 1&1 to host my weather website and want to
>> get weewx to upload files to it, allowing for the fact that they now use
>> SFTP, not plain FTP, so I can't use the FTP weewx facility. I tried to use
>> Matthew Wall's weew-sftp extension, but couldn't manage to get the python
>> pysftp module installed, so I thought I would try Rsync.   I followed the
>> steps below and can successfully ssh to my 1&1 FTP account without needing
>> to type in a password.
>>
>> However, when I amend Rysc configuration in weewx.conf as per below,
>> Rsync seems to fail.  My syslog is below.  The Rsync error is at the end,
>> but I included earlier errors in the syslog, but not sure if they are
>> related to the Rsync issue or not.
>>
>> Any ideas on what is going wrong?
>>
>> Many Thanks
>>
>> David.
>>
>> Oct  4 17:51:17 WeatherPi weewx[10224]: manager: Daily summary version is
>> 2.0
>> Oct  4 17:51:17 WeatherPi weewx[10224]: reportengine: Caught
>> unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator
>> Oct  4 17:51:17 WeatherPi weewx[10224]:   No module named
>> forecast
>> Oct  4 17:51:17 WeatherPi weewx[10224]:   Traceback (most
>> recent call last):
>> Oct  4 17:51:17 WeatherPi weewx[10224]: File
>> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
>> Oct  4 17:51:17 WeatherPi weewx[10224]:   obj.start()
>> Oct  4 17:51:17 WeatherPi weewx[10224]: File
>> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
>> Oct  4 17:51:17 WeatherPi weewx[10224]:   self.run()
>> Oct  4 17:51:17 WeatherPi weewx[10224]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 155, in run
>> Oct  4 17:51:17 WeatherPi weewx[10224]: 
>> self.initExtensions(gen_dict[section_name])
>> Oct  4 17:51:17 WeatherPi weewx[10224]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 197, in initExtensions
>> Oct  4 17:51:17 WeatherPi weewx[10224]:   class_ =
>> weeutil.weeutil._get_object(x)
>> Oct  4 17:51:17 WeatherPi weewx[10224]: File
>> "/usr/share/weewx/weeutil/weeutil.py", line 1132, in _get_object
>> Oct  4 17:51:17 WeatherPi weewx[10224]:   mod =
>> __import__(module)
>> Oct  4 17:51:17 WeatherPi weewx[10224]:   ImportError: No
>> module named forecast
>> Oct  4 17:51:17 WeatherPi weewx[10224]:   Generator terminated
>> Oct  4 17:51:17 WeatherPi weewx[10224]: reportengine: Caught
>> unrecoverable exception in generator weewx.imagegenerator.ImageGenerator
>> Oct  4 17:51:17 WeatherPi weewx[10224]:   'skin'
>> Oct  4 17:51:17 WeatherPi weewx[10224]:   Traceback (most
>> recent call last):
>> Oct  4 17:51:17 WeatherPi weewx[10224]: File
>> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
>> Oct  4 17:51:17 WeatherPi weewx[10224]:   obj.start()
>> Oct  4 17:51:17 WeatherPi weewx[10224]: File
>> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
>> Oct  4 17:51:17 WeatherPi weewx[10224]:   self.run()
>> Oct  4 17:51:17 WeatherPi weewx[10224]: File
>> "/usr/share/weewx/weewx/imagegenerator.py", line 31, in run
>> Oct  4 17:51:17 WeatherPi weewx[10224]:   self.setup()
>> Oct  4 17:51:17 WeatherPi weewx[10224]: File
>> "/usr/share/weewx/weewx/imagegenerator.py", line 44, in setup
>> Oct  4 17:51:17 WeatherPi weewx[10224]: 
>> self.skin_dict['skin']))
>> Oct  4 17:51:17 WeatherPi weewx[10224]:  

Re: [weewx-user] Re: Secure FTP from ftpupload call?

[David Hindley]

Thanks, Gary.

I think my problems with pysftp are something to do with using Wheezy on a
RPi and ver 2.7 of Python. That seems to have an old version of pip, so I
managed to update that to pip ver 18.0, but then pip shows several nasty
looking errors when I try to install pysftp.  The syslog is below, but I
suspect I am going to have to upgrade my Pi to raspbian stretch  - any tips
on making that process quick, allowing for a weewx install would be
appreciated.

David.

pi@WeatherPi ~ $ sudo pip install pysftp
Collecting pysftp
/usr/local/lib/python2.7/dist-packages/pip/_vendor/urllib3/util/ssl_.py:369:
SNIMissingWarning: An HTTPS request has been made, but the SNI (Se

rver Name Indication) extension to TLS is not available on this
platform. This may cause the server to present an incorrect TLS
certificate, wh
  ich can cause validation failures. You
can upgrade to a newer version of Python to solve this. For more
information, see https://urllib3.readth

edocs.io/en/latest/advanced-usage.html#ssl-warnings
  SNIMissingWarning
/usr/local/lib/python2.7/dist-packages/pip/_vendor/urllib3/util/ssl_.py:160:
InsecurePlatformWarning: A true SSLContext object is not available

. This prevents urllib3 from configuring SSL appropriately and may
cause certain SSL connections to fail. You can upgrade to a newer version
of
 Python to solve this. For more information, see
https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
  InsecurePlatformWarning
/usr/local/lib/python2.7/dist-packages/pip/_vendor/urllib3/util/ssl_.py:160:
InsecurePlatformWarning: A true SSLContext object is not available

. This prevents urllib3 from configuring SSL appropriately and may
cause certain SSL connections to fail. You can upgrade to a newer version
of
 Python to solve this. For more information, see
https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
  InsecurePlatformWarning
  Downloading
https://files.pythonhosted.org/packages/36/60/45f30390a38b1f92e0a8cf4de178cd7c2bc3f874c85430e40ccf99df8fe7/pysftp-0.2.9.tar.gz
Collecting paramiko>=1.17 (from pysftp)
  Downloading
https://files.pythonhosted.org/packages/cf/ae/94e70d49044ccc234bfdba20114fa947d7ba6eb68a2e452d89b920e62227/paramiko-2.4.2-py2.py3

-none-any.whl (193kB)
100% || 194kB 2.1MB/s
Collecting cryptography>=1.5 (from paramiko>=1.17->pysftp)
  Downloading
https://files.pythonhosted.org/packages/22/21/233e38f74188db94e8451ef6385754a98f3cad9b59bedf3a8e8b14988be4/cryptography-2.3.1.tar

.gz (449kB)
100% || 450kB 2.0MB/s
Collecting pynacl>=1.0.1 (from paramiko>=1.17->pysftp)
  Downloading
https://files.pythonhosted.org/packages/61/ab/2ac6dea8489fa713e2b4c6c5b549cc962dd4a842b5998d9e80cf8440b7cd/PyNaCl-1.3.0.tar.gz
(3
.4MB)
100% || 3.4MB 953kB/s
  Installing build dependencies ... error
  Complete output from command /usr/bin/python -m pip install
--ignore-installed --no-user --prefix /tmp/pip-build-env-FXioj2
--no-warn-script-
location --no-binary :none:
--only-binary :none: -i https://pypi.org/simple -- setuptools wheel
"cffi>=1.4.1; python_implementation != 'PyPy'":
  Collecting setuptools

/usr/local/lib/python2.7/dist-packages/pip/_vendor/urllib3/util/ssl_.py:369:
SNIMissingWarning: An HTTPS request has been made, but the SNI (

  Server Name Indication) extension to TLS is not available on this
platform. This may cause the server to present an incorrect TLS
certificate,
   which can cause validation failures. You can
upgrade to a newer version of Python to solve this. For more information,
see https://urllib3.read

thedocs.io/en/latest/advanced-usage.html#ssl-warnings
SNIMissingWarning

/usr/local/lib/python2.7/dist-packages/pip/_vendor/urllib3/util/ssl_.py:160:
InsecurePlatformWarning: A true SSLContext object is not availab

  le. This prevents urllib3 from configuring SSL appropriately and may
cause certain SSL connections to fail. You can upgrade to a newer version

 of Python to solve this. For more information, see
https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
InsecurePlatformWarning

/usr/local/lib/python2.7/dist-packages/pip/_vendor/urllib3/util/ssl_.py:160:
InsecurePlatformWarning: A true SSLContext object is not availab

  le. This prevents urllib3 from configuring SSL appropriately and may
cause certain SSL connections to fail. You can upgrade to a newer version

 of Python to solve this. For more information, see
https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
InsecurePlatformWarning
Downloading
https://files.pythonhosted.org/packages/96/06/c8ee69628191285ffb277bd5abdf769166e7a14b867c2a172f0175b1/set

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[David Hindley]

Good point re windy.  I thought I had set lat/long, but will check.

Maybe the graphs problem is to do with the FTP skin?


On Sun, 30 Sep 2018 at 16:41, Pat  wrote:

> Windy: It shows your location for you, but for me it shows my location. Up
> to you, but it's weird to see Massachusetts in Celsius :) I'm sure others
> here would see the same (their location) which doesn't match your station's
> location. It's advised to put your lat/lon in the URL so it all matches up.
>
> For your graphs: Yes, the day/week/month/year.json files need to be in the
> http://www.djhindley.com/weather/json folder. I'm not 100% sure on your
> setup but if you're able to get them there that should fix everything up.
>
>
>
> On Sunday, September 30, 2018 at 11:38:32 AM UTC-4, David Hindley wrote:
>>
>> Re windy - it seems to find my location automatically, so this feature is
>> fine.
>>
>> On Sun, 30 Sep 2018 at 15:46, Pat O'Brien  wrote:
>>
>> Couple other observations. Looks like all the json/ files are missing on
>> the website. Day.json, week.json, month.json and year.json all 404 not
>> found.
>>
>>
>>
>> And your windy map shows me my location. If you’ve updated it to show
>> your location, there are actually 2 spots for your lat/lon that need to be
>> updated.
>>
>>
>>
>> *From:* weewx...@googlegroups.com [mailto:weewx...@googlegroups.com] *On
>> Behalf Of *David Hindley
>> *Sent:* Sunday, September 30, 2018 10:36 AM
>> *To:* weewx...@googlegroups.com
>> *Subject:* Re: [weewx-user] Re: Belchertown skin for weewx now available!
>>
>>
>>
>> Site is at www.djhindley.com/weather
>>
>>
>>
>> I will check syslog.
>>
>>
>>
>> Yes, the js
>>
>> ...
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/GSrKZEiPqsc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[David Hindley]

Re windy - it seems to find my location automatically, so this feature is
fine.

On Sun, 30 Sep 2018 at 15:46, Pat O'Brien  wrote:

> Couple other observations. Looks like all the json/ files are missing on
> the website. Day.json, week.json, month.json and year.json all 404 not
> found.
>
>
>
> And your windy map shows me my location. If you’ve updated it to show your
> location, there are actually 2 spots for your lat/lon that need to be
> updated.
>
>
>
> *From:* weewx-user@googlegroups.com [mailto:weewx-user@googlegroups.com] *On
> Behalf Of *David Hindley
> *Sent:* Sunday, September 30, 2018 10:36 AM
> *To:* weewx-user@googlegroups.com
> *Subject:* Re: [weewx-user] Re: Belchertown skin for weewx now available!
>
>
>
> Site is at www.djhindley.com/weather
>
>
>
> I will check syslog.
>
>
>
> Yes, the json directory has index.html and some .json files.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/GSrKZEiPqsc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[David Hindley]

Thanks.  The files are being uploaded by FTP - examples from FTP part of
syslog are:

Uploaded file /httpdocs/weather/belchertown/js/highcharts-dayplots.js

and

Uploaded file  /httpdocs/weather/belchertown/json/day.json

and

Uploaded file  /httpdocs/weather/js/highcharts-dayplots.js

And I have checked the server containing the files and they are there, so
it seems the json files are being uploaded by FTP to
/httpdocs/weather/belchertown/json/ rather than /httpdocs/weather/json/.
Is this the problem perhaps?

On Sun, 30 Sep 2018 at 15:42, Pat O'Brien  wrote:

> Getting a 404 file not found on this file which would explain why the
> graphs aren’t being generated.
> http://www.djhindley.com/weather/json/day.json
>
>
>
> So there may be an error in syslog or the file isn’t being copied if
> you’re using the FTP skin to upload it? This file is generated by the
> Highcharts_Belchertown skin.
>
>
>
> The file should be in /var/www/html/weewx/Belchertown/json according to
> your configs.
>
>
>
> *From:* weewx-user@googlegroups.com [mailto:weewx-user@googlegroups.com] *On
> Behalf Of *David Hindley
> *Sent:* Sunday, September 30, 2018 10:36 AM
> *To:* weewx-user@googlegroups.com
> *Subject:* Re: [weewx-user] Re: Belchertown skin for weewx now available!
>
>
>
> Site is at www.djhindley.com/weather
>
>
>
> I will check syslog.
>
>
>
> Yes, the json directory has index.html and some .json files.
>
>
>
> On Sun, 30 Sep 2018 at 15:30, Pat O'Brien  wrote:
>
> No I don’t think so. Those sections look good, too. Does your system log
> show anything in error? Usually it’s at /var/log/syslog
>
>
>
> Also does /var/www/html/weewx/Belchertown/json have any files in it?
>
>
>
> Is this site public?
>
>
>
> *From:* weewx-user@googlegroups.com [mailto:weewx-user@googlegroups.com] *On
> Behalf Of *David Hindley
> *Sent:* Sunday, September 30, 2018 10:28 AM
> *To:* weewx-user@googlegroups.com
> *Subject:* Re: [weewx-user] Re: Belchertown skin for weewx now available!
>
>
>
>
> Sure.  It is below.  Thanks for looking at this.  Could it be due to
> inclusion of forecast and cmon skins?  Maybe I should delete those?
>
>
>
>
>
> [StdReport]
>
>
>
> # Where the skins reside, relative to WEEWX_ROOT
>
> SKIN_ROOT = /etc/weewx/skins
>
>
>
> # Where the generated reports should go, relative to WEEWX_ROOT
>
> HTML_ROOT = /var/www/html/weewx
>
>
>
> # The database binding indicates which data should be used in reports.
>
> data_binding = wx_binding
>
>
>
> # Each of the following subsections defines a report that will be run.
>
>
>
> [[StandardReport]]
>
> # See the customizing guide to change the units, plot types and
> line
>
> # colors, modify the fonts, display additional sensor data, and
> other
>
> # customizations. Many of those changes can be made here by
> overriding
>
> # parameters, or by modifying templates within the skin itself.
>
>
>
> # The StandardReport uses the 'Standard' skin, which contains the
>
> # images, templates and plots for the report.
>
> skin = Belchertown
>
> [[[Units]]]
>
> Groups
>
> group_altitude = meter
>
> group_speed2 = meter_per_second2
>
> group_pressure = mbar
>
> group_rain = mm
>
> group_rainrate = mm_per_hour
>
> group_temperature = degree_C
>
> group_degree_day = degree_C_day
>
> group_speed = meter_per_second
>
> [[forecast]]
>
> HTML_ROOT = /var/www/html/weewx/forecast
>
> skin = forecast
>
> # [[exfoliation]]
>
> #HTML_ROOT = /var/www/html/weewx/exfoliation
>
> #   skin = exfoliation
>
> [[cmon]]
>
> HTML_ROOT = /var/www/html/weewx/cmon
>
> skin = cmon
>
> [[Highcharts_Belchertown]]
>
> HTML_ROOT = /var/www/html/weewx/belchertown
>
> skin = Highcharts_Belchertown
>
> [[[Units]]]
>
> Groups
>
> group_altitude = meter
>
> group_degree_day = degree_C_day
>
> group_pressure = mbar
>
> group_rain = mm
>
> group_rainrate = mm_per_hour
>
> group_speed = meter_per_second
>
> group_speed2 = meter_per_second2
>
> group_temperature = degree_C
>
> [[Belchertown]]
>
>   

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[David Hindley]

Site is at www.djhindley.com/weather

I will check syslog.

Yes, the json directory has index.html and some .json files.

On Sun, 30 Sep 2018 at 15:30, Pat O'Brien  wrote:

> No I don’t think so. Those sections look good, too. Does your system log
> show anything in error? Usually it’s at /var/log/syslog
>
>
>
> Also does /var/www/html/weewx/Belchertown/json have any files in it?
>
>
>
> Is this site public?
>
>
>
> *From:* weewx-user@googlegroups.com [mailto:weewx-user@googlegroups.com] *On
> Behalf Of *David Hindley
> *Sent:* Sunday, September 30, 2018 10:28 AM
> *To:* weewx-user@googlegroups.com
> *Subject:* Re: [weewx-user] Re: Belchertown skin for weewx now available!
>
>
>
>
> Sure.  It is below.  Thanks for looking at this.  Could it be due to
> inclusion of forecast and cmon skins?  Maybe I should delete those?
>
>
>
>
>
> [StdReport]
>
>
>
> # Where the skins reside, relative to WEEWX_ROOT
>
> SKIN_ROOT = /etc/weewx/skins
>
>
>
> # Where the generated reports should go, relative to WEEWX_ROOT
>
> HTML_ROOT = /var/www/html/weewx
>
>
>
> # The database binding indicates which data should be used in reports.
>
> data_binding = wx_binding
>
>
>
> # Each of the following subsections defines a report that will be run.
>
>
>
> [[StandardReport]]
>
> # See the customizing guide to change the units, plot types and
> line
>
> # colors, modify the fonts, display additional sensor data, and
> other
>
> # customizations. Many of those changes can be made here by
> overriding
>
> # parameters, or by modifying templates within the skin itself.
>
>
>
> # The StandardReport uses the 'Standard' skin, which contains the
>
> # images, templates and plots for the report.
>
> skin = Belchertown
>
> [[[Units]]]
>
> Groups
>
> group_altitude = meter
>
> group_speed2 = meter_per_second2
>
> group_pressure = mbar
>
> group_rain = mm
>
> group_rainrate = mm_per_hour
>
> group_temperature = degree_C
>
> group_degree_day = degree_C_day
>
> group_speed = meter_per_second
>
> [[forecast]]
>
> HTML_ROOT = /var/www/html/weewx/forecast
>
> skin = forecast
>
> # [[exfoliation]]
>
> #HTML_ROOT = /var/www/html/weewx/exfoliation
>
> #   skin = exfoliation
>
> [[cmon]]
>
> HTML_ROOT = /var/www/html/weewx/cmon
>
> skin = cmon
>
> [[Highcharts_Belchertown]]
>
> HTML_ROOT = /var/www/html/weewx/belchertown
>
> skin = Highcharts_Belchertown
>
> [[[Units]]]
>
> Groups
>
> group_altitude = meter
>
> group_degree_day = degree_C_day
>
> group_pressure = mbar
>
> group_rain = mm
>
> group_rainrate = mm_per_hour
>
> group_speed = meter_per_second
>
> group_speed2 = meter_per_second2
>
> group_temperature = degree_C
>
> [[Belchertown]]
>
> HTML_ROOT = /var/www/html/weewx/belchertown
>
> skin = Belchertown
>
> [[[Units]]]
>
> Groups
>
> group_altitude = meter
>
> group_degree_day = degree_C_day
>
> group_pressure = hPa
>
>     group_rain = mm
>
> group_rainrate = mm_per_hour
>
> group_speed = meter-per_second
>
> group_speed2 = meter_per_second2
>
> group_temperature = degree_C
>
>
>
>
>
> On Sun, 30 Sep 2018 at 15:22, Pat O'Brien  wrote:
>
> No shouldn't matter. Can you paste those two sections? Removing any kind
> of password or app key.
>
>
>
> The HTML_DIR needs to be the same, too
>
>
>
> On Sun, Sep 30, 2018, 10:02 AM David Hindley 
> wrote:
>
> Hi - yes to those questions, but curiously the Highcharts_Belchertown
> content in weewx.conf comes before the Belchertown content, but not sure if
> that will make any difference.
>
>
>
> David.
>
>
>
> On Sun, 30 Sep 2018 at 14:44, Pat O'Brien  wrote:
>
> I'm replying on mobile so hopefully this is helpful...
>
>
>
> How did you install the zip? Using wee_extension like in the GitHub readme?
>
>
>
> Do you have a [Belchert

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[David Hindley]

Sure.  It is below.  Thanks for looking at this.  Could it be due to
inclusion of forecast and cmon skins?  Maybe I should delete those?


[StdReport]

# Where the skins reside, relative to WEEWX_ROOT
SKIN_ROOT = /etc/weewx/skins

# Where the generated reports should go, relative to WEEWX_ROOT
HTML_ROOT = /var/www/html/weewx

# The database binding indicates which data should be used in reports.
data_binding = wx_binding

# Each of the following subsections defines a report that will be run.

[[StandardReport]]
# See the customizing guide to change the units, plot types and line
# colors, modify the fonts, display additional sensor data, and
other
# customizations. Many of those changes can be made here by
overriding
# parameters, or by modifying templates within the skin itself.

# The StandardReport uses the 'Standard' skin, which contains the
# images, templates and plots for the report.
skin = Belchertown
[[[Units]]]
Groups
group_altitude = meter
group_speed2 = meter_per_second2
group_pressure = mbar
group_rain = mm
group_rainrate = mm_per_hour
group_temperature = degree_C
group_degree_day = degree_C_day
group_speed = meter_per_second
[[forecast]]
HTML_ROOT = /var/www/html/weewx/forecast
skin = forecast
# [[exfoliation]]
#HTML_ROOT = /var/www/html/weewx/exfoliation
#   skin = exfoliation
[[cmon]]
HTML_ROOT = /var/www/html/weewx/cmon
skin = cmon
[[Highcharts_Belchertown]]
HTML_ROOT = /var/www/html/weewx/belchertown
skin = Highcharts_Belchertown
[[[Units]]]
Groups
group_altitude = meter
group_degree_day = degree_C_day
group_pressure = mbar
group_rain = mm
group_rainrate = mm_per_hour
group_speed = meter_per_second
group_speed2 = meter_per_second2
group_temperature = degree_C
[[Belchertown]]
HTML_ROOT = /var/www/html/weewx/belchertown
skin = Belchertown
[[[Units]]]
Groups
group_altitude = meter
group_degree_day = degree_C_day
group_pressure = hPa
group_rain = mm
group_rainrate = mm_per_hour
group_speed = meter-per_second
group_speed2 = meter_per_second2
group_temperature = degree_C


On Sun, 30 Sep 2018 at 15:22, Pat O'Brien  wrote:

> No shouldn't matter. Can you paste those two sections? Removing any kind
> of password or app key.
>
> The HTML_DIR needs to be the same, too
>
>
> On Sun, Sep 30, 2018, 10:02 AM David Hindley 
> wrote:
>
>> Hi - yes to those questions, but curiously the Highcharts_Belchertown
>> content in weewx.conf comes before the Belchertown content, but not sure if
>> that will make any difference.
>>
>> David.
>>
>> On Sun, 30 Sep 2018 at 14:44, Pat O'Brien  wrote:
>>
>>> I'm replying on mobile so hopefully this is helpful...
>>>
>>> How did you install the zip? Using wee_extension like in the GitHub
>>> readme?
>>>
>>> Do you have a [Belchertown] and a [Highcharts_Belchertown] in your
>>> weewx.conf?
>>>
>>> On Sun, Sep 30, 2018, 9:36 AM  wrote:
>>>
>>>> however, none of the graphs seem to be displaying.  Is there an
>>>> obvious reason why this is the case, please?
>>>>
>>>> Thanks.
>>>>
>>>> On Saturday, 29 September 2018 22:21:51 UTC+1, dhin...@djhindley.com
>>>> wrote:
>>>>>
>>>>> Thanks.  I did that and managed to get the skin installed. Looking
>>>>> great.  Thanks for your work in creating the skin. Much appreciated.
>>>>>
>>>>> On Saturday, 29 September 2018 12:13:06 UTC+1, Pat wrote:
>>>>>
>>>>> You can download the zip to your computer by using the http link in
>>>>> the wget command, then copy the zip to your Pi using FTP, SFTP or USB file
>>>>> copy. Whatever's easiest.
>>>>>
>>>>> On Saturday, September 29, 2018 at 4:05:10 AM UTC-4,
>>>>> dhin...@djhindley.com wrote:
>>>>>
>>>>> I like the look of this skin, but am failing at the first hurdle. When
>>>>> I try to download ver 0.7 tar file using wget, I get the following error:
>>>>>
>>>>> GnuTLS:A TLS fatal alert has been received.
>>>>

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[David Hindley]

Hi - yes to those questions, but curiously the Highcharts_Belchertown
content in weewx.conf comes before the Belchertown content, but not sure if
that will make any difference.

David.

On Sun, 30 Sep 2018 at 14:44, Pat O'Brien  wrote:

> I'm replying on mobile so hopefully this is helpful...
>
> How did you install the zip? Using wee_extension like in the GitHub readme?
>
> Do you have a [Belchertown] and a [Highcharts_Belchertown] in your
> weewx.conf?
>
> On Sun, Sep 30, 2018, 9:36 AM  wrote:
>
>> however, none of the graphs seem to be displaying.  Is there an
>> obvious reason why this is the case, please?
>>
>> Thanks.
>>
>> On Saturday, 29 September 2018 22:21:51 UTC+1, dhin...@djhindley.com
>> wrote:
>>>
>>> Thanks.  I did that and managed to get the skin installed. Looking
>>> great.  Thanks for your work in creating the skin. Much appreciated.
>>>
>>> On Saturday, 29 September 2018 12:13:06 UTC+1, Pat wrote:
>>>
>>> You can download the zip to your computer by using the http link in the
>>> wget command, then copy the zip to your Pi using FTP, SFTP or USB file
>>> copy. Whatever's easiest.
>>>
>>> On Saturday, September 29, 2018 at 4:05:10 AM UTC-4,
>>> dhin...@djhindley.com wrote:
>>>
>>> I like the look of this skin, but am failing at the first hurdle. When I
>>> try to download ver 0.7 tar file using wget, I get the following error:
>>>
>>> GnuTLS:A TLS fatal alert has been received.
>>> Unable to establish SSL connection.
>>>
>>> I am probably doing something dumb; any ideas on how to solve this would
>>> be much appreciated.  I am downloading it to my Raspberry pi.
>>>
>>> Thanks.
>>>
>>> On Tuesday, 21 August 2018 19:45:13 UTC+1, Pat wrote:
>>>
>>> The Belchertown skin for weewx is now available. This skin is modeled
>>> after
>>>
>>> ...
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/weewx-user/GSrKZEiPqsc/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/GSrKZEiPqsc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [weewx-user] Suggested workflow when importing data and amending the database

[David Hindley]

Gary

Many Thanks. I will try this process.  My station is a Davis Vantage Pro 2
with IP datalogger - does anyone know if this will allow weewx to
"catch-up" if the weewx service has been stopped for a while for some
database management, or will the records that would have normally been
created in the downtime, be lost?

David.

On 15 April 2018 at 04:51, Glenn McKechnie 
wrote:

> I note that you say that you know how to edit the database, so the
> following points may appear to be redundant. But for the benefit for
> someone reading this thread later, that may not have the same confidence as
> yourself,  I'll include them anyway.
>
> > should I stop the weewx service, work on the database and then start the
> weewx service again (it might take me anything between 10 mins and a few
> hours to do this).
>
> If it's the default sqlite (weewx.sdb) database then you have no option.
> If you start editing the live database you'll lock it and weewx will halt
> all writes to it.
> You say 10 minutes to an hour so you won't want that.
> .
> For others , that may or may not be a problem, but be aware of it.
>
> You can get away with copying the sqlite while weewx is running, try and
> do it during the report cycle if you feel nervous (no writes, only reads).
> If you want 100% surity then stop it, you'll have then removed another
> potentional hiccup.
>
> You can dump a mysql database while it's running. You can also edit it on
> the fly without getting into serious problems, but if you make a mistake???
> See Rule #1 below.
>
> So
> Unless you like living on the edge...
> Rule #1 says to make a copy of the database.
> Optional Rule #2 suggests to make another copy and work on that.
>
> When you've got the process down pat - ie: you're satisfied with what you
> are doing and the results are good, then you can swap over the databases.
> Or if a longtime has elapsed, make another copy, fix that with your
> recently honed process and swap it back in (with fewer values missed.)
> weewx will be stopped while you do all that.
>
> >  If I stop the service, will weewx automatically reload all the database
> entries for the time period when it was stopped in the previous step.
>
> Depends on the weather station. Some will catch up, others won't (or
> can't)
>
> See if your station gets a mention in the online documentation or tell the
> group what the station is and someone with more authority may be able to
> answer that question. Mine can't
>
> If it won't, you can dump the pre-swap database, edit and extract the new
> entries and insert them into the new copy , which shouldn't take too long -
> even with the precautions outlined above.
>
>
> Cheers
>  Glenn
>
> rorpi - read only raspberry pi & various weewx addons
> https://github.com/glennmckechnie
>
> On 15 April 2018 at 01:54,  wrote:
>
>> I am in the process of importing some data to the database and making
>> some corrections to the data once imported.  I know how to do this, but am
>> not sure what the best/recommended workflow process is.  For example:
>>
>> - should I stop the weewx service, work on the database and then start
>> the weewx service again (it might take me anything between 10 mins and a
>> few hours to do this).
>>  - If I stop the service, will weewx automatically reload all the
>> database entries for the time period when it was stopped in the previous
>> step.
>>
>> Or, should I not bother stopping the service, and if so, will this cause
>> any problems if I am working on the database whilst weewx is trying to save
>> records to it?
>>
>> Any help/tips are appreciated.
>>
>> Thanks
>>
>> David.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-user+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/3EgxZ01zaKc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [weewx-user] Re: Manually adding historical data to weewx database

[David Hindley]

Many Thanks. I had an interval field in my history, so I used that, which
seemed to work OK.  I have successfully loaded the 2018 history; now the
rest.

David.

On Sat, 14 Apr 2018 at 00:46, gjr80  wrote:

> David,
>
> Perhaps a bit late but the answer is it depends. 'derive' will attempt to
> derive the interval from the incoming data, it's not a very sophisticated
> algorithm, it is simply the difference in timestamps of successive records.
> So derive can suffer if you have big gaps. 'conf' will use the archive
> interval in your weewx.conf (or whatever weeWX config file wee_import is
> told to use). This will be fine if all of your source data say came from
> weeWX and uses the same interval as the archive interval specified in
> weewx.conf. The advantage here is that large data gaps don't have the
> disruptive impact they did with 'derive'. Of course the downside is that
> your source data and weewx.conf may have different intervals. 'x' (where x
> is the number of minutes) allows you to force all imported records to use x
> as the interval. Again this can be handy if your source data has a fixed
> interval but there are large data gaps. Also useful for importing tranches
> of source data that may have different intervals.
>
> In summary - beware of 'derive', you really need a good solid (regular)
> data source for it to be effective.
>
> You will find the interval config option
>  described in the wee_import
> section of the Utilities Guide .
>
> Gary
>
>
> On Friday, 13 April 2018 18:22:49 UTC+10, dhin...@djhindley.com wrote:
>>
>> Gary
>>
>> Many Thanks for your very helpful reply.  So which setting do I use for
>> the archive interval in the config file? "derive" seems the most logical,
>> but the instructions say that "derive" is suitable when the data was
>> recorded at fixed intervals.
>>
>> I do have some gaps in my data - up to two weeks in some cases.  I plan
>> to try to fill as many of these gaps as possible using a combination of
>> downloaded data from weathercloud (for my weather station) and also using
>> the Met office's 5km grid data as a suitable proxy (for the grid containing
>> my PWS).  I will attempt to process this all into a single archive database
>> using R software and then use weewx import. If I need to take up your kind
>> offer of a Weatherlink import module, I will let you know.
>>
>> David.
>>
>> On Friday, 13 April 2018 02:37:20 UTC+1, gjr80 wrote:
>>>
>>> David,
>>>
>>> Variable archive intervals have been supported since weeWX v3.0.0,
>>> though I believe there was a display/report calculation bug that was
>>> addressed in 3.7.0 (of course we are all running 3.8.0 so neither of these
>>> should be an issue :))
>>>
>>> One thing to be mindful of when using wee_import to import data is that
>>> when you are deriving the archive interval from the source data (ie finding
>>> the difference between successive timestamps) missing records can skew this
>>> significantly. A single missing record in a data set with an interval of 5
>>> minutes will likely have negligible effect but if you have several hours or
>>> days missing it may be a different matter. For this reason when importing
>>> from WeatherUnderground if your WeatherUndergroud data was posted every 10
>>> minutes it is quite often handy to force wee_import to use a 10 minute
>>> archive interval as WeatherUnderground often does not return all available
>>> data, plus it is not unusual for users to have large gaps in their
>>> WeatherUnderground data.
>>>
>>> If you have a changing archive interval in your data and are concerned
>>> about data gaps, it might be useful to break the import down into smaller
>>> chunks that use a single archive interval and import that data with a set
>>> rather derived interval.
>>>
>>> Gary
>>>
>>> PS. If there is significant reformatting required to import the
>>> ex-WeatherLink data I am happy to put together a WeatherLink module for
>>> wee_import, I will just need to know the data format. Only thing is it will
>>> take time for me to put the module together, though I guess your old data
>>> is not going anywhere :)
>>>
>>> On Friday, 13 April 2018 01:16:54 UTC+10, Andrew Milner wrote:

 As far as I know the latest version of weewx casn handle variable
 intervals- so just let wee_import derive the interval from the time stamps*
 should* work (I think!!)

 someone more knowledgeable maywish to comment 



 On Thursday, 12 April 2018 17:59:03 UTC+3, dhin...@djhindley.com wrote:

> The import facility looks like the right way to go - but unfortunately
> my source data has variable archive intervals. Is there any way of dealing
> with this in the weewx import utlility, or is it best to convert all the
> source data to have the same archive interval (painful!)?
>
> Thanks.
>
> On Wednesday, 11 April 2018 17:45:19 UTC+1, dhin

Re: [weewx-user] Re: Manually adding historical data to weewx database

[David Hindley]

The data has been downloaded to a text file from the WeatherLink software,
stores in a txt file on my Windows PC.

David.

On Wed, 11 Apr 2018 at 18:05, Andrew Milner 
wrote:

> where is the historical data kept??
>
>
>
> On Wednesday, 11 April 2018 19:45:19 UTC+3, dhin...@djhindley.com wrote:
>
>> Hi
>>
>> I have just started using weewx on a Raspberry Pi with a Davis Vantage
>> using Weatherlink IP. The weather station has been running for 2 years, but
>> I only got weewx working from today. All is working fine, except that since
>> I updated my archive record to 5mins immediately prior to the installation,
>> weewx only shows the recent records. Does anyone know if there is a way I
>> can manually add the historical data to the weewx database, so that the
>> full history is shown on my weewx webpage?
>>
>> Thanks
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/VCwuWaT2kwY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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