from:"John"

I just examined the code in /bin/weeutil/rsyncupload.py
It contains:
if self.ssh_options:
rsyncsshstring = rsyncsshstring + " " + self.ssh_options

I don’t see a how this couldn’t be including options.  Would you send your 
entire RSYNC stanza again?

> On Aug 9, 2022, at 10:32 AM, John Kline  wrote:
> 
> 
> Did you restart weewx after changing weewx.conf?
> 
>>> On Aug 9, 2022, at 10:05 AM, Dan Jones  wrote:
>>> 
>> ssh stanza removed
>> 
>> debug on 1
>> 
>> output still the same:
>> 
>> DEBUG weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', 
>> '--stats', '-e', 'ssh', '/tmp/weather34/serverdata/', 
>> 'www-data@123.123.123.123:/var/www/html/weather34/serverdata']]
>> 
>> 
>> Still ignoring ssh_options and still using IP address rather than host name.
>> 
>> Surely ssh_options wouldn't be needed if it used the host name, and then 
>> rsync would use .ssh/config with the correct host name configuration?
>> 
>> 
>>> On Tuesday, August 9, 2022 at 5:09:51 PM UTC+1 jo...@johnkline.com wrote:
>>> Oh, I didn’t notice the SSH stanza, remove that line.  ssh_options should 
>>> be directly under RSYNC.
>>> 
>>>>> On Aug 9, 2022, at 9:01 AM, bell...@gmail.com  wrote:
>>>>> 
>>>> I don’t have a [[SSH]] stanza. Try removing that.
>>> 
>>>> rich
>>>> 
>>>>> On Tuesday, 9 August 2022 at 11:53:57 UTC-4 dan.rh...@gmail.com wrote:
>>>>> Yep, correct, its the private key. 
>>>>> 
>>>>> But it looks like that whole ssh_options bit is being ignored. I can't 
>>>>> see it in the logs when I tail them. 
>>>>> 
>>>>>> On Tuesday, August 9, 2022 at 4:52:18 PM UTC+1 jo...@johnkline.com wrote:
>>>>>> -i should refer to a file that contains a private key.  Is that the case?
>>>>>> 
>>>>>>>> On Aug 9, 2022, at 8:14 AM, Dan Jones  wrote:
>>>>>>>> 
>>>>>>> My weewx.conf contains this:
>>>>>> 
>>>>>>> 
>>>>>>> [[RSYNC]]
>>>>>>> skin = Rsync
>>>>>>> HTML_ROOT = /var/www/html
>>>>>>> server = awsbox
>>>>>>> user = www-data
>>>>>>> path = /var/www/html
>>>>>>> delete = 0
>>>>>>> ssh_options = -i /root/.ssh/aws
>>>>>>> [[SSH]]
>>>>>>>ssh_options = -i /root/.ssh/aws
>>>>>>> 
>>>>>>> I have awsbox in my host file, pointing to the correct ip address
>>>>>>> 
>>>>>>> in my .ssh/config I have:
>>>>>>> 
>>>>>>> Host awsbox
>>>>>>> user www-data
>>>>>>> IdentityFile /root/.ssh/aws
>>>>>>> 
>>>>>>> 
>>>>>>> when I start the Weewx server, I get this error 
>>>>>>> 
>>>>>>> DEBUG weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', 
>>>>>>> '--stats', '-e', 'ssh', '/tmp/weather34/serverdata/', 
>>>>>>> 'www-...@123.123.123.123:/var/www/html/weather34/serverdata']]
>>>>>>> 
>>>>>>> (IP changed for security)
>>>>>>> 
>>>>>>> I can't see where the ip address is coming from. Is weewx or rsync 
>>>>>>> converting it from the host file?
>>>>>>> 
>>>>>>> Also, It seems to be ignoring the ssh_options parameter (though I could 
>>>>>>> be using the wrong) But I hope that it isn't required, as I guess that 
>>>>>>> rsync should be using the config in .ssh/config
>>>>>>> 
>>>>>>> Any help would be greatly appreciated
>>>>>>> 
>>>>>>> This is all on the latest version of Weewx
>>>>>>> 
>>>>>> 
>>>>>>> -- 
>>>>>>> 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.
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/weewx-user/e84797ff-e452-4099-bac1-e032a1f6d903n%40googlegroups.com.
>>>> 
>>>> -- 
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "weewx-user" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>> email to weewx-user+...@googlegroups.com.
>>> 
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/7a2e36e8-00fe-491e-acd7-01fca28be7a0n%40googlegroups.com.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/6ce83cde-458e-4058-917c-f8b6b10d44d6n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/540444EA-03F2-4A72-BCD0-D36E73A5D5F4%40johnkline.com.

Re: [weewx-user] RSYNC is using IP address and not host name

Did you restart weewx after changing weewx.conf?

> On Aug 9, 2022, at 10:05 AM, Dan Jones  wrote:
> 
> ssh stanza removed
> 
> debug on 1
> 
> output still the same:
> 
> DEBUG weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', 
> '--stats', '-e', 'ssh', '/tmp/weather34/serverdata/', 
> 'www-data@123.123.123.123:/var/www/html/weather34/serverdata']]
> 
> 
> Still ignoring ssh_options and still using IP address rather than host name.
> 
> Surely ssh_options wouldn't be needed if it used the host name, and then 
> rsync would use .ssh/config with the correct host name configuration?
> 
> 
>> On Tuesday, August 9, 2022 at 5:09:51 PM UTC+1 jo...@johnkline.com wrote:
>> Oh, I didn’t notice the SSH stanza, remove that line.  ssh_options should be 
>> directly under RSYNC.
>> 
 On Aug 9, 2022, at 9:01 AM, bell...@gmail.com  wrote:
 
>>> I don’t have a [[SSH]] stanza. Try removing that.
>> 
>>> rich
>>> 
 On Tuesday, 9 August 2022 at 11:53:57 UTC-4 dan.rh...@gmail.com wrote:
 Yep, correct, its the private key. 
 
 But it looks like that whole ssh_options bit is being ignored. I can't see 
 it in the logs when I tail them. 
 
> On Tuesday, August 9, 2022 at 4:52:18 PM UTC+1 jo...@johnkline.com wrote:
> -i should refer to a file that contains a private key.  Is that the case?
> 
>>> On Aug 9, 2022, at 8:14 AM, Dan Jones  wrote:
>>> 
>> My weewx.conf contains this:
> 
>> 
>> [[RSYNC]]
>> skin = Rsync
>> HTML_ROOT = /var/www/html
>> server = awsbox
>> user = www-data
>> path = /var/www/html
>> delete = 0
>> ssh_options = -i /root/.ssh/aws
>> [[SSH]]
>>ssh_options = -i /root/.ssh/aws
>> 
>> I have awsbox in my host file, pointing to the correct ip address
>> 
>> in my .ssh/config I have:
>> 
>> Host awsbox
>> user www-data
>> IdentityFile /root/.ssh/aws
>> 
>> 
>> when I start the Weewx server, I get this error 
>> 
>> DEBUG weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', 
>> '--stats', '-e', 'ssh', '/tmp/weather34/serverdata/', 
>> 'www-...@123.123.123.123:/var/www/html/weather34/serverdata']]
>> 
>> (IP changed for security)
>> 
>> I can't see where the ip address is coming from. Is weewx or rsync 
>> converting it from the host file?
>> 
>> Also, It seems to be ignoring the ssh_options parameter (though I could 
>> be using the wrong) But I hope that it isn't required, as I guess that 
>> rsync should be using the config in .ssh/config
>> 
>> Any help would be greatly appreciated
>> 
>> This is all on the latest version of Weewx
>> 
> 
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/e84797ff-e452-4099-bac1-e032a1f6d903n%40googlegroups.com.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to weewx-user+...@googlegroups.com.
>> 
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/7a2e36e8-00fe-491e-acd7-01fca28be7a0n%40googlegroups.com.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/6ce83cde-458e-4058-917c-f8b6b10d44d6n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/AE34A74C-F383-4D53-9A98-DE0812E22BDD%40johnkline.com.

Re: [weewx-user] RSYNC is using IP address and not host name

Oh, I didn’t notice the SSH stanza, remove that line.  ssh_options should be 
directly under RSYNC.

> On Aug 9, 2022, at 9:01 AM, bell...@gmail.com  wrote:
> 
> I don’t have a [[SSH]] stanza. Try removing that.
> rich
> 
>> On Tuesday, 9 August 2022 at 11:53:57 UTC-4 dan.rh...@gmail.com wrote:
>> Yep, correct, its the private key. 
>> 
>> But it looks like that whole ssh_options bit is being ignored. I can't see 
>> it in the logs when I tail them. 
>> 
>>> On Tuesday, August 9, 2022 at 4:52:18 PM UTC+1 jo...@johnkline.com wrote:
>>> -i should refer to a file that contains a private key.  Is that the case?
>>> 
> On Aug 9, 2022, at 8:14 AM, Dan Jones  wrote:
> 
 My weewx.conf contains this:
>>> 
 
 [[RSYNC]]
 skin = Rsync
 HTML_ROOT = /var/www/html
 server = awsbox
 user = www-data
 path = /var/www/html
 delete = 0
 ssh_options = -i /root/.ssh/aws
 [[SSH]]
ssh_options = -i /root/.ssh/aws
 
 I have awsbox in my host file, pointing to the correct ip address
 
 in my .ssh/config I have:
 
 Host awsbox
 user www-data
 IdentityFile /root/.ssh/aws
 
 
 when I start the Weewx server, I get this error 
 
 DEBUG weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', 
 '--stats', '-e', 'ssh', '/tmp/weather34/serverdata/', 
 'www-...@123.123.123.123:/var/www/html/weather34/serverdata']]
 
 (IP changed for security)
 
 I can't see where the ip address is coming from. Is weewx or rsync 
 converting it from the host file?
 
 Also, It seems to be ignoring the ssh_options parameter (though I could be 
 using the wrong) But I hope that it isn't required, as I guess that rsync 
 should be using the config in .ssh/config
 
 Any help would be greatly appreciated
 
 This is all on the latest version of Weewx
 
>>> 
 -- 
 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.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/e84797ff-e452-4099-bac1-e032a1f6d903n%40googlegroups.com.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/7a2e36e8-00fe-491e-acd7-01fca28be7a0n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CBB32A30-AB6D-4EEC-934E-1485CD416627%40johnkline.com.

Re: [weewx-user] RSYNC is using IP address and not host name

Also, add:
debug = 1
In your weewx.conf file and restart WeeWX.

Your log will then contain output of the form:
rsyncupload: cmd: 

That will tell you if -i is being passed (likely it is) and also let you try it 
from the command line.

