[weewx-user] Re: Wind data wrong

[Nicolas Cazan]

After some trouble, it's good, the data erroned is deleted, what is this 
burst at 737 km / h raspberry bug, or Weewx or interference?

In any case, thank you

Le samedi 27 janvier 2018 23:19:37 UTC+1, Nicolas Cazan a écrit :
>
> Hello, I have a problem, I use Weewx 3.7.1 and it has just recorded a 
> burst at 737 km / h (tornado !!) How can I delete this data wrong?
> Thank you in advance for your help.
>

-- 
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: Wind data wrong

[Nicolas Cazan]

sorry it's in french


Le samedi 27 janvier 2018 23:58:16 UTC+1, gjr80 a écrit :
>
> Can you please post a screen capture of exactly what you are typing and 
> what is returned/what error you see. Descriptions are good but screen 
> captures are better.
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Wind data wrong

[Nicolas Cazan]

yes but I get  Error: near line 1: no such table: archive


Le samedi 27 janvier 2018 23:33:32 UTC+1, gjr80 a écrit :
>
> Hi,
>
> Have a look at the wiki (
> https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data). You 
> might also want to look at implementing some appropriate MinMax limits in 
> [StdQC] in weewx.conf (
> http://weewx.com/docs/usersguide.htm#%5B%5BMinMax%5D%5D)
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Wind data wrong

[Nicolas Cazan]

Hello, I have a problem, I use Weewx 3.7.1 and it has just recorded a burst 
at 737 km / h (tornado !!) How can I delete this data wrong?
Thank you in advance for your help.

-- 
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] Wind Gust N/A

[Nicolas Cazan]

hello, I had a problem with a wmr200, for wind direction weewx regularly 
show N / A for a weak wind, and did not take ignore_zero_wind = false

in uploading wmr200.py download on github, the problem is solved, I no 
longer get N / A but well l direction of the wind.

On the other hand, a question, when we have a recording every 5 minutes and 
we use $ current.windGust.formatted this returns the maximum wind gust of 
the last 5 minutes, can be done like rain or temperature and set to the 
last 15 minutes without changing the five minute recording step eg $ 
time_delta = 900
thank you in advance

-- 
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] Wind Gust N/A

[Nicolas Cazan]

I have downloaded weewx via github and uploader with filezila wmr200.py in 
the drivers folder, I have relaunched weewx for now more problem for me.

-- 
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] Wind Gust N/A

[Nicolas Cazan]

I realize that the wind graph is incomplete
very low or no wind.

for the windgustdir which displays N/A this occurs regularly as the wind is 
less than 10 km /h.

As wind gusts exceed 10 km / h no problem for the directions.

[StdWXCalculate]
  ignore_zero_wind = false
 [[Calculations]]

this does not change anything in wind nil, N/A at all wind values.

-- 
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: Can we change the method of calculating the rain rate ?

[Nicolas Cazan]

I put software for rain rate, it has just been a last rain depositing 1mm 
of precipitation and I have a rate rate of 4.1 mm / h you think what?

-- 
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] Can we change the method of calculating the rain rate ?

[Nicolas Cazan]

Hello, I have a wmr200, and I had noticed for years a strange thing.
The rainrate works well, but it takes a long time to return to 0 when it 
does not rain anymore.
Example: it just rained, only it does not rain for more than an hour and I 
keep a 2.8mm / h groove, so the data in weewx are identical.
If I recover the rainfall values over 15 minutes I get 0,0 well since 1:15 
otherwise it does not rain anymore, but can we force weewx to calculate 
itself the rainrate?

-- 
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: Skin pws added rain over 15 minutes

[Nicolas Cazan]

Good it works, it's great

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

[weewx-user] Re: Skin pws added rain over 15 minutes

[Nicolas Cazan]

Hello,
the line to recover the rain value of the last fifteen minutes did not work.

I have not been able to test it since it does not rain often in the 
south-east of France.

I think I made a mistake here is the change


$span($time_delta=900).rain.sum.formatted


This line for the moment brings the value 0 in weewx_pws.xml
but thunderstorms are expected this afternoon, I hope to get in this line 
the rainfall value of the last fifteen minutes, do you think it is correct?


For min and max values, I will use the min and max function of sql and php.


thank you in advance
have a good day
ManuLe lundi 7 août 2017 09:59:18 UTC+2, Nicolas Cazan a écrit :
>
> I put this
>
> > realtime="rainheure">$span($time_delta=900).rain.min.formatted
>>
>
> This seems to work, the file has been generated, actually there was a 
> problem in yesterday's syntax.
>
> Le lundi 7 août 2017 09:41:28 UTC+2, Nicolas Cazan a écrit :
>>
>> Weewx_pws.xml seems to contain the desired info.
>> As for the rain, I checked to obte, ir rain of the last 15 minutes 
>> (archiving via php and cron every 15 minutes) tomorrow thunderstorms are 
>> expected to see what this is going, actually $ span seemed to be problem, I 
>> will try still.
>>
>> 
>>>
>>
>> return :
>>
>> 0,0
>>
>>
>>  
>> Le lundi 7 août 2017 02:40:15 UTC+2, gjr80 a écrit :
>>>
>>> Hi,
>>>
>>> Well the date time now makes sense but there is still a fundamental 
>>> problem here. If you have this:
>>>
>>> $span($time_delta=900).rain.sum.
>>> formatted
>>>
>>> in your .tmpl file then the generated file will have 
>>>
>>> 
>>>
>>> in there somewhere, irrespective of whether the $span tag is right, 
>>> wrong or indifferent. I do not see this text anywhere in your generated 
>>> file.
>>>
>>>
>>> For all those who have the same problem:
>>>>
>>>> >>>> realtime="tempanneemax">$month.outTemp.max.formatted
>>>>> >>>> realtime="tempanneemax">$year.outTemp.max.formatted
>>>>> >>>> realtime="tempanneemini">$month.outTemp.min.formatted
>>>>> >>>> realtime="tempanneemini">$year.outTemp.min.formatted
>>>>>
>>>>
>>>> >>>> realtime="rainheure">$hour.rain.min.formatted
>>>>
>>>>
>>>> On the rain I do not know if it is correct, it does not rain often in 
>>>> Provence
>>>>
>>>
>>> Have you made more changes to weewx_pws.xml.tmpl? Did these changes 
>>> come through in your generated weewx_pws.xml? What about the $span line?
>>>
>>> The tag $hour.rain.min.formatted will display the minimum archive 
>>> period rainfall from all of the archive periods in the current hour. So if 
>>> there was rainfall in each archive period in the current hour you will get 
>>> the minimum of these values, if there was an archive period in the current 
>>> hour during which it did not rain you will get 0. Is this really what you 
>>> are trying to display,  seems to imply you 
>>> want the rainfall in the last immediate 1 hour period? 
>>> $span($time_delta=3600).rain.sum.formatted will display the rainfall in the 
>>> last immediate 1 hour period. ($hour works on x:00 hour boundaries).
>>>
>>> On the other hand it returns only the minimum and maximum temperature of 
>>>> the current month.
>>>>
>>>> I extract this data via a php page, are you able to specify the desired 
>>>> month?
>>>>
>>>
>>> I assume you are referring to $month.outTemp.max.formatted ? If so, as 
>>> you rightly say this will provide the max outTemp seen in the current 
>>> calendar month, so at 06:00 on 1 August it will return the max outTemp 
>>> seen in the last 6 hours, $month works on the the period since midnight 
>>> on the 1st of the current month. If you want the max outTemp from some 
>>> other month in the past, say March, then this is not easily done with the 
>>> current 
>>> weeWX tags, it can be done but it will require some python coding either in 
>>> a template or as a search list extension.
>>>
>>> It might help if you could describe exactly what you want in each of 
>>> your fields.
>>>
>>> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Skin pws added rain over 15 minutes

