Re: [weewx-user] Re: Second crash after 11 days

[gjr80]

Steve,

When I look at your gauges just now they are not working, the clue is in 
the scroller message - 'error: Not Found'. This means the gauges.js script 
cannot find gauge-data.txt. I suppose it is possible that when we 
uncommented the SteelSeries skin a few days ago to get your plots back that 
caused your web server gauges.js to be overwritten with the default 
gauges.js (or a version that is not up to date with your latest setup). 
Though if this were the case/cause I would have expected the gauges to stop 
straight away and I remember seeing them working properly after your plots 
came back. No matter, this is clearly a case of gauges.js not finding 
gauge-data.txt. I can see that gauge-data.txt is being updated on your web 
server every few seconds so rtgd is doing its job. The file is located in 
photokinetics.org/Weather/. To fix it, on your WeeWX machine, edit 
skins/SteelSeries/scripts/gauges.js and find the realTimeUrlWeewx setting 
at about line 74, it probably looks like:

realTimeUrlWeewx : 'gauge-data.txt', // *** WeeWX Users: Change 
to your location of the gauge data file **


Try changing the setting to '../gauge-data.txt'. Save the file and the 
restart WeeWX. The next report cycle should seethe modified gauges.js 
uploaded to your server and hopefully the gauges will come on line.

Gary

On Tuesday, 28 May 2019 10:25:26 UTC+10, Steve2Q wrote:
>
> Gary...I was away for the weekend, so when I checked in using the Chrome 
> browser on my phone, the Steel Gauges were, and still are, working. 
> However, if I pull up the guages on my desktop or tablet, they are frozen 
> and "offline".  Please take a look at photokinetics.org/Weather and click 
> on the Steel Gauges button at the bottom and see if you observe the same 
> behavior. I tried both Chrome and Firefox on both devices. 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/4b1de92a-fc25-4050-b692-d9dfb54033b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Weather34 Template for WeeWX - New Major Update

[Jd D]

Hi Ian,
No problem with the name been called a lot worst in the past. :-)
 I do have a suggestion for the displaying and graphing of different units 
that I have tested. But first I like to explain my reasons for doing 
something different. Right now I am using US units with a device that is 
sending US unit data. To do it the current way (which I still see issues 
with) the system would have to convert the F data in the database to C and 
then back to F when I display it. From a CS point of view these types of 
operations really should be avoided. Also I am using the CRT data for other 
systems which means I would have to convert the data for those systems. To 
me the biggest reason I do not like the current approach is the data is in 
the database with its "native" units. Just by adding $unit.label.outTemp to 
the result template and now I know the units of the data where ever I use 
it. Then all I needed was a three line javascript function to compare the 
units of the data with the units I am displaying and decide if a conversion 
is needed. For me this removes three conversions of the data and works for 
both C and F settings of the template. I can send you what I have if it 
would help understand what I am getting at. I still need to send you my 
other changes but I am making sure I have not missing anything.
Thanks
Jake aka Jerry

