RE: [weewx-user] Re: Installation/configuration issues (WeeWx on a Raspberry Pi4)

[garryalockyer]

Thanks.

 

I don’t see anything obviously wrong.

 

I would:

 

*   Go back to using the Simulator

*   In weewx.conf, change station_type to Simulator.

 

*   Verify that weewx is starting correctly:

*   sudo /etc/init.d/weewx start
*   tail -f /var/log/syslog

*   Fix any errors reported in syslog

 

*   Verify that web page are being generated

*   2 -5 minutes after starting WeeWX, depending up the driver/device 
settings, you should see log entries indicating that reports are being 
generated.
*   Open /var/www/html/weewx/index.html in a web browser on the same system 
(so that a web server is not required).
*   Refresh webpage after 2-5 minutes (or when syslog indicates WeeWX has 
started up another reporting cycle) to verify the web pages are being 
updated/regenerated.

 

*   After getting webpages reliably generated and updated, change to the 
desired driver

*   sudo /etc/init.d/weewx stop
*   In weewx.conf, change station_type to “some other driver”
*   sudo /etc/init.d/weewx start
*   monitor syslog: tail -f /var/log syslog
*   If web pages do not get generated, there’s a problem with the driver, 
or more likely, it’s set up.

 

You only need a web server such as Apache and to open ports on your firewall if 
you want that system to serve pages to the public side of your firewall.  If 
you want another server to serve the pages, you FTP the pages from 
/var/www/html/weewx to the other server.

 

You can delete everything in /var/www/html/weewx – files there are regenerated 
every reporting cycle.  If you delete everything and they reappear, you know 
that WeeWX is at least generating and moving some files.

 

Regards,

 

Garry

 

From: weewx-user@googlegroups.com  On Behalf Of 
Stuart Beaumont
Sent: June 19, 2020 1:08 PM
To: weewx-user 
Subject: [weewx-user] Re: Installation/configuration issues (WeeWx on a 
Raspberry Pi4)

 

Here you go Garry. Thanks.



On Tuesday, June 16, 2020 at 5:14:13 PM UTC+2, Stuart Beaumont wrote:

Evening all

 

I'm having a few challenges with an installation and configuration of weewx on 
a Raspberry Pi. Here is an overview of what im trying to do and what ive done:

 

Ive got a WH6006 Weather Station. It is a cellular system in that it connects 
to the internet with mobile data. I'm wanting to connect it to a Pi4 running 
Weewx. Initially i want to be able to monitor the weather using Weewx, but 
ultimately i need to get the data off the weather station in excel or csv 
format and save it to OneDrive. From there i'll use Power Query to process it.

 

After a few attempts i had managed to get Weewx running on the Pi with the 
Simulator (but now that seems to have stopped too??). I have installed the 
Interceptor driver, but at that time i was still getting Simulator data, 
despite making the necessary changes to the config file. (station-type = 
interceptor)

 

I've set up a (temporary) DNS and configured the router/modem.

 

I've set up port forwarding on the router for the Pi. Also added port = 8000 to 
the config file.

 

The challenge i'm having is i still cant get the console to talk to Weewx.

 

Ive set device_type = observer

 

I stopped and restarted weewx a number of times to effect the changes.

 

I'm a novice with this stuff but got some great help from gelfert back on the 
wxforum. He's been great.

 

Lastly, i have managed to get the station to upload to WU and retrieve the data 
with the API. Its works, but not the ideal system. Its fine for a backup.

 

Any help in completing my configuration would be really great.

-- 
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/ec55e87f-2721-474c-86b2-24615b671b2fo%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/037301d64685%24af31cec0%240d956c40%24%40gmail.com.

Re: [weewx-user] Re: Small Python 'daemon' script to check if weewx is running

[Constantine Samaklis]

Yes, that is correct. The idea is that there is something really going
wrong if you have this happening multiple times. (You can bypass that by
setting the restarts in the config to a higher number but I would not
advise to do so)

If it is a one off, then resetting the number in the flag file to 0 would
work best and is a safer approach.

On Fri, Jun 19, 2020 at 5:04 PM James Bellanca  wrote:

> I know this threads a little old, but thanks for the script. I just
> implemented it now.
>
> It appears that after it detects WeeWx is down, it restarts it, but then
> leaves the weewxNotRunning.txt file out there with the number of retries in
> it. So, say it has to restart WeeWx, successfully does so, and a week later
> does it again, etc. After the 3rd week, because it counts as a "retry" and
> the file's left out there, it will stop. So, in other words, you have to
> know, if you get the email, make sure you go out there and delete
> the weewxNotRunning.txt manually to reset the counter, or it'll stop
> working after the 3rd time it happens. I'm not missing anything, right?
>
>
> On Friday, September 13, 2013 at 7:44:28 PM UTC-4, Constantine Samaklis
> wrote:
>>
>> I thought I would give something back to the group since I have gotten
>> good help to my questions. I have created a Python utility script that can
>> be ran periodically (cron?) to check if weewx is running and if it is not,
>> it will send out an email with a number of lines from the end of the log
>> (/var/log/messages, or whatever log you want) that would show the error
>> that weewx encountered. The script will try to restart weex a number of pre
>> configurable times, in case the error was a fluke rather than a fatal one.
>>
>> The script will stop trying to send messages after it has reached the
>> indicated *restarts* times in the configuration times, and you will need
>> to delete the *flagFile* that has been created. (or write a 0 in it).
>> The script has a configurable log rotation, where you can indicate the log
>> rotation interval (in days) and the days of logs to keep.
>>
>> *logOutput* is the temporary tail of the messages log (or could be the
>> syslog or whatever you specify) that will be emailed as an attachment if
>> weewx is found not to be running.
>>
>> I hope everyone finds this somewhat useful. If you are somewhat paranoid
>> about your weather station being up 24/7 like me then you probably will. :-)
>>
>> Questions and comments are welcome.
>>
>>
>> #configuration file for checking routine
>> [mail]
>> fromaddr=us...@gmail.com
>> toaddr=tou...@gmail.com
>> msgSubj=weewx process is not running
>> body=weewx process is not running. Please check the attached log and
>> address the issue
>> userName=gmailu...@gmail.com
>> password=yourPwd
>> smtpServer=smtp.gmail.com:587
>>
>> [logging]
>> logDir=/home/user/scripts
>> logFile=checkWeewx.log
>> logOutput=tail.log
>> linesToTail=200
>> logToTail=/var/log/messages
>> logRotationDayInterval=1
>> logDaysToKeep=5
>>
>> [weewx]
>> #how many times to try and restart the weewx process
>> restarts=3
>> flagLogDir=/home/user/scripts
>> flagFile=weewxNotRunning.txt
>> startCommand=sudo /etc/init.d/weewx start
>>
>> You can launch the script by typing: Python ./checkWeewx.py
>> /pathToConfigFile/checkWeewx.config
>>
>> The configuration format:
>>
>> #configuration file for checking routine
>> [mail]
>> fromaddr=us...@gmail.com
>> toaddr=tou...@gmail.com
>> msgSubj=weewx process is not running
>> body=weewx process is not running. Please check the attached log and
>> address the issue
>> userName=gmailu...@gmail.com
>> password=yourPwd
>> smtpServer=smtp.gmail.com:587
>>
>> [logging]
>> logDir=/home/user/scripts
>> logFile=checkWeewx.log
>> logOutput=tail.log
>> linesToTail=200
>> logToTail=/var/log/messages
>> logRotationDayInterval=1
>> logDaysToKeep=5
>>
>> [weewx]
>> #how many times to try and restart the weewx process
>> restarts=3
>> flagLogDir=/home/user/scripts
>> flagFile=weewxNotRunning.txt
>> startCommand=sudo /etc/init.d/weewx start
>>
> --
> 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/9yskDGu9vI0/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/3e10898a-5ec9-4ee1-b4ea-aceb85e8602ao%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 

[weewx-user] Re: Small Python 'daemon' script to check if weewx is running

[James Bellanca]

I know this threads a little old, but thanks for the script. I just 
implemented it now.

It appears that after it detects WeeWx is down, it restarts it, but then 
leaves the weewxNotRunning.txt file out there with the number of retries in 
it. So, say it has to restart WeeWx, successfully does so, and a week later 
does it again, etc. After the 3rd week, because it counts as a "retry" and 
the file's left out there, it will stop. So, in other words, you have to 
know, if you get the email, make sure you go out there and delete 
the weewxNotRunning.txt manually to reset the counter, or it'll stop 
working after the 3rd time it happens. I'm not missing anything, right?


