[weewx-user] Re: Belchertown skin 1.0 released!

[Xant]

Francesco

Also to note, that Pat made Belchertown skin much customizable and easy to 
adapt (for most part) to your "own language". Please, verify the section 
"Labels" in 'skin.conf' file.



On Monday, October 21, 2019 at 4:56:03 PM UTC-4, Francesco Scaramella wrote:
>
> what parts of the skin do you need to translate for customization in your 
> own language??
>

-- 
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/422b4e6b-de7e-41f9-8bbc-c7e6c383f170%40googlegroups.com.

[weewx-user] Re: Did someone test Weewx in Raspbian Buster?

[Susan Mackay]

After a bit of trial and error, I've managed to find the incantation that 
lets Github display the installation lines correctly from the 'readme.md' 
file.
Hopefully this should stop the problems for others in the future.
Susan

-- 
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/f14267a9-3f81-43c3-aeec-307be5c95b66%40googlegroups.com.

Re: [weewx-user] Documentation Improvement Suggestion - and Solar Panel fun

[Alex Edwards]

Thanks for your reply - I've not tried before, but will give a go :)

-- 
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/1d081b5a-a3a7-4446-890f-478b0d63f58c%40googlegroups.com.

Re: [weewx-user] Documentation Improvement Suggestion - and Solar Panel fun

[Alex Edwards]

Thanks for your reply - I've not tried before, but will give a go :)

On Wednesday, 23 October 2019 14:05:28 UTC+13, Thomas Keffer wrote:
>
> That looks pretty good!
>
> Can you submit a Pull Request to the Customization Guide with your 
> changes? Do it on the 'development' branch.
>
> Thanks in advance
>
> -tk
>
> On Tue, Oct 22, 2019 at 5:36 PM Alex Edwards  > wrote:
>
>> Hi all,
>>
>> I've enjoyed playing with Weewx and WS2080 for the past few months - 
>> thanks!
>>
>> I've wanted to extend this with solar panel information too, thinking 
>> weewx sounds great for this.  I got most of the way to writing a 
>> tool/driver to read the data, then noticed that Matthew Wall recently 
>> released something similar as Weewx driver too.  Doh!  Though my 'driver' 
>> might be more flexible .. stay tuned.
>>
>> However, its taken me longer than I'd expect or like to get my head 
>> around such a Weewx driver and how to 'use' it.  Some of it is Weewx is 
>> arguably simpler to use than the documentation implied, and so I thought 
>> much more would be required on top of a driver to use it - e.g. services, 
>> database etc.  Even after reading the documentation several times it wasn't 
>> obvious that a 'driver' should almost just work in Weewx - together with 
>> some not quite so obvious edits to weewx.conf and StdArchive etc.  
>> Something that may help is more of an intro to the 'system architecture' in 
>> the customization documentation, possibly at the very start e g. below.  I 
>> think if I'd have read something like the 'document' below I'd have picked 
>> things up faster.  Also, if these drivers/examples could more automatically 
>> setup their separate database and some example reports would be great for 
>> newbie users.
>>
>> Anyway, once I got my head around this 'architecture' getting these 
>> graphs out has been almost a pleasure - see below, still some tidying to 
>> do.  I really wanted the 'day/night' shading, and the graphs clearly show 
>> the voltage low point through the night and the current dropping off as the 
>> battery reaches full charge.  With a bit more finesse I'll upload my driver 
>> / skin etc to Github to share.  Though a future step may be to look at the 
>> gorgeous Belchertown style graphs :)  
>>
>> System Architecture
>>
>>- 
>>
>>A weewx process normally handles the monitoring of one station - e.g. 
>>a weather station.  The process is configured with a weewx.conf file. 
>>- 
>>
>>Multiple weewx processes may be run simultaneously to monitor 
>>multiple stations, using separate weewx.conf files to refer to different 
>>driver and databases etc.  More advanced weewx processes might create 
>>reports across multiple other weewx station databases, e.g. as a 
>> dashboard.
>>- 
>>
>>A weewx process has at most one ‘driver’ to communicate with the 
>>station hardware and receive ‘high resolution’ (i.e. every few seconds) 
>>measurement data in the form of LOOP packets.  The driver is 
>>single-threaded and blocking, so no more than one driver can run in a 
>> weewx 
>>process. 
>>- 
>>
>>LOOP packets may contain arbitrary data from the station/driver in 
>>the form of a Python dictionary. LOOP packet fields should conform to 
>>defined Weewx measurement units and measurement groups so they can then 
>> be summarised 
>>automatically (e.g. average of temperature, or sum of rainfall) by weewx 
>>over a set interval period (e.g. 5 minutes) into ‘archive records’.
>>- 
>>
>>A number of services may be configured within the weewx process to 
>>operate on the LOOP, archive record and database data - triggering when 
>> new 
>>data or timed events arise.  Typically these services run at 5 minute 
>>intervals. Standard services include - 
>>- 
>>   
>>   StdArchive - automatically create a database based on a user 
>>   ‘schema’ (a database table definition held as a python array in the 
>> driver 
>>   or service) then write archive records as they arise. Only archive 
>> record 
>>   fields which match the schema will be written to database.
>>   - 
>>   
>>   StdReport - generate reports based on database archive records, 
>>   stored by StdArchive.
>>   - 
>>   
>>   etc
>>   - 
>>
>>In addition some simpler services may generate archive records 
>>directly rather than from a driver (e.g. pmon example) and possibly store 
>>to their own database, partly configured through weewx.  These would be 
>>‘low resolution’ measurements taken at the same frequency services are 
>> run 
>>(e.g. 5 minutes) and without the statistical summarisation weewx can 
>>provide.
>>- 
>>
>>Weewx Extensions may consist of a combination of driver, service, 
>>database and/or skin code. However, only one station and associated 
>> driver 
>>can be run at a time.
>>
>>
>>
>>

