[weewx-user] dirplot.gif request (wind rose as a scatter plot)

[Your Name Here]

I started using Weather Display back in 2007 and it served me well until 
three years ago. In my search for options I discovered weewx and I have 
been quite pleased with it.

Ever since that switch-over, I have been wishing for the wind speed and 
direction radial graph Weather Display provides (see dirplot.gif 

 and dirplot.gif )., 
though 

At a glance I could quickly understand the wind direction trends (since 
it's based on a compass, it's easier/faster than daywinddir or daywindvec 
for me) and speed (it uses many steps to transition from white to pink to 
red as the wind speed increases). 

This has been mentioned before (see this 
), but 
I haven't found anything else about it. I do remember seeing it on a weewx 
wish list sometime back but that disappeared. I found something here 
 but I 
haven't tried it or figured out if it yields what I want. 

Here are some more examples: Piwnice weather 
 and this one shows the math 
 (MathWorks: see the 
functions and examples, they come from a Norwegian 
 site).

I am not looking for this style 
,
 
just the one from MathWorks 

 (nice 
example!).

Can someone help me with this, please?

Thanks in advance.


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

Re: [weewx-user] one computer to retrieve/store data, another to process/generate reports

[Your Name Here]

Okay, since my attempts aren't showing but this is:

 I am still trying to figure out how to get a wind rose scatter plot like 
Weather Display has (like this 

 and this ). 

This MathWorks site has an entry 

 for 
the math to make a very nice wind rose scatter plot 

. 

Can someone please help me out?

And if someone can explain why my two topic posts haven't shown, that would 
be nice to know, too.

Thanks.

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

Re: [weewx-user] one computer to retrieve/store data, another to process/generate reports

[Your Name Here]

I have tried to post a question, but it hasn't shown up. Since my first 
attempt hadn't shown in 12 hours, I made a new post. That doesn't show, 
either.

This is a test to see if a reply will show...

-- 
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: Seasons Skin timestamps

[Mark Jenks]

Thanks, I didn't even see those things.  Now I do.

As for the other one, If I click on month, it shows me the daily.  It's 
been so long I forgot about it.  :)

On Tuesday, April 9, 2019 at 6:51:13 PM UTC-5, mwall wrote:
>
>
>
> On Tuesday, April 9, 2019 at 7:43:24 PM UTC-4, Mark Jenks wrote:
>>
>> Why was the time removed from daily for the highs and lows?   Any way to 
>> bring them back without going back to Standard?
>>
>  
> put the cursor over the value.  or click on the 'High/Low' text to see it 
> all at once.
>
>
> Also, is there a way to see hourly stats instead of just Weekly or Monthly?
>>
>
>  not sure what you're asking for.  the 'day' plots show that information - 
> just look at the vertical line above each hour.
>
>

-- 
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: Seasons Skin timestamps

[mwall]

On Tuesday, April 9, 2019 at 7:43:24 PM UTC-4, Mark Jenks wrote:
>
> Why was the time removed from daily for the highs and lows?   Any way to 
> bring them back without going back to Standard?
>
 
put the cursor over the value.  or click on the 'High/Low' text to see it 
all at once.


Also, is there a way to see hourly stats instead of just Weekly or Monthly?
>

 not sure what you're asking for.  the 'day' plots show that information - 
just look at the vertical line above each hour.

-- 
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: Seasons Skin timestamps

[Mark Jenks]

Also, the Wind only shows degrees.   In Standard it show SSW, SW, W, etc 
next to it.



On Tuesday, April 9, 2019 at 6:43:24 PM UTC-5, Mark Jenks wrote:
>
> Why was the time removed from daily for the highs and lows?   Any way to 
> bring them back without going back to Standard?
>
> Also, is there a way to see hourly stats instead of just Weekly or Monthly?
>
> -Mark
>
> High Temperature
> Low Temperature 55.5°F at 02:15:21 PM
> 37.4°F at 04:51:05 AM
> High Heat Index
> Low Wind Chill 55.5°F at 02:15:21 PM
> 31.8°F at 05:58:24 AM
> High Humidity
> Low Humidity 90% at 04:04:59 AM
> 45% at 02:02:54 PM
> High Dewpoint
> Low Dewpoint 41.6°F at 11:39:02 AM
> 25.6°F at 06:34:09 PM
> High Barometer
> Low Barometer 29.945 inHg at 06:29:03 PM
> 29.801 inHg at 01:07:02 PM
>

-- 
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] Seasons Skin timestamps

[Mark Jenks]

Why was the time removed from daily for the highs and lows?   Any way to 
bring them back without going back to Standard?

Also, is there a way to see hourly stats instead of just Weekly or Monthly?

-Mark

High Temperature
Low Temperature 55.5°F at 02:15:21 PM
37.4°F at 04:51:05 AM
High Heat Index
Low Wind Chill 55.5°F at 02:15:21 PM
31.8°F at 05:58:24 AM
High Humidity
Low Humidity 90% at 04:04:59 AM
45% at 02:02:54 PM
High Dewpoint
Low Dewpoint 41.6°F at 11:39:02 AM
25.6°F at 06:34:09 PM
High Barometer
Low Barometer 29.945 inHg at 06:29:03 PM
29.801 inHg at 01:07:02 PM

-- 
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: RSync failing after the first upload

[Tom Mitchell]

Thanks, Vince.


On Tue, Apr 9, 2019 at 11:20 AM vince  wrote:

> On Tuesday, April 9, 2019 at 7:50:17 AM UTC-7, Tom Mitchell wrote:
>>
>> Thanks for the advice. What happens is gcp appends a new entry to my
>> known_hosts file (which already has the hostname and key I use) with a very
>> strange looking one, and then fails to connect after doing it once
>> successfully. I am happy to get it right, but at this point, I just don't
>> understand the rewrite and subsequent behavior.
>>
>>
> Yes - with strict host checking off, you'll get an additional line added
> automatically.   Normally it prompts.  This is ssh-101 (and admittedly a
> little annoying in some circumstances when you try to automate things).
> The known_hosts file containes the 'remote' computer(s) host key(s), not
> your account's key, not your 'local' computer or container's host key.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/qbvL3PX1vDg/unsubscribe.
> To unsubscribe from this group and all its topics, 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: MQTT client service - proof of concept/alpha code

[Ralph Underwood]

Bravo! Look forward to testing next month when I should have some free 
time. 