[Nicolas Cazan]

I put this

 realtime="rainheure">$span($time_delta=900).rain.min.formatted
>

This seems to work, the file has been generated, actually there was a 
problem in yesterday's syntax.

Le lundi 7 août 2017 09:41:28 UTC+2, Nicolas Cazan a écrit :
>
> Weewx_pws.xml seems to contain the desired info.
> As for the rain, I checked to obte, ir rain of the last 15 minutes 
> (archiving via php and cron every 15 minutes) tomorrow thunderstorms are 
> expected to see what this is going, actually $ span seemed to be problem, I 
> will try still.
>
> 
>>
>
> return :
>
> 0,0
>
>
>  
> Le lundi 7 août 2017 02:40:15 UTC+2, gjr80 a écrit :
>>
>> Hi,
>>
>> Well the date time now makes sense but there is still a fundamental 
>> problem here. If you have this:
>>
>> $span($time_delta=900).rain.sum.
>> formatted
>>
>> in your .tmpl file then the generated file will have 
>>
>> 
>>
>> in there somewhere, irrespective of whether the $span tag is right, 
>> wrong or indifferent. I do not see this text anywhere in your generated 
>> file.
>>
>>
>> For all those who have the same problem:
>>>
>>> >>> realtime="tempanneemax">$month.outTemp.max.formatted
>>>> >>> realtime="tempanneemax">$year.outTemp.max.formatted
>>>> >>> realtime="tempanneemini">$month.outTemp.min.formatted
>>>> >>> realtime="tempanneemini">$year.outTemp.min.formatted
>>>>
>>>
>>> >>> realtime="rainheure">$hour.rain.min.formatted
>>>
>>>
>>> On the rain I do not know if it is correct, it does not rain often in 
>>> Provence
>>>
>>
>> Have you made more changes to weewx_pws.xml.tmpl? Did these changes come 
>> through in your generated weewx_pws.xml? What about the $span line?
>>
>> The tag $hour.rain.min.formatted will display the minimum archive period 
>> rainfall from all of the archive periods in the current hour. So if there 
>> was rainfall in each archive period in the current hour you will get the 
>> minimum of these values, if there was an archive period in the current hour 
>> during which it did not rain you will get 0. Is this really what you are 
>> trying to display,  seems to imply you want 
>> the rainfall in the last immediate 1 hour period? 
>> $span($time_delta=3600).rain.sum.formatted will display the rainfall in the 
>> last immediate 1 hour period. ($hour works on x:00 hour boundaries).
>>
>> On the other hand it returns only the minimum and maximum temperature of 
>>> the current month.
>>>
>>> I extract this data via a php page, are you able to specify the desired 
>>> month?
>>>
>>
>> I assume you are referring to $month.outTemp.max.formatted ? If so, as 
>> you rightly say this will provide the max outTemp seen in the current 
>> calendar month, so at 06:00 on 1 August it will return the max outTemp 
>> seen in the last 6 hours, $month works on the the period since midnight 
>> on the 1st of the current month. If you want the max outTemp from some 
>> other month in the past, say March, then this is not easily done with the 
>> current 
>> weeWX tags, it can be done but it will require some python coding either in 
>> a template or as a search list extension.
>>
>> It might help if you could describe exactly what you want in each of your 
>> fields.
>>
>> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Skin pws added rain over 15 minutes

[Nicolas Cazan]

Weewx_pws.xml seems to contain the desired info.
As for the rain, I checked to obte, ir rain of the last 15 minutes 
(archiving via php and cron every 15 minutes) tomorrow thunderstorms are 
expected to see what this is going, actually $ span seemed to be problem, I 
will try still.


>

return :

0,0


 
Le lundi 7 août 2017 02:40:15 UTC+2, gjr80 a écrit :
>
> Hi,
>
> Well the date time now makes sense but there is still a fundamental 
> problem here. If you have this:
>
> $span($time_delta=900).rain.sum.
> formatted
>
> in your .tmpl file then the generated file will have 
>
> 
>
> in there somewhere, irrespective of whether the $span tag is right, wrong 
> or indifferent. I do not see this text anywhere in your generated file.
>
>
> For all those who have the same problem:
>>
>> >> realtime="tempanneemax">$month.outTemp.max.formatted
>>> >> realtime="tempanneemax">$year.outTemp.max.formatted
>>> >> realtime="tempanneemini">$month.outTemp.min.formatted
>>> >> realtime="tempanneemini">$year.outTemp.min.formatted
>>>
>>
>> >> realtime="rainheure">$hour.rain.min.formatted
>>
>>
>> On the rain I do not know if it is correct, it does not rain often in 
>> Provence
>>
>
> Have you made more changes to weewx_pws.xml.tmpl? Did these changes come 
> through in your generated weewx_pws.xml? What about the $span line?
>
> The tag $hour.rain.min.formatted will display the minimum archive period 
> rainfall from all of the archive periods in the current hour. So if there 
> was rainfall in each archive period in the current hour you will get the 
> minimum of these values, if there was an archive period in the current hour 
> during which it did not rain you will get 0. Is this really what you are 
> trying to display,  seems to imply you want 
> the rainfall in the last immediate 1 hour period? 
> $span($time_delta=3600).rain.sum.formatted will display the rainfall in the 
> last immediate 1 hour period. ($hour works on x:00 hour boundaries).
>
> On the other hand it returns only the minimum and maximum temperature of 
>> the current month.
>>
>> I extract this data via a php page, are you able to specify the desired 
>> month?
>>
>
> I assume you are referring to $month.outTemp.max.formatted ? If so, as 
> you rightly say this will provide the max outTemp seen in the current 
> calendar month, so at 06:00 on 1 August it will return the max outTemp 
> seen in the last 6 hours, $month works on the the period since midnight 
> on the 1st of the current month. If you want the max outTemp from some 
> other month in the past, say March, then this is not easily done with the 
> current 
> weeWX tags, it can be done but it will require some python coding either in 
> a template or as a search list extension.
>
> It might help if you could describe exactly what you want in each of your 
> fields.
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Skin pws added rain over 15 minutes

