Re: [weewx-user] Re: how to test for null data

[Andrew Milner]

as i said if communication is lost no data is saved in the database - so 
you will not have n/a, null or anything else in the database.  in fact 
weewx will ultimately stop running and eventually do a restart.  the 
symptom will be shown by the time of the generated html file - which will 
be older than 5 minutes ago (or whatever archive period you have 
specified).  do my test and see what happens.



On Monday, 7 October 2019 21:15:43 UTC+3, Pila wrote:
>
> I meant: my external program parses output. How will my program know USB 
> broke down? What value in my program should i test to find reset is needed? 
> Will N/A be saved?
>
> Na 7. listopada 2019. 15:26:17 CEST, Andrew Milner  > wrote:
>>
>> the driver will log an error if communication with the fine offset is 
>> lost, and does not continue to store data in the database until 
>> communication is restored.
>>
>>
>>
>>
>>
>> On Monday, 7 October 2019 16:19:19 UTC+3, Pila wrote:
>>>
>>> I export InTemp to check if my USB connection to the First Offset 
>>> dropped dead.
>>>
>>> InTemp  $current.inTemp.format(add_label=False)
>>> InTemp  $current.inTemp.raw
>>>
>>> What will be produced in case of null data? What do I need to test? 
>>>
>>> In the first case, I expect N/A to mean USB connection is lost. I am 
>>> guessing N/A will not be in raw data. An empty field?
>>>
>>> So, probably the first line is a better choice for such purpose?
>>>
>>>

-- 
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/d568a3df-30af-4642-8337-7bbae390a8bf%40googlegroups.com.

Re: [weewx-user] Re: minmax and maxmin with span killing page?

[Thomas Keffer]

There is indeed a "minmax" aggregate, but it comes with limitations. The
start and end of the aggregation interval must be at midnight. I suspect
the problem is that you are attempting to do it from a random time of the
day. In that case, minmax (and maxmin) would then be not well-defined
mathematically.

-tk

On Mon, Oct 7, 2019 at 11:11 AM Pila  wrote:

> They are not nearly the same thing. In the summer, we do not care about
> the coldest night. Warmest nights are the problem. Warmest nights are of
> interest. In the winter lowest daily maximum becomes crucial.
>
> Pity. This is very unfortunate missing crucial feature. These two really
> should exist in any good meteo program.
>
> Then again, why they exist in standard form which is useless to describe
> graphs?
>
>
> Na 7. listopada 2019. 19:36:52 CEST, Andrew Milner <
> andrew.s.r.mil...@gmail.com> wrote:
>>
>> there is no aggregate minmax or maxmin - just saying min will give the
>> lowest value over the span and just saying max will give the highest value
>> over the period
>>
>> so
>>
>> minmax: $span(day_delta=7).outTemp.minmax
>> maxmin: $span(day_delta=7).outTemp.maxmin
>>
>> should be
>>
>> minmax: $span(day_delta=7).outTemp.min
>> maxmin: $span(day_delta=7).outTemp.max
>>
>> On Monday, 7 October 2019 20:21:09 UTC+3, Pila wrote:
>>>
>>> Sorry, I was making notes on everything I wanted to ask, and in all that
>>> logging, I forgot a log I should include :)
>>>
>>> wee_reports[14046]: cheetahgenerator: Generate failed with exception '>> 'weewx.ViolatedPrecondition'>'
>>> wee_reports[14046]: cheetahgenerator:  Ignoring template /home/weewx
>>> /skins/Smartphone/temp.html.tmpl
>>> wee_reports[14046]: cheetahgenerator:  Reason: Invalid aggregation
>>> type 'minmax'
>>> wee_reports[14046]:   Traceback (most recent call last):
>>> wee_reports[14046]: File
>>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 332, in generate
>>> wee_reports[14046]:   fd.write(str(compiled_template))
>>> wee_reports[14046]: File
>>> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1045, in
>>> __str__
>>> wee_reports[14046]:   rc = getattr(self, mainMethName)()
>>> wee_reports[14046]: File
>>> "_home_weewx_skins_Smartphone_temp_html_tmpl.py", line 151, in respond
>>> wee_reports[14046]: File "/home/weewx/bin/weewx/tags.py", line
>>> 329, in __getattr__
>>> wee_reports[14046]:   return self._do_query(aggregate_type)
>>> wee_reports[14046]: File "/home/weewx/bin/weewx/tags.py", line
>>> 343, in _do_query
>>> wee_reports[14046]:   val=val, **self.option_dict)
>>> wee_reports[14046]: File "/home/weewx/bin/weewx/wxmanager.py",
>>> line 60, in getAggregate
>>> wee_reports[14046]:   return weewx.manager.DaySummaryManager.
>>> getAggregate(self, timespan, obs_type, aggregateType, **option_dict)
>>> wee_reports[14046]: File "/home/weewx/bin/weewx/manager.py",
>>> line 1268, in getAggregate
>>> wee_reports[14046]:   **option_dict)
>>> wee_reports[14046]: File "/home/weewx/bin/weewx/manager.py",
>>> line 450, in getAggregate
>>> wee_reports[14046]:   raise weewx.ViolatedPrecondition("Invalid
>>> aggregation type '%s'" % aggregate_type)
>>> wee_reports[14046]:   ViolatedPrecondition: Invalid aggregation
>>> type 'minmax'
>>>
>>>
>>>
>>> --
> 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/26FB5345-2EA6-41AB-A6A7-09CD1FECBCA3%40gmail.com
> 
> .
>

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

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

[Xant]

Hey Pat

DarkSky 8 Day Forecast its interesting, but takes a lot of "real state", 
specially when or if you check WeeWX/Belchertown from a mobile device. 
Sure, there is an option in 'skin.conf' to turn it off, but by doing that, 
the "current weather icon" on side on current Temp, and probably weather 
warnings will go off too.

I managed to turned the "2nd row" off, by tweaking the 'index.html.tmpl' 
file. But would be interesting if you may add "another switch", to turn the 
2nd row off, while still keeping "current weather icon" and weather 
warnings On.

Or better yet, make "current weather icon" and weather warning 'skin 
standard', while still keeping DarkSky 8 Day Forecast On/Off switch.

Thank you always for B-skin,
Xant

-- 
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/75ed70fb-d123-4005-a57c-85e9a7df72e2%40googlegroups.com.

Re: [weewx-user] Re: minmax and maxmin with span killing page?

[vince]

On Monday, October 7, 2019 at 11:11:32 AM UTC-7, Pila wrote:

> Pity. This is very unfortunate missing crucial feature. These two really 
> should exist in any good meteo program.
>
> Then again, why they exist in standard form which is useless to describe 
> graphs? 
>>
>>

[...rant on...]

FWIW, your constant negativity and criticism is getting extremely tiring 
and is likely stopping people from spending their minimal time and energy 
to try to give you (free) support out of the goodness of your hearts.

I'd invite you to please write your own weather app that does what you want 
it to do.  Then you can criticize the author by looking in the mirror.

Thank you.

[...rant off...]

-- 
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/2043784d-79c6-4e95-a1c4-d0820c9157b1%40googlegroups.com.

Re: [weewx-user] Re: how to test for null data

[Pila]

I meant: my external program parses output. How will my program know USB broke 
down? What value in my program should i test to find reset is needed? Will N/A 
be saved?

Na 7. listopada 2019. 15:26:17 CEST, Andrew Milner 
 wrote:
>the driver will log an error if communication with the fine offset is
>lost, 
>and does not continue to store data in the database until communication
>is 
>restored.
>
>
>
>
>
>On Monday, 7 October 2019 16:19:19 UTC+3, Pila wrote:
>>
>> I export InTemp to check if my USB connection to the First Offset
>dropped 
>> dead.
>>
>> InTemp  $current.inTemp.format(add_label=False)
>> InTemp  $current.inTemp.raw
>>
>> What will be produced in case of null data? What do I need to test? 
>>
>> In the first case, I expect N/A to mean USB connection is lost. I am 
>> guessing N/A will not be in raw data. An empty field?
>>
>> So, probably the first line is a better choice for such purpose?
>>
>>
>
>-- 
>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/ae479a8c-309e-49b0-b797-9839a62743ff%40googlegroups.com.

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

Re: [weewx-user] Re: minmax and maxmin with span killing page?

[Pila]

They are not nearly the same thing. In the summer, we do not care about the 
coldest night. Warmest nights are the problem. Warmest nights are of interest. 
In the winter lowest daily maximum becomes crucial.

Pity. This is very unfortunate missing crucial feature. These two really should 
exist in any good meteo program.

Then again, why they exist in standard form which is useless to describe 
graphs? 


Na 7. listopada 2019. 19:36:52 CEST, Andrew Milner 
 wrote:
>there is no aggregate minmax or maxmin - just saying min will give the 
>lowest value over the span and just saying max will give the highest
>value 
>over the period
>
>so
>
>minmax: $span(day_delta=7).outTemp.minmax
>maxmin: $span(day_delta=7).outTemp.maxmin
>
>should be
>
>minmax: $span(day_delta=7).outTemp.min
>maxmin: $span(day_delta=7).outTemp.max
>
>On Monday, 7 October 2019 20:21:09 UTC+3, Pila wrote:
>>
>> Sorry, I was making notes on everything I wanted to ask, and in all
>that 
>> logging, I forgot a log I should include :)
>>
>> wee_reports[14046]: cheetahgenerator: Generate failed with exception
>'> 'weewx.ViolatedPrecondition'>'
>> wee_reports[14046]: cheetahgenerator:  Ignoring template
>/home/weewx/
>> skins/Smartphone/temp.html.tmpl
>> wee_reports[14046]: cheetahgenerator:  Reason: Invalid
>aggregation 
>> type 'minmax'
>> wee_reports[14046]:   Traceback (most recent call last):
>> wee_reports[14046]: File 
>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 332, in generate
>> wee_reports[14046]:   fd.write(str(compiled_template))
>> wee_reports[14046]: File 
>> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1045, in
>
>> __str__
>> wee_reports[14046]:   rc = getattr(self, mainMethName)()
>> wee_reports[14046]: File 
>> "_home_weewx_skins_Smartphone_temp_html_tmpl.py", line 151, in
>respond
>> wee_reports[14046]: File "/home/weewx/bin/weewx/tags.py",
>line 329
>> , in __getattr__
>> wee_reports[14046]:   return self._do_query(aggregate_type)
>> wee_reports[14046]: File "/home/weewx/bin/weewx/tags.py",
>line 343
>> , in _do_query
>> wee_reports[14046]:   val=val, **self.option_dict)
>> wee_reports[14046]: File
>"/home/weewx/bin/weewx/wxmanager.py", 
>> line 60, in getAggregate
>> wee_reports[14046]:   return weewx.manager.DaySummaryManager.
>> getAggregate(self, timespan, obs_type, aggregateType, **option_dict)
>> wee_reports[14046]: File "/home/weewx/bin/weewx/manager.py",
>line 
>> 1268, in getAggregate
>> wee_reports[14046]:   **option_dict)
>> wee_reports[14046]: File "/home/weewx/bin/weewx/manager.py",
>line 
>> 450, in getAggregate
>> wee_reports[14046]:   raise
>weewx.ViolatedPrecondition("Invalid 
>> aggregation type '%s'" % aggregate_type)
>> wee_reports[14046]:   ViolatedPrecondition: Invalid aggregation
>type 
>> 'minmax'
>>
>>
>>
>>
>
>-- 
>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/e81fb202-03a6-41aa-b35b-4344f608fddb%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/26FB5345-2EA6-41AB-A6A7-09CD1FECBCA3%40gmail.com.

[weewx-user] Re: minmax and maxmin with span killing page?

[Andrew Milner]

there is no aggregate minmax or maxmin - just saying min will give the 
lowest value over the span and just saying max will give the highest value 
over the period

so

minmax: $span(day_delta=7).outTemp.minmax
maxmin: $span(day_delta=7).outTemp.maxmin

should be

minmax: $span(day_delta=7).outTemp.min
maxmin: $span(day_delta=7).outTemp.max

On Monday, 7 October 2019 20:21:09 UTC+3, Pila wrote:
>
> Sorry, I was making notes on everything I wanted to ask, and in all that 
> logging, I forgot a log I should include :)
>
> wee_reports[14046]: cheetahgenerator: Generate failed with exception ' 'weewx.ViolatedPrecondition'>'
> wee_reports[14046]: cheetahgenerator:  Ignoring template /home/weewx/
> skins/Smartphone/temp.html.tmpl
> wee_reports[14046]: cheetahgenerator:  Reason: Invalid aggregation 
> type 'minmax'
> wee_reports[14046]:   Traceback (most recent call last):
> wee_reports[14046]: File 
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 332, in generate
> wee_reports[14046]:   fd.write(str(compiled_template))
> wee_reports[14046]: File 
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1045, in 
> __str__
> wee_reports[14046]:   rc = getattr(self, mainMethName)()
> wee_reports[14046]: File 
> "_home_weewx_skins_Smartphone_temp_html_tmpl.py", line 151, in respond
> wee_reports[14046]: File "/home/weewx/bin/weewx/tags.py", line 329
> , in __getattr__
> wee_reports[14046]:   return self._do_query(aggregate_type)
> wee_reports[14046]: File "/home/weewx/bin/weewx/tags.py", line 343
> , in _do_query
> wee_reports[14046]:   val=val, **self.option_dict)
> wee_reports[14046]: File "/home/weewx/bin/weewx/wxmanager.py", 
> line 60, in getAggregate
> wee_reports[14046]:   return weewx.manager.DaySummaryManager.
> getAggregate(self, timespan, obs_type, aggregateType, **option_dict)
> wee_reports[14046]: File "/home/weewx/bin/weewx/manager.py", line 
> 1268, in getAggregate
> wee_reports[14046]:   **option_dict)
> wee_reports[14046]: File "/home/weewx/bin/weewx/manager.py", line 
> 450, in getAggregate
> wee_reports[14046]:   raise weewx.ViolatedPrecondition("Invalid 
> aggregation type '%s'" % aggregate_type)
> wee_reports[14046]:   ViolatedPrecondition: Invalid aggregation type 
> 'minmax'
>
>
>
>

-- 
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/e81fb202-03a6-41aa-b35b-4344f608fddb%40googlegroups.com.

[weewx-user] Re: minmax and maxmin with span killing page?

[Pila]

Sorry, I was making notes on everything I wanted to ask, and in all that 
logging, I forgot a log I should include :)