> On Aug 9, 2022, at 8:55 AM, John Kline  wrote:
> 
> 
> Just to double check, it’s the private key and not the directory that 
> contains the private key?
> 
>>> On Aug 9, 2022, at 8:54 AM, Dan Jones  wrote:
>>> 
>> Yep, correct, its the private key. 
>> 
>> But it looks like that whole ssh_options bit is being ignored. I can't see 
>> it in the logs when I tail them. 
>> 
>>> On Tuesday, August 9, 2022 at 4:52:18 PM UTC+1 jo...@johnkline.com wrote:
>>> -i should refer to a file that contains a private key.  Is that the case?
>>> 
>>>>> On Aug 9, 2022, at 8:14 AM, Dan Jones  wrote:
>>>>> 
>>>> My weewx.conf contains this:
>>> 
>>>> 
>>>> [[RSYNC]]
>>>> skin = Rsync
>>>> HTML_ROOT = /var/www/html
>>>> server = awsbox
>>>> user = www-data
>>>> path = /var/www/html
>>>> delete = 0
>>>> ssh_options = -i /root/.ssh/aws
>>>> [[SSH]]
>>>>ssh_options = -i /root/.ssh/aws
>>>> 
>>>> I have awsbox in my host file, pointing to the correct ip address
>>>> 
>>>> in my .ssh/config I have:
>>>> 
>>>> Host awsbox
>>>> user www-data
>>>> IdentityFile /root/.ssh/aws
>>>> 
>>>> 
>>>> when I start the Weewx server, I get this error 
>>>> 
>>>> DEBUG weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', 
>>>> '--stats', '-e', 'ssh', '/tmp/weather34/serverdata/', 
>>>> 'www-...@123.123.123.123:/var/www/html/weather34/serverdata']]
>>>> 
>>>> (IP changed for security)
>>>> 
>>>> I can't see where the ip address is coming from. Is weewx or rsync 
>>>> converting it from the host file?
>>>> 
>>>> Also, It seems to be ignoring the ssh_options parameter (though I could be 
>>>> using the wrong) But I hope that it isn't required, as I guess that rsync 
>>>> should be using the config in .ssh/config
>>>> 
>>>> Any help would be greatly appreciated
>>>> 
>>>> This is all on the latest version of Weewx
>>>> 
>>> 
>>>> -- 
>>>> 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.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/e84797ff-e452-4099-bac1-e032a1f6d903n%40googlegroups.com.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/2240d22e-6787-4ac6-a6ba-7a4fb231da96n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9C7EF1B6-814D-4009-99B6-F3090A869D49%40johnkline.com.

Re: [weewx-user] RSYNC is using IP address and not host name

Just to double check, it’s the private key and not the directory that contains 
the private key?

> On Aug 9, 2022, at 8:54 AM, Dan Jones  wrote:
> 
> Yep, correct, its the private key. 
> 
> But it looks like that whole ssh_options bit is being ignored. I can't see it 
> in the logs when I tail them. 
> 
>> On Tuesday, August 9, 2022 at 4:52:18 PM UTC+1 jo...@johnkline.com wrote:
>> -i should refer to a file that contains a private key.  Is that the case?
>> 
 On Aug 9, 2022, at 8:14 AM, Dan Jones  wrote:
 
>>> My weewx.conf contains this:
>> 
>>> 
>>> [[RSYNC]]
>>> skin = Rsync
>>> HTML_ROOT = /var/www/html
>>> server = awsbox
>>> user = www-data
>>> path = /var/www/html
>>> delete = 0
>>> ssh_options = -i /root/.ssh/aws
>>> [[SSH]]
>>>ssh_options = -i /root/.ssh/aws
>>> 
>>> I have awsbox in my host file, pointing to the correct ip address
>>> 
>>> in my .ssh/config I have:
>>> 
>>> Host awsbox
>>> user www-data
>>> IdentityFile /root/.ssh/aws
>>> 
>>> 
>>> when I start the Weewx server, I get this error 
>>> 
>>> DEBUG weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', 
>>> '--stats', '-e', 'ssh', '/tmp/weather34/serverdata/', 
>>> 'www-...@123.123.123.123:/var/www/html/weather34/serverdata']]
>>> 
>>> (IP changed for security)
>>> 
>>> I can't see where the ip address is coming from. Is weewx or rsync 
>>> converting it from the host file?
>>> 
>>> Also, It seems to be ignoring the ssh_options parameter (though I could be 
>>> using the wrong) But I hope that it isn't required, as I guess that rsync 
>>> should be using the config in .ssh/config
>>> 
>>> Any help would be greatly appreciated
>>> 
>>> This is all on the latest version of Weewx
>>> 
>> 
>>> -- 
>>> 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.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/e84797ff-e452-4099-bac1-e032a1f6d903n%40googlegroups.com.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/2240d22e-6787-4ac6-a6ba-7a4fb231da96n%40googlegroups.com.

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

Re: [weewx-user] Forecast stopped working

You are running a version of the forecast extension that is incompatible with with WeeWX 4/Python 3.Please install this version:https://github.com/chaunceygardiner/weewx-forecastOn Aug 5, 2022, at 5:15 PM, Mike Hutchins  wrote:
  

  
  
I did not upgrade. I installed it in January and took a few days
  to get it going. Everything was running until July 1. I do not
  believe I changed anything but possible. It's running on a pi 3+
  along with PIHOLE.

mylog attached.
Thanks

On 8/5/2022 6:37 PM, 'John Kline' via
  weewx-user wrote:


  
  

Hmmm.  Did you upgrade WeeWX from 3.x to 4.x?


Rather than going back and forth with questions,
  please follow the instructions here:
https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user
so that we can see what versions of everything
  you are using.

  On Aug 5, 2022, at 4:01 PM, MikeH
 wrote:

  


  
PYTHONPATH=/usr/share/weewx python3
  /usr/share/weewx/user/forecast.py --method=NWS --foid=FWD
  --lid=TXZ118


Returns

  Traceback (most recent call last):
    File "/usr/share/weewx/user/forecast.py", line 5132, in
  
      main()
    File "/usr/share/weewx/user/forecast.py", line 5070, in
  main
      lines = NWSExtractLocation(fcast, options.lid)
    File "/usr/share/weewx/user/forecast.py", line 1807, in
  NWSExtractLocation
      if line.startswith(lid):
  TypeError: startswith first arg must be bytes or a tuple
  of bytes, not str


  On Friday, August 5,
2022 at 5:07:09 PM UTC-5 an oldman wrote:
  
  
you could try
PYTHONPATH=/usr/share/weewx python
  /usr/share/weewx/user/forecast.py --method=NWS
  --foid=FWD --lid=TXZ118
to see if that will works.


  On Friday, August
5, 2022 at 3:04:50 PM UTC-5 MikeH wrote:
  
  What is the
latest version and where is it?  All I see on gethub
is 3.4.0b1


  On Friday,
August 5, 2022 at 11:50:37 AM UTC-5 jo...@johnkline.com
wrote:
  


  

  

  


  

  
One last thing, you are using
  a rather old version of forecast.  Using
  an up-to-date version will let us
  eliminate the version as the cause.

  On Aug 5, 2022, at
    9:44 AM, John Kline <jo...@johnkline.com>
wrote:

  


  

  

  


  

  

  
It’s done every three
  hours by default (10800 seconds).  You
  can hurry it along by temporarily
  adding a shorter interval of 5 minutes
  (300 seconds) in weewx.conf and
  restarting weewx:



  [Forecast]
      data_binding =
forecast_binding
      [[NWS]]
          lid = TXZ118
          foid = FWD
          interval = 300



BTW, I just tried this

Re: [weewx-user] Forecast stopped working


Hmmm.  Did you upgrade WeeWX from 3.x to 4.x?

Rather than going back and forth with questions, please follow the instructions 
here:
https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user
so that we can see what versions of everything you are using.

> On Aug 5, 2022, at 4:01 PM, MikeH  wrote:
> 
> PYTHONPATH=/usr/share/weewx python3 /usr/share/weewx/user/forecast.py 
> --method=NWS --foid=FWD --lid=TXZ118
> 
> Returns
> 
> Traceback (most recent call last):
>   File "/usr/share/weewx/user/forecast.py", line 5132, in 
> main()
>   File "/usr/share/weewx/user/forecast.py", line 5070, in main
> lines = NWSExtractLocation(fcast, options.lid)
>   File "/usr/share/weewx/user/forecast.py", line 1807, in NWSExtractLocation
> if line.startswith(lid):
> TypeError: startswith first arg must be bytes or a tuple of bytes, not str
> On Friday, August 5, 2022 at 5:07:09 PM UTC-5 an oldman wrote:
>> you could try
>> PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/forecast.py 
>> --method=NWS --foid=FWD --lid=TXZ118
>> to see if that will works.
>> 
>> On Friday, August 5, 2022 at 3:04:50 PM UTC-5 MikeH wrote:
>>> What is the latest version and where is it?  All I see on gethub is 3.4.0b1
>>> 
>>> On Friday, August 5, 2022 at 11:50:37 AM UTC-5 jo...@johnkline.com wrote:
>>>> 
>>> 
>>>> One last thing, you are using a rather old version of forecast.  Using an 
>>>> up-to-date version will let us eliminate the version as the cause.
>>>> 
>>>>> On Aug 5, 2022, at 9:44 AM, John Kline  wrote:
>>>>> 
>>> 
>>>>> It’s done every three hours by default (10800 seconds).  You can hurry it 
>>>>> along by temporarily adding a shorter interval of 5 minutes (300 seconds) 
>>>>> in weewx.conf and restarting weewx:
>>>>> 
>>>>> [Forecast]
>>>>> data_binding = forecast_binding
>>>>> [[NWS]]
>>>>> lid = TXZ118
>>>>> foid = FWD
>>>>> interval = 300
>>>>> 
>>>>> BTW, I just tried this and had no problem downloading your forecast.
>>>>> 
>>>>>> On Aug 5, 2022, at 9:30 AM, MikeH  wrote:
>>>>>> Also this sorry.
>>>>>> 
>>>>>> Aug  5 11:15:48 PIHOLE weewx[12658] DEBUG weewx.engine: Loading service 
>>>>>> user.forecast.NWSForecast
>>>>>> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: forecast 
>>>>>> version 3.4.0b1
>>>>>> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: last forecast 
>>>>>> issued 2022-07-01 05:07:00 CDT (1656670020), requested 2022-07-01 
>>>>>> 09:45:32 CDT (1656686732)
>>>>>> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: 
>>>>>> interval=10800 max_age=604800 lid=TXZ118 foid=FWD
>>>>>> Aug  5 11:15:48 PIHOLE weewx[12658] DEBUG weewx.engine: Finished loading 
>>>>>> service user.forecast.NWSForecast
>>>>>> 
>>>>>> On Friday, August 5, 2022 at 10:45:21 AM UTC-5 jo...@johnkline.com wrote:
>>>>>>> Your log snippet doesn’t show any attempts to download the forecast.  
>>>>>>> 
>>>>>>> Would you look at your logs for entries of the form below (of course, 
>>>>>>> not exactly the same as this is for my forecast) and send them?
>>>>>>> 
>>>>>>> INFO user.forecast: NWSThread: NWS: downloading forecast from 
>>>>>>> 'http://forecast.weather.gov/product.php?site=NWS=PFM=txt=MTR'
>>>>>>> 
>>>>>>>> On Aug 5, 2022, at 6:57 AM, MikeH  wrote:
>>>>>>>> Around July 1 my forecast from NWS stopped working. I tried 
>>>>>>>> reinstalling and still cannot get data. Logs show it running and 
>>>>>>>> generating pages but they all show Now forecast data for NWS. I am 
>>>>>>>> using lid=TXZ118 foid=FWD.
>>>>>>> 
>>>>>>>> 
>>>>>>>> Not sure where to look if I am actually getting data from nws or not.
>>>>>>>> 
>>>>>>>> Files and logs attached.
>>>>>>>> 
>>>>>>>> Thanks
>>>>>>> 
>>>>>>>> -- 
>>>>>>>> You received this mes

