[weewx-user] Re: Current wind graphic?

[RobbH]

On the other hand, it may be possible to do all I need with javascript, and 
I'll probably try that first.

A crude version, without making the wind directional pointer proportional 
to wind speed, can be done with svg graphics and no outside help. I've 
posted that to the old thread that I linked in the first post.


On Friday, March 30, 2018 at 8:27:41 PM UTC-4, RobbH wrote:
>
> Maybe, at long last, I'm going to have to buckle down and learn enough of 
> Python to do this!
>
>
> On Friday, March 30, 2018 at 6:51:49 PM UTC-4, vince wrote:
>>
>> On Friday, March 30, 2018 at 1:54:30 PM UTC-7, RobbH wrote:
>>>
>>> Still pursuing this, and I have learned how to generate the sort of 
>>> image I want, but not within Weewx. Is it possible call an external program 
>>> (shell script) during each report cycle?
>>>
>>>
>> It is possible to do darn near anything if you write an extension to do 
>> so.assuming the account weewx runs as has privileges to do so.
>>  
>>
>

-- 
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: WeeWX now also with wind rose.

[RobbH]

This a very old thread, but it still turns up in searches. Here's a simple 
way to do a crude version of what the original poster was doing. That is, a 
display of the most recent wind direction on the background of a compass 
rose, not a wind rose, showing history. May not work in all browsers, but 
hasn't failed me yet.

Add the following code to index.html.tmpl. I created a table with one row 
of two cells at the top of the page, put the masthead text in the left cell 
and this in the right cell:

http://www.w3.org/2000/svg;>
 
 
 
 
 N
 S
 W
 E
 
 $current.windSpeed.formatted
 #if $current.windDir.formatted != "   N/A"
 
 #end if


I hope someone finds this helpful, and that someone will improve on it.


On Friday, June 24, 2016 at 11:56:03 AM UTC-4, Panos Vatikiotis wrote:
>
> Well it worked for me too and thank you all! I could not find any roses so 
> i made some by photoshop so here
> they are: http://www.milosbeach.gr/weatherstation/
>
> On Monday, 3 February 2014 16:18:12 UTC+2, gonk smith wrote:
>>
>>
>> ok, I got it work for low wind speed, eg < 1. ( I have a Fine Offset USB 
>> Weather station)
>>
>> 1. I created 9 rose.png files on my pc, with rose0.png = north pointing 
>> compass picture, rose1.png = north/east pointing compass picture, etc. 
>>  With the exception of rose8.png, it is pointer-less picture of the compass 
>> as it represents no wind.
>> 2. I uploaded all 9 rose.png files to the folder "public_html"
>> 3. I placed this code (below) near the top of the file "index.html.tmpl" 
>> in the folder  /skins/Standard..eg the bold is code that was already 
>> present, just to show exactly where I placed it. I worked out what the 
>> minus in front of the equals does... eg  #set $octant-= 8.  This is 
>> correct. I still had to change "*#set $bigdir=$winddir+360.0-22.5"* to 
>> *"**#set $bigdir=$winddir+22.5"*
>>
>>
>> *#errorCatcher Echo*
>>
>> #def rose_file($winddir)
>> #set $bigdir=$winddir+22.5
>> #set $octant=int($bigdir/45.0)
>> #if $octant >= 8
>> #set $octant-= 8
>> #end if
>> $("rose"+str($octant)+".png")
>> #end def
>>
>> *##$Revision: 1669 $*
>> .
>> .
>> *.further down in the file index.html.tmpl*
>> .
>>
>> 4. I Added this code into index.html.tmpl to check for low wind with 
>> stops the N/A problem, I placed it near the bottom of the tables for now..
>>
>> * *
>>
>>  #if $current.windSpeed.raw  < 1
>>  
>>   #else 
>>   
>>   #end if
>>
>> *  #if $day.radiation.has_data*
>>
>>
>>
>> I hope this helps... and thanks a heap Tom K...it is a very nice tool.
>>
>

-- 
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: Realtime rain data with CRT service, Interceptor driver and AcuRite sensor/hub

[RobbH]

Thanks. I understand that, for a change.

So there's no way to work around that? Those fields are not updated until 
the end of the archive interval, but the value I want is available to the 
driver as rain_total, but it is not mapped to a weewx field. Is there any 
way to pass that value to the crt service, without waiting for weewx to do 
its calculations?