On Friday, September 13, 2013 at 7:44:28 PM UTC-4, Constantine Samaklis 
wrote:
>
> I thought I would give something back to the group since I have gotten 
> good help to my questions. I have created a Python utility script that can 
> be ran periodically (cron?) to check if weewx is running and if it is not, 
> it will send out an email with a number of lines from the end of the log 
> (/var/log/messages, or whatever log you want) that would show the error 
> that weewx encountered. The script will try to restart weex a number of pre 
> configurable times, in case the error was a fluke rather than a fatal one.
>
> The script will stop trying to send messages after it has reached the 
> indicated *restarts* times in the configuration times, and you will need 
> to delete the *flagFile* that has been created. (or write a 0 in it). The 
> script has a configurable log rotation, where you can indicate the log 
> rotation interval (in days) and the days of logs to keep. 
>
> *logOutput* is the temporary tail of the messages log (or could be the 
> syslog or whatever you specify) that will be emailed as an attachment if 
> weewx is found not to be running.
>
> I hope everyone finds this somewhat useful. If you are somewhat paranoid 
> about your weather station being up 24/7 like me then you probably will. :-)
>
> Questions and comments are welcome.
>
>
> #configuration file for checking routine
> [mail]
> fromaddr=us...@gmail.com 
> toaddr=tou...@gmail.com 
> msgSubj=weewx process is not running
> body=weewx process is not running. Please check the attached log and 
> address the issue
> userName=gmailu...@gmail.com 
> password=yourPwd
> smtpServer=smtp.gmail.com:587
>
> [logging]
> logDir=/home/user/scripts
> logFile=checkWeewx.log
> logOutput=tail.log
> linesToTail=200
> logToTail=/var/log/messages
> logRotationDayInterval=1
> logDaysToKeep=5
>
> [weewx]
> #how many times to try and restart the weewx process
> restarts=3
> flagLogDir=/home/user/scripts
> flagFile=weewxNotRunning.txt
> startCommand=sudo /etc/init.d/weewx start
>
> You can launch the script by typing: Python ./checkWeewx.py 
> /pathToConfigFile/checkWeewx.config
>
> The configuration format:
>
> #configuration file for checking routine
> [mail]
> fromaddr=us...@gmail.com 
> toaddr=tou...@gmail.com 
> msgSubj=weewx process is not running
> body=weewx process is not running. Please check the attached log and 
> address the issue
> userName=gmailu...@gmail.com 
> password=yourPwd
> smtpServer=smtp.gmail.com:587
>
> [logging]
> logDir=/home/user/scripts
> logFile=checkWeewx.log
> logOutput=tail.log
> linesToTail=200
> logToTail=/var/log/messages
> logRotationDayInterval=1
> logDaysToKeep=5
>
> [weewx]
> #how many times to try and restart the weewx process
> restarts=3
> flagLogDir=/home/user/scripts
> flagFile=weewxNotRunning.txt
> startCommand=sudo /etc/init.d/weewx start
>

-- 
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/3e10898a-5ec9-4ee1-b4ea-aceb85e8602ao%40googlegroups.com.

[weewx-user] Re: Installation/configuration issues (WeeWx on a Raspberry Pi4)

[Stuart Beaumont]

Here you go Garry. Thanks.


On Tuesday, June 16, 2020 at 5:14:13 PM UTC+2, Stuart Beaumont wrote:
>
> Evening all
>
> I'm having a few challenges with an installation and configuration of 
> weewx on a Raspberry Pi. Here is an overview of what im trying to do and 
> what ive done:
>
> Ive got a WH6006 Weather Station. It is a cellular system in that it 
> connects to the internet with mobile data. I'm wanting to connect it to a 
> Pi4 running Weewx. Initially i want to be able to monitor the weather using 
> Weewx, but ultimately i need to get the data off the weather station in 
> excel or csv format and save it to OneDrive. From there i'll use Power 
> Query to process it.
>
> After a few attempts i had managed to get Weewx running on the Pi with the 
> Simulator (but now that seems to have stopped too??). I have installed the 
> Interceptor driver, but at that time i was still getting Simulator data, 
> despite making the necessary changes to the config file. (station-type = 
> interceptor)
>
> I've set up a (temporary) DNS and configured the router/modem.
>
> I've set up port forwarding on the router for the Pi. Also added port = 
> 8000 to the config file.
>
> The challenge i'm having is i still cant get the console to talk to Weewx.
>
> Ive set device_type = observer
>
> I stopped and restarted weewx a number of times to effect the changes.
>
> I'm a novice with this stuff but got some great help from gelfert back on 
> the wxforum. He's been great.
>
> Lastly, i have managed to get the station to upload to WU and retrieve the 
> data with the API. Its works, but not the ideal system. Its fine for a 
> backup.
>
> Any help in completing my configuration would be really great.
>

-- 
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/ec55e87f-2721-474c-86b2-24615b671b2fo%40googlegroups.com.
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2019 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 0

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 4.1.1

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = KwaWula Game Estate

# Latitude in decimal degrees. Negative for southern hemisphere
latitude = -29.461403
# Longitude in decimal degrees. Negative for western hemisphere.
longitude = 30.258868

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 1156, meter

# Set to type of station hardware. There must be a corresponding stanza
# in this file with a 'driver' parameter indicating the driver to be used.
station_type = Interceptor

# If you have a website, you may specify an URL
#station_url = http://www.example.com

# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1

# Start of week (0=Monday, 6=Sunday)
week_start = 0

##

[Interceptor]
# This section is for the network traffic interceptor driver.

# The driver to use:
driver = user.interceptor

# Specify the hardware device to capture.  Options include:
#   acurite-bridge - acurite internet bridge, smarthub, or access
#   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
#   lw30x - oregon scientific LW301/LW302
#   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
#   ecowitt-client - any hardware that uses the ecowitt protocol
#   wu-client - any hardware that uses the weather underground protocol
device_type = wu-client
port = 8000

##

[Simulator]
# This section is for the weewx weather station simulator

# The time (in seconds) between LOOP packets.
loop_interval = 2.5

# The simulator mode can be either 'simulator' or 'generator'.
# Real-time simulator. Sleep between each LOOP packet.

Re: [weewx-user] Re: Installation/configuration issues (WeeWx on a Raspberry Pi4)

[Garry A Lockyer]

I think you should post your weewx.conf, without any passwords. It should 
provide the information needed to assist you.

Regards,

Garry Lockyer
C: +1.250.689.0686
E: ga...@lockyer.ca


> On Jun 19, 2020, at 12:38, Stuart Beaumont  wrote:
> 
> 
> I've made some good progress here. I've set up a Public IP and configured the 
> console with it. The data is now reaching the pi and updating the weewx.sdb 
> file. I confirmed this by looking at the file with DB Browser.
> 
> I then installed the Apache web server. (was this necessary?)
> 
> When i open the station webpage via file:///var/www/html/weewx/index.html or 
> via http://localhost/weewx i dont get any data being reported. Current 
> Conditions are all N/A.
> 
> To recap, i have set the device_type = wu-client
> 
> Attached is my weewx.sdb file
> 
> As a double check i have configured the weewx.conf file to send the data to 
> Wunderground to a dummy station. The station is live, so the data is being 
> sent there, but again, there is no data populating the charts etc.
> 
> Any suggestions? I feel i'm really close now.
> 
> 
> 
> 
>> On Tuesday, June 16, 2020 at 5:14:13 PM UTC+2, Stuart Beaumont wrote:
>> Evening all
>> 
>> I'm having a few challenges with an installation and configuration of weewx 
>> on a Raspberry Pi. Here is an overview of what im trying to do and what ive 
>> done:
>> 
>> Ive got a WH6006 Weather Station. It is a cellular system in that it 
>> connects to the internet with mobile data. I'm wanting to connect it to a 
>> Pi4 running Weewx. Initially i want to be able to monitor the weather using 
>> Weewx, but ultimately i need to get the data off the weather station in 
>> excel or csv format and save it to OneDrive. From there i'll use Power Query 
>> to process it.
>> 
>> After a few attempts i had managed to get Weewx running on the Pi with the 
>> Simulator (but now that seems to have stopped too??). I have installed the 
>> Interceptor driver, but at that time i was still getting Simulator data, 
>> despite making the necessary changes to the config file. (station-type = 
>> interceptor)
>> 
>> I've set up a (temporary) DNS and configured the router/modem.
>> 
>> I've set up port forwarding on the router for the Pi. Also added port = 8000 
>> to the config file.
>> 
>> The challenge i'm having is i still cant get the console to talk to Weewx.
>> 
>> Ive set device_type = observer
>> 
>> I stopped and restarted weewx a number of times to effect the changes.
>> 
>> I'm a novice with this stuff but got some great help from gelfert back on 
>> the wxforum. He's been great.
>> 
>> Lastly, i have managed to get the station to upload to WU and retrieve the 
>> data with the API. Its works, but not the ideal system. Its fine for a 
>> backup.
>> 
>> Any help in completing my configuration would be really great.
> 
> -- 
> 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/1e28eed4-5d5c-43ce-92fc-eec3224754dbo%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/DE5B464D-A85B-472B-B7D8-9E19CE7F7D03%40gmail.com.

Re: [weewx-user] Re: Full day highcharts question

[Pat]