wee_reports[14046]: cheetahgenerator: Generate failed with exception ''
wee_reports[14046]: cheetahgenerator:  Ignoring template /home/weewx/
skins/Smartphone/temp.html.tmpl
wee_reports[14046]: cheetahgenerator:  Reason: Invalid aggregation type 
'minmax'
wee_reports[14046]:   Traceback (most recent call last):
wee_reports[14046]: File "/home/weewx/bin/weewx/cheetahgenerator.py"
, line 332, in generate
wee_reports[14046]:   fd.write(str(compiled_template))
wee_reports[14046]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1045, in 
__str__
wee_reports[14046]:   rc = getattr(self, mainMethName)()
wee_reports[14046]: File 
"_home_weewx_skins_Smartphone_temp_html_tmpl.py", line 151, in respond
wee_reports[14046]: File "/home/weewx/bin/weewx/tags.py", line 329, 
in __getattr__
wee_reports[14046]:   return self._do_query(aggregate_type)
wee_reports[14046]: File "/home/weewx/bin/weewx/tags.py", line 343, 
in _do_query
wee_reports[14046]:   val=val, **self.option_dict)
wee_reports[14046]: File "/home/weewx/bin/weewx/wxmanager.py", line 
60, in getAggregate
wee_reports[14046]:   return weewx.manager.DaySummaryManager.
getAggregate(self, timespan, obs_type, aggregateType, **option_dict)
wee_reports[14046]: File "/home/weewx/bin/weewx/manager.py", line 
1268, in getAggregate
wee_reports[14046]:   **option_dict)
wee_reports[14046]: File "/home/weewx/bin/weewx/manager.py", line 
450, in getAggregate
wee_reports[14046]:   raise weewx.ViolatedPrecondition("Invalid 
aggregation type '%s'" % aggregate_type)
wee_reports[14046]:   ViolatedPrecondition: Invalid aggregation type 
'minmax'



-- 
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/a1ef2b75-9930-4ec9-a78e-4c26770c7866%40googlegroups.com.

Re: [weewx-user] Re: Rasberry Pi weather station with anemometer and camera only

[Sean Jahnig]

Thanks for the suggestion Liz,

I tried to open it but i didn't find any hidden usb port... worth a try.

I ordered a display that is labelled as having ' PC connect' so i'm hoping
that one will be right.


On Sun, Oct 6, 2019 at 9:47 AM Liz  wrote:

> On Sat, 5 Oct 2019 21:10:59 +0400
> Sean Jahnig  wrote:
>
> > Nah it's my fault. I thought i had researched it properly but clearly
> > not. Let's hope the new display that I've bought will solve the
> > problem.
> >
> > Thanks again for the help.
> >
> > Thanks,
> >
> > Sean Jahnig
>
> Is this a device which is compatible with an interceptor?
> If you are not intending to return it, have you looked inside the
> plastic box to see if the port is actually there, just hidden?
>
> Liz
>
> --
> 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/20191006164531.13f822a4%40billiau.net
> .
>

-- 
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/CALeSoZnLR2e6h9ROEPPnhrKAQUF0cuNVbyW1dx6m_S_fRTiv3w%40mail.gmail.com.

Re: [weewx-user] Graphs do not display data perfectly

[Andrew Milner]

I plot max for windgust to ensure I always plot the maximum wind.



On Monday, 7 October 2019 14:57:08 UTC+3, Thomas Keffer wrote:
>
> Yes, you are right about the averaging effect. Averaging does that. If you 
> want to show the extremes, you can try plotting min and max dewpoint.
>
> And, knock off the comments about "pointlessly count." It's getting old.
>
> On Mon, Oct 7, 2019 at 2:34 AM mrzimgjugl asdf  > wrote:
>
>> Daily graph is correct, weekly seems to have misplaced the same min 
>> value, likely by averaging. I have a weekly graph showing dew point going 
>> somewhere about 1C and not near the 0C bottom line. At the same moment, my 
>> daily graph shows the red line clearly at the 0C.
>>
>> By now I know both the original day and month min dew are wrong since 
>> they ignore the 27 hours and 7 day (and so on) shown above them and 
>> pointlessly count from the monday (today). Span method prints the same 
>> correct min -0,1C (present in graphs from yesterday) in both day and week.
>>
>> If I am right about the averaging taking place (aggregation), can I 
>> somehow modify it to show graph more preciselly? This 0C Dew is important. 
>> I would like to see it a week and month graphs. To what extent can i reduce 
>> aggregate period for a week graph with no ill effects?
>>
>> -- 
>> 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/772952bf-cbd4-4e38-923d-12fc2ce09868%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2dccd581-f724-43dd-9088-169a9e029f39%40googlegroups.com.

[weewx-user] Re: how to test for null data

[Andrew Milner]

to test just disconnect the usb and then check the log.  you should not 
find null data recorded.  when communication is restored weewx will attempt 
to read data from the fineoffset station which may have been stored whilst 
there was no communication and will then resume normal loop and rec 
operations.



On Monday, 7 October 2019 16:26:17 UTC+3, Andrew Milner wrote:
>
> the driver will log an error if communication with the fine offset is 
> lost, and does not continue to store data in the database until 
> communication is restored.
>
>
>
>
>
> On Monday, 7 October 2019 16:19:19 UTC+3, Pila wrote:
>>
>> I export InTemp to check if my USB connection to the First Offset dropped 
>> dead.
>>
>> InTemp  $current.inTemp.format(add_label=False)
>> InTemp  $current.inTemp.raw
>>
>> What will be produced in case of null data? What do I need to test? 
>>
>> In the first case, I expect N/A to mean USB connection is lost. I am 
>> guessing N/A will not be in raw data. An empty field?
>>
>> So, probably the first line is a better choice for such purpose?
>>
>>

-- 
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/0959bce7-6b19-4a14-aea8-f830d6a75a50%40googlegroups.com.

[weewx-user] Re: how to test for null data

[Andrew Milner]

the driver will log an error if communication with the fine offset is lost, 
and does not continue to store data in the database until communication is 
restored.





On Monday, 7 October 2019 16:19:19 UTC+3, Pila wrote:
>
> I export InTemp to check if my USB connection to the First Offset dropped 
> dead.
>
> InTemp  $current.inTemp.format(add_label=False)
> InTemp  $current.inTemp.raw
>
> What will be produced in case of null data? What do I need to test? 
>
> In the first case, I expect N/A to mean USB connection is lost. I am 
> guessing N/A will not be in raw data. An empty field?
>
> So, probably the first line is a better choice for such purpose?
>
>

-- 
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/ae479a8c-309e-49b0-b797-9839a62743ff%40googlegroups.com.

[weewx-user] how to test for null data

[Pila]

I export InTemp to check if my USB connection to the First Offset dropped 
dead.

InTemp  $current.inTemp.format(add_label=False)
InTemp  $current.inTemp.raw

What will be produced in case of null data? What do I need to test? 

In the first case, I expect N/A to mean USB connection is lost. I am 
guessing N/A will not be in raw data. An empty field?

So, probably the first line is a better choice for such purpose?

-- 
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/6b994706-af4d-4268-bcde-bf9d379d7434%40googlegroups.com.

Re: [weewx-user] Bash: get current weather data

[Pila]

If you really want just to send a notification, use alarm.Py.

If you want to base automation on this data, I can provide example how I did 
it. But you would still need to solve sending e-mails on your own since my RPI 
Zero uses my router to do so.

Na 5. listopada 2019. 18:34:06 CEST, Ramesh Rasappan  wrote:
>do you parse the html page? could you please share the shell script?
>thanks
>
>On Friday, October 4, 2019 at 5:19:09 PM UTC+5:30, Pila wrote:
>>
>> If you really want notification, it can generate email.
>>
>> I use data to close shutters if it rains from the west half. I simply
>
>> parse generated page and extract data I need. All from shell script.
>5 
>> lines of code to extract 8 variables. My Zero jest closed shutters
>since it 
>> was sunset. 
>>
>> Na 3. listopada 2019. 16:01:58 CEST, Ramesh Rasappan
>> > wrote:
>>>
>>> My current setup pulls weather data from Offset console using 
>>> weewx-wh23xx driver. I want to run a bash script that can get the
>current 
>>> weather and send me a notification if it meets the criteria.
>>>
>>>
>>> I could probably get the weather data directly from PWS console 
>>> using weewx-wh23xx driver but I can't figure out this!! Of course
>one could 
>>> use sqlite3 to pull the data from either weewx database 
>>> (/var/lib/weewx/weewx.sdb) but it looks complicated for me that I
>have to 
>>> run some complex script to retrieve the current data!
>>>
>>>
>>> Can you share some script that can pull the current data from either
>
>>> weewx database or from the console? thank you
>>>
>>>
>>>
>>>
>> -- 
>> Poslano sa mog Android uređaja sa K-9 Mail. Molim vas oprostite na
>mojoj 
>> sažetosti.
>>
>
>-- 
>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/729bdb6a-42fd-4f1e-a2d4-3e58fbb44814%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/A60E30FD-92AB-405D-AEB2-824FBCE83910%40gmail.com.

Re: [weewx-user] Graphs do not display data perfectly

[Thomas Keffer]

Yes, you are right about the averaging effect. Averaging does that. If you
want to show the extremes, you can try plotting min and max dewpoint.

And, knock off the comments about "pointlessly count." It's getting old.

On Mon, Oct 7, 2019 at 2:34 AM mrzimgjugl asdf  wrote:

> Daily graph is correct, weekly seems to have misplaced the same min value,
> likely by averaging. I have a weekly graph showing dew point going
> somewhere about 1C and not near the 0C bottom line. At the same moment, my
> daily graph shows the red line clearly at the 0C.
>
> By now I know both the original day and month min dew are wrong since they
> ignore the 27 hours and 7 day (and so on) shown above them and pointlessly
> count from the monday (today). Span method prints the same correct min
> -0,1C (present in graphs from yesterday) in both day and week.
>
> If I am right about the averaging taking place (aggregation), can I
> somehow modify it to show graph more preciselly? This 0C Dew is important.
> I would like to see it a week and month graphs. To what extent can i reduce
> aggregate period for a week graph with no ill effects?
>
> --
> 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/772952bf-cbd4-4e38-923d-12fc2ce09868%40googlegroups.com
> 
> .
>

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

[weewx-user] Re: minmax and maxmin with span killing page?

[Andrew Milner]

what error does the log give when the html fails to generate??

the log usually contains the key to all weewx failures, and should always 
be the first place to look.  In the event of a suspected weewx failure or 
problem the log should also be attached to the post describing the issue so 
taht others may get to see the log clues.





On Monday, 7 October 2019 12:37:12 UTC+3, Pila wrote:
>
> I have added minmax and maxmin to the SmartPhone temp.html.tmpl. I use the 
> weekly outside temeprature for examples. The standard but useless (becuase 
> it does not relate to the above graph) form works perfectly fine:
>
> maxmin2: $week.outTemp.minmax at $week.outTemp.minmaxtime
> minmax2: $week.outTemp.maxmin at $week.outTemp.maxmintime
>
> But, when I try my span delta modified version, not only they do not 
> display, temp.html stops being generated at all until I remove these lines 
> completely! I added two lines in front of the regular max and min:
>
> minmax: $span(day_delta=7).outTemp.minmax
> maxmin: $span(day_delta=7).outTemp.maxmin
>
>

-- 
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/1ca686a3--405f-bcfe-16c27ba642f7%40googlegroups.com.

Re: [weewx-user] span delta does not start from NOW?

[Pila]

I have just realized I probably misspoke and invented a problem!

I made a mistake of looking the start time of the graph and assuming it to be 
27 hours ago! It is not since graph steps in 3 hours intervals.

Since I was working on this some time between other things I do, timeline (my 
reports) changed in the meantime and I failed to take that into account.

Span actually works as advertised taking NOW as a reference point. And does it 
literary. Graph is not. And both work fine. 

Am I right to say I was wrong?

Na 7. listopada 2019. 11:31:59 CEST, mrzimgjugl asdf  
wrote:
>Thanks to Andrew Milner, I can now fix wrong min/max lines using span
>with 
>delta. Now min/max correspond mostly with the graphs above them. Good
>thing 
>WeeWX is almost escellent and almost anything can be achieved with it.
>So, 
>I am expecting this should be fixable.
>
>Using span delta, I am getting some wierd results not seen on the
>graphs 
>directly above to which I tried to sync these min and max lines.
>
>Problem may be with the reference from which span delta starts and that
>
>reference seems not to be NOW. Possibly, the midnight before NOW is
>taken 
>as a reference and starting point for the span? I can see the problem
>in 
>many cases. How to fix that?
>
>Current report was generated at monday 9:15. Graph correctly starts at
>9:00 
>at Sunday and it just added new segment after 9:00 monday, so it shows
>27 
>hours. I have modified summary min/max text below the graph into:
>
>max: $span(hour_delta = 27).outTemp.max at $span(hour_delta = 
>27).outTemp.maxtime.format("%A %k:%M")
>min: $span(hour_delta = 27).outTemp.min at $span(hour_delta = 
>27).outTemp.mintime.format("%A %k:%M")
>
>But the text says:
>max: 25,6°C at Sunday 15:25
>min: 15,0°C at Sunday 6:55
>
>Sunday 6:55 should be out of scope since I generated report at monday
>9:15. 
>I do not see in manual a precise definition what is the starting point
>for 
>span delta. So, I estimate it is not using NOW as the end starting
>point 
>but something else.
>
>My question: what is the reference point in time for commands like:
>$span(hour_delta=27)
>$span(day_delta=7)
>$span(day_delta=30)
>
>I want spans to summarise the same period as the graphs above them.
>They 
>all summarise form the moment when the report is generated back for
>given 
>time: 27 hours or 7 or 30 days. Not take entire calendar days from the
>last 
>midngiht or something like this. I even tried to give all spans in
>hours, 
>but I do not think that helps. This is not the simplest issue to test.
>
>-- 
>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/5b5f998f-d384-4cd0-9c5b-b1019c06b40a%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/111669A1-4D6A-47F5-AA75-81E1AE361B1C%40gmail.com.

[weewx-user] minmax and maxmin with span killing page?

[mrzimgjugl asdf]

I have added minmax and maxmin to the SmartPhone temp.html.tmpl. I use the 
weekly outside temeprature for examples. The standard but useless (becuase 
it does not relate to the above graph) form works perfectly fine:

maxmin2: $week.outTemp.minmax at $week.outTemp.minmaxtime
minmax2: $week.outTemp.maxmin at $week.outTemp.maxmintime

But, when I try my span delta modified version, not only they do not 
display, temp.html stops being generated at all until I remove these lines 
completely! I added two lines in front of the regular max and min:

minmax: $span(day_delta=7).outTemp.minmax
maxmin: $span(day_delta=7).outTemp.maxmin

-- 
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/3a012719-f136-49d6-878e-f020b180be5b%40googlegroups.com.

[weewx-user] span delta does not start from NOW?

[mrzimgjugl asdf]

Thanks to Andrew Milner, I can now fix wrong min/max lines using span with 
delta. Now min/max correspond mostly with the graphs above them. Good thing 
WeeWX is almost escellent and almost anything can be achieved with it. So, 
I am expecting this should be fixable.

Using span delta, I am getting some wierd results not seen on the graphs 
directly above to which I tried to sync these min and max lines.

Problem may be with the reference from which span delta starts and that 
reference seems not to be NOW. Possibly, the midnight before NOW is taken 
as a reference and starting point for the span? I can see the problem in 
many cases. How to fix that?

Current report was generated at monday 9:15. Graph correctly starts at 9:00 
at Sunday and it just added new segment after 9:00 monday, so it shows 27 
hours. I have modified summary min/max text below the graph into:

max: $span(hour_delta = 27).outTemp.max at $span(hour_delta = 
27).outTemp.maxtime.format("%A %k:%M")
min: $span(hour_delta = 27).outTemp.min at $span(hour_delta = 
27).outTemp.mintime.format("%A %k:%M")

But the text says:
max: 25,6°C at Sunday 15:25
min: 15,0°C at Sunday 6:55

Sunday 6:55 should be out of scope since I generated report at monday 9:15. 
I do not see in manual a precise definition what is the starting point for 
span delta. So, I estimate it is not using NOW as the end starting point 
but something else.

My question: what is the reference point in time for commands like:
$span(hour_delta=27)
$span(day_delta=7)
$span(day_delta=30)

I want spans to summarise the same period as the graphs above them. They 
all summarise form the moment when the report is generated back for given 
time: 27 hours or 7 or 30 days. Not take entire calendar days from the last 
midngiht or something like this. I even tried to give all spans in hours, 
but I do not think that helps. This is not the simplest issue to test.

-- 
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/5b5f998f-d384-4cd0-9c5b-b1019c06b40a%40googlegroups.com.

[weewx-user] Graphs do not display data perfectly

[mrzimgjugl asdf]

Daily graph is correct, weekly seems to have misplaced the same min value, 
likely by averaging. I have a weekly graph showing dew point going 
somewhere about 1C and not near the 0C bottom line. At the same moment, my 
daily graph shows the red line clearly at the 0C.

By now I know both the original day and month min dew are wrong since they 
ignore the 27 hours and 7 day (and so on) shown above them and pointlessly 
count from the monday (today). Span method prints the same correct min 
-0,1C (present in graphs from yesterday) in both day and week.

If I am right about the averaging taking place (aggregation), can I somehow 
modify it to show graph more preciselly? This 0C Dew is important. I would 
like to see it a week and month graphs. To what extent can i reduce 
aggregate period for a week graph with no ill effects?

-- 
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/772952bf-cbd4-4e38-923d-12fc2ce09868%40googlegroups.com.