[Nicolas Cazan]

On the other hand it returns only the minimum and maximum temperature of 
the current month.

I extract this data via a php page, are you able to specify the desired 
month?

Le dimanche 6 août 2017 17:56:22 UTC+2, Nicolas Cazan a écrit :
>
> For all those who have the same problem:
>
> > realtime="tempanneemax">$month.outTemp.max.formatted
>> > realtime="tempanneemax">$year.outTemp.max.formatted
>> > realtime="tempanneemini">$month.outTemp.min.formatted
>> > realtime="tempanneemini">$year.outTemp.min.formatted
>>
>
> > realtime="rainheure">$hour.rain.min.formatted
>
>
> On the rain I do not know if it is correct, it does not rain often in 
> Provence 
>
> Le dimanche 6 août 2017 15:20:30 UTC+2, Nicolas Cazan a écrit :
>>
>> oups ...
>>
>> Le dimanche 6 août 2017 15:01:02 UTC+2, gjr80 a écrit :
>>>
>>> Are you sure that this file has just been generated? The date time at 
>>> line 7 does not seem correct, as I write this it is 5 minutes before the 
>>> hour, but the date time in the file is 5 minutes after the hour?
>>>
>>> 14:05 CEST
>>>
>>> I am also suspicious given that that none of the xml tags from the line 
>>> you are trying to add are appearing in the file you posted. Are you sure 
>>> you are editing the correct weewx_pws.xml.tmpl and/or are you sure you 
>>> are posting the most recently generated weewx_pws.xml ?
>>>
>>> Gary
>>>
>>> On Sunday, 6 August 2017 22:50:34 UTC+10, Nicolas Cazan wrote:
>>>>
>>>>
>>>>
>>>> Le dimanche 6 août 2017 14:36:15 UTC+2, gjr80 a écrit :
>>>>>
>>>>> Ok, so what does the generated weewx_pws.xml look like now?
>>>>>
>>>>> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Skin pws added rain over 15 minutes

[Nicolas Cazan]

For all those who have the same problem:

 realtime="tempanneemax">$month.outTemp.max.formatted
>  realtime="tempanneemax">$year.outTemp.max.formatted
>  realtime="tempanneemini">$month.outTemp.min.formatted
>  realtime="tempanneemini">$year.outTemp.min.formatted
>

 realtime="rainheure">$hour.rain.min.formatted


On the rain I do not know if it is correct, it does not rain often in 
Provence 

Le dimanche 6 août 2017 15:20:30 UTC+2, Nicolas Cazan a écrit :
>
> oups ...
>
> Le dimanche 6 août 2017 15:01:02 UTC+2, gjr80 a écrit :
>>
>> Are you sure that this file has just been generated? The date time at 
>> line 7 does not seem correct, as I write this it is 5 minutes before the 
>> hour, but the date time in the file is 5 minutes after the hour?
>>
>> 14:05 CEST
>>
>> I am also suspicious given that that none of the xml tags from the line 
>> you are trying to add are appearing in the file you posted. Are you sure 
>> you are editing the correct weewx_pws.xml.tmpl and/or are you sure you 
>> are posting the most recently generated weewx_pws.xml ?
>>
>> Gary
>>
>> On Sunday, 6 August 2017 22:50:34 UTC+10, Nicolas Cazan wrote:
>>>
>>>
>>>
>>> Le dimanche 6 août 2017 14:36:15 UTC+2, gjr80 a écrit :
>>>>
>>>> Ok, so what does the generated weewx_pws.xml look like now?
>>>>
>>>> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Skin pws added rain over 15 minutes

[Nicolas Cazan]

oups ...

Le dimanche 6 août 2017 15:01:02 UTC+2, gjr80 a écrit :
>
> Are you sure that this file has just been generated? The date time at line 
> 7 does not seem correct, as I write this it is 5 minutes before the hour, 
> but the date time in the file is 5 minutes after the hour?
>
> 14:05 CEST
>
> I am also suspicious given that that none of the xml tags from the line 
> you are trying to add are appearing in the file you posted. Are you sure 
> you are editing the correct weewx_pws.xml.tmpl and/or are you sure you 
> are posting the most recently generated weewx_pws.xml ?
>
> Gary
>
> On Sunday, 6 August 2017 22:50:34 UTC+10, Nicolas Cazan wrote:
>>
>>
>>
>> Le dimanche 6 août 2017 14:36:15 UTC+2, gjr80 a écrit :
>>>
>>> Ok, so what does the generated weewx_pws.xml look like now?
>>>
>>> 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.
For more options, visit https://groups.google.com/d/optout.


weewx_pws.xml
Description: XML document

[weewx-user] Re: Skin pws added rain over 15 minutes

[Nicolas Cazan]

Le dimanche 6 août 2017 14:36:15 UTC+2, gjr80 a écrit :
>
> Ok, so what does the generated weewx_pws.xml look like now?
>
> 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.
For more options, visit https://groups.google.com/d/optout.


weewx_pws.xml
Description: XML document

[weewx-user] Re: Skin pws added rain over 15 minutes

[Nicolas Cazan]

ok.

No, it does not work, the file is generated, but the value does not appear.

Le dimanche 6 août 2017 14:27:45 UTC+2, gjr80 a écrit :
>
> No need to restart if changing a .tmpl or skin.conf. Just make the change, 
> save the file and it will be use on the next report cycle. 
>
> Simple rule of thumb. Change a .py file and you must stop then start 
> weeWX, change weewx.conf you need to stop then start weeWX or do a config 
> reload, change a .tmpl or skin.conf and you don't need to do anything other 
> than save the changes.
>
> 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.
For more options, visit https://groups.google.com/d/optout.