No, not sure. I assume it's because the data points aren't reset to "None" 
using this new way of getting data for the rain observation?

Gary - did you create an issue for this? I'd hate to patch something in the 
skin to only undo it if/when Tom properly patches this.

On Friday, June 19, 2020 at 1:06:11 PM UTC-4, didier@gmail.com wrote:
>
> Oh, just a small problem:
> For Rain graph, the curve continue after "now"! (screenshot attached)
> All others curves stop at datetime=now, it's correct)
> The problem concern "rainTotal" and is also available for day, week, month 
> and year time_length
> Have you an idea?
>
> hereafter the part of grah.conf
>
> [week]
> # Chart Timespan Defaults
> title = "Cette semaine"
> show_button = true
> button_text = "SEMAINE"
> time_length = week
> tooltip_date_format = ""
> type = spline
> aggregate_type = max
> aggregate_interval = 3600 # 1 hour
> gapsize = 360 # 1 hour in milliseconds
>
> [[chart1]]
> title = Température
> [[[outTemp]]]
> color = "#b2df8a"
> [[[dewpoint]]]
> yAxis_label = ( °C )
> yAxis_tickInterval = 2
> yAxis_softMin = 0
> 
> [[chart2]]
> title = Pluie
> [[[rainTotal]]]  < Problem
> color = "#f7a35c"
> name = Cumul
> [[[rain]]]
> color = "#268bd2"
> aggregate_type = sum
> name = pluie
> type = column
> yAxis_tickInterval = 1
> yAxis_label = ( mm )
> yAxis_min = 0
>
>
> Le lundi 15 juin 2020 à 14:58:26 UTC+2, Pat a écrit :
>
>> Awesome! Glad that it worked for you
>>
>>
>> On Monday, June 15, 2020 at 5:29:59 AM UTC-4, didier@gmail.com wrote:
>>>
>>> Thanks it's work 
>>>
>>>
>>> Le lundi 15 juin 2020 à 11:12:27 UTC+2, Manfred Maier a écrit :
>>>
 Thanks, Gary, for this comprehensive explanation.

 Based on what you wrote I was now able to plot an entire day.

 [image: Bildschirmfoto 2020-06-15 um 11.07.53.png]

 The trick is quite simple: I just had to define an aggregation for the 
 daily charts. I.e. adding the following two lines to the graphs.conf:

 aggregate_type = max

 aggregate_interval = 300





-- 
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/0d89abe0-f383-486e-8ace-6f3ecc0e543eo%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Pat]

This looks like it's a mismatch setting with gapSize 


On Friday, June 19, 2020 at 10:35:32 AM UTC-4, Manfred Maier wrote:
>
> Switching back to English, since I guess we need the help of Pat here.
>
> @Pat 
> Have you seen the following issue before?
> There is data behind the Highcharts and individual data points are 
> displayed, but somehow the line seems to be set to 'hidden'.
> Is there anything wring in the graphs.conf?
>
> Here is an example screenshot.
>
>
>
> geni08...@gmail.com schrieb am Freitag, 19. Juni 2020 um 16:23:39 UTC+2:
>
>> Gratuliere, der Schuss ging ins schwarze!
>> Im skin.conf habe ich auto
>> Der Raspberry lief natürlich für mich lokal auf de_CH.UTF-8
>> ich habe diesen nun auf de_DE.UTF-8 geändert und schon hatte ich das 
>> Zuletzt aktualisiert und Charts.
>> Die Charts sind leider teilweise leer?
>>
>>
>> Am Freitag, 19. Juni 2020 15:25:44 UTC+2 schrieb Manfred Maier:
>>>
>>> Das ist jetzt ein Schuss ins Blaue (vielleicht treffe ich aber):
>>> Welche "belchertown_locale" hast Du angegeben? Bzw. in welcher 
>>> "Locale"Einstellung läuft Dein Rechner?
>>>
>>> In der besagten Belchertown.js auf Deinem Webserver steht in Zeile 507:
>>>thousandsSep: '''
>>>
>>> Es sieht so aus, als würde ein Hochkomma als Tausender-Punkt verwendet. 
>>> Der Browser fällt hier wohl drüber (3 Hochkommas nacheinander).
>>>
>>> Der Tausender-Seperator ist eigentlich automatisch von der Locale 
>>> gesteuert.
>>>  
>>>
>>> Manfred Maier schrieb am Freitag, 19. Juni 2020 um 15:01:48 UTC+2:
>>>
 Ich hab mir Deine Website jetzt mal angesehen.
 Es sieht so aus, als hättest Du ein Problem mit Deiner 
 Belchertown.js.tmpl

 Hast Du da mal etwas geändert?

 Wenn ich die Fehlermeldung richtig interpretiere, gibt es ein Problem 
 bei Zeile 506. Das EOF bedeutet meiner Meinung nach, dass das File hier 
 endet?
 Wie viele Zeilen hat Deine Belchertown.js.tmpl?



 Manfred Maier schrieb am Freitag, 19. Juni 2020 um 13:14:23 UTC+2:

> Ist bei mir in der index_hook_after_charts.inc drin.
>
>
> 1) Datei (index_hook_after_charts.inc) im Belchertown-Verzeichnis 
> anlegen
> 2) den folgenden Code reinkopieren
> 3) In der weewx.conf (Belchertown -Section) einschalten, dass der 
> Index-Hook alle 300 Sekunden (oder auch weniger oft) neu geladen wird.
> 4) Noch den iframe aus meinem Code für Deinen Standort anpassen (den 
> Code gibt's auf Meteoblue unter Website-Widgets).
>
> 
> 
> 
> https://www.meteoblue.com/de/wetter/widget/three/zorneding_deutschland_2803884?geoloc=fixed=1=0=7=CELSIUS=KILOMETER_PER_HOUR=image;
>  
>  frameborder="0" scrolling="YES" allowtransparency="true" 
> sandbox="allow-same-origin allow-scripts allow-popups 
> allow-popups-to-escape-sandbox" style="width: 100%; height: 525px; 
> padding-left: 16px; padding-right: 16px">
> 
> 
>
>

-- 
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/e49723ad-7de2-418e-8e6e-93a496204469o%40googlegroups.com.

[weewx-user] Suggestions on best way to upgrade to 4.1.1

[michael form]

I have Weewx 3.92 running on a Raspberry  Pi3 using One-Wire sensors for 
all measurements via a USB to 1-Wire interface (DS9490). The Pi is running 
Buster and I installed Weewx using the Debian installation package. 
Everything is now working fine and I want to tempt fate by upgrading to 
Weewx 4.1.1 (and Python 3).

What is the easiest and most reliable way to do this? Do I just install 
Weewx again on the same Pi using the procedure for an initial install of 
the Debian package? Will it keep the database and conf files or do I have 
to save them and put them back when done? Do I need to do anything with 
OWFS to work with Python 3? Should I follow the procedure in installation 
guide:

Tell your system to trust weewx.com:

wget -qO - http://weewx.com/keys.html | sudo apt-key add -

For Debian10 and later, use python3:

wget -qO - http://weewx.com/apt/weewx-python3.list | sudo tee 
/etc/apt/sources.list.d/weewx.list


Basically, how best to upgrade without losing the old data and keeping 
things working?

Thanks for any guidance.

Michael

-- 
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/ff7326d5-d1cf-4523-b963-eb9104dc1e0fo%40googlegroups.com.

[weewx-user] Database deadlock during database backup

[Luc Heijst]

My weewx application TFRC crashed during the backup of the database, see 
logging below.

Weewx version: 4.1.1
Python version: 3.7.3.
on Raspberry PI 3B+

Database: MariaDB 10.3.21-0063 on Synology NAS in the same local network

Usually a weewx program continues after the short period a database is not 
available (duration typically 90 seconds or less), but this time a database 
deadlock occurred.

Note: I did not set "loop_on_init = True" in weewx_tfrc.conf, but I wonder 
if weewx was restarted in this case if I did include the loop_on_init 
command.

Luc


Jun 16 03:10:20 pi31 tfrc[490] INFO user.tfrc: shutdown process 
/home/weewx/tfrec/tfrec -D -T 1
Jun 16 03:10:20 pi31 tfrc[490] INFO user.tfrc: tfrec with pid 6712 killed
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__: Caught unrecoverable 
exception:
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   (1213, 
'Deadlock found when trying to get lock; try restarting transaction')
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   Traceback (most 
recent call last):
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__: File 
"/home/weewx/bin/weewx/engine.py", line 195, in run
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   
self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__: File 
"/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   
callback(event)
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__: File 
"/home/weewx/bin/weewx/engine.py", line 578, in check_loop
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   raise 
BreakLoop
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   
weewx.engine.BreakLoop
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   During handling 
of the above exception, another exception occurred:
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   Traceback (most 
recent call last):
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__: File 
"/home/weewx/bin/weewx/engine.py", line 594, in post_loop
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   
self._catchup(self.engine.console.genArchiveRecords)
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__: File 
"/home/weewx/bin/weewx/engine.py", line 638, in _catchup
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   for record 
in generator(lastgood_ts):
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__: File 
"/home/weewx/bin/weewx/drivers/__init__.py", line 30, in genArchiveRecords
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   raise 
NotImplementedError("Method 'genArchiveRecords' not implemented")
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   
NotImplementedError: Method 'genArchiveRecords' not implemented
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   During handling 
of the above exception, another exception occurred:
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   Traceback (most 
recent call last):
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__: File 
"/home/weewx/bin/weedb/mysql.py", line 52, in guarded_fn
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   return 
fn(*args, **kwargs)
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__: File 
"/home/weewx/bin/weedb/mysql.py", line 262, in execute
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   
self.cursor.execute(mysql_string, tuple(sql_tuple))
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__: File 
"/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 250, in execute
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   
self.errorhandler(self, exc, value)
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__: File 
"/usr/lib/python3/dist-packages/MySQLdb/connections.py", line 50, in 
defaulterrorhandler
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   raise 
errorvalue
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__: File 
"/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 247, in execute
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   res = 
self._query(query)
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__: File 
"/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 411, in _query
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   rowcount = 
self._do_query(q)
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__: File 
"/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 374, in _do_query
Jun 16 03:10:20 pi31 tfrc[490] CRITICAL __main__:   

[weewx-user] Re: Belchertown no charts

[Manfred Maier]

Switching back to English, since I guess we need the help of Pat here.

@Pat 
Have you seen the following issue before?
There is data behind the Highcharts and individual data points are 
displayed, but somehow the line seems to be set to 'hidden'.
Is there anything wring in the graphs.conf?

Here is an example screenshot.



geni08...@gmail.com schrieb am Freitag, 19. Juni 2020 um 16:23:39 UTC+2:

> Gratuliere, der Schuss ging ins schwarze!
> Im skin.conf habe ich auto
> Der Raspberry lief natürlich für mich lokal auf de_CH.UTF-8
> ich habe diesen nun auf de_DE.UTF-8 geändert und schon hatte ich das 
> Zuletzt aktualisiert und Charts.
> Die Charts sind leider teilweise leer?
>
>
> Am Freitag, 19. Juni 2020 15:25:44 UTC+2 schrieb Manfred Maier:
>>
>> Das ist jetzt ein Schuss ins Blaue (vielleicht treffe ich aber):
>> Welche "belchertown_locale" hast Du angegeben? Bzw. in welcher 
>> "Locale"Einstellung läuft Dein Rechner?
>>
>> In der besagten Belchertown.js auf Deinem Webserver steht in Zeile 507:
>>thousandsSep: '''
>>
>> Es sieht so aus, als würde ein Hochkomma als Tausender-Punkt verwendet. 
>> Der Browser fällt hier wohl drüber (3 Hochkommas nacheinander).
>>
>> Der Tausender-Seperator ist eigentlich automatisch von der Locale 
>> gesteuert.
>>  
>>
>> Manfred Maier schrieb am Freitag, 19. Juni 2020 um 15:01:48 UTC+2:
>>
>>> Ich hab mir Deine Website jetzt mal angesehen.
>>> Es sieht so aus, als hättest Du ein Problem mit Deiner 
>>> Belchertown.js.tmpl
>>>
>>> Hast Du da mal etwas geändert?
>>>
>>> Wenn ich die Fehlermeldung richtig interpretiere, gibt es ein Problem 
>>> bei Zeile 506. Das EOF bedeutet meiner Meinung nach, dass das File hier 
>>> endet?
>>> Wie viele Zeilen hat Deine Belchertown.js.tmpl?
>>>
>>>
>>>
>>> Manfred Maier schrieb am Freitag, 19. Juni 2020 um 13:14:23 UTC+2:
>>>
 Ist bei mir in der index_hook_after_charts.inc drin.


 1) Datei (index_hook_after_charts.inc) im Belchertown-Verzeichnis 
 anlegen
 2) den folgenden Code reinkopieren
 3) In der weewx.conf (Belchertown -Section) einschalten, dass der 
 Index-Hook alle 300 Sekunden (oder auch weniger oft) neu geladen wird.
 4) Noch den iframe aus meinem Code für Deinen Standort anpassen (den 
 Code gibt's auf Meteoblue unter Website-Widgets).

 
 
 
 https://www.meteoblue.com/de/wetter/widget/three/zorneding_deutschland_2803884?geoloc=fixed=1=0=7=CELSIUS=KILOMETER_PER_HOUR=image;
  
  frameborder="0" scrolling="YES" allowtransparency="true" 
 sandbox="allow-same-origin allow-scripts allow-popups 
 allow-popups-to-escape-sandbox" style="width: 100%; height: 525px; 
 padding-left: 16px; padding-right: 16px">
 
 



-- 
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/76558996-bdbe-4120-82b6-1d92afaec910n%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Geni 0815]

