[weewx-user] Re: adding extension which applies to reporting on one file only

[gjr80]

Hi Rich,

Unfortunately the SLEs are applied to each report in a skin. Can you pull 
out the template concerned into its own skin and use the SLE in that skin 
only? 

Gary

On Thursday, 5 April 2018 14:59:13 UTC+10, Rich Altmaier wrote:
>
> I'm creating a Report extension which is fairly expensive to calculate.  
> When I add my extension to skin.conf, with the usual  
> search_list_extensions under CheetahGenerator, I find my extension is 
> invoked about 14 times, which costs many seconds.   Is it possible to make 
> a Report extension apply to a selected file generation, such as in 
> generating index.html only?
> Thank you!
> Rich
>
>

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

[weewx-user] adding extension which applies to reporting on one file only

['Rich Altmaier' via weewx-user]

I'm creating a Report extension which is fairly expensive to calculate.  
When I add my extension to skin.conf, with the usual  
search_list_extensions under CheetahGenerator, I find my extension is 
invoked about 14 times, which costs many seconds.   Is it possible to make 
a Report extension apply to a selected file generation, such as in 
generating index.html only?
Thank you!
Rich

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

Re: [weewx-user] Re: weewx crashes with error: unpack requires a string of len 104

[vk3anz]

You are not being a nuisance at all, but it is a bit hard to do 'remote 
diagnostics'.

The log file would be useful but not the whole thing: just the part a bit 
before you start weewx until just after it has stopped will be enough.

Where are you setting the loop delay value and can you show us the 
file/line in question?

Susan

On Thursday, April 5, 2018 at 2:20:53 AM UTC+10, Graham Seward wrote:
>
> Hi Susan
>
> Regret to say that weewx stopped running again without writing anything to 
> syslog, messages or user.log. Syslog shows that when weewx starts it is 
> using the correct version of the driver, so I’m puzzled as to what is going 
> on. Would you like a copy of the syslog file in it’s entirety to see if 
> that throws up any clues?
>
>  
>
> I’m going to run weewx again but with your original driver to see what 
> happens this time. Incidentally if I set the loop-delay to 60 secs the 
> program doesn’t run at all – currently set at 30secs. 
>
>  
>
> Sorry to be a nuisance!
>
> Graham
>
>  
>
> *From:* weewx...@googlegroups.com   > *On Behalf Of *vk3...@gmail.com 
> *Sent:* 04 April 2018 03:50
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] Re: weewx crashes with error: unpack requires 
> a string of len 104
>
>  
>
> G - too long since I wrote the code and I made a stupid mistake. The 
> two 'loginf' lines should read
>
>  
>
> loginf('Bad data: length = {0}'.format(len(rxData)))
>
> loginf('Bad data: "{0}"'.format(rxData))
>
>  
>
> I've attached your file with the correction in it.
>
>  
>
> Sorry about that.
>
>  
>
> 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+...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>

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

[weewx-user] Re: WU Import failed

[gjr80]

Hi,

The problem appears to be that the radiation data for your station on WU is 
recorded as '---' instead of it being blank or a numeric. It is a simple 
fix to ignore the '---' but I just need to work through some other parts of 
wee_import to make sure I do not introduce some inconsistent behaviour. 
Give me a day or 2 and I should have a revised wee_import that will do the 
job.

Gary

On Wednesday, 4 April 2018 01:16:46 UTC+10, Andre wrote:
>
> Hi,
>
> First I have to say I'm not Linux professional and all my 'know-how' is 
> based on reading a lot of tutorials.
>
> My weather station is a Davis Vantage Vue. WeeWX is running on a Raspberry 
> Pi 2. This setup is running and all data are fine.
>
> My problem is I can't import any data from WU with wee_import.
>
> ---log---
> wee_import --import-config=/var/tmp/wu.conf --from=2018-01-01T00:30 --to=
> 2018-01-31T00:00 --dry-run
> Starting wee_import...
> Observation history for Weather Underground station 'INORDERS99' will be 
> imported.
> Using database binding 'wx_binding', which is bound to database 
> 'weewx.sdb'
> Destination table 'archive' unit system is '0x01' (US).
> Observations timestamped after 2018-01-01 00:30:00 CET (1514763000) and 
> up to and
> including 2018-01-31 00:00:00 CET (1517353200) will be imported.
> This is a dry run, imported data will not be saved to archive.
> * radiation: cannot convert '---' to float at timestamp '2018-01-01 
> 00:30:00 CET (1514763000)'.*
>  Nothing done, exiting.
> ---log---
>
> What does it mean "radiation: cannot convert '---' to float at timestamp 
> '2018-01-01 00:30:00 CET (1514763000)'?
> Is there data mismatch on WU? What can I do to solv this issue?
>
> Regards, Andre
>

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

[weewx-user] Re: wee_import from Weather Underground with UV Index

[gjr80]

Hi,

My apologies, wanted to sit down and try a few things with WU before 
replying.

It does indeed look like we can get UV from the XML. I have no idea why 
non-XML queries do not return UV, maybe just have to put it down to another 
of the vagaries of WU. From the quick look I had this morning I see no 
reason why a XML based import cannot be implemented, wee_import was written 
with a very modular structure so hopefully it is easy to implement. I 
cannot see any downsides, other than the fact that the XML response seems 
about 10 time the byte size of an equivalent CSV response (there is a lot 
of repeated crud in the XML response) - probably not an issue these days 
though.

I will put it on the list to do, hopefully to be included in the next 
release (as long as Tom does not spring 3.8.1 on us in the week or so).

Thanks.

Gary

