[weewx-user] Re: FineOffset Hang ups

[Andrew Milner]

The usb ports on the pi are notoriously power sensitive.



On Saturday, 30 December 2017 00:48:48 UTC+2, Redanman wrote:

> For anyone else struggling with this problem, the behaviour pattern of USB 
> lock-ups has completely changed when I swapped the Pi power supply for a 
> different one.  My system was locking up at 1 to 2 day intervals on the old 
> power supply; I am now at 10 days without a problem on the new power 
> supply.  It seems that the USB interface on the WH1080 is voltage (or 
> current) sensitive.  This would be consistent with the recommendation to 
> use a powered USB hub.

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

[Andrew Milner]

I think I got it wrong and it should be  rather than  and also I 
would have thought more like
format = "{station} {dateTime:%H:%M %b %d %Y}: T: {outTe
or
format = "{station} {dateTime:%H:%M %b %d %Y}: T: {outTe

really clutching at straws though!!

good luck



On Friday, 29 December 2017 19:44:44 UTC+2, Chris Alemany wrote:

> No luck. Not parsed. :(
>
> Hourly Auto-Tweet 09:35 Dec 29 2017:  T: 2.2ºC D: 2.2ºC W: * 0.0kph 
> gusting to 0.0kph H: 100% P: 1013.92hPa Rain 0.25mm Rain Rate: 0.0mm/hr 
> Chill:2.2ºC HIndex:2.2ºC Solar: 10W/m2 UV: 0
>
> On Friday, December 29, 2017 at 6:48:14 AM UTC-8, Andrew Milner wrote:
>>
>> Try and insert  for the newline
>>
>>
>>
>> On Friday, 29 December 2017 15:35:10 UTC+2, Chris Alemany wrote:
>>
>>> Thanks for the mental push on ‘the whole twitter section”. I’ve figured 
>>> out the day rain issue. 
>>>
>>> I was using METRIC rather than METRICWX so dayRain was reporting in cm 
>>> rather than mm.  Since it was a small amount of rain… it was reporting 
>>> 0.0cm.  We’ve subsequently had almost 20mm of rain today, which means there 
>>> is enough to notice the units mixup.
>>>
>>> Here is the successful wview.conf including the formatting used for the 
>>> tweet below:
>>>
>>> station = Hourly Auto-Tweet
>>> unit_system = METRICWX
>>> post_interval = 3600
>>> format_None = *
>>> 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:%.2f}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;
>>>
>>> https://twitter.com/Auto_AlberniWx/status/946581641299771392
>>>
>>> So that is good.
>>>
>>> Unfortunately, I have not found a solution to the original request of 
>>> inserting a new line. But I am willing to let it go and chalk it up to a 
>>> limitation of twython. :)
>>>
>>> Thank you all for your help and suggestions.
>>>
>>> Chris
>>>
>>>
>>>
>>> On Dec 28, 2017, at 6:40 PM, Thomas Keffer  wrote:
>>>
>>> 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.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 

[weewx-user] Re: upgrade not working

[gjr80]

I should have said, wee_device was introduced in weeWX 3.2.0. Previously it was 
known as wee_config_device. Probably some command line option changes too, 
running --help against either should list the supported command line options.

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: upgrade not working

[Mike Robokoff]

Thanks again Gary, I really appreciate it. I will give that a try next time 
I try and connect the system. 
I checked my weewx 2.5 system and I don't see the wee_device command. I 
guess that was added later. 
I should be able to run it from my new system weewx 3.8 or is it a separate 
down load. I can't look at my 3.8 system right now.



On Friday, December 29, 2017 at 8:29:16 PM UTC-6, gjr80 wrote:
>
> Mike,
>
> I've always used wee_device --clear-memory (
> http://weewx.com/docs/hardware.htm#vantage_clear_console_memory45 
> ).
>  
> Of course you need to stop weeWX first.
>
> 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: upgrade not working

[gjr80]

Mike,

I've always used wee_device --clear-memory 
(http://weewx.com/docs/hardware.htm#vantage_clear_console_memory45). Of course 
you need to stop weeWX first.

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: Acurite (ugh), and weewx ona RasbPi.

[Craig Thom]

I built a pressure and temperature sensor using a BMP280 connected directly 
to the Raspberry Pi and wrote a driver.  It's too close to the Pi and my 
other computers to give useful temperature readings.  I bought an indoor 
Acurite temperature/humidity sensor and use that for indoor temp and 
humidity.  Actually I bought four of them, so I have lots of indoor 
temperature and humidity.

On Wednesday, December 13, 2017 at 12:03:50 PM UTC-5, Andy wrote:
>
> I switched to the USB SDR receiver so no longer using the USB console 
> connection. This driver  and a 
> $10 receiver from aliexpress like this 
> .
>   
> You lose pressure and inside temperature since you are only connecting to 
> the outside unit, but there are ways to solve that issue
>

-- 
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: Redundant and self synchronizing database between two systems - which approach (MQTT ?) ?

[Craig Thom]

Is weewx running on the Raspberry Pi?

Weewx on my Raspberry Pi uses MySQL for logging data.  I use master/slave 
replication to duplicate they database on my Windows computer, but it would 
certainly work on a Linux computer.  When either is down it catches up when 
they are both back up.

Replication is a built in function of MySQL.

On Wednesday, December 27, 2017 at 2:46:03 AM UTC-5, Markus wrote:
>
> Hello,
>
> i am building up a Raspberry Pi based home made weather station at my 
> garden house.
> The data collecting script will be self written (more to this script here: 
> https://www.wxforum.net/index.php?topic=22428.0 )
> For a stable system the RasPi will run with a industrial grade microSD 
> (Transcend High Endurance) and a UPS.
>
> The weather data will be collected locally on the RasPi but should also be 
> stored on my Linux server - both are connected via LAN.
> The Linux server is also responsible for visualizing the weather data.
>
> When the Linux server or the RasPi were down, they should synchronize to 
> the latest available data automatically when they up again.
>
> My question:
> Which approach may be a good solution (and easy maintainable) for this 
> requirements?
> May be a mqtt with two servers be used?
> I am happy for every proposal.
>
> Regards
> Markus
>
>
>

-- 
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: Reading historical data from Klimalogg Pro

[Luc Heijst]

The klimalogg driver tries to calculate where to start with collecting 'missed' 
data. This calculation will be wrong when the klimalogg memory is filled with 
data of different intervals. Example: the first 20.000 records have an interval 
of 30 minutes, then 15.000 records with an interval of 1 minute and the newer 
records have an interval of 5 minutes.

Also the data in the klimalogg memory can have the time stamps not in 
increasing order.
We have seen problems with the reception of the DCF time. Then 10 march 2017 
suddenly was read as 10 february 2017. One day later the time was normal again 
(11 march 2017 in this example). The logic in the klimalogg driver tries to 
overcome such timestamp jumps and will skip the records the logic thinks are 
bad. 
It might also do not foreseen actions when a number of such wrong timestamps 
come close next after each other.

When such a situation occurs the only cure might be to clear all data in the 
klimalogg memory.

Luc

-- 
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: upgrade not working

[Mike Robokoff]

Gary, Thank you very much for your response, I also believe it is related 
to the logger. I have never had to clear/reset the logger. How does one do 
that?


On Friday, December 29, 2017 at 6:34:38 PM UTC-6, gjr80 wrote:
>
> Hi,
>
> Might be a bit hard to say given all the swapping in/out and resetting but 
> I wonder if perhaps the Davis logger was getting a bit cranky being swapped 
> in and out. As far as I know resetting the console does not necessarily 
> clear/reset the logger. The age of the console and weeWX versions concerned 
> should not have been an issue.
>
> 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] upgrade not working

[gjr80]

Hi,

Might be a bit hard to say given all the swapping in/out and resetting but I 
wonder if perhaps the Davis logger was getting a bit cranky being swapped in 
and out. As far as I know resetting the console does not necessarily 
clear/reset the logger. The age of the console and weeWX versions concerned 
should not have been an issue.

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.

Re: [weewx-user] Re: inside dewpoint?

[gjr80]

Good to hear it's working. I'll give your comments some thought as I travel 
home today and will reply from home, much easier to give a easier to read 
response to multiple points from home than trying to reply on this iPad.

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] upgrade not working

