Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

*It works! I have reports!*

Now, I suspect the issue was not coming from python 2.7, but from the 
installation of the WMR200 extension.
When I shifted from python 2.7 to 3.x, after updating the apt sources, I 
re-installed the weewx package. 
I noticed changes in weewx.conf:

1) *station_type = Simulator.* I remember that was something required. But* 
I had done it before the install of the extension*, and *when I installed 
the extension, it reverted to station_type = WMR200* (or did I do something 
wrong?) and I thought it was intentional.

2) there is *a [Simulator] section*, with driver = weewx.drivers.simulator. 

I just wonder how weewx knows it should read also the WMR200 section which 
contains user.wmr200 driver... but it works.

*I have an issue with values however: my temperature is nuts, I have no 
wind etc.* I'm going to look into that and post in a separate thread if I 
can't solve it, because it looks like a different issue.

Thanks.








On Saturday, January 23, 2021 at 2:32:16 PM UTC+1 tke...@gmail.com wrote:

> It is a good idea to switch. I'll be very interested to hear if it makes 
> any difference.
>
> On Sat, Jan 23, 2021 at 5:31 AM Invisible Man  
> wrote:
>
>> I'm going to shift to python3. Let you know when it's done. Besides my 
>> bug, I think it's a good idea to abandon python 2.7 ;-)
>>
>> On Saturday, January 23, 2021 at 2:20:26 PM UTC+1 Invisible Man wrote:
>>
>>> > Yes, that was fixed with commit 624fb9e 
>>> .
>>>  
>>> It's only a problem under Python 2.7.
>>>
>>> Ok, I manually applied the fix to config.py, and now *wee_reports runs* 
>>> :)
>>>
>>> $ wee_reports /etc/weewx/weewx.conf
>>> Using configuration file /etc/weewx/weewx.conf
>>> Generating for all time
>>>
>>>
>>>- The files in public_html have been updated :-) (that's my 
>>>HTML_ROOT)
>>>- The external website has been updated :-) so the FTP worked for 
>>>sure.
>>>- The RSYNC also worked :-)
>>>- I don't have anything more related to reports in the logs, but 
>>>perhaps wee_reports does not log there.
>>>
>>> So, *it is working with wee_reports* (which is already a workaround), *but 
>>> not automatically.*
>>>
>>> Side question: would it help that I use python 3.x instead? 
>>>
>>> On Saturday, January 23, 2021 at 1:49:56 PM UTC+1 tke...@gmail.com 
>>> wrote:
>>>
 Yes, that was fixed with commit 624fb9e 
 .
  
 It's only a problem under Python 2.7.

 On Sat, Jan 23, 2021 at 4:35 AM Invisible Man  
 wrote:

> >1. Your weewx.conf file is in /etc/weewx/weewx.conf, which is a 
> location usually associated with a Debian package installer, but the rest 
> of weewx is in /home/weewx, which is usually >associated with a setup.py 
> install. Is that what you intended?
>
> Yes, that's "normal", it is because a long time ago, when there were 
> no Debian package yet, I had installed it in /home/weewx. Then, there was 
> a 
> Debian package, and I decided to use that but still use lots of things 
> from 
> the /home/weewx directory. 
>
> However, it is worth checking, so I checked : I have a weewx.conf only 
> in /etc/weewx. There is none for instance in /home/weewx tree. (there are 
> still more weewx.conf files than I expected, but I think it is normal).
>
> $ locate weewx.conf
> /etc/weewx/apache/conf.d/weewx.conf
> /etc/weewx/logwatch/conf/logfiles/weewx.conf
> /etc/weewx/logwatch/conf/services/weewx.conf
> /etc/weewx/rsyslog.d/weewx.conf
> /etc/weewx/weewx.conf
> /etc/weewx/weewx.conf-3.5.0
> /etc/weewx/weewx.conf-4.1.1
> /etc/weewx/weewx.conf-4.2.0
> /etc/weewx/weewx.conf-4.3.0
> /etc/weewx/weewx.conf.20191208202810
> /etc/weewx/weewx.conf.2020163218
> /etc/weewx/weewx.conf.20210120225317
> /etc/weewx/weewx.conf.20210120225326
> /etc/weewx/weewx.conf.bak
> /etc/weewx/weewx.conf.dist
> /etc/weewx/weewx.conf.dpkg-dist
> /etc/weewx/weewx.conf.my.4.2.0
> /etc/weewx/weewx.conf~
> /home/axelle/anonymized-weewx.conf
> /home/axelle/anonymized-weewx.conf~
> /var/lib/dpkg/info/weewx.conffiles
> /var/lib/dpkg/info/weewx.config
>
> >2. You have both FTP *and* rsync enabled. Is that what you intended?
>
> Yes. My setup is slightly complicated but I am backuping the website 
> locally to another host, and using rsync for that. I am also uploading 
> the 
> website to an external host, and that host only has FTP. That's why I use 
> both. But each is going to a different location.
> However, I'll give it a try by disabling some services (but indeed I 
> don't think that's the issue).
>
> >3. What happens if you try and use wee_reports? Does that work?
>
> Oh nice idea!
> It is failing. But 

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Tom Keffer]

It is a good idea to switch. I'll be very interested to hear if it makes
any difference.

On Sat, Jan 23, 2021 at 5:31 AM Invisible Man 
wrote:

> I'm going to shift to python3. Let you know when it's done. Besides my
> bug, I think it's a good idea to abandon python 2.7 ;-)
>
> On Saturday, January 23, 2021 at 2:20:26 PM UTC+1 Invisible Man wrote:
>
>> > Yes, that was fixed with commit 624fb9e
>> .
>> It's only a problem under Python 2.7.
>>
>> Ok, I manually applied the fix to config.py, and now *wee_reports runs*
>> :)
>>
>> $ wee_reports /etc/weewx/weewx.conf
>> Using configuration file /etc/weewx/weewx.conf
>> Generating for all time
>>
>>
>>- The files in public_html have been updated :-) (that's my HTML_ROOT)
>>- The external website has been updated :-) so the FTP worked for
>>sure.
>>- The RSYNC also worked :-)
>>- I don't have anything more related to reports in the logs, but
>>perhaps wee_reports does not log there.
>>
>> So, *it is working with wee_reports* (which is already a workaround), *but
>> not automatically.*
>>
>> Side question: would it help that I use python 3.x instead?
>>
>> On Saturday, January 23, 2021 at 1:49:56 PM UTC+1 tke...@gmail.com wrote:
>>
>>> Yes, that was fixed with commit 624fb9e
>>> .
>>> It's only a problem under Python 2.7.
>>>
>>> On Sat, Jan 23, 2021 at 4:35 AM Invisible Man 
>>> wrote:
>>>
 >1. Your weewx.conf file is in /etc/weewx/weewx.conf, which is a
 location usually associated with a Debian package installer, but the rest
 of weewx is in /home/weewx, which is usually >associated with a setup.py
 install. Is that what you intended?

 Yes, that's "normal", it is because a long time ago, when there were no
 Debian package yet, I had installed it in /home/weewx. Then, there was a
 Debian package, and I decided to use that but still use lots of things from
 the /home/weewx directory.

 However, it is worth checking, so I checked : I have a weewx.conf only
 in /etc/weewx. There is none for instance in /home/weewx tree. (there are
 still more weewx.conf files than I expected, but I think it is normal).

 $ locate weewx.conf
 /etc/weewx/apache/conf.d/weewx.conf
 /etc/weewx/logwatch/conf/logfiles/weewx.conf
 /etc/weewx/logwatch/conf/services/weewx.conf
 /etc/weewx/rsyslog.d/weewx.conf
 /etc/weewx/weewx.conf
 /etc/weewx/weewx.conf-3.5.0
 /etc/weewx/weewx.conf-4.1.1
 /etc/weewx/weewx.conf-4.2.0
 /etc/weewx/weewx.conf-4.3.0
 /etc/weewx/weewx.conf.20191208202810
 /etc/weewx/weewx.conf.2020163218
 /etc/weewx/weewx.conf.20210120225317
 /etc/weewx/weewx.conf.20210120225326
 /etc/weewx/weewx.conf.bak
 /etc/weewx/weewx.conf.dist
 /etc/weewx/weewx.conf.dpkg-dist
 /etc/weewx/weewx.conf.my.4.2.0
 /etc/weewx/weewx.conf~
 /home/axelle/anonymized-weewx.conf
 /home/axelle/anonymized-weewx.conf~
 /var/lib/dpkg/info/weewx.conffiles
 /var/lib/dpkg/info/weewx.config

 >2. You have both FTP *and* rsync enabled. Is that what you intended?

 Yes. My setup is slightly complicated but I am backuping the website
 locally to another host, and using rsync for that. I am also uploading the
 website to an external host, and that host only has FTP. That's why I use
 both. But each is going to a different location.
 However, I'll give it a try by disabling some services (but indeed I
 don't think that's the issue).

 >3. What happens if you try and use wee_reports? Does that work?

 Oh nice idea!
 It is failing. But it seems like another issue... A French accent in
 weewx.conf perhaps ?

 $ wee_reports /etc/weewx/weewx.conf
 Using configuration file /etc/weewx/weewx.conf
 Generating for all time
 Traceback (most recent call last):
   File "/usr/share/weewx/wee_reports", line 103, in 
 main()
   File "/usr/share/weewx/wee_reports", line 99, in main
 t.run()
   File "/usr/share/weewx/weewx/reportengine.py", line 141, in run
 skin_dict = self._build_skin_dict(report)
   File "/usr/share/weewx/weewx/reportengine.py", line 249, in
 _build_skin_dict
 merge_dict =
 weeutil.config.deep_copy(self.config_dict)['StdReport']['Defaults']
   File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
 new_value = deep_copy(old_value, new_dict, new_dict.depth+1,
 new_dict.main)
   File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
 new_value = deep_copy(old_value, new_dict, new_dict.depth+1,
 new_dict.main)
   File "/usr/share/weewx/weeutil/config.py", line 262, in deep_copy
 new_dict.comments[entry] = [str(x) for x in
 old_dict.comments[entry]]
 UnicodeEncodeError: 'ascii' 

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

I'm going to shift to python3. Let you know when it's done. Besides my bug, 
I think it's a good idea to abandon python 2.7 ;-)

On Saturday, January 23, 2021 at 2:20:26 PM UTC+1 Invisible Man wrote:

> > Yes, that was fixed with commit 624fb9e 
> .
>  
> It's only a problem under Python 2.7.
>
> Ok, I manually applied the fix to config.py, and now *wee_reports runs* :)
>
> $ wee_reports /etc/weewx/weewx.conf
> Using configuration file /etc/weewx/weewx.conf
> Generating for all time
>
>
>- The files in public_html have been updated :-) (that's my HTML_ROOT)
>- The external website has been updated :-) so the FTP worked for sure.
>- The RSYNC also worked :-)
>- I don't have anything more related to reports in the logs, but 
>perhaps wee_reports does not log there.
>
> So, *it is working with wee_reports* (which is already a workaround), *but 
> not automatically.*
>
> Side question: would it help that I use python 3.x instead? 
>
> On Saturday, January 23, 2021 at 1:49:56 PM UTC+1 tke...@gmail.com wrote:
>
>> Yes, that was fixed with commit 624fb9e 
>> .
>>  
>> It's only a problem under Python 2.7.
>>
>> On Sat, Jan 23, 2021 at 4:35 AM Invisible Man  
>> wrote:
>>
>>> >1. Your weewx.conf file is in /etc/weewx/weewx.conf, which is a 
>>> location usually associated with a Debian package installer, but the rest 
>>> of weewx is in /home/weewx, which is usually >associated with a setup.py 
>>> install. Is that what you intended?
>>>
>>> Yes, that's "normal", it is because a long time ago, when there were no 
>>> Debian package yet, I had installed it in /home/weewx. Then, there was a 
>>> Debian package, and I decided to use that but still use lots of things from 
>>> the /home/weewx directory. 
>>>
>>> However, it is worth checking, so I checked : I have a weewx.conf only 
>>> in /etc/weewx. There is none for instance in /home/weewx tree. (there are 
>>> still more weewx.conf files than I expected, but I think it is normal).
>>>
>>> $ locate weewx.conf
>>> /etc/weewx/apache/conf.d/weewx.conf
>>> /etc/weewx/logwatch/conf/logfiles/weewx.conf
>>> /etc/weewx/logwatch/conf/services/weewx.conf
>>> /etc/weewx/rsyslog.d/weewx.conf
>>> /etc/weewx/weewx.conf
>>> /etc/weewx/weewx.conf-3.5.0
>>> /etc/weewx/weewx.conf-4.1.1
>>> /etc/weewx/weewx.conf-4.2.0
>>> /etc/weewx/weewx.conf-4.3.0
>>> /etc/weewx/weewx.conf.20191208202810
>>> /etc/weewx/weewx.conf.2020163218
>>> /etc/weewx/weewx.conf.20210120225317
>>> /etc/weewx/weewx.conf.20210120225326
>>> /etc/weewx/weewx.conf.bak
>>> /etc/weewx/weewx.conf.dist
>>> /etc/weewx/weewx.conf.dpkg-dist
>>> /etc/weewx/weewx.conf.my.4.2.0
>>> /etc/weewx/weewx.conf~
>>> /home/axelle/anonymized-weewx.conf
>>> /home/axelle/anonymized-weewx.conf~
>>> /var/lib/dpkg/info/weewx.conffiles
>>> /var/lib/dpkg/info/weewx.config
>>>
>>> >2. You have both FTP *and* rsync enabled. Is that what you intended?
>>>
>>> Yes. My setup is slightly complicated but I am backuping the website 
>>> locally to another host, and using rsync for that. I am also uploading the 
>>> website to an external host, and that host only has FTP. That's why I use 
>>> both. But each is going to a different location.
>>> However, I'll give it a try by disabling some services (but indeed I 
>>> don't think that's the issue).
>>>
>>> >3. What happens if you try and use wee_reports? Does that work?
>>>
>>> Oh nice idea!
>>> It is failing. But it seems like another issue... A French accent in 
>>> weewx.conf perhaps ?
>>>
>>> $ wee_reports /etc/weewx/weewx.conf
>>> Using configuration file /etc/weewx/weewx.conf
>>> Generating for all time
>>> Traceback (most recent call last):
>>>   File "/usr/share/weewx/wee_reports", line 103, in 
>>> main()
>>>   File "/usr/share/weewx/wee_reports", line 99, in main
>>> t.run()
>>>   File "/usr/share/weewx/weewx/reportengine.py", line 141, in run
>>> skin_dict = self._build_skin_dict(report)
>>>   File "/usr/share/weewx/weewx/reportengine.py", line 249, in 
>>> _build_skin_dict
>>> merge_dict = 
>>> weeutil.config.deep_copy(self.config_dict)['StdReport']['Defaults']
>>>   File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
>>> new_value = deep_copy(old_value, new_dict, new_dict.depth+1, 
>>> new_dict.main)
>>>   File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
>>> new_value = deep_copy(old_value, new_dict, new_dict.depth+1, 
>>> new_dict.main)
>>>   File "/usr/share/weewx/weeutil/config.py", line 262, in deep_copy
>>> new_dict.comments[entry] = [str(x) for x in old_dict.comments[entry]]
>>> UnicodeEncodeError: 'ascii' codec can't encode character u'\xb0' in 
>>> position 56: ordinal not in range(128)
>>>
>>> On Friday, January 22, 2021 at 11:08:39 PM UTC+1 tke...@gmail.com wrote:
>>>
 Rather strange. A few questions:

 1. Your weewx.conf file 

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

> Yes, that was fixed with commit 624fb9e 
.
 
It's only a problem under Python 2.7.

Ok, I manually applied the fix to config.py, and now *wee_reports runs* :)

$ wee_reports /etc/weewx/weewx.conf
Using configuration file /etc/weewx/weewx.conf
Generating for all time


   - The files in public_html have been updated :-) (that's my HTML_ROOT)
   - The external website has been updated :-) so the FTP worked for sure.
   - The RSYNC also worked :-)
   - I don't have anything more related to reports in the logs, but perhaps 
   wee_reports does not log there.

So, *it is working with wee_reports* (which is already a workaround), *but 
not automatically.*

Side question: would it help that I use python 3.x instead? 

On Saturday, January 23, 2021 at 1:49:56 PM UTC+1 tke...@gmail.com wrote:

> Yes, that was fixed with commit 624fb9e 
> .
>  
> It's only a problem under Python 2.7.
>
> On Sat, Jan 23, 2021 at 4:35 AM Invisible Man  
> wrote:
>
>> >1. Your weewx.conf file is in /etc/weewx/weewx.conf, which is a location 
>> usually associated with a Debian package installer, but the rest of weewx 
>> is in /home/weewx, which is usually >associated with a setup.py install. Is 
>> that what you intended?
>>
>> Yes, that's "normal", it is because a long time ago, when there were no 
>> Debian package yet, I had installed it in /home/weewx. Then, there was a 
>> Debian package, and I decided to use that but still use lots of things from 
>> the /home/weewx directory. 
>>
>> However, it is worth checking, so I checked : I have a weewx.conf only in 
>> /etc/weewx. There is none for instance in /home/weewx tree. (there are 
>> still more weewx.conf files than I expected, but I think it is normal).
>>
>> $ locate weewx.conf
>> /etc/weewx/apache/conf.d/weewx.conf
>> /etc/weewx/logwatch/conf/logfiles/weewx.conf
>> /etc/weewx/logwatch/conf/services/weewx.conf
>> /etc/weewx/rsyslog.d/weewx.conf
>> /etc/weewx/weewx.conf
>> /etc/weewx/weewx.conf-3.5.0
>> /etc/weewx/weewx.conf-4.1.1
>> /etc/weewx/weewx.conf-4.2.0
>> /etc/weewx/weewx.conf-4.3.0
>> /etc/weewx/weewx.conf.20191208202810
>> /etc/weewx/weewx.conf.2020163218
>> /etc/weewx/weewx.conf.20210120225317
>> /etc/weewx/weewx.conf.20210120225326
>> /etc/weewx/weewx.conf.bak
>> /etc/weewx/weewx.conf.dist
>> /etc/weewx/weewx.conf.dpkg-dist
>> /etc/weewx/weewx.conf.my.4.2.0
>> /etc/weewx/weewx.conf~
>> /home/axelle/anonymized-weewx.conf
>> /home/axelle/anonymized-weewx.conf~
>> /var/lib/dpkg/info/weewx.conffiles
>> /var/lib/dpkg/info/weewx.config
>>
>> >2. You have both FTP *and* rsync enabled. Is that what you intended?
>>
>> Yes. My setup is slightly complicated but I am backuping the website 
>> locally to another host, and using rsync for that. I am also uploading the 
>> website to an external host, and that host only has FTP. That's why I use 
>> both. But each is going to a different location.
>> However, I'll give it a try by disabling some services (but indeed I 
>> don't think that's the issue).
>>
>> >3. What happens if you try and use wee_reports? Does that work?
>>
>> Oh nice idea!
>> It is failing. But it seems like another issue... A French accent in 
>> weewx.conf perhaps ?
>>
>> $ wee_reports /etc/weewx/weewx.conf
>> Using configuration file /etc/weewx/weewx.conf
>> Generating for all time
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/wee_reports", line 103, in 
>> main()
>>   File "/usr/share/weewx/wee_reports", line 99, in main
>> t.run()
>>   File "/usr/share/weewx/weewx/reportengine.py", line 141, in run
>> skin_dict = self._build_skin_dict(report)
>>   File "/usr/share/weewx/weewx/reportengine.py", line 249, in 
>> _build_skin_dict
>> merge_dict = 
>> weeutil.config.deep_copy(self.config_dict)['StdReport']['Defaults']
>>   File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
>> new_value = deep_copy(old_value, new_dict, new_dict.depth+1, 
>> new_dict.main)
>>   File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
>> new_value = deep_copy(old_value, new_dict, new_dict.depth+1, 
>> new_dict.main)
>>   File "/usr/share/weewx/weeutil/config.py", line 262, in deep_copy
>> new_dict.comments[entry] = [str(x) for x in old_dict.comments[entry]]
>> UnicodeEncodeError: 'ascii' codec can't encode character u'\xb0' in 
>> position 56: ordinal not in range(128)
>>
>> On Friday, January 22, 2021 at 11:08:39 PM UTC+1 tke...@gmail.com wrote:
>>
>>> Rather strange. A few questions:
>>>
>>> 1. Your weewx.conf file is in /etc/weewx/weewx.conf, which is a location 
>>> usually associated with a Debian package installer, but the rest of weewx 
>>> is in /home/weewx, which is usually associated with a setup.py install. Is 
>>> that what you intended?
>>>
>>> 2. You have both FTP *and* rsync enabled. Is that what you intended?
>>>
>>> However, I 

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Tom Keffer]