Re: [weewx-user] ftpuploader timeout with Davis Vantage Pro2 - Weewx on CentOS 7

[Kevin H. Phillips]

Got it.  Thanks for the input.


Kevin

On 10/22/19 8:13 PM, Thomas Keffer wrote:

Kevin,

I don't think there is much of a mystery here. The Davis site does 
/not/ support FTP. I would be surprised if they did: that would make 
them just another website provider, which they are not.


What they do support is a proprietary HTTP "RESTful" upload protocol 
for their WeatherLink customers. That generally requires a 
subscription, although they do offer a crippled version for "3rd 
parties", which would be us. However, we do not offer such an upload 
extension, and have no plans to do so.


So, you will have to either

1) Set up your own website with a hosting provider. Several were 
suggested in an earlier email.
2) Be satisfied with a website on your Local Area Network, that is, 
your house. You can supplement this with uploads to CWOP or 
WeatherUnderground, or one of the many other upload sites WeeWX 
supports. Unfortunately, WeatherLink is not one of them.
3) Give up on WeeWX and go all Davis. Buy their WeatherLink Live 
logger, or use a regular logger, but run their WeatherLink Computer 
Software on a computer. Either way, you would need a subscription. See 
their website for details.


-tk



On Tue, Oct 22, 2019 at 5:33 PM Kevin H. Phillips 
mailto:kh-phill...@9-5usa.org>> wrote:


I posed the question to Davis Support of "how" their WeatherLink
software uploads information to their site.  I haven not yet
received a direct response from them but I received this evening
what appears to be a generic message that might contain some
clues.  I don't know if someone directed this to me or whether
this was directed at anyone using their WeatherLink software. 
Here it is:


Dear Developers,

There are upcoming changes to api.weatherlink.com
 that may affect those using SSL to
make requests to https://api.weatherlink.com/. The upcoming change
will disable support for outdated versions of TLS. Developers
using our API without SSL will not be affected.

Changes:
On Monday, November 4th, 2019, TLS version 1.0 will be disabled on
https://api.weatherlink.com
On Monday, January 6th 2020, TLS version 1.1 will be disabled on
https://api.weatherlink.com.

Background: TLS 1.0/1.1 protocols have known security
vulnerabilities and most modern web browsers will remove all
support for TLS 1.0/1.1 in January of next year. TLS version 1.2
was originally released in 2006, therefore most of you should
already support these newer protocols. Concerned application
developers or those operating applications that support critical
infrastructure should ensure software is up-to-date to support TLS
1.2 and modern encryption ciphers.

Thanks,

Davis Instruments WeatherLink Team.


On 10/20/19 10:28 AM, Thomas Keffer wrote:

The standard approach is to host your own website on a hosting
service that supports FTP or rsync. There are tons of them out
there. Personally, I use Amazon Web Services, but that's not a
simple system. Others are GoDaddy.com, or hostgator.com
, dreamhost.com , and
many, many others.

I don't know anything about WeatherLink, but I suppose it makes
the same assumption: that you will be hosting your own website,
and, if you put in the proper credentials, WeatherLink will FTP
files up to it. But, as I said, I don't know anything about the
program.