Re: [weewx-user] Forecast stopped working


One last thing, you are using a rather old version of forecast.  Using an 
up-to-date version will let us eliminate the version as the cause.

> On Aug 5, 2022, at 9:44 AM, John Kline  wrote:
> 
> It’s done every three hours by default (10800 seconds).  You can hurry it 
> along by temporarily adding a shorter interval of 5 minutes (300 seconds) in 
> weewx.conf and restarting weewx:
> 
> [Forecast]
> data_binding = forecast_binding
> [[NWS]]
> lid = TXZ118
> foid = FWD
> interval = 300
> 
> BTW, I just tried this and had no problem downloading your forecast.
> 
>> On Aug 5, 2022, at 9:30 AM, MikeH  wrote:
>> Also this sorry.
>> 
>> Aug  5 11:15:48 PIHOLE weewx[12658] DEBUG weewx.engine: Loading service 
>> user.forecast.NWSForecast
>> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: forecast version 
>> 3.4.0b1
>> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: last forecast 
>> issued 2022-07-01 05:07:00 CDT (1656670020), requested 2022-07-01 09:45:32 
>> CDT (1656686732)
>> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: interval=10800 
>> max_age=604800 lid=TXZ118 foid=FWD
>> Aug  5 11:15:48 PIHOLE weewx[12658] DEBUG weewx.engine: Finished loading 
>> service user.forecast.NWSForecast
>> 
>> On Friday, August 5, 2022 at 10:45:21 AM UTC-5 jo...@johnkline.com wrote:
>>> Your log snippet doesn’t show any attempts to download the forecast.  
>>> 
>>> Would you look at your logs for entries of the form below (of course, not 
>>> exactly the same as this is for my forecast) and send them?
>>> 
>>> INFO user.forecast: NWSThread: NWS: downloading forecast from 
>>> 'http://forecast.weather.gov/product.php?site=NWS=PFM=txt=MTR'
>>> 
>>>> On Aug 5, 2022, at 6:57 AM, MikeH  wrote:
>>>> Around July 1 my forecast from NWS stopped working. I tried reinstalling 
>>>> and still cannot get data. Logs show it running and generating pages but 
>>>> they all show Now forecast data for NWS. I am using lid=TXZ118 foid=FWD.
>>> 
>>>> 
>>>> Not sure where to look if I am actually getting data from nws or not.
>>>> 
>>>> Files and logs attached.
>>>> 
>>>> 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+...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/b95d50a9-082c-40e9-9ec8-925748304776n%40googlegroups.com.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/d4d6f56e-8b14-4765-a4dc-9368b49282fan%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/B362244E-89E9-473E-A80E-6E7F23A340ED%40johnkline.com.

Re: [weewx-user] Forecast stopped working

It’s done every three hours by default (10800 seconds).  You can hurry it along 
by temporarily adding a shorter interval of 5 minutes (300 seconds) in 
weewx.conf and restarting weewx:

[Forecast]
data_binding = forecast_binding
[[NWS]]
lid = TXZ118
foid = FWD
interval = 300

BTW, I just tried this and had no problem downloading your forecast.

> On Aug 5, 2022, at 9:30 AM, MikeH  wrote:
> 
> Also this sorry.
> 
> Aug  5 11:15:48 PIHOLE weewx[12658] DEBUG weewx.engine: Loading service 
> user.forecast.NWSForecast
> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: forecast version 
> 3.4.0b1
> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: last forecast 
> issued 2022-07-01 05:07:00 CDT (1656670020), requested 2022-07-01 09:45:32 
> CDT (1656686732)
> Aug  5 11:15:48 PIHOLE /weewxd: forecast: MainThread: NWS: interval=10800 
> max_age=604800 lid=TXZ118 foid=FWD
> Aug  5 11:15:48 PIHOLE weewx[12658] DEBUG weewx.engine: Finished loading 
> service user.forecast.NWSForecast
> 
>> On Friday, August 5, 2022 at 10:45:21 AM UTC-5 jo...@johnkline.com wrote:
>> Your log snippet doesn’t show any attempts to download the forecast.  
>> 
>> Would you look at your logs for entries of the form below (of course, not 
>> exactly the same as this is for my forecast) and send them?
>> 
>> INFO user.forecast: NWSThread: NWS: downloading forecast from 
>> 'http://forecast.weather.gov/product.php?site=NWS=PFM=txt=MTR'
>> 
 On Aug 5, 2022, at 6:57 AM, MikeH  wrote:
 
>>> Around July 1 my forecast from NWS stopped working. I tried reinstalling 
>>> and still cannot get data. Logs show it running and generating pages but 
>>> they all show Now forecast data for NWS. I am using lid=TXZ118 foid=FWD.
>> 
>>> 
>>> Not sure where to look if I am actually getting data from nws or not.
>>> 
>>> Files and logs attached.
>>> 
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/b95d50a9-082c-40e9-9ec8-925748304776n%40googlegroups.com.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/d4d6f56e-8b14-4765-a4dc-9368b49282fan%40googlegroups.com.

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

Re: [weewx-user] Forecast stopped working

Your log snippet doesn’t show any attempts to download the forecast.  Would you look at your logs for entries of the form below (of course, not exactly the same as this is for my forecast) and send them?INFO user.forecast: NWSThread: NWS: downloading forecast from 'http://forecast.weather.gov/product.php?site=NWS=PFM=txt=MTR'On Aug 5, 2022, at 6:57 AM, MikeH  wrote:Around July 1 my forecast from NWS stopped working. I tried reinstalling and still cannot get data. Logs show it running and generating pages but they all show Now forecast data for NWS. I am using lid=TXZ118 foid=FWD.Not sure where to look if I am actually getting data from nws or not.Files and logs attached.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/b95d50a9-082c-40e9-9ec8-925748304776n%40googlegroups.com.




-- 
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/BD84C608-A9BF-4313-896D-A0778F1314F3%40johnkline.com.
messages

4 17:53:31 PIHOLE /weewxd: forecast: MainThread: Zambretti: forecast version 
3.4.0b1
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: Zambretti: interval=600 
max_age=604800 winddir_period=1800 pressure_period=10800 hemisphere=NORTH 
lower_pressure=950.0 upper_pressure=1050.0
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: NWS: forecast version 
3.4.0b1
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: NWS: interval=10800 
max_age=604800 lid=TXZ118 foid=FWD
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: WU: forecast version 
3.4.0b1
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: OWM: forecast version 
3.4.0b1
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: UKMO: forecast version 
3.4.0b1
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: Aeris: forecast version 
3.4.0b1
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: WWO: forecast version 
3.4.0b1
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: DS: forecast version 
3.4.0b1
Aug  4 17:53:31 PIHOLE /weewxd: forecast: MainThread: XTide: forecast version 
3.4.0b1


syslog
--
4 17:55:33 PIHOLE /weewxd: forecast: MainThread: Zambretti: starting thread
Aug  4 17:55:33 PIHOLE /weewxd: forecast: MainThread: NWS: starting thread
Aug  4 17:55:33 PIHOLE weewx[12959] DEBUG weewx.reportengine: Running reports 
for latest time in the database.
Aug  4 17:55:33 PIHOLE weewx[12959] DEBUG weewx.reportengine: Running report 
'SeasonsReport'
Aug  4 17:55:33 PIHOLE weewx[12959] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Seasons/skin.conf for report 'SeasonsReport'
Aug  4 17:55:33 PIHOLE weewx[12959] DEBUG weewx.cheetahgenerator: Using search 
list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
'weewx.cheetahgenerator.JSONHelpers']
Aug  4 17:55:33 PIHOLE weewx[12959] DEBUG weewx.manager: Daily summary version 
is 4.0
Aug  4 17:55:38 PIHOLE weewx[12959] INFO weewx.cheetahgenerator: Generated 8 
files for report SeasonsReport in 4.64 seconds
Aug  4 17:55:38 PIHOLE weewx[12959] DEBUG weewx.manager: Daily summary version 
is 4.0
Aug  4 17:55:39 PIHOLE weewx[12959] INFO weewx.imagegenerator: Generated 15 
images for report SeasonsReport in 1.27 seconds
Aug  4 17:55:39 PIHOLE weewx[12959] INFO weewx.reportengine: Copied 5 files to 
/var/www/html/weewx
Aug  4 17:55:39 PIHOLE weewx[12959] DEBUG weewx.reportengine: Running report 
'SmartphoneReport'
Aug  4 17:55:39 PIHOLE weewx[12959] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Smartphone/skin.conf for report 
'SmartphoneReport'
Aug  4 17:55:39 PIHOLE weewx[12959] DEBUG weewx.cheetahgenerator: Using search 
list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
'weewx.cheetahgenerator.JSONHelpers']
Aug  4 17:55:39 PIHOLE weewx[12959] DEBUG weewx.manager: Daily summary version 
is 4.0
Aug  4 17:55:40 PIHOLE weewx[12959] INFO weewx.cheetahgenerator: Generated 6 
files for report SmartphoneReport in 0.34 seconds
Aug  4 17:55:40 PIHOLE weewx[12959] DEBUG weewx.manager: Daily summary version 
is 4.0
Aug  4 17:55:40 PIHOLE weewx[12959] INFO weewx.imagegenerator: Generated 6 
images for report SmartphoneReport in 0.47 seconds
Aug  4 17:55:40 PIHOLE weewx[12959] INFO weewx.reportengine: Copied 6 files to

Re: [weewx-user] Re: National Weather Service location IDs

2022-07-09 Thread 'John Kline' via weewx-user

> The newer api.weather.gov can return a lot of detailed forecast information 
> for quite specific locations using gridpoints, but that's not integrated into 
> weewx AFAIK.


https://github.com/chaunceygardiner/weewx-nws

> On Jul 9, 2022, at 11:22 AM, wfs...@gmail.com  wrote:
> 
> Yes, Mike I think you're right.  The weewx forecasting extension looks to be 
> scraping those PFM reports for its data, so you can only choose from those 
> zones where a PFM is generated.
> The newer api.weather.gov can return a lot of detailed forecast information 
> for quite specific locations using gridpoints, but that's not integrated into 
> weewx AFAIK.
> 
> Walt
> 
>> On Friday, July 8, 2022 at 10:56:16 AM UTC-5 MikeQ wrote:
>> Does someone here understand how the NWS generates a forecast for a specific 
>> location?  I used the API link above and it says my forecast zone is IDZ033. 
>>  When I put this in weewx I get the following error:
>> 
>> Jul  8 09:30:20 weatherpi weewxd: forecast: NWSThread: NWS: no PFM found for 
>> IDZ033 in forecast from BOI
>> Jul  8 09:30:20 weatherpi weewxd: forecast: NWSThread: NWS: terminating 
>> thread
>> 
>> If I go to the PFM link above, there are only 5 PFMs for the BOI forecast 
>> office all located at airports.  If I go to weather.gov, put in my zip code, 
>> and click on the map, it puts my lat/lon in URL and generates a forecast for 
>> that location.  The forecast for the closest PFM, which is over 90 miles 
>> away, is different than the one generated on the forecast web page.  I would 
>> like the more accurate forecast, but it doesn't look like the forecast 
>> module in weewx supports anything other than PFMs?
>> 
>>> On Friday, July 8, 2022 at 6:18:51 AM UTC-6 mcu...@gmail.com wrote:
>>> I appreciate the helpthank you
>>> 
>>> 
 On Wednesday, July 6, 2022 at 10:45:51 PM UTC-4 an oldman wrote:
 if you are looking for the pfm try this address
 https://forecast.weather.gov/product_sites.php?site=NWS=PFM
 it list all the pfms
 