Yes, that was fixed with commit 624fb9e
.
It's only a problem under Python 2.7.

On Sat, Jan 23, 2021 at 4:35 AM Invisible Man 
wrote:

> >1. Your weewx.conf file is in /etc/weewx/weewx.conf, which is a location
> usually associated with a Debian package installer, but the rest of weewx
> is in /home/weewx, which is usually >associated with a setup.py install. Is
> that what you intended?
>
> Yes, that's "normal", it is because a long time ago, when there were no
> Debian package yet, I had installed it in /home/weewx. Then, there was a
> Debian package, and I decided to use that but still use lots of things from
> the /home/weewx directory.
>
> However, it is worth checking, so I checked : I have a weewx.conf only in
> /etc/weewx. There is none for instance in /home/weewx tree. (there are
> still more weewx.conf files than I expected, but I think it is normal).
>
> $ locate weewx.conf
> /etc/weewx/apache/conf.d/weewx.conf
> /etc/weewx/logwatch/conf/logfiles/weewx.conf
> /etc/weewx/logwatch/conf/services/weewx.conf
> /etc/weewx/rsyslog.d/weewx.conf
> /etc/weewx/weewx.conf
> /etc/weewx/weewx.conf-3.5.0
> /etc/weewx/weewx.conf-4.1.1
> /etc/weewx/weewx.conf-4.2.0
> /etc/weewx/weewx.conf-4.3.0
> /etc/weewx/weewx.conf.20191208202810
> /etc/weewx/weewx.conf.2020163218
> /etc/weewx/weewx.conf.20210120225317
> /etc/weewx/weewx.conf.20210120225326
> /etc/weewx/weewx.conf.bak
> /etc/weewx/weewx.conf.dist
> /etc/weewx/weewx.conf.dpkg-dist
> /etc/weewx/weewx.conf.my.4.2.0
> /etc/weewx/weewx.conf~
> /home/axelle/anonymized-weewx.conf
> /home/axelle/anonymized-weewx.conf~
> /var/lib/dpkg/info/weewx.conffiles
> /var/lib/dpkg/info/weewx.config
>
> >2. You have both FTP *and* rsync enabled. Is that what you intended?
>
> Yes. My setup is slightly complicated but I am backuping the website
> locally to another host, and using rsync for that. I am also uploading the
> website to an external host, and that host only has FTP. That's why I use
> both. But each is going to a different location.
> However, I'll give it a try by disabling some services (but indeed I don't
> think that's the issue).
>
> >3. What happens if you try and use wee_reports? Does that work?
>
> Oh nice idea!
> It is failing. But it seems like another issue... A French accent in
> weewx.conf perhaps ?
>
> $ wee_reports /etc/weewx/weewx.conf
> Using configuration file /etc/weewx/weewx.conf
> Generating for all time
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_reports", line 103, in 
> main()
>   File "/usr/share/weewx/wee_reports", line 99, in main
> t.run()
>   File "/usr/share/weewx/weewx/reportengine.py", line 141, in run
> skin_dict = self._build_skin_dict(report)
>   File "/usr/share/weewx/weewx/reportengine.py", line 249, in
> _build_skin_dict
> merge_dict =
> weeutil.config.deep_copy(self.config_dict)['StdReport']['Defaults']
>   File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
> new_value = deep_copy(old_value, new_dict, new_dict.depth+1,
> new_dict.main)
>   File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
> new_value = deep_copy(old_value, new_dict, new_dict.depth+1,
> new_dict.main)
>   File "/usr/share/weewx/weeutil/config.py", line 262, in deep_copy
> new_dict.comments[entry] = [str(x) for x in old_dict.comments[entry]]
> UnicodeEncodeError: 'ascii' codec can't encode character u'\xb0' in
> position 56: ordinal not in range(128)
>
> On Friday, January 22, 2021 at 11:08:39 PM UTC+1 tke...@gmail.com wrote:
>
>> Rather strange. A few questions:
>>
>> 1. Your weewx.conf file is in /etc/weewx/weewx.conf, which is a location
>> usually associated with a Debian package installer, but the rest of weewx
>> is in /home/weewx, which is usually associated with a setup.py install. Is
>> that what you intended?
>>
>> 2. You have both FTP *and* rsync enabled. Is that what you intended?
>>
>> However, I don't know why either of these would cause your reports not to
>> run to completion.
>>
>> 3. What happens if you try and use wee_reports? Does that work?
>>
>> -tk
>>
>>
>> On Fri, Jan 22, 2021 at 12:55 PM Invisible Man 
>> wrote:
>>
>>> I've re-read the documentation for the wmr200 driver extension (
>>> https://github.com/weewx/weewx-wmr200). I'm not sure my configuration
>>> is correct. I don't understand the doc very well .
>>>
>>> - Am I meant to have something in sensor_map, or is default correct?
>>> - Am I meant to have mode set to something?
>>> - Am I meant to uncomment driver = weewx.drivers.simulator ?
>>>
>>> This is what I have:
>>>
>>> [WMR200]
>>> # This section is for the Oregon Scientific WMR200
>>>
>>> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
>>> model = WMR200
>>>
>>> # The driver to use:
>>> driver = user.wmr200
>>>
>>> # default is 300 seconds
>>> archive_interval = 600
>>>
>>>
>>>
>>> 

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

>1. Your weewx.conf file is in /etc/weewx/weewx.conf, which is a location 
usually associated with a Debian package installer, but the rest of weewx 
is in /home/weewx, which is usually >associated with a setup.py install. Is 
that what you intended?

Yes, that's "normal", it is because a long time ago, when there were no 
Debian package yet, I had installed it in /home/weewx. Then, there was a 
Debian package, and I decided to use that but still use lots of things from 
the /home/weewx directory. 

However, it is worth checking, so I checked : I have a weewx.conf only in 
/etc/weewx. There is none for instance in /home/weewx tree. (there are 
still more weewx.conf files than I expected, but I think it is normal).

$ locate weewx.conf
/etc/weewx/apache/conf.d/weewx.conf
/etc/weewx/logwatch/conf/logfiles/weewx.conf
/etc/weewx/logwatch/conf/services/weewx.conf
/etc/weewx/rsyslog.d/weewx.conf
/etc/weewx/weewx.conf
/etc/weewx/weewx.conf-3.5.0
/etc/weewx/weewx.conf-4.1.1
/etc/weewx/weewx.conf-4.2.0
/etc/weewx/weewx.conf-4.3.0
/etc/weewx/weewx.conf.20191208202810
/etc/weewx/weewx.conf.2020163218
/etc/weewx/weewx.conf.20210120225317
/etc/weewx/weewx.conf.20210120225326
/etc/weewx/weewx.conf.bak
/etc/weewx/weewx.conf.dist
/etc/weewx/weewx.conf.dpkg-dist
/etc/weewx/weewx.conf.my.4.2.0
/etc/weewx/weewx.conf~
/home/axelle/anonymized-weewx.conf
/home/axelle/anonymized-weewx.conf~
/var/lib/dpkg/info/weewx.conffiles
/var/lib/dpkg/info/weewx.config

>2. You have both FTP *and* rsync enabled. Is that what you intended?

Yes. My setup is slightly complicated but I am backuping the website 
locally to another host, and using rsync for that. I am also uploading the 
website to an external host, and that host only has FTP. That's why I use 
both. But each is going to a different location.
However, I'll give it a try by disabling some services (but indeed I don't 
think that's the issue).

>3. What happens if you try and use wee_reports? Does that work?

Oh nice idea!
It is failing. But it seems like another issue... A French accent in 
weewx.conf perhaps ?

$ wee_reports /etc/weewx/weewx.conf
Using configuration file /etc/weewx/weewx.conf
Generating for all time
Traceback (most recent call last):
  File "/usr/share/weewx/wee_reports", line 103, in 
main()
  File "/usr/share/weewx/wee_reports", line 99, in main
t.run()
  File "/usr/share/weewx/weewx/reportengine.py", line 141, in run
skin_dict = self._build_skin_dict(report)
  File "/usr/share/weewx/weewx/reportengine.py", line 249, in 
_build_skin_dict
merge_dict = 
weeutil.config.deep_copy(self.config_dict)['StdReport']['Defaults']
  File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
new_value = deep_copy(old_value, new_dict, new_dict.depth+1, 
new_dict.main)
  File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
new_value = deep_copy(old_value, new_dict, new_dict.depth+1, 
new_dict.main)
  File "/usr/share/weewx/weeutil/config.py", line 262, in deep_copy
new_dict.comments[entry] = [str(x) for x in old_dict.comments[entry]]
UnicodeEncodeError: 'ascii' codec can't encode character u'\xb0' in 
position 56: ordinal not in range(128)

On Friday, January 22, 2021 at 11:08:39 PM UTC+1 tke...@gmail.com wrote:

> Rather strange. A few questions:
>
> 1. Your weewx.conf file is in /etc/weewx/weewx.conf, which is a location 
> usually associated with a Debian package installer, but the rest of weewx 
> is in /home/weewx, which is usually associated with a setup.py install. Is 
> that what you intended?
>
> 2. You have both FTP *and* rsync enabled. Is that what you intended?
>
> However, I don't know why either of these would cause your reports not to 
> run to completion.
>
> 3. What happens if you try and use wee_reports? Does that work?
>
> -tk
>
>
> On Fri, Jan 22, 2021 at 12:55 PM Invisible Man  
> wrote:
>
>> I've re-read the documentation for the wmr200 driver extension (
>> https://github.com/weewx/weewx-wmr200). I'm not sure my configuration is 
>> correct. I don't understand the doc very well .
>>
>> - Am I meant to have something in sensor_map, or is default correct?
>> - Am I meant to have mode set to something?
>> - Am I meant to uncomment driver = weewx.drivers.simulator ?
>>
>> This is what I have:
>>
>> [WMR200]
>> # This section is for the Oregon Scientific WMR200
>> 
>> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
>> model = WMR200
>> 
>> # The driver to use:
>> driver = user.wmr200
>> 
>> # default is 300 seconds
>> archive_interval = 600
>> 
>> 
>> 
>> ###
>> ###
>> 
>> #[Simulator]
>> # This section for the weewx weather station simulator
>> 
>> # The time (in seconds) between LOOP packets.
>> loop_interval = 2.5
>> erase_archive = False
>> sensor_status = True
>> archive_threshold = 1512000
>> archive_startup = 120
>> 

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Tom Keffer]

That's occurred to me, but it doesn't explain why nothing reports are not
running to completion.