On Tuesday, April 9, 2019 at 1:45:51 PM UTC-7, bell...@gmail.com wrote:
>
> To further my WeeWX/MQTT/Python knowledge,  I have written a WeeWX 
> multi-threaded service. One thread receives the MQTT messages and puts them 
> on a queue. In the other thread, when a NEW_ARCHIVE_RECORD event is 
> received, it process the queue and updates the archive record with the data.
> Currently, processing of the queue means - take the last element and use 
> its data to update the archive record. My next big education will be to 
> develop some type of accumulation of these (essentially software 
> generation). 
> Also, the MQTT payload is expected to be json. I am hoping that other 
> formats can easily be supported by creating a subclass and overriding the 
> function that maps the MQTT payload to a WeeWX like dictionary.
> Being a proof of concept, documentation is lacking, error handling is 
> minimal, limited functionality, no install support, etc.  But, I thought 
> even in this form it might be useful/educational. 
> If interested, it can be found here, 
> https://github.com/bellrichm/weewx-addons/blob/master/user/MQTTSubscribeService.py
> - Rich
>
>

-- 
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] Stupid question / solved !

[Paul Bartholdi]

I thought it was simple, sorry.

sudo wee_database /etc/weewx/weewx.conf --drop-daily
sudo wee_database /etc/weewx/weewx.conf --rebuild-daily

I still don't understand how I got there.

What a wunderful system, where ther is always a solution not that far.

Thanks again, Paul

-- 
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: Fresh install of weewx 3.9.1 with WMR300A on RPI, Non-positive value for record field 'interval': 0.0

[mwall]

On Tuesday, April 9, 2019 at 4:42:17 PM UTC-4, Leon Shaner wrote:
>
>
> On Tuesday, April 9, 2019 at 4:06:26 PM UTC-4, Leon Shaner wrote:
>>
>> Seeing several recent posts with a similar message with WMR200, but mine 
>> is on a new install with an WMR300A.
>> Any solutions?
>>
>
looks like the wmr300 driver needs the same fix that we gave to the wmr200 
driver - reject any historical records that have a negative interval.

fixed at commit b5240b05

 

> I can't figure where that 2012 year is coming from.  My RPI has the 
> correct date and timezone for my US/Eastern local time.
> My WMR300A itself also has the correct data and timezone (E as in 
> US/Eastern). 
>

there are probably records in the station's data logger, and apparently 
some of them are corrupt.

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] Stupid question

[Paul Bartholdi]

I did some thing stupid and wrong but what, probably typing to fast...
Sorry,  what to do after this error produced when I want to restart the
service weewx (ubuntu). Paul

manager: Starting backfill of daily summaries
engine: Caught unrecoverable exception in engine:
  lastUpdate(2019-04-09 22:25:00 CEST (1554841500)) >
lastRecord(2019-04-09 22:20:00 CEST (1554841200))
  Traceback (most recent call last):
File "/usr/share/weewx/weewx/engine.py", line 884, in main
  engine = engine_class(config_dict)
File "/usr/share/weewx/weewx/engine.py", line 78, in __init__
  self.loadServices(config_dict)
File "/usr/share/weewx/weewx/engine.py", line 142, in loadServices
  self.service_obj.append(weeutil.weeutil._get_object(svc)(self,
config_dict))
File "/usr/share/weewx/weewx/engine.py", line 500, in __init__
***  self.setup_database(config_dict)
File "/usr/share/weewx/weewx/engine.py", line 617, in setup_database
  _nrecs, _ndays = dbmanager.backfill_day_summary() #
@UnusedVariable
File "/usr/share/weewx/weewx/manager.py", line 1447, in
backfill_day_summary
  timestamp_to_string(lastRecord)))
  ViolatedPrecondition: lastUpdate(2019-04-09 22:25:00 CEST
(1554841500)) > lastRecord(2019-04-09 22:20:00 CEST (1554841200))

-- 
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] Ambient Weather WS-2902A

[Adnan Mumtaz]

So the idea of running Observer IP module, it wont work too? I can place it 
up near the roof and pull a network cable from there to my apartment, I 
want to understand what changes I will need to make to make it work from my 
existing setup

On Tuesday, 9 April 2019 23:51:26 UTC+3, Scott Grayban wrote:
>
> So it must be pretty thick concrete to restrict signal. Nothing we can do 
> help on that.
>
> On Tuesday, April 9, 2019 at 1:39:12 PM UTC-7, Adnan Mumtaz wrote:
>>
>> Its all concrete here, right now I am on the top floor and the station is 
>> above me on roof and I get full signals only in the room which is under the 
>> roof where the station is installed.
>>
>> On Tuesday, 9 April 2019 21:47:25 UTC+3, Scott Grayban wrote:
>>>
>>> My WS is 40 feet up and 55 feet away from my console and my signal is 
>>> strong.
>>>
>>> Unless your roof is metal and the walls are metal you shouldn't have any 
>>> problems.
>>>
>>> On Tuesday, April 9, 2019 at 11:42:00 AM UTC-7, Tom Robertson wrote:

 Why do you say you will not be able to get the signals from the roof to 
 your station? The third floor will probably be less than 40 feet from the 
 ground.  My wireless Davis station sends signals much farther than 40 feet 
 and through several walls.
 -
 Tom

 On Apr 9, 2019, at 1:22 PM, Adnan Mumtaz  wrote:

 Hi Scott, you had been very helpful earlier, I am getting into a 
 situation soon, moving my apartment and in the new apartment I 
 will be on 
 the ground floor and the station will be at the 3rd floor which is 
 the 
 roof, there is no way I will get signals from the station to the 
 display 
 base screen, hence I have planned to buy ObserverIP module and 
 keep it near 
 the station on the 3rd floor and pull a network cable from 
 ObserverIP  to 
 my apartment  to connect it to my home network, I will also need 
 standalone 
 hygrometer module for barometer readings since I my base station 
 wont be 
 working any more and the barometer is inside the display screen. 
 Right now 
 my setup is jsut like yours, what modifications you suggest I will 
 need to 
 do to make the observerIP work. 
>>>
>>>
 If nothing works out the only solution will be to invest in a cabled 
 Davis station which will be not easy on my pocket specially the shipping 
 and custom charges.

 Will appreciate your response at your ease.

 Thank you,
 Adnan

 -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx...@googlegroups.com.
 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] Ambient Weather WS-2902A

[Scott Grayban]

So it must be pretty thick concrete to restrict signal. Nothing we can do 
help on that.

