[weewx-user] Re: crt extension has been updated

[gjr80]

I did a bit of digging/googling/reading between the lines when I was putting 
together an extension to produce a loop based gauge-data.txt for the 
SteelSeries gauges and worked out the format of the windrose 'field' 
(realtime.txt and gauge-data.txt use the same Cumulus windrose web tag). From 
memory it is simply the sum of the wind speeds for each of the 16 
cardinal/intercardinal/secondary intercardinal directions over a period of 
time. A fairly straightforward sql query and a bit of processing of the query 
results gives the required data. Units are irrelevant since all you are 
concerned with is the relative values. My implementation is in def 
calc_windrose() in rtgd.py 
(https://github.com/gjr80/weewx-realtime_gauge-data/blob/master/bin/user/rtgd.py)

Don't see why a simple template could not be used for realmore.txt, there is 
nothing complex about it and one of the linked docs says 'does not require an 
update in realtime, just every few minutes' so a cheetah template would do fine.

CumulusWebTagsEngine and CumulusGenerator, maybe next months job, unless you 
have one ready to go Matthew?

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: crt extension has been updated

[mwall]

On Thursday, December 28, 2017 at 11:05:22 PM UTC-5, gjr80 wrote:
>
> Just look like standard Cumulus web tags to me (
> http://wiki.sandaysoft.com/a/Webtags).
>
> Gary
>

right you are, gary!  but i'm still not clear what cumulus wind rose data 
actually look like.  examples would help, with corner cases.

imho, the weewx-crt extension is getting a bit too complicated.  it would 
be better if there were a CumulusWebTagsEngine that could be used in a 
weewx-crt extension to emit the realtime.txt, realmore.txt, and whatever 
else someone might create that emits cumulus web tags.  and it could also 
be used in a CumulusGenerator that could be used like CheetahGenerator but 
with cumulus syntax instead of cheetah syntax.

as a quick way to do what chote wants, maybe use CheetahGenerator to emit 
the realmore.txt (since once per archive interval should be fast enough for 
those data), and the weewx-crt extension to emit the realtime.txt (since 
those can be LOOP and emitted much more frequently).

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: crt extension has been updated

[gjr80]

Just look like standard Cumulus web tags to me 
(http://wiki.sandaysoft.com/a/Webtags).

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: crt extension has been updated

[mwall]

On Thursday, December 28, 2017 at 10:25:18 PM UTC-5, Chotechai Piyavongsiri 
wrote:
>
> mwall...thanks a lot for this useful extensions. Do you have any idea 
> about producing a realmore.txt file mentioned in this forum?
> http://sandaysoft.com/forum/viewtopic.php?f=26=16398
>

hello chotechai!

this is the first time i've heard of 'realmore.txt'

apparently it contains:

<#pressYL> <#TpressYL> <#pressYH> <#TpressYH> <#pressTL> <#TpressTL> 
<#pressTH>
<#TpressTH> <#WindRoseData> <#realtimeinterval> 

if you can provide a definition for each field (we need to know the set of 
possible units for each field too!) as well as at least one example of 
actual output for each field (a few sample realmore.txt files would be 
best), then we might be able to add 'realmore.txt' to the list of files 
output by the weewx-crt extension.

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: crt extension has been updated

[Chotechai Piyavongsiri]

mwall...thanks a lot for this useful extensions. Do you have any idea about 
producing a realmore.txt file mentioned in this forum?
http://sandaysoft.com/forum/viewtopic.php?f=26=16398

On Wednesday, April 13, 2016 at 2:30:17 PM UTC+7, mwall wrote:
>
> the cumulus realtime (crt) extension has been around awhile, but recently 
> received a major update:
>
> https://github.com/weewx/weewx/wiki/crt
>
> this extension should make it trivial to use weewx with any weather 
> template that gets its data from a cumulus 'realtime.txt' file.  that 
> includes meteotemplate, leuven, saratoga, and weatherbyyou.
>
> thanks to gary for extensive testing.
>
> we thought about an extension that would output weather display 
> 'customXXX' files, but pretty much anything that works with wd customXXX 
> works with cumulus realtime.
>
> from the changelog:
>
> 0.18 10apr2016
> * graceful recovery when no forecast binding defined
> * refactor unit conversions to support per-observation unit specifications
> * more fixes from gary for better unit conversions and cumulus compliance
>
> 0.17 28mar2016
> * lots of fixes from gary roderick:
> * Introduced StrictVersion to more easily compare weewx version numbers.
> * crt now requires weewx 3.2.0 or later.
> * Fixed UNITS_RAIN typo, weewx rain unit is 'inch' not 'in'.
> * Added UNITS_ALT to facilitate cloudbase units lookup.
> * Replaced knottoBeaufort() with call to weewx.wxformulas.beaufort().
> * cloudbase, maxSolarRad, humidex, appTemp and heatindex are now included 
> in
>   weewx loop packets so removed manual calculations of these obs.
> * Side benefit of using maxSolarRad from loop packet means crt no longer
>   crashes if pyephem is not installed.
> * Reworked calcDaylightHours() to use Almanac objects
>   rather than Sun object calcs so that additional accuracy of pyephem can 
> be
>   taken advantage of if installed.
> * Weewx is now windrun aware though windrun is not included in loop 
> packets.
> * Reworked windrun unit conversions to make use of weewx API.
> * Sunshine hours calculations remain flawed but it now uses an Almanac
>   object as the basis for its calculation.
> * radiation had no formatting applied resulting in numerous decimal places
>   in realtime.txt, reduced that to 1 decimal place (probably only an issue
>   with simulator).
> * Minor changes to some packet names to reflect new fields now in weewx 
> loop
>   packet eg cloud_base v cloudbase.
> * Found that crt would fail if used with an empty archive (could not get db
>   US units to do conversion so _cvt() method would cause a failure). Was a
>   vicious circle; if used with an empty archive crt would cause weewx to 
> fail
>   and because weewx failed you could never get any records into the 
> archive.
>   The only work around was to not install/run crt on an empty archive. I
>   reworked the _cvt() method to return None is the archive has no records,
>   gives a lot of NULLs in the output until you get records in the archive 
> then
>   it operates as normal.
> * Did some further comparison of Cumulus realtime.txt wiki page and Cumulus
>   Webtags wiki page. By cross referencing the Webtags between the wiki 
> pages
>   it was possible to confirm details of a number of realtime.txt fields:
>- field 6 (wind avg speed)and field 47 (wind avg dir). Averaging period 
> is
>  not mentioned directly although the corresponding Webtags use 10 
> minute
>  averages by default. This confirms current crt settings.
>- field 52 (avg_wind_dir). This is the compass direction of the 10 min
>  average wind bearing, changed code to reflect this.
>- Cumulus uses wind direction of 0+ to 360 with 0 indicating calm.
> * Reworked calcAvgWindDir() and calc10MinAvgWindDir() to return None or
>   0+ to 360 rather than None or 0 to 360-.
> * Given the way Cumulus represents wind direction introduced
>   data['cumulus_windDir'] mainly to differentiate from/not overwrite
>   data['windDir']
> * Confirmed that month and year rain are month to date and year to date
>   values from 1st of month and year respectively. Removed 2 related FIXME
>   comments.
> * field 11 is listed as in the realtime.txt wiki page as 'barometer (The
>   sea level pressure)' with the equivalent webtag of #press. #press is 
> listed
>   in the webtags wiki page as 'The sea level pressure'. These are 
> completely
>   consistent with using weewx 'barometer'. Removed the comment re 
> uncertainty
>   over what pressure is specified in realtime.txt.
> * Observed a number of real world live realtime.txt files and confirmed 
> that:
>- realtime.txt uses local time. Reworked date/time to use local time
>  throughout.
>- None/NULL handling is not specified in Cumulus realtime.txt wiki but
>  observation of a number of realtime sites showed that when there is no
>  wind, wind speeds are set to 0 not NULL. Introduced 'none' setting in
>  weewx.conf[CumulusRealTime] to allow user specification of what
> 

Re: [weewx-user] Re: twitter extension: Able to insert a return/new line?

[Thomas Keffer]

You're not making it easy!

Make sure you're showing us the correct format and the exact output that
goes along with it. Better yet, cut and paste the whole twitter section of
your weewx.conf.

Python is case-sensitive, so you definitely want dayRain.

-tk

On Thu, Dec 28, 2017 at 5:24 PM, Chris Alemany  wrote:

> Apologies I had removed it temporarily it is supposed to be before
> Rain Rate.
>
> format = "{station} {dateTime:%H:%M %b %d %Y}: T: {outTemp:%.1f}ºC D:
> {dewpoint:%.1f}ºC W: {windDir:ORD} {windSpeed:%.1f}kph gusting to
> {windGust:%.1f}kph H: {outHumidity:%.0f}% P: {barometer:%.2f}hPa Rain
> {dayrain:%.1f}mm Rain Rate: {rainRate:%.1f}mm/hr Chill:{windchill:%.1f}ºC
> HIndex:{heatindex:%.1f}ºC Solar: {radiation:%.0f}W/m2 UV: {UV:%.0f}
> #PortAlberni https://www.alberniweather.ca https://www.youtube.com/
> alberniweather"
>
> On Thursday, December 28, 2017 at 5:07:45 PM UTC-8, Tom Keffer wrote:
>>
>> format = "{station} {dateTime:%H:%M %b %d %Y}: T: {outTemp:%.1f}ºC D:
>>> {dewpoint:%.1f}ºC W: {windDir:ORD} {windSpeed:%.1f}kph gusting to
>>> {windGust:%.1f}kph H: {outHumidity:%.0f}% P: {barometer:%.2f}hPa Rain Rate:
>>> {rainRate:%.1f}mm/hr Chill:{windchill:%.1f}ºC HIndex:{heatindex:%.1f}ºC
>>> Solar: {radiation:%.0f}W/m2 UV: {UV:%.0f} #PortAlberni https://www.alber
>>> niweather.cahttps://www.youtube.com/alberniweather;
>>
>>
>> I'm not seeing dayrain (or dayRain) in your format at all. Where is it
>> coming from?
>>
>> -tk
>>
>> On Thu, Dec 28, 2017 at 4:48 PM, Chris Alemany  wrote:
>>
>>> This is the format string:
>>>
>>> format = "{station} {dateTime:%H:%M %b %d %Y}: T: {outTemp:%.1f}ºC D:
>>> {dewpoint:%.1f}ºC W: {windDir:ORD} {windSpeed:%.1f}kph gusting to
>>> {windGust:%.1f}kph H: {outHumidity:%.0f}% P: {barometer:%.2f}hPa Rain Rate:
>>> {rainRate:%.1f}mm/hr Chill:{windchill:%.1f}ºC HIndex:{heatindex:%.1f}ºC
>>> Solar: {radiation:%.0f}W/m2 UV: {UV:%.0f} #PortAlberni
>>> https://www.alberniweather.ca https://www.youtube.com/alberniweather;
>>>
>>> This is what twitter output looks like (same for dayRain or dayrain as
>>> variable):
>>>
>>> Hourly Auto-Tweet 16:45 Dec 28 2017: T: 2.4ºC D: 2.4ºC W: * 0.0kph
>>> gusting to 0.0kph H: 100% P: 1013.07hPa Rain: {dayrain:%.1f}mm Rain Rate:
>>> 0.0mm/hr Chill:2.4ºC HIndex:2.4ºC Solar: 0W/m2 UV: 0 #PortAlberni
>>>  https://www.
>>> alberniweather.ca  
>>>
>>> and
>>>
>>> Hourly Auto-Tweet 16:40 Dec 28 2017: T: 2.5ºC D: 2.5ºC W: * 0.0kph
>>> gusting to 0.0kph H: 100% P: 1013.04hPa Rain: {dayRain:%.1f}mm Rain Rate:
>>> 0.0mm/hr Chill:2.5ºC HIndex:2.5ºC Solar: 0W/m2 UV: 0 #PortAlberni
>>>  https://www.
>>> alberniweather.ca  
>>>
>>>
>>> On Thursday, December 28, 2017 at 4:45:42 PM UTC-8, Chris Alemany wrote:

 no improvement. :(

 On Thursday, December 28, 2017 at 4:19:58 PM UTC-8, mwall wrote:
>
> On Thursday, December 28, 2017 at 6:52:36 PM UTC-5, Chris Alemany
> wrote:
>>
>>
>> I used dayrain without success.
>>
>
> at line 267 of twitter.py change this:
>
> def process_record(self, record, dummy_manager):
>
> if self.unit_system is not None:
>
> record = weewx.units.to_std_system(record,
> self.unit_system)
>
> record['station'] = self.station
>
> to this:
>
> def process_record(self, record, mgr):
>
> record = self.get_record(record, mgr)
>
> if self.unit_system is not None:
>
> record = weewx.units.to_std_system(record,
> self.unit_system)
>
> record['station'] = self.station
>
> then restart weewx.
>
> 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+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [weewx-user] Re: twitter extension: Able to insert a return/new line?

[Chris Alemany]

Apologies I had removed it temporarily it is supposed to be before Rain 
Rate.

format = "{station} {dateTime:%H:%M %b %d %Y}: T: {outTemp:%.1f}ºC D: 
{dewpoint:%.1f}ºC W: {windDir:ORD} {windSpeed:%.1f}kph gusting to 
{windGust:%.1f}kph H: {outHumidity:%.0f}% P: {barometer:%.2f}hPa Rain 
{dayrain:%.1f}mm Rain Rate: {rainRate:%.1f}mm/hr Chill:{windchill:%.1f}ºC 
HIndex:{heatindex:%.1f}ºC Solar: {radiation:%.0f}W/m2 UV: {UV:%.0f} 
#PortAlberni https://www.alberniweather.ca 
https://www.youtube.com/alberniweather;

On Thursday, December 28, 2017 at 5:07:45 PM UTC-8, Tom Keffer wrote:
>
> format = "{station} {dateTime:%H:%M %b %d %Y}: T: {outTemp:%.1f}ºC D: 
>> {dewpoint:%.1f}ºC W: {windDir:ORD} {windSpeed:%.1f}kph gusting to 
>> {windGust:%.1f}kph H: {outHumidity:%.0f}% P: {barometer:%.2f}hPa Rain Rate: 
>> {rainRate:%.1f}mm/hr Chill:{windchill:%.1f}ºC HIndex:{heatindex:%.1f}ºC 
>> Solar: {radiation:%.0f}W/m2 UV: {UV:%.0f} #PortAlberni 
>> https://www.alberniweather.cahttps://www.youtube.com/alberniweather;
>
>
> I'm not seeing dayrain (or dayRain) in your format at all. Where is it 
> coming from?
>
> -tk
>
> On Thu, Dec 28, 2017 at 4:48 PM, Chris Alemany  > wrote:
>
>> This is the format string:
>>
>> format = "{station} {dateTime:%H:%M %b %d %Y}: T: {outTemp:%.1f}ºC D: 
>> {dewpoint:%.1f}ºC W: {windDir:ORD} {windSpeed:%.1f}kph gusting to 
>> {windGust:%.1f}kph H: {outHumidity:%.0f}% P: {barometer:%.2f}hPa Rain Rate: 
>> {rainRate:%.1f}mm/hr Chill:{windchill:%.1f}ºC HIndex:{heatindex:%.1f}ºC 
>> Solar: {radiation:%.0f}W/m2 UV: {UV:%.0f} #PortAlberni 
>> https://www.alberniweather.ca https://www.youtube.com/alberniweather;
>>
>> This is what twitter output looks like (same for dayRain or dayrain as 
>> variable):
>>
>> Hourly Auto-Tweet 16:45 Dec 28 2017: T: 2.4ºC D: 2.4ºC W: * 0.0kph 
>> gusting to 0.0kph H: 100% P: 1013.07hPa Rain: {dayrain:%.1f}mm Rain Rate: 
>> 0.0mm/hr Chill:2.4ºC HIndex:2.4ºC Solar: 0W/m2 UV: 0 #PortAlberni 
>>  https://www.
>> alberniweather.ca  
>>
>> and
>>
>> Hourly Auto-Tweet 16:40 Dec 28 2017: T: 2.5ºC D: 2.5ºC W: * 0.0kph 
>> gusting to 0.0kph H: 100% P: 1013.04hPa Rain: {dayRain:%.1f}mm Rain Rate: 
>> 0.0mm/hr Chill:2.5ºC HIndex:2.5ºC Solar: 0W/m2 UV: 0 #PortAlberni 
>>  https://www.
>> alberniweather.ca  
>>
>>
>> On Thursday, December 28, 2017 at 4:45:42 PM UTC-8, Chris Alemany wrote:
>>>
>>> no improvement. :(
>>>
>>> On Thursday, December 28, 2017 at 4:19:58 PM UTC-8, mwall wrote:

 On Thursday, December 28, 2017 at 6:52:36 PM UTC-5, Chris Alemany wrote:
>
>
> I used dayrain without success.
>

 at line 267 of twitter.py change this:

 def process_record(self, record, dummy_manager):

 if self.unit_system is not None:

 record = weewx.units.to_std_system(record, 
 self.unit_system)

 record['station'] = self.station

 to this:

 def process_record(self, record, mgr):

 record = self.get_record(record, mgr)

 if self.unit_system is not None:

 record = weewx.units.to_std_system(record, 
 self.unit_system)

 record['station'] = self.station

 then restart weewx.

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

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

Re: [weewx-user] Re: twitter extension: Able to insert a return/new line?

[Thomas Keffer]

>
> format = "{station} {dateTime:%H:%M %b %d %Y}: T: {outTemp:%.1f}ºC D:
> {dewpoint:%.1f}ºC W: {windDir:ORD} {windSpeed:%.1f}kph gusting to
> {windGust:%.1f}kph H: {outHumidity:%.0f}% P: {barometer:%.2f}hPa Rain Rate:
> {rainRate:%.1f}mm/hr Chill:{windchill:%.1f}ºC HIndex:{heatindex:%.1f}ºC
> Solar: {radiation:%.0f}W/m2 UV: {UV:%.0f} #PortAlberni
> https://www.alberniweather.cahttps://www.youtube.com/alberniweather;


I'm not seeing dayrain (or dayRain) in your format at all. Where is it
coming from?

-tk

On Thu, Dec 28, 2017 at 4:48 PM, Chris Alemany  wrote:

> This is the format string:
>
> format = "{station} {dateTime:%H:%M %b %d %Y}: T: {outTemp:%.1f}ºC D:
> {dewpoint:%.1f}ºC W: {windDir:ORD} {windSpeed:%.1f}kph gusting to
> {windGust:%.1f}kph H: {outHumidity:%.0f}% P: {barometer:%.2f}hPa Rain Rate:
> {rainRate:%.1f}mm/hr Chill:{windchill:%.1f}ºC HIndex:{heatindex:%.1f}ºC
> Solar: {radiation:%.0f}W/m2 UV: {UV:%.0f} #PortAlberni
> https://www.alberniweather.ca https://www.youtube.com/alberniweather;
>
> This is what twitter output looks like (same for dayRain or dayrain as
> variable):
>
> Hourly Auto-Tweet 16:45 Dec 28 2017: T: 2.4ºC D: 2.4ºC W: * 0.0kph gusting
> to 0.0kph H: 100% P: 1013.07hPa Rain: {dayrain:%.1f}mm Rain Rate: 0.0mm/hr
> Chill:2.4ºC HIndex:2.4ºC Solar: 0W/m2 UV: 0 #PortAlberni
>  https://www.
> alberniweather.ca  
>
> and
>
> Hourly Auto-Tweet 16:40 Dec 28 2017: T: 2.5ºC D: 2.5ºC W: * 0.0kph gusting
> to 0.0kph H: 100% P: 1013.04hPa Rain: {dayRain:%.1f}mm Rain Rate: 0.0mm/hr
> Chill:2.5ºC HIndex:2.5ºC Solar: 0W/m2 UV: 0 #PortAlberni
>  https://www.
> alberniweather.ca  
>
>
> On Thursday, December 28, 2017 at 4:45:42 PM UTC-8, Chris Alemany wrote:
>>
>> no improvement. :(
>>
>> On Thursday, December 28, 2017 at 4:19:58 PM UTC-8, mwall wrote:
>>>
>>> On Thursday, December 28, 2017 at 6:52:36 PM UTC-5, Chris Alemany wrote:


 I used dayrain without success.

>>>
>>> at line 267 of twitter.py change this:
>>>
>>> def process_record(self, record, dummy_manager):
>>>
>>> if self.unit_system is not None:
>>>
>>> record = weewx.units.to_std_system(record, self.unit_system)
>>>
>>> record['station'] = self.station
>>>
>>> to this:
>>>
>>> def process_record(self, record, mgr):
>>>
>>> record = self.get_record(record, mgr)
>>>
>>> if self.unit_system is not None:
>>>
>>> record = weewx.units.to_std_system(record, self.unit_system)
>>>
>>> record['station'] = self.station
>>>
>>> then restart weewx.
>>>
>>> m
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[weewx-user] Re: twitter extension: Able to insert a return/new line?

[Chris Alemany]

This is the format string:

format = "{station} {dateTime:%H:%M %b %d %Y}: T: {outTemp:%.1f}ºC D: 
{dewpoint:%.1f}ºC W: {windDir:ORD} {windSpeed:%.1f}kph gusting to 
{windGust:%.1f}kph H: {outHumidity:%.0f}% P: {barometer:%.2f}hPa Rain Rate: 
{rainRate:%.1f}mm/hr Chill:{windchill:%.1f}ºC HIndex:{heatindex:%.1f}ºC 
Solar: {radiation:%.0f}W/m2 UV: {UV:%.0f} #PortAlberni 
https://www.alberniweather.ca https://www.youtube.com/alberniweather;

This is what twitter output looks like (same for dayRain or dayrain as 
variable):

Hourly Auto-Tweet 16:45 Dec 28 2017: T: 2.4ºC D: 2.4ºC W: * 0.0kph gusting 
to 0.0kph H: 100% P: 1013.07hPa Rain: {dayrain:%.1f}mm Rain Rate: 0.0mm/hr 
Chill:2.4ºC HIndex:2.4ºC Solar: 0W/m2 UV: 0 #PortAlberni 
 https://www.
alberniweather.ca  

and

Hourly Auto-Tweet 16:40 Dec 28 2017: T: 2.5ºC D: 2.5ºC W: * 0.0kph gusting 
to 0.0kph H: 100% P: 1013.04hPa Rain: {dayRain:%.1f}mm Rain Rate: 0.0mm/hr 
Chill:2.5ºC HIndex:2.5ºC Solar: 0W/m2 UV: 0 #PortAlberni 
 https://www.
alberniweather.ca  

On Thursday, December 28, 2017 at 4:45:42 PM UTC-8, Chris Alemany wrote:
>
> no improvement. :(
>
> On Thursday, December 28, 2017 at 4:19:58 PM UTC-8, mwall wrote:
>>
>> On Thursday, December 28, 2017 at 6:52:36 PM UTC-5, Chris Alemany wrote:
>>>
>>>
>>> I used dayrain without success.
>>>
>>
>> at line 267 of twitter.py change this:
>>
>> def process_record(self, record, dummy_manager):
>>
>> if self.unit_system is not None:
>>
>> record = weewx.units.to_std_system(record, self.unit_system)
>>
>> record['station'] = self.station
>>
>> to this:
>>
>> def process_record(self, record, mgr):
>>
>> record = self.get_record(record, mgr)
>>
>> if self.unit_system is not None:
>>
>> record = weewx.units.to_std_system(record, self.unit_system)
>>
>> record['station'] = self.station
>>
>> then restart weewx.
>>
>> 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: twitter extension: Able to insert a return/new line?

[Chris Alemany]

no improvement. :(

On Thursday, December 28, 2017 at 4:19:58 PM UTC-8, mwall wrote:
>
> On Thursday, December 28, 2017 at 6:52:36 PM UTC-5, Chris Alemany wrote:
>>
>>
>> I used dayrain without success.
>>
>
> at line 267 of twitter.py change this:
>
> def process_record(self, record, dummy_manager):
>
> if self.unit_system is not None:
>
> record = weewx.units.to_std_system(record, self.unit_system)
>
> record['station'] = self.station
>
> to this:
>
> def process_record(self, record, mgr):
>
> record = self.get_record(record, mgr)
>
> if self.unit_system is not None:
>
> record = weewx.units.to_std_system(record, self.unit_system)
>
> record['station'] = self.station
>
> then restart weewx.
>
> 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: twitter extension: Able to insert a return/new line?

[mwall]

On Thursday, December 28, 2017 at 6:52:36 PM UTC-5, Chris Alemany wrote:
>
>
> I used dayrain without success.
>

at line 267 of twitter.py change this:

def process_record(self, record, dummy_manager):

if self.unit_system is not None:

record = weewx.units.to_std_system(record, self.unit_system)

record['station'] = self.station

to this:

def process_record(self, record, mgr):

record = self.get_record(record, mgr)

if self.unit_system is not None:

record = weewx.units.to_std_system(record, self.unit_system)

record['station'] = self.station

then restart weewx.

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: twitter extension: Able to insert a return/new line?

[Chris Alemany]

Hmm.  
On the variabiles:

I am using the default binding (archive).  I don't need the frequency of 
loop, though, for debugging sake I should mention that when I have tried 
out binding=loop, weewx fails to start. I have not looked into why that 
might be as it's not part of my goal.

This is what weewx reports from the Vantage raw stream:

REC:2017-12-28 12:50:00 PST (1514494200) altimeter: 29.8871528188, 
appTemp: 32.1224062668, barometer: 29.901, cloudbase: 101.0, 
consBatteryVoltage: 4.62, dateTime: 1514494200, dayET: 0.0, dayRain: 0.75, 
dewpoint: 35.2, ET: 0.0, extraAlarm1: 0.0, extraAlarm2: 0.0, extraAlarm3: 
0.0, extraAlarm4: 0.0, extraAlarm5: 0.0, extraAlarm6: 0.0, extraAlarm7: 
0.0, extraAlarm8: 0.0, forecastIcon: 7.0, forecastRule: 93, heatindex: 
35.2, highOutTemp: 35.2, highRadiation: 58.0, highUV: 0.0, humidex: 35.2, 
inDewpoint: 40.2825325477, inHumidity: 38.0, insideAlarm: 0.0, inTemp: 
66.7, interval: 5, leafWet4: 0.0, lowOutTemp: 35.1, maxSolarRad: 
200.328662136, monthET: 0.22, monthRain: 3.13, outHumidity: 100.0, 
outsideAlarm1: 0.0, outsideAlarm2: 0.0, outTemp: 35.2, outTempDay: 35.2, 
outTempNight: None, pressure: 29.7870205707, radiation: 48.0, rain: 0.0, 
rainAlarm: 0.0, rainRate: 0.0, rxCheckPercent: 97.375, soilLeafAlarm1: 0.0, 
soilLeafAlarm2: 0.0, soilLeafAlarm3: 0.0, soilLeafAlarm4: 0.0, stormRain: 
0.94, stormStart: 1514188800.0, sunrise: 1514477640.0, sunset: 
1514507280.0, trendIcon: -60.0, txBatteryStatus: 0, usUnits: 1, UV: 0.0, 
windchill: 35.2, windDir: None, windGust: 0.0, windGustDir: None, windrun: 
0.000566893424036, windSpeed: 0.0, windSpeed10: 0.0, yearET: 32.26, 
yearRain: 28.79


LOOP:   2017-12-28 12:50:27 PST (1514494227) altimeter: 29.8871528188, 
appTemp: 32.1224062668, barometer: 29.901, cloudbase: 101.0, 
consBatteryVoltage: 4.62, dateTime: 1514494227, dayET: 0.0, dayRain: 0.75, 
dewpoint: 35.2, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
extraAlarm8: 0, forecastIcon: 7, forecastRule: 93, heatindex: 35.2, 
humidex: 35.2, inDewpoint: 40.2825325477, inHumidity: 38.0, insideAlarm: 0, 
inTemp: 66.7, leafWet4: 0.0, maxSolarRad: 200.155823598, monthET: 0.22, 
monthRain: 3.13, outHumidity: 100.0, outsideAlarm1: 0, outsideAlarm2: 0, 
outTemp: 35.2, outTempDay: 35.2, outTempNight: None, pressure: 
29.7870205707, radiation: 62.0, rain: 0.0, rainAlarm: 0, rainRate: 0.0, 
soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, 
stormRain: 0.94, stormStart: 1514188800, sunrise: 1514477640, sunset: 
1514507280, trendIcon: -60, txBatteryStatus: 0, usUnits: 1, UV: 0.0, 
windchill: 35.2, windDir: None, windGust: 0.0, windGustDir: None, 
windSpeed: 0.0, windSpeed10: 0.0, yearET: 32.26, yearRain: 28.79


I used dayrain without success.


On the newline issue.  No luck with either of the escape characters, which 
I had tried before, or the unicode.


I have also tried a few techniques for getting new lines into code listed 
here:

https://www.smallsurething.com/multi-line-strings-in-python/


Unfortunately, no success.


Chris




On Thursday, December 28, 2017 at 1:37:19 PM UTC-8, mwall wrote:
>
>
>
> On Thursday, December 28, 2017 at 4:24:05 PM UTC-5, Chris Alemany wrote:
>>
>> Also, any ideas on how to pass a new line within the format option so that
>> Output
>> on
>> Twitter
>> can look
>> more
>> like this?
>>
>
> use a newline?  maybe:
>
> format = "first line\\nsecond line\\nthird line"
>
> or if that does not work, try to find the unicode character for newline 
> and stick that into your string
>
> 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] weewx via magic-mirror ?

[vince]

I ran across a posting in /r/raspberry_pi from a guy who did a Magic Mirror 
based on a module somebody wrote to track e-currency prices.  While I have 
no interest in that specifically, I thought the idea of Magic Mirror as a 
software 'carrier' so to speak looked pretty slick and easy to do.  Has 
anybody thought of trying to put up weewx data similarly to a Magic Mirror 
?   Any interest in such a thing ?

His example image is at https://imgur.com/a/5Q36m FWIW, original article 
is 
https://www.reddit.com/r/dogecoin/comments/7mj95a/raspberry_pi_3_7_inch_screen_live_doge_tracker_i/

-- 
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: twitter extension: Able to insert a return/new line?

[mwall]

On Thursday, December 28, 2017 at 4:24:05 PM UTC-5, Chris Alemany wrote:
>
> Also, any ideas on how to pass a new line within the format option so that
> Output
> on
> Twitter
> can look
> more
> like this?
>

use a newline?  maybe:

format = "first line\\nsecond line\\nthird line"

or if that does not work, try to find the unicode character for newline and 
stick that into your string

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: twitter extension: Able to insert a return/new line?

[mwall]

On Thursday, December 28, 2017 at 4:12:38 PM UTC-5, Chris Alemany wrote:
>
>
> Whoa. OK, that was awesome.
>
> However, if I put in 'dayRain' (or dayrain) as it is delivered within the 
> LOOP or REC packets from weewx within my format command for the twitter 
> extension, it just spits out:
>
>  Rain Today: {dayRain:%.1f}mm  
>
> rather than actually parsing the variable.  
>
> However, other variables, like outTemp or heatindex or windchill seem to 
> match up and work just fine.  So I am definitely missing a crucial step 
> here.
>

are the observations you want in REC or LOOP?

use the 'binding' option to the weewx-twitter extension to choose which you 
want to tweet

if that does not get what you want, then you'll have to modify the 
twitter.py code to make additional database queries (see other restful 
extensions in restx.py for examples of how to do 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: twitter extension: Able to insert a return/new line?

[Chris Alemany]

Also, any ideas on how to pass a new line within the format option so that
Output
on
Twitter
can look
more
like this?

On Thursday, December 28, 2017 at 1:12:38 PM UTC-8, Chris Alemany wrote:
>
>
>
> On Thursday, December 28, 2017 at 12:38:55 PM UTC-8, mwall wrote:
>>
>> On Thursday, December 28, 2017 at 3:24:00 PM UTC-5, Chris Alemany wrote:
>>>
>>>
>>> On Thursday, December 28, 2017 at 11:58:22 AM UTC-8, mwall wrote:


 but the fastest and most accurate way is rather pythonic: just do it! 
  run weewx directly and see what it spits out in each LOOP and REC 
 dictionary.

>>>
>>> I sense this is the answer I am looking for (Luke lol) but as to how I 
>>> might accomplish that... my use of the pythonic-force is weak.
>>>
>>> Help me Obi-MWall-Kenobi you're my only hope. 
>>>
>>
>>
>> here you go:
>>
>> http://weewx.com/docs/usersguide.htm#running 
>>
>> m
>>
>
> Whoa. OK, that was awesome.
>
> However, if I put in 'dayRain' (or dayrain) as it is delivered within the 
> LOOP or REC packets from weewx within my format command for the twitter 
> extension, it just spits out:
>
>  Rain Today: {dayRain:%.1f}mm  
>
> rather than actually parsing the variable.  
>
> However, other variables, like outTemp or heatindex or windchill seem to 
> match up and work just fine.  So I am definitely missing a crucial step 
> here.
>
> Chris
>

-- 
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: twitter extension: Able to insert a return/new line?

[Chris Alemany]

On Thursday, December 28, 2017 at 12:38:55 PM UTC-8, mwall wrote:
>
> On Thursday, December 28, 2017 at 3:24:00 PM UTC-5, Chris Alemany wrote:
>>
>>
>> On Thursday, December 28, 2017 at 11:58:22 AM UTC-8, mwall wrote:
>>>
>>>
>>> but the fastest and most accurate way is rather pythonic: just do it! 
>>>  run weewx directly and see what it spits out in each LOOP and REC 
>>> dictionary.
>>>
>>
>> I sense this is the answer I am looking for (Luke lol) but as to how I 
>> might accomplish that... my use of the pythonic-force is weak.
>>
>> Help me Obi-MWall-Kenobi you're my only hope. 
>>
>
>
> here you go:
>
> http://weewx.com/docs/usersguide.htm#running 
>
> m
>

Whoa. OK, that was awesome.

However, if I put in 'dayRain' (or dayrain) as it is delivered within the 
LOOP or REC packets from weewx within my format command for the twitter 
extension, it just spits out:

 Rain Today: {dayRain:%.1f}mm  

rather than actually parsing the variable.  

However, other variables, like outTemp or heatindex or windchill seem to 
match up and work just fine.  So I am definitely missing a crucial step 
here.

Chris

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

Re: [weewx-user] Re: Original Vantage Pro, connected via serial-ethernet converter?

[vince]

On Thursday, December 28, 2017 at 11:44:23 AM UTC-8, Tom Keffer wrote:
>
> What happened to the other 3?
>
> -tk
>
> On Thu, Dec 28, 2017 at 11:14 AM, Chris Alemany  > wrote:
>
>> My welcome has been similar :)
>>
>> On the 15 years or so of data from wview. I successfully imported 12 
>> years of data. So it's possible! :)
>>
>>
>>
what he said !

heck you might find somebody here who would try to convert it for you just 
for the adventure of it..
 

-- 
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: twitter extension: Able to insert a return/new line?

[mwall]

On Thursday, December 28, 2017 at 3:24:00 PM UTC-5, Chris Alemany wrote:
>
>
> On Thursday, December 28, 2017 at 11:58:22 AM UTC-8, mwall wrote:
>>
>>
>> but the fastest and most accurate way is rather pythonic: just do it! 
>>  run weewx directly and see what it spits out in each LOOP and REC 
>> dictionary.
>>
>
> I sense this is the answer I am looking for (Luke lol) but as to how I 
> might accomplish that... my use of the pythonic-force is weak.
>
> Help me Obi-MWall-Kenobi you're my only hope. 
>


here you go:

http://weewx.com/docs/usersguide.htm#running 

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: twitter extension: Able to insert a return/new line?

[Chris Alemany]

On Thursday, December 28, 2017 at 11:58:22 AM UTC-8, mwall wrote:
>
>
>
> but the fastest and most accurate way is rather pythonic: just do it!  run 
> weewx directly and see what it spits out in each LOOP and REC dictionary.
>
> m
>
>
I sense this is the answer I am looking for (Luke lol) but as to how I 
might accomplish that... my use of the pythonic-force is weak.

Help me Obi-MWall-Kenobi you're my only hope. 

:) 

-- 
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: twitter extension: Able to insert a return/new line?

[mwall]

On Thursday, December 28, 2017 at 2:19:02 PM UTC-5, Chris Alemany wrote:
>
> Haha. I suspect that 'server uptime' variable is optimistic. :)
>
> Maybe this is a more general question than just on this extension.
>
> How do I know what weewx values are available to the extension (or any 
> extension for that matter?).  For example, what is the "rain" variable 
> actually returning in twitter.  It is not the daily rain sum... how can I 
> know what is what and what is available for display?
>
>>
>>
the set of observations depends on what hardware is running and what 
services are running.

start with the hardware docs:

http://weewx.com/docs/hardware.htm

see the 'station data' section for your hardware.

then see the docs for the services you are running.  for example, 
StdWXCalculate adds a few:

http://weewx.com/docs/usersguide.htm#StdWXCalculate

but the fastest and most accurate way is rather pythonic: just do it!  run 
weewx directly and see what it spits out in each LOOP and REC dictionary.

m

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

Re: [weewx-user] Re: Original Vantage Pro, connected via serial-ethernet converter?

[Thomas Keffer]

What happened to the other 3?

-tk

On Thu, Dec 28, 2017 at 11:14 AM, Chris Alemany  wrote:

> My welcome has been similar :)
>
> On the 15 years or so of data from wview. I successfully imported 12 years
> of data. So it's possible! :)
>
> Good luck.
> Chris
>
>
> On Wednesday, December 27, 2017 at 8:56:51 PM UTC-8, loonsailor wrote:
>>
>> Thanks, that did it!  Actually, I'm not sure whether it was the "port" or
>> the "tcp_port" parameter in weewx.conf, so I changed both.  I'm up and
>> running!  It barfed on importing my 15 years or so of data from wview, but
>> that's a problem for another day, and I won't have a chance to dig into it
>> for a couple of weeks.
>>
>> Thanks again for all the help!  What a nice way to enter a new community.
>>
>> On Wednesday, December 27, 2017 at 6:16:56 PM UTC-8, Tom Keffer wrote:
>>>
>>> The "host" line should just  be the IP address: no port.
>>>
>>> The "port" line should be the port.
>>>
>>> you're combining the two as "host".
>>>
>>> So, you want
>>>
>>> [Vantage]
>>>   type = ethernet
>>>   host = 192.168.198.202
>>>   port = 3001
>>>
>>> -tk
>>>
>>> On Wed, Dec 27, 2017 at 6:05 PM, 'loonsailor' via weewx-user <
>>> weewx...@googlegroups.com> wrote:
>>>
 Thanks for this.  I was really excited.  Tried it, but it doesn't
 work.  Specifically, here is the log file:

 Dec 27 18:00:32 ubu-mini-weather weewx[10917]: engine: Loading station
 type Vantage (weewx.drivers.vantage)
 Dec 27 18:00:32 ubu-mini-weather weewx[10902]:...done.
 Dec 27 18:00:32 ubu-mini-weather systemd[1]: Started LSB: weewx
 weather system.
 Dec 27 18:00:32 ubu-mini-weather weewx[10917]: vantage: Socket error
 while opening port 2 to ethernet host 192.168.198.202.
 Dec 27 18:00:32 ubu-mini-weather weewx[10917]: import of driver failed:
 [Errno 111] Connection refused ()
 Dec 27 18:00:32 ubu-mini-weather weewx[10917]: engine: Unable to load
 driver: [Errno 111] Connection refused
 Dec 27 18:00:32 ubu-mini-weather weewx[10917]:   Exiting...



 The serial port converter wants to use socket 3001.  Worked fine in
 wview, so I chaged the socket address in weewx.conf to be
 192.168.198.202:3001.  Then, I get the following:

 Dec 27 17:31:29 ubu-mini-weather weewx[10673]: engine: Loading station
 type Vantage (weewx.drivers.vantage)
 Dec 27 17:31:29 ubu-mini-weather weewx[10673]: vantage: Socket error
 while opening port 2 to ethernet host 192.168.198.202:3001.
 Dec 27 17:31:29 ubu-mini-weather weewx[10673]: import of driver failed:
 [Errno -2] Name or service not known ()
 Dec 27 17:31:29 ubu-mini-weather weewx[10673]: engine: Unable to load
 driver: [Errno -2] Name or service not known
 Dec 27 17:31:29 ubu-mini-weather weewx[10658]:...done.

 So, I'm not sure how to tell it to open the correct socket on the
 lantronix.  I'll have a look at the code, but any ideas?

 Thanks

 On Wednesday, December 27, 2017 at 11:03:43 AM UTC-8, Chris Alemany
 wrote:

> Hi loonsailor,
>
> I have been using a serial to ethernet interface for years as well
> (with the wview software).  I moved to weewx recently and after some
> digging realized the support for serial-ethernet is there, just not
> documented up front.
>
> Just go through the regular install process and when you get into the
> weewx.conf file below is what I am using for my Serial-Ethernet bridge.
> Exactly what I used for wview all this time.  Worked on the first try.
>
> Good luck!
>
> [Vantage]
> # This section is for the Davis Vantage series of weather stations.
>
> # Connection type: serial or ethernet
> #  serial (the classic VantagePro)
> #  ethernet (the WeatherLinkIP)
> type = ethernet
>
> # If the connection type is serial, a port must be specified:
> #   Debian, Ubuntu, Redhat, Fedora, and SuSE:
> # /dev/ttyUSB0 is a common USB port name
> # /dev/ttyS0   is a common serial port name
> #   BSD:
> # /dev/cuaU0   is a common serial port name
> port = /dev/ttyUSB0
>
> # If the connection type is ethernet, an IP Address/hostname is
> required:
> host = 192.168.1.101
>
> ##
> # The rest of this section rarely needs any attention.
> # You can safely leave it "as is."
> ##
>
> # Serial baud rate (usually 19200)
> baudrate = 19200
>
> # TCP port (when using the WeatherLinkIP)
> tcp_port = 4660
>
> # TCP send delay (when using the WeatherLinkIP):
> tcp_send_delay = 0.5
>
> # The id of your ISS station (usually 1). If you use a wind meter
> connected

[weewx-user] Re: twitter extension: Able to insert a return/new line?

[Chris Alemany]

Haha. I suspect that 'server uptime' variable is optimistic. :)

Maybe this is a more general question than just on this extension.

How do I know what weewx values are available to the extension (or any 
extension for that matter?).  For example, what is the "rain" variable 
actually returning in twitter.  It is not the daily rain sum... how can I 
know what is what and what is available for display?

Cheers,
Chris

On Wednesday, December 27, 2017 at 1:17:34 PM UTC-8, vince wrote:
>
> On Wednesday, December 27, 2017 at 12:02:24 PM UTC-8, Chris Alemany wrote:
>>
>> And any idea how I could add the barometer trend value?
>>
>> I'm still learning how to find all of the available values in extensions 
>> and throughout the system.
>>
>>
>>
> https://github.com/weewx/weewx/wiki/twitter has the docs
>
> Speculating on your other question, wondering if 'format' would let you 
> add the newline. 
>
> I like your system uptime (what a stable system :-)
> Server uptime: 17527 days, 21 hours, 15 minutes
>
>

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

Re: [weewx-user] Re: Original Vantage Pro, connected via serial-ethernet converter?

[Chris Alemany]

My welcome has been similar :)

On the 15 years or so of data from wview. I successfully imported 12 years 
of data. So it's possible! :)

Good luck.
Chris

On Wednesday, December 27, 2017 at 8:56:51 PM UTC-8, loonsailor wrote:
>
> Thanks, that did it!  Actually, I'm not sure whether it was the "port" or 
> the "tcp_port" parameter in weewx.conf, so I changed both.  I'm up and 
> running!  It barfed on importing my 15 years or so of data from wview, but 
> that's a problem for another day, and I won't have a chance to dig into it 
> for a couple of weeks.
>
> Thanks again for all the help!  What a nice way to enter a new community.
>
> On Wednesday, December 27, 2017 at 6:16:56 PM UTC-8, Tom Keffer wrote:
>>
>> The "host" line should just  be the IP address: no port.
>>
>> The "port" line should be the port.
>>
>> you're combining the two as "host".
>>
>> So, you want
>>
>> [Vantage]
>>   type = ethernet
>>   host = 192.168.198.202
>>   port = 3001
>>
>> -tk
>>
>> On Wed, Dec 27, 2017 at 6:05 PM, 'loonsailor' via weewx-user <
>> weewx...@googlegroups.com> wrote:
>>
>>> Thanks for this.  I was really excited.  Tried it, but it doesn't work.  
>>> Specifically, here is the log file:
>>>
>>> Dec 27 18:00:32 ubu-mini-weather weewx[10917]: engine: Loading station 
>>> type Vantage (weewx.drivers.vantage)
>>> Dec 27 18:00:32 ubu-mini-weather weewx[10902]:...done.
>>> Dec 27 18:00:32 ubu-mini-weather systemd[1]: Started LSB: weewx weather 
>>> system.
>>> Dec 27 18:00:32 ubu-mini-weather weewx[10917]: vantage: Socket error 
>>> while opening port 2 to ethernet host 192.168.198.202.
>>> Dec 27 18:00:32 ubu-mini-weather weewx[10917]: import of driver failed: 
>>> [Errno 111] Connection refused ()
>>> Dec 27 18:00:32 ubu-mini-weather weewx[10917]: engine: Unable to load 
>>> driver: [Errno 111] Connection refused
>>> Dec 27 18:00:32 ubu-mini-weather weewx[10917]:   Exiting...
>>>
>>>
>>>
>>> The serial port converter wants to use socket 3001.  Worked fine in 
>>> wview, so I chaged the socket address in weewx.conf to be 
>>> 192.168.198.202:3001.  Then, I get the following:
>>>
>>> Dec 27 17:31:29 ubu-mini-weather weewx[10673]: engine: Loading station 
>>> type Vantage (weewx.drivers.vantage)
>>> Dec 27 17:31:29 ubu-mini-weather weewx[10673]: vantage: Socket error 
>>> while opening port 2 to ethernet host 192.168.198.202:3001.
>>> Dec 27 17:31:29 ubu-mini-weather weewx[10673]: import of driver failed: 
>>> [Errno -2] Name or service not known ()
>>> Dec 27 17:31:29 ubu-mini-weather weewx[10673]: engine: Unable to load 
>>> driver: [Errno -2] Name or service not known
>>> Dec 27 17:31:29 ubu-mini-weather weewx[10658]:...done.
>>>
>>> So, I'm not sure how to tell it to open the correct socket on the 
>>> lantronix.  I'll have a look at the code, but any ideas?
>>>
>>> Thanks
>>>
>>> On Wednesday, December 27, 2017 at 11:03:43 AM UTC-8, Chris Alemany 
>>> wrote:
>>>
 Hi loonsailor,

 I have been using a serial to ethernet interface for years as well 
 (with the wview software).  I moved to weewx recently and after some 
 digging realized the support for serial-ethernet is there, just not 
 documented up front.

 Just go through the regular install process and when you get into the 
 weewx.conf file below is what I am using for my Serial-Ethernet bridge.  
 Exactly what I used for wview all this time.  Worked on the first try.

 Good luck!

 [Vantage]
 # This section is for the Davis Vantage series of weather stations.
 
 # Connection type: serial or ethernet 
 #  serial (the classic VantagePro)
 #  ethernet (the WeatherLinkIP)
 type = ethernet
 
 # If the connection type is serial, a port must be specified:
 #   Debian, Ubuntu, Redhat, Fedora, and SuSE:
 # /dev/ttyUSB0 is a common USB port name
 # /dev/ttyS0   is a common serial port name
 #   BSD:
 # /dev/cuaU0   is a common serial port name
 port = /dev/ttyUSB0
 
 # If the connection type is ethernet, an IP Address/hostname is 
 required:
 host = 192.168.1.101
 
 ##
 # The rest of this section rarely needs any attention. 
 # You can safely leave it "as is."
 ##
 
 # Serial baud rate (usually 19200)
 baudrate = 19200
 
 # TCP port (when using the WeatherLinkIP)
 tcp_port = 4660
 
 # TCP send delay (when using the WeatherLinkIP):
 tcp_send_delay = 0.5
 
 # The id of your ISS station (usually 1). If you use a wind meter 
 connected
 # to a anemometer transmitter kit, use its id
 iss_id = 1
 
 # How long to wait for a response from the station before giving up 
 (in
 

[weewx-user] MQTT extension

[Daniel Jönsson]

Hi,

I've just installed the MQTT extension (
https://github.com/weewx/weewx/wiki/mqtt) to get my readings into my home 
automation system (Home Assistant) and it works perfect!
But I have a question about the topics sent.

But I would like to have the total amount of rain the last 7 days. Not rain 
this week, but accumulated amount for the last 168 hours. So I could get a 
notice that maybe it is time to take out the garden hose...

In the available topics I find:

rainRate
rain
rainTotal
rain24
dayRain
hourRain

I figured out that rain24 must be the amount accumulated the last 24 hours. 
The rest is still a guess. (For some reason it has stopped rain the one 
time I want some rain)

I found another thread here about custom topics (
https://groups.google.com/d/msg/weewx-user/NBG_-D-Hghw/Nx6426vtBgAJ) and 
there the author of the extension answered that it is not possible to use 
aggregation templates for this extension. It can only publish LOOP-packages 
or archive records.
I have not stated anything to bind to in my settings, so it should be the 
default, which should be archive records.

About two years ago I wrote my own (not very nice one) "extension" to send 
archive records to my previous automation system (Domoticz). And the only 
three records about rain I could find then was:

rainRate
rain
rainTotal

And if I look in the documentation of weewx (
http://www.weewx.com/docs/customizing.htm#archive_types) I can only find:

rainRate
rain

So my question is; where is rain24, dayRain and hourRain picked up?
And is there any way to publish a topic for lets say: rain7days?

-- 
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: logrotate

[mwall]

On Thursday, December 28, 2017 at 11:06:08 AM UTC-5, Daniel Jönsson wrote:
>
> I guess you are right about that it not should cause any harm.
> I just thought it was some misstake and it should be weewx that should 
> restart instead.
>
> But any way. In Ubuntu it works fine with rotating without restarting 
> either rsyslog or weewx. Mine has rotate the logs now 3 times without 
> problems.
>

daniel,

thank you for pointing out this issue.  it has been addressed at commit 
54d9aac4 

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: logrotate

[Daniel Jönsson]

I guess you are right about that it not should cause any harm.
I just thought it was some misstake and it should be weewx that should 
restart instead.

But any way. In Ubuntu it works fine with rotating without restarting 
either rsyslog or weewx. Mine has rotate the logs now 3 times without 
problems.



Den onsdag 13 december 2017 kl. 17:17:45 UTC+1 skrev Andrew Milner:
>
> looks as though centos once had a problem 
> https://www.centos.org/forums/viewtopic.php?t=32715
>
> guess the stop and start may not be necessary nowadays - but they should 
> not cause any harm either
>
>
>
> On Wednesday, 13 December 2017 16:58:01 UTC+2, Daniel Jönsson wrote:
>
>> Sorry, I meant syslog, as I also wrote in the first post.
>>
>>
>> Den onsdag 13 december 2017 kl. 15:36:53 UTC+1 skrev Andrew Milner:
>>>
>>> My logrotate stops and starts syslog at postrotate, it does not restart 
>>> logrotate.
>>>
>>> /var/log/weewx.log {
>>>   weekly
>>>   missingok
>>>   rotate 52
>>>   compress
>>>   delaycompress
>>>   notifempty
>>> # debian uses root:adm
>>> #  create 644 root adm
>>> # ubuntu uses syslog:adm
>>> #  create 644 syslog adm
>>>   sharedscripts
>>>   postrotate
>>> # standard way of invoking rc scripts
>>> /etc/init.d/rsyslog stop
>>> /etc/init.d/rsyslog start
>>>
>>>
>>> On Wednesday, 13 December 2017 15:56:42 UTC+2, Daniel Jönsson wrote:
>>>
 I understand. I am only familiar with Debian/Ubuntu so I can not help 
 you with that.
 And to me it seemed strange. Some times you restart/reload the 
 service/demaon, but I have never seen that a logrotate is restarting 
 logrotate...



 Den onsdag 13 december 2017 kl. 12:42:38 UTC+1 skrev mwall:
>
> On Wednesday, December 13, 2017 at 4:36:01 AM UTC-5, Daniel Jönsson 
> wrote:
>>
>> In this logrotate example you are restarting rsyslog postrotate!! Why?
>>
>
> restarting rsyslog is probably not necessary for the most recent 
> operating systems.
>
> i found that on some systems, logrotate did not manage open file 
> handles properly.  when logrotate rotated the weewx log file, (r)syslog 
> would continue to write to the log that had been rotated.
>
> do you know of a way to ensure proper logrotate behavior that works on 
> all operating systems and all operating system versions?
>
> 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.