Gratuliere, der Schuss ging ins schwarze!
Im skin.conf habe ich auto
Der Raspberry lief natürlich für mich lokal auf de_CH.UTF-8
ich habe diesen nun auf de_DE.UTF-8 geändert und schon hatte ich das 
Zuletzt aktualisiert und Charts.
Die Charts sind leider teilweise leer?


Am Freitag, 19. Juni 2020 15:25:44 UTC+2 schrieb Manfred Maier:
>
> Das ist jetzt ein Schuss ins Blaue (vielleicht treffe ich aber):
> Welche "belchertown_locale" hast Du angegeben? Bzw. in welcher 
> "Locale"Einstellung läuft Dein Rechner?
>
> In der besagten Belchertown.js auf Deinem Webserver steht in Zeile 507:
>thousandsSep: '''
>
> Es sieht so aus, als würde ein Hochkomma als Tausender-Punkt verwendet. 
> Der Browser fällt hier wohl drüber (3 Hochkommas nacheinander).
>
> Der Tausender-Seperator ist eigentlich automatisch von der Locale 
> gesteuert.
>  
>
> Manfred Maier schrieb am Freitag, 19. Juni 2020 um 15:01:48 UTC+2:
>
>> Ich hab mir Deine Website jetzt mal angesehen.
>> Es sieht so aus, als hättest Du ein Problem mit Deiner Belchertown.js.tmpl
>>
>> Hast Du da mal etwas geändert?
>>
>> Wenn ich die Fehlermeldung richtig interpretiere, gibt es ein Problem bei 
>> Zeile 506. Das EOF bedeutet meiner Meinung nach, dass das File hier endet?
>> Wie viele Zeilen hat Deine Belchertown.js.tmpl?
>>
>>
>>
>> Manfred Maier schrieb am Freitag, 19. Juni 2020 um 13:14:23 UTC+2:
>>
>>> Ist bei mir in der index_hook_after_charts.inc drin.
>>>
>>>
>>> 1) Datei (index_hook_after_charts.inc) im Belchertown-Verzeichnis anlegen
>>> 2) den folgenden Code reinkopieren
>>> 3) In der weewx.conf (Belchertown -Section) einschalten, dass der 
>>> Index-Hook alle 300 Sekunden (oder auch weniger oft) neu geladen wird.
>>> 4) Noch den iframe aus meinem Code für Deinen Standort anpassen (den 
>>> Code gibt's auf Meteoblue unter Website-Widgets).
>>>
>>> 
>>> 
>>> 
>>> https://www.meteoblue.com/de/wetter/widget/three/zorneding_deutschland_2803884?geoloc=fixed=1=0=7=CELSIUS=KILOMETER_PER_HOUR=image;
>>>  
>>>  frameborder="0" scrolling="YES" allowtransparency="true" 
>>> sandbox="allow-same-origin allow-scripts allow-popups 
>>> allow-popups-to-escape-sandbox" style="width: 100%; height: 525px; 
>>> padding-left: 16px; padding-right: 16px">
>>> 
>>> 
>>>
>>>

-- 
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/810af773-6f20-4783-816d-184f49f447c9o%40googlegroups.com.

Re: [weewx-user] Re: Weatherlink IP Discontinued... What are folks using now?

[Jeff Rabin]

I'll assume you are using weewx as this is the weewx forum.   

In your weewx.conf file:

[Vantage]

  # This section is for the Davis Vantage series of weather stations.


  # Connection type: serial or ethernet 

  #  serial (the classic VantagePro)

  #  ethernet (the WeatherLinkIP or Serial-Ethernet bridge)

  type = ethernet



and set the host to the address of the Pi.





On Friday, June 19, 2020 at 9:40:28 AM UTC-4, Dale wrote:
>
> Jeff: 
>
> This sounds like a solution to another use I have. 
>
>
> I can understand plugging the serial output from the Davis or whatever 
> into the Pi, having the Pi plugged into the LAN, and that program you 
> mention reads the Davis (as example) and sends it in some form over the 
> ethernet. 
>
>
> But once the destination computer running the program which needs the 
> serial data, how does the data on the ethernet get converted back into a 
> form that the program (which is looking for a COM port) able to get 
> those data from the ethernet? 
>
>
> It seems to me there must be some additional software on the receiving 
> end which un-does this and makes it appear that it is coming in on a COM. 
>
>
> For instance, Weather Display has some options to receive data from an 
> IP address, but those conversions are done within Weather Display 
> station interface. 
>
>
> Am I overthinking this, or is there more I would need to do on the 
> receiving end to be successful? 
>
> Thanks for any clarificationDale 
>
>
>

-- 
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/68a73c15-1a32-462d-b7d0-7f82fdd51749o%40googlegroups.com.

Re: [weewx-user] Re: Weatherlink IP Discontinued... What are folks using now?

[Dale]

Jeff:

This sounds like a solution to another use I have.


I can understand plugging the serial output from the Davis or whatever 
into the Pi, having the Pi plugged into the LAN, and that program you 
mention reads the Davis (as example) and sends it in some form over the 
ethernet.



But once the destination computer running the program which needs the 
serial data, how does the data on the ethernet get converted back into a 
form that the program (which is looking for a COM port) able to get 
those data from the ethernet?



It seems to me there must be some additional software on the receiving 
end which un-does this and makes it appear that it is coming in on a COM.



For instance, Weather Display has some options to receive data from an 
IP address, but those conversions are done within Weather Display 
station interface.



Am I overthinking this, or is there more I would need to do on the 
receiving end to be successful?


Thanks for any clarification    Dale


--
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/e10962b4-e980-3fa3-676c-cdd96d0bc70d%40charter.net.

[weewx-user] unrecognised magic number

[Raffaello Bonvino]

Hi all, I have a WH1080SE and I'm running weewx 3.9.2 on a raspberrypi. I 
just noticed that the fousb driver logs the following sentence:

Jun 19 15:11:42 raspberrypi weewx[13403]: fousb: unrecognised magic number 
3d3f
Jun 19 15:11:42 raspberrypi weewx[13403]: fousb: synchronising to the 
weather station (quality=0)
Jun 19 15:12:37 raspberrypi weewx[13403]: fousb: unstable read: blocks 
differ for ptr 0x000d80



It complains about an unrecognised magic number, but is able to poll 
correctly the weather station. What's the matter with this error? Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a74c8f00-9747-46e8-b047-4531897adb24o%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Manfred Maier]

Das ist jetzt ein Schuss ins Blaue (vielleicht treffe ich aber):
Welche "belchertown_locale" hast Du angegeben? Bzw. in welcher 
"Locale"Einstellung läuft Dein Rechner?

In der besagten Belchertown.js auf Deinem Webserver steht in Zeile 507:
   thousandsSep: '''