On Fri, Jan 22, 2021 at 2:43 PM vince  wrote:

>
>
> On Friday, January 22, 2021 at 2:08:39 PM UTC-8 Tom Keffer wrote:
>
>> Rather strange. A few questions:
>>
>> 1. Your weewx.conf file is in /etc/weewx/weewx.conf, which is a location
>> usually associated with a Debian package installer, but the rest of weewx
>> is in /home/weewx, which is usually associated with a setup.py install. Is
>> that what you intended?
>>
>
> I'm wondering if there are two installed weewx setups.  One using setup.py
> (the logs mention /home/weewx) and one using dpkg (all the other mentions
> of /etc/weewx).   If there are two, it's possible the user is editing
> instance-A but actually running instance-B which uses a different
> weewx.conf ()
>
>
> --
> 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/11cc4bbc-0e52-4b09-8b91-19a59306da2bn%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/CAPq0zECHKz-G-w4HSOSOU6SzJQBhLsdfuZ5PgGyPrh8GtgpCZA%40mail.gmail.com.

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[vince]

On Friday, January 22, 2021 at 2:08:39 PM UTC-8 Tom Keffer wrote:

> Rather strange. A few questions:
>
> 1. Your weewx.conf file is in /etc/weewx/weewx.conf, which is a location 
> usually associated with a Debian package installer, but the rest of weewx 
> is in /home/weewx, which is usually associated with a setup.py install. Is 
> that what you intended?
>

I'm wondering if there are two installed weewx setups.  One using setup.py 
(the logs mention /home/weewx) and one using dpkg (all the other mentions 
of /etc/weewx).   If there are two, it's possible the user is editing 
instance-A but actually running instance-B which uses a different 
weewx.conf ()
 

-- 
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/11cc4bbc-0e52-4b09-8b91-19a59306da2bn%40googlegroups.com.

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Tom Keffer]

Rather strange. A few questions:

1. Your weewx.conf file is in /etc/weewx/weewx.conf, which is a location
usually associated with a Debian package installer, but the rest of weewx
is in /home/weewx, which is usually associated with a setup.py install. Is
that what you intended?

2. You have both FTP *and* rsync enabled. Is that what you intended?

However, I don't know why either of these would cause your reports not to
run to completion.

3. What happens if you try and use wee_reports? Does that work?

-tk


On Fri, Jan 22, 2021 at 12:55 PM Invisible Man 
wrote:

> I've re-read the documentation for the wmr200 driver extension (
> https://github.com/weewx/weewx-wmr200). I'm not sure my configuration is
> correct. I don't understand the doc very well .
>
> - Am I meant to have something in sensor_map, or is default correct?
> - Am I meant to have mode set to something?
> - Am I meant to uncomment driver = weewx.drivers.simulator ?
>
> This is what I have:
>
> [WMR200]
> # This section is for the Oregon Scientific WMR200
>
> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
> model = WMR200
>
> # The driver to use:
> driver = user.wmr200
>
> # default is 300 seconds
> archive_interval = 600
>
>
>
> ###
> ###
>
> #[Simulator]
> # This section for the weewx weather station simulator
>
> # The time (in seconds) between LOOP packets.
> loop_interval = 2.5
> erase_archive = False
> sensor_status = True
> archive_threshold = 1512000
> archive_startup = 120
> user_pc_time = True
> [[sensor_map]]
>
> # The simulator mode can be either 'simulator' or 'generator'.
> # Real-time simulator. Sleep between each LOOP packet.
> #mode = simulator
> # Generator.  Emit LOOP packets as fast as possible (useful for testing).
> #mode = generator
>
> # The start time. If not specified, the default is to use the present time.
> #start = 2011-01-01 00:00
>
> # The driver to use:
> #driver = weewx.drivers.simulator
>
>
>
> On Friday, January 22, 2021 at 3:55:54 PM UTC+1 Invisible Man wrote:
>
>> > Impossible to say without seeing a full log. Restart weewx, let it run
>> through the first reporting cycle, post the full log.
>>
>> Ok, I'm going to do that in a few secs.
>>
>> Meanwhile, posting the configuration.
>>
>> On Friday, January 22, 2021 at 3:49:30 PM UTC+1 tke...@gmail.com wrote:
>>
>>> Impossible to say without seeing a full log. Restart weewx, let it run
>>> through the first reporting cycle, post the full log.
>>>
>>> On Fri, Jan 22, 2021 at 6:42 AM Invisible Man 
>>> wrote:
>>>
 Up :)

 Please assist. It's really an issue, because my website does not get
 generated nor uploaded.
 *It thought it was a problem with the FTP upload report, but with
 investigation, I think it is general to all my reports.*

 This is what I know so far:

- My configuration has several reports
- Only the first one "StandardReport" shows some activity in the
logs (see thread above)
- The other reports never run at all,  though several are marked
enabled.
- *Even "StandardReport" does not work properly*, because given my
configuration, it should put things in /home/weewx/public_html

 WEEWX_ROOT = /home/weewx/
 SKIN_ROOT = skins
 HTML_ROOT = public_html

 And in that directory, I have nothing new since the evening I did my
 upgrade ! :( [notice the date, jan 20 - we are now jan 22).

 $ ls -lt | head
 total 700
 -rw-r--r-- 1 weewx axelle  7036 Jan 20 22:20 dayuv.png
 -rw-r--r-- 1 weewx axelle  4293 Jan 20 22:20 dayradiation.png
 -rw-r--r-- 1 weewx axelle 15639 Jan 20 22:20 daywindvec.png
 ...

 So, something prevents reports from running in my config.
 Again, it used to work in 4.2.0. The issue appeared at upgrade to
 4.3.0. As I installed the weewx_wmr200 extension, weewx.conf was modified.

 Those are the differences I have from my 4.2.0 config. I can't see any
 problem to be honest...

 $ diff weewx.conf weewx.conf.my.4.2.0
 35c35
 < location = "Le mas des crocodiles, Biot"
 ---
 > location = Le mas des crocodiles, Biot
 64a65,66
 >
 ##
 >
 72c74
 < driver = user.wmr200
 ---
 > driver = weewx.drivers.wmr200
 85,90d86
 < erase_archive = False
 < sensor_status = True
 < archive_threshold = 1512000
 < archive_startup = 120
 < user_pc_time = True
 < [[sensor_map]]
 119c115
 < post_interval = 3600
 ---
 > post_interval = 3600
 213d208
 < enable = True
 240d234
 < enable = True
 271d264
 < enable = True
 518,519c511,512
 < windchill = hardware

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

I've re-read the documentation for the wmr200 driver extension 
(https://github.com/weewx/weewx-wmr200). I'm not sure my configuration is 
correct. I don't understand the doc very well .

- Am I meant to have something in sensor_map, or is default correct?
- Am I meant to have mode set to something?
- Am I meant to uncomment driver = weewx.drivers.simulator ?

This is what I have:

[WMR200]
# This section is for the Oregon Scientific WMR200

# The station model, e.g., WMR200, WMR200A, Radio Shack W200
model = WMR200

# The driver to use:
driver = user.wmr200

# default is 300 seconds
archive_interval = 600



###
###

#[Simulator]
# This section for the weewx weather station simulator

# The time (in seconds) between LOOP packets.
loop_interval = 2.5
erase_archive = False
sensor_status = True
archive_threshold = 1512000
archive_startup = 120
user_pc_time = True
[[sensor_map]]

# The simulator mode can be either 'simulator' or 'generator'.
# Real-time simulator. Sleep between each LOOP packet.
#mode = simulator
# Generator.  Emit LOOP packets as fast as possible (useful for testing).
#mode = generator

# The start time. If not specified, the default is to use the present time.
#start = 2011-01-01 00:00

# The driver to use:
#driver = weewx.drivers.simulator



On Friday, January 22, 2021 at 3:55:54 PM UTC+1 Invisible Man wrote:

> > Impossible to say without seeing a full log. Restart weewx, let it run 
> through the first reporting cycle, post the full log.
>
> Ok, I'm going to do that in a few secs. 
>
> Meanwhile, posting the configuration.
>
> On Friday, January 22, 2021 at 3:49:30 PM UTC+1 tke...@gmail.com wrote:
>
>> Impossible to say without seeing a full log. Restart weewx, let it run 
>> through the first reporting cycle, post the full log.
>>
>> On Fri, Jan 22, 2021 at 6:42 AM Invisible Man  
>> wrote:
>>
>>> Up :)
>>>
>>> Please assist. It's really an issue, because my website does not get 
>>> generated nor uploaded.
>>> *It thought it was a problem with the FTP upload report, but with 
>>> investigation, I think it is general to all my reports.*
>>>
>>> This is what I know so far:
>>>
>>>- My configuration has several reports
>>>- Only the first one "StandardReport" shows some activity in the 
>>>logs (see thread above)
>>>- The other reports never run at all,  though several are marked 
>>>enabled.
>>>- *Even "StandardReport" does not work properly*, because given my 
>>>configuration, it should put things in /home/weewx/public_html
>>>
>>> WEEWX_ROOT = /home/weewx/
>>> SKIN_ROOT = skins
>>> HTML_ROOT = public_html
>>>
>>> And in that directory, I have nothing new since the evening I did my 
>>> upgrade ! :( [notice the date, jan 20 - we are now jan 22).
>>>
>>> $ ls -lt | head
>>> total 700
>>> -rw-r--r-- 1 weewx axelle  7036 Jan 20 22:20 dayuv.png
>>> -rw-r--r-- 1 weewx axelle  4293 Jan 20 22:20 dayradiation.png
>>> -rw-r--r-- 1 weewx axelle 15639 Jan 20 22:20 daywindvec.png
>>> ...
>>>
>>> So, something prevents reports from running in my config.
>>> Again, it used to work in 4.2.0. The issue appeared at upgrade to 4.3.0. 
>>> As I installed the weewx_wmr200 extension, weewx.conf was modified. 
>>>
>>> Those are the differences I have from my 4.2.0 config. I can't see any 
>>> problem to be honest...
>>>
>>> $ diff weewx.conf weewx.conf.my.4.2.0 
>>> 35c35
>>> < location = "Le mas des crocodiles, Biot"
>>> ---
>>> > location = Le mas des crocodiles, Biot
>>> 64a65,66
>>> > 
>>> ##
>>> > 
>>> 72c74
>>> < driver = user.wmr200
>>> ---
>>> > driver = weewx.drivers.wmr200
>>> 85,90d86
>>> < erase_archive = False
>>> < sensor_status = True
>>> < archive_threshold = 1512000
>>> < archive_startup = 120
>>> < user_pc_time = True
>>> < [[sensor_map]]
>>> 119c115
>>> < post_interval = 3600
>>> ---
>>> > post_interval = 3600
>>> 213d208
>>> < enable = True
>>> 240d234
>>> < enable = True
>>> 271d264
>>> < enable = True
>>> 518,519c511,512
>>> < windchill = hardware
>>> < heatindex = hardware
>>> ---
>>> > windchill = prefer_hardware
>>> > heatindex = prefer_hardware
>>> 522c515
>>> < rainRate = hardware
>>> ---
>>> > rainRate = prefer_hardware
>>>
>>>
>>> Thanks!
>>> On Thursday, January 21, 2021 at 10:09:28 PM UTC+1 Invisible Man wrote:
>>>

 Continuing. What bothers me is that in the StdReport section I have 
 several reports:

- StandardReport: we see logs for this one
- External: I have no logs for this one
- SeasonsReport: disabled
- SmartphoneReport: disabled
- MobileReport: disabled
- FTP: no logs for this one...
- RSYNC: enabled, 

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Tom Keffer]

On low-powered machines running complex reports, 20 seconds may not be long
enough. What comes afterwards?

On Fri, Jan 22, 2021 at 7:05 AM Invisible Man 
wrote:

> So, I stopped and restarted weewx, and I am posting below the logs from
> the restart to when it ran reports.
>
> You will probably notice these:
>
>  WARNING user.wmr200: Temp outdoor sensor fault
> WARNING user.wmr200: Clock time unsynchronized
> WARNING user.wmr200: Wind sensor: Battery low
> WARNING user.wmr200: UV sensor: Battery low
>
>
>-   the outdoor sensor is faulty, and I have replaced it by a DIY MQTT
>sensor, which is why I have a MQTT service in weewx :)
>-   Yes, I know Wind and UV sensor batteries are low :) I need to
>replace them soon.
>
> If you prefer an attached file, let me know.
>
> -- Axelle
>
> Jan 22 15:54:42 vegan python2[19925]: weewx[19925] DEBUG weewx.engine:
> Loading service weewx.engine.StdReport
> Jan 22 15:54:42 vegan python2[19925]: weewx[19925] DEBUG weewx.engine:
> Finished loading service weewx.engine.StdReport
> Jan 22 15:54:42 vegan python2[19925]: weewx[19925] INFO __main__: Starting
> up weewx version 4.3.0
> Jan 22 15:54:42 vegan python2[19925]: weewx[19925] DEBUG weewx.engine:
> Station does not support reading the time
> Jan 22 15:54:42 vegan python2[19925]: weewx[19925] INFO weewx.engine:
> Using binding 'wx_binding' to database 'weewx.sdb'
> Jan 22 15:54:42 vegan python2[19925]: weewx[19925] INFO weewx.manager:
> Starting backfill of daily summaries
> Jan 22 15:54:42 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> genStartup() phase getting archive packets since 2021-01-22 15:50:00 CET
> (1611327000)
> Jan 22 15:54:50 vegan python2[19925]: weewx[19925] INFO user.wmr200: Time
> drift between host and console in seconds:-5890
> Jan 22 15:54:50 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:1 live_queue_len:1
> Jan 22 15:54:51 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:2 live_queue_len:2
> Jan 22 15:55:00 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:3 live_queue_len:3
> Jan 22 15:55:05 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:4 live_queue_len:4
> Jan 22 15:55:08 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Initializing Rain.rain_total_last to 581.08
> Jan 22 15:55:08 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:5 live_queue_len:5
> Jan 22 15:55:10 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:6 live_queue_len:6
> Jan 22 15:55:16 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:7 live_queue_len:7
> Jan 22 15:55:19 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:8 live_queue_len:8
> Jan 22 15:55:19 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:9 live_queue_len:9
> Jan 22 15:55:20 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:10 live_queue_len:10
> Jan 22 15:55:30 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:11 live_queue_len:11
> Jan 22 15:55:33 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:12 live_queue_len:12
> Jan 22 15:55:40 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:13 live_queue_len:13
> Jan 22 15:55:41 vegan python2[19925]: weewx[19925] WARNING user.wmr200:
> Temp outdoor sensor fault
> Jan 22 15:55:41 vegan python2[19925]: weewx[19925] WARNING user.wmr200:
> Clock time unsynchronized
> Jan 22 15:55:41 vegan python2[19925]: weewx[19925] WARNING user.wmr200:
> Wind sensor: Battery low
> Jan 22 15:55:41 vegan python2[19925]: weewx[19925] WARNING user.wmr200: UV
> sensor: Battery low
> Jan 22 15:55:41 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:14 live_queue_len:14
> Jan 22 15:55:42 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Acknowledged control packet rx:1
> Jan 22 15:55:47 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:15 live_queue_len:15
> Jan 22 15:55:50 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:16 live_queue_len:16
> Jan 22 15:55:55 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> adjust_rain rain_total:581.08 Rain.rain_total_last:581.08 rain_interval:0.00
> Jan 22 15:55:55 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:17 live_queue_len:17
> Jan 22 15:56:00 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:18 live_queue_len:18
> Jan 22 15:56:01 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:19 live_queue_len:19
> Jan 22 15:56:10 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live packet rx:20 live_queue_len:20
> Jan 22 15:56:15 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:
> Queuing live 

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