On Tuesday, April 9, 2019 at 1:39:12 PM UTC-7, Adnan Mumtaz wrote:
>
> Its all concrete here, right now I am on the top floor and the station is 
> above me on roof and I get full signals only in the room which is under the 
> roof where the station is installed.
>
> On Tuesday, 9 April 2019 21:47:25 UTC+3, Scott Grayban wrote:
>>
>> My WS is 40 feet up and 55 feet away from my console and my signal is 
>> strong.
>>
>> Unless your roof is metal and the walls are metal you shouldn't have any 
>> problems.
>>
>> On Tuesday, April 9, 2019 at 11:42:00 AM UTC-7, Tom Robertson wrote:
>>>
>>> Why do you say you will not be able to get the signals from the roof to 
>>> your station? The third floor will probably be less than 40 feet from the 
>>> ground.  My wireless Davis station sends signals much farther than 40 feet 
>>> and through several walls.
>>> -
>>> Tom
>>>
>>> On Apr 9, 2019, at 1:22 PM, Adnan Mumtaz  wrote:
>>>
>>> Hi Scott, you had been very helpful earlier, I am getting into a 
>>> situation soon, moving my apartment and in the new apartment I will 
>>> be on 
>>> the ground floor and the station will be at the 3rd floor which is 
>>> the 
>>> roof, there is no way I will get signals from the station to the 
>>> display 
>>> base screen, hence I have planned to buy ObserverIP module and keep 
>>> it near 
>>> the station on the 3rd floor and pull a network cable from 
>>> ObserverIP  to 
>>> my apartment  to connect it to my home network, I will also need 
>>> standalone 
>>> hygrometer module for barometer readings since I my base station 
>>> wont be 
>>> working any more and the barometer is inside the display screen. 
>>> Right now 
>>> my setup is jsut like yours, what modifications you suggest I will 
>>> need to 
>>> do to make the observerIP work. 
>>
>>
>>> If nothing works out the only solution will be to invest in a cabled 
>>> Davis station which will be not easy on my pocket specially the shipping 
>>> and custom charges.
>>>
>>> Will appreciate your response at your ease.
>>>
>>> Thank you,
>>> Adnan
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx...@googlegroups.com.
>>> 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] MQTT client service - proof of concept/alpha code

[bellrichm]

To further my WeeWX/MQTT/Python knowledge,  I have written a WeeWX 
multi-threaded service. One thread receives the MQTT messages and puts them on 
a queue. In the other thread, when a NEW_ARCHIVE_RECORD event is received, it 
process the queue and updates the archive record with the data.
Currently, processing of the queue means - take the last element and use its 
data to update the archive record. My next big education will be to develop 
some type of accumulation of these (essentially software generation). 
Also, the MQTT payload is expected to be json. I am hoping that other formats 
can easily be supported by creating a subclass and overriding the function that 
maps the MQTT payload to a WeeWX like dictionary.
Being a proof of concept, documentation is lacking, error handling is minimal, 
limited functionality, no install support, etc.  But, I thought even in this 
form it might be useful/educational. 
If interested, it can be found here, 
https://github.com/bellrichm/weewx-addons/blob/master/user/MQTTSubscribeService.py
- Rich

-- 
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: Fresh install of weewx 3.9.1 with WMR300A on RPI, Non-positive value for record field 'interval': 0.0

[Leon Shaner]

On Tuesday, April 9, 2019 at 4:06:26 PM UTC-4, Leon Shaner wrote:
>
> Seeing several recent posts with a similar message with WMR200, but mine 
> is on a new install with an WMR300A.
> Any solutions?
>
>
My guess is that there is some kind of a date issue.
I put in a hack in wmr300.py to return 1 second instead of None for the 
interval.

Now I see:

Apr 09 16:38:08 nixie weewx[1584]: manager: Unable to add record 2018-12-31 
06:01:00 EST (1546254060) to database 'weewx.sdb': UNIQUE constraint fail
Apr 09 16:38:08 nixie weewx[1584]: manager: Unable to add record 2012-01-01 
12:00:00 EST (1325437200) to database 'weewx.sdb': UNIQUE constraint fail

I can't figure where that 2012 year is coming from.  My RPI has the correct 
date and timezone for my US/Eastern local time.
My WMR300A itself also has the correct data and timezone (E as in 
US/Eastern). 

-- 
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] Ambient Weather WS-2902A

[Adnan Mumtaz]

Its all concrete here, right now I am on the top floor and the station is 
above me on roof and I get full signals only in the room which is under the 
roof where the station is installed.

On Tuesday, 9 April 2019 21:47:25 UTC+3, Scott Grayban wrote:
>
> My WS is 40 feet up and 55 feet away from my console and my signal is 
> strong.
>
> Unless your roof is metal and the walls are metal you shouldn't have any 
> problems.
>
> On Tuesday, April 9, 2019 at 11:42:00 AM UTC-7, Tom Robertson wrote:
>>
>> Why do you say you will not be able to get the signals from the roof to 
>> your station? The third floor will probably be less than 40 feet from the 
>> ground.  My wireless Davis station sends signals much farther than 40 feet 
>> and through several walls.
>> -
>> Tom
>>
>> On Apr 9, 2019, at 1:22 PM, Adnan Mumtaz  wrote:
>>
>> Hi Scott, you had been very helpful earlier, I am getting into a 
>> situation soon, moving my apartment and in the new apartment I will 
>> be on 
>> the ground floor and the station will be at the 3rd floor which is 
>> the 
>> roof, there is no way I will get signals from the station to the 
>> display 
>> base screen, hence I have planned to buy ObserverIP module and keep 
>> it near 
>> the station on the 3rd floor and pull a network cable from 
>> ObserverIP  to 
>> my apartment  to connect it to my home network, I will also need 
>> standalone 
>> hygrometer module for barometer readings since I my base station 
>> wont be 
>> working any more and the barometer is inside the display screen. 
>> Right now 
>> my setup is jsut like yours, what modifications you suggest I will 
>> need to 
>> do to make the observerIP work. 
>
>
>> If nothing works out the only solution will be to invest in a cabled 
>> Davis station which will be not easy on my pocket specially the shipping 
>> and custom charges.
>>
>> Will appreciate your response at your ease.
>>
>> Thank you,
>> Adnan
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com.
>> 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] Fresh install of weewx 3.9.1 with WMR300A on RPI, Non-positive value for record field 'interval': 0.0

[Leon Shaner]

Seeing several recent posts with a similar message with WMR200, but mine is 
on a new install with an WMR300A.
Any solutions?