Es sieht so aus, als würde ein Hochkomma als Tausender-Punkt verwendet. 
Der Browser fällt hier wohl drüber (3 Hochkommas nacheinander).

Der Tausender-Seperator ist eigentlich automatisch von der Locale gesteuert.
 

Manfred Maier schrieb am Freitag, 19. Juni 2020 um 15:01:48 UTC+2:

> Ich hab mir Deine Website jetzt mal angesehen.
> Es sieht so aus, als hättest Du ein Problem mit Deiner Belchertown.js.tmpl
>
> Hast Du da mal etwas geändert?
>
> Wenn ich die Fehlermeldung richtig interpretiere, gibt es ein Problem bei 
> Zeile 506. Das EOF bedeutet meiner Meinung nach, dass das File hier endet?
> Wie viele Zeilen hat Deine Belchertown.js.tmpl?
>
>
>
> Manfred Maier schrieb am Freitag, 19. Juni 2020 um 13:14:23 UTC+2:
>
>> Ist bei mir in der index_hook_after_charts.inc drin.
>>
>>
>> 1) Datei (index_hook_after_charts.inc) im Belchertown-Verzeichnis anlegen
>> 2) den folgenden Code reinkopieren
>> 3) In der weewx.conf (Belchertown -Section) einschalten, dass der 
>> Index-Hook alle 300 Sekunden (oder auch weniger oft) neu geladen wird.
>> 4) Noch den iframe aus meinem Code für Deinen Standort anpassen (den Code 
>> gibt's auf Meteoblue unter Website-Widgets).
>>
>> 
>> 
>> 
>> https://www.meteoblue.com/de/wetter/widget/three/zorneding_deutschland_2803884?geoloc=fixed=1=0=7=CELSIUS=KILOMETER_PER_HOUR=image;
>>  
>>  frameborder="0" scrolling="YES" allowtransparency="true" 
>> sandbox="allow-same-origin allow-scripts allow-popups 
>> allow-popups-to-escape-sandbox" style="width: 100%; height: 525px; 
>> padding-left: 16px; padding-right: 16px">
>> 
>> 
>>
>>

-- 
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/fa3c4e9e-659b-4305-8762-4cc72af91f7dn%40googlegroups.com.

[weewx-user] Upgrading from 3.8.0 prior to going to xubuntu 20.04

[Iain Simpson]

In preparation to a move to latest xubuntu (20.04.1) from 18.04 I am 
looking to upgrade to the latest version of weewx.

I am still running 3.8.0 and have made some additions (to interface with 
Conky).
Reading the upgrade documentation I was going to go via the 'setup.py' 
route.
Checking my current setup I am running from
/usr/share/weewx
/etc/weewx
/var/lib/weekx (sqlite)

The upgrade documentation says to change setup.cfg to 'previous 
installation' this presumably will be '/usr/share/weewx'

I am wondering whether this is the wisest route or whether to 
a. use the '.deb' file and rebuild my customisation.
b. stick with Python 2

It's some years since I did the original weewx installation and a lot has 
been forgotten.

Can anyone advise please.

-- 
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/367f3f6a-4fc0-49bd-ba6a-9b7a5e8e30b8o%40googlegroups.com.

[weewx-user] Re: Weatherlink IP Discontinued... What are folks using now?

[Jeff Rabin]

Easy to config.Add this to /etc/ser2net.conf

2:raw:0:/dev/ttyUSB0:19200 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS

On Friday, June 19, 2020 at 8:24:11 AM UTC-4, Jeff Rabin wrote:
>
>
> Get the cheapest Pi you can. There is a Unix package called ser2net 
> that converts the Serial/USB connection to ethernet. (sudo apt install 
> ser2net).I’ve got it running on 2 so basically emulates the Davis 
> Ethernet dongle.
>
> No real maintenance as the remote Pi is doing nothing related to weewx.   
>  It’s just converting serial to IP.
>
>
> On Thursday, June 18, 2020 at 2:26:36 PM UTC-4, Russell van vlack wrote:
>>
>> I operate several Davis Vantage Pro weather stations (cabled versions) 
>> for our local skywarn spotter network.  These stations are often located at 
>> remote sites and then we've got Weewx running on a server that goes out and 
>> polls all of the stations.  The stations are linked to the internet via a 
>> Weatherlink IP behind a router and it works beautifully (once we tweaked a 
>> few of the network settings in weewx, btw.)
>>
>> With the Davis Weatherlink IP being discontinued, what are folks using to 
>> connect their cabled stations to the internet?  I see a couple of 
>> recommendations a while ago for something like this: 
>> https://www.gridconnect.com/products/net232-serial-to-ethernet-intelligent-cable-adapter
>>  .  
>> Is this a good option?  How about something that does usb via ip instead?  
>> We had RaspPi's running at all the sites sending data back to the central 
>> server for a long time, but we really like the elegance of the solution we 
>> have currently.
>>
>> I'd appreciate any comments.  Kinda bummed that Davis moved to the 
>> weatherlink live idea.  I'd been able to get some of the IP loggers on ebay 
>> for a while but they're dwindling.
>>
>> Thanks.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2b478162-9396-469a-8041-7121e6f8eb7co%40googlegroups.com.

[weewx-user] Re: Weatherlink IP Discontinued... What are folks using now?

[Jeff Rabin]

Get the cheapest Pi you can. There is a Unix package called ser2net 
that converts the Serial/USB connection to ethernet. (sudo apt install 
ser2net).I’ve got it running on 2 so basically emulates the Davis 
Ethernet dongle.

No real maintenance as the remote Pi is doing nothing related to weewx.   
 It’s just converting serial to IP.


On Thursday, June 18, 2020 at 2:26:36 PM UTC-4, Russell van vlack wrote:
>
> I operate several Davis Vantage Pro weather stations (cabled versions) for 
> our local skywarn spotter network.  These stations are often located at 
> remote sites and then we've got Weewx running on a server that goes out and 
> polls all of the stations.  The stations are linked to the internet via a 
> Weatherlink IP behind a router and it works beautifully (once we tweaked a 
> few of the network settings in weewx, btw.)
>
> With the Davis Weatherlink IP being discontinued, what are folks using to 
> connect their cabled stations to the internet?  I see a couple of 
> recommendations a while ago for something like this: 
> https://www.gridconnect.com/products/net232-serial-to-ethernet-intelligent-cable-adapter
>  .  
> Is this a good option?  How about something that does usb via ip instead?  
> We had RaspPi's running at all the sites sending data back to the central 
> server for a long time, but we really like the elegance of the solution we 
> have currently.
>
> I'd appreciate any comments.  Kinda bummed that Davis moved to the 
> weatherlink live idea.  I'd been able to get some of the IP loggers on ebay 
> for a while but they're dwindling.
>
> Thanks.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/23b9735b-aa4c-41c7-acd1-83e888c70f52o%40googlegroups.com.

[weewx-user] Re: Weatherlink IP Discontinued... What are folks using now?

[Russell van vlack]

Thanks, Pat.

The ProData WiFi Logger seems like maybe the best option at this point.  It 
looks like it has worked well for folks based on what I see in the forum.  
Because these are remote sites, we have appreciated the robustness (is that 
a word?) of having everything cabled from the weather station right through 
to the internet, but we may have to break away from that.

And it's not so much a worry about the weatherlink ip turning off as it is 
just finding them out there to buy when we expand the network like we're 
doing now.

Thanks.  

On Thursday, June 18, 2020 at 7:15:27 PM UTC-4, Pat wrote:
>
> I don't think the weatherlink ip will turn off anytime soon. So it should 
> continue to work for a long time. If you're having a hard time buying a new 
> one, I see people are using a clone 
> . 
>
> On Thursday, June 18, 2020 at 4:52:53 PM UTC-4, vince wrote:
>>
>> On Thursday, June 18, 2020 at 11:26:36 AM UTC-7, Russell van vlack wrote:
>>>
>>> With the Davis Weatherlink IP being discontinued, what are folks using 
>>> to connect their cabled stations to the internet?  I see a couple of 
>>> recommendations a while ago for something like this: 
>>> https://www.gridconnect.com/products/net232-serial-to-ethernet-intelligent-cable-adapter
>>>  .  
>>> Is this a good option?  How about something that does usb via ip instead?  
>>> We had RaspPi's running at all the sites sending data back to the central 
>>> server for a long time, but we really like the elegance of the solution we 
>>> have currently. 
>>>
>>
>>
>> You could do a pi4 running in ramdisk (to protect the SD card) for less 
>> than the half of cost of your serial-to-ethernet adaptor.
>>
>>

-- 
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/aa44e964-0420-4a02-aeda-49ef1fe8840bo%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Manfred Maier]