On Monday, May 27, 2019 at 5:43:58 PM UTC-7, steeple ian wrote:
>
> Whoops,
>
> Sorry Jerry, this was meant for you not Jake.
>
> Ian
>
> On 27 May 2019, at 23:01, steeple ian > 
> wrote:
>
> Hi Jake,
>
> I now see what is happening and the reason that you are having to change 
> things when they relate to non metric units.
>
> The template is designed to receive realtime data in metric units. One of 
> the early roots for this template was based on Cumulus realtime.txt, which 
> by default emits metric units, that is why the CRT extension should be set 
> for METRIC in the weewx.conf file (as per the snippet in the install guide. 
> Unless, of course you are also using CRT for an additional purpose which 
> requires US units). Give it a try with the original files and see what 
> happens.
>
> I will update the instructions to emphasise this important point.
>
> Regarding the dew point graphs appearing instead of rainfall, I did 
> exactly as you suggested. I realised what happened when I was updating the 
> charts for another purpose 3 days ago and I fixed them at the same time.
>
> Regards Ian
>
> On 27 May 2019, at 19:22, Jd D > 
> wrote:
>
> Hi Ian,
>
> It is set to
> unit_system = US
>
> Also a couple chart items.
> 1) Yearly and Monthly rainfall charts are dew point charts in your 
> release. Looks like something got overwritten or renamed. The file names 
> are correct just the code inside does not match the file name.
>
> 2) Also had to comment out the conv code for the barometer charts so the 
> charts matched my units inHg.
>
> Thanks Jerry
>
> On Monday, May 27, 2019 at 11:11:23 AM UTC-7, steeple ian wrote:
>>
>> Jerry,
>>
>> Can I just check, have you got realtime.txt set for US units or METRIC 
>> units in your weewx.conf file?
>>
>> On Mon, May 27, 2019 at 6:09 PM steeple ian  wrote:
>>
>>> Hi Jerry,
>>> That’s excellent information. I will be very interested to have a copy 
>>> of the livedata and other file changes when you have completed them.
>>> Thank you very much,
>>> Ian 
>>>
>>> Sent from my iPhone
>>>
>>> On 27 May 2019, at 17:53, Jd D  wrote:
>>>
>>> Hi Ian,
>>>
>>> Here are a couple more. The following code exists in multiple graphs and 
>>> causes the graphs to be messed up since the data is already Fahrenheit . 
>>> Not sure why this was needed at all. I commented it out to fixed the graphs
>>> .//  if ($tempunit == 'F') {
>>> //  $conv = '(9 / 5) + 32';
>>> //  } else {
>>> $conv = '1';
>>> //  }
>>>
>>> Also in shared.php looks like a cut and paste error deleted most of the 
>>> code for function anyToF. The bold text below was what I added.
>>>  
>>> function anyToF($field){
>>> *global $weather;*
>>> *if ($weather["temp_units"] == 'F'){*
>>> *return $field;*
>>> *} else {*
>>>
>>> return cToFDirect ($field);
>>> }
>>> *}*
>>>
>>> In barometer.php there is a hard coded 100 in a for loop that blows up. 
>>> I changed it to be the sizeof the array.
>>> for ($i = 0; $i <* sizeof($parsed_json)*; $i++) {
>>>
>>> $magnitude[$i]=$parsed_json{$i}{'magnitude'};$eqtitle[$i]=$parsed_json{$i}['title'];$depth[$i]=$parsed_json{$i}['depth'];$time[$i]=$parsed_json{$i}['date_time'];
>>>
>>> In livedata.php I made a number of changes to handle when the data was 
>>> not as expected. Like if the time value was a string instead of a integer. 
>>> I just put a (int) in front of the variable so that it would work for both 
>>> string and integer values. Did the same for float for wind speed. Also 
>>> there were a number of places where N/A was used when data did not exists 

[weewx-user] Re: RFM95W as alternative to RTL-SDR for Davis Vantage Pro 2

[John]

Maybe hook up to the console connector then.  That would upgrade both my 
active station and perhaps salvage the old one as well. Does the console 
connector provide a buffer for the data stream so that I could just have 
the ULP wake up the ESP32, read out the data buffer, write to the SD, 
transmit, and go back to sleep?

-- 
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/9f3a847d-0e28-481d-9801-aa06349370ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Weather34 Template for WeeWX - New Major Update

[steeple ian]

Whoops,

Sorry Jerry, this was meant for you not Jake.

Ian

> On 27 May 2019, at 23:01, steeple ian  wrote:
> 
> Hi Jake,
> 
> I now see what is happening and the reason that you are having to change 
> things when they relate to non metric units.
> 
> The template is designed to receive realtime data in metric units. One of the 
> early roots for this template was based on Cumulus realtime.txt, which by 
> default emits metric units, that is why the CRT extension should be set for 
> METRIC in the weewx.conf file (as per the snippet in the install guide. 
> Unless, of course you are also using CRT for an additional purpose which 
> requires US units). Give it a try with the original files and see what 
> happens.
> 
> I will update the instructions to emphasise this important point.
> 
> Regarding the dew point graphs appearing instead of rainfall, I did exactly 
> as you suggested. I realised what happened when I was updating the charts for 
> another purpose 3 days ago and I fixed them at the same time.
> 
> Regards Ian
> 
>> On 27 May 2019, at 19:22, Jd D > > wrote:
>> 
>> Hi Ian,
>> 
>> It is set to
>> unit_system = US
>> 
>> Also a couple chart items.
>> 1) Yearly and Monthly rainfall charts are dew point charts in your release. 
>> Looks like something got overwritten or renamed. The file names are correct 
>> just the code inside does not match the file name.
>> 
>> 2) Also had to comment out the conv code for the barometer charts so the 
>> charts matched my units inHg.
>> 
>> Thanks Jerry
>> 
>> On Monday, May 27, 2019 at 11:11:23 AM UTC-7, steeple ian wrote:
>> Jerry,
>> 
>> Can I just check, have you got realtime.txt set for US units or METRIC units 
>> in your weewx.conf file?
>> 
>> On Mon, May 27, 2019 at 6:09 PM steeple ian > wrote:
>> Hi Jerry,
>> That’s excellent information. I will be very interested to have a copy of 
>> the livedata and other file changes when you have completed them.
>> Thank you very much,
>> Ian 
>> 
>> Sent from my iPhone
>> 
>> On 27 May 2019, at 17:53, Jd D > wrote:
>> 
>>> Hi Ian,
>>> 
>>> Here are a couple more. The following code exists in multiple graphs and 
>>> causes the graphs to be messed up since the data is already Fahrenheit . 
>>> Not sure why this was needed at all. I commented it out to fixed the graphs
>>> .//  if ($tempunit == 'F') {
>>> //  $conv = '(9 / 5) + 32';
>>> //  } else {
>>> $conv = '1';
>>> //  }
>>> 
>>> Also in shared.php looks like a cut and paste error deleted most of the 
>>> code for function anyToF. The bold text below was what I added.
>>>  
>>> function anyToF($field){
>>> global $weather;
>>> if ($weather["temp_units"] == 'F'){
>>> return $field;
>>> } else {
>>> 
>>> return cToFDirect ($field);
>>> }
>>> }
>>> 
>>> In barometer.php there is a hard coded 100 in a for loop that blows up. I 
>>> changed it to be the sizeof the array.
>>> for ($i = 0; $i < sizeof($parsed_json); $i++) {
>>> $magnitude[$i]=$parsed_json{$i}{'magnitude'};$eqtitle[$i]=$parsed_json{$i}['title'];$depth[$i]=$parsed_json{$i}['depth'];$time[$i]=$parsed_json{$i}['date_time'];
>>> 
>>> In livedata.php I made a number of changes to handle when the data was not 
>>> as expected. Like if the time value was a string instead of a integer. I 
>>> just put a (int) in front of the variable so that it would work for both 
>>> string and integer values. Did the same for float for wind speed. Also 
>>> there were a number of places where N/A was used when data did not exists 
>>> and then those variables where used in a number format function which then 
>>> errors out. I just check to see if the variable is_numeric before calling 
>>> the number format function. I will send you my livedata.php and other files 
>>> that I have changed when I am all done if you like.
>>> 
>>> I still see few more things that do not look right that I still need to 
>>> track down.
>>> Take care
>>> Jerry
>>> 
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to weewx...@googlegroups.com <>.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/271661a7-066c-40ae-a6c9-40c622b1faed%40googlegroups.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 
>> .
>> To view this discussion on 

Re: [weewx-user] Re: Second crash after 11 days

[p q]

Do you have gauge-data.txt in the directory with your gauges? It looks like
you might not.

By the way, I got the same results with desktop chrome and on my android
phone. Could you be seeing different results because of a browser cache?

On Mon, May 27, 2019 at 5:25 PM Steve2Q  wrote:

> Gary...I was away for the weekend, so when I checked in using the Chrome
> browser on my phone, the Steel Gauges were, and still are, working.
> However, if I pull up the guages on my desktop or tablet, they are frozen
> and "offline".  Please take a look at photokinetics.org/Weather and click
> on the Steel Gauges button at the bottom and see if you observe the same
> behavior. I tried both Chrome and Firefox on both devices. 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/f0f27dc6-7ea5-4ec8-b27f-6411907e5292%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Peter Quinn
(415)794-2264

-- 
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/CAA1SM23tzWD7TJOKDNRWHEJDmOde%2B9ExfCNTkZC6-RBPNLx%2B2w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Second crash after 11 days

[Steve2Q]

Gary...I was away for the weekend, so when I checked in using the Chrome 
browser on my phone, the Steel Gauges were, and still are, working. 
However, if I pull up the guages on my desktop or tablet, they are frozen 
and "offline".  Please take a look at photokinetics.org/Weather and click 
on the Steel Gauges button at the bottom and see if you observe the same 
behavior. I tried both Chrome and Firefox on both devices. 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/f0f27dc6-7ea5-4ec8-b27f-6411907e5292%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: RFM95W as alternative to RTL-SDR for Davis Vantage Pro 2

[kobuki]

That's also doable, but a LOT of work. Plus the T/H sensor has a 
proprietary protocol, so you might need to replace that sensor. Then you 
still need to write handlers for rain, wind, solar/UV sensors (if 
installed) as they're not interfaced digitally, and light sensors are 
analog, require a special pulsing of voltage for operation, etc. If you do 
it and open source it, that might be useful for others. But then again, a 
SIM board is $128 if you live in the US...

On Tuesday, May 28, 2019 at 1:38:25 AM UTC+2, John wrote:
>
> I'm kinda assumed the whole ISS board was dead but I didn't really dive 
> into it at the time. I was thinking along the lines of just hooking up each 
> of the sensors to the esp32 and use the ULP to aggressively sleep the 
> wifi/bt between LoRa transmissions.  The modules I have came with a SD card 
> connector so maybe log everything to SD and occasionally wake up the WiFi 
> via a LoRa command for a drive by download.
>

-- 
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/7149d782-9f20-4f96-9cfe-5522fdc8f38c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: RFM95W as alternative to RTL-SDR for Davis Vantage Pro 2

[John]

I'm kinda assumed the whole ISS board was dead but I didn't really dive 
into it at the time. I was thinking along the lines of just hooking up each 
of the sensors to the esp32 and use the ULP to aggressively sleep the 
wifi/bt between LoRa transmissions.  The modules I have came with a SD card 
connector so maybe log everything to SD and occasionally wake up the WiFi 
via a LoRa command for a drive by download.

-- 
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/c8f65918-03bb-4568-b409-ed94e04501b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Add additional rain gauge via second data source

[gjr80]

On Tuesday, 28 May 2019 06:52:22 UTC+10, engolling wrote:
>
> So I started off with the noob variant...
> https://github.com/menachers/WeatherDuino/tree/master/WeeWx_Plugin
>

That looks like it will work, but be aware that if the record you are 
augmenting is in anything other than US customary units no conversion will 
be applied (this may be fine given your current setup but who knows how it 
may change in the future). Nothing to worry about if you are going to 
rewrite the code anyway.
 

> I will change it to the sophisticated procedure you proposed. 
> As I got you right
> # express our rainfall value as a ValueTuple
> rainfall_vt = weewx.units.ValueTuple(rainfall, 'mm', 'group_rain')
> I have to generate a tuple with the variable holding the actual value, 
> followed by the unit of the signal as it can be found in the units.py dict 
> and ending with the unit group which it belongs to.
>

Correct. The ValueTuple is the basis of the WeeWX system for unit 
conversion; it brings together the value, the units used and the unit group 
to which it belongs. When WeeWX needs to convert the value to some other 
units or to the units used in a particular unit system (US, Metric or 
MetricWX) the ValueTuple has the core information used to determine how to 
do the conversion. You might want to look at the class ValueTuple in 
bin/weewx/units.py 
. the 
other good thing about ValueTuple based conversion is that it will handle 
the case where the data value is None - note how in the simple approach I 
outlined we had to take care of the case where the data value may be None. 

Gary

-- 
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/5a5068ac-1c63-4aba-b741-41e05e48eb61%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Weather34 Template for WeeWX - New Major Update

[steeple ian]

Hi Jake,

I now see what is happening and the reason that you are having to change things 
when they relate to non metric units.

The template is designed to receive realtime data in metric units. One of the 
early roots for this template was based on Cumulus realtime.txt, which by 
default emits metric units, that is why the CRT extension should be set for 
METRIC in the weewx.conf file (as per the snippet in the install guide. Unless, 
of course you are also using CRT for an additional purpose which requires US 
units). Give it a try with the original files and see what happens.

I will update the instructions to emphasise this important point.

Regarding the dew point graphs appearing instead of rainfall, I did exactly as 
you suggested. I realised what happened when I was updating the charts for 
another purpose 3 days ago and I fixed them at the same time.

Regards Ian

> On 27 May 2019, at 19:22, Jd D  wrote:
> 
> Hi Ian,
> 
> It is set to
> unit_system = US
> 
> Also a couple chart items.
> 1) Yearly and Monthly rainfall charts are dew point charts in your release. 
> Looks like something got overwritten or renamed. The file names are correct 
> just the code inside does not match the file name.
> 
> 2) Also had to comment out the conv code for the barometer charts so the 
> charts matched my units inHg.
> 
> Thanks Jerry
> 
> On Monday, May 27, 2019 at 11:11:23 AM UTC-7, steeple ian wrote:
> Jerry,
> 
> Can I just check, have you got realtime.txt set for US units or METRIC units 
> in your weewx.conf file?
> 
> On Mon, May 27, 2019 at 6:09 PM steeple ian > wrote:
> Hi Jerry,
> That’s excellent information. I will be very interested to have a copy of the 
> livedata and other file changes when you have completed them.
> Thank you very much,
> Ian 
> 
> Sent from my iPhone
> 
> On 27 May 2019, at 17:53, Jd D > wrote:
> 
>> Hi Ian,
>> 
>> Here are a couple more. The following code exists in multiple graphs and 
>> causes the graphs to be messed up since the data is already Fahrenheit . Not 
>> sure why this was needed at all. I commented it out to fixed the graphs
>> .//  if ($tempunit == 'F') {
>> //  $conv = '(9 / 5) + 32';
>> //  } else {
>> $conv = '1';
>> //  }
>> 
>> Also in shared.php looks like a cut and paste error deleted most of the code 
>> for function anyToF. The bold text below was what I added.
>>  
>> function anyToF($field){
>> global $weather;
>> if ($weather["temp_units"] == 'F'){
>> return $field;
>> } else {
>> 
>> return cToFDirect ($field);
>> }
>> }
>> 
>> In barometer.php there is a hard coded 100 in a for loop that blows up. I 
>> changed it to be the sizeof the array.
>> for ($i = 0; $i < sizeof($parsed_json); $i++) {
>> $magnitude[$i]=$parsed_json{$i}{'magnitude'};$eqtitle[$i]=$parsed_json{$i}['title'];$depth[$i]=$parsed_json{$i}['depth'];$time[$i]=$parsed_json{$i}['date_time'];
>> 
>> In livedata.php I made a number of changes to handle when the data was not 
>> as expected. Like if the time value was a string instead of a integer. I 
>> just put a (int) in front of the variable so that it would work for both 
>> string and integer values. Did the same for float for wind speed. Also there 
>> were a number of places where N/A was used when data did not exists and then 
>> those variables where used in a number format function which then errors 
>> out. I just check to see if the variable is_numeric before calling the 
>> number format function. I will send you my livedata.php and other files that 
>> I have changed when I am all done if you like.
>> 
>> I still see few more things that do not look right that I still need to 
>> track down.
>> Take care
>> Jerry
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com <>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/271661a7-066c-40ae-a6c9-40c622b1faed%40googlegroups.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 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/cdf8a5f6-1543-449b-97ee-8cf564168fcf%40googlegroups.com
>  
> .
> For more options, visit 

Re: [weewx-user] Re: Weather34 Template for WeeWX - New Major Update

[steeple ian]

Hello Praveen,

This is not a skin in the normal accepted WeeWX, it is a self-contained 
dashboard template which is harnessing the power of WeeWX to feed it with live 
and archive data. There are three versions of this template, one for 
Meteobridge (the parent), one for Cumulus and and this one for WeeWX. The WeeWX 
version is by far the most versatile with the vast number of weather station 
hardware that it connect to and the ease in which archive data can be extracted 
from the database. As this version tracks the design features of the parent 
template as closely as possible, NOAA reports are not included. However, it 
would be very straightforward to do so, either by creating a link in the menu 
back to the NOAA reports in, for example,  the Standard or Seasons skin or by 
pop-up windows in the style of the template (which would be my preferred 
solution as it is in the spirit of the designer’s original concept).  

I would be very open to anyone who would want to collaborate on this idea.

Ian 

> On 27 May 2019, at 21:55, Praveen Chandrasekaran  
> wrote:
> 
> Where is the link for noaa reports in this skin ?
> 
> -- 
> 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/24609903-708e-483d-8aa7-3efcba091130%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/F393CFC7-0503-4CCB-886B-DFBFEF3B37FA%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Weather34 Template for WeeWX - New Major Update

[Praveen Chandrasekaran]

Where is the link for noaa reports in this skin ?

-- 
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/24609903-708e-483d-8aa7-3efcba091130%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Add additional rain gauge via second data source

[engolling]

Hi Gary,

sometimes I can't see the forest because of all of those trees anymore... :)
Thank you for your great answer again.

So I started off with the noob variant...
https://github.com/menachers/WeatherDuino/tree/master/WeeWx_Plugin

I will change it to the sophisticated procedure you proposed. 
As I got you right
# express our rainfall value as a ValueTuple
rainfall_vt = weewx.units.ValueTuple(rainfall, 'mm', 'group_rain')
I have to generate a tuple with the variable holding the actual value, 
followed by the unit of the signal as it can be found in the units.py dict 
and ending with the unit group which it belongs to.

best regards,
engolling

-- 
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/8ef8d2da-4c89-4629-8f21-4495fe059ba5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Weather34 Template for WeeWX - New Major Update

[Jd D]

Hi Ian,

It is set to
unit_system = US

Also a couple chart items.
1) Yearly and Monthly rainfall charts are dew point charts in your release. 
Looks like something got overwritten or renamed. The file names are correct 
just the code inside does not match the file name.