[Mike Robokoff]

I have an old vantage pro 2 that was running for years on on old raspberry 
pi with weewx. Recently I had an issue and thought I would get a second 
raspberry pi with new sd card for a back up. When I got the new raspberry 
pi, I found it was not compatible with my old one. The new one uses micro 
sd and the old was a regular, my old raspberry pi is running weewx 2.5 and 
the new one I built with weewx 3.8 The os was also updated on the new 
raspberry pi. When I swapped out the old pi for the new one, it started 
working just fine. it worked a few hours and then it crashed. I connected 
the old pi and still could not get updates to work. I reset both the pi and 
the vantage pro 2 console a few times to no avail. I finally just left the 
old pi connected and left it alone. After a few hours it started working 
fine on its own with out me doing anything. I let it run over night and all 
seemed fine. So I tried the new pi again only this time it woud run though 
the archives but would not send updates. Again the vantage pro was messed 
up as I reconnected the old pi and again could not get it working After 
resetting both the vantage pro 2 console and the pi I did finally get it 
working again on the old pi and the old version of weewx. So I am wondering 
is there a compatibility issue with the new version of weewx and an old 
vantage pro 2? Or does anyone have any ideas on what the issue may be?  
Thanks for reading this and any input you can offer. 

-- 
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] windrun calculation error ?

[gjr80]

That's a bit strong, just 'read the code'. I think it is as simple as adding 
the current records windrun, the only corner case I see might be the record 
timestamped midnight, but again I think the same approach (add the current 
records windrun) should work.

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.

Re: [weewx-user] windrun calculation error ?

[Thomas Keffer]

Opened as Issue #294 .

-tk

On Fri, Dec 29, 2017 at 4:11 PM, Thomas Keffer  wrote:

> That's effin brilliant, Gary. Never occurred to me.
>
> So, the solution would be to add the "current" windrun on to the total.
>
> -tk
>
> On Fri, Dec 29, 2017 at 4:06 PM, gjr80  wrote:
>
>> I can see why the 1st archive entry after midnight is always 0.
>> StdWXCalculate calculates windrun by queriying the archive for windSpeed
>> and interval values after midnight and up to and including the current
>> archive record dateTime. As StdWXCalculate is run before StdArchive the 1st
>> archive record after midnight is not yet in the archive when windrun is
>> calculated by StdWxCalculate (in fact because of this the windrun from the
>> current achive record is never included). Hence for the 1st archive record
>> after midnight windrun is calculated as 0 (there were no records) and that
>> is what StdArchive saves to archive. The StdWXCalculate windrun calculation
>> should add in the windrun calculated from the current archive record.
>>
>> Not sure about the other anomalies though.
>>
>> 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.
>>
>
>

-- 
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: Reading historical data from Klimalogg Pro

[eddy B]

Hey Luc,

yes, that's also the idea I came up with. I set the batch length to 51.200 
as you suggested in your older post and it is populating a new database as 
we speak. I hope it will work :)

Any idea why it failed in the first place? or the reason why it sometimes 
failes to read historical data properly?

On Saturday, 30 December 2017 00:52:50 UTC+1, Luc Heijst wrote:
>
> Hi Eddy,
>
> At startup the klimalogg driver reads the timestamp of the most recent 
> record in the weewx database.
> It then tries to read all records in the klimalogg memory with a bigger 
> time stamp until no newer records can't be found.
> Then the driver starts collecting the recent data each five minutes.
> When you want to start all over with reading all records of the klimalogg 
> (this can be as many as 51.200 !!) you will have to stop weewx, delete or 
> rename your weewx database file and start weewx. This process can take many 
> hours, sometimes several days, to complete depending of the speed of your 
> computersystem.
>
> If you don't want to start all over, but read the data back since a 
> certain date, you need to delete all newer records in the weewx database 
> and then restart weewx.
>
> Luc
>
>

-- 
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] windrun calculation error ?

[Thomas Keffer]

That's effin brilliant, Gary. Never occurred to me.

So, the solution would be to add the "current" windrun on to the total.

-tk

On Fri, Dec 29, 2017 at 4:06 PM, gjr80  wrote:

> I can see why the 1st archive entry after midnight is always 0.
> StdWXCalculate calculates windrun by queriying the archive for windSpeed
> and interval values after midnight and up to and including the current
> archive record dateTime. As StdWXCalculate is run before StdArchive the 1st
> archive record after midnight is not yet in the archive when windrun is
> calculated by StdWxCalculate (in fact because of this the windrun from the
> current achive record is never included). Hence for the 1st archive record
> after midnight windrun is calculated as 0 (there were no records) and that
> is what StdArchive saves to archive. The StdWXCalculate windrun calculation
> should add in the windrun calculated from the current archive record.
>
> Not sure about the other anomalies though.
>
> 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.
>

-- 
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: inside dewpoint?

[Greg Troxel]

gjr80  writes:

Thank you for taking the time to explain things to me.  I misunderstood
a few things, which may just be me, or may be useful for enhancing the
docs (which are very impressive).

> WeeWX is doing exactly what it should/has been told to do. Inside
> dewpoint is not provided by Davis VP2 hardware (have a look at the
> loop, loop2 and rev A/rev B archive records in the Davis Serial
> Communications Reference (about page 30 in
> https://www.davisnet.com/support/weather/download/VantageSerialProtocolDocs_v261.pdf).
>  StdWXCalculate
> has been told to 'prefer' gettting inside dewpoint from
> hardware. Since the hardware doesn't provide inside dewpoint weeWX
> calculates it instead (if it was set to hardware_only the weeWX would
> not calculate it) and adds it to loop packets and archive
> records. That explains why you are seeing inDewpoint.

I assumed it was from the hardware because the LOOP line output on
stdout (I am saving to a file, not using --daemon, for now) had it.  I
realize now (I think) that the LOOP line is a virtual LOOP packet which
has the hardware-supplied values and the calculated values.

> As Vince said weeWX defaults to using the wview schema and the wview
> schema does not include inDewpoint, so weeWX does not save inDewpoint
> to the database (by default weeWX will save to the database any fields
> in an archive record that are also defined in the db schema you are
> using).

So fields that are calculated by StdReport will just be dropped, if they
aren't in the schema.  That makes sense now that I understand the grand
plan, but I didn't expect that.  (I did read most of the docs all the
way through quickly before starting to use weewx, and I have never used
any other weather logging software.)

> In terms of reports, something like $current.inDewpoint will
> work because reports can use any field in the current archive record
> without having saved it to the database. However, any aggregates eg

Ah.  That explains my confusion when indeed that worked.  I knew
something was wrong when adding inDewpoint to the inTemp graph threw an
exception.

> $day.inDewpoint.max used in a report or plotting inDewpoint will not
> work as these require inDewpoint to be saved to the database. There
> are a number of ways to add inDewpiunt to the database, you can extend
> the current schema (as Vince points out) or you could add a new
> database. The former will be easier. This link might help
> http://weewx.com/docs/customizing.htm#archive_database

Thanks.  I found that from Vince's hint and it explained exactly how to
do things.  I just adjusted my sources, did a backup and ran
wee_database --config, and now things are fine.

The other thing that might be good to make clear -- but maybe this is
getting into nits that are confusing rather than helpful for new poeple
-- is that all the calculations are either at LOOP or just before
archive time, and do not work to synthesize values from the existing
data for use in graphs.

I don't mean to sound cranky.  My out-of-box experience with weewx has
been far smoother than I could possibly expect given the inherent
complexity of the problem, and the effort to do something odd has been
very small.

(I realize I'm quite odd for wanting indoor dewpoint.  Basically I'm
concerned about indoor humidity and want to keep an eye on my
humidifier, and am curious to see how dewpoint tracks because the
temperature varies with day/night setpoints.  Outdoors, I find humidity
to be a confounded combination of dewpoint and temp, and don't pay much
attention to it.  It may be that indoors, it's really humidity that
matters, since for values one wants, it tends to zero absent the forced
humidifier -- my outdoor dewpoint is -2.3F right now.)

Greg Troxel 

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


signature.asc
Description: PGP signature

Re: [weewx-user] windrun calculation error ?

[gjr80]

I can see why the 1st archive entry after midnight is always 0. StdWXCalculate 
calculates windrun by queriying the archive for windSpeed and interval values 
after midnight and up to and including the current archive record dateTime. As 
StdWXCalculate is run before StdArchive the 1st archive record after midnight 
is not yet in the archive when windrun is calculated by StdWxCalculate (in fact 
because of this the windrun from the current achive record is never included). 
Hence for the 1st archive record after midnight windrun is calculated as 0 
(there were no records) and that is what StdArchive saves to archive. The 
StdWXCalculate windrun calculation should add in the windrun calculated from 
the current archive record.

Not sure about the other anomalies though.

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: Reading historical data from Klimalogg Pro

[Luc Heijst]

Hi Eddy,

At startup the klimalogg driver reads the timestamp of the most recent record 
in the weewx database.
It then tries to read all records in the klimalogg memory with a bigger time 
stamp until no newer records can't be found.
Then the driver starts collecting the recent data each five minutes.
When you want to start all over with reading all records of the klimalogg (this 
can be as many as 51.200 !!) you will have to stop weewx, delete or rename your 
weewx database file and start weewx. This process can take many hours, 
sometimes several days, to complete depending of the speed of your 
computersystem.

If you don't want to start all over, but read the data back since a certain 
date, you need to delete all newer records in the weewx database and then 
restart weewx.

Luc

-- 
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] Report generation breaking whenever we lose internet

[mwall]

Set record_generation=software in your weewx config

But it would be best if we could determine why a power/time/net glitch borks 
your logger

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: inside dewpoint?

[gjr80]

Hi,