weewx_pws.xml.tmpl
Description: Binary data

[weewx-user] Re: Skin pws added rain over 15 minutes

[Nicolas Cazan]

Should i restart weewx with each modification?

Le dimanche 6 août 2017 14:13:06 UTC+2, gjr80 a écrit :
>
> You have a typo in weewx_pws.xml.tmpl. You have:
>
> $day.barometer.min.formatted
> 
> 
> $time_delta=900).rain.sum.formatted
> 
> $day.rain.sum.formatted
> 
>
> it should read:
>
> $day.barometer.min.formatted
> 
> 
> $span(
> $time_delta=900).rain.sum.formatted
> $day.rain.sum.formatted
> 
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Skin pws added rain over 15 minutes

[Nicolas Cazan]

Le dimanche 6 août 2017 13:46:58 UTC+2, gjr80 a écrit :
>
> Hi,
>
> If the following line is what is in weewx_pws.xml then it indicates that 
> there is an error in the syntax of the $span tag in your template.
>
> > realtime="minrain">$day_delta=900).rain.sum.formatted
>>
>
> Could you please post copies of:
>
> skins/PWS/weewx_pws.xml.tmpl
> skins/PWS/skin.conf
> the generated weewx_pws.xml
>
> Please attach the files in their entirety, do not copy one or two lines, 
> we need to see the entire files.
>
> 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.
For more options, visit https://groups.google.com/d/optout.

#   
   #
#   
   #
#  WEEWX-WD PWS SKIN CONFIGURATION FILE 
   #
#   
   #
# Version: 1.0.0 Date: 10 
January 2015 #
#   
   #


[Extras]



[Units]

#
# This section is for managing the selection and formatting of units.
#

[[Groups]]
#
# For each group of measurements, this section sets what units to use 
for it.
# NB: The unit is always in the singular. I.e., 'mile_per_hour', NOT 
'miles_per_hour'
#
group_altitude = meter  # Options are 'foot' or 'meter'
group_degree_day   = degree_C_day   # Options are 'degree_F_day' or 
'degree_C_day'
group_direction= degree_compass
group_moisture = centibar
group_percent  = percent
group_pressure = hPa# Weewx options are 'inHg', 'mmHg', 
'mbar', or 'hPa'
# Saratoga templates expect 'inHg', 
'mbar', or 'hPa'
group_radiation= watt_per_meter_squared
group_rain = mm # Weewx options are 'inch', 'cm', 
or 'mm'
# Saratoga templates expect 'inch' 
or 'mm'
group_rainrate = mm_per_hour# Weewx options are 
'inch_per_hour', 'cm_per_hour', or 'mm_per_hour'
# Saratoga templates expect 
'inch_per_hour' or 'mm_per_hour'
group_speed= km_per_hour# Options are 'mile_per_hour', 
'km_per_hour', 'knot', or 'meter_per_second'
group_speed2   = km # Options are 'mi', 'km'
group_temperature  = degree_C   # Options are 'degree_F' or 
'degree_C'
group_temperature2 = C  # Options are 'F' or 'C'
group_uv   = uv_index
group_volt = volt

# The following unit groups are used internally and should not be 
changed:
group_count= count
group_interval = minute
group_time = unix_epoch
group_elapsed  = second

[[StringFormats]]
#
# This section sets the string formatting for each type of unit.
#
centibar   = %.0f
cm = %.2f
cm_per_hour= %.2f
degree_C   = %.1f
degree_F   = %.1f
degree_compass = %.0f
foot   = %.0f
hPa= %.1f
inHg   = %.3f
inch   = %.2f
inch_per_hour  = %.2f
km_per_hour= %.0f
km_per_hour2   = %.1f
knot   = %.0f
knot2  = %.1f
mbar   = %.1f
meter  = %.0f
meter_per_second   = %.1f
meter_per_second2  = %.1f
mile_per_hour  = %.0f
mile_per_hour2 = %.1f
mm = %.1f
mmHg   = %.1f
mm_per_hour= %.1f
percent= %.0f
uv_index   = %.1f
volt   = %.1f
watt_per_meter_squared = %.0f
NONE   = "N/A"

[[Labels]]
#
# This section sets a label to be used for each type of unit.
#
centibar  = " cb"
cm= " cm"
cm_per_hour   = " cm/hr"
degree_C  = " C"
degree_F  = " F"
degree_compass=   
foot  = " 

[weewx-user] Re: Skin pws added rain over 15 minutes

[Nicolas Cazan]

Hello,
The weewx_pws.xml file is generated, but the line does not appear, here is 
the last modification.

 realtime="minrain">$day_delta=900).rain.sum.formatted
>

-- 
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] Skin pws added rain over 15 minutes

[Nicolas Cazan]

Hello I have a question: I try to add the rain fell on the last fifteen 
minutes in the XML/weewx_pws.xml file so I modified 
skins/PWS/weewx_pws.xml.tmpl and added in line rain . 

 realtime="minrain">$span($time_delta=900).rain.sum.formatted

 
But it does not work nothing adds, can you help me, thanks in advance

-- 
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: N/A in direction of maximum wind

[Nicolas Cazan]

Here are nearly twelve hours and none of N / A, the graphics are complete.
See it tomorrow morning, but I think it's ok.

Le dimanche 16 avril 2017 17:45:35 UTC+2, Nicolas Cazan a écrit :
>
> Hello, I just updated Weewx on my raspberry this morning.
>
> And I realize that in the measurements page to since midnight I is no 
> longer the direction of the maximum burst.
> I have instead N / A.
>
> My station is a wmr200, I already had this problem with an older version 
> of Weewx, an update a year ago had corrected this problem.
> Where could it come from?
>
> Thank you
>

-- 
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: N/A in direction of maximum wind

[Nicolas Cazan]

For now, and especially since I put hardware for heat index and windchill 
it had become very rare to have N / A, unlike before or I had software.

Now that the recording takes place every 5 minutes, I handed software, and 
for almost two hours no problem (software for heat index and windchill 
allows not to have two graphs blank, or graphic interspersed).

To see to the use what this gives, I keep you informed.

-- 
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: N/A in direction of maximum wind

[Nicolas Cazan]

Apr 17 11:09:53 raspberrypi weewx[24247]: engine: Record generation will be 
attempted in 'software'
Apr 17 11:09:53 raspberrypi weewx[24247]: engine: Using archive interval of 
300 seconds (specified by hardware)