Now, posting to the WeatherUnderground and/or CWOP is a
completely different thing. That is done using HTTP, not FTP.

-tk

On Sun, Oct 20, 2019 at 7:10 AM Kevin Phillips
mailto:kh-phill...@9-5usa.org>> wrote:

Thanks for the reply.  I thought it seemed to be working from
what I could tell.  I have re-set the archive interval to 5
minutes.   In terms of whether or not I'm sure their website
supports FTP, my answer has to be "no".  Their Weatherlink
software in Windows has FTP settings in the Internet Settings
window (FTP hostname, FTP logon name, FTP path, etc).  I had
also written Davis Support to ask if anyone had any ideas
about this.  One person responded by telling me to try the
davisinstruments.com  setting
(It had originally been davisnet.com 
from when I first got the station and set up the software).
When I replied that that did not work, a different person
responded and appeared to say that the site did not support
FTP but the reply talked in terms of initial set-up of
Weatherlink which I have had running for a couple of years. 
The response was that I just follow the prompts and "it just
uploads".  While I do agree that the Internet is magic, this
was not quite as helpful or technical response as I had hoped
for.  ;-) 

Re: [weewx-user] ftpuploader timeout with Davis Vantage Pro2 - Weewx on CentOS 7

[Thomas Keffer]

Kevin,

I don't think there is much of a mystery here. The Davis site does
*not* support
FTP. I would be surprised if they did: that would make them just
another website provider, which they are not.

What they do support is a proprietary HTTP "RESTful" upload protocol for
their WeatherLink customers. That generally requires a subscription,
although they do offer a crippled version for "3rd parties", which would be
us. However, we do not offer such an upload extension, and have no plans to
do so.

So, you will have to either

1) Set up your own website with a hosting provider. Several were suggested
in an earlier email.
2) Be satisfied with a website on your Local Area Network, that is, your
house. You can supplement this with uploads to CWOP or WeatherUnderground,
or one of the many other upload sites WeeWX supports. Unfortunately,
WeatherLink is not one of them.
3) Give up on WeeWX and go all Davis. Buy their WeatherLink Live logger, or
use a regular logger, but run their WeatherLink Computer Software on a
computer. Either way, you would need a subscription. See their website for
details.

-tk



On Tue, Oct 22, 2019 at 5:33 PM Kevin H. Phillips 
wrote:

> I posed the question to Davis Support of "how" their WeatherLink software
> uploads information to their site.  I haven not yet received a direct
> response from them but I received this evening what appears to be a generic
> message that might contain some clues.  I don't know if someone directed
> this to me or whether this was directed at anyone using their WeatherLink
> software.  Here it is:
>
>
> Dear Developers,
>
> There are upcoming changes to api.weatherlink.com that may affect those
> using SSL to make requests to https://api.weatherlink.com/. The upcoming
> change will disable support for outdated versions of TLS. Developers using
> our API without SSL will not be affected.
>
> Changes:
> On Monday, November 4th, 2019, TLS version 1.0 will be disabled on
> https://api.weatherlink.com
> On Monday, January 6th 2020, TLS version 1.1 will be disabled on
> https://api.weatherlink.com.
>
> Background: TLS 1.0/1.1 protocols have known security vulnerabilities and
> most modern web browsers will remove all support for TLS 1.0/1.1 in January
> of next year. TLS version 1.2 was originally released in 2006, therefore
> most of you should already support these newer protocols. Concerned
> application developers or those operating applications that support
> critical infrastructure should ensure software is up-to-date to support TLS
> 1.2 and modern encryption ciphers.
>
> Thanks,
>
> Davis Instruments WeatherLink Team.
>
>
> On 10/20/19 10:28 AM, Thomas Keffer wrote:
>
> The standard approach is to host your own website on a hosting service
> that supports FTP or rsync. There are tons of them out there. Personally, I
> use Amazon Web Services, but that's not a simple system. Others are
> GoDaddy.com, or hostgator.com, dreamhost.com, and many, many others.
>
> I don't know anything about WeatherLink, but I suppose it makes the same
> assumption: that you will be hosting your own website, and, if you put in
> the proper credentials, WeatherLink will FTP files up to it. But, as I
> said, I don't know anything about the program.
>
> Now, posting to the WeatherUnderground and/or CWOP is a completely
> different thing. That is done using HTTP, not FTP.
>
> -tk
>
> On Sun, Oct 20, 2019 at 7:10 AM Kevin Phillips 
> wrote:
>
>> Thanks for the reply.  I thought it seemed to be working from what I
>> could tell.  I have re-set the archive interval to 5 minutes.   In terms of
>> whether or not I'm sure their website supports FTP, my answer has to be
>> "no".  Their Weatherlink software in Windows has FTP settings in the
>> Internet Settings window (FTP hostname, FTP logon name, FTP path, etc).  I
>> had also written Davis Support to ask if anyone had any ideas about this.
>> One person responded by telling me to try the davisinstruments.com
>> setting (It had originally been davisnet.com from when I first got the
>> station and set up the software).  When I replied that that did not work, a
>> different person responded and appeared to say that the site did not
>> support FTP but the reply talked in terms of initial set-up of Weatherlink
>> which I have had running for a couple of years.  The response was that I
>> just follow the prompts and "it just uploads".  While I do agree that the
>> Internet is magic, this was not quite as helpful or technical response as I
>> had hoped for.  ;-)  They did not respond after I pointed out the FTP
>> jargon in Weatherlink.  So, my question is:  if it does not support FTP,
>> how should I set up the Davis site in weewx?  Thanks again.  Kevin
>>
>> On Sunday, October 20, 2019 at 8:20:49 AM UTC-5, Thomas Keffer wrote:
>>>
>>> Your installation is actually running properly, but there are 3 issues:
>>>
>>> 1. This log entry gives a clue to one of your problems:
>>>
>>> Oct 15 05:43:12 RadioShack weewx[4433]:  device reports 