Apr  9 16:03:20 nixie systemd[1]: Starting LSB: weewx weather system...
Apr  9 16:03:22 nixie weewx[807]: engine: Initializing weewx version 3.9.1
Apr  9 16:03:22 nixie weewx[807]: engine: Using Python 2.7.13 (default, Sep 
26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Apr  9 16:03:22 nixie weewx[807]: engine: Platform 
Linux-4.14.98+-armv6l-with-debian-9.8
Apr  9 16:03:22 nixie weewx[807]: engine: Locale is 'en_GB.UTF-8'
Apr  9 16:03:22 nixie weewx[807]: engine: pid file is /var/run/weewx.pid
Apr  9 16:03:22 nixie weewx[796]: Starting weewx weather system: weewx.
Apr  9 16:03:22 nixie systemd[1]: Started LSB: weewx weather system.
Apr  9 16:03:22 nixie weewx[811]: engine: Using configuration file 
/etc/weewx/weewx.conf
Apr  9 16:03:22 nixie weewx[811]: engine: Loading station type WMR300 
(weewx.drivers.wmr300)
Apr  9 16:03:22 nixie weewx[811]: wmr300: driver version is 0.19rc6
Apr  9 16:03:22 nixie weewx[811]: wmr300: usb info: pyusb_version=1.0.0
Apr  9 16:03:22 nixie weewx[811]: wmr300: sensor map is {'outHumidity': 
'humidity_1', 'extraDewpoint6': 'dewpoint_7', 'windchill': 'windchill', 
'extraDewpoint4': 'dewpoint_5', 'rainRate': 'rain_rate', 'heatindex': 
'heatindex_1', 'inTemp': 'temperature_0', 'windGustDir': 'wind_gust_dir', 
'extraDewpoint2': 'dewpoint_3', 'extraDewpoint3': 'dewpoint_4', 
'extraDewpoint1': 'dewpoint_2', 'barometer': 'barometer', 'extraDewpoint7': 
'dewpoint_8', 'dewpoint': 'dewpoint_1', 'extraDewpoint5': 'dewpoint_6', 
'extraHumid6': 'humidity_7', 'pressure': 'pressure', 'extraHumid4': 
'humidity_5', 'extraHumid5': 'humidity_6', 'extraHumid2': 'humidity_3', 
'extraHumid3': 'humidity_4', 'extraHumid1': 'humidity_2', 'extraTemp6': 
'temperature_7', 'extraTemp7': 'temperature_8', 'extraTemp4': 
'temperature_5', 'extraTemp5': 'temperature_6', 'extraTemp2': 
'temperature_3', 'extraTemp3': 'temperature_4', 'extraTemp1': 
'temperature_2', 'extraHeatindex3': 'heatindex_4', 'extraHeatindex2': 
'heatindex_3', 'extraHeatindex1': 'heatindex_2', 'extraHeatindex7': 
'heatindex_8', 'extraHeatindex6': 'heatindex_7', 'extraHeatindex5': 
'heatindex_6', 'extraHumid7': 'humidity_8', 'extraHeatindex4': 
'heatindex_5', 'windDir': 'wind_dir', 'outTemp': 'temperature_1', 
'windSpeed': 'wind_avg', 'inHumidity': 'humidity_0', 'windGust': 
'wind_gust'}
Apr  9 16:03:22 nixie weewx[811]: wmr300: history limit is 20%
Apr  9 16:03:23 nixie weewx[811]: wmr300: communication established: 
{'station_model': 'A004', 'latest_index': 32736, 'station_type': 'WMR300', 
'mystery1': 44, 'mystery0': 73, 'history_cleared': False, 'magic1': 88, 
'magic0': 159, 'packet_type': 87}
Apr  9 16:03:23 nixie weewx[811]: engine: StdConvert target unit is 0x1
Apr  9 16:03:23 nixie weewx[811]: wxcalculate: The following values will be 
calculated: barometer=prefer_hardware, windchill=hardware, 
dewpoint=software, appTemp=prefer_hardware, rainRate=hardware, 
windrun=prefer_hardware, heatindex=hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Apr  9 16:03:23 nixie weewx[811]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Apr  9 16:03:23 nixie weewx[811]: engine: Archive will use data binding 
wx_binding
Apr  9 16:03:23 nixie weewx[811]: engine: Record generation will be 
attempted in 'hardware'
Apr  9 16:03:23 nixie weewx[811]: engine: Using archive interval of 300 
seconds (specified in weewx configuration)
Apr  9 16:03:23 nixie weewx[811]: manager: Created and initialized table 
'archive' in database 'weewx.sdb'
Apr  9 16:03:23 nixie weewx[811]: manager: Created daily summary tables
Apr  9 16:03:24 nixie weewx[811]: engine: Using binding 'wx_binding' to 
database 'weewx.sdb'
Apr  9 16:03:24 nixie weewx[811]: manager: Starting backfill of daily 
summaries
Apr  9 16:03:24 nixie weewx[811]: restx: StationRegistry: Registration not 
requested.
Apr  9 16:03:24 nixie weewx[811]: restx: Wunderground-RF: Data for station 
KMIDEARB5 will be posted
Apr  9 16:03:24 nixie weewx[811]: restx: PWSweather: Posting not enabled.
Apr  9 16:03:24 nixie weewx[811]: restx: CWOP: Posting not enabled.
Apr  9 16:03:24 nixie weewx[811]: restx: WOW: Posting not enabled.
Apr  9 16:03:24 nixie weewx[811]: restx: AWEKAS: Posting not enabled.
Apr  9 16:03:24 nixie weewx[811]: engine: Starting up weewx version 3.9.1
Apr  9 16:03:24 nixie weewx[811]: wmr300: reading records since *** N/A 
*** (N/A   ) (last_index=31 latest_index=32736)
Apr  9 16:03:24 nixie weewx[811]: wmr300: possible missed rain event: 
new=16645.89 old=None
Apr  9 16:03:24 nixie weewx[811]: wmr300: rain=None rain_total=16645.89 
last_rain=None
Apr  9 16:03:24 nixie weewx[811]: manager: Added record 2012-01-01 12:00:00 
EST (1325437200) to database 'weewx.sdb'

Re: [weewx-user] Ambient Weather WS-2902A

[Scott Grayban]

My WS is 40 feet up and 55 feet away from my console and my signal is 
strong.

Unless your roof is metal and the walls are metal you shouldn't have any 
problems.

On Tuesday, April 9, 2019 at 11:42:00 AM UTC-7, Tom Robertson wrote:
>
> Why do you say you will not be able to get the signals from the roof to 
> your station? The third floor will probably be less than 40 feet from the 
> ground.  My wireless Davis station sends signals much farther than 40 feet 
> and through several walls.
> -
> Tom
>
> On Apr 9, 2019, at 1:22 PM, Adnan Mumtaz > 
> wrote:
>
> Hi Scott, you had been very helpful earlier, I am getting into a situation 
> soon, moving my apartment and in the new apartment I will be on the 
> ground 
> floor and the station will be at the 3rd floor which is the roof, 
> there is 
> no way I will get signals from the station to the display base 
> screen, 
> hence I have planned to buy ObserverIP module and keep it near the 
> station 
> on the 3rd floor and pull a network cable from ObserverIP  to my 
> apartment  
> to connect it to my home network, I will also need standalone 
> hygrometer 
> module for barometer readings since I my base station wont be working 
> any 
> more and the barometer is inside the display screen. Right now my 
> setup is 
> jsut like yours, what modifications you suggest I will need to do to 
> make 
> the observerIP work. 


> If nothing works out the only solution will be to invest in a cabled Davis 
> station which will be not easy on my pocket specially the shipping and 
> custom charges.
>
> Will appreciate your response at your ease.
>
> Thank you,
> Adnan
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx...@googlegroups.com .
> 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] Ambient Weather WS-2902A

[Tom Robertson]