Le lundi 17 avril 2017 11:04:12 UTC+2, gjr80 a écrit :
>
> You will need to stop then start weeWX after the change.
>
> Gary
>
> On Monday, 17 April 2017 19:03:37 UTC+10, gjr80 wrote:
>>
>> Try adding
>>
>> archive_interval = 300
>>
>> to the [WMR200] stanza.
>>
>> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: N/A in direction of maximum wind

[Nicolas Cazan]

[WMR200]
# This section is for the Oregon Scientific WMR200

# The station model, e.g., WMR200, WMR200A, Radio Shack W200
model = WMR200

# The driver to use:
driver = weewx.drivers.wmr200

Le lundi 17 avril 2017 10:56:29 UTC+2, gjr80 a écrit :
>
> Ok, the following lines indicate that software record generation has been 
> selected and weewx.conf [StdArchive] is set to a 300 second archive 
> period, but the archive period continues to revert to 60. 
>
> Apr 17 10:31:44 raspberrypi weewx[23850]: engine: Record generation will 
> be attempted in 'software'
> Apr 17 10:31:44 raspberrypi weewx[23850]: engine: The archive interval in 
> the configuration file (300) does not match the station hardware interval 
> (60).
> Apr 17 10:31:44 raspberrypi weewx[23850]: engine: Using archive interval 
> of 60 seconds (specified by hardware)
>
> My knoweledge of the WMR200 is being stretched, can you please post the 
> [WMR200] section of weewx.conf?
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: N/A in direction of maximum wind

[Nicolas Cazan]