Re: [weewx-user] Documentation Improvement Suggestion - and Solar Panel fun

[Thomas Keffer]

That looks pretty good!

Can you submit a Pull Request to the Customization Guide with your changes?
Do it on the 'development' branch.

Thanks in advance

-tk

On Tue, Oct 22, 2019 at 5:36 PM Alex Edwards 
wrote:

> Hi all,
>
> I've enjoyed playing with Weewx and WS2080 for the past few months -
> thanks!
>
> I've wanted to extend this with solar panel information too, thinking
> weewx sounds great for this.  I got most of the way to writing a
> tool/driver to read the data, then noticed that Matthew Wall recently
> released something similar as Weewx driver too.  Doh!  Though my 'driver'
> might be more flexible .. stay tuned.
>
> However, its taken me longer than I'd expect or like to get my head around
> such a Weewx driver and how to 'use' it.  Some of it is Weewx is arguably
> simpler to use than the documentation implied, and so I thought much more
> would be required on top of a driver to use it - e.g. services, database
> etc.  Even after reading the documentation several times it wasn't obvious
> that a 'driver' should almost just work in Weewx - together with some not
> quite so obvious edits to weewx.conf and StdArchive etc.  Something that
> may help is more of an intro to the 'system architecture' in the
> customization documentation, possibly at the very start e g. below.  I
> think if I'd have read something like the 'document' below I'd have picked
> things up faster.  Also, if these drivers/examples could more automatically
> setup their separate database and some example reports would be great for
> newbie users.
>
> Anyway, once I got my head around this 'architecture' getting these graphs
> out has been almost a pleasure - see below, still some tidying to do.  I
> really wanted the 'day/night' shading, and the graphs clearly show the
> voltage low point through the night and the current dropping off as the
> battery reaches full charge.  With a bit more finesse I'll upload my driver
> / skin etc to Github to share.  Though a future step may be to look at the
> gorgeous Belchertown style graphs :)
>
> System Architecture
>
>-
>
>A weewx process normally handles the monitoring of one station - e.g.
>a weather station.  The process is configured with a weewx.conf file.
>-
>
>Multiple weewx processes may be run simultaneously to monitor multiple
>stations, using separate weewx.conf files to refer to different driver and
>databases etc.  More advanced weewx processes might create reports across
>multiple other weewx station databases, e.g. as a dashboard.
>-
>
>A weewx process has at most one ‘driver’ to communicate with the
>station hardware and receive ‘high resolution’ (i.e. every few seconds)
>measurement data in the form of LOOP packets.  The driver is
>single-threaded and blocking, so no more than one driver can run in a weewx
>process.
>-
>
>LOOP packets may contain arbitrary data from the station/driver in the
>form of a Python dictionary. LOOP packet fields should conform to defined
>Weewx measurement units and measurement groups so they can then be 
> summarised
>automatically (e.g. average of temperature, or sum of rainfall) by weewx
>over a set interval period (e.g. 5 minutes) into ‘archive records’.
>-
>
>A number of services may be configured within the weewx process to
>operate on the LOOP, archive record and database data - triggering when new
>data or timed events arise.  Typically these services run at 5 minute
>intervals. Standard services include -
>-
>
>   StdArchive - automatically create a database based on a user
>   ‘schema’ (a database table definition held as a python array in the 
> driver
>   or service) then write archive records as they arise. Only archive 
> record
>   fields which match the schema will be written to database.
>   -
>
>   StdReport - generate reports based on database archive records,
>   stored by StdArchive.
>   -
>
>   etc
>   -
>
>In addition some simpler services may generate archive records
>directly rather than from a driver (e.g. pmon example) and possibly store
>to their own database, partly configured through weewx.  These would be
>‘low resolution’ measurements taken at the same frequency services are run
>(e.g. 5 minutes) and without the statistical summarisation weewx can
>provide.
>-
>
>Weewx Extensions may consist of a combination of driver, service,
>database and/or skin code. However, only one station and associated driver
>can be run at a time.
>
>
>
>
> [image: weewx.png]
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> 