On Friday, March 30, 2018 at 9:54:25 PM UTC-4, mwall wrote:
>
> On Friday, March 30, 2018 at 6:00:14 PM UTC-4, RobbH wrote:
>>
>>
>> We can see that field 10 (rain today) and 48 (rainfall last hour) still 
>> contain zero. They will be updated in another minute, at the end of the 
>> archive period.
>>
>> How might I get the current value of rain_total.2774.* into the 
>> realtime.txt file?
>>
>
> the rain today and rain last hour are calculated from the database, and 
> the database is updated each archive interval.  this would explain the 
> behavior you see.
>
> m 
>

-- 
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: using apache2 with weewx

[vince]

On Saturday, March 31, 2018 at 9:15:28 AM UTC-7, William Webb wrote:
>
> So does anyone know how to change the where apache2 finds index.html in 
> the current version of stretch?
>
>>
>>

Well that's more of a question for a Debian forum as it's not 
weewx-specific, but you should find a config file in 
/etc/apache2/sites-enabled that has a DoumentRoot entry in it that you can 
edit.  Then do a restart of apache2. 

-- 
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: using apache2 with weewx

[William Webb]

To some extent, I answered my own question.  It can be done with a symLink 
after deleting or renaming the existing index.html in /var/www/html.

ln -s /var/www/html/weewx/index.html

There may be a cleaner way.

On Saturday, March 31, 2018 at 9:15:28 AM UTC-7, William Webb wrote:
>
> I was hoping to use option #1. This is where I ran into trouble. From the 
> instructions that I googled it is only necessary to edit sites-available  
> and sites-enabled to point to the new location.  This had no effect.  Some 
> instruction mention editing hppd.conf.  I could not find it anywhere.  My 
> assumption is that the instructions I was reading either do no apply to 
> Debian or are old.
>
> So does anyone know how to change the where apache2 finds index.html in 
> the current version of stretch?
>
> thanks Bill - AB6OR
>
>
> On Friday, March 30, 2018 at 6:36:24 PM UTC-7, mwall wrote:
>>
>> On Friday, March 30, 2018 at 9:30:15 PM UTC-4, William Webb wrote:
>>>
>>> As set up right now my weather station page is reached by 
>>> 192.168.0.38/weewx.
>>>
>>> I would like to simplify this so that apache2  opens index.html directly 
>>> as 192.168.0.38
>>>
>>> Can someone lead me by the hand or give me a link to correct, current 
>>> instructions?
>>>
>>
>>
>>
>> option 1: set DocumentRoot in your apache configuration to be the 
>> directory where weewx puts files
>>
>> option 2: set HTML_ROOT in your weewx skin configuration to be the 
>> document root of your apache configuration
>>
>>

-- 
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: using apache2 with weewx

[William Webb]

I was hoping to use option #1. This is where I ran into trouble. From the 
instructions that I googled it is only necessary to edit sites-available  
and sites-enabled to point to the new location.  This had no effect.  Some 
instruction mention editing hppd.conf.  I could not find it anywhere.  My 
assumption is that the instructions I was reading either do no apply to 
Debian or are old.

So does anyone know how to change the where apache2 finds index.html in the 
current version of stretch?

thanks Bill - AB6OR


On Friday, March 30, 2018 at 6:36:24 PM UTC-7, mwall wrote:
>
> On Friday, March 30, 2018 at 9:30:15 PM UTC-4, William Webb wrote:
>>
>> As set up right now my weather station page is reached by 
>> 192.168.0.38/weewx.
>>
>> I would like to simplify this so that apache2  opens index.html directly 
>> as 192.168.0.38
>>
>> Can someone lead me by the hand or give me a link to correct, current 
>> instructions?
>>
>
>
>
> option 1: set DocumentRoot in your apache configuration to be the 
> directory where weewx puts files
>
> option 2: set HTML_ROOT in your weewx skin configuration to be the 
> document root of your apache configuration
>
>

-- 
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: Ambient Weather WS-2902 reporting troubles with the interceptor extension

[jan hallink]

I don't know which router you have, but I have a Asus rt-n66u
This router have a possibility of command line access (telnet or ssh)