Apr 17 10:30:46 raspberrypi systemd[1]: Stopping LSB: weewx weather 
system...
Apr 17 10:30:47 raspberrypi weewx[1802]: engine: Shutting down StdReport 
thread
Apr 17 10:31:07 raspberrypi weewx[1802]: engine: Unable to shut down 
StdReport thread
Apr 17 10:31:07 raspberrypi weewx[1802]: wmr200: Thread-30: I USB polling 
device thread exiting
Apr 17 10:31:07 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
next retry is Mon Apr 17 10:32:37 2017 [try http://www.rsyslog.com/e/2007 ]
Apr 17 10:31:07 raspberrypi weewx[1802]: wmr200: MainThread: I USB polling 
thread expired
Apr 17 10:31:07 raspberrypi weewx[1802]: wmr200: Thread-29: I Watchdog 
received shutdown
Apr 17 10:31:07 raspberrypi weewx[1802]: wmr200: Thread-29: I Watchdog 
thread exiting
Apr 17 10:31:07 raspberrypi weewx[1802]: wmr200: MainThread: I Watchdog 
thread expired
Apr 17 10:31:07 raspberrypi weewx[1802]: wmr200: MainThread: I Received 
packet count live:16713 archive:226 control:1205
Apr 17 10:31:07 raspberrypi weewx[1802]: wmr200: MainThread: I Received 
bytes:5560 sent bytes:88
Apr 17 10:31:07 raspberrypi weewx[1802]: wmr200: MainThread: I Packet 
archive queue len:0 live queue len:0
Apr 17 10:31:07 raspberrypi weewx[1802]: wmr200: MainThread: I Driver 
gracefully exiting
Apr 17 10:31:07 raspberrypi weewx[1802]: engine: Terminating weewx version 
3.7.1
Apr 17 10:31:40 raspberrypi weewx[1802]: imagegenerator: Generated 20 
images for StandardReport in 68.55 seconds
Apr 17 10:31:40 raspberrypi weewx[1802]: copygenerator: copied 14 files to 
/var/www/html/weewx
Apr 17 10:31:41 raspberrypi weewx[23734]: Stopping weewx weather system: 
weewx...
Apr 17 10:31:41 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...
Apr 17 10:31:43 raspberrypi weewx[23846]: engine: Initializing weewx 
version 3.7.1
Apr 17 10:31:43 raspberrypi weewx[23846]: engine: Using Python 2.7.9 
(default, Mar  8 2015, 00:52:26) #012[GCC 4.9.2]
Apr 17 10:31:43 raspberrypi weewx[23846]: engine: Platform 
Linux-4.1.17+-armv6l-with-debian-8.0
Apr 17 10:31:43 raspberrypi weewx[23846]: engine: Locale is 'fr_FR.UTF-8'
Apr 17 10:31:43 raspberrypi weewx[23846]: engine: pid file is 
/var/run/weewx.pid
Apr 17 10:31:43 raspberrypi weewx[23836]: Starting weewx weather system: 
weewx.
Apr 17 10:31:43 raspberrypi systemd[1]: Started LSB: weewx weather system.
Apr 17 10:31:43 raspberrypi weewx[23850]: engine: Using configuration file 
/etc/weewx/weewx.conf
Apr 17 10:31:43 raspberrypi weewx[23850]: engine: Loading station type 
WMR200 (weewx.drivers.wmr200)
Apr 17 10:31:43 raspberrypi weewx[23850]: wmr200: MainThread: I driver 
version is 3.3.1
Apr 17 10:31:43 raspberrypi weewx[23850]: wmr200: MainThread: I sensor map 
is {'outTempBatteryStatus': 'battery_status_out', 'outHumidity': 
'humidity_1', 'rainRate': 'rain_rate', 'heatindex4': 'heatindex_5', 
'rainTotal': 'rain_total', 'rainBatteryStatus': 'battery_status_rain', 
'heatindex6': 'heatindex_7', 'extraTemp5': 'temperature_6', 'uvFault': 
'uv_fault', 'extraTemp2': 'temperature_3', 'heatindex': 'heatindex_1', 
'extraTemp3': 'temperature_4', 'rain24': 'rain_24', 'inHeatindex': 
'heatindex_0', 'inTemp': 'temperature_0', 'extraTemp1': 'temperature_2', 
'hourRain': 'rain_hour', 'windFault': 'wind_fault', 'windchill': 
'windchill', 'clockUnsynchronized': 'clock_unsynchronized', 'extraTemp7': 
'temperature_8', 'rain': 'rain', 'forecastIcon': 'forecast_icon', 
'pressure': 'pressure', 'extraHumid4': 'humidity_5', 'extraHumid5': 
'humidity_6', 'extraHumid2': 'humidity_3', 'extraHumid3': 'humidity_4', 
'extraHumid1': 'humidity_2', 'extraTemp6': 'temperature_7', 'heatindex5': 
'heatindex_6', 'extraTemp4': 'temperature_5', 'heatindex7': 'heatindex_8', 
'altimeter': 'altimeter', 'heatindex1': 'heatindex_2', 'heatindex2': 
'heatindex_3', 'heatindex3': 'heatindex_4', 'extraHumid6': 'humidity_7', 
'extraHumid7': 'humidity_8', 'windBatteryStatus': 'battery_status_wind', 
'UV': 'uv', 'rainFault': 'rain_fault', 'windDir': 'wind_dir', 'outTemp': 
'temperature_1', 'windSpeed': 'wind_speed', 'inHumidity': 'humidity_0', 
'outTempFault': 'out_fault', 'windGust': 'wind_gust', 'uvBatteryStatus': 
'battery_status_uv'}
Apr 17 10:31:43 raspberrypi weewx[23850]: wmr200: MainThread: I Created 
watchdog thread to poke for live data every 30 seconds
Apr 17 10:31:43 raspberrypi weewx[23850]: wmr200: MainThread: I Created USB 
polling thread to read block on device
Apr 17 10:31:43 raspberrypi weewx[23850]: wmr200: Thread-2: I USB polling 
device thread for live data launched
Apr 17 10:31:43 raspberrypi weewx[23850]: wmr200: MainThread: I Reset 
console device
Apr 17 10:31:43 raspberrypi weewx[23850]: wmr200: Thread-2: I USB polling 
device thread signaled to start
Apr 17 10:31:44 raspberrypi weewx[23850]: engine: StdConvert target unit is 
0x1
Apr 17 10:31:44 raspberrypi weewx[23850]: wmr200: Thread-1: I Started 
watchdog thread live data
Apr 17 10:31:44 raspberrypi weewx[23850]: wxcalculate: The following values 
will be calculated: 

[weewx-user] Re: N/A in direction of maximum wind

[Nicolas Cazan]

I have set the time for the wmr200, small /etc/init.d/weewx reload but the 
log always returns a desynchronized clock.

Synchronization of the wmr200 by radio control does not work the one where 
it is placed, I had thought of a problem of interference, because if I move 
it it works again.

I also changed the recording frequency of the datalogger initially on 1 
minute, I put it on two minutes, but also the log returns me a frequency of 
60 seconds.

I know that I can tell Weewx to use the frequency by the software, to see 

By cone I notice a cut in the graph of the dew point around 6:00 this 
morning but no cut in temperature.

-- 
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: N/A in direction of maximum wind

[Nicolas Cazan]

Apr 16 15:08:24 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...
Apr 16 15:08:26 raspberrypi weewx[1798]: engine: Initializing weewx version 
3.7.1
Apr 16 15:08:26 raspberrypi weewx[1798]: engine: Using Python 2.7.9 
(default, Mar  8 2015, 00:52:26) #012[GCC 4.9.2]
Apr 16 15:08:26 raspberrypi weewx[1798]: engine: Platform 
Linux-4.1.17+-armv6l-with-debian-8.0
Apr 16 15:08:26 raspberrypi weewx[1798]: engine: Locale is 'fr_FR.UTF-8'
Apr 16 15:08:26 raspberrypi weewx[1798]: engine: pid file is 
/var/run/weewx.pid
Apr 16 15:08:26 raspberrypi weewx[1788]: Starting weewx weather system: 
weewx.
Apr 16 15:08:26 raspberrypi systemd[1]: Started LSB: weewx weather system.
Apr 16 15:08:27 raspberrypi weewx[1802]: engine: Using configuration file 
/etc/weewx/weewx.conf
Apr 16 15:08:27 raspberrypi weewx[1802]: engine: Loading station type 
WMR200 (weewx.drivers.wmr200)
Apr 16 15:08:27 raspberrypi weewx[1802]: wmr200: MainThread: I driver 
version is 3.3.1
Apr 16 15:08:27 raspberrypi weewx[1802]: wmr200: MainThread: I sensor map 
is {'outTempBatteryStatus': 'battery_status_out', 'outHumidity': 
'humidity_1', 'rainRate': 'rain_rate', 'heatindex4': 'heatindex_5', 
'rainTotal': 'rain_total', 'rainBatteryStatus': 'battery_status_rain', 
'heatindex6': 'heatindex_7', 'extraTemp5': 'temperature_6', 'uvFault': 
'uv_fault', 'extraTemp2': 'temperature_3', 'heatindex': 'heatindex_1', 
'extraTemp3': 'temperature_4', 'rain24': 'rain_24', 'inHeatindex': 
'heatindex_0', 'inTemp': 'temperature_0', 'extraTemp1': 'temperature_2', 
'hourRain': 'rain_hour', 'windFault': 'wind_fault', 'windchill': 
'windchill', 'clockUnsynchronized': 'clock_unsynchronized', 'extraTemp7': 
'temperature_8', 'rain': 'rain', 'forecastIcon': 'forecast_icon', 
'pressure': 'pressure', 'extraHumid4': 'humidity_5', 'extraHumid5': 
'humidity_6', 'extraHumid2': 'humidity_3', 'extraHumid3': 'humidity_4', 
'extraHumid1': 'humidity_2', 'extraTemp6': 'temperature_7', 'heatindex5': 
'heatindex_6', 'extraTemp4': 'temperature_5', 'heatindex7': 'heatindex_8', 
'altimeter': 'altimeter', 'heatindex1': 'heatindex_2', 'heatindex2': 
'heatindex_3', 'heatindex3': 'heatindex_4', 'extraHumid6': 'humidity_7', 
'extraHumid7': 'humidity_8', 'windBatteryStatus': 'battery_status_wind', 
'UV': 'uv', 'rainFault': 'rain_fault', 'windDir': 'wind_dir', 'outTemp': 
'temperature_1', 'windSpeed': 'wind_speed', 'inHumidity': 'humidity_0', 
'outTempFault': 'out_fault', 'windGust': 'wind_gust', 'uvBatteryStatus': 
'battery_status_uv'}
Apr 16 15:08:27 raspberrypi weewx[1802]: wmr200: MainThread: I Created 
watchdog thread to poke for live data every 30 seconds
Apr 16 15:08:27 raspberrypi weewx[1802]: wmr200: MainThread: I Created USB 
polling thread to read block on device
Apr 16 15:08:27 raspberrypi weewx[1802]: wmr200: Thread-2: I USB polling 
device thread for live data launched
Apr 16 15:08:27 raspberrypi weewx[1802]: wmr200: MainThread: I Reset 
console device
Apr 16 15:08:28 raspberrypi weewx[1802]: wmr200: Thread-2: I USB polling 
device thread signaled to start
Apr 16 15:08:28 raspberrypi weewx[1802]: wmr200: Thread-1: I Started 
watchdog thread live data
Apr 16 15:08:28 raspberrypi weewx[1802]: engine: StdConvert target unit is 
0x1
Apr 16 15:08:28 raspberrypi weewx[1802]: wxcalculate: The following values 
will be calculated: barometer=prefer_hardware, windchill=hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=hardware, 
windrun=prefer_hardware, heatindex=hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Apr 16 15:08:28 raspberrypi weewx[1802]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Apr 16 15:08:28 raspberrypi weewx[1802]: engine: Archive will use data 
binding wx_binding
Apr 16 15:08:28 raspberrypi weewx[1802]: engine: Record generation will be 
attempted in 'hardware'
Apr 16 15:08:28 raspberrypi weewx[1802]: engine: The archive interval in 
the configuration file (300) does not match the station hardware interval 
(60).
Apr 16 15:08:28 raspberrypi weewx[1802]: engine: Using archive interval of 
60 seconds (specified by hardware)
Apr 16 15:08:29 raspberrypi weewx[1802]: engine: Using binding 'wx_binding' 
to database 'weewx.sdb'
Apr 16 15:08:30 raspberrypi weewx[1802]: manager: Starting backfill of 
daily summaries
Apr 16 15:08:30 raspberrypi systemd[1]: Reloading.
Apr 16 15:08:31 raspberrypi weewx[1802]: restx: StationRegistry: 
Registration not requested.
Apr 16 15:08:31 raspberrypi weewx[1802]: restx: Wunderground: Posting not 
enabled.
Apr 16 15:08:31 raspberrypi weewx[1802]: restx: PWSweather: Posting not 
enabled.
Apr 16 15:08:31 raspberrypi weewx[1802]: restx: CWOP: Posting not enabled.
Apr 16 15:08:31 raspberrypi weewx[1802]: restx: WOW: Posting not enabled.
Apr 16 15:08:31 raspberrypi weewx[1802]: restx: AWEKAS: Posting not enabled.
Apr 16 

[weewx-user] Re: N/A in direction of maximum wind

[Nicolas Cazan]

Apr 16 20:19:49 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
next retry is Sun Apr 16 20:21:19 2017 [try http://www.rsyslog.com/e/2007 ]
Apr 16 20:20:48 raspberrypi weewx[1802]: wmr200: MainThread: W Clock time 
unsynchronized
Apr 16 20:20:48 raspberrypi weewx[1802]: wmr200: MainThread: W Wind sensor: 
Battery low
Apr 16 20:20:54 raspberrypi weewx[1802]: wmr200: MainThread: I genStartup() 
phase exiting since looks like all archive packets have been retrieved 
after 120 sec cnt:0
Apr 16 20:20:54 raspberrypi weewx[1802]: engine: Starting main packet loop.
Apr 16 20:21:16 raspberrypi weewx[1802]: manager: Added record 2017-04-16 
20:21:00 CEST (1492366860) to database 'weewx.sdb'
Apr 16 20:21:16 raspberrypi weewx[1802]: manager: Added record 2017-04-16 
20:21:00 CEST (1492366860) to daily summary in 'weewx.sdb'
Apr 16 20:21:22 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
next retry is Sun Apr 16 20:22:52 2017 [try http://www.rsyslog.com/e/2007 ]
Apr 16 20:21:32 raspberrypi weewx[1802]: cheetahgenerator: Generated 15 
files for report StandardReport in 14.95 seconds
Apr 16 20:21:41 raspberrypi weewx[1802]: imagegenerator: Generated 12 
images for StandardReport in 8.79 seconds
Apr 16 20:21:41 raspberrypi weewx[1802]: copygenerator: copied 14 files to 
/var/www/html/weewx
Apr 16 20:21:48 raspberrypi weewx[1802]: wmr200: MainThread: W Clock time 
unsynchronized
Apr 16 20:21:48 raspberrypi weewx[1802]: wmr200: MainThread: W Wind sensor: 
Battery low
Apr 16 20:22:17 raspberrypi weewx[1802]: manager: Added record 2017-04-16 
20:22:00 CEST (1492366920) to database 'weewx.sdb'
Apr 16 20:22:18 raspberrypi weewx[1802]: manager: Added record 2017-04-16 
20:22:00 CEST (1492366920) to daily summary in 'weewx.sdb'
Apr 16 20:22:33 raspberrypi weewx[1802]: cheetahgenerator: Generated 15 
files for report StandardReport in 15.15 seconds
Apr 16 20:22:42 raspberrypi weewx[1802]: imagegenerator: Generated 12 
images for StandardReport in 8.82 seconds
Apr 16 20:22:42 raspberrypi weewx[1802]: copygenerator: copied 0 files to 
/var/www/html/weewx
Apr 16 20:22:47 raspberrypi weewx[1802]: wmr200: MainThread: W Clock time 
unsynchronized
Apr 16 20:22:47 raspberrypi weewx[1802]: wmr200: MainThread: W Wind sensor: 
Battery low
Apr 16 20:22:53 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
next retry is Sun Apr 16 20:24:23 2017 [try http://www.rsyslog.com/e/2007 ]
Apr 16 20:23:18 raspberrypi weewx[1802]: manager: Added record 2017-04-16 
20:23:00 CEST (1492366980) to database 'weewx.sdb'
Apr 16 20:23:18 raspberrypi weewx[1802]: manager: Added record 2017-04-16 
20:23:00 CEST (1492366980) to daily summary in 'weewx.sdb'
Apr 16 20:23:33 raspberrypi weewx[1802]: cheetahgenerator: Generated 15 
files for report StandardReport in 14.77 seconds
Apr 16 20:23:43 raspberrypi weewx[1802]: imagegenerator: Generated 12 
images for StandardReport in 9.19 seconds
Apr 16 20:23:43 raspberrypi weewx[1802]: copygenerator: copied 0 files to 
/var/www/html/weewx
Apr 16 20:23:48 raspberrypi weewx[1802]: wmr200: MainThread: W Clock time 
unsynchronized
Apr 16 20:23:48 raspberrypi weewx[1802]: wmr200: MainThread: W Wind sensor: 
Battery low
Apr 16 20:24:17 raspberrypi weewx[1802]: manager: Added record 2017-04-16 
20:24:00 CEST (1492367040) to database 'weewx.sdb'
Apr 16 20:24:17 raspberrypi weewx[1802]: manager: Added record 2017-04-16 
20:24:00 CEST (1492367040) to daily summary in 'weewx.sdb'
Apr 16 20:24:31 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
next retry is Sun Apr 16 20:26:01 2017 [try http://www.rsyslog.com/e/2007 ]
Apr 16 20:24:32 raspberrypi weewx[1802]: cheetahgenerator: Generated 15 
files for report StandardReport in 13.95 seconds
Apr 16 20:24:41 raspberrypi weewx[1802]: imagegenerator: Generated 12 
images for StandardReport in 9.38 seconds
Apr 16 20:24:41 raspberrypi weewx[1802]: copygenerator: copied 0 files to 
/var/www/html/weewx
Apr 16 20:24:48 raspberrypi weewx[1802]: wmr200: MainThread: W Clock time 
unsynchronized
Apr 16 20:24:48 raspberrypi weewx[1802]: wmr200: MainThread: W Wind sensor: 
Battery low
Apr 16 20:25:18 raspberrypi weewx[1802]: manager: Added record 2017-04-16 
20:25:00 CEST (1492367100) to database 'weewx.sdb'
Apr 16 20:25:18 raspberrypi weewx[1802]: manager: Added record 2017-04-16 
20:25:00 CEST (1492367100) to daily summary in 'weewx.sdb'
Apr 16 20:25:32 raspberrypi weewx[1802]: cheetahgenerator: Generated 15 
files for report StandardReport in 14.03 seconds
Apr 16 20:25:42 raspberrypi weewx[1802]: imagegenerator: Generated 12 
images for StandardReport in 9.38 seconds

Le lundi 17 avril 2017 01:22:56 UTC+2, mwall a écrit :
>
> good call, gary.  i forgot that the wmr200 supports a data logger.
>
> nicolas, please post the log output from the time weewx starts up until 
> after a few archive intervals.
>
> 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 

[weewx-user] Re: N/A in direction of maximum wind

[Nicolas Cazan]

The one-minute delay must certainly be a problem.
Indeed the fact of having put hardware at the level of StdWXCalculate, more 
than N / A for the temperature, damages not being able to put software for 
heat index and the windchill because suddenly these two values display 
logically N / A

-- 
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: N/A in direction of maximum wind

[Nicolas Cazan]

Caution, do not take into account the clippings on the graphics between 
12:00 and 15:00, weewx update time, setting.

[URL=http://www.hostingpics.net/viewer.php?id=852574daybarometer.png][IMG]http://img4.hostingpics.net/thumbs/mini_852574daybarometer.png[/IMG][/URL]

[URL=http://www.hostingpics.net/viewer.php?id=287041daytempchill.png][IMG]http://img4.hostingpics.net/thumbs/mini_287041daytempchill.png[/IMG][/URL]

[URL=http://www.hostingpics.net/viewer.php?id=906523daytempdew.png][IMG]http://img4.hostingpics.net/thumbs/mini_906523daytempdew.png[/IMG][/URL]

[URL=http://www.hostingpics.net/viewer.php?id=148711daywinddir.png][IMG]http://img4.hostingpics.net/thumbs/mini_148711daywinddir.png[/IMG][/URL]

Le dimanche 16 avril 2017 23:51:52 UTC+2, mwall a écrit :
>
> On Sunday, April 16, 2017 at 5:41:56 PM UTC-4, Nicolas Cazan wrote:
>>
>> The graphs are generated by weewx, the curves are split into several 
>> places probably when the displayed data is N / A.
>>
>> On the contrary strange with the old version I had parameterized a 
>> frequency of five minutes for the data, that is 300 seconds, I put the same 
>> setting in weewx.conf and skin.conf, but I always get a frequency d 'One 
>> minute, I think that if I move to the month 3 to 5 minutes this should 
>> reduce the N / A.
>>
>
> could you post an example that illustrates the problem?
>
> another thing to beware of is whether a variable is an observation from 
> the sensors or a derived calculation, for example temperature and dewpoint, 
> respectively.
>
> for stations such as wmr200 that have partial packets and that emit 
> derived values, you should have 'hardware' for any derived calculations 
> that the hardware provides.  for example, for wmr200 you should have this 
> in your weewx configuration:
>
> [StdWXCalculate]
> [[Calculations]]
> rainRate = hardware
> windchill = hardware
> heatindex = hardware
>
> 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: N/A in direction of maximum wind

[Nicolas Cazan]

The graphs are generated by weewx, the curves are split into several places 
probably when the displayed data is N / A.

On the contrary strange with the old version I had parameterized a 
frequency of five minutes for the data, that is 300 seconds, I put the same 
setting in weewx.conf and skin.conf, but I always get a frequency d 'One 
minute, I think that if I move to the month 3 to 5 minutes this should 
reduce the N / A.

-- 
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: N/A in direction of maximum wind

[Nicolas Cazan]

Le dimanche 16 avril 2017 22:51:34 UTC+2, mwall a écrit :
>
>
> expected behavior for wmr200 stations is that there is no windGustDir
>
> if you want windGustDir, use the configuration change described in a 
> previous message in this thread
>
>

I made the change in weewx.conf, but the wind faded, I would see at 
midnight the result, in an hour.

 

>  
>
>> I also notice that it is at times, for temperature, pressure, hygrometry, 
>> heat index, windchill, this displays N / A randomly or even at the same 
>> time.
>>
>
> this is normal behavior for stations that emit partial packets.
>
> if you look at loop packets, there will be many None/NULL values.  if you 
> look at archive records, all of the fields should be populated (if you have 
> sensors for those fields, of course).
>
>

This behavior is unfortunate, this produces graphs often incomplete.
Is there a way around this? 

-- 
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: N/A in direction of maximum wind

[Nicolas Cazan]

I did not understand sorry, in addition I explained myself badly, I updated 
this morning my version of weewx for version 3.7.1, the .deb of this 
version contains you the corrective of January or must Do I edit the 
wmr200.py file manually?


I also notice that it is at times, for temperature, pressure, hygrometry, 
heat index, windchill, this displays N / A randomly or even at the same 
time.

I am a French user with a rather average level of English, I sometimes find 
it difficult to understand.

-- 
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: N/A in direction of maximum wind

[Nicolas Cazan]

Okay, but today's driver update contains the fixes, or should we do them 
manually?

-- 
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] N/A in direction of maximum wind

[Nicolas Cazan]

Hello, I just updated Weewx on my raspberry this morning.

And I realize that in the measurements page to since midnight I is no 
longer the direction of the maximum burst.
I have instead N / A.

My station is a wmr200, I already had this problem with an older version of 
Weewx, an update a year ago had corrected this problem.
Where could it come from?

Thank you

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