Why do you say you will not be able to get the signals from the roof to your 
station? The third floor will probably be less than 40 feet from the ground.  
My wireless Davis station sends signals much farther than 40 feet and through 
several walls.
-
Tom

> On Apr 9, 2019, at 1:22 PM, Adnan Mumtaz  wrote:
> 
> Hi Scott, you had been very helpful earlier, I am getting into a situation 
> soon, moving my apartment and in the new apartment I will be on the ground 
> floor and the station will be at the 3rd floor which is the roof, there is no 
> way I will get signals from the station to the display base screen, hence I 
> have planned to buy ObserverIP module and keep it near the station on the 3rd 
> floor and pull a network cable from ObserverIP  to my apartment  to connect 
> it to my home network, I will also need standalone hygrometer module for 
> barometer readings since I my base station wont be working any more and the 
> barometer is inside the display screen. Right now my setup is jsut like 
> yours, what modifications you suggest I will need to do to make the 
> observerIP work.
> 
> If nothing works out the only solution will be to invest in a cabled Davis 
> station which will be not easy on my pocket specially the shipping and custom 
> charges.
> 
> Will appreciate your response at your ease.
> 
> Thank you,
> Adnan
> 
> -- 
> 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] Ambient Weather WS-2902A

[Adnan Mumtaz]

>
> Hi Scott, you had been very helpful earlier, I am getting into a situation 
 soon, moving my apartment and in the new apartment I will be on the 
 ground 
 floor and the station will be at the 3rd floor which is the roof, 
 there is 
 no way I will get signals from the station to the display base screen, 
 hence I have planned to buy ObserverIP module and keep it near the 
 station 
 on the 3rd floor and pull a network cable from ObserverIP  to my 
 apartment  
 to connect it to my home network, I will also need standalone 
 hygrometer 
 module for barometer readings since I my base station wont be working 
 any 
 more and the barometer is inside the display screen. Right now my 
 setup is 
 jsut like yours, what modifications you suggest I will need to do to 
 make 
 the observerIP work. 
>>>
>>>
If nothing works out the only solution will be to invest in a cabled Davis 
station which will be not easy on my pocket specially the shipping and 
custom charges.

Will appreciate your response at your ease.

Thank you,
Adnan

-- 
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: make check up on data in order to auto-restart the weather console

[Andrew Milner]

Yes, you need to change weewx.conf to
specify the binding in [DataBindings] [[wx_binding]] database = x 
where xx is an entry in [Databases] below

and you specify the database in [Databases]