> On Wednesday, July 6, 2022 at 9:11:39 PM UTC-5 vince wrote:
> That is a GREAT find.   Comes up right on the money for me.
> 
> Forecast office is SEW(foid in weewx.conf)
> Forecast zone is WAZ558   (lid in weewx.conf)
> 
>> On Wednesday, July 6, 2022 at 6:33:23 PM UTC-7 wfs...@gmail.com wrote:
>> if you plug your lat and lon into the weather.gov api, a la
>> https://api.weather.gov/points/39.7832,-89.6644
>> you'll get a bunch of info back that might contain what you're looking 
>> for.  I'm not familiar with the terms LID and FOID
>> In my case it tells me
>> my forecast office is ILX
>> my grid coordinates are 46,54
>> my forecast zone is ILZ051
>> my county zone is ILC167
>> my fire weather zone is ILZ051
>> 
>> api documentation at 
>> API Web Service (weather.gov)
>> 
>>> On Wednesday, July 6, 2022 at 3:41:56 PM UTC-5 mcu...@gmail.com wrote:
>>> I have been relentlessly searching for a list of NWS LIDs for the 
>>> forecast module and cannot even find a mention of them on their site or 
>>> Wikican somone push me in the right direction I am trying to get 
>>> the Foid and lid for Columbia SC.  I beleive the Foid to be CAE but the 
>>> 6 digit ID is the problem. 
>>> Thank-you
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/e00b92d8-e852-47f3-b50c-185ecf3aa945n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4A05B1A1-A8B5-4C66-87BC-97DAE7A4D648%40johnkline.com.

Re: [weewx-user] new install (4.8) using the GW1000 extension - missing ET?

2022-07-04 Thread John Hill

omg... it was right there in the wiki.  So sorry to bother you.  Plugged in 
the formula and it's working great.  Thanks!

On Monday, July 4, 2022 at 5:46:31 PM UTC-4 gjr80 wrote:

> Ecowitt Gateway devices provide a measure of luminosity in lux rather than 
> a measure of solar insolation in watts/square metre (as used by WeeWX in 
> the radiation field). There is a simple linear approximation for radiation 
> given a luminosity value in lux by dividing the luminosity value by 126.7. 
> This is what Ecowitt Gateway devices use when posting to Ecowitt.net or 
> WeatherUnderground etc. Within WeeWX it is not appropriate for the Ecowitt 
> gateway driver to implement this approximation , rather it should be 
> applied by adding a correction entry to the [StdCalibration] 
> [[Corrections]] stanza in weewx.conf. More detail (including 
> implementation of the radiation field approximation) is covered in the 
> Ecowitt gateway device wiki page Understanding GW1000 radiation fields 
> <https://github.com/gjr80/weewx-gw1000/wiki/Understanding-GW1000-radiation-fields>
> .
>
> Once you have the radiation field being calculated you should should find 
> that ET is also calculated provided you have the other pre-requisites 
> outlined in Tom's post are available. 
>
> Gary
> On Tuesday, 5 July 2022 at 07:14:39 UTC+10 tke...@gmail.com wrote:
>
>> In order to calculate ET, you'll need outside temperature, radiation, and 
>> humidity. From your query, you don't have radiation, and possibly the 
>> others. Make sure they are all there.
>>
>> On Mon, Jul 4, 2022 at 9:49 AM John Hill  wrote:
>>
>>> Sorry - this is going to sound poorly informed... but here it goes.
>>>
>>> I've been running weewx for years since the 3.x days.  Using the 
>>> interceptor driver - first with the Ambient Weather devices, now with 
>>> Ecowitt using a GW1000 as a gateway.
>>>
>>> During that time I made numerous tweaks to the file system, changing 
>>> skins, schemas, adding extensions, removing extensions, running through 
>>> hubitat, then nodered, etc.  Of course, I'm not very good at documentation, 
>>> so each change I made would eventually get pushed out of my brain in favor 
>>> of the new project du jour.
>>>
>>> I noticed a new gw1000 extension and thought maybe now would be a good 
>>> time to wipe the slate and see what works out of the box.
>>>
>>> Surprisingly, most everything does.  I do see some label and unit 
>>> changes for radiation (used to be wmp2/radiation, now it's lux/luminosity).
>>>
>>> But the most noticeable changes is I'm now missing ET.  Not sure how.  I 
>>> don't remember having to do anything in my prior install to get it to 
>>> calculate.
>>>
>>> confirmed in sqlite that it's not in the archive:
>>>
>>> sqlite> select dateTime,ET,radiation,UV from archive order by dateTime 
>>> desc limit 4;
>>>
>>> 1656952200|||6.0
>>>
>>> 1656952140|||4.0
>>>
>>> 1656952080|||2.0
>>>
>>> 1656952020|||3.0
>>>
>>>
>>> It's in my wview.py schema and in my skins.conf:
>>>
>>> [[[dayET]]]
>>>
>>> # Make sure the y-axis increment is at least 0.02 for the 
>>> ET plot
>>>
>>> yscale = None, None, 0.02
>>>
>>> plot_type = bar
>>>
>>> ET
>>>
>>> aggregate_type = sum
>>>
>>> aggregate_interval = hour
>>>
>>> label = Evapotranspiration (hourly total)
>>>
>>>
>>> have tried both prefer-hardware and software in my weewx.conf for ET 
>>> calcualtion.
>>>
>>> Hope it's obvious, but what am I missing?
>>>
>>> -- 
>>> 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.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/1549e44c-8848-44ef-8c04-81444b2cd034n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/1549e44c-8848-44ef-8c04-81444b2cd034n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/15ff4629-7f64-48d4-b314-e5a3e258ccban%40googlegroups.com.

[weewx-user] new install (4.8) using the GW1000 extension - missing ET?

2022-07-04 Thread John Hill

Sorry - this is going to sound poorly informed... but here it goes.

I've been running weewx for years since the 3.x days. Using the
interceptor driver - first with the Ambient Weather devices, now with
Ecowitt using a GW1000 as a gateway.

During that time I made numerous tweaks to the file system, changing skins,
schemas, adding extensions, removing extensions, running through hubitat,
then nodered, etc. Of course, I'm not very good at documentation, so each
change I made would eventually get pushed out of my brain in favor of the
new project du jour.

I noticed a new gw1000 extension and thought maybe now would be a good time
to wipe the slate and see what works out of the box.

Surprisingly, most everything does. I do see some label and unit changes
for radiation (used to be wmp2/radiation, now it's lux/luminosity).

But the most noticeable changes is I'm now missing ET. Not sure how. I
don't remember having to do anything in my prior install to get it to
calculate.

confirmed in sqlite that it's not in the archive:

sqlite> select dateTime,ET,radiation,UV from archive order by dateTime desc
limit 4;

1656952200|||6.0

1656952140|||4.0

1656952080|||2.0

1656952020|||3.0

It's in my wview.py schema and in my skins.conf:

[[[dayET]]]

# Make sure the y-axis increment is at least 0.02 for the ET
plot

yscale = None, None, 0.02

plot_type = bar

aggregate_type = sum

aggregate_interval = hour

label = Evapotranspiration (hourly total)

have tried both prefer-hardware and software in my weewx.conf for ET
calcualtion.

Hope it's obvious, but what am I missing?

Re: [weewx-user] Re: Help with forecast

2022-06-15 Thread 'John Kline' via weewx-user

Our emails crossed.  I’m glad you got it working.

> On Jun 15, 2022, at 7:53 AM, John Kline  wrote:
> 
> 
> It sure looks like your forecast.sdb archive table got created as a weewx 
> archive table.  If so, it wasn’t the forecast extension that did it.  Perhaps 
> the binding were misconfigured when forecast.sdb was created.
> 
> Before we delete it, let’s have a look at it.
> 
> Please paste the output of (adjusting the path of forecast.sdb as necessary):
> 
> $ sqlite3 /home/weewx/archive/forecast.sdb 
> SQLite version 3.34.1 2021-01-20 14:10:07
> Enter ".help" for usage hints.
> sqlite> PRAGMA table_info(archive);
> 
> 
> If so, delete your forecast.sdb file and restart weewx.
> 
>>> On Jun 15, 2022, at 7:09 AM, Timothy Reaves  
>>> wrote:
>>> 
>> 
>> I'm going to start looking more at the python code now.
>> 
>> [DataBindings]
>> 
>>   [[wx_binding]]
>> # The database must match one of the sections in [Databases].
>> # This is likely to be the only option you would want to change.
>> database = archive_sqlite
>> # The name of the table within the database
>> table_name = archive
>> # The manager handles aggregation of data for historical summaries
>> manager = weewx.manager.DaySummaryManager
>> # The schema defines the structure of the database.
>> # It is *only* used when the database is created.
>> schema = schemas.wview_extended.schema
>> 
>>   [[forecast_binding]]
>> manager = weewx.manager.Manager
>> schema = user.forecast.schema
>> table_name = archive
>> database = forecast_sqlite
>> 
>> ##
>> 
>> #   This section defines various databases.
>> 
>> [Databases]
>> 
>>   # A SQLite database is simply a single file
>>   [[archive_sqlite]]
>> database_name = weewx.sdb
>> database_type = SQLite
>>   
>>   [[forecast_sqlite]]
>> database_type = SQLite
>> database_name = forecast.sdb
>> 
>> 
>>> On Wednesday, June 15, 2022 at 8:22:37 AM UTC-4 jo...@johnkline.com wrote:
>>> This looks like a clear case of forecast being pointed to the wrong 
>>> database.
>>> 
>>> Please send the data_binding line in the [forecast[ section of weewx.conf.
>>> Also send the [DataBindings] section of weewx.conf.
>>> 
>>>>> On Jun 13, 2022, at 6:49 AM, Timothy Reaves  
>>>>> wrote:
>>>>> 
>>>> Thank you both for the responses.
>>> 
>>>> 
>>>> Doug, that is the extension I wrote this post about.  I have followed the 
>>>> instructions, and receive the error I'd posted. So I have all of the 
>>>> configuration that the plugin lists.  When I enable the archive_service, I 
>>>> get the error.  So for some reason it doesn't seem to be connecting to the 
>>>> correct database.  Here is the snippet from my configuration regarding the 
>>>> databases:
>>>> 
>>>> [Databases]
>>>> 
>>>> # A SQLite database is simply a single file
>>>> [[archive_sqlite]]
>>>> database_name = weewx.sdb
>>>> database_type = SQLite
>>>> 
>>>> # MySQL
>>>> [[archive_mysql]]
>>>> database_name = weewx
>>>> database_type = MySQL
>>>> 
>>>> [[forecast_sqlite]]
>>>> database_type = SQLite
>>>> database_name = forecast.sdb
>>>> 
>>>> [[forecast_mysql]]
>>>> database_type = MySql
>>>> database_name = forecast
>>>> 
>>>>>> On Friday, June 10, 2022 at 11:22:26 AM UTC-4 do...@dougjenkins.com 
>>>>>> wrote:
>>>>>> Tim:
>>>>>> 
>>>>>> The forecast module uses a completely different schema and database. 
>>>>>> What you need to do is configure the module to a separate database and 
>>>>>> in your skin, bring in the data to be presented.
>>>>>> 
>>>>>> I personally use John Kline's weewx forecast driver ( GitHub - 
>>>>>> chaunceygardiner/weewx-forecast: forecasting extension for weewx) as it 
>>>>>> is being maintained and it works with the latest version of WeeWX 
>>>>>> (v4.8). You will need to look at the sample page

Re: [weewx-user] Re: Help with forecast

2022-06-15 Thread 'John Kline' via weewx-user

It sure looks like your forecast.sdb archive table got created as a weewx 
archive table.  If so, it wasn’t the forecast extension that did it.  Perhaps 
the binding were misconfigured when forecast.sdb was created.

Before we delete it, let’s have a look at it.

Please paste the output of (adjusting the path of forecast.sdb as necessary):

$ sqlite3 /home/weewx/archive/forecast.sdb 
SQLite version 3.34.1 2021-01-20 14:10:07
Enter ".help" for usage hints.
sqlite> PRAGMA table_info(archive);


If so, delete your forecast.sdb file and restart weewx.

> On Jun 15, 2022, at 7:09 AM, Timothy Reaves  
> wrote:
> 
> 
> I'm going to start looking more at the python code now.
> 
> [DataBindings]
> 
>   [[wx_binding]]
> # The database must match one of the sections in [Databases].
> # This is likely to be the only option you would want to change.
> database = archive_sqlite
> # The name of the table within the database
> table_name = archive
> # The manager handles aggregation of data for historical summaries
> manager = weewx.manager.DaySummaryManager
> # The schema defines the structure of the database.
> # It is *only* used when the database is created.
> schema = schemas.wview_extended.schema
> 
>   [[forecast_binding]]
> manager = weewx.manager.Manager
> schema = user.forecast.schema
> table_name = archive
> database = forecast_sqlite
> 
> ##
> 
> #   This section defines various databases.
> 
> [Databases]
> 
>   # A SQLite database is simply a single file
>   [[archive_sqlite]]
> database_name = weewx.sdb
> database_type = SQLite
>   
>   [[forecast_sqlite]]
> database_type = SQLite
> database_name = forecast.sdb
> 
> 
>> On Wednesday, June 15, 2022 at 8:22:37 AM UTC-4 jo...@johnkline.com wrote:
>> This looks like a clear case of forecast being pointed to the wrong database.
>> 
>> Please send the data_binding line in the [forecast[ section of weewx.conf.
>> Also send the [DataBindings] section of weewx.conf.
>> 
>>>> On Jun 13, 2022, at 6:49 AM, Timothy Reaves  
>>>> wrote:
>>>> 
>>> Thank you both for the responses.
>> 
>>> 
>>> Doug, that is the extension I wrote this post about.  I have followed the 
>>> instructions, and receive the error I'd posted. So I have all of the 
>>> configuration that the plugin lists.  When I enable the archive_service, I 
>>> get the error.  So for some reason it doesn't seem to be connecting to the 
>>> correct database.  Here is the snippet from my configuration regarding the 
>>> databases:
>>> 
>>> [Databases]
>>> 
>>> # A SQLite database is simply a single file
>>> [[archive_sqlite]]
>>> database_name = weewx.sdb
>>> database_type = SQLite
>>> 
>>> # MySQL
>>> [[archive_mysql]]
>>> database_name = weewx
>>> database_type = MySQL
>>> 
>>> [[forecast_sqlite]]
>>> database_type = SQLite
>>> database_name = forecast.sdb
>>> 
>>> [[forecast_mysql]]
>>> database_type = MySql
>>> database_name = forecast
>>> 
>>>>> On Friday, June 10, 2022 at 11:22:26 AM UTC-4 do...@dougjenkins.com wrote:
>>>>> Tim:
>>>>> 
>>>>> The forecast module uses a completely different schema and database. What 
>>>>> you need to do is configure the module to a separate database and in your 
>>>>> skin, bring in the data to be presented.
>>>>> 
>>>>> I personally use John Kline's weewx forecast driver ( GitHub - 
>>>>> chaunceygardiner/weewx-forecast: forecasting extension for weewx) as it 
>>>>> is being maintained and it works with the latest version of WeeWX (v4.8). 
>>>>> You will need to look at the sample pages that accompany the driver and 
>>>>> integrate the cheetah template code into your skin. 
>>>>> 
>>>>> Best practice is to copy your existing skin folder (eg seasons) to a 
>>>>> separate folder (seasons-forecast) and make the modifications there. I 
>>>>> usually use the wee_reports utility to generate the html when I make 
>>>>> changes to the skin.
>>>>> 
>>>>> Please let us know if you have any questions.
>>>>> 
>>>>> Doug
>>>>> www.largoweather

Re: [weewx-user] Re: Help with forecast

2022-06-15 Thread 'John Kline' via weewx-user

This looks like a clear case of forecast being pointed to the wrong database.

Please send the data_binding line in the [forecast[ section of weewx.conf.
Also send the [DataBindings] section of weewx.conf.

> On Jun 13, 2022, at 6:49 AM, Timothy Reaves  
> wrote:
> 
> Thank you both for the responses.
> 
> Doug, that is the extension I wrote this post about.  I have followed the 
> instructions, and receive the error I'd posted. So I have all of the 
> configuration that the plugin lists.  When I enable the archive_service, I 
> get the error.  So for some reason it doesn't seem to be connecting to the 
> correct database.  Here is the snippet from my configuration regarding the 
> databases:
> 
> [Databases]
> 
> # A SQLite database is simply a single file
> [[archive_sqlite]]
> database_name = weewx.sdb
> database_type = SQLite
> 
> # MySQL
> [[archive_mysql]]
> database_name = weewx
> database_type = MySQL
> 
> [[forecast_sqlite]]
> database_type = SQLite
> database_name = forecast.sdb
> 
> [[forecast_mysql]]
> database_type = MySql
> database_name = forecast
> 
>> On Friday, June 10, 2022 at 11:22:26 AM UTC-4 do...@dougjenkins.com wrote:
>> Tim:
>> 
>> The forecast module uses a completely different schema and database. What 
>> you need to do is configure the module to a separate database and in your 
>> skin, bring in the data to be presented.
>> 
>> I personally use John Kline's weewx forecast driver ( GitHub - 
>> chaunceygardiner/weewx-forecast: forecasting extension for weewx) as it is 
>> being maintained and it works with the latest version of WeeWX (v4.8). You 
>> will need to look at the sample pages that accompany the driver and 
>> integrate the cheetah template code into your skin. 
>> 
>> Best practice is to copy your existing skin folder (eg seasons) to a 
>> separate folder (seasons-forecast) and make the modifications there. I 
>> usually use the wee_reports utility to generate the html when I make changes 
>> to the skin.
>> 
>> Please let us know if you have any questions.
>> 
>> Doug
>> www.largoweather.com
>> 
>> 
>>> On Friday, June 10, 2022 at 10:22:59 AM UTC-4 RobbH wrote:
>>> This is certainly not what you are looking for, but it is what I use to get 
>>> NWS forecasts.
>>> 
>>> Here is a url for a forecast for a randomly selected location:
>>> 
>>> https://forecast.weather.gov/MapClick.php?lat=41.177010=-73.141963=0=english=text=2
>>> 
>>> Note where latitude and longitude are inserted. "TextType=2" at the end 
>>> tells the server to include forecast graphics.
>>> 
>>> Several times a day, a cron job uses PhantomJS to retrieve that page and 
>>> create an jpeg of the forecast graphics, which is then displayed on my 
>>> weewx home page.
>>> 
>>> It usually works well enough for my purposes, but there are times when the 
>>> forecast page is down, so I end up with a blank rectangle on the weewx page.
>>> 
>>> 
>>> 
>>>> On Wednesday, June 8, 2022 at 12:16:33 PM UTC-4 Timothy Reaves wrote:
>>>> Hello all.  I'm using the latest version running on a Pi 4, with a Davis 
>>>> Vantage Pro.  I've had my site configured to use Aeris for forecasting, 
>>>> and have never really liked it.  It just isn't as accurate as the NWS.  
>>>> But I stuck with it.  Then last week, the Aeris forecast for my sight 
>>>> started diverging significantly not only from the NWS, but also from the 
>>>> actual Aeris site (which following the forecast link).  I don't know 
>>>> what's going on, so I thought I'd jut stop using it.
>>>> 
>>>> So I installed the Forecast user module.  When I start weewx now, it fails 
>>>> to load with the error below.  In looking at the code, the database schema 
>>>> isn't matching the extensions in-memory schema.  Don't know why.
>>>> 
>>>> Has anyone an example of using NWS forecasts instead of Aeris?  Or can 
>>>> provide any other ideas to troubleshoot?
>>>> 
>>>> Thanks.
>>>> 
>>>> Jun  8 10:12:34 pi4home weewx[12748] CRITICAL __main__:   
>>>> Exception: NWS: schema mismatch: ['dateTime', 'usUnits', 'interval', 
>>>> 'altimeter', 'appTemp', 'appTemp1', 'barometer', 'batteryStatus1', 
>>>> 'batteryStatus2', 'batteryStatus3', 'batteryStatus4', 'batteryS

Re: [weewx-user] Problem with weewx-airlink

2022-05-30 Thread 'John Kline' via weewx-user

Well, first, the subject of this thread is not accurate.  The problem is not 
with weewx-airlink.

I had a look at Davis’ Airlink manual and this case isn’t covered.  I suggest 
you contact Davis Technical Support:
supp...@davisinstruments.com
(510) 732-7814
Monday - Friday, 7:00 a.m. - 5:30 p.m. Pacific Time.

> On May 30, 2022, at 4:09 AM, anc...@gmail.com  wrote:
> 
> Hi,
> that page gives me
> curl http://192.168.0.196/v1/current_conditions
> { "data": { "did": "001D0A100829", "name": "IIS Ceccano", "ts": 506449, 
> "conditions": [{ "lsid": 522424, "data_structure_type": 6, "temp": 86.1, 
> "hum": 43.5, "dew_point": 61.3, "wet_bulb": 66.5, "heat_index": 86.5, 
> "pm_1_last": 2, "pm_2p5_last": 3, "pm_10_last": 3, "pm_1": null, "pm_2p5": 
> null, "pm_2p5_last_1_hour": null, "pm_2p5_last_3_hours": null, 
> "pm_2p5_last_24_hours": null, "pm_2p5_nowcast": null, "pm_10": null, 
> "pm_10_last_1_hour": null, "pm_10_last_3_hours": null, "pm_10_last_24_hours": 
> null, "pm_10_nowcast": null, "last_report_time": 506449, 
> "pct_pm_data_last_1_hour": null, "pct_pm_data_last_3_hours": null, 
> "pct_pm_data_nowcast": null, "pct_pm_data_last_24_hours": null }] }, "error": 
> null }
> 
> So it seems it has not neither good timestamp neither good concentrations. 
> How can I fix this?
> 
> 
> Il giorno mercoledì 25 maggio 2022 alle 19:30:40 UTC+2 jo...@johnkline.com ha 
> scritto:
>> You’re getting this because the timestamp is bad:
>> 'ts': 85460
>> 
>> The specific message: user.airlink: last_report_time must be time since 
>> boot: 85441 seconds.
>> is worded that way because I found airlink was reporting time since reboot 
>> (rather than time since epoch).  I observed this behavior until the airlink 
>> started reporting concentrations.  I specifically check for pm1 to determine 
>> this state.  In the case below, pm_1 is missing ('pm_1': None).
>> 
>> I wouldn’t try to get this running in weewx until you have good data.  In a 
>> browser, go to:
>> http:///v1/current_conditions
>> 
>> You need a good timestamp to show up here (e.g., right now, "ts": 
>> 1653499667) and good concentrations (rather than None); e.g., "pm_1": 5.16
>> 
>> Since it’s finding no valid concentrations, you are seeing the message 
>> “Could not get concentrations from any source.”
>> 
>> John
>> 
>>>> On May 25, 2022, at 8:24 AM, anc...@gmail.com  wrote:
>>>> 
>>> Hi guys,
>> 
>>> I just installed for the first time a Davis Airlink and I want to integrate 
>>> it in WeeWX with which my Davis VP2 already works. I followed the 
>>> instructions on the weewx-airlink page, but for some reason it is not 
>>> working . Here is some log:
>>> 
>>> May 25 16:11:01 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
>>> Could not get concentrations from any source.
>>> May 25 16:11:01 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
>>> Found no concentrations to insert.
>>> May 25 16:11:03 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
>>> Found no concentrations to insert.
>>> May 25 16:11:05 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
>>> Found no concentrations to insert.
>>> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink: 
>>> last_report_time must be time since boot: 85441 seconds.  Record: {'data': 
>>> {'did': '001D0A100829', 'name': 'IIS Ceccano', 'ts': 85441, 'conditions': 
>>> [{'lsid': 522424, 'data_structure_type': 6, 'temp': 92.0, 'hum': 26.5, 
>>> 'dew_point': 52.7, 'wet_bulb': 60.0, 'heat_index': 89.8, 'pm_1_last': 4, 
>>> 'pm_2p5_last': 5, 'pm_10_last': 5, 'pm_1': None, 'pm_2p5': None, 
>>> 'pm_2p5_last_1_hour': None, 'pm_2p5_last_3_hours': None, 
>>> 'pm_2p5_last_24_hours': None, 'pm_2p5_nowcast': None, 'pm_10': None, 
>>> 'pm_10_last_1_hour': None, 'pm_10_last_3_hours': None, 
>>> 'pm_10_last_24_hours': None, 'pm_10_nowcast': None, 'last_report_time': 
>>> 85441, 'pct_pm_data_last_1_hour': None, 'pct_pm_data_last_3_hours': None, 
>>> 'pct_pm_data_nowcast': None, 'pct_pm_data_last_24_hours': None}]}, 'error': 
>>> None}
>>> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
>>> Could not get concentrations

Re: [weewx-user] weewx migration

2022-05-28 Thread 'John Kline' via weewx-user

I’m sure someone can help if you send a log.
See: https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user

> On May 28, 2022, at 5:51 AM, hajsek...@gmail.com  
> wrote:
> 
> 
> Thank you
> I now manage to start weewx and it looks like it populate weewx database in 
> mysql.
> But it doesn't update my html files
> I use a observer driver to get data from my froggit HP1000 weather station
> I seton weather station to send data to my external  ip 123.123.123.123 on 
> port 9000
> this is server where I have installed weewx.
> but when I setup observer it doesn't work I get errors
> now I setup interceptor but still web page doesn't update.
> what I am missing here?
> 
> ##
> [Observer]
> # This section is for the Observer weather stations.
> 
> # The driver to use
> #driver = user.observer
> 
> # How often to poll the device, in seconds
> poll_interval = 60
> 
> ##
> 
> [Interceptor]
> # This section is for the network traffic interceptor driver.
> 
> # The driver to use:
> # device_type = observer
> driver = user.interceptor
> device_type = ecowitt-client
> 
> # Specify the hardware device to capture.  Options include:
> #   acurite-bridge - acurite internet bridge, smarthub, or access
> #   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
> #   lw30x - oregon scientific LW301/LW302
> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
> #   ecowitt-client - any hardware that uses the ecowitt protocol
> #   wu-client - any hardware that uses the weather underground protocol
> # device_type = acurite-bridge
> mode = listen
> port = 9900
> [[sensor_map_extensions]]
> inTemp = temperature_1
> inHumidity = humidity_1
> outTemp = temperature_4
> outHumidity = humidity_4
> ##
> 
> 
> sobota, 28. maj 2022 ob 03:00:56 UTC+2 je oseba jo...@johnkline.com napisala:
>> 
>> 
>> 
>> After you follow Gary’s advice to install the current version of 
>> readltime_gauge-data, you’ll hit a problem with your version of 
>> weewx-forecast, as it hasn’t been updated for Python3.  To fix this, you can 
>> install a fork that has been ported:
>> https://github.com/chaunceygardiner/weewx-forecast/releases/download/v3.4.0b11/weewx-forecast-3.4.0b11.zip
>> 
 On May 27, 2022, at 5:37 PM, gjr80  wrote:
 
>>> 
>> 
>>> It look like you are using the realtime_gauge-data v0.3.7 or earlier. The 
>>> current version is v0.5.5 - you will need to upgrade as python3 support was 
>>> not added until v0.4.0. Use the latest version - it is available on GitHub 
>>> here.
>>> 
>>> Gary
>>> 
 On Saturday, 28 May 2022 at 08:11:59 UTC+10 hajsek...@gmail.com wrote:
 I use python3 version
 weewex is installed by this guide and I use centos 8
 http://weewx.com/docs/redhat.htm
 weewx interceptor is this one 
 https://github.com/matthewwall/weewx-interceptor
 weewx forecast is this one
 https://codeload.github.com/matthewwall/weewx-forecast/zip/refs/heads/master/weewx-forecast-master.zip
 I set debug = 2
 this is log
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
   self.loadServices(config_dict)
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
 File "/usr/share/weewx/weewx/engine.py", line 161, in loadServices
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
   obj = weeutil.weeutil.get_object(svc)(self, config_dict)
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
 File "/usr/share/weewx/weeutil/weeutil.py", line 1150, in 
 get_object
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
   mod = __import__(module)
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
 File "/usr/share/weewx/user/rtgd.py", line 1234
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
   except Exception, e:
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
   ^
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
   SyntaxError: invalid syntax
 May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__: 
   Exiting.
 May 28 00:09:37 web systemd[1]: Started Session 5 of user root.
 May 28 00:09:37 web systemd-logind[1010]: New session 5 of user root.
 May 28 00:09:41 web systemd[1]: Stopping SYSV: start and stop the weewx 
 weather system...
 May 28 00:09:41 web weewx[19416]: Shutting down weewx: [  V redu  ]
 May 28 00:09:41 web

[weewx-user] weewx migration

2022-05-27 Thread 'John Kline' via weewx-user




After you follow Gary’s advice to install the current version of 
readltime_gauge-data, you’ll hit a problem with your version of weewx-forecast, 
as it hasn’t been updated for Python3.  To fix this, you can install a fork 
that has been ported:
https://github.com/chaunceygardiner/weewx-forecast/releases/download/v3.4.0b11/weewx-forecast-3.4.0b11.zip

> On May 27, 2022, at 5:37 PM, gjr80  wrote:
> 
> It look like you are using the realtime_gauge-data v0.3.7 or earlier. The 
> current version is v0.5.5 - you will need to upgrade as python3 support was 
> not added until v0.4.0. Use the latest version - it is available on GitHub 
> here.
> 
> Gary
> 
> On Saturday, 28 May 2022 at 08:11:59 UTC+10 hajsek...@gmail.com wrote:
>> I use python3 version
>> weewex is installed by this guide and I use centos 8
>> http://weewx.com/docs/redhat.htm
>> weewx interceptor is this one 
>> https://github.com/matthewwall/weewx-interceptor
>> weewx forecast is this one
>> https://codeload.github.com/matthewwall/weewx-forecast/zip/refs/heads/master/weewx-forecast-master.zip
>> I set debug = 2
>> this is log
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>  self.loadServices(config_dict)
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>File "/usr/share/weewx/weewx/engine.py", line 161, in loadServices
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>  obj = weeutil.weeutil.get_object(svc)(self, config_dict)
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>File "/usr/share/weewx/weeutil/weeutil.py", line 1150, in get_object
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>  mod = __import__(module)
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>File "/usr/share/weewx/user/rtgd.py", line 1234
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>  except Exception, e:
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>  ^
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>  SyntaxError: invalid syntax
>> May 28 00:08:27 web journal[19319]: weewx[19319] CRITICAL __main__:  
>>  Exiting.
>> May 28 00:09:37 web systemd[1]: Started Session 5 of user root.
>> May 28 00:09:37 web systemd-logind[1010]: New session 5 of user root.
>> May 28 00:09:41 web systemd[1]: Stopping SYSV: start and stop the weewx 
>> weather system...
>> May 28 00:09:41 web weewx[19416]: Shutting down weewx: [  V redu  ]
>> May 28 00:09:41 web systemd[1]: weewx.service: Succeeded.
>> May 28 00:09:41 web systemd[1]: Stopped SYSV: start and stop the weewx 
>> weather system.
>> May 28 00:09:41 web systemd[1]: Starting SYSV: start and stop the weewx 
>> weather system...
>> May 28 00:09:42 web journal[19440]: weewx[19440] INFO __main__: Initializing 
>> weewx version 4.8.0
>> May 28 00:09:42 web journal[19440]: weewx[19440] INFO __main__: Using Python 
>> 3.6.8 (default, Apr 29 2022, 13:46:02) #012[GCC 8.5.0 20210514 (Red Hat 
>> 8.5.0-10)]
>> May 28 00:09:42 web journal[19440]: weewx[19440] INFO __main__: Platform 
>> Linux-4.18.0-372.9.1.el8.x86_64-x86_64-with-almalinux-8.6-Sky_Tiger
>> May 28 00:09:42 web journal[19440]: weewx[19440] INFO __main__: Locale is 
>> 'sl_SI.UTF-8'
>> May 28 00:09:42 web journal[19440]: weewx[19440] INFO __main__: Using 
>> configuration file /etc/weewx/weewx.conf
>> May 28 00:09:42 web journal[19440]: weewx[19440] INFO __main__: Debug is 2
>> May 28 00:09:42 web journal[19440]: weewx[19440] INFO __main__: PID file is 
>> /var/run/weewx.pid
>> May 28 00:09:42 web journal[19444]: weewx[19444] INFO weewx.engine: Loading 
>> station type Interceptor (user.interceptor)
>> May 28 00:09:42 web weewx[19431]: Starting weewx: [  V redu  ]
>> May 28 00:09:42 web systemd[1]: Started SYSV: start and stop the weewx 
>> weather system.
>> May 28 00:09:42 web journal[19444]: weewx[19444] INFO user.interceptor: 
>> driver version is 0.53
>> May 28 00:09:42 web journal[19444]: weewx[19444] INFO user.interceptor: 
>> device type: observer
>> May 28 00:09:42 web journal[19444]: weewx[19444] INFO user.interceptor: mode 
>> is listen
>> May 28 00:09:42 web journal[19444]: weewx[19444] INFO user.interceptor: 
>> listen on :9900
>> May 28 00:09:42 web journal[19444]: weewx[19444] INFO user.interceptor: 
>> sensor map: {'pressure': 'pressure', 'barometer': 'barometer', 
>> 'outHumidity': 'humidity_out', 'inHumidity': 'humidity_in', 'outTemp': 
>> 'temperature_out', 'inTemp': 'temperature_in', 'windSpeed': 'wind_speed', 
>> 'windGust': 'wind_gust', 'windDir': 'wind_dir', 'windGustDir': 
>> 'wind_gust_dir', 'radiation': 'solar_radiation', 'dewpoint': 'dewpoint', 
>> 'windchill': 'windchill', 'rain': 'rain', 'rainRate': 'rain_rate', 'UV': 
>> 'uv', 'txBatteryStatus': 'battery', 'extraTemp1':

Re: [weewx-user] weewx migration

2022-05-27 Thread 'John Kline' via weewx-user

Your log snippet shows an error in  weewx-realtime_gauge-data, probably because 
it’s an old version that doesn’t work with Python3.  What version of  
weewx-realtime_gauge-data have you installed?

Also, since you are want to get the forecast extension working, what version 
are you using of that?

And what python version are you running?

Lastly, it would be good if you included the log as it would answer these 
questions.  See: https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user

> On May 27, 2022, at 7:46 AM, hajsek...@gmail.com  
> wrote:
> 
> 
> I have migrated weewx to another server, but have a problem.
> First I copied old files to new server and try to start it and didn't worked.
> Than i Have new installation of weex and after that I have installed driver 
> observer when I start weewx it was ok. But after that I have installed 
> forecast.zip and try to start weewx and all stopped.
> I use before version 4.8 and don't know if I migrate do I need to install 
> wewx first and than install observer driver and forecast.
> after that copy old weewx.conf into /etc/weewx
> and restore mysql database and it should work, but doesn't.
> when I start weewx I get this error.
> May 27 16:23:58 web journal[6058]: weewx[6058] INFO weewx.restx: 
> StationRegistry: Registration not requested.
> May 27 16:23:58 web journal[6058]: weewx[6058] INFO weewx.restx: PWSweather: 
> Posting not enabled.
> May 27 16:23:58 web journal[6058]: weewx[6058] INFO weewx.restx: CWOP: 
> Posting not enabled.
> May 27 16:23:58 web journal[6058]: weewx[6058] INFO weewx.restx: WOW: Posting 
> not enabled.
> May 27 16:23:58 web journal[6058]: weewx[6058] INFO weewx.restx: AWEKAS: 
> Posting not enabled.
> May 27 16:23:58 web journal[6058]: weewx[6058] INFO weewx.engine: 'pyephem' 
> detected, extended almanac data is available
> May 27 16:23:58 web journal[6058]: weewx[6058] INFO user.interceptor: 
> shutting down server thread
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: Caught 
> unrecoverable exception:
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__:   
> invalid syntax (rtgd.py, line 1234)
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__:   
> Traceback (most recent call last):
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
> File "/usr/share/weewx/weewxd", line 147, in main
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
>   engine = weewx.engine.StdEngine(config_dict)
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/engine.py", line 93, in __init__
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
>   self.loadServices(config_dict)
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
> File "/usr/share/weewx/weewx/engine.py", line 161, in loadServices
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
>   obj = weeutil.weeutil.get_object(svc)(self, config_dict)
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
> File "/usr/share/weewx/weeutil/weeutil.py", line 1150, in get_object
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
>   mod = __import__(module)
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
> File "/usr/share/weewx/user/rtgd.py", line 1234
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
>   except Exception, e:
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__: 
>   ^
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__:   
> SyntaxError: invalid syntax
> May 27 16:23:58 web journal[6058]: weewx[6058] CRITICAL __main__:   
> Exiting.
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/57148ec2-5516-40e6-b02f-896df88d13e9n%40googlegroups.com.

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

Re: [weewx-user] Problem with weewx-airlink

2022-05-25 Thread 'John Kline' via weewx-user

You’re getting this because the timestamp is bad:
'ts': 85460

The specific message: user.airlink: last_report_time must be time since boot: 
85441 seconds.
is worded that way because I found airlink was reporting time since reboot 
(rather than time since epoch).  I observed this behavior until the airlink 
started reporting concentrations.  I specifically check for pm1 to determine 
this state.  In the case below, pm_1 is missing ('pm_1': None).

I wouldn’t try to get this running in weewx until you have good data.  In a 
browser, go to:
http:///v1/current_conditions

You need a good timestamp to show up here (e.g., right now, "ts": 1653499667) 
and good concentrations (rather than None); e.g., "pm_1": 5.16

Since it’s finding no valid concentrations, you are seeing the message “Could 
not get concentrations from any source.”

John

> On May 25, 2022, at 8:24 AM, anc...@gmail.com  wrote:
> 
> Hi guys,
> I just installed for the first time a Davis Airlink and I want to integrate 
> it in WeeWX with which my Davis VP2 already works. I followed the 
> instructions on the weewx-airlink page, but for some reason it is not working 
> . Here is some log:
> 
> May 25 16:11:01 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Could not get concentrations from any source.
> May 25 16:11:01 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:03 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:05 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink: 
> last_report_time must be time since boot: 85441 seconds.  Record: {'data': 
> {'did': '001D0A100829', 'name': 'IIS Ceccano', 'ts': 85441, 'conditions': 
> [{'lsid': 522424, 'data_structure_type': 6, 'temp': 92.0, 'hum': 26.5, 
> 'dew_point': 52.7, 'wet_bulb': 60.0, 'heat_index': 89.8, 'pm_1_last': 4, 
> 'pm_2p5_last': 5, 'pm_10_last': 5, 'pm_1': None, 'pm_2p5': None, 
> 'pm_2p5_last_1_hour': None, 'pm_2p5_last_3_hours': None, 
> 'pm_2p5_last_24_hours': None, 'pm_2p5_nowcast': None, 'pm_10': None, 
> 'pm_10_last_1_hour': None, 'pm_10_last_3_hours': None, 'pm_10_last_24_hours': 
> None, 'pm_10_nowcast': None, 'last_report_time': 85441, 
> 'pct_pm_data_last_1_hour': None, 'pct_pm_data_last_3_hours': None, 
> 'pct_pm_data_nowcast': None, 'pct_pm_data_last_24_hours': None}]}, 'error': 
> None}
> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Could not get concentrations from any source.
> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:09 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:11 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:12 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink: 
> last_report_time must be time since boot: 85446 seconds.  Record: {'data': 
> {'did': '001D0A100829', 'name': 'IIS Ceccano', 'ts': 85446, 'conditions': 
> [{'lsid': 522424, 'data_structure_type': 6, 'temp': 92.1, 'hum': 26.7, 
> 'dew_point': 53.0, 'wet_bulb': 60.3, 'heat_index': 89.9, 'pm_1_last': 4, 
> 'pm_2p5_last': 4, 'pm_10_last': 4, 'pm_1': None, 'pm_2p5': None, 
> 'pm_2p5_last_1_hour': None, 'pm_2p5_last_3_hours': None, 
> 'pm_2p5_last_24_hours': None, 'pm_2p5_nowcast': None, 'pm_10': None, 
> 'pm_10_last_1_hour': None, 'pm_10_last_3_hours': None, 'pm_10_last_24_hours': 
> None, 'pm_10_nowcast': None, 'last_report_time': 85446, 
> 'pct_pm_data_last_1_hour': None, 'pct_pm_data_last_3_hours': None, 
> 'pct_pm_data_nowcast': None, 'pct_pm_data_last_24_hours': None}]}, 'error': 
> None}
> May 25 16:11:12 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Could not get concentrations from any source.
> May 25 16:11:13 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:15 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] INFO weewx.manager: 
> Added record 2022-05-25 16:11:00 CEST (1653487860) to database 'weewx.sdb'
> May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] INFO weewx.manager: 
> Added record 2022-05-25 16:11:00 CEST (1653487860) to daily summary in 
> 'weewx.sdb'
> May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:17 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink: 
> Found no concentrations to insert.
> May 25 16:11:19 StazioneMe

Re: [weewx-user] Re: Realtime-_gauge-data.txt

That rsync command you listed, it is in root’s crontab?
And why aren’t you doing the rsync in weewx?

> On May 23, 2022, at 1:15 PM, philip@gmail.com  
> wrote:
> 
> Im using rsync to copy the public_html folder to my server using a cron job 
> every 10mins = rsync -a /home/weewx/public_html/ lushe...@192.xxx.x.xxx 
> etc etc
> Then thought I would use rsync in rtgd, from weewx.conf to update the gauges 
> in real time.
> OS is Buster 10 using a Raspberry Pi
> 
> 
>> On Monday, May 23, 2022 at 8:28:18 PM UTC+1 jo...@johnkline.com wrote:
>> I’m curious, are you using rsync to publish weewx?  I’m asking because rtgd 
>> is calling the same weewx method.
>> 
>> If you are using rsync to publish weewx, please send that section of your 
>> weewx.conf.  There must be some difference.
>> 
>> Also, what OS are you using?  I’m worried that it is Windows from your 
>> paths.  If it is, I’m unlikely to be able to debug this.
>> 
>>>> On May 23, 2022, at 10:56 AM, philip@gmail.com  
>>>> wrote:
>>>> 
>>> Im using LushEr21 for both and ssh LushEr21@server-ip-address logs on to 
>>> the server without a password
>> 
>>> 
>>> 
>>>> On Monday, May 23, 2022 at 4:39:47 PM UTC+1 jo...@johnkline.com wrote:
>>>> 
>>>> 
>>>> I’m assuming that  in ssh-copy-id -i ~/.ssh/id_rsa.pub 
>>>> @ - is:
>>>> LushEr21
>>>> Since that what you specified in weewx.conf.
>>>> 
>>>> Please confirm that the following works (i.e., you are logged in to 
>>>>  as LushEr21 without having to enter a password or an 
>>>> [empty] passphrase:
>>>> (As root:)
>>>> ssh LushEr21@
>>>> 
>>>>>> On May 23, 2022, at 7:00 AM, philip@gmail.com  
>>>>>> wrote:
>>>>>> 
>>>>> For ssh 
>>>> 
>>>>> I used when I was root
>>>>> ssh-keygen -f C:\Users\\.ssh\id_rsa -t rsa -P ""
>>>>> ssh-copy-id -i ~/.ssh/id_rsa.pub @ -o 
>>>>> StrictHostKeyChecking=No
>>>>> Should I have a file /usr/bin/ssh-askpass
>>>>> Sorry to be a pain
>>>>> Phil
>>>>> 
>>>>> 
>>>>>> On Monday, May 23, 2022 at 1:39:10 PM UTC+1 jo...@johnkline.com wrote:
>>>>>> I don’t recommend extending the timeout.  It’s there so that requests 
>>>>>> don’t build up.
>>>>>> Are you sure you have ssh set up correctly?  In particular, did you set 
>>>>>> it up for the same user as weewx is running as?  That’s often root.  If 
>>>>>> weewx is running as root for you, please try to ssh in without a 
>>>>>> password when you are logged in as root.
>>>>>> 
>>>>>>>> On May 23, 2022, at 3:13 AM, philip@gmail.com 
>>>>>>>>  wrote:
>>>>>>>> 
>>>>>>> Thanks John
>>>>>>>  I now get 
>>>>>>> May 23 10:59:03 raspberrypi weewx-weewx[1438] ERROR 
>>>>>>> weeutil.rsyncupload: [['rsync', '--archive', '--stats', '--timeout=4', 
>>>>>>> '-e ssh -o ConnectTimeout=1', '/home/weewx/public_html/gauge-data.txt', 
>>>>>>> 'lush...@192.xxx.x.xxx:/volume1/web/SheringhamDDNS/gaugedata/gauge-data.txt']]
>>>>>>>  reported errors: ssh_askpass: exec(/usr/bin/ssh-askpass): No such file 
>>>>>>> or directory. [sender] io timeout after 4 seconds -- exiting. rsync 
>>>>>>> error: timeout in data send/receive (code 30) at io.c(204) 
>>>>>>> [sender=3.1.3]
>>>>>>> May 23 10:59:03 raspberrypi weewx-weewx[1438] INFO weeutil.rsyncupload: 
>>>>>>> rsync executed in 6.03 seconds
>>>>>>> I had to extend the Timeout = 4 as it would time out.
>>>>>>> I dont appear to have a file usr/bin/ssh_askpass When the passwordless 
>>>>>>> key was set up I believe it saved the info to ssh-keygen
>>>>>>> 
>>>>>>> rsync -v /home/weewx/public_html/gauge-data.txt 
>>>>>>> lush...@192.xxx.x.xxx:/volume1/web/SheringhamDDNS works OK in a cron job
>>>>>>> Phil
>>>>>>>> On Sunday, May 22, 2022 at 6:24:58 PM UTC+1 jo...@johnkline.com wrote:
>>>>>>>> OK, you could also replace rtgd.py (in weewx’s bin/user directory) 
>>>>>>&g

Re: [weewx-user] Re: Realtime-_gauge-data.txt

I’m curious, are you using rsync to publish weewx?  I’m asking because rtgd is 
calling the same weewx method.

If you are using rsync to publish weewx, please send that section of your 
weewx.conf.  There must be some difference.

Also, what OS are you using?  I’m worried that it is Windows from your paths.  
If it is, I’m unlikely to be able to debug this.

> On May 23, 2022, at 10:56 AM, philip@gmail.com  
> wrote:
> 
> Im using LushEr21 for both and ssh LushEr21@server-ip-address logs on to the 
> server without a password
> 
>> On Monday, May 23, 2022 at 4:39:47 PM UTC+1 jo...@johnkline.com wrote:
>> 
>> 
>> I’m assuming that  in ssh-copy-id -i ~/.ssh/id_rsa.pub 
>> @ - is:
>> LushEr21
>> Since that what you specified in weewx.conf.
>> 
>> Please confirm that the following works (i.e., you are logged in to 
>>  as LushEr21 without having to enter a password or an 
>> [empty] passphrase:
>> (As root:)
>> ssh LushEr21@
>> 
>>>> On May 23, 2022, at 7:00 AM, philip@gmail.com  
>>>> wrote:
>>>> 
>>> For ssh 
>> 
>>> I used when I was root
>>> ssh-keygen -f C:\Users\\.ssh\id_rsa -t rsa -P ""
>>> ssh-copy-id -i ~/.ssh/id_rsa.pub @ -o 
>>> StrictHostKeyChecking=No
>>> Should I have a file /usr/bin/ssh-askpass
>>> Sorry to be a pain
>>> Phil
>>> 
>>> 
>>>> On Monday, May 23, 2022 at 1:39:10 PM UTC+1 jo...@johnkline.com wrote:
>>>> I don’t recommend extending the timeout.  It’s there so that requests 
>>>> don’t build up.
>>>> Are you sure you have ssh set up correctly?  In particular, did you set it 
>>>> up for the same user as weewx is running as?  That’s often root.  If weewx 
>>>> is running as root for you, please try to ssh in without a password when 
>>>> you are logged in as root.
>>>> 
>>>>>> On May 23, 2022, at 3:13 AM, philip@gmail.com  
>>>>>> wrote:
>>>>>> 
>>>>> Thanks John
>>>>>  I now get 
>>>>> May 23 10:59:03 raspberrypi weewx-weewx[1438] ERROR weeutil.rsyncupload: 
>>>>> [['rsync', '--archive', '--stats', '--timeout=4', '-e ssh -o 
>>>>> ConnectTimeout=1', '/home/weewx/public_html/gauge-data.txt', 
>>>>> 'lush...@192.xxx.x.xxx:/volume1/web/SheringhamDDNS/gaugedata/gauge-data.txt']]
>>>>>  reported errors: ssh_askpass: exec(/usr/bin/ssh-askpass): No such file 
>>>>> or directory. [sender] io timeout after 4 seconds -- exiting. rsync 
>>>>> error: timeout in data send/receive (code 30) at io.c(204) [sender=3.1.3]
>>>>> May 23 10:59:03 raspberrypi weewx-weewx[1438] INFO weeutil.rsyncupload: 
>>>>> rsync executed in 6.03 seconds
>>>>> I had to extend the Timeout = 4 as it would time out.
>>>>> I dont appear to have a file usr/bin/ssh_askpass When the passwordless 
>>>>> key was set up I believe it saved the info to ssh-keygen
>>>>> 
>>>>> rsync -v /home/weewx/public_html/gauge-data.txt 
>>>>> lush...@192.xxx.x.xxx:/volume1/web/SheringhamDDNS works OK in a cron job
>>>>> Phil
>>>>>> On Sunday, May 22, 2022 at 6:24:58 PM UTC+1 jo...@johnkline.com wrote:
>>>>>> OK, you could also replace rtgd.py (in weewx’s bin/user directory) with 
>>>>>> the file at:
>>>>>> https://github.com/chaunceygardiner/weewx-realtime_gauge-data/blob/master/bin/user/rtgd.py
>>>>>> 
>>>>>> I’ve also sent Gary a PR at:
>>>>>> https://github.com/gjr80/weewx-realtime_gauge-data/pull/28
>>>>>> 
>>>>>> 
>>>>>>>> On May 22, 2022, at 10:07 AM, John Kline  wrote:
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>>> Never mind.  I installed it and found the issue.  It’s been broken 
>>>>>>> since it was refactored.
>>>>>>> 
>>>>>>> Below is the patch to get it working.  I’ll also follow up with a URL 
>>>>>>> to grab the file from github; as well as a PR to Gary (who may take it 
>>>>>>> if he notices it).
>>>>>>> 
>>>>>>> diff --git a/bin/user/rtgd.py b/bin/user/rtgd.py
>>>>>>> index 9f631c9..09ddd24 100644
>>>>>>> --- a/bin/user/rtgd.py
>>>>>>> +++ b/bin/user/rtgd.py
>>>>>>> @@ -1300,7

Re: [weewx-user] Re: Realtime-_gauge-data.txt



I’m assuming that  in ssh-copy-id -i ~/.ssh/id_rsa.pub 
@ - is:
LushEr21
Since that what you specified in weewx.conf.

Please confirm that the following works (i.e., you are logged in to 
 as LushEr21 without having to enter a password or an 
[empty] passphrase:
(As root:)
ssh LushEr21@

> On May 23, 2022, at 7:00 AM, philip@gmail.com  
> wrote:
> For ssh 
> I used when I was root
> ssh-keygen -f C:\Users\\.ssh\id_rsa -t rsa -P ""
> ssh-copy-id -i ~/.ssh/id_rsa.pub @ -o 
> StrictHostKeyChecking=No
> Should I have a file /usr/bin/ssh-askpass
> Sorry to be a pain
> Phil
> 
> 
> On Monday, May 23, 2022 at 1:39:10 PM UTC+1 jo...@johnkline.com wrote:
>> I don’t recommend extending the timeout.  It’s there so that requests don’t 
>> build up.
>> Are you sure you have ssh set up correctly?  In particular, did you set it 
>> up for the same user as weewx is running as?  That’s often root.  If weewx 
>> is running as root for you, please try to ssh in without a password when you 
>> are logged in as root.
>> 
>>> On May 23, 2022, at 3:13 AM, philip@gmail.com  
>>> wrote:
>> 
>>> Thanks John
>>>  I now get 
>>> May 23 10:59:03 raspberrypi weewx-weewx[1438] ERROR weeutil.rsyncupload: 
>>> [['rsync', '--archive', '--stats', '--timeout=4', '-e ssh -o 
>>> ConnectTimeout=1', '/home/weewx/public_html/gauge-data.txt', 
>>> 'lush...@192.xxx.x.xxx:/volume1/web/SheringhamDDNS/gaugedata/gauge-data.txt']]
>>>  reported errors: ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or 
>>> directory. [sender] io timeout after 4 seconds -- exiting. rsync error: 
>>> timeout in data send/receive (code 30) at io.c(204) [sender=3.1.3]
>>> May 23 10:59:03 raspberrypi weewx-weewx[1438] INFO weeutil.rsyncupload: 
>>> rsync executed in 6.03 seconds
>>> I had to extend the Timeout = 4 as it would time out.
>>> I dont appear to have a file usr/bin/ssh_askpass When the passwordless key 
>>> was set up I believe it saved the info to ssh-keygen
>>> 
>>> rsync -v /home/weewx/public_html/gauge-data.txt 
>>> lush...@192.xxx.x.xxx:/volume1/web/SheringhamDDNS works OK in a cron job
>>> Phil
>>> On Sunday, May 22, 2022 at 6:24:58 PM UTC+1 jo...@johnkline.com wrote:
>>>> OK, you could also replace rtgd.py (in weewx’s bin/user directory) with 
>>>> the file at:
>>>> https://github.com/chaunceygardiner/weewx-realtime_gauge-data/blob/master/bin/user/rtgd.py
>>>> 
>>>> I’ve also sent Gary a PR at:
>>>> https://github.com/gjr80/weewx-realtime_gauge-data/pull/28
>>>> 
>>>> 
>>>>> On May 22, 2022, at 10:07 AM, John Kline  wrote:
>>>>> 
>>>> 
>>>>> Never mind.  I installed it and found the issue.  It’s been broken since 
>>>>> it was refactored.
>>>>> 
>>>>> Below is the patch to get it working.  I’ll also follow up with a URL to 
>>>>> grab the file from github; as well as a PR to Gary (who may take it if he 
>>>>> notices it).
>>>>> 
>>>>> diff --git a/bin/user/rtgd.py b/bin/user/rtgd.py
>>>>> index 9f631c9..09ddd24 100644
>>>>> --- a/bin/user/rtgd.py
>>>>> +++ b/bin/user/rtgd.py
>>>>> @@ -1300,7 +1300,7 @@ class HttpPostExport(object):
>>>>>  # response text from remote URL if post was successful
>>>>>  self.response = post_config_dict.get('response_text', None)
>>>>>  
>>>>> -def export(self, data):
>>>>> +def export(self, data, dateTime):
>>>>>  """Post the data."""
>>>>>  
>>>>>  self.post_data(data)
>>>>> @@ -1419,10 +1419,11 @@ class RsyncExport(object):
>>>>>  self.rsync_skip_if_older_than = 
>>>>> to_int(rsync_config_dict.get('rsync_skip_if_older_than',
>>>>>   4))
>>>>>  
>>>>> -def export(self, data):
>>>>> +def export(self, data, dateTime):
>>>>>  """Rsync the data."""
>>>>>  
>>>>> -packet_time = datetime.datetime.fromtimestamp(data['dateTime'])
>>>>> +log.info("export: data: %r" % data)
>>>>> +packet_time = datetime.datetime.fromtimestamp(dateTime)
>>>>>  self.rsync_data(packet_time)

Re: [weewx-user] Re: Realtime-_gauge-data.txt