So, I stopped and restarted weewx, and I am posting below the logs from the 
restart to when it ran reports.

You will probably notice these:

 WARNING user.wmr200: Temp outdoor sensor fault
WARNING user.wmr200: Clock time unsynchronized
WARNING user.wmr200: Wind sensor: Battery low
WARNING user.wmr200: UV sensor: Battery low


   -   the outdoor sensor is faulty, and I have replaced it by a DIY MQTT 
   sensor, which is why I have a MQTT service in weewx :)
   -   Yes, I know Wind and UV sensor batteries are low :) I need to 
   replace them soon.
   
If you prefer an attached file, let me know.

-- Axelle

Jan 22 15:54:42 vegan python2[19925]: weewx[19925] DEBUG weewx.engine: 
Loading service weewx.engine.StdReport
Jan 22 15:54:42 vegan python2[19925]: weewx[19925] DEBUG weewx.engine: 
Finished loading service weewx.engine.StdReport
Jan 22 15:54:42 vegan python2[19925]: weewx[19925] INFO __main__: Starting 
up weewx version 4.3.0
Jan 22 15:54:42 vegan python2[19925]: weewx[19925] DEBUG weewx.engine: 
Station does not support reading the time
Jan 22 15:54:42 vegan python2[19925]: weewx[19925] INFO weewx.engine: Using 
binding 'wx_binding' to database 'weewx.sdb'
Jan 22 15:54:42 vegan python2[19925]: weewx[19925] INFO weewx.manager: 
Starting backfill of daily summaries
Jan 22 15:54:42 vegan python2[19925]: weewx[19925] DEBUG user.wmr200: 
genStartup() phase getting archive packets since 2021-01-22 15:50:00 CET 
(1611327000)
Jan 22 15:54:50 vegan python2[19925]: weewx[19925] INFO user.wmr200: Time 
drift between host and console in seconds:-5890
Jan 22 15:54:50 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:1 live_queue_len:1
Jan 22 15:54:51 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:2 live_queue_len:2
Jan 22 15:55:00 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:3 live_queue_len:3
Jan 22 15:55:05 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:4 live_queue_len:4
Jan 22 15:55:08 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Initializing Rain.rain_total_last to 581.08
Jan 22 15:55:08 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:5 live_queue_len:5
Jan 22 15:55:10 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:6 live_queue_len:6
Jan 22 15:55:16 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:7 live_queue_len:7
Jan 22 15:55:19 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:8 live_queue_len:8
Jan 22 15:55:19 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:9 live_queue_len:9
Jan 22 15:55:20 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:10 live_queue_len:10
Jan 22 15:55:30 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:11 live_queue_len:11
Jan 22 15:55:33 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:12 live_queue_len:12
Jan 22 15:55:40 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:13 live_queue_len:13
Jan 22 15:55:41 vegan python2[19925]: weewx[19925] WARNING user.wmr200: 
Temp outdoor sensor fault
Jan 22 15:55:41 vegan python2[19925]: weewx[19925] WARNING user.wmr200: 
Clock time unsynchronized
Jan 22 15:55:41 vegan python2[19925]: weewx[19925] WARNING user.wmr200: 
Wind sensor: Battery low
Jan 22 15:55:41 vegan python2[19925]: weewx[19925] WARNING user.wmr200: UV 
sensor: Battery low
Jan 22 15:55:41 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:14 live_queue_len:14
Jan 22 15:55:42 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Acknowledged control packet rx:1
Jan 22 15:55:47 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:15 live_queue_len:15
Jan 22 15:55:50 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:16 live_queue_len:16
Jan 22 15:55:55 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
adjust_rain rain_total:581.08 Rain.rain_total_last:581.08 rain_interval:0.00
Jan 22 15:55:55 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:17 live_queue_len:17
Jan 22 15:56:00 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:18 live_queue_len:18
Jan 22 15:56:01 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:19 live_queue_len:19
Jan 22 15:56:10 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:20 live_queue_len:20
Jan 22 15:56:15 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:21 live_queue_len:21
Jan 22 15:56:19 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:22 live_queue_len:22
Jan 22 15:56:20 vegan python2[19925]: weewx[19925] DEBUG user.wmr200:   
Queuing live packet rx:23 

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

> Impossible to say without seeing a full log. Restart weewx, let it run 
through the first reporting cycle, post the full log.

Ok, I'm going to do that in a few secs. 

Meanwhile, posting the configuration.

On Friday, January 22, 2021 at 3:49:30 PM UTC+1 tke...@gmail.com wrote:

> Impossible to say without seeing a full log. Restart weewx, let it run 
> through the first reporting cycle, post the full log.
>
> On Fri, Jan 22, 2021 at 6:42 AM Invisible Man  
> wrote:
>
>> Up :)
>>
>> Please assist. It's really an issue, because my website does not get 
>> generated nor uploaded.
>> *It thought it was a problem with the FTP upload report, but with 
>> investigation, I think it is general to all my reports.*
>>
>> This is what I know so far:
>>
>>- My configuration has several reports
>>- Only the first one "StandardReport" shows some activity in the logs 
>>(see thread above)
>>- The other reports never run at all,  though several are marked 
>>enabled.
>>- *Even "StandardReport" does not work properly*, because given my 
>>configuration, it should put things in /home/weewx/public_html
>>
>> WEEWX_ROOT = /home/weewx/
>> SKIN_ROOT = skins
>> HTML_ROOT = public_html
>>
>> And in that directory, I have nothing new since the evening I did my 
>> upgrade ! :( [notice the date, jan 20 - we are now jan 22).
>>
>> $ ls -lt | head
>> total 700
>> -rw-r--r-- 1 weewx axelle  7036 Jan 20 22:20 dayuv.png
>> -rw-r--r-- 1 weewx axelle  4293 Jan 20 22:20 dayradiation.png
>> -rw-r--r-- 1 weewx axelle 15639 Jan 20 22:20 daywindvec.png
>> ...
>>
>> So, something prevents reports from running in my config.
>> Again, it used to work in 4.2.0. The issue appeared at upgrade to 4.3.0. 
>> As I installed the weewx_wmr200 extension, weewx.conf was modified. 
>>
>> Those are the differences I have from my 4.2.0 config. I can't see any 
>> problem to be honest...
>>
>> $ diff weewx.conf weewx.conf.my.4.2.0 
>> 35c35
>> < location = "Le mas des crocodiles, Biot"
>> ---
>> > location = Le mas des crocodiles, Biot
>> 64a65,66
>> > 
>> ##
>> > 
>> 72c74
>> < driver = user.wmr200
>> ---
>> > driver = weewx.drivers.wmr200
>> 85,90d86
>> < erase_archive = False
>> < sensor_status = True
>> < archive_threshold = 1512000
>> < archive_startup = 120
>> < user_pc_time = True
>> < [[sensor_map]]
>> 119c115
>> < post_interval = 3600
>> ---
>> > post_interval = 3600
>> 213d208
>> < enable = True
>> 240d234
>> < enable = True
>> 271d264
>> < enable = True
>> 518,519c511,512
>> < windchill = hardware
>> < heatindex = hardware
>> ---
>> > windchill = prefer_hardware
>> > heatindex = prefer_hardware
>> 522c515
>> < rainRate = hardware
>> ---
>> > rainRate = prefer_hardware
>>
>>
>> Thanks!
>> On Thursday, January 21, 2021 at 10:09:28 PM UTC+1 Invisible Man wrote:
>>
>>>
>>> Continuing. What bothers me is that in the StdReport section I have 
>>> several reports:
>>>
>>>- StandardReport: we see logs for this one
>>>- External: I have no logs for this one
>>>- SeasonsReport: disabled
>>>- SmartphoneReport: disabled
>>>- MobileReport: disabled
>>>- FTP: no logs for this one...
>>>- RSYNC: enabled, no logs...
>>>
>>> So, I have only have logs for the first one. That's strange isn't it? I 
>>> added explicit "enable = True" (or False) to each. It did not solve the 
>>> problem.
>>>
>>>
>>> [[StandardReport]]
>>> 
>>> # What skin this report should be based on:
>>> skin = Standard
>>> enable = True
>>> 
>>> [[External]]
>>> skin = External
>>> HTML_ROOT = external_html
>>> enable = True
>>> [[[ImageGenerator]]]
>>> image_width = 600
>>> image_height = 360
>>> 
>>> [[SeasonsReport]]
>>> # The SeasonsReport uses the 'Seasons' skin, which contains the
>>> # images, templates and plots for the report.
>>> skin = Seasons
>>> enable = false
>>>
>>> Strange... right?
>>>
>>> On Thursday, January 21, 2021 at 9:37:30 PM UTC+1 Invisible Man wrote:
>>>
 Posting it again here. This is /etc/weewx.conf:


 version = 4.3.0
 [Station]
   ...
   station_type = WMR200

 [WMR200]
 # This section is for the Oregon Scientific WMR200
 
 # The station model, e.g., WMR200, WMR200A, Radio Shack W200
 model = WMR200
 
 # The driver to use:
 driver = user.wmr200
 
 # default is 300 seconds
 archive_interval = 600
  
 #[Simulator]
 # This section for the weewx weather station simulator
 
 # The time (in seconds) between LOOP packets.
 loop_interval = 2.5
 erase_archive = False
 sensor_status = True
 archive_threshold = 1512000

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Tom Keffer]

Impossible to say without seeing a full log. Restart weewx, let it run
through the first reporting cycle, post the full log.

On Fri, Jan 22, 2021 at 6:42 AM Invisible Man 
wrote:

> Up :)
>
> Please assist. It's really an issue, because my website does not get
> generated nor uploaded.
> *It thought it was a problem with the FTP upload report, but with
> investigation, I think it is general to all my reports.*
>
> This is what I know so far:
>
>- My configuration has several reports
>- Only the first one "StandardReport" shows some activity in the logs
>(see thread above)
>- The other reports never run at all,  though several are marked
>enabled.
>- *Even "StandardReport" does not work properly*, because given my
>configuration, it should put things in /home/weewx/public_html
>
> WEEWX_ROOT = /home/weewx/
> SKIN_ROOT = skins
> HTML_ROOT = public_html
>
> And in that directory, I have nothing new since the evening I did my
> upgrade ! :( [notice the date, jan 20 - we are now jan 22).
>
> $ ls -lt | head
> total 700
> -rw-r--r-- 1 weewx axelle  7036 Jan 20 22:20 dayuv.png
> -rw-r--r-- 1 weewx axelle  4293 Jan 20 22:20 dayradiation.png
> -rw-r--r-- 1 weewx axelle 15639 Jan 20 22:20 daywindvec.png
> ...
>
> So, something prevents reports from running in my config.
> Again, it used to work in 4.2.0. The issue appeared at upgrade to 4.3.0.
> As I installed the weewx_wmr200 extension, weewx.conf was modified.
>
> Those are the differences I have from my 4.2.0 config. I can't see any
> problem to be honest...
>
> $ diff weewx.conf weewx.conf.my.4.2.0
> 35c35
> < location = "Le mas des crocodiles, Biot"
> ---
> > location = Le mas des crocodiles, Biot
> 64a65,66
> >
> ##
> >
> 72c74
> < driver = user.wmr200
> ---
> > driver = weewx.drivers.wmr200
> 85,90d86
> < erase_archive = False
> < sensor_status = True
> < archive_threshold = 1512000
> < archive_startup = 120
> < user_pc_time = True
> < [[sensor_map]]
> 119c115
> < post_interval = 3600
> ---
> > post_interval = 3600
> 213d208
> < enable = True
> 240d234
> < enable = True
> 271d264
> < enable = True
> 518,519c511,512
> < windchill = hardware
> < heatindex = hardware
> ---
> > windchill = prefer_hardware
> > heatindex = prefer_hardware
> 522c515
> < rainRate = hardware
> ---
> > rainRate = prefer_hardware
>
>
> Thanks!
> On Thursday, January 21, 2021 at 10:09:28 PM UTC+1 Invisible Man wrote:
>
>>
>> Continuing. What bothers me is that in the StdReport section I have
>> several reports:
>>
>>- StandardReport: we see logs for this one
>>- External: I have no logs for this one
>>- SeasonsReport: disabled
>>- SmartphoneReport: disabled
>>- MobileReport: disabled
>>- FTP: no logs for this one...
>>- RSYNC: enabled, no logs...
>>
>> So, I have only have logs for the first one. That's strange isn't it? I
>> added explicit "enable = True" (or False) to each. It did not solve the
>> problem.
>>
>>
>> [[StandardReport]]
>>
>> # What skin this report should be based on:
>> skin = Standard
>> enable = True
>>
>> [[External]]
>> skin = External
>> HTML_ROOT = external_html
>> enable = True
>> [[[ImageGenerator]]]
>> image_width = 600
>> image_height = 360
>>
>> [[SeasonsReport]]
>> # The SeasonsReport uses the 'Seasons' skin, which contains the
>> # images, templates and plots for the report.
>> skin = Seasons
>> enable = false
>>
>> Strange... right?
>>
>> On Thursday, January 21, 2021 at 9:37:30 PM UTC+1 Invisible Man wrote:
>>
>>> Posting it again here. This is /etc/weewx.conf:
>>>
>>>
>>> version = 4.3.0
>>> [Station]
>>>   ...
>>>   station_type = WMR200
>>>
>>> [WMR200]
>>> # This section is for the Oregon Scientific WMR200
>>>
>>> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
>>> model = WMR200
>>>
>>> # The driver to use:
>>> driver = user.wmr200
>>>
>>> # default is 300 seconds
>>> archive_interval = 600
>>>
>>> #[Simulator]
>>> # This section for the weewx weather station simulator
>>>
>>> # The time (in seconds) between LOOP packets.
>>> loop_interval = 2.5
>>> erase_archive = False
>>> sensor_status = True
>>> archive_threshold = 1512000
>>> archive_startup = 120
>>> user_pc_time = True
>>> [[sensor_map]]
>>>
>>> [StdReport]
>>> # This section specifies what reports, using which skins, to
>>> generate.
>>>
>>> # Where the skins reside, relative to WEEWX_ROOT:
>>> SKIN_ROOT = skins
>>>
>>> # Where the generated reports should go, relative to WEEWX_ROOT:
>>> HTML_ROOT = public_html
>>>
>>> # The database binding indicates which data should be used in reports
>>> data_binding = wx_binding
>>>
>>>

Re: [weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[John Kline]

I don’t know that it is your problem, but does your hardware provide windchill, 
heatindex and rainRate?  I would change those entries back to prefer_hardware 
in weewx.conf.

> On Jan 22, 2021, at 6:42 AM, Invisible Man  wrote:
> 
> 
> Up :)
> 
> Please assist. It's really an issue, because my website does not get 
> generated nor uploaded.
> It thought it was a problem with the FTP upload report, but with 
> investigation, I think it is general to all my reports.
> 
> This is what I know so far:
> My configuration has several reports
> Only the first one "StandardReport" shows some activity in the logs (see 
> thread above)
> The other reports never run at all,  though several are marked enabled.
> Even "StandardReport" does not work properly, because given my configuration, 
> it should put things in /home/weewx/public_html
> WEEWX_ROOT = /home/weewx/
> SKIN_ROOT = skins
> HTML_ROOT = public_html
> 
> And in that directory, I have nothing new since the evening I did my upgrade 
> ! :( [notice the date, jan 20 - we are now jan 22).
> 
> $ ls -lt | head
> total 700
> -rw-r--r-- 1 weewx axelle  7036 Jan 20 22:20 dayuv.png
> -rw-r--r-- 1 weewx axelle  4293 Jan 20 22:20 dayradiation.png
> -rw-r--r-- 1 weewx axelle 15639 Jan 20 22:20 daywindvec.png
> ...
> 
> So, something prevents reports from running in my config.
> Again, it used to work in 4.2.0. The issue appeared at upgrade to 4.3.0. As I 
> installed the weewx_wmr200 extension, weewx.conf was modified. 
> 
> Those are the differences I have from my 4.2.0 config. I can't see any 
> problem to be honest...
> 
> $ diff weewx.conf weewx.conf.my.4.2.0 
> 35c35
> < location = "Le mas des crocodiles, Biot"
> ---
> > location = Le mas des crocodiles, Biot
> 64a65,66
> > ##
> > 
> 72c74
> < driver = user.wmr200
> ---
> > driver = weewx.drivers.wmr200
> 85,90d86
> < erase_archive = False
> < sensor_status = True
> < archive_threshold = 1512000
> < archive_startup = 120
> < user_pc_time = True
> < [[sensor_map]]
> 119c115
> < post_interval = 3600
> ---
> > post_interval = 3600
> 213d208
> < enable = True
> 240d234
> < enable = True
> 271d264
> < enable = True
> 518,519c511,512
> < windchill = hardware
> < heatindex = hardware
> ---
> > windchill = prefer_hardware
> > heatindex = prefer_hardware
> 522c515
> < rainRate = hardware
> ---
> > rainRate = prefer_hardware
> 
> 
> Thanks!
>> On Thursday, January 21, 2021 at 10:09:28 PM UTC+1 Invisible Man wrote:
>> 
>> Continuing. What bothers me is that in the StdReport section I have several 
>> reports:
>> StandardReport: we see logs for this one
>> External: I have no logs for this one
>> SeasonsReport: disabled
>> SmartphoneReport: disabled
>> MobileReport: disabled
>> FTP: no logs for this one...
>> RSYNC: enabled, no logs...
>> So, I have only have logs for the first one. That's strange isn't it? I 
>> added explicit "enable = True" (or False) to each. It did not solve the 
>> problem.
>> 
>> 
>> [[StandardReport]]
>> 
>> # What skin this report should be based on:
>> skin = Standard
>> enable = True
>> 
>> [[External]]
>> skin = External
>> HTML_ROOT = external_html
>> enable = True
>> [[[ImageGenerator]]]
>> image_width = 600
>> image_height = 360
>> 
>> [[SeasonsReport]]
>> # The SeasonsReport uses the 'Seasons' skin, which contains the
>> # images, templates and plots for the report.
>> skin = Seasons
>> enable = false
>> 
>> Strange... right?
>> 
>>> On Thursday, January 21, 2021 at 9:37:30 PM UTC+1 Invisible Man wrote:
>>> Posting it again here. This is /etc/weewx.conf:
>>> 
>>> 
>>> version = 4.3.0
>>> [Station]
>>>   ...
>>>   station_type = WMR200
>>> 
>>> [WMR200]
>>> # This section is for the Oregon Scientific WMR200
>>> 
>>> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
>>> model = WMR200
>>> 
>>> # The driver to use:
>>> driver = user.wmr200
>>> 
>>> # default is 300 seconds
>>> archive_interval = 600
>>>  
>>> #[Simulator]
>>> # This section for the weewx weather station simulator
>>> 
>>> # The time (in seconds) between LOOP packets.
>>> loop_interval = 2.5
>>> erase_archive = False
>>> sensor_status = True
>>> archive_threshold = 1512000
>>> archive_startup = 120
>>> user_pc_time = True
>>> [[sensor_map]]
>>> 
>>> [StdReport]
>>> # This section specifies what reports, using which skins, to generate.
>>> 
>>> # Where the skins reside, relative to WEEWX_ROOT:
>>> SKIN_ROOT = skins
>>> 
>>> # Where the generated reports should go, relative to WEEWX_ROOT:
>>> HTML_ROOT = public_html
>>> 
>>> # The database binding indicates which data should be used 

[weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

Up :)

Please assist. It's really an issue, because my website does not get 
generated nor uploaded.
*It thought it was a problem with the FTP upload report, but with 
investigation, I think it is general to all my reports.*

This is what I know so far:

   - My configuration has several reports
   - Only the first one "StandardReport" shows some activity in the logs 
   (see thread above)
   - The other reports never run at all,  though several are marked enabled.
   - *Even "StandardReport" does not work properly*, because given my 
   configuration, it should put things in /home/weewx/public_html
   
WEEWX_ROOT = /home/weewx/
SKIN_ROOT = skins
HTML_ROOT = public_html

And in that directory, I have nothing new since the evening I did my 
upgrade ! :( [notice the date, jan 20 - we are now jan 22).

$ ls -lt | head
total 700
-rw-r--r-- 1 weewx axelle  7036 Jan 20 22:20 dayuv.png
-rw-r--r-- 1 weewx axelle  4293 Jan 20 22:20 dayradiation.png
-rw-r--r-- 1 weewx axelle 15639 Jan 20 22:20 daywindvec.png
...

So, something prevents reports from running in my config.
Again, it used to work in 4.2.0. The issue appeared at upgrade to 4.3.0. As 
I installed the weewx_wmr200 extension, weewx.conf was modified. 

Those are the differences I have from my 4.2.0 config. I can't see any 
problem to be honest...

$ diff weewx.conf weewx.conf.my.4.2.0 
35c35
< location = "Le mas des crocodiles, Biot"
---
> location = Le mas des crocodiles, Biot
64a65,66
> 
##
> 
72c74
< driver = user.wmr200
---
> driver = weewx.drivers.wmr200
85,90d86
< erase_archive = False
< sensor_status = True
< archive_threshold = 1512000
< archive_startup = 120
< user_pc_time = True
< [[sensor_map]]
119c115
< post_interval = 3600
---
> post_interval = 3600
213d208
< enable = True
240d234
< enable = True
271d264
< enable = True
518,519c511,512
< windchill = hardware
< heatindex = hardware
---
> windchill = prefer_hardware
> heatindex = prefer_hardware
522c515
< rainRate = hardware
---
> rainRate = prefer_hardware


Thanks!
On Thursday, January 21, 2021 at 10:09:28 PM UTC+1 Invisible Man wrote:

>
> Continuing. What bothers me is that in the StdReport section I have 
> several reports:
>
>- StandardReport: we see logs for this one
>- External: I have no logs for this one
>- SeasonsReport: disabled
>- SmartphoneReport: disabled
>- MobileReport: disabled
>- FTP: no logs for this one...
>- RSYNC: enabled, no logs...
>
> So, I have only have logs for the first one. That's strange isn't it? I 
> added explicit "enable = True" (or False) to each. It did not solve the 
> problem.
>
>
> [[StandardReport]]
> 
> # What skin this report should be based on:
> skin = Standard
> enable = True
> 
> [[External]]
> skin = External
> HTML_ROOT = external_html
> enable = True
> [[[ImageGenerator]]]
> image_width = 600
> image_height = 360
> 
> [[SeasonsReport]]
> # The SeasonsReport uses the 'Seasons' skin, which contains the
> # images, templates and plots for the report.
> skin = Seasons
> enable = false
>
> Strange... right?
>
> On Thursday, January 21, 2021 at 9:37:30 PM UTC+1 Invisible Man wrote:
>
>> Posting it again here. This is /etc/weewx.conf:
>>
>>
>> version = 4.3.0
>> [Station]
>>   ...
>>   station_type = WMR200
>>
>> [WMR200]
>> # This section is for the Oregon Scientific WMR200
>> 
>> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
>> model = WMR200
>> 
>> # The driver to use:
>> driver = user.wmr200
>> 
>> # default is 300 seconds
>> archive_interval = 600
>>  
>> #[Simulator]
>> # This section for the weewx weather station simulator
>> 
>> # The time (in seconds) between LOOP packets.
>> loop_interval = 2.5
>> erase_archive = False
>> sensor_status = True
>> archive_threshold = 1512000
>> archive_startup = 120
>> user_pc_time = True
>> [[sensor_map]]
>>
>> [StdReport]
>> # This section specifies what reports, using which skins, to generate.
>> 
>> # Where the skins reside, relative to WEEWX_ROOT:
>> SKIN_ROOT = skins
>> 
>> # Where the generated reports should go, relative to WEEWX_ROOT:
>> HTML_ROOT = public_html
>> 
>> # The database binding indicates which data should be used in reports
>> data_binding = wx_binding
>>
>>[[StandardReport]]
>> # What skin this report should be based on:
>> skin = Standard
>> enable = True
>>...
>>[[FTP]]
>> skin = Ftp
>> 
>> # FTP'ing the results to a webserver is treated as just another 
>> report,
>> # albeit one with an unusual report generator!
>> #
>> 

[weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

Continuing. What bothers me is that in the StdReport section I have several 
reports:

   - StandardReport: we see logs for this one
   - External: I have no logs for this one
   - SeasonsReport: disabled
   - SmartphoneReport: disabled
   - MobileReport: disabled
   - FTP: no logs for this one...
   - RSYNC: enabled, no logs...

So, I have only have logs for the first one. That's strange isn't it? I 
added explicit "enable = True" (or False) to each. It did not solve the 
problem.

[[StandardReport]]

# What skin this report should be based on:
skin = Standard
enable = True

[[External]]
skin = External
HTML_ROOT = external_html
enable = True
[[[ImageGenerator]]]
image_width = 600
image_height = 360

[[SeasonsReport]]
# The SeasonsReport uses the 'Seasons' skin, which contains the
# images, templates and plots for the report.
skin = Seasons
enable = false

Strange... right?

On Thursday, January 21, 2021 at 9:37:30 PM UTC+1 Invisible Man wrote:

> Posting it again here. This is /etc/weewx.conf:
>
>
> version = 4.3.0
> [Station]
>   ...
>   station_type = WMR200
>
> [WMR200]
> # This section is for the Oregon Scientific WMR200
> 
> # The station model, e.g., WMR200, WMR200A, Radio Shack W200
> model = WMR200
> 
> # The driver to use:
> driver = user.wmr200
> 
> # default is 300 seconds
> archive_interval = 600
>  
> #[Simulator]
> # This section for the weewx weather station simulator
> 
> # The time (in seconds) between LOOP packets.
> loop_interval = 2.5
> erase_archive = False
> sensor_status = True
> archive_threshold = 1512000
> archive_startup = 120
> user_pc_time = True
> [[sensor_map]]
>
> [StdReport]
> # This section specifies what reports, using which skins, to generate.
> 
> # Where the skins reside, relative to WEEWX_ROOT:
> SKIN_ROOT = skins
> 
> # Where the generated reports should go, relative to WEEWX_ROOT:
> HTML_ROOT = public_html
> 
> # The database binding indicates which data should be used in reports
> data_binding = wx_binding
>
>[[StandardReport]]
> # What skin this report should be based on:
> skin = Standard
> enable = True
>...
>[[FTP]]
> skin = Ftp
> 
> # FTP'ing the results to a webserver is treated as just another 
> report,
> # albeit one with an unusual report generator!
> #
> # If you wish to use FTP, uncomment and fill out the next four 
> lines:
> user = CENSORED
> password = CENSORED
> server = CENSORED
> path = CENSORED
> 
> # If you wish to upload files from something other than what 
> HTML_ROOT
> # is set to above, then reset it here:
> HTML_ROOT = external_html
> 
> # Most FTP servers use port 21, but if yours is different, you can
> # change it here
> port = 21
> 
> # Set to 1 to use passive mode, zero for active mode:
> passive = 1
> 
> # How many times to try to transfer a file before giving up:
> max_tries = 5
>
> ...
> [Engine]
> # The following section specifies which services should be run and in 
> what order.
> [[Services]]
> prep_services = weewx.engine.StdTimeSynch,
> data_services = user.MQTTSubscribe.MQTTSubscribeService,
> process_services = weewx.engine.StdConvert, 
> weewx.engine.StdCalibrate, weewx.engine.StdQC, weewx.wxservices.StdWXCa
> lculate
> xtype_services = weewx.wxxtypes.StdWXXTypes, 
> weewx.wxxtypes.StdPressureCooker, weewx.wxxtypes.StdRainRater, weewx.w
> xxtypes.StdDelta
> archive_services = weewx.engine.StdArchive,
> restful_services = weewx.restx.StdStationRegistry, 
> user.twitter.Twitter
> report_services = weewx.engine.StdPrint, weewx.engine.StdReport
>
> ...
> ---
> This is a few logs for the service
>
> Jan 21 21:35:10 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
> Queuing live packet rx:1399 live_queue_len:1
> Jan 21 21:35:11 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
> genLoop() Yielding live queued packet id:1507
> Jan 21 21:35:11 vegan python2[29779]: weewx[29779] DEBUG 
> user.MQTTSubscribe: (Service) data-> final packet is 2021-01-21 21:35:11 
> CET (1611261311): dateTime: 1611261311, inHeatindex: None, inHumidity: 46, 
> inTemp: 20.8, usUnits: 16
> Jan 21 21:35:18 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
> adjust_rain rain_total:579.07 Rain.rain_total_last:579.07 rain_interval:0.00
> Jan 21 21:35:18 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
> Queuing live packet rx:1400 live_queue_len:1
> Jan 21 21:35:19 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
> genLoop() Yielding live queued packet 

[weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

Posting it again here. This is /etc/weewx.conf:


version = 4.3.0
[Station]
  ...
  station_type = WMR200

[WMR200]
# This section is for the Oregon Scientific WMR200

# The station model, e.g., WMR200, WMR200A, Radio Shack W200
model = WMR200

# The driver to use:
driver = user.wmr200

# default is 300 seconds
archive_interval = 600
 
#[Simulator]
# This section for the weewx weather station simulator

# The time (in seconds) between LOOP packets.
loop_interval = 2.5
erase_archive = False
sensor_status = True
archive_threshold = 1512000
archive_startup = 120
user_pc_time = True
[[sensor_map]]

[StdReport]
# This section specifies what reports, using which skins, to generate.

# Where the skins reside, relative to WEEWX_ROOT:
SKIN_ROOT = skins

# Where the generated reports should go, relative to WEEWX_ROOT:
HTML_ROOT = public_html

# The database binding indicates which data should be used in reports
data_binding = wx_binding

   [[StandardReport]]
# What skin this report should be based on:
skin = Standard
enable = True
   ...
   [[FTP]]
skin = Ftp

# FTP'ing the results to a webserver is treated as just another 
report,
# albeit one with an unusual report generator!
#
# If you wish to use FTP, uncomment and fill out the next four 
lines:
user = CENSORED
password = CENSORED
server = CENSORED
path = CENSORED

# If you wish to upload files from something other than what 
HTML_ROOT
# is set to above, then reset it here:
HTML_ROOT = external_html

# Most FTP servers use port 21, but if yours is different, you can
# change it here
port = 21

# Set to 1 to use passive mode, zero for active mode:
passive = 1

# How many times to try to transfer a file before giving up:
max_tries = 5

...
[Engine]
# The following section specifies which services should be run and in 
what order.
[[Services]]
prep_services = weewx.engine.StdTimeSynch,
data_services = user.MQTTSubscribe.MQTTSubscribeService,
process_services = weewx.engine.StdConvert, 
weewx.engine.StdCalibrate, weewx.engine.StdQC, weewx.wxservices.StdWXCa
lculate
xtype_services = weewx.wxxtypes.StdWXXTypes, 
weewx.wxxtypes.StdPressureCooker, weewx.wxxtypes.StdRainRater, weewx.w
xxtypes.StdDelta
archive_services = weewx.engine.StdArchive,
restful_services = weewx.restx.StdStationRegistry, 
user.twitter.Twitter
report_services = weewx.engine.StdPrint, weewx.engine.StdReport

...
---
This is a few logs for the service

Jan 21 21:35:10 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
Queuing live packet rx:1399 live_queue_len:1
Jan 21 21:35:11 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
genLoop() Yielding live queued packet id:1507
Jan 21 21:35:11 vegan python2[29779]: weewx[29779] DEBUG 
user.MQTTSubscribe: (Service) data-> final packet is 2021-01-21 21:35:11 
CET (1611261311): dateTime: 1611261311, inHeatindex: None, inHumidity: 46, 
inTemp: 20.8, usUnits: 16
Jan 21 21:35:18 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
adjust_rain rain_total:579.07 Rain.rain_total_last:579.07 rain_interval:0.00
Jan 21 21:35:18 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
Queuing live packet rx:1400 live_queue_len:1
Jan 21 21:35:19 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
genLoop() Yielding live queued packet id:1508
Jan 21 21:35:19 vegan python2[29779]: weewx[29779] DEBUG 
user.MQTTSubscribe: (Service) data-> final packet is 2021-01-21 21:35:19 
CET (1611261319): dateTime: 1611261319, hourRain: 0.0, rain: 0.0, rain24: 
1.4732, rainRate: 0.0, rainTotal: 579.0692, usUnits: 16
Jan 21 21:35:20 vegan python2[29779]: weewx[29779] DEBUG user.wmr200:   
Queuing live packet rx:1401 live_queue_len:1
Jan 21 21:35:21 vegan python2[29779]: weewx[29779] DEBUG user.wmr200: 
genLoop() Yielding live queued packet id:1509
Jan 21 21:35:21 vegan python2[29779]: weewx[29779] DEBUG 
user.MQTTSubscribe: (Service) data-> final packet is 2021-01-21 21:35:21 
CET (1611261321): dateTime: 1611261321, inHeatindex: None, inHumidity: 46, 
inTemp: 20.8, usUnits: 16

--
If I grep on "report": sudo journalctl -u weewx | grep -i report
we see that things are happening for StandardReport.

Jan 21 21:10:21 vegan python2[29779]: weewx[29779] DEBUG 
weewx.reportengine: Running report 'StandardReport'
Jan 21 21:10:21 vegan python2[29779]: weewx[29779] DEBUG 
weewx.reportengine: Found configuration file 
/home/weewx/skins/Standard/skin.conf for report 'StandardReport'
Jan 21 21:20:21 vegan python2[29779]: weewx[29779] DEBUG 
weewx.reportengine: Running reports for latest time in the database.
Jan 21 21:20:21 vegan 

[weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[Invisible Man]

@vince : the info is already posted in the thread "No module named wmr200 
(Weewx 4.3.0)"

On Thursday, January 21, 2021 at 9:27:56 PM UTC+1 vince wrote:

> Normal "how to report a problem" answer follows
>
> Nobody can help you without seeing what you have in your weewx.conf 
> (obfuscate the username+password please) and some logfile entries after you 
> set debug=1 in weewx.conf
>
> On Thursday, January 21, 2021 at 12:20:33 PM UTC-8 axelle@gmail.com 
> wrote:
>
>>
>> Hi,
>>
>> I have upgraded Weewx 4.2.0 to 4.3.0, and had to install WMR200 extension 
>> during that process.
>> My weather station is configured to upload its web pages to a FTP server.
>> This used to work fine.
>> However, since the upgrade, it hasn't uploaded anything (no attempt in 
>> the logs) now for over an hour.
>> This is really abnormal. Is there something in the fact that I'm using 
>> now an extension or upgraded that could cause this?
>>
>> I have no error log. But I never get the usual FTP upload logs that I 
>> used to have every 10 minutes. Just like it was disabled.
>>
>> I posted a few logs in the thread "No module named wmr200 (Weewx 
>> 4.3.0)". I am posting here in a separate topic as it seems it is a 
>> different issue (?).
>>
>> 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/184e83ae-dd13-409e-9c45-3fba8710b19fn%40googlegroups.com.

[weewx-user] Re: Weewx StdReport FTP is not uploading... ?

[vince]

Normal "how to report a problem" answer follows

Nobody can help you without seeing what you have in your weewx.conf 
(obfuscate the username+password please) and some logfile entries after you 
set debug=1 in weewx.conf

On Thursday, January 21, 2021 at 12:20:33 PM UTC-8 axelle@gmail.com 
wrote:

>
> Hi,
>
> I have upgraded Weewx 4.2.0 to 4.3.0, and had to install WMR200 extension 
> during that process.
> My weather station is configured to upload its web pages to a FTP server.
> This used to work fine.
> However, since the upgrade, it hasn't uploaded anything (no attempt in the 
> logs) now for over an hour.
> This is really abnormal. Is there something in the fact that I'm using now 
> an extension or upgraded that could cause this?
>
> I have no error log. But I never get the usual FTP upload logs that I used 
> to have every 10 minutes. Just like it was disabled.
>
> I posted a few logs in the thread "No module named wmr200 (Weewx 4.3.0)". 
> I am posting here in a separate topic as it seems it is a different issue 
> (?).
>
> 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/1aa4a61f-3234-4779-b2a5-4c9d8da8fe17n%40googlegroups.com.