On Tuesday, 9 April 2019 20:06:12 UTC+3, Pietro Benotto wrote:
>
> Thanks to everyone,
> I think something like this is what I searched.
>
>   
>  
> --cit.
>
>RXCHECK=$(mysql --batch --column-names=0 -uweewx -pweewx 
> --database=weewx --execute="select rxCheckPercent from archive WHERE 
> dateTime=(select MAX(dateTime) from archive); ");
>RXCHECK=`echo $RXCHECK | awk '{printf("%.1f", $1)}'`
>echo $RXCHECK
>
>   
>  
> --
>
> You converted the standard .sdb weewx DB into a mysql one, didn't you? 
> After the conversion of the DB how it's possible to change weewx parameters 
> in order to add new data into the correct table? I think it would try to 
> build the weewx.sdb again, if no changes in the conf file are made.
>
> PB
>

-- 
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: make check up on data in order to auto-restart the weather console

[Pietro Benotto]

Thanks to everyone,
I think something like this is what I searched.

  
 
--cit.

   RXCHECK=$(mysql --batch --column-names=0 -uweewx -pweewx 
--database=weewx --execute="select rxCheckPercent from archive WHERE 
dateTime=(select MAX(dateTime) from archive); ");
   RXCHECK=`echo $RXCHECK | awk '{printf("%.1f", $1)}'`
   echo $RXCHECK

  
 
--

You converted the standard .sdb weewx DB into a mysql one, didn't you? 
After the conversion of the DB how it's possible to change weewx parameters 
in order to add new data into the correct table? I think it would try to 
build the weewx.sdb again, if no changes in the conf file are made.

PB

-- 
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: RSync failing after the first upload

[vince]

On Tuesday, April 9, 2019 at 7:50:17 AM UTC-7, Tom Mitchell wrote:
>
> Thanks for the advice. What happens is gcp appends a new entry to my 
> known_hosts file (which already has the hostname and key I use) with a very 
> strange looking one, and then fails to connect after doing it once 
> successfully. I am happy to get it right, but at this point, I just don't 
> understand the rewrite and subsequent behavior.
>
>
Yes - with strict host checking off, you'll get an additional line added 
automatically.   Normally it prompts.  This is ssh-101 (and admittedly a 
little annoying in some circumstances when you try to automate things). 
The known_hosts file containes the 'remote' computer(s) host key(s), not 
your account's key, not your 'local' computer or container's host key.

-- 
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: RSync failing after the first upload

[Tom Mitchell]

Thanks for the advice. What happens is gcp appends a new entry to my
known_hosts file (which already has the hostname and key I use) with a very
strange looking one, and then fails to connect after doing it once
successfully. I am happy to get it right, but at this point, I just don't
understand the rewrite and subsequent behavior.

On Tue, Apr 9, 2019 at 10:45 AM vince  wrote:

> On Tuesday, April 9, 2019 at 1:57:25 AM UTC-7, Tom Mitchell wrote:
>>
>> Thanks @gary for the followup. I turned off stricthostkeychecking in the
>> .ssh/config file which resolved it. I don't know exactly this cloud server
>> does this, but it works and I am not going to dig too deep on it.
>>
>>
>>
> That's usually a really bad idea.  Strict host checking tries to make sure
> that you're not connecting to an imposter computer using the same ip
> address as the one you're trying to connect to.   What rsync is doing is
> saying "hey - I don't know who that remote system is, is this ok?" and
> asking for verification.   Very normal ssh behavior.
>
> If you're building a docker container to run weewx, you could have your
> container build proces create its ~/.ssh/known_hosts file with the host key
> for the system you typically connect to, if you have stable host keys on
> the system you're rsync'ing to (which is usually the case).  That's a far
> more secure way of doing things.
>
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/qbvL3PX1vDg/unsubscribe.
> To unsubscribe from this group and all its topics, 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: RSync failing after the first upload

[vince]

On Tuesday, April 9, 2019 at 1:57:25 AM UTC-7, Tom Mitchell wrote:
>
> Thanks @gary for the followup. I turned off stricthostkeychecking in the 
> .ssh/config file which resolved it. I don't know exactly this cloud server 
> does this, but it works and I am not going to dig too deep on it.
>
>
>
That's usually a really bad idea.  Strict host checking tries to make sure 
that you're not connecting to an imposter computer using the same ip 
address as the one you're trying to connect to.   What rsync is doing is 
saying "hey - I don't know who that remote system is, is this ok?" and 
asking for verification.   Very normal ssh behavior.

If you're building a docker container to run weewx, you could have your 
container build proces create its ~/.ssh/known_hosts file with the host key 
for the system you typically connect to, if you have stable host keys on 
the system you're rsync'ing to (which is usually the case).  That's a far 
more secure way of doing things.



-- 
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: Crash with log info

[Ron]

Re: the added loginf, I wanted to let this version run for several days. If 
it is stable up to then I plan to remove the unnecessary loginf. Congrats 
on the new grandkid! And thanks again for creating the HP1000 driver. 

On Monday, April 8, 2019 at 10:48:19 PM UTC-5, vk3...@gmail.com wrote:
>
> I'm not sure what this means but if it works then great.
>
> On Monday, April 8, 2019 at 8:59:13 PM UTC+10, Ron wrote:
>>
>> Oh, in my repo I also changed the formatting of the installation steps in 
>> the README file. Githubs markdown was smushing them all onto a single line 
>> and eating the portions of the commands saying to insert the HP1000 
>> directory.
>
>
> You have uncovered a bug in my code that has been there all along with 
> regard to the 'sleep' command. As I mentioned above, there is a 
> 'sleep'command in the genLoopPackates function that stops the weather 
> station being accessed too frequently. in *that* call to 'sleep' I *do* 
> prefix it with 'time.' but in all other cases I don't. I guess it shows 
> that I hadn't checked all of the error code paths well enough!!!
>
> The only word of warning I'd make is that anyone using your code will get 
> the additional 'loginf' messages as it is reading in the history 
> packets.(BTW, in line 785 of your file, the 'loginf' is after the 'raise' 
> so probably won;t get actioned.)
>
> Thanks for the assistance on this - I'll update my repository over the 
> next few days as time permits (my daughter is about to make me a 'Grannie' 
> again).
>
> Susan
>

-- 
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] dirplot.gif

[Your Name Here]

I used Weather Display for years but switched to weewx a couple of years 
ago. I really appreciate that weewx is open source and can be customized.

But in regards to Weather Display, I really miss the wind speed and 
direction radial graph it provides (see dirplot.gif 

 and dirplot.gif ). At 
a glance I could quickly understand the wind direction trends (since it's 
based on a compass, it's easier/faster than daywinddir or daywindvec for 
me) and speed (it uses many steps to transition from white to pink to red 
as the wind speed increases). This has been mentioned before (see this 
), but 
I haven't found anything else about it. I do remember seeing it on a weewx 
wish list sometime back but that disappeared. I found something here 
 but I 
haven't tried it or figured out if it yields what I want. 

Please see this (colorized)  
example 
and especially this (includes math) 
,
 
too.

Is there anyone else wishing for this? I am hoping someone can implement it.

Thanks in advance.

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

[weewx-user] Re: Error on upgrading to 3.9.1

[robinqrf]

Ok brilliant, thanks!

(Sorry, I am a complete novice at Python)


On Tuesday, April 9, 2019 at 10:22:29 AM UTC+2, gjr80 wrote:
>
> Hi,
>
> Other than the obvious:
>
> Apr  9 09:47:48 raspberrypi weewx[22241]: File 
> "/home/weewx/bin/user/glowworm.py", line 40, in __init__
> Apr  9 09:47:48 raspberrypi weewx[22241]:   self.archive_thread 
> = GWThread(self.archive_queue, _manager_dict, *_config_dict)
> Apr  9 09:47:48 raspberrypi weewx[22241]:   TypeError: __init__() 
> got an unexpected keyword argument 'log_success'
>
> which tells us that class GWThread received an unexpected keyword 
> argument named 'log_success' as part of its initialisation, it's 
> impossible to say much without knowing anything about 
> /home/weewx/bin/user/glowworm.py. glowworm.py is not part of the WeeWX 
> code base so you might need to seek out the author or give us some further 
> details.
>
> Gary
>
> On Tuesday, 9 April 2019 17:51:26 UTC+10, robi...@gmail.com wrote:
>>
>> Good  morning
>>
>> I have just upgrade 3.7.0 to 3.9.1 on a raspberry pi
>>
>> I get the following in the log now:
>>
>> Apr  9 09:47:48 raspberrypi weewx[22241]: engine: Caught unrecoverable 
>> exception in engine:
>> Apr  9 09:47:48 raspberrypi weewx[22241]:   __init__() got an 
>> unexpected keyword argument 'log_success'
>> Apr  9 09:47:48 raspberrypi weewx[22241]:   Traceback (most 
>> recent call last):
>> Apr  9 09:47:48 raspberrypi weewx[22241]: File 
>> "/home/weewx/bin/weewx/engine.py", line 884, in main
>> Apr  9 09:47:48 raspberrypi weewx[22241]:   engine = 
>> engine_class(config_dict)
>> Apr  9 09:47:48 raspberrypi weewx[22241]: File 
>> "/home/weewx/bin/weewx/engine.py", line 78, in __init__
>> Apr  9 09:47:48 raspberrypi weewx[22241]:  
>>  self.loadServices(config_dict)
>> Apr  9 09:47:48 raspberrypi weewx[22241]: File 
>> "/home/weewx/bin/weewx/engine.py", line 142, in loadServices
>> Apr  9 09:47:48 raspberrypi weewx[22241]:  
>>  self.service_obj.append(weeutil.weeutil._get_object(svc)(self, 
>> config_dict))
>> Apr  9 09:47:48 raspberrypi weewx[22241]: File 
>> "/home/weewx/bin/user/glowworm.py", line 40, in __init__
>> Apr  9 09:47:48 raspberrypi weewx[22241]:  
>>  self.archive_thread = GWThread(self.archive_queue, _manager_dict, 
>> **_config_dict)
>> Apr  9 09:47:48 raspberrypi weewx[22241]:   TypeError: __init__() 
>> got an unexpected keyword argument 'log_success'
>> Apr  9 09:47:48 raspberrypi weewx[22241]:   Exiting.
>> ^
>>
>> Any ideas?
>>
>

-- 
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: RSync failing after the first upload

[gjr80]

Well you're way ahead of me. Main thing is it works.

Gary

On Tuesday, 9 April 2019 18:57:25 UTC+10, Tom Mitchell wrote:
>
> Thanks @gary for the followup. I turned off stricthostkeychecking in the 
> .ssh/config file which resolved it. I don't know exactly this cloud server 
> does this, but it works and I am not going to dig too deep on it.
>
> Thanks again.
>
>
>
> On Mon, Apr 8, 2019 at 10:50 PM gjr80 > 
> wrote:
>
>> Hi,
>>
>> Certainly seen the same message before but can't say it was under the 
>> same circumstances though. No ssh/rsync expert but just thinking aloud as 
>> to what you could do; have you tried running rsync (repeatedly) from the 
>> command line with the same credentials so you can see/deal with anything it 
>> throws up? Have you tried removing the cached key for foo.bar.com with:
>>
>> $ ssh-keygen -R 192.168.1.123
>>
>> Gary
>>
>>
>> On Sunday, 7 April 2019 06:26:33 UTC+10, Tom Mitchell wrote:
>>>
>>> Hello,
>>>
>>> weewx 3.8.2 running in a Docker container. Connecting the the database 
>>> just fine and using the Simulator. I have rsync configured to upload to a 
>>> cloud host.
>>>
>>> First time through, the report upload works fine:
>>>
>>> weewx[9]: reportengine: Running report RSYNC
>>> weewx[9]: reportengine: Found configuration file 
>>> /home/weewx/skins/Rsync/skin.conf for report RSYNC
>>> weewx[9]: manager: Added record 2019-04-06 16:05:17 EDT (1554581117) to 
>>> database 'weewx_local'
>>> LOOP:   2019-04-06 16:05:17 EDT (1554581117) altimeter: 32.3940721833, 
>>> appTemp: 28.369127419, barometer: 32.3429914465, cloudbase: 1295.87222115, 
>>> dateTime: 1554581117, dewpoint: 27.1243263624, heatindex: 32.5973641355, 
>>> humidex: 32.5973641355, inDewpoint: 31.0794006064, inHumidity: 
>>> 29.999657861, inTemp: 63.0001710695, maxSolarRad: 495.258619499, 
>>> outHumidity: 79.9997433946, outTemp: 32.5973641355, pressure: 
>>> 32.3429914465, radiation: 230.36959363, rain: 0, rainRate: 0, usUnits: 1, 
>>> UV: 3.22517431082, windchill: 32.5973641355, windDir: 359.998460368, 
>>> windGust: 5.13210704991e-05, windGustDir: 359.998460368, windSpeed: 
>>> 4.27675587487e-05
>>> weewx[9]: rsyncupload: rsync'd 160 files (271,814 bytes) in 2.10 seconds
>>>
>>> But on the subsequent passes, it acts like it doesn't recognize the 
>>> upload host:
>>>
>>> weewx[9]: reportengine: Running report RSYNC
>>> weewx[9]: reportengine: Found configuration file 
>>> /home/weewx/skins/Rsync/skin.conf for report RSYNC
>>> The authenticity of host 'foo.bar.com (a.b.c.d)' can't be established.
>>> ECDSA key fingerprint is a8:17:90:cd:08:5d:3f:84:8d:b3:9d:91:3d:e0:e2:68.
>>> Are you sure you want to continue connecting (yes/no)? weewx[9]: 
>>> manager: Added record 2019-04-06 16:10:17 EDT (1554581417) to database 
>>> 'weewx_local'
>>> LOOP:   2019-04-06 16:10:17 EDT (1554581417) altimeter: 32.3939674154, 
>>> appTemp: 28.1327127704, barometer: 32.3428868355, cloudbase: 1294.87161178, 
>>> dateTime: 1554581417, dewpoint: 26.9178545608, heatindex: 32.3864896527, 
>>> humidex: 32.38648965
>>>
>>> I do have a known_hosts file in /home/weewx/.ssh
>>> I am able to ssh in as the username configured in weewx without being 
>>> prompted.
>>>
>>> [[RSYNC]]
>>> # rsync'ing to a webserver is treated as just another report
>>> skin = Rsync
>>>
>>> # If you wish to use rsync, you must configure passwordless ssh using
>>> # public/private key authentication from the user account that weewx
>>> # runs as to the user account on the remote machine where the files
>>> # will be copied.
>>> #
>>> # The following three lines determine where files will be sent.
>>> server = foo.bar.com
>>> path = /home/tom/html/local/
>>> user = tom
>>>
>>> # Rsync can be configured to remove files from the remote server if
>>> # they don't exist under HTML_ROOT locally. USE WITH CAUTION: if you
>>> # make a mistake in the remote path, you could could unintentionally
>>> # cause unrelated files to be deleted. Set to 1 to enable remote file
>>> # deletion, zero to allow files to accumulate remotely.
>>> delete = 0
>>>
>>> Curious of anyone has ever seen this before.
>>>
>>> Thanks in advance.
>>>
>>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/qbvL3PX1vDg/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx...@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: RSync failing after the first upload

[Tom Mitchell]

Thanks @gary for the followup. I turned off stricthostkeychecking in the
.ssh/config file which resolved it. I don't know exactly this cloud server
does this, but it works and I am not going to dig too deep on it.

Thanks again.



On Mon, Apr 8, 2019 at 10:50 PM gjr80  wrote:

> Hi,
>
> Certainly seen the same message before but can't say it was under the same
> circumstances though. No ssh/rsync expert but just thinking aloud as to
> what you could do; have you tried running rsync (repeatedly) from the
> command line with the same credentials so you can see/deal with anything it
> throws up? Have you tried removing the cached key for foo.bar.com with:
>
> $ ssh-keygen -R 192.168.1.123
>
> Gary
>
>
> On Sunday, 7 April 2019 06:26:33 UTC+10, Tom Mitchell wrote:
>>
>> Hello,
>>
>> weewx 3.8.2 running in a Docker container. Connecting the the database
>> just fine and using the Simulator. I have rsync configured to upload to a
>> cloud host.
>>
>> First time through, the report upload works fine:
>>
>> weewx[9]: reportengine: Running report RSYNC
>> weewx[9]: reportengine: Found configuration file
>> /home/weewx/skins/Rsync/skin.conf for report RSYNC
>> weewx[9]: manager: Added record 2019-04-06 16:05:17 EDT (1554581117) to
>> database 'weewx_local'
>> LOOP:   2019-04-06 16:05:17 EDT (1554581117) altimeter: 32.3940721833,
>> appTemp: 28.369127419, barometer: 32.3429914465, cloudbase: 1295.87222115,
>> dateTime: 1554581117, dewpoint: 27.1243263624, heatindex: 32.5973641355,
>> humidex: 32.5973641355, inDewpoint: 31.0794006064, inHumidity:
>> 29.999657861, inTemp: 63.0001710695, maxSolarRad: 495.258619499,
>> outHumidity: 79.9997433946, outTemp: 32.5973641355, pressure:
>> 32.3429914465, radiation: 230.36959363, rain: 0, rainRate: 0, usUnits: 1,
>> UV: 3.22517431082, windchill: 32.5973641355, windDir: 359.998460368,
>> windGust: 5.13210704991e-05, windGustDir: 359.998460368, windSpeed:
>> 4.27675587487e-05
>> weewx[9]: rsyncupload: rsync'd 160 files (271,814 bytes) in 2.10 seconds
>>
>> But on the subsequent passes, it acts like it doesn't recognize the
>> upload host:
>>
>> weewx[9]: reportengine: Running report RSYNC
>> weewx[9]: reportengine: Found configuration file
>> /home/weewx/skins/Rsync/skin.conf for report RSYNC
>> The authenticity of host 'foo.bar.com (a.b.c.d)' can't be established.
>> ECDSA key fingerprint is a8:17:90:cd:08:5d:3f:84:8d:b3:9d:91:3d:e0:e2:68.
>> Are you sure you want to continue connecting (yes/no)? weewx[9]: manager:
>> Added record 2019-04-06 16:10:17 EDT (1554581417) to database 'weewx_local'
>> LOOP:   2019-04-06 16:10:17 EDT (1554581417) altimeter: 32.3939674154,
>> appTemp: 28.1327127704, barometer: 32.3428868355, cloudbase: 1294.87161178,
>> dateTime: 1554581417, dewpoint: 26.9178545608, heatindex: 32.3864896527,
>> humidex: 32.38648965
>>
>> I do have a known_hosts file in /home/weewx/.ssh
>> I am able to ssh in as the username configured in weewx without being
>> prompted.
>>
>> [[RSYNC]]
>> # rsync'ing to a webserver is treated as just another report
>> skin = Rsync
>>
>> # If you wish to use rsync, you must configure passwordless ssh using
>> # public/private key authentication from the user account that weewx
>> # runs as to the user account on the remote machine where the files
>> # will be copied.
>> #
>> # The following three lines determine where files will be sent.
>> server = foo.bar.com
>> path = /home/tom/html/local/
>> user = tom
>>
>> # Rsync can be configured to remove files from the remote server if
>> # they don't exist under HTML_ROOT locally. USE WITH CAUTION: if you
>> # make a mistake in the remote path, you could could unintentionally
>> # cause unrelated files to be deleted. Set to 1 to enable remote file
>> # deletion, zero to allow files to accumulate remotely.
>> delete = 0
>>
>> Curious of anyone has ever seen this before.
>>
>> Thanks in advance.
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/qbvL3PX1vDg/unsubscribe.
> To unsubscribe from this group and all its topics, 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: Error on upgrading to 3.9.1

[gjr80]

Hi,

Other than the obvious:

Apr  9 09:47:48 raspberrypi weewx[22241]: File 
"/home/weewx/bin/user/glowworm.py", line 40, in __init__
Apr  9 09:47:48 raspberrypi weewx[22241]:   self.archive_thread 
= GWThread(self.archive_queue, _manager_dict, *_config_dict)
Apr  9 09:47:48 raspberrypi weewx[22241]:   TypeError: __init__() 
got an unexpected keyword argument 'log_success'

which tells us that class GWThread received an unexpected keyword argument 
named 'log_success' as part of its initialisation, it's impossible to say 
much without knowing anything about /home/weewx/bin/user/glowworm.py. glow
worm.py is not part of the WeeWX code base so you might need to seek out 
the author or give us some further details.

Gary

On Tuesday, 9 April 2019 17:51:26 UTC+10, robi...@gmail.com wrote:
>
> Good  morning
>
> I have just upgrade 3.7.0 to 3.9.1 on a raspberry pi
>
> I get the following in the log now:
>
> Apr  9 09:47:48 raspberrypi weewx[22241]: engine: Caught unrecoverable 
> exception in engine:
> Apr  9 09:47:48 raspberrypi weewx[22241]:   __init__() got an 
> unexpected keyword argument 'log_success'
> Apr  9 09:47:48 raspberrypi weewx[22241]:   Traceback (most recent 
> call last):
> Apr  9 09:47:48 raspberrypi weewx[22241]: File 
> "/home/weewx/bin/weewx/engine.py", line 884, in main
> Apr  9 09:47:48 raspberrypi weewx[22241]:   engine = 
> engine_class(config_dict)
> Apr  9 09:47:48 raspberrypi weewx[22241]: File 
> "/home/weewx/bin/weewx/engine.py", line 78, in __init__
> Apr  9 09:47:48 raspberrypi weewx[22241]:  
>  self.loadServices(config_dict)
> Apr  9 09:47:48 raspberrypi weewx[22241]: File 
> "/home/weewx/bin/weewx/engine.py", line 142, in loadServices
> Apr  9 09:47:48 raspberrypi weewx[22241]:  
>  self.service_obj.append(weeutil.weeutil._get_object(svc)(self, 
> config_dict))
> Apr  9 09:47:48 raspberrypi weewx[22241]: File 
> "/home/weewx/bin/user/glowworm.py", line 40, in __init__
> Apr  9 09:47:48 raspberrypi weewx[22241]:  
>  self.archive_thread = GWThread(self.archive_queue, _manager_dict, 
> **_config_dict)
> Apr  9 09:47:48 raspberrypi weewx[22241]:   TypeError: __init__() 
> got an unexpected keyword argument 'log_success'
> Apr  9 09:47:48 raspberrypi weewx[22241]:   Exiting.
> ^
>
> Any ideas?
>

-- 
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] Error on upgrading to 3.9.1