WeeWX is doing exactly what it should/has been told to do. Inside dewpoint is 
not provided by Davis VP2 hardware (have a look at the loop, loop2 and rev 
A/rev B archive records in the Davis Serial Communications Reference (about 
page 30 in 
https://www.davisnet.com/support/weather/download/VantageSerialProtocolDocs_v261.pdf).
 StdWXCalculate has been told to 'prefer' gettting inside dewpoint from 
hardware. Since the hardware doesn't provide inside dewpoint weeWX calculates 
it instead (if it was set to hardware_only the weeWX would not calculate it) 
and adds it to loop packets and archive records. That explains why you are 
seeing inDewpoint.

As Vince said weeWX defaults to using the wview schema and the wview schema 
does not include inDewpoint, so weeWX does not save inDewpoint to the database 
(by default weeWX will save to the database any fields in an archive record 
that are also defined in the db schema you are using). In terms of reports, 
something like $current.inDewpoint will work because reports can use any field 
in the current archive record without having saved it to the database. However, 
any aggregates eg $day.inDewpoint.max used in a report or plotting inDewpoint 
will not work as these require inDewpoint to be saved to the database. There 
are a number of ways to add inDewpiunt to the database, you can extend the 
current schema (as Vince points out) or you could add a new database. The 
former will be easier. This link might help 
http://weewx.com/docs/customizing.htm#archive_database

Hope this explains what is going on.

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: FineOffset Hang ups

[Redanman]

For anyone else struggling with this problem, the behaviour pattern of USB 
lock-ups has completely changed when I swapped the Pi power supply for a 
different one.  My system was locking up at 1 to 2 day intervals on the old 
power supply; I am now at 10 days without a problem on the new power supply.  
It seems that the USB interface on the WH1080 is voltage (or current) 
sensitive.  This would be consistent with the recommendation to use a powered 
USB hub.

-- 
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] Anyone using the La Crosse 330-2315 Professional Weather Station with weewx

[Ted Bevenour]

Fantastic! Thank you so much!   

I'll be playing around with the setup this weekend, I'll let you know how 
it goes!

On Friday, December 29, 2017 at 2:44:06 PM UTC-6, Tom Keffer wrote:
>
> The interceptor driver  
> can do this.
>
> Be sure to check the Wiki ! It and 
> many other drivers are listed there.
>
> -tk
>
>
> On Fri, Dec 29, 2017 at 9:57 AM, Ted Bevenour  > wrote:
>
>> Oh, very interesting! Thanks so much for the link, I'll see what I can 
>> come up with. 
>>
>> On Friday, December 29, 2017 at 11:31:22 AM UTC-6, ln77 wrote:
>>>
>>> I don’t see any interface for getting the data from that console, other 
>>> than its wifi that appears to be specialized to posting the data to weather 
>>> underground, so it doesn’t support weewx in the usual way.
>>>
>>> But there’s hope! I ran across this posting on the wxforum Lacrosse 
>>> topic https://www.wxforum.net/index.php?topic=30932.msg335582#msg335582 
>>> from 
>>> someone who’s doing what you want to do, by sniffing the data.  I’d assume 
>>> that means the console is configured to post to weather underground, with 
>>> some code on the RPi sniffing the network connection and extracting the 
>>> data.  Not sure if this was discussed on this forum but you might contact 
>>> the author directly.
>>>
>>>   -Les
>>>
>>>
>>>
>>> On 29 Dec 2017, at 8:54, Ted Bevenour  wrote:
>>>
>>> So Santa brought me this station 
>>> 
>>>  
>>> for xmas this year... I'd like to run weewx on a RPi and access the 
>>> stations data that way. I didn't see this particular model listed on the 
>>> hardware page, but was curious if anyone might be using it anyway.   
>>>
>>> I'm guess this is probably a no, but thought I'd ask anyway.  
>>>
>>> Thanks in advance,   
>>>
>>> // Ted
>>>
>>> -- 
>>> 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+...@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] windrun calculation error ?

[Thomas Keffer]

Thanks for the debugging info. You've obviously looked through the source
code to see what the calculation uses!

A few questions:

What hardware are you using?

Did you set windrun to "software" in [[Calculations]]? Or, something else?

Are the "zero" values truly zero, or are they null?

It's a pretty simple calculation. Hard to see what's going wrong. One thing
you could try is to insert a couple of temporary print statement in the
code to see what values it is using and what logic it is following.

-tk



On Fri, Dec 29, 2017 at 1:35 PM, Michael Hornsby <
michael.d.horn...@gmail.com> wrote:

> Thanks Tom
>
> I enabled windrun in weewx , added the fields to the database. Here's an
> example of what was calculated by weewx and the zero values I mentioned.
>
> 1514466000 is  Friday, 29 December 2017 00:00:00
>
> 1514552400 is Saturday, 30 December 2017 00:00:00
>
>
>
>
> dateTime usUnits interval windSpeed windrun
> 1514465700 1 5 4.205298013 173.1249273
> 1514466000 1 5 4.715231788 0
> 1514466300 1 5 3.927631579 0
> 1514466600 1 5 3.71333 0.327302632
> 1514466900 1 5 2.291390728 0.636747076
> 1514467200 1 5 2.635761589 0.827696303
> 1514552100 1 5 6.947019868 115.6742846
> 1514552400 1 5 6.264900662 0
> 1514552700 1 5 6.611842105 0
> 1514553000 1 5 8.44 0.550986842
> 1514553300 1 5 8.417218543 1.254320175
> Just wondering if this is what you would expect, two zero values ?
>
>  My backfill based on the code in wxservices.py gave me
>
> 1514552400 as 0.0
> and 1514552700 as 0.550986842105
>
> Thanks
> Michael
>
>
>
> On Saturday, 30 December 2017 07:52:22 UTC+11, Tom Keffer wrote:
>>
>> What was the wind for the first five minutes? Maybe it was calm?
>>
>> Also, note that the archive record at midnight belongs to the *previous* day.
>> So, 12:05AM will be the very first record of the day.
>>
>> Finally, did you specify that windrun be calculated? By default, it is
>> not. See the section [[Calculations]]
>>  in the User's
>> Guide.
>>
>> -tk
>>
>> On Fri, Dec 29, 2017 at 12:10 PM, Michael Hornsby 
>> wrote:
>>
>>> Hi
>>>
>>> I've enabled windrun and am working on back filing the database. When I
>>> looked through the database to compare my back filling with the actual
>>> calculations I find at  midnight there are two zero values for windrun.
>>>
>>> at 12:00 windrun is zero - ok I would expect that but at 12:05 windrun
>>> is also zero. I would expect windrun would be the wind for the first 5
>>> minutes of the day ??
>>>
>>> Am I missing something ??
>>>
>>> Thanks
>>> Michael
>>>
>>> --
>>> 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] windrun calculation error ?

[Michael Hornsby]

Thanks Tom

I enabled windrun in weewx , added the fields to the database. Here's an 
example of what was calculated by weewx and the zero values I mentioned.

1514466000 is  Friday, 29 December 2017 00:00:00

1514552400 is Saturday, 30 December 2017 00:00:00