2) Also had to comment out the conv code for the barometer charts so the 
charts matched my units inHg.

Thanks Jerry

On Monday, May 27, 2019 at 11:11:23 AM UTC-7, steeple ian wrote:
>
> Jerry,
>
> Can I just check, have you got realtime.txt set for US units or METRIC 
> units in your weewx.conf file?
>
> On Mon, May 27, 2019 at 6:09 PM steeple ian  > wrote:
>
>> Hi Jerry,
>> That’s excellent information. I will be very interested to have a copy of 
>> the livedata and other file changes when you have completed them.
>> Thank you very much,
>> Ian 
>>
>> Sent from my iPhone
>>
>> On 27 May 2019, at 17:53, Jd D > 
>> wrote:
>>
>> Hi Ian,
>>
>> Here are a couple more. The following code exists in multiple graphs and 
>> causes the graphs to be messed up since the data is already Fahrenheit . 
>> Not sure why this was needed at all. I commented it out to fixed the graphs
>> .//  if ($tempunit == 'F') {
>> //  $conv = '(9 / 5) + 32';
>> //  } else {
>> $conv = '1';
>> //  }
>>
>> Also in shared.php looks like a cut and paste error deleted most of the 
>> code for function anyToF. The bold text below was what I added.
>>  
>> function anyToF($field){
>> *global $weather;*
>> *if ($weather["temp_units"] == 'F'){*
>> *return $field;*
>> *} else {*
>>
>> return cToFDirect ($field);
>> }
>> *}*
>>
>> In barometer.php there is a hard coded 100 in a for loop that blows up. I 
>> changed it to be the sizeof the array.
>> for ($i = 0; $i <* sizeof($parsed_json)*; $i++) {
>>
>> $magnitude[$i]=$parsed_json{$i}{'magnitude'};$eqtitle[$i]=$parsed_json{$i}['title'];$depth[$i]=$parsed_json{$i}['depth'];$time[$i]=$parsed_json{$i}['date_time'];
>>
>> In livedata.php I made a number of changes to handle when the data was 
>> not as expected. Like if the time value was a string instead of a integer. 
>> I just put a (int) in front of the variable so that it would work for both 
>> string and integer values. Did the same for float for wind speed. Also 
>> there were a number of places where N/A was used when data did not exists 
>> and then those variables where used in a number format function which then 
>> errors out. I just check to see if the variable is_numeric before calling 
>> the number format function. I will send you my livedata.php and other files 
>> that I have changed when I am all done if you like.
>>
>> I still see few more things that do not look right that I still need to 
>> track down.
>> Take care
>> Jerry
>>
>>>
 -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/271661a7-066c-40ae-a6c9-40c622b1faed%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/cdf8a5f6-1543-449b-97ee-8cf564168fcf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Weather34 Template for WeeWX - New Major Update

[steeple ian]

Jerry,

Can I just check, have you got realtime.txt set for US units or METRIC
units in your weewx.conf file?

On Mon, May 27, 2019 at 6:09 PM steeple ian  wrote:

> Hi Jerry,
> That’s excellent information. I will be very interested to have a copy of
> the livedata and other file changes when you have completed them.
> Thank you very much,
> Ian
>
> Sent from my iPhone
>
> On 27 May 2019, at 17:53, Jd D  wrote:
>
> Hi Ian,
>
> Here are a couple more. The following code exists in multiple graphs and
> causes the graphs to be messed up since the data is already Fahrenheit .
> Not sure why this was needed at all. I commented it out to fixed the graphs
> .//  if ($tempunit == 'F') {
> //  $conv = '(9 / 5) + 32';
> //  } else {
> $conv = '1';
> //  }
>
> Also in shared.php looks like a cut and paste error deleted most of the
> code for function anyToF. The bold text below was what I added.
>
> function anyToF($field){
> *global $weather;*
> *if ($weather["temp_units"] == 'F'){*
> *return $field;*
> *} else {*
>
> return cToFDirect ($field);
> }
> *}*
>
> In barometer.php there is a hard coded 100 in a for loop that blows up. I
> changed it to be the sizeof the array.
> for ($i = 0; $i <* sizeof($parsed_json)*; $i++) {
>
> $magnitude[$i]=$parsed_json{$i}{'magnitude'};$eqtitle[$i]=$parsed_json{$i}['title'];$depth[$i]=$parsed_json{$i}['depth'];$time[$i]=$parsed_json{$i}['date_time'];
>
> In livedata.php I made a number of changes to handle when the data was not
> as expected. Like if the time value was a string instead of a integer. I
> just put a (int) in front of the variable so that it would work for both
> string and integer values. Did the same for float for wind speed. Also
> there were a number of places where N/A was used when data did not exists
> and then those variables where used in a number format function which then
> errors out. I just check to see if the variable is_numeric before calling
> the number format function. I will send you my livedata.php and other files
> that I have changed when I am all done if you like.
>
> I still see few more things that do not look right that I still need to
> track down.
> Take care
> Jerry
>
>>
>>> --
> 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/271661a7-066c-40ae-a6c9-40c622b1faed%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CADASSaTBGo%2BwnnAkNCc0DhnLsNm1XAfq_QGOOe2CCQ2MGRB7dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Weather34 Template for WeeWX - New Major Update

[Jd D]

Hi Ian,

The calculation for Feels value is not displaying correctly for my 
location. It is like 30+ degrees too high. I know there are number of ways 
this can be done and there are numerous thoughts on what is best but for me 
I use the python program written by jfcarr  located here 
https://gist.github.com/jfcarr/e68593c92c878257550d It seems to match my 
local weather stations and takes into account wind speed. So I converted it 
from python to php and added it to livedata.php. Note it works on 
Fahrenheit temps so a conversion to C temps would be needed on the output 
and the input would need  a C to F conversion as well. Here is the code.
  
>
> if ($weather['temp'] <= 50 and $weather["wind_speed"] >= 3){
> $vFeelsLike = 35.74 + (0.6215*$weather['temp']) - 
> 35.75*($weather["wind_speed"]**0.16) + 
> ((0.4275*$weather['temp'])*($weather["wind_speed"]**0.16));}
> else{
> $vFeelsLike = $weather['temp'];}
> if ($vFeelsLike == $weather['temp'] and $weather['temp'] >= 80){
> $vFeelsLike = 0.5 * ($weather['temp'] + 61.0 + 
> (($weather['temp']-68.0)*1.2) + ($weather['humidity']*0.094));}
> if ($vFeelsLike >= 80){
> $vFeelsLike = -42.379 + 2.04901523*$weather['temp'] + 
> 10.14333127*$weather['humidity'] - 
> .22475541*$weather['temp']*$weather['humidity'] - 
> .00683783*$weather['temp']*$weather['temp'] - 
> .05481717*$weather['humidity']*$weather['humidity'] + 
> .00122874*$weather['temp']*$weather['temp']*$weather['humidity'] + 
> .00085282*$weather['temp']*$weather['humidity']*$weather['humidity'] - 
> .0199*$weather['temp']*$weather['temp']*$weather['humidity']*$weather['humidity'];}
> if ($weather['humidity'] < 13 and $weather['temp'] >= 80 and 
> $weather['temp'] <= 112){
> $vFeelsLike = $vFeelsLike - 
> ((13-$weather['humidity'])/4)*sqrt((17-abs($weather['temp']-95.))/17);}
> if ($weather['humidity'] > 85 and $weather['temp'] >= 80 
> and $weather['temp'] <= 87){
> $vFeelsLike = $vFeelsLike + 
> (($weather['humidity']-85)/10) * ((87-$weather['temp'])/5);}
> $weather['realfeel'] =  round($vFeelsLike,1);
>
> Thanks
Jerry 

-- 
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/fc2ccbe6-b3d9-4316-bec0-6fec0016025a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Weather34 Template for WeeWX - New Major Update

[steeple ian]

Hi Jerry,
That’s excellent information. I will be very interested to have a copy of the 
livedata and other file changes when you have completed them.
Thank you very much,
Ian 

Sent from my iPhone

> On 27 May 2019, at 17:53, Jd D  wrote:
> 
> Hi Ian,
> 
> Here are a couple more. The following code exists in multiple graphs and 
> causes the graphs to be messed up since the data is already Fahrenheit . Not 
> sure why this was needed at all. I commented it out to fixed the graphs
> .//  if ($tempunit == 'F') {
> //  $conv = '(9 / 5) + 32';
> //  } else {
> $conv = '1';
> //  }
> 
> Also in shared.php looks like a cut and paste error deleted most of the code 
> for function anyToF. The bold text below was what I added.
>  
> function anyToF($field){
> global $weather;
> if ($weather["temp_units"] == 'F'){
> return $field;
> } else {
> 
> return cToFDirect ($field);
> }
> }
> 
> In barometer.php there is a hard coded 100 in a for loop that blows up. I 
> changed it to be the sizeof the array.
> for ($i = 0; $i < sizeof($parsed_json); $i++) {
> $magnitude[$i]=$parsed_json{$i}{'magnitude'};$eqtitle[$i]=$parsed_json{$i}['title'];$depth[$i]=$parsed_json{$i}['depth'];$time[$i]=$parsed_json{$i}['date_time'];
> 
> In livedata.php I made a number of changes to handle when the data was not as 
> expected. Like if the time value was a string instead of a integer. I just 
> put a (int) in front of the variable so that it would work for both string 
> and integer values. Did the same for float for wind speed. Also there were a 
> number of places where N/A was used when data did not exists and then those 
> variables where used in a number format function which then errors out. I 
> just check to see if the variable is_numeric before calling the number format 
> function. I will send you my livedata.php and other files that I have changed 
> when I am all done if you like.
> 
> I still see few more things that do not look right that I still need to track 
> down.
> Take care
> Jerry
>>> 
> 
> -- 
> 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/271661a7-066c-40ae-a6c9-40c622b1faed%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/38968EB8-CCDB-4E94-83F0-0D4FB7050282%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Weather34 Template for WeeWX - New Major Update

[Jd D]

Hi Ian,

Here are a couple more. The following code exists in multiple graphs and 
causes the graphs to be messed up since the data is already Fahrenheit . 
Not sure why this was needed at all. I commented it out to fixed the graphs
.//  if ($tempunit == 'F') {
//  $conv = '(9 / 5) + 32';
//  } else {
$conv = '1';
//  }

Also in shared.php looks like a cut and paste error deleted most of the 
code for function anyToF. The bold text below was what I added.
 
function anyToF($field){
*global $weather;*
*if ($weather["temp_units"] == 'F'){*
*return $field;*
*} else {*

return cToFDirect ($field);
}
*}*

In barometer.php there is a hard coded 100 in a for loop that blows up. I 
changed it to be the sizeof the array.
for ($i = 0; $i <* sizeof($parsed_json)*; $i++) {
$magnitude[$i]=$parsed_json{$i}{'magnitude'};$eqtitle[$i]=$parsed_json{$i}['title'];$depth[$i]=$parsed_json{$i}['depth'];$time[$i]=$parsed_json{$i}['date_time'];

In livedata.php I made a number of changes to handle when the data was not 
as expected. Like if the time value was a string instead of a integer. I 
just put a (int) in front of the variable so that it would work for both 
string and integer values. Did the same for float for wind speed. Also 
there were a number of places where N/A was used when data did not exists 
and then those variables where used in a number format function which then 
errors out. I just check to see if the variable is_numeric before calling 
the number format function. I will send you my livedata.php and other files 
that I have changed when I am all done if you like.

I still see few more things that do not look right that I still need to 
track down.
Take care
Jerry

>
>>

-- 
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/271661a7-066c-40ae-a6c9-40c622b1faed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: On this date

[p q]

Pretty simple. I've been meaning to do that for myself by hadn't gotten
around to it yet.

You need a if statement just inside the loop like
#if $day.dateTime.format("%Y")<>$year.dateTime.format("%Y")

This compares the year returned by the loop to the current year, formatted
the same. If they are different output as normal.
You need to close the if with an #end if just before the #end for

Here's my code:
#for $day in $this_span.periods
   #if
$day.dateTime.format("%Y")<>$year.dateTime.format("%Y")
  $day.dateTime.format("%Y")
   H: $day.outTemp.max :
$day.outTemp.min
  #if $day.rain.sum.raw >0.0
  Rain: $day.rain.sum
  #end if
   #end if
#end for

I have an extra #if to not print out rain if it's zero. If you get rain
throughout the year, you might want to remove the second #if line and first
#end if.

Good luck.

On Mon, May 27, 2019 at 3:33 AM Robin  wrote:

>
>>
> Gary,
>
> Thank you for the search list extension. It is very useful.
>
> I'm sorry to be a pest, I have one more question. I have been trying to
> see if I can exclude the current year so that I get only historic records.
> I have looked at the code to try and understand how it all works, but that
> simply reminds me that I don't understand code.
>
> Is there a way to exclude the current year?
>
> Thank you again.
>
> Robin
>
> --
> 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/ae22c835-f43a-48d5-80c7-c8690f1eadd3%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Peter Quinn
(415)794-2264

-- 
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/CAA1SM20pAGjZCYbhe4dhxQcu2eRQdUFC1VfrwjGwc-itEi4FFQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: We have finally put the last nail on the coffin for Wunderfixer?

[Leon Shaner]

> On May 27, 2019, at 12:12 AM, gjr80  wrote:
> 
>> On Monday, 27 May 2019 13:16:53 UTC+10, Leon Shaner wrote:
>> [snip]
>> If you can see any shorter paths to a more reliable outcome than I have 
>> achieved so far, then you know know know I will be very grateful.  =D
> 
> I am not sure what local/UTC issue you refer to. When I do a 
> api.weather.com/v2/pws/history query on a station to the east of Greenwich I 
> am returned all records for the date specified (eg 20190525 gives me all 
> records for 25 May 2019), each record contains an epoch timestamp which is 
> correct and consistent with 25 May 2019. Everything is as I would expect. 
> However, when I perform the same query on a station to the west of Greenwich 
> I am returned records for the day before the date specified (ie 20190525 
> gives me all records for 24 May 2019 not 25 May 2019), again each record 
> contains an epoch timestamp but the timestamp is for the previous day Ie 24 
> May 2019. I have checked a number of data records in the stations history 
> table and WU is definitely returning the midnight to midnight data for the 
> day before. I have confirmed this behaviour with a number of stations both 
> east and west of Greenwich.
> 
> I don't think there is a local/UTC time issue, I think WU is having some 
> implementation issues and for stations west of Greenwich they are returning 
> the wrong day of data.

Thanks, Gary!  This was all very helpful.
In addition to what you've described across the east vs west of GMT, I get 
similar behavior if I am within X hours of my local UTC offset when querying my 
own station.
Last night as soon as localtime rolled over midnight, the queries for the 
previous day were correct.

--Leon

> 
> Gary

-- 
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/7BBF146A-7408-44AD-8676-FDE99ED6532C%40isylum.org.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: On this date

[Robin]

>
>
>
Gary,

Thank you for the search list extension. It is very useful. 

I'm sorry to be a pest, I have one more question. I have been trying to see 
if I can exclude the current year so that I get only historic records. I 
have looked at the code to try and understand how it all works, but that 
simply reminds me that I don't understand code.

Is there a way to exclude the current year?

Thank you again.

Robin 

-- 
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/ae22c835-f43a-48d5-80c7-c8690f1eadd3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: BloomSky SKY2+STORM - No Pressure?

[Rick M0LEP]

I think I found what was missing. The release of the BloomSky driver I 
was using came from:

https://github.com/gjr80/weewx-bloomsky/releases/download/v0.1.0/bloomsky-0.1.0.tar.gz

However, the git repository contains a more up-to-date driver that 
doesn't seem to have made it into the release yet. Getting the latest 
copy of bloomsky.py from https://github.com/gjr80/weewx-bloomsky and 
installing it manually has cured the problem.

On Mon 27 May Rick M0LEP wrote:
> I've recently switched my system over to getting data from a BloomSky 
> SKY2, and all seems to work fine except the pressure, which shows as N/A 
> (or null) in all the readings I can see in weewx. Looking atthe raw data 
> from the BloomSky, the pressure is being reported, so I'm guessing 
> someting in the driver is somehow missing it. Any ideas?

-- 
73, Rick, M0LEP

-- 
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/7adf.5cebb950.cdb4f.m0lep%40hewett.org.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] BloomSky SKY2+STORM - No Pressure?

[Rick M0LEP]

I've recently switched my system over to getting data from a BloomSky 
SKY2, and all seems to work fine except the pressure, which shows as N/A 
(or null) in all the readings I can see in weewx. Looking atthe raw data 
from the BloomSky, the pressure is being reported, so I'm guessing 
someting in the driver is somehow missing it. Any ideas?

-- 
73, Rick, M0LEP

-- 
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/799f.5cebb6a2.44d0.m0lep%40hewett.org.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Weather34 Template for WeeWX - New Major Update

[steeple ian]

Yes it looks like that. I have fixed that as well.

I would be interested to see what you have done with livedata.php as I am
continuing to evolve this for the WeeWX version.

Thanks,
Ian

On Mon, May 27, 2019 at 5:21 AM Jd D  wrote:

> Hi Ian,
> Also notice some left-over debug code in shared.php that prevents
> Fahrenheit temps from displaying correctly.
>
> *$weather["temp_units"]='C'; *
> if ($weather["temp_units"] == 'C'){
> $heatIndex = fToCDirect($heatIndex);
>
> Thanks Jerry
>
> On Sunday, May 26, 2019 at 7:28:06 PM UTC-7, Jd D wrote:
>>
>> Hi Ian,
>>
>> Noticed this in weewxcron.php
>>
>> if ($position6=="forecast3ds.php" || $position6=='forecast3wu.php' ||
>> $position6=='forecast3wularge.php' || *$position4   = "advisory.php")*{
>>
>> I think you want ==
>>
>> Also I cleaned up most of my apache errors by making small changes to
>> livedata.php
>>
>> Thanks Jerry
>>
>> On Sunday, May 26, 2019 at 11:47:25 AM UTC-7, Jd D wrote:
>>>
>>> Hi Ian,
>>> Right now just using the template for my local weather station and my
>>> nearby metar.
>>> Here is my settings1.php.
>>> I XXed out personal stuff.
>>> Also I tried to use the least number of sections so to reduce the number
>>> of apache errors I am logging.
>>> Since I cut and pasted the file into the replay so you can see where the
>>> cut and pastes happen. :-)
>>> I can send my w34stats.php file if that would help.
>>> I can work these issues if you rather and just send you what I find if
>>> that is a better. I have the time and experience with php/javascript and
>>> python.
>>> Thanks Jerry
>>>
>>>  $apikey = "";
>>>  $wuapikey = "";
>>>  $weatherflowID = "";
>>>  $weatherflowoption   = "no";
>>>  $weatherflowlightning = "";
>>>  $weatherflowmapzoom   = "";
>>>  $id = "";
>>>  $purpleairID = "";
>>>  $purpleairhardware   = "no";
>>>  $metarapikey ="";
>>>  $TZ = "X";
>>>  $UTC = "XX";
>>>  $lon = X;
>>>  $lat = ;
>>>  $darkskyunit   = "us";
>>>  $wuapiunit   = "h";
>>>  $stationlocation = "XXX";
>>>  $stationName = "X";
>>>  $moonadj = "";
>>>  $minmag = "3";
>>>  $unit = "english";
>>>  $metric = false;
>>>  $elevation = "1792";
>>>  $uk = false;
>>>  $usa = true;
>>>  $scandinavia = false;
>>>  $restoftheworld = false;
>>>  $windunit = "mph";
>>>  $distanceunit = "mi";
>>>  $tempunit = "F";
>>>  $rainunit  = "in";
>>>  $rainrate = "/h";
>>>  $pressureunit  = "inHg";
>>>  $livedataFormat = "WeeWX-CRT";
>>>  $livedata   = "demodata/realtime.txt";
>>>  $currentconditions   = "currentconditionsds.php";
>>>  $chartsource   = "mbcharts";
>>>  $extralinks   = "yes";
>>>  $languages   = "no";
>>>  $dateFormat   = "m-d-Y";
>>>  $timeFormat= "g:i:s a";
>>>  $timeFormatShort= "g:i";
>>>  $clockformat= "12";
>>>  $showDate = false;
>>>  $temperaturemodule   = "temperaturein.php";
>>>  $position1   = "temperatureyear.php";
>>>  $position2   = "temperatureyear.php";
>>>  $position3   = "temperatureyear.php";
>>>  $position4   = "temperatureyear.php";
>>>  $position1title   = "1";
>>>  $position2title   = "2";
>>>  $position3title   = "3";
>>>  $position4title   = "4"
>>>  $position6title   = "6";
>>> $position6   = "";
>>>
 $position12title   = "12";
 $position12   = "indoortemperature.php";
 $positionlastmoduletitle   = "l";
 $positionlastmodule   = "indoortemperature.php";
 $webcamurl   = "";
 $email= "";
 $twitter   = "";
 $theme1   = "dark";
 $since= "2016";
 $weatherhardware   = "La Crosse";
 $mbplatform   = "WeeWX";
 $davis   = "No";
 $db_host   = "localhost";
 $db_user= "root";
 $db_pass  = "";
 $db_name   = "weatherstation";
 $notifications = "yes";
 $sunoption = "";
 $hemisphere   = "";
 $metar   = "yes";
 $icao1   = "";
 $airport1   = "";
 $airport1dist   = "10";
 $defaultlanguage   = "en";
 $language= "en";
 $password= "";
 $flag   = "us";
 $dshourly   = "no";
 $manifestShortName = "";

 --
> 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/4ebf7f6b-a6d7-4e89-89b2-d50d1b44d3cf%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CADASSaQH7zoMgMAtza7-T%3D_TUMWfetx4L71kckQ1jjVAoryULw%40mail.gmail.com.
For more options, visit 

Re: [weewx-user] Re: Weather34 Template for WeeWX - New Major Update

[steeple ian]

Thanks Jerry,

Not sure how that one slipped through as it is correct in my working live
copy. Now corrected in the repository.

Ian

On Mon, May 27, 2019 at 3:28 AM Jd D  wrote:

> Hi Ian,
>
> Noticed this in weewxcron.php
>
> if ($position6=="forecast3ds.php" || $position6=='forecast3wu.php' ||
> $position6=='forecast3wularge.php' || *$position4   = "advisory.php")*{
>
> I think you want ==
>
> Also I cleaned up most of my apache errors by making small changes to
> livedata.php
>
> Thanks Jerry
>
> On Sunday, May 26, 2019 at 11:47:25 AM UTC-7, Jd D wrote:
>>
>> Hi Ian,
>> Right now just using the template for my local weather station and my
>> nearby metar.
>> Here is my settings1.php.
>> I XXed out personal stuff.
>> Also I tried to use the least number of sections so to reduce the number
>> of apache errors I am logging.
>> Since I cut and pasted the file into the replay so you can see where the
>> cut and pastes happen. :-)
>> I can send my w34stats.php file if that would help.
>> I can work these issues if you rather and just send you what I find if
>> that is a better. I have the time and experience with php/javascript and
>> python.
>> Thanks Jerry
>>
>>  $apikey = "";
>>  $wuapikey = "";
>>  $weatherflowID = "";
>>  $weatherflowoption   = "no";
>>  $weatherflowlightning = "";
>>  $weatherflowmapzoom   = "";
>>  $id = "";
>>  $purpleairID = "";
>>  $purpleairhardware   = "no";
>>  $metarapikey ="";
>>  $TZ = "X";
>>  $UTC = "XX";
>>  $lon = X;
>>  $lat = ;
>>  $darkskyunit   = "us";
>>  $wuapiunit   = "h";
>>  $stationlocation = "XXX";
>>  $stationName = "X";
>>  $moonadj = "";
>>  $minmag = "3";
>>  $unit = "english";
>>  $metric = false;
>>  $elevation = "1792";
>>  $uk = false;
>>  $usa = true;
>>  $scandinavia = false;
>>  $restoftheworld = false;
>>  $windunit = "mph";
>>  $distanceunit = "mi";
>>  $tempunit = "F";
>>  $rainunit  = "in";
>>  $rainrate = "/h";
>>  $pressureunit  = "inHg";
>>  $livedataFormat = "WeeWX-CRT";
>>  $livedata   = "demodata/realtime.txt";
>>  $currentconditions   = "currentconditionsds.php";
>>  $chartsource   = "mbcharts";
>>  $extralinks   = "yes";
>>  $languages   = "no";
>>  $dateFormat   = "m-d-Y";
>>  $timeFormat= "g:i:s a";
>>  $timeFormatShort= "g:i";
>>  $clockformat= "12";
>>  $showDate = false;
>>  $temperaturemodule   = "temperaturein.php";
>>  $position1   = "temperatureyear.php";
>>  $position2   = "temperatureyear.php";
>>  $position3   = "temperatureyear.php";
>>  $position4   = "temperatureyear.php";
>>  $position1title   = "1";
>>  $position2title   = "2";
>>  $position3title   = "3";
>>  $position4title   = "4"
>>  $position6title   = "6";
>> $position6   = "";
>>
>>> $position12title   = "12";
>>> $position12   = "indoortemperature.php";
>>> $positionlastmoduletitle   = "l";
>>> $positionlastmodule   = "indoortemperature.php";
>>> $webcamurl   = "";
>>> $email= "";
>>> $twitter   = "";
>>> $theme1   = "dark";
>>> $since= "2016";
>>> $weatherhardware   = "La Crosse";
>>> $mbplatform   = "WeeWX";
>>> $davis   = "No";
>>> $db_host   = "localhost";
>>> $db_user= "root";
>>> $db_pass  = "";
>>> $db_name   = "weatherstation";
>>> $notifications = "yes";
>>> $sunoption = "";
>>> $hemisphere   = "";
>>> $metar   = "yes";
>>> $icao1   = "";
>>> $airport1   = "";
>>> $airport1dist   = "10";
>>> $defaultlanguage   = "en";
>>> $language= "en";
>>> $password= "";
>>> $flag   = "us";
>>> $dshourly   = "no";
>>> $manifestShortName = "";
>>>
>>> --
> 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/e0799a00-01e7-4f85-9364-a61a8ebb5cc3%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CADASSaRhqfiB0L6Dtr2NiH3wS4zhPRGAFNVKFCjqnqS3cSH%2BsA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: csv.py don't add radiation and UV

[JanC]

Gary, thanks for your reply,i will add it right now.

Op maandag 27 mei 2019 04:41:44 UTC+2 schreef gjr80:
>
> Hi,
>
> Your 'fix' has merely forced the csv service to always generate data.csv 
> based on archive records rather than the default loop packets. Using 
> archive records rather than loop packets would make sense for a station 
> that emits partial loop packets (ie a station that does not include 
> radiation and UV in every loop packet) but based on the log extract you 
> provided your station does not appear to be a partial packet type. In any 
> case, if generating data.csv based on archive records rather than loop 
> packets solves your problem a far better approach would be to return 
> csv.py to its original state and change your [CSV] stanza in weewx.conf 
> to read:
>
> [CSV]
> filename = /var/tmp/tmp/data.csv
> binding = archive
>
> This will require a WeeWX restart. This achieves the same effect as your 
> changes whilst ensuring your system will continue to work across future 
> upgrades.
>
> Gary
>
>
> On Sunday, 26 May 2019 16:48:16 UTC+10, JanC wrote:
>>
>> I found the solution myself.
>>
>> In csv.py :
>>
>> if self.binding == 'binding':
>>
>>
>> self.binding = d.get('binding', 'loop')
>>  ##   if self.binding == 'loop':
>> if self.binding == 'binding':
>> self.bind(weewx.NEW_LOOP_PACKET, self.handle_new_loop)
>> else:
>> self.bind(weewx.NEW_ARCHIVE_RECORD, self.handle_new_archive)
>>
>> janc
>>
>> Op zaterdag 25 mei 2019 11:39:11 UTC+2 schreef JanC:
>>>
>>> I use a WH2600 weatherstation with a raspberry pi
>>>
>>> debian8
>>> weewx 3.9.1
>>> driver interceptor observer
>>> csv.py to collect the data to a csv-file
>>>
>>> with weewx 3.8 it works ok, after upgrade to 3.9 it fails
>>>
>>> I have some things overlooked?
>>>
>>> JanC
>>>
>>

-- 
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/e4b4375e-b47d-4433-8459-392cfa9aa00f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.