[robinqrf]

Good  morning

I have just upgrade 3.7.0 to 3.9.1 on a raspberry pi

I get the following in the log now:

Apr  9 09:47:48 raspberrypi weewx[22241]: engine: Caught unrecoverable 
exception in engine:
Apr  9 09:47:48 raspberrypi weewx[22241]:   __init__() got an 
unexpected keyword argument 'log_success'
Apr  9 09:47:48 raspberrypi weewx[22241]:   Traceback (most recent 
call last):
Apr  9 09:47:48 raspberrypi weewx[22241]: File 
"/home/weewx/bin/weewx/engine.py", line 884, in main
Apr  9 09:47:48 raspberrypi weewx[22241]:   engine = 
engine_class(config_dict)
Apr  9 09:47:48 raspberrypi weewx[22241]: File 
"/home/weewx/bin/weewx/engine.py", line 78, in __init__
Apr  9 09:47:48 raspberrypi weewx[22241]:  
 self.loadServices(config_dict)
Apr  9 09:47:48 raspberrypi weewx[22241]: File 
"/home/weewx/bin/weewx/engine.py", line 142, in loadServices
Apr  9 09:47:48 raspberrypi weewx[22241]:  
 self.service_obj.append(weeutil.weeutil._get_object(svc)(self, 
config_dict))
Apr  9 09:47:48 raspberrypi weewx[22241]: File 
"/home/weewx/bin/user/glowworm.py", line 40, in __init__
Apr  9 09:47:48 raspberrypi weewx[22241]:   self.archive_thread 
= GWThread(self.archive_queue, _manager_dict, **_config_dict)
Apr  9 09:47:48 raspberrypi weewx[22241]:   TypeError: __init__() 
got an unexpected keyword argument 'log_success'
Apr  9 09:47:48 raspberrypi weewx[22241]:   Exiting.
^

Any ideas?

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