dateTime usUnits interval windSpeed windrun 
1514465700 1 5 4.205298013 173.1249273 
1514466000 1 5 4.715231788 0 
1514466300 1 5 3.927631579 0 
1514466600 1 5 3.71333 0.327302632 
1514466900 1 5 2.291390728 0.636747076 
1514467200 1 5 2.635761589 0.827696303 
1514552100 1 5 6.947019868 115.6742846 
1514552400 1 5 6.264900662 0 
1514552700 1 5 6.611842105 0 
1514553000 1 5 8.44 0.550986842 
1514553300 1 5 8.417218543 1.254320175 
Just wondering if this is what you would expect, two zero values ?

 My backfill based on the code in wxservices.py gave me

1514552400 as 0.0
and 1514552700 as 0.550986842105

Thanks
Michael



On Saturday, 30 December 2017 07:52:22 UTC+11, Tom Keffer wrote:
>
> What was the wind for the first five minutes? Maybe it was calm?
>
> Also, note that the archive record at midnight belongs to the *previous* day. 
> So, 12:05AM will be the very first record of the day.
>
> Finally, did you specify that windrun be calculated? By default, it is 
> not. See the section [[Calculations]] 
>  in the User's 
> Guide.
>
> -tk
>
> On Fri, Dec 29, 2017 at 12:10 PM, Michael Hornsby  > wrote:
>
>> Hi
>>
>> I've enabled windrun and am working on back filing the database. When I 
>> looked through the database to compare my back filling with the actual 
>> calculations I find at  midnight there are two zero values for windrun.
>>
>> at 12:00 windrun is zero - ok I would expect that but at 12:05 windrun is 
>> also zero. I would expect windrun would be the wind for the first 5 minutes 
>> of the day ??
>>
>> Am I missing something ??
>>
>> Thanks
>> Michael
>>
>> -- 
>> 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] windrun calculation error ?

[Thomas Keffer]

What was the wind for the first five minutes? Maybe it was calm?

Also, note that the archive record at midnight belongs to the *previous* day.
So, 12:05AM will be the very first record of the day.

Finally, did you specify that windrun be calculated? By default, it is not.
See the section [[Calculations]]
 in the User's Guide.

-tk

On Fri, Dec 29, 2017 at 12:10 PM, Michael Hornsby <
michael.d.horn...@gmail.com> wrote:

> Hi
>
> I've enabled windrun and am working on back filing the database. When I
> looked through the database to compare my back filling with the actual
> calculations I find at  midnight there are two zero values for windrun.
>
> at 12:00 windrun is zero - ok I would expect that but at 12:05 windrun is
> also zero. I would expect windrun would be the wind for the first 5 minutes
> of the day ??
>
> Am I missing something ??
>
> Thanks
> Michael
>
> --
> 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: Reading historical data from Klimalogg Pro

[eddy B]

Hey, 

sorry to necro this thread, but I do have the exact same issue:
I set up weewx for a klimalogg which was already running since end of 2013. 
Once I connected everything it started reading out the historical data:





Dec 26 20:52:25 raspberrypi weewx[8067]: KlimaLogg: RFComm: 
handleHistoryData: records cached=1782, records skipped=0, next=1783

Dec 26 20:52:25 raspberrypi weewx[8067]: KlimaLogg: RFComm: 
handleHistoryData: records cached=1788, records skipped=0, next=1789

Dec 26 20:52:26 raspberrypi weewx[8067]: KlimaLogg: RFComm: 
handleHistoryData: records cached=1794, records skipped=0, next=1795

Dec 26 20:52:26 raspberrypi weewx[8067]: KlimaLogg: RFComm: 
handleHistoryData: records cached=1800, records skipped=0, next=1801

Dec 26 20:52:29 raspberrypi weewx[8067]: KlimaLogg: MainThread: Records 
scanned: 1800

Dec 26 20:52:29 raspberrypi weewx[8067]: KlimaLogg: MainThread: Found 1799 
historical records

Dec 26 20:52:29 raspberrypi weewx[8067]: KlimaLogg: MainThread: Handle 
record 1: 2013-11-04 11:30:00 CET (1383561000)

Dec 26 20:52:29 raspberrypi weewx[8067]: KlimaLogg: MainThread: Handle 
record 2: 2013-11-04 11:45:00 CET (1383561900)

Dec 26 20:52:29 raspberrypi weewx[8067]: manager: Added record 2013-11-04 11
:45:00 CET (1383561900) to database 'weewx-kl.sdb'

Dec 26 20:52:29 raspberrypi weewx[8067]: manager: Added record 2013-11-04 11
:45:00 CET (1383561900) to daily summary in 'weewx-kl.sdb'

[...] after a few minutes: 


Dec 26 20:57:35 raspberrypi weewx[8067]: manager: Added record 2013-12-11 03
:00:00 CET (1386727200) to database 'weewx-kl.sdb'

Dec 26 20:57:35 raspberrypi weewx[8067]: manager: Added record 2013-12-11 03
:00:00 CET (1386727200) to daily summary in 'weewx-kl.sdb'

Dec 26 20:57:35 raspberrypi weewx[8067]: KlimaLogg: MainThread: Saved 1799 
historical records; ts last saved record 2013-12-11 03:00:00 CET (1386727200
)

Dec 26 20:57:35 raspberrypi weewx[8067]: KlimaLogg: MainThread: Scan the 
next batch of 1800 historical records

Dec 26 20:57:35 raspberrypi weewx[8067]: KlimaLogg: MainThread: The scan 
will start after the next historical record is received.

Dec 26 20:58:05 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next 
batch of 1800 records will start within 5 minutes

Dec 26 20:58:20 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next 
batch of 1800 records will start within 5 minutes

Dec 26 20:58:35 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next 
batch of 1800 records will start within 5 minutes

Dec 26 20:58:50 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next 
batch of 1800 records will start within 5 minutes

Dec 26 20:59:05 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next 
batch of 1800 records will start within 5 minutes

Dec 26 20:59:20 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next 
batch of 1800 records will start within 5 minutes

Dec 26 20:59:35 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next 
batch of 1800 records will start within 5 minutes

Dec 26 20:59:50 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next 
batch of 1800 records will start within 5 minutes

Dec 26 21:00:05 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next 
batch of 1800 records will start within 5 minutes

Dec 26 21:00:06 raspberrypi weewx[8067]: KlimaLogg: RFComm: 
handleHistoryData: request records since 2013-12-11 03:00:00 CET (1386727200
)

Dec 26 21:00:06 raspberrypi weewx[8067]: KlimaLogg: RFComm: Number of 
history records limited to: 51200