Re: [weewx-user] Re: Weewx stops working on Raspberry Pi

[Andrew Milner]

that looks to me like cron table settings



On Wed, 23 Oct 2019 at 02:44, K Weaver  wrote:

> Where do you put this script?
>
>
> On Monday, February 10, 2014 at 10:21:11 AM UTC-5, Per Edström wrote:
>>
>> I "solved" the problem with Weewx on R.Pi stopping by restarting it every
>> hour. One minute delay so that ongoing activity (FTP etc) is finished
>> before starting again (else start will fail quietly):
>>
>> 0 */1 * * * /etc/init.d/weewx stop
>> 1 */1 * * * /etc/init.d/weewx start
>>
>> Now it works well! :-)
>>
>> --
> 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/AFDE424PQqA/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/d4b3cad4-0730-4b94-8d2c-b56c34a35f35%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/CAHa2sA%2B3dtq3B88VjXfXQOBufvHY_BObhcH3V%3DrtiKQ_jBjc3A%40mail.gmail.com.

[weewx-user] Documentation Improvement Suggestion - and Solar Panel fun

[Alex Edwards]

Hi all,

I've enjoyed playing with Weewx and WS2080 for the past few months - thanks!

I've wanted to extend this with solar panel information too, thinking weewx 
sounds great for this.  I got most of the way to writing a tool/driver to 
read the data, then noticed that Matthew Wall recently released something 
similar as Weewx driver too.  Doh!  Though my 'driver' might be more 
flexible .. stay tuned.

However, its taken me longer than I'd expect or like to get my head around 
such a Weewx driver and how to 'use' it.  Some of it is Weewx is arguably 
simpler to use than the documentation implied, and so I thought much more 
would be required on top of a driver to use it - e.g. services, database 
etc.  Even after reading the documentation several times it wasn't obvious 
that a 'driver' should almost just work in Weewx - together with some not 
quite so obvious edits to weewx.conf and StdArchive etc.  Something that 
may help is more of an intro to the 'system architecture' in the 
customization documentation, possibly at the very start e g. below.  I 
think if I'd have read something like the 'document' below I'd have picked 
things up faster.  Also, if these drivers/examples could more automatically 
setup their separate database and some example reports would be great for 
newbie users.

Anyway, once I got my head around this 'architecture' getting these graphs 
out has been almost a pleasure - see below, still some tidying to do.  I 
really wanted the 'day/night' shading, and the graphs clearly show the 
voltage low point through the night and the current dropping off as the 
battery reaches full charge.  With a bit more finesse I'll upload my driver 
/ skin etc to Github to share.  Though a future step may be to look at the 
gorgeous Belchertown style graphs :)  

System Architecture
   
   - 
   
   A weewx process normally handles the monitoring of one station - e.g. a 
   weather station.  The process is configured with a weewx.conf file. 
   - 
   
   Multiple weewx processes may be run simultaneously to monitor multiple 
   stations, using separate weewx.conf files to refer to different driver and 
   databases etc.  More advanced weewx processes might create reports across 
   multiple other weewx station databases, e.g. as a dashboard.
   - 
   
   A weewx process has at most one ‘driver’ to communicate with the station 
   hardware and receive ‘high resolution’ (i.e. every few seconds) measurement 
   data in the form of LOOP packets.  The driver is single-threaded and 
   blocking, so no more than one driver can run in a weewx process. 
   - 
   
   LOOP packets may contain arbitrary data from the station/driver in the 
   form of a Python dictionary. LOOP packet fields should conform to defined 
   Weewx measurement units and measurement groups so they can then be 