PS. In answer to your last question, I am not aware of any simple way to 
import UV data from WU. Your WU data is not going anywhere (I hope) so if I 
get the XML import working there should be no reason why you cannot just 
add in the missing UV data later.

On Thursday, 29 March 2018 14:09:30 UTC+10, Daniel Welty wrote:
>
> I have been running my weather station for a few months before I got weewx 
> installed.  During that time it uploaded to Weather Underground, so I took 
> advantage of wee_import to back fill all of the previous data.
>
> I noticed that it doesn't include the UV Index and that isn't mentioned in 
> the documentation.  It looks like it uses this URL format: 
> http://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=%s=%d=%d=%d=1
>
> I noticed that when using the XML format then UV data is available. 
> http://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=%s=%d=%d=%d=XML
>
> Has anyone tried to import from the XML format?  Or is there an easier way 
> to accomplish getting the UV data?
>

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

[weewx-user] Re: WMR300 testing LAST Driver

[Ruben Navarro Huedo]

I have 10 days uptime with this driver version.

I think all is stable now :-D

Thank's a lot for your work.

El sábado, 17 de marzo de 2018, 13:53:04 (UTC+1), Ruben Navarro Huedo 
escribió:
>
> I am trying it now.
>
> I will tell result in some hours.
>
> Mar 17 13:51:31 MeteoElche weewx[9026]: wmr300: content: d2 80 00 3f 
> ee ee ee 00 0a 00 e9 00 00 7f ff 7f ff 7f ff 7f ff 7f ff 7f ff 7f ff 20 04 
> 7f 7f 7f 7f 7f 7f 7f 00 08 7f ff 7f ff 7f ff 7f ff 7f ff 7f ff 7f ff 7f fd 
> 7f ff 7f ff 7f ff 7f ff 7f ff 7f ff 7f ff 7f fd 7f ff 00 15 00 02 00 02 00 
> 14 00 00 00 00 00 00 02 00 11 03 09 0f 01 00 00 27 e1 01 7f ff 7f ff 7f ff 
> 7f ff 7f 7f 7f 7f 7f 7f 7f 7f ff 7f ff 7f ff 00 00 00 00 00 00 00 0f 01
> Mar 17 13:52:20 MeteoElche weewx[9026]: wmr300: get history complete: 
> count=0 last_index=15584 history_end_index=15585
> Mar 17 13:52:20 MeteoElche weewx[9026]: engine: Starting main packet loop.
> Mar 17 13:52:21 MeteoElche weewx[9026]: wmr300: dump history
> Mar 17 13:52:21 MeteoElche weewx[9026]: wmr300: reading records since 
> 2018-03-17 13:52:21 CET (1521291141) (last_index=15584 
> history_end_index=15585)
> Mar 17 13:52:21 MeteoElche weewx[9026]: wmr300: get history complete: 
> count=0 last_index=15584 history_end_index=15585
>
>
>
> El sábado, 17 de marzo de 2018, 1:18:02 (UTC+1), Cameron D escribió:
>>
>> Following up on my last post, I decided to bump the failure rate and ran 
>> raid-check every day.
>> This revealed gaps up to 2 minutes between heartbeats, which confirmed 
>> the diagnosis, so I have added the code to send a restart and it seems to 
>> be keeping it alive.
>>
>> I have attached what I hope is a working version, with various diagnostic 
>> log outputs.
>>
>> Ruben, it would be good if you could try this out.  I don't think your 
>> problems relate to the actual history reset code, but if you could leave 
>> the history_limit value at 5 or 6% then it helps confirm that that code is 
>> OK.  In fact, I can't think of a good reason to have it much higher than 
>> that.
>>
>> Cameron.
>>
>

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

RE: [weewx-user] Re: weewx crashes with error: unpack requires a string of len 104

[Graham Seward]

Hi Susan

Regret to say that weewx stopped running again without writing anything to 
syslog, messages or user.log. Syslog shows that when weewx starts it is using 
the correct version of the driver, so I’m puzzled as to what is going on. Would 
you like a copy of the syslog file in it’s entirety to see if that throws up 
any clues?

 

I’m going to run weewx again but with your original driver to see what happens 
this time. Incidentally if I set the loop-delay to 60 secs the program doesn’t 
run at all – currently set at 30secs. 

 

Sorry to be a nuisance!

Graham

 

From: weewx-user@googlegroups.com  On Behalf Of 
vk3...@gmail.com
Sent: 04 April 2018 03:50
To: weewx-user 
Subject: Re: [weewx-user] Re: weewx crashes with error: unpack requires a 
string of len 104

 

G - too long since I wrote the code and I made a stupid mistake. The two 
'loginf' lines should read

 

loginf('Bad data: length = {0}'.format(len(rxData)))

loginf('Bad data: "{0}"'.format(rxData))

 

I've attached your file with the correction in it.

 

Sorry about that.

 

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 
 .
For more options, visit https://groups.google.com/d/optout.

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

[weewx-user] Re: Problem with installation when setting up on Digital Ocean ubuntu server - perhap caused by use of firewall - ufw

[Devonian]

I'm guessing the IP address of 10.0.1.42 is the IP address of the 
Weatherlink IP sat on your home network?

The droplet has no knowledge of that address, hence the error message.  It 
also has nothing to do with ufw.

If the WL IP is sat on your home network, you will need to open port  
on your home router from the internet and forward it to 10.0.1.42 (port 
forward rule).
You will also need to know the public IP address of your home router 
(hopefully it will be a static address rather than a dynamically assigned 
one) - let's assume it's 1.2.3.4 (it won't be, but for this example we'll 
assume it)

In the droplet config, you need to set weewx to look for the VP2 on your 
public IP address of 1.2.3.4 (instead of 10.0.1.42).

HTH

Nigel.


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