What I did is the following:
enable SSH in my router
connect with putty (or other ssh client) to my router
type the 2 iptable rules

after that, interceptor driver could read the 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.

Re: [weewx-user] Re: Adding archive data to daily report

[Thomas Carlin]

Hi Chris,
Sorry it took so long, I started a new job a few weeks ago, and hobbies 
have taken a back seat!  Let me start by saying that all the information, 
and better descriptions of what is happening can be found in the Weewx 
Customization Guide that TK and the guys have put together.  
http://weewx.com/docs/customizing.htm

All of the back end is contained in one file, On my system 
\usr\share\weewx\user\ArchiveSearch.py  Look at Defining New Tags 
 in the docs, the 
similarities should be immediately apparent.  This then get's included in 
the search list extensions in skin.conf.  You can then include your new 
tags in your *.tmpl files, to be generated each time the generator runs. 

First the ArchiveSearch.py:  I removed most of the comments that are in the 
documentation for the sake of brevity.  It is worth noting that you may 
need to install python relativedelta on your system for this to work.

*import datetime*
*import time*
*from dateutil.relativedelta import relativedelta*

*from weewx.cheetahgenerator import SearchList*
*from weewx.tags import TimespanBinder*
*from weeutil.weeutil import TimeSpan*
*from weeutil.weeutil import archiveDaySpan*
*from weeutil.weeutil import archiveWeekSpan*
*from weeutil.weeutil import archiveMonthSpan*
*from weeutil.weeutil import archiveYearSpan*

*class ArchiveSearch(SearchList):  
   # 1*
*"""My search list extension"""*

*def __init__(self, generator):
   # 2*
*SearchList.__init__(self, generator)*

*def get_extension_list(self, timespan, db_lookup):
   # 3*
*"""Returns a search list extension with two additions.*

*Parameters:*
*  timespan: An instance of weeutil.weeutil.TimeSpan. This will*
*hold the start and stop times of the domain of *
*valid times.*

*  db_lookup: This is a function that, given a data binding*
* as its only parameter, will return a database manager*
* object.*


*"""*
*# First, create TimespanBinder object for all time. This one is 
easy*
*# because the object timespan already holds all valid times to be*
*# used in the report.*
*all_time = TimespanBinder(timespan, *
*   db_lookup,*
*   formatter=self.generator.formatter,*
*   converter=self.generator.converter,*
*  context="month")   # 4*

*# Now get a TimespanBinder object for the last seven days. This 
one we*
*# will have to calculate. First, calculate the time at midnight, 
seven*
*# days ago. The variable week_dt will be an instance of 
datetime.date.*
*today_last_year_dt = datetime.date.fromtimestamp(timespan.stop) - 
relativedelta(years=1)*

*# Convert it to unix epoch time:*
*today_last_year_ts = time.mktime(today_last_year_dt.timetuple())  
 # 6*



*today_last_year_time_span = archiveDaySpan(today_last_year_ts)*
*# Form a TimespanBinder object, using the time span we just*
*# calculated:*
*today_last_year= TimespanBinder(today_last_year_time_span,*
* db_lookup,*
*
 formatter=self.generator.formatter,*
*
 converter=self.generator.converter,*
* context="month") # 7*
*#Assembles this week last year*
*week_last_year_time_span = archiveWeekSpan(today_last_year_ts)*
*# Form a TimespanBinder object, using the time span we just*
*# calculated:*
*week_last_year= TimespanBinder(week_last_year_time_span,*
* db_lookup,*
*
 formatter=self.generator.formatter,*
*
 converter=self.generator.converter,*
* context="month") # 7*


*#Assembles this month last year.*
*month_last_year_time_span = archiveMonthSpan(today_last_year_ts)*
*# Form a TimespanBinder object, using the time span we just*
*# calculated:*
*month_last_year= TimespanBinder(month_last_year_time_span,*
* db_lookup,*
*
 formatter=self.generator.formatter,*
*
 converter=self.generator.converter,*
* context="month") # 7*

*#Assembles last year.*
*last_year_time_span = archiveYearSpan(today_last_year_ts)*
*# Form a TimespanBinder object, using the time span we just*
*# calculated:*
*last_year= 

Re: [weewx-user] Re: Calculate the sum of a weekly energy production for a solar panel