summarised 
   automatically (e.g. average of temperature, or sum of rainfall) by weewx 
   over a set interval period (e.g. 5 minutes) into ‘archive records’.
   - 
   
   A number of services may be configured within the weewx process to 
   operate on the LOOP, archive record and database data - triggering when new 
   data or timed events arise.  Typically these services run at 5 minute 
   intervals. Standard services include - 
   - 
  
  StdArchive - automatically create a database based on a user ‘schema’ 
  (a database table definition held as a python array in the driver or 
  service) then write archive records as they arise. Only archive record 
  fields which match the schema will be written to database.
  - 
  
  StdReport - generate reports based on database archive records, 
  stored by StdArchive.
  - 
  
  etc
  - 
   
   In addition some simpler services may generate archive records directly 
   rather than from a driver (e.g. pmon example) and possibly store to their 
   own database, partly configured through weewx.  These would be ‘low 
   resolution’ measurements taken at the same frequency services are run (e.g. 
   5 minutes) and without the statistical summarisation weewx can provide.
   - 
   
   Weewx Extensions may consist of a combination of driver, service, 
   database and/or skin code. However, only one station and associated driver 
   can be run at a time.
   



[image: weewx.png]



-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e039cd25-7ba9-4546-87bc-3c2cf87a8e6d%40googlegroups.com.

Re: [weewx-user] ftpuploader timeout with Davis Vantage Pro2 - Weewx on CentOS 7

[Kevin H. Phillips]

I posed the question to Davis Support of "how" their WeatherLink 
software uploads information to their site.  I haven not yet received a 
direct response from them but I received this evening what appears to be 
a generic message that might contain some clues.  I don't know if 
someone directed this to me or whether this was directed at anyone using 
their WeatherLink software. Here it is:



Dear Developers,

There are upcoming changes to api.weatherlink.com that may affect those 
using SSL to make requests to https://api.weatherlink.com/. The upcoming 
change will disable support for outdated versions of TLS. Developers 
using our API without SSL will not be affected.


Changes:
On Monday, November 4th, 2019, TLS version 1.0 will be disabled on 
https://api.weatherlink.com
On Monday, January 6th 2020, TLS version 1.1 will be disabled on 
https://api.weatherlink.com.


Background: TLS 1.0/1.1 protocols have known security vulnerabilities 
and most modern web browsers will remove all support for TLS 1.0/1.1 in 
January of next year. TLS version 1.2 was originally released in 2006, 
therefore most of you should already support these newer protocols. 
Concerned application developers or those operating applications that 
support critical infrastructure should ensure software is up-to-date to 
support TLS 1.2 and modern encryption ciphers.


Thanks,

Davis Instruments WeatherLink Team.


On 10/20/19 10:28 AM, Thomas Keffer wrote:
The standard approach is to host your own website on a hosting service 
that supports FTP or rsync. There are tons of them out there. 
Personally, I use Amazon Web Services, but that's not a simple system. 
Others are GoDaddy.com, or hostgator.com , 
dreamhost.com , and many, many others.


I don't know anything about WeatherLink, but I suppose it makes the 
same assumption: that you will be hosting your own website, and, if 
you put in the proper credentials, WeatherLink will FTP files up to 
it. But, as I said, I don't know anything about the program.


Now, posting to the WeatherUnderground and/or CWOP is a completely 
different thing. That is done using HTTP, not FTP.


-tk

On Sun, Oct 20, 2019 at 7:10 AM Kevin Phillips > wrote:


Thanks for the reply.  I thought it seemed to be working from what
I could tell.  I have re-set the archive interval to 5 minutes.  
In terms of whether or not I'm sure their website supports FTP, my
answer has to be "no".  Their Weatherlink software in Windows has
FTP settings in the Internet Settings window (FTP hostname, FTP
logon name, FTP path, etc).  I had also written Davis Support to
ask if anyone had any ideas about this.  One person responded by
telling me to try the davisinstruments.com
 setting (It had originally been
davisnet.com  from when I first got the
station and set up the software). When I replied that that did not
work, a different person responded and appeared to say that the
site did not support FTP but the reply talked in terms of initial
set-up of Weatherlink which I have had running for a couple of
years. The response was that I just follow the prompts and "it
just uploads".  While I do agree that the Internet is magic, this
was not quite as helpful or technical response as I had hoped
for.  ;-)  They did not respond after I pointed out the FTP jargon
in Weatherlink.  So, my question is:  if it does not support FTP,
how should I set up the Davis site in weewx?  Thanks again.  Kevin