Dec 26 21:00:06 raspberrypi weewx[8067]: KlimaLogg: RFComm: 
handleHistoryData: records cached=0, records skipped=0, next=39180

Dec 26 21:00:20 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next 
batch of 1800 records will start within 5 minutes

As you see on line with the time stamp 21:00:06 for some reason it now says 
"next=39180"

and five more minutes of "the next batch will start in 5 minutes" messages:

Dec 26 21:04:50 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next 
batch of 1800 records will start within 5 minutes

Dec 26 21:05:02 raspberrypi weewx[8067]: KlimaLogg: RFComm: 
handleHistoryData: records cached=1, records skipped=5, next=39181

Dec 26 21:05:05 raspberrypi weewx[8067]: KlimaLogg: MainThread: Records 
scanned: 1

Dec 26 21:05:05 raspberrypi weewx[8067]: KlimaLogg: MainThread: Found 0 
historical records

Dec 26 21:05:05 raspberrypi weewx[8067]: KlimaLogg: MainThread: Handle 
record 1801: 2017-12-26 21:05:00 CET (1514318700)

Dec 26 21:05:05 raspberrypi weewx[8067]: KlimaLogg: MainThread: Saved 0 
historical records; ts last saved record 2017-12-26 21:05:00 CET (1514318700
)

Dec 26 21:05:05 raspberrypi weewx[8067]: engine: Starting main packet loop.

Dec 26 21:10:16 raspberrypi weewx[8067]: manager: Added record 2017-12-26 21
:10:00 CET (1514319000) to database 'weewx-kl.sdb'

Dec 26 21:10:16 raspberrypi weewx[8067]: manager: Added record 2017-12-26 21
:10:00 CET (1514319000) to daily summary in 'weewx-kl.sdb'

Dec 26 21:10:17 

Re: [weewx-user] Anyone using the La Crosse 330-2315 Professional Weather Station with weewx

[Thomas Keffer]

The interceptor driver 
can do this.

Be sure to check the Wiki ! It and
many other drivers are listed there.

-tk


On Fri, Dec 29, 2017 at 9:57 AM, Ted Bevenour 
wrote:

> Oh, very interesting! Thanks so much for the link, I'll see what I can
> come up with.
>
> On Friday, December 29, 2017 at 11:31:22 AM UTC-6, ln77 wrote:
>>
>> I don’t see any interface for getting the data from that console, other
>> than its wifi that appears to be specialized to posting the data to weather
>> underground, so it doesn’t support weewx in the usual way.
>>
>> But there’s hope! I ran across this posting on the wxforum Lacrosse topic
>> https://www.wxforum.net/index.php?topic=30932.msg335582#msg335582 from
>> someone who’s doing what you want to do, by sniffing the data.  I’d assume
>> that means the console is configured to post to weather underground, with
>> some code on the RPi sniffing the network connection and extracting the
>> data.  Not sure if this was discussed on this forum but you might contact
>> the author directly.
>>
>>   -Les
>>
>>
>>
>> On 29 Dec 2017, at 8:54, Ted Bevenour  wrote:
>>
>> So Santa brought me this station
>> 
>> for xmas this year... I'd like to run weewx on a RPi and access the
>> stations data that way. I didn't see this particular model listed on the
>> hardware page, but was curious if anyone might be using it anyway.
>>
>> I'm guess this is probably a no, but thought I'd ask anyway.
>>
>> Thanks in advance,
>>
>> // Ted
>>
>> --
>> 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] Sun altitude at different date e time

[Thomas Keffer]

I believe you've found a bug!

Give this version of almanac.py

a try and see if it does any better. With it, you should be able to specify

$almanac($almanac_time=$almanac.sun.transit.raw).sun.alt


We should probably document this feature as well. I assume you found it by
poking around the source code?

-tk

On Fri, Dec 29, 2017 at 9:23 AM, stefano siega 
wrote:

> Hi all,
> can you tell me how i have to use almanac to know the altitude of the sun
> at sun transit.
>
> I try: $almanac.sun.transit.alt
> and the result is an error: cheetahgenerator:  Reason: cannot find
> 'alt' while searching for 'almanac.sun.transit.alt
>
> I also try: $almanac($almanac_time=$almanac.sun.transit.raw).sun.alt
> but the result is the same of: $almanac.sun.alt
>
> Anyone have an idea?
>
> --
> 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] windrun calculation error ?

[Michael Hornsby]

Hi

I've enabled windrun and am working on back filing the database. When I 
looked through the database to compare my back filling with the actual 
calculations I find at  midnight there are two zero values for windrun.

at 12:00 windrun is zero - ok I would expect that but at 12:05 windrun is 
also zero. I would expect windrun would be the wind for the first 5 minutes 
of the day ??

Am I missing something ??

Thanks
Michael

-- 
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] Report generation breaking whenever we lose internet

[gjr80]

Hi Alec,

> I don't see anything revealing in the log file.
This doesn't mean there won't be a clue in there

> Can anyone think of something I should try?
Yep, set debug=1, stop then start weeWX, let it run for a couple of archive 
periods, drop your internet, let weeWX run for a couple more archive periods 
and then post the log from startup covering the entire period. Oh, and put your 
internet back up :)

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: inside dewpoint?

[vince]

On Friday, December 29, 2017 at 10:25:46 AM UTC-8, Greg Troxel wrote:
>
> I'm confused by this, because my LOOP packets have inside dewpoint, and 
> my config, not changed from stock, says prefer_hardware.  But, I don't 
> see inDewpoint in the archive database, only inTempt and inHumidity. 
>
>  
>

The default archive schema matches wview.

You could certainly extend the schema and add it, I'd think.
Lots of examples here in the archives for people doing that, as well as the 
Customization Guide

-- 
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] inside dewpoint?

[Greg Troxel]

I am running weewx from git master, about 4 commits behind current.
I have a Vantage Pro 2, serial datalogger, and am using NetBSD 7 i386.

First, thanks for doing such a great job.  After wiring up the logger,
time from git clone to functional was under 30 minutes and generally
things are working well.

I saw that the outside graph has temperature and dewpoint, and that
seems like the right thing to do.  There is an inside temp graph, but I
found the following missing (relative to what I want):

  1) inside humidity current/daily extremes
  2 inside humidity graph

  3) inside dewpoint on the inside temperature graph
  4) inside dewpoint current/daily extremes