[Thomas Keffer]

1. This may be resulting from confusion of what the timestamps represent.
In weeWX, all data in a time period is timestamped by the *end* of that
period. As an example, data for a 5 minute archive period with a timestamp
0950 Tuesday, is the data from (but not including) 0945 up to *and
including* 0950.

That's for a single archive record. Now think about aggregations over a
day. Take a day like Tuesday. The tag $day.outTemp.avg is the average
temperature for Tuesday, which is the average temperature for times *greater
than* midnight Tuesday through times less than *or equal to *midnight
Wednesday. So, $day.outTemp.last is the temperature for the very last
record in that aggregation interval, which is going to be timestamped
midnight Wednesday. That is, it represents the temperature from 2355
Tuesday to  Wednesday. By contrast, $day.dateTime is the time of the
*beginning* of that period, which is midnight Tuesday.

If $day.electric_ed.last is the data for the following day (Wednesday, in
our example), then it is being timestamped wrong.

2. There is no tag for something like that. You would have to keep your own
running total, or write a search list extension.

3. Documented in the Customizing Guide
. Timestamps
use strftime
formatting

.

Putting it all together, and it should look something like (NOT TESTED):

#set $week_total=0
#for $day in $week.days
 The energy production for $day.dateTime.format("%A") is
$day.electric_ed.last
#set $week_total += $day.electric_ed.last.raw
#end for
Energy production for the week: $week_total

Note that $week_total will be just a raw number. It would be up to you to
provide any formatting.

-tk

On Sat, Mar 31, 2018 at 5:31 AM, Marco Biner  wrote:

> Hi Tom
> thank you for the fast reply.
> I added your code to my report, but it summarisez all stored values from a
> day, not the last value.
> I have to clarify that the logger of the solar panel gives everytime it is
> polled the sum of the daily solar production.
> The modification of your code, like this:
>
> #for $day in $week.days
> The energy production for $day.dateTime is $day.electric_ed.sum
>
>  The energy production for $day.dateTime is
> $day.electric_ed.last
>
> #end for
>
> gives the following output:
>
> The energy production for 00:00 is 2777070.68 Wh
>
> The energy production for 00:00 is 4105.47 Wh
>
> The energy production for 00:00 is 1814408.75 Wh
>
> The energy production for 00:00 is 2380.86 Wh
>
> The energy production for 00:00 is 2188879.96 Wh
>
> The energy production for 00:00 is 3105.47 Wh
>
> The energy production for 00:00 is 2349953.71 Wh
>
> The energy production for 00:00 is 3298.83 Wh
>
> The energy production for 00:00 is 3153128.84 Wh
>
> The energy production for 00:00 is 4515.62 Wh
>
> The energy production for 00:00 is 112733.52 Wh
>
> The energy production for 00:00 is 1305.66 Wh
>
> The energy production for 00:00 is N/A
>
> The energy production for 00:00 is N/A
>
>
> there I have two issues:
>
> 1. for today I get N/A and all other results are one day shiftet, means
> the value of 1305.66 is actual production of today,  4515.62 is from
> yesterday
>
> 2. I need the sum for the last seven days, which is the sum of
> $day.electric_ed.last
>
> 3. Question by the way, why is $day.dateTime alway 00:00
>
> Kind regards
> Marco
>
> --
> 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] temperatures at specific date and time

[stefano siega]

I would like to know the temperature at a specific time and date. Something 
like: 

$(1490956200)outTemp.formatted
or 
$(year_ago= 1).outTemp.formatted. 

I tried it over and over again but I could not make it work. How can I do? 

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

Re: [weewx-user] Re: Internal Temp - WunderStation

[Thomas Keffer]

Fixed in commit 981a0e4

.

-tk

On Fri, Mar 30, 2018 at 9:36 PM, Andrew Milner 
wrote:

> Matthew - That option seems to be missing from the user guide!!
>
>
>
> On Saturday, 31 March 2018 05:11:01 UTC+3, mwall wrote:
>
>>
>>
>> On Friday, March 23, 2018 at 5:50:56 AM UTC-4, Sam Walton wrote:
>>>
>>> Hi All,
>>>
>>> I have an IPad with Wunderstation installed, Has anyone successfully
>>> outputted the Internal Temp into Wunderground so I can see it in the app?
>>>
>>
>> did you try the 'post_indoor_observations' option in the wu stanza of
>> your weewx configuration?
>>
>> [StdRESTful]
>> [[Wunderground]]
>> post_indoor_observations = true
>>
>> m
>>
> --
> 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: Calculate the sum of a weekly energy production for a solar panel