On Sunday, October 20, 2019 at 8:20:49 AM UTC-5, Thomas Keffer wrote:

Your installation is actually running properly, but there are
3 issues:

1. This log entry gives a clue to one of your problems:

Oct 15 05:43:12 RadioShack weewx[4433]:  device
reports readiness to read but returned no data (device
disconnected or multiple access on port?)
Oct 15 05:43:12 RadioShack weewx[4433]:  Is there
a competing process running??
Oct 15 05:43:16 RadioShack wee_device[5135]: vantage:
Max retries exceeded while getting EEPROM data at
address 0x29


You cannot run wee_device and weewxd at the same time. They
both need to control the console. Run one or the other, never
both.

2. Are you sure that www.davisinstruments.com
 supports FTP? When I try it,
the connection just times out. I would be very surprised if
they did.

3. Your console has a very long archive interval (1800
seconds, or half an hour). That means it will generate reports
and do the FTP upload only every half an hour. Consider
changing it to 5 minutes by using the utility wee_device with
the 

Re: [weewx-user] Re: Weewx stops working on Raspberry Pi

[K Weaver]

Where do you put this script?


On Monday, February 10, 2014 at 10:21:11 AM UTC-5, Per Edström wrote:
>
> I "solved" the problem with Weewx on R.Pi stopping by restarting it every 
> hour. One minute delay so that ongoing activity (FTP etc) is finished 
> before starting again (else start will fail quietly):
>
> 0 */1 * * * /etc/init.d/weewx stop
> 1 */1 * * * /etc/init.d/weewx start
>
> Now it works well! :-)
>
>

-- 
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/d4b3cad4-0730-4b94-8d2c-b56c34a35f35%40googlegroups.com.

[weewx-user] Re: exfoliation skin: problem with current page display

[Timothy Buchanan]

I have simply removed that column as the information is covered elsewhere 
in the skin. Looks pretty good now. thanks again for your help.

On Tuesday, October 22, 2019 at 5:29:15 PM UTC-6, gjr80 wrote:
>
> To properly display $day.maxSolarRad.xxx tags will require you to add the 
> field maxSolarRad to your database schema. maxSolarRad is a derived 
> observation that is calculated by WeeWX and added to loop packets and 
> archive records. The current maxSolarRad value (ie $current.maxSolarRad) 
> can be displayed without any change to the schema, but aggregates or plots 
> require WeeWX to be archiving the underlying data. If you want to go ahead 
> and add maxSolarRad to the database schema refer to the Adding a new type 
> to the database  
> section of the Customization Guide 
> .
>
> As for the other issue with the missing forecast data I don't use the 
> Exfoliation skin nor do I use the NWS forecast so it's going to take a 
> little time before I can provide any assistance there. 
>
> Gary
>
> On Tuesday, 22 October 2019 05:44:51 UTC+10, Timothy Buchanan wrote:
>>
>> I am using the exfoliation skin and have gotten all the pages working, 
>> except there is a problem with the display of the "current" page. I've 
>> attached a file showing the problem. The current weather source is set in 
>> the weewx.conf Forecast extension as NWS with lid = COZ081 and foid = PUB. 
>> The three-day forecast is working properly in the third column, but the 
>> forecast conditions in the second column are missing. There is also a 
>> formatting statement shown there. I am using the standard index.html.tmpl 
>> as it comes with the extension. Any help (especially from the extension's 
>> author!) is appreciated.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5b5ad75c-ed5c-42fb-aac4-2576c0d0fcfd%40googlegroups.com.

[weewx-user] Re: exfoliation skin: problem with current page display

[gjr80]

To properly display $day.maxSolarRad.xxx tags will require you to add the 
field maxSolarRad to your database schema. maxSolarRad is a derived 
observation that is calculated by WeeWX and added to loop packets and 
archive records. The current maxSolarRad value (ie $current.maxSolarRad) 
can be displayed without any change to the schema, but aggregates or plots 
require WeeWX to be archiving the underlying data. If you want to go ahead 
and add maxSolarRad to the database schema refer to the Adding a new type 
to the database  
section of the Customization Guide .

As for the other issue with the missing forecast data I don't use the 
Exfoliation skin nor do I use the NWS forecast so it's going to take a 
little time before I can provide any assistance there. 

Gary