1 and 2 were easy in terms of editing the Standard skin.  I haven't
tried 4 yet.

For 3, inside dewpoint, I tried to add a inDewpoint line to the
dayinside graph.  That resulted in:

Generating for all time
Traceback (most recent call last):
File "/usr/weewx/bin/weewx/reportengine.py", line 239, in run obj.start()
File "/usr/weewx/bin/weewx/reportengine.py", line 273, in start self.run()
File "/usr/weewx/bin/weewx/imagegenerator.py", line 32, in run 
self.genImages(self.gen_ts)
File "/usr/weewx/bin/weewx/imagegenerator.py", line 149, in genImages 
aggregate_interval=aggregate_interval)
File "/usr/weewx/bin/weewx/manager.py", line 512, in getSqlVectors 
aggregate_type, aggregate_interval)
File "/usr/weewx/bin/weewx/manager.py", line 775, in _getSqlVectors for _rec in 
_cursor.execute(sql_str, (startstamp, stopstamp)):
File "/usr/weewx/bin/weedb/sqlite.py", line 41, in guarded_fn raise 
weedb.NoColumnError(e)
NoColumnError: no such column: inDewpoint

I'm confused by this, because my LOOP packets have inside dewpoint, and
my config, not changed from stock, says prefer_hardware.  But, I don't
see inDewpoint in the archive database, only inTempt and inHumidity.

Thanks,
Greg

-- 
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: Oregon Scientific WMR89

[Bruno BORDAS]

Hi people,

Is there any news about this station?
Any compatible drivers ?

Thanks for the help.

Le mercredi 3 février 2016 08:53:56 UTC+1, John Devine a écrit :
>
> Hi Roger
>
> I had already cancelled and ordered a FineOffset clone from Clas Olsen 
> which also works fine ;)
>
> JD
>
> On Tuesday, February 2, 2016 at 6:45:35 PM UTC, Roger Knobbe wrote:
>>
>> Works fine with the WMR100 driver
>>
>> On Thursday, January 28, 2016 at 6:32:05 AM UTC-8, John Pugh wrote:
>>>
>>> Thanks for the tip, I just ordered one from REI.  Were you able to 
>>> define the 88 in weewx, or did you use another model's setup?  I haven't 
>>> looked yet to see if there's a description for it, but the next reply on 
>>> the forum says its not there.
>>>
>>> John
>>>
>>> On Wednesday, January 27, 2016 at 2:59:09 PM UTC-5, Roger Knobbe wrote:

 I'm using a WMR88 with a Raspberry PI. REI has them in their clearance 
 section for $56.73 US. Works just fine.


 http://www.rei.com/product/890509/oregon-scientific-semi-pro-weather-station-2014-closeout?cm_mmc=email_tran-_-shipping_conf-_-20151224-_-itemdesc=ShipmentConfirmation_Sterling=19314826


 On Sunday, January 24, 2016 at 1:09:51 AM UTC-8, John Devine wrote:
>
> Hi
>
> I am thinking of buying the Oregon Scientific WMR89 for use with weewx, 
> is anyone else doing similar here? Is there a better weather station 
> around 
> the £120 mark in the UK?
>
> Thanks
>
> JohnnyD
>


-- 
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] Report generation breaking whenever we lose internet

[Alec Bennett]

Whenever we lose internet for a moment our installation of weeWX stops
updating it's reports. It'll still upload the reports every 5 minutes, but
they're outdated.

Details and symptoms:

- using a Vantage Pro2

- the Vantage Pro still sends it's data, as the real time gauge (RTG) still
works

- weeWX still uploads files every 5 minutes, but they're old reports

- the "generated time" timestamp ($current) doesn't update. It shows the
date of the last successful report from before the internet outage.

The way I've been fixing it is to run wee_device --clear_memory. That
works, but I lose a lot of data, and I get downtime until running that
command.

I don't see anything revealing in the log file.

Can anyone think of something I should try?

And/or is there a way to generate the data from the loop data itself (the
data the RTG is using), as opposed to downloading it from the console in
bulk?

Thanks for any help.

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

Re: [weewx-user] Anyone using the La Crosse 330-2315 Professional Weather Station with weewx

[Ted Bevenour]

Oh, very interesting! Thanks so much for the link, I'll see what I can come 
up with. 

On Friday, December 29, 2017 at 11:31:22 AM UTC-6, ln77 wrote:
>
> I don’t see any interface for getting the data from that console, other 
> than its wifi that appears to be specialized to posting the data to weather 
> underground, so it doesn’t support weewx in the usual way.
>
> But there’s hope! I ran across this posting on the wxforum Lacrosse topic 
> https://www.wxforum.net/index.php?topic=30932.msg335582#msg335582 from 
> someone who’s doing what you want to do, by sniffing the data.  I’d assume 
> that means the console is configured to post to weather underground, with 
> some code on the RPi sniffing the network connection and extracting the 
> data.  Not sure if this was discussed on this forum but you might contact 
> the author directly.
>
>   -Les
>
>
>
> On 29 Dec 2017, at 8:54, Ted Bevenour  
> wrote:
>
> So Santa brought me this station 
> 
>  
> for xmas this year... I'd like to run weewx on a RPi and access the 
> stations data that way. I didn't see this particular model listed on the 
> hardware page, but was curious if anyone might be using it anyway.   
>
> I'm guess this is probably a no, but thought I'd ask anyway.  
>
> Thanks in advance,   
>
> // Ted
>
> -- 
> 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] twitter extension: Able to insert a return/new line?

[Chris Alemany]