[Marco Biner]

Hi Tom
thank you for the fast reply.
I added your code to my report, but it summarisez all stored values from a 
day, not the last value.
I have to clarify that the logger of the solar panel gives everytime it is 
polled the sum of the daily solar production.
The modification of your code, like this:

#for $day in $week.days
The energy production for $day.dateTime is $day.electric_ed.sum

 The energy production for $day.dateTime is $day.electric_ed.last

#end for

gives the following output:

The energy production for 00:00 is 2777070.68 Wh

The energy production for 00:00 is 4105.47 Wh

The energy production for 00:00 is 1814408.75 Wh

The energy production for 00:00 is 2380.86 Wh

The energy production for 00:00 is 2188879.96 Wh

The energy production for 00:00 is 3105.47 Wh

The energy production for 00:00 is 2349953.71 Wh

The energy production for 00:00 is 3298.83 Wh

The energy production for 00:00 is 3153128.84 Wh

The energy production for 00:00 is 4515.62 Wh

The energy production for 00:00 is 112733.52 Wh

The energy production for 00:00 is 1305.66 Wh

The energy production for 00:00 is N/A

The energy production for 00:00 is N/A


there I have two issues:

1. for today I get N/A and all other results are one day shiftet, means the 
value of 1305.66 is actual production of today,  4515.62 is from yesterday

2. I need the sum for the last seven days, which is the sum of 
$day.electric_ed.last

3. Question by the way, why is $day.dateTime alway 00:00

Kind regards
Marco

-- 
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: Fine Offset lockup (possible to recover data?)

[mwall]

On Saturday, March 31, 2018 at 3:45:35 AM UTC-4, Richard Cain wrote:
>
> Hi
> Thanks for the reply. On my console there is an icon which shows the 
> memory, this doesn't clear with a power cycle so it has retained the data. 
> So again, any chance of getting this data?
>

ah, you have a 30xx.  those retain data through a power cycle.

weewx will only pull data from the logger if the data are newer than the 
latest data in the weewx database

so after a lockup, weewx *should* pull the data since the lockup began

use the wee_device utility to see exactly what is in the logger

wee_device --history

this will dump all of the data from the logger.  then you can put that into 
the weewx database using sqlite tools.

m

-- 
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] spurious gaps within weather data - wh23xx on raspberry pi 3

[Michale Waldor]

Now I have tried two things:

1. I have moved the sensor array from balcony into the garden. Now there 
are no longer gaps in the data.

2. I have tried to use the power supply for my raspberry to also feed the 
base station. This worked for half a day - but in the early morning USB 
connection between base station and Raspy died completely. Thus I conclude 
that either my power supply is too weak, or there are some spikes on the 
power net which might have disturbed the base station. But only the USB 
connection has died, the weather station itself worked smoothly including 
logging of data.
Thus I have withdrawn my idea to use the power supply for the base station, 
too.

-- 
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: Fine Offset lockup (possible to recover data?)

[Richard Cain]

Hi
Thanks for the reply. On my console there is an icon which shows the 
memory, this doesn't clear with a power cycle so it has retained the data. 
So again, any chance of getting this data?

On Saturday, 31 March 2018 02:58:58 UTC+1, mwall wrote:
>
> On Tuesday, March 27, 2018 at 5:21:05 AM UTC-4, Richard Cain wrote:
>>
>> However, my question is this, I've lost all the data while my station was 
>> locked as there are no records in the database file. Is there no way to get 
>> this data back?
>>
>
> when the station usb locks up, the station still functions, and apparently 
> still records data to the logger.  unfortunately, the only way to fix the 
> lockup is to power cycle the station, and power cycling the station clears 
> the logger memory.
>
> fine offset fixed this in the next generation of station.  the wh23xx 
> logger retains data even through a power cycle.  the wh23xx also does not 
> suffer usb lockups (actually i have seen some with the wh23xx, but i was 
> abusing the usb pretty badly)
>

-- 
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.