Ist bei mir in der index_hook_after_charts.inc drin.


1) Datei (index_hook_after_charts.inc) im Belchertown-Verzeichnis anlegen
2) den folgenden Code reinkopieren
3) In der weewx.conf (Belchertown -Section) einschalten, dass der 
Index-Hook alle 300 Sekunden (oder auch weniger oft) neu geladen wird.
4) Noch den iframe aus meinem Code für Deinen Standort anpassen (den Code 
gibt's auf Meteoblue unter Website-Widgets).




https://www.meteoblue.com/de/wetter/widget/three/zorneding_deutschland_2803884?geoloc=fixed=1=0=7=CELSIUS=KILOMETER_PER_HOUR=image;
 
 frameborder="0" scrolling="YES" allowtransparency="true" 
sandbox="allow-same-origin allow-scripts allow-popups 
allow-popups-to-escape-sandbox" style="width: 100%; height: 525px; 
padding-left: 16px; padding-right: 16px">



-- 
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/fce92db2-c73d-4533-8d4d-04bf5e95a75cn%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Geni 0815]

@Manfred, wie und wo hast die meteoblue vorhersage eingebaut?

Am Freitag, 19. Juni 2020 10:48:16 UTC+2 schrieb Geni 0815:
>
>
> What do I have to set where and how to get diagrams
>
> Regards
> Geni
>

-- 
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/0cb4795c-4c60-47b2-a2b2-c3e534208970o%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Manfred Maier]

Ist Deine Seite schon von extern erreichbar? Kannst Du mal die Adresse 
schicken?

geni08...@gmail.com schrieb am Freitag, 19. Juni 2020 um 12:59:59 UTC+2:

> Die charts liefen noch nie.
> Der Eintrag highcharts_enabled = 1 ist nur in der skin.conf.
> Es gibt keine Fehlermeldungen, ich habe das belchertown_debug = 1 gesetzt, 
> wo sieht man diese Meldungen?
>
> Am Freitag, 19. Juni 2020 11:49:03 UTC+2 schrieb Manfred Maier:
>>
>> Liefen die Charts bei Dir schon mal?
>>
>> Der generelle Switch für die Highcharts ist in der skin.conf (bzw. 
>> weewx.conf):
>> # Highcharts settings
>> highcharts_enabled = 1
>>
>> Kommen auf Deiner Website irgendwelche Fehlermeldungen? 
>>
>> geni08...@gmail.com schrieb am Freitag, 19. Juni 2020 um 11:42:06 UTC+2:
>>
>>> Es ist die Original graphs.conf.example, da sollte doch nichts falsch 
>>> sein?
>>>
>>>
>>> Am Freitag, 19. Juni 2020 10:59:49 UTC+2 schrieb Manfred Maier:

 And if still no charts are produced, you probably have an error in 
 somewhere in your graphs.conf. If one chart in there is invalid, no charts 
 at all are produced.

 geni08...@gmail.com schrieb am Freitag, 19. Juni 2020 um 10:48:16 
 UTC+2:

>
> What do I have to set where and how to get diagrams
>
> Regards
> Geni
>


-- 
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/70efbc3b-08d6-4ac0-aa3a-0b983b5d8d54n%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Geni 0815]

Die charts liefen noch nie.
Der Eintrag highcharts_enabled = 1 ist nur in der skin.conf.
Es gibt keine Fehlermeldungen, ich habe das belchertown_debug = 1 gesetzt, 
wo sieht man diese Meldungen?

Am Freitag, 19. Juni 2020 11:49:03 UTC+2 schrieb Manfred Maier:
>
> Liefen die Charts bei Dir schon mal?
>
> Der generelle Switch für die Highcharts ist in der skin.conf (bzw. 
> weewx.conf):
> # Highcharts settings
> highcharts_enabled = 1
>
> Kommen auf Deiner Website irgendwelche Fehlermeldungen? 
>
> geni08...@gmail.com schrieb am Freitag, 19. Juni 2020 um 11:42:06 UTC+2:
>
>> Es ist die Original graphs.conf.example, da sollte doch nichts falsch 
>> sein?
>>
>>
>> Am Freitag, 19. Juni 2020 10:59:49 UTC+2 schrieb Manfred Maier:
>>>
>>> And if still no charts are produced, you probably have an error in 
>>> somewhere in your graphs.conf. If one chart in there is invalid, no charts 
>>> at all are produced.
>>>
>>> geni08...@gmail.com schrieb am Freitag, 19. Juni 2020 um 10:48:16 UTC+2:
>>>

 What do I have to set where and how to get diagrams

 Regards
 Geni

>>>

-- 
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/c266b139-87ee-4639-9064-ece981b6136co%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Geni 0815]

und warum bekomme ich keine Letzte Update Information

Am Freitag, 19. Juni 2020 10:48:16 UTC+2 schrieb Geni 0815:
>
>
> What do I have to set where and how to get diagrams
>
> Regards
> Geni
>

-- 
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/fa242998-aa80-4150-9a0d-880516b4467co%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

['NanoG5Kite' via weewx-user]

Du hast die aber auch richtig umbenannt? Anbei meine...

Gruß,

Matthias

Am Freitag, 19. Juni 2020 11:42:06 UTC+2 schrieb Geni 0815:
>
> Es ist die Original graphs.conf.example, da sollte doch nichts falsch sein?
>
>
> Am Freitag, 19. Juni 2020 10:59:49 UTC+2 schrieb Manfred Maier:
>>
>> And if still no charts are produced, you probably have an error in 
>> somewhere in your graphs.conf. If one chart in there is invalid, no charts 
>> at all are produced.
>>
>> geni08...@gmail.com schrieb am Freitag, 19. Juni 2020 um 10:48:16 UTC+2:
>>
>>>
>>> What do I have to set where and how to get diagrams
>>>
>>> Regards
>>> Geni
>>>
>>

-- 
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/e748abaf-773a-462e-a459-cf2ee4a32107o%40googlegroups.com.
# This is the Belchertown skin charting system which utilizes Highcharts to 
display the chart data.
#
# PLEASE READ THE CHARTS WIKI! A lot of information is there and it will help 
you! 
# It is located here: 
https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation
#   
# Caution!
# The more charts you have, the slower things can become. This is especially 
true at the YEAR level. These are interactive charts which have to build plot 
points from the database on every archive interval. This could result in large 
file sizes to generate, and for your website visitors to download. You're 
welcome to customize as many charts as you want, but be warned things could 
slow down if you do too much!
# The defaults in this skin have proven to be a good baseline for the number of 
charts and options without overwhelming your system. 
#
# Overview of options:
# A timespan refers to "day", "week", "month" or "year". 
# The first configuration item is the graph group, such as [day], [week], 
[month], [year] sections. 
# The charts are defined under the graph group and can be renamed and 
reorganized. They will display on your website in the order they appear here.
# Under the chart are the observation names from the WeeWX database. Any item 
within your database "archive type" can be charted. For a list of "archive 
types" refer to this chart. http://weewx.com/docs/customizing.htm#archive_types
# Each observation can be customized with built-in Highcharts "series" options. 
Popular ones are color, name and zIndex. For a list of Highcharts Series 
options refer to https://api.highcharts.com/highcharts/series 
#
# If a custom option broke your charts:
# Undo your change and run wee_reports. You do not need to restart weewx if you 
make a graphs.conf change.
# If that doesn't work, undo ALL changes and go back to the default 
graphs.conf.example configuration.
# There is no guarantee that every customization option will work. 
#
# Detailed settings overview can be found in the wiki under Detailed 
Configuration Settings Overview
#
###

# Global Chart Defaults
# These are fallback options that charts will use if an option is not defined. 
aggregate_type = None
time_length = 9 # Last 25 hours
type = line
colors = "#7cb5ec, #b2df8a, #f7a35c, #8c6bb1, #dd3497, #e4d354, #268bd2, 
#f45b5b, #6a3d9a, #33a02c"
tooltip_date_format = "LLL"

[homepage]
# Chart Timespan Defaults
title = "Homepage"
show_button = true
button_text = "Homepage"
time_length = today
tooltip_date_format = "LLL"
gapsize = 30 # This should be your archive_interval from weewx.conf 
multiplied by 1000 to get milliseconds. Standard is 5 minutes

[[chart1]]
title = Temperature
[[[outTemp]]]
zIndex = 1
name = Temperature
[[[windchill]]]
[[[heatindex]]]
color = "#f7a35c"
[[[dewpoint]]]
color = purple

[[chart2]]
# The combined Wind Chart works best in this configuration
title = Wind Speed and Direction
yAxis_min = 0
[[[windDir]]]
zIndex = 1
yAxis = 1
yAxis_max = 360
lineWidth = 0
marker
enabled = true
states
[hover]
lineWidthPlus = 0
[[[windGust]]]
[[[windSpeed]]]
zIndex = 2

[[chart3]]
title = Rain
[[[rainRate]]]
yAxis = 1
[[[rainTotal]]]
name = Rain Total

[[chart4]]
title = Barometer
type = spline
[[[barometer]]]
color = "#BECC00"
yAxis_tickinterval = 0.01

[[chart5]]
title = Wind Rose
[[[windRose]]]

[[chart6]]
title = Solar Radiation and  UV Index
[[[radiation]]]
   name = 

[weewx-user] Re: Interceptor and WH57 Lightning sensor from Ecowitt

['NanoG5Kite' via weewx-user]

Hi Gert,

then you are further than me the last time and I also did another error 
last time, using: 

[[sensor_map]]insteadt of [[sensor_map_extensions]]

So I have no really good answer for now. But will try also over the weekend.

What I know so far. The lightning_time is Unix time - so for now/noon something 
like : 
1592562248 - for me without further conversion to a normal/understandable time 
string not usable...

Br, Matthias



Am Freitag, 19. Juni 2020 09:53:49 UTC+2 schrieb Gert Andersen:
>
> Hi Matthias
>
> Yes I have the data and data inserted into the DB. But with this setting:
>
> [[sensor_map_extensions]]
> lightning_strike_count = lightning_num
> lightning_distance = lightning
>
> You're missing this information:
> lightning_time
> wh57batt
>
> Because these fields are not mapped to any fields in the DB. So the 
> question is, should I extend the DB to include these fields or are there 
> any other solution. What have you done? If you have done the mapping which 
> types are you then mapping lightning_time and wh57batt to in the weewx.sdb.
>
> I'm using the extended scheme.
>
> Gert
>
> On Friday, June 19, 2020 at 7:28:47 AM UTC+2, NanoG5Kite wrote:
>>
>> Hi Gert,
>>
>> I‘m not sure about the Battery Value, but has your sensor and gw1000 ever 
>> detected one strike before? You need this first strike to get all data 
>> points.
>>
>> Br,
>>
>> Matthias
>>
>> Am Freitag, 19. Juni 2020 06:42:15 UTC+2 schrieb Gert Andersen:
>>>
>>> Hi 
>>> I'm also waiting to the next strike.
>>>
>>> What do you do with the 2 other fields:
>>> lightning_time
>>> wh57batt
>>>
>>> Currently they are not in the database, so have you updated the database 
>>> with these fields or just forget them?
>>>
>>> Thanks to Oliver for the help.
>>>
>>> Gert
>>>
>>>
>>> On Saturday, June 6, 2020 at 10:28:48 AM UTC+2, Gert Andersen wrote:

 Hi

 I get these infos from the log:

 INFO user.interceptor: unrecognized parameter lightning_time=
 INFO user.interceptor: unrecognized parameter lightning_num=0
 INFO user.interceptor: unrecognized parameter lightning=
 INFO user.interceptor: unrecognized parameter wh57batt=5

 I could not see a new version at Github, the latest version include 
 wh40 and is 4 month old. Seems to be version 0.53

 Is there a newer version around which include the lightning sensor.

 Gert

>>>

-- 
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/6ad4ac13-8334-4a4d-898f-6c6d306d77e7o%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Manfred Maier]

Liefen die Charts bei Dir schon mal?

Der generelle Switch für die Highcharts ist in der skin.conf (bzw. 
weewx.conf):
# Highcharts settings
highcharts_enabled = 1

Kommen auf Deiner Website irgendwelche Fehlermeldungen? 

geni08...@gmail.com schrieb am Freitag, 19. Juni 2020 um 11:42:06 UTC+2:

> Es ist die Original graphs.conf.example, da sollte doch nichts falsch sein?
>
>
> Am Freitag, 19. Juni 2020 10:59:49 UTC+2 schrieb Manfred Maier:
>>
>> And if still no charts are produced, you probably have an error in 
>> somewhere in your graphs.conf. If one chart in there is invalid, no charts 
>> at all are produced.
>>
>> geni08...@gmail.com schrieb am Freitag, 19. Juni 2020 um 10:48:16 UTC+2:
>>
>>>
>>> What do I have to set where and how to get diagrams
>>>
>>> Regards
>>> Geni
>>>
>>

-- 
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/41dbedad-5fdc-4d2f-a632-12186e5114b2n%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Geni 0815]

Es ist die Original graphs.conf.example, da sollte doch nichts falsch sein?


Am Freitag, 19. Juni 2020 10:59:49 UTC+2 schrieb Manfred Maier:
>
> And if still no charts are produced, you probably have an error in 
> somewhere in your graphs.conf. If one chart in there is invalid, no charts 
> at all are produced.
>
> geni08...@gmail.com schrieb am Freitag, 19. Juni 2020 um 10:48:16 UTC+2:
>
>>
>> What do I have to set where and how to get diagrams
>>
>> Regards
>> Geni
>>
>

-- 
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/90d9440e-1916-47f5-a97b-3dcd6e80b66co%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Manfred Maier]

And if still no charts are produced, you probably have an error in 
somewhere in your graphs.conf. If one chart in there is invalid, no charts 
at all are produced.

geni08...@gmail.com schrieb am Freitag, 19. Juni 2020 um 10:48:16 UTC+2:

>
> What do I have to set where and how to get diagrams
>
> Regards
> Geni
>

-- 
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/b954dd24-3914-4d99-9e82-514400805c03n%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Andre]

You can use wee_reports to perform updates for reports.

Am Freitag, 19. Juni 2020 10:48:16 UTC+2 schrieb Geni 0815:
>
>
> What do I have to set where and how to get diagrams
>
> Regards
> Geni
>

-- 
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/2e34c16e-9494-485a-99b2-f34a59a79524o%40googlegroups.com.

[weewx-user] Belchertown no charts

[Geni 0815]

What do I have to set where and how to get diagrams

Regards
Geni

-- 
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/6ae74ae1-c020-4d8c-8f68-8ed82afeda0co%40googlegroups.com.

[weewx-user] Re: Interceptor and WH57 Lightning sensor from Ecowitt

[Gert Andersen]

Hi Matthias

Yes I have the data and data inserted into the DB. But with this setting:

[[sensor_map_extensions]]
lightning_strike_count = lightning_num
lightning_distance = lightning

You're missing this information:
lightning_time
wh57batt

Because these fields are not mapped to any fields in the DB. So the 
question is, should I extend the DB to include these fields or are there 
any other solution. What have you done? If you have done the mapping which 
types are you then mapping lightning_time and wh57batt to in the weewx.sdb.

I'm using the extended scheme.

Gert

On Friday, June 19, 2020 at 7:28:47 AM UTC+2, NanoG5Kite wrote:
>
> Hi Gert,
>
> I‘m not sure about the Battery Value, but has your sensor and gw1000 ever 
> detected one strike before? You need this first strike to get all data 
> points.
>
> Br,
>
> Matthias
>
> Am Freitag, 19. Juni 2020 06:42:15 UTC+2 schrieb Gert Andersen:
>>
>> Hi 
>> I'm also waiting to the next strike.
>>
>> What do you do with the 2 other fields:
>> lightning_time
>> wh57batt
>>
>> Currently they are not in the database, so have you updated the database 
>> with these fields or just forget them?
>>
>> Thanks to Oliver for the help.
>>
>> Gert
>>
>>
>> On Saturday, June 6, 2020 at 10:28:48 AM UTC+2, Gert Andersen wrote:
>>>
>>> Hi
>>>
>>> I get these infos from the log:
>>>
>>> INFO user.interceptor: unrecognized parameter lightning_time=
>>> INFO user.interceptor: unrecognized parameter lightning_num=0
>>> INFO user.interceptor: unrecognized parameter lightning=
>>> INFO user.interceptor: unrecognized parameter wh57batt=5
>>>
>>> I could not see a new version at Github, the latest version include wh40 
>>> and is 4 month old. Seems to be version 0.53
>>>
>>> Is there a newer version around which include the lightning sensor.
>>>
>>> Gert
>>>
>>

-- 
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/219067f8-6350-4e9d-a6ff-0f83516d5918o%40googlegroups.com.

[weewx-user] Re: Export (high)charts Belchertown

[Arend]

Hello Pat,

Your solution did indeed work for me: highchart export menu options are now 
showing up! For your information: after using and closing the menu option 
'View in full screen' the chart doesn't return to its original size. But 
this is restored after doing a page refresh.

Thank you for providing this great skin.

Regards, Arend

Op vrijdag 19 juni 2020 01:39:33 UTC+2 schreef Pat:
>
> I think I fixed it. Replace your skins/Belchertown/style.css with the one 
> attached in the zip file, then let an archive interval pass and refresh 
> your page. 
>
>
>
> On Thursday, June 18, 2020 at 4:17:58 PM UTC-4, Arend wrote:
>>
>>
>>
>> Op donderdag 18 juni 2020 21:18:14 UTC+2 schreef Pat:
>>>
>>> It works in my debugger, but not on my site. I'll have to look into this
>>>
>>
>>
>> Hello Pat,
>>
>> Thank you for your quick response. If you need additional information for 
>> tracing the cause of this problem, please let me know.
>>
>> With kind regards, Arend
>>
>

-- 
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/6abd3e41-e128-4b41-bd7d-d0f4f28154beo%40googlegroups.com.

[weewx-user] Re: Belchertown - German Translation

['NanoG5Kite' via weewx-user]

https://groups.google.com/d/msg/weewx-user/_L1B5wIjku0/oI182bHQAwAJ

Am Freitag, 19. Juni 2020 08:20:24 UTC+2 schrieb Geni 0815:
>
> Hallo Manfred, ich finde hier nichts übersetztes.
> Gruss Geni
>
> Am Donnerstag, 11. Juni 2020 11:19:14 UTC+2 schrieb Manfred Maier:
>>
>> Here you go!
>>
>> Attached please find my skin.conf (with - I guess - no relevant 
>> information in it), plus the relevant part of my weewx.conf that holds all 
>> the German translations. It's important to put the translations into the 
>> weewx.conf. Otherwise the translations might get lost when updating the 
>> skin.
>>
>> Would be great if you could post the URL of your site. I'm always looking 
>> for ideas of how to improve my site ;)
>>
>> Best regards!
>> Manfred 
>>
>> Am Donnerstag, 11. Juni 2020 11:02:22 UTC+2 schrieb Manfred Maier:
>>>
>>> Sure. 
>>> I'll upload my translations for you. Give me 15 mins.
>>>
>>> Manfred
>>>
>>> PS: On my site you can see my German translation in action (
>>> wetter-zorneding.de) 
>>>
>>> Am Donnerstag, 11. Juni 2020 10:53:22 UTC+2 schrieb NanoG5Kite:

 Hello everybody

 Would someone support me with his German skin-conf...?

 Regards,

 Matthias

>>>

-- 
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/4e5a1541-5290-41ac-b145-5edf4ab8def4o%40googlegroups.com.

[weewx-user] Re: Belchertown github_version.json. Reason: [Errno 2]

[Geni 0815]

Hello Pat
thank you so no more errors.
Regards
Geni

Am Mittwoch, 17. Juni 2020 19:26:52 UTC+2 schrieb Pat:
>
> I'll be removing this feature in skin 1.2. It's not working as I had 
> planned and I've invested too much time trying to resolve it. The reward 
> isn't there any longer. 
>
> In your skin.conf, set check_for_updates = 0 and restart weewx and this 
> will go away
>
> On Wednesday, June 17, 2020 at 1:19:54 PM UTC-4, Geni 0815 wrote:
>>
>> I have reinstalled the skin Belchertown
>> I have weewx 4.1.1 on a Raspberry 3+ with Buster lite.
>> Minimally no Darksky and no MQTT.
>> Only the weather data is generated with the Windy picture but no graphics. 
>> Many 
>> lines are displayed in the console with the following:
>>
>> Jun 17 18:30:32 Wetter-Raspi weewx[22848] INFO user.belchertown: version 
>> 1.1
>> Jun 17 18:30:32 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Error downloading GitHub Version data. The error is: HTTP Error 
>> 403: rate limit exceeded
>> Jun 17 18:30:32 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Unable to open 
>> /home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
>> Datei oder Verzeichnis nicht gefunden: 
>> '/home/pi/NAS/www/belchertown/json/github_version.json'
>> Jun 17 18:30:33 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Error downloading GitHub Version data. The error is: HTTP Error 
>> 403: rate limit exceeded
>> Jun 17 18:30:33 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Unable to open 
>> /home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
>> Datei oder Verzeichnis nicht gefunden: 
>> '/home/pi/NAS/www/belchertown/json/github_version.json'
>> Jun 17 18:30:35 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Error downloading GitHub Version data. The error is: HTTP Error 
>> 403: rate limit exceeded
>> Jun 17 18:30:35 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Unable to open 
>> /home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
>> Datei oder Verzeichnis nicht gefunden: 
>> '/home/pi/NAS/www/belchertown/json/github_version.json'
>> Jun 17 18:30:36 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Error downloading GitHub Version data. The error is: HTTP Error 
>> 403: rate limit exceeded
>> Jun 17 18:30:36 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Unable to open 
>> /home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
>> Datei oder Verzeichnis nicht gefunden: 
>> '/home/pi/NAS/www/belchertown/json/github_version.json'
>> Jun 17 18:30:37 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Error downloading GitHub Version data. The error is: HTTP Error 
>> 403: rate limit exceeded
>> Jun 17 18:30:37 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Unable to open 
>> /home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
>> Datei oder Verzeichnis nicht gefunden: 
>> '/home/pi/NAS/www/belchertown/json/github_version.json'
>> Jun 17 18:30:38 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Error downloading GitHub Version data. The error is: HTTP Error 
>> 403: rate limit exceeded
>> Jun 17 18:30:38 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Unable to open 
>> /home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
>> Datei oder Verzeichnis nicht gefunden: 
>> '/home/pi/NAS/www/belchertown/json/github_version.json'
>>
>>
>> What's missing?
>>
>> Regards 
>> Geni
>>
>

-- 
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/84b8a353-7341-4a5a-a837-a7ce1e75e276o%40googlegroups.com.

[weewx-user] Re: Belchertown - German Translation

[Geni 0815]

Hallo Manfred, ich finde hier nichts übersetztes.
Gruss Geni

Am Donnerstag, 11. Juni 2020 11:19:14 UTC+2 schrieb Manfred Maier:
>
> Here you go!
>
> Attached please find my skin.conf (with - I guess - no relevant 
> information in it), plus the relevant part of my weewx.conf that holds all 
> the German translations. It's important to put the translations into the 
> weewx.conf. Otherwise the translations might get lost when updating the 
> skin.
>
> Would be great if you could post the URL of your site. I'm always looking 
> for ideas of how to improve my site ;)
>
> Best regards!
> Manfred 
>
> Am Donnerstag, 11. Juni 2020 11:02:22 UTC+2 schrieb Manfred Maier:
>>
>> Sure. 
>> I'll upload my translations for you. Give me 15 mins.
>>
>> Manfred
>>
>> PS: On my site you can see my German translation in action (
>> wetter-zorneding.de) 
>>
>> Am Donnerstag, 11. Juni 2020 10:53:22 UTC+2 schrieb NanoG5Kite:
>>>
>>> Hello everybody
>>>
>>> Would someone support me with his German skin-conf...?
>>>
>>> Regards,
>>>
>>> Matthias
>>>
>>

-- 
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/64bb03ff-0bf4-47ea-b9b1-be478580b43do%40googlegroups.com.