No luck. Not parsed. :(

Hourly Auto-Tweet 09:35 Dec 29 2017:  T: 2.2ºC D: 2.2ºC W: * 0.0kph 
gusting to 0.0kph H: 100% P: 1013.92hPa Rain 0.25mm Rain Rate: 0.0mm/hr 
Chill:2.2ºC HIndex:2.2ºC Solar: 10W/m2 UV: 0

On Friday, December 29, 2017 at 6:48:14 AM UTC-8, Andrew Milner wrote:
>
> Try and insert  for the newline
>
>
>
> On Friday, 29 December 2017 15:35:10 UTC+2, Chris Alemany wrote:
>
>> Thanks for the mental push on ‘the whole twitter section”. I’ve figured 
>> out the day rain issue. 
>>
>> I was using METRIC rather than METRICWX so dayRain was reporting in cm 
>> rather than mm.  Since it was a small amount of rain… it was reporting 
>> 0.0cm.  We’ve subsequently had almost 20mm of rain today, which means there 
>> is enough to notice the units mixup.
>>
>> Here is the successful wview.conf including the formatting used for the 
>> tweet below:
>>
>> station = Hourly Auto-Tweet
>> unit_system = METRICWX
>> post_interval = 3600
>> format_None = *
>> 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:%.2f}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;
>>
>> https://twitter.com/Auto_AlberniWx/status/946581641299771392
>>
>> So that is good.
>>
>> Unfortunately, I have not found a solution to the original request of 
>> inserting a new line. But I am willing to let it go and chalk it up to a 
>> limitation of twython. :)
>>
>> Thank you all for your help and suggestions.
>>
>> Chris
>>
>>
>>
>> On Dec 28, 2017, at 6:40 PM, Thomas Keffer  wrote:
>>
>> 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.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 

Re: [weewx-user] Anyone using the La Crosse 330-2315 Professional Weather Station with weewx

[Les Niles]

I don’t see any interface for getting the data from that console, other than 
its wifi that appears to be specialized to posting the data to weather 
underground, so it doesn’t support weewx in the usual way.

But there’s hope! I ran across this posting on the wxforum Lacrosse topic 
https://www.wxforum.net/index.php?topic=30932.msg335582#msg335582 
 from 
someone who’s doing what you want to do, by sniffing the data.  I’d assume that 
means the console is configured to post to weather underground, with some code 
on the RPi sniffing the network connection and extracting the data.  Not sure 
if this was discussed on this forum but you might contact the author directly.

  -Les



> On 29 Dec 2017, at 8:54, Ted Bevenour  wrote:
> 
> So Santa brought me this station 
> 
>  for xmas this year... I'd like to run weewx on a RPi and access the stations 
> data that way. I didn't see this particular model listed on the hardware 
> page, but was curious if anyone might be using it anyway.
> 
> I'm guess this is probably a no, but thought I'd ask anyway.
> 
> Thanks in advance,
> 
> // Ted
> 
> --
> 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.


signature.asc
Description: Message signed with OpenPGP

[weewx-user] Sun altitude at different date e time

[stefano siega]

Hi all,
can you tell me how i have to use almanac to know the altitude of the sun 
at sun transit.

I try: $almanac.sun.transit.alt
and the result is an error: cheetahgenerator:  Reason: cannot find 
'alt' while searching for 'almanac.sun.transit.alt

I also try: $almanac($almanac_time=$almanac.sun.transit.raw).sun.alt
but the result is the same of: $almanac.sun.alt

Anyone have an idea?

-- 
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] Anyone using the La Crosse 330-2315 Professional Weather Station with weewx

[Ted Bevenour]

So Santa brought me this station 
 
for xmas this year... I'd like to run weewx on a RPi and access the 
stations data that way. I didn't see this particular model listed on the 
hardware page, but was curious if anyone might be using it anyway.   

I'm guess this is probably a no, but thought I'd ask anyway.  

Thanks in advance,   

// Ted

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

[Andrew Milner]

Try and insert  for the newline



On Friday, 29 December 2017 15:35:10 UTC+2, Chris Alemany wrote:

> Thanks for the mental push on ‘the whole twitter section”. I’ve figured 
> out the day rain issue. 
>
> I was using METRIC rather than METRICWX so dayRain was reporting in cm 
> rather than mm.  Since it was a small amount of rain… it was reporting 
> 0.0cm.  We’ve subsequently had almost 20mm of rain today, which means there 
> is enough to notice the units mixup.
>
> Here is the successful wview.conf including the formatting used for the 
> tweet below:
>
> station = Hourly Auto-Tweet
> unit_system = METRICWX
> post_interval = 3600
> format_None = *
> 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:%.2f}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;
>
> https://twitter.com/Auto_AlberniWx/status/946581641299771392
>
> So that is good.
>
> Unfortunately, I have not found a solution to the original request of 
> inserting a new line. But I am willing to let it go and chalk it up to a 
> limitation of twython. :)
>
> Thank you all for your help and suggestions.
>
> Chris
>
>
>
> On Dec 28, 2017, at 6:40 PM, Thomas Keffer  
> wrote:
>
> 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.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:
>>

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

[Chris Alemany]

Thanks for the mental push on ‘the whole twitter section”. I’ve figured out the 
day rain issue. 

I was using METRIC rather than METRICWX so dayRain was reporting in cm rather 
than mm.  Since it was a small amount of rain… it was reporting 0.0cm.  We’ve 
subsequently had almost 20mm of rain today, which means there is enough to 
notice the units mixup.

Here is the successful wview.conf including the formatting used for the tweet 
below:

station = Hourly Auto-Tweet
unit_system = METRICWX
post_interval = 3600
format_None = *
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:%.2f}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;

https://twitter.com/Auto_AlberniWx/status/946581641299771392

So that is good.

Unfortunately, I have not found a solution to the original request of inserting 
a new line. But I am willing to let it go and chalk it up to a limitation of 
twython. :)

Thank you all for your help and suggestions.

Chris



> On Dec 28, 2017, at 6:40 PM, Thomas Keffer  wrote:
> 
> 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.alberniweather.ca 
> https://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 

[weewx-user] Re: Redundant and self synchronizing database between two systems - which approach (MQTT ?) ?

[Markus]

Hello Tom,

many thanks for your help. 

I read the thread and did some further research.
The data collecting script on the RasPi at garden writes all data to a CSV 
file. I will read this CSV file over LAN into the weeWx instance at the 
server.

If the server with weeWx is down, but data collecting on RasPi at garden 
goes on:
Do you know about a CSV fileparser for weeWx which can automatically read 
in a archive CSV file, if some data is missing?
How to get in weeWx the timestamp from the last successful saved data?

Regards
Markus

-- 
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] Redundant and self synchronizing database between two systems - which approach (MQTT ?) ?

[Markus]

Hello Tom,

many thanks for your help. 

I read the thread and did some further research.
The data collecting script on the RasPi at garden writes all data to a CSV 
file. I will read this CSV file over LAN into the weeWx instance at the 
server.

If the server with weeWx is down, but data collecting on RasPi at garden 
goes on:
Do you know about a CSV fileparser for weeWx which can automatically read 
in a archive CSV file, if some data is missing?

Regards
Markus

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