On Tuesday, 22 October 2019 05:44:51 UTC+10, Timothy Buchanan wrote:
>
> I am using the exfoliation skin and have gotten all the pages working, 
> except there is a problem with the display of the "current" page. I've 
> attached a file showing the problem. The current weather source is set in 
> the weewx.conf Forecast extension as NWS with lid = COZ081 and foid = PUB. 
> The three-day forecast is working properly in the third column, but the 
> forecast conditions in the second column are missing. There is also a 
> formatting statement shown there. I am using the standard index.html.tmpl 
> as it comes with the extension. Any help (especially from the extension's 
> author!) is appreciated.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0db299f7-47c4-48c5-983d-6735bb675db6%40googlegroups.com.

[weewx-user] Re: can WeeWx be instaleld on LibreElec RPi?

[Andrew Milner]

the documentation has a list of prerequisite modules in addition to python 
- check that you have them all




On Tuesday, 22 October 2019 17:10:00 UTC+3, Pila wrote:
>
> Can I manually install WeeWx on an LibreElec RPi 3? It has Python 2.7.11 
> instaleld on it.
>
> Later, I would use different setup, but for the testing at the moment, I 
> would need to run WeeWx for some time from an RPi with LE running.
>

-- 
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/5b863a1f-1f2a-47a5-a160-9f32b2ad6a7a%40googlegroups.com.

[weewx-user] can WeeWx be instaleld on LibreElec RPi?

[Pila]

Can I manually install WeeWx on an LibreElec RPi 3? It has Python 2.7.11 
instaleld on it.

Later, I would use different setup, but for the testing at the moment, I 
would need to run WeeWx for some time from an RPi with LE running.

-- 
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/f818679e-b1de-4723-bbbf-b94116dec705%40googlegroups.com.

[weewx-user] Re: Belchertown skin 1.0 released!

[Pat]

Great thanks. You can try the GitHub but if that confuses you then you can 
just attach the files here and I can try to figure it out when I have some 
time. 

On Tuesday, October 22, 2019 at 8:52:37 AM UTC-4, Kike .Asekas wrote:
>
> What I did was adapt the renderDayNight function of genplot.py to get the 
> timestamps of dawn and dusk and with those timestamps write plotBands 
> (HighCharts function) in xAxis in the json.
> The code already has the possibility to activate them or not. It takes 
> about a second on the daily chart in a rpi 2b + to paint them.
> I am watching the github desktop program so I can send it to you. I guess 
> you will have to make some changes, I don't dominate much python or js.
>
> El sábado, 19 de octubre de 2019, 22:26:17 (UTC+2), Pat escribió:
>>
>> Hi Kike, this looks very interesting! Perhaps I can add it as a skin 
>> option to enable/disable it. How did you do it?
>>
>> On Saturday, October 19, 2019 at 4:07:41 PM UTC-4, Kike .Asekas wrote:
>>>
>>> Hi, Pat. I wanted to make a contribution to such an impressive skin, 
>>> but I don't know very well how to do it. If you are interested tell me 
>>> how.
>>> They are the transitions between night and day in the graphics.
>>>
>>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions(1).png]
>>>
>>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions(2).png]
>>>
>>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions.png]
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b3e38cde-46af-4149-82db-9f85a25fcba9%40googlegroups.com.

[weewx-user] Re: Belchertown skin 1.0 released!

[Kike .Asekas]

What I did was adapt the renderDayNight function of genplot.py to get the 
timestamps of dawn and dusk and with those timestamps write plotBands 
(HighCharts function) in xAxis in the json.
The code already has the possibility to activate them or not. It takes 
about a second on the daily chart in a rpi 2b + to paint them.
I am watching the github desktop program so I can send it to you. I guess 
you will have to make some changes, I don't dominate much python or js.

El sábado, 19 de octubre de 2019, 22:26:17 (UTC+2), Pat escribió:
>
> Hi Kike, this looks very interesting! Perhaps I can add it as a skin 
> option to enable/disable it. How did you do it?
>
> On Saturday, October 19, 2019 at 4:07:41 PM UTC-4, Kike .Asekas wrote:
>>
>> Hi, Pat. I wanted to make a contribution to such an impressive skin, but 
>> I don't know very well how to do it. If you are interested tell me how.
>> They are the transitions between night and day in the graphics.
>>
>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions(1).png]
>>
>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions(2).png]
>>
>> [image: Screenshot_2019-10-19 Areal, Padron Weather Conditions.png]
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c953c67e-9052-4c68-b62b-ce525cd7b02b%40googlegroups.com.