Re: [weewx-user] Problems with weewx on MacOS

[seano...@gmail.com]

ns.html. Nothing is displayed. The GET 
>>>> request to  /api/v2/stations/?limit=2000 is also returning a 502. So, like 
>>>> you said, seems like a server issue…
>>>> rich
>>>>
>>>> On Sunday, 21 May 2023 at 16:22:54 UTC-4 Tom Keffer wrote:
>>>>
>>>>> Oops. Missed that! Thanks, Rich.
>>>>>
>>>>> Not sure why the registry would return that error. Try debug=2 in 
>>>>> weewx.conf, restart weewxd, let it run for a reporting cycle of two, then 
>>>>> post the log. Option debug=2 will log the full URL used for the GET to 
>>>>> the 
>>>>> registry. 
>>>>>
>>>>>
>>>>>
>>>>> On Sun, May 21, 2023 at 12:53 PM bell...@gmail.com  
>>>>> wrote:
>>>>>
>>>>>> Tom, 
>>>>>> I think the 502 is from station registry. Nothing is displaying on 
>>>>>> the map and GET stations is returning a 502
>>>>>> rich 
>>>>>>
>>>>>> On Sunday, 21 May 2023 at 11:59:08 UTC-4 Tom Keffer wrote:
>>>>>>
>>>>>>> I don't know anything about the windguru uploader. You can try 
>>>>>>> asking the author.
>>>>>>>
>>>>>>> I will say that "Bad Gateway" usually means a problem with a load 
>>>>>>> balancing server, or something like that. It could be a problem on the 
>>>>>>> windguru end.
>>>>>>>
>>>>>>> There's also a pending "pull request 
>>>>>>> <https://github.com/claudobahn/weewx-windguru/pull/4>" that updates 
>>>>>>> how authentication is done. Perhaps that's the problem? Don't know. You 
>>>>>>> can 
>>>>>>> give it a try.
>>>>>>>
>>>>>>> -tk
>>>>>>>
>>>>>>> On Sun, May 21, 2023 at 8:47 AM seano...@gmail.com <
>>>>>>> seano...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Thank you for the replies and suggestions. The logging is now 
>>>>>>>> working to /var/log/weewx.log
>>>>>>>>
>>>>>>>> When I run weewx directly I can see the sensor data coming in. It 
>>>>>>>> seems like it's just the final step when it uploads the data to 
>>>>>>>> windguru 
>>>>>>>> that it is failing. I have confirmed that the station details are 
>>>>>>>> correct. 
>>>>>>>> When I ping windguru.cz, there is a reply. Any ideas?
>>>>>>>>
>>>>>>>> 2023-05-21 19:35:41  weewx[3859] DEBUG weewx.reportengine: Report 
>>>>>>>> 'RSYNC' not enabled. Skipping.
>>>>>>>> 2023-05-21 19:35:44  weewx[3859] DEBUG weewx.restx: WindGuru: 
>>>>>>>> Failed upload attempt 2: Server response: b'ERROR (no data)'
>>>>>>>> 2023-05-21 19:35:45  weewx[3859] DEBUG weewx.restx: 
>>>>>>>> StationRegistry: Failed upload attempt 2: HTTP Error 502: Bad Gateway
>>>>>>>> 2023-05-21 19:35:50  weewx[3859] DEBUG weewx.restx: WindGuru: 
>>>>>>>> Failed upload attempt 3: Server response: b'ERROR (no data)'
>>>>>>>> 2023-05-21 19:35:50  weewx[3859] ERROR weewx.restx: WindGuru: 
>>>>>>>> Failed to publish record 2023-05-21 19:35:00 +04 (1684683300): Failed 
>>>>>>>> upload after 3 tries
>>>>>>>> 2023-05-21 19:35:51  weewx[3859] DEBUG weewx.restx: 
>>>>>>>> StationRegistry: Failed upload attempt 3: HTTP Error 502: Bad Gateway
>>>>>>>> 2023-05-21 19:35:51  weewx[3859] ERROR weewx.restx: 
>>>>>>>> StationRegistry: Failed to publish record 2023-05-21 19:35:00 +04 
>>>>>>>> (1684683300): Failed upload after 3 tries
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sunday, May 21, 2023 at 3:43:15 PM UTC+4 Tom Keffer wrote:
>>>>>>>>
>>>>>>>>> I have never been able to get system logging from Python to work 
>>>>>>>>> on the Mac. I'm sure it can be done --- I just don't know how. If you 
>>>>>>>>> Google around, apparently others have stru

Re: [weewx-user] Problems with weewx on MacOS

[seano...@gmail.com]

Thanks for the feedback. So is it something I am doing wrong, or can fix on 
my end? What action should I take?

Important to note that through my fiddling over the last few days, the 
station did report for about 20 min yesterday and then about 3 hours on 
19th May.

The location of the station is off grid and only powers on with generators 
from 12pm every day. Later today I will try debug=2 in weewx.conf and 
report back.

Thanks
On Monday, May 22, 2023 at 3:28:01 AM UTC+4 Tom Keffer wrote:

> Right you are. 
>
> Fixed.
>
> On Sun, May 21, 2023 at 2:40 PM bell...@gmail.com  
> wrote:
>
>> Sorry, I was in a hurry and wasn’t clear. I think StationRegistry and 
>> WindGuru are both failing.
>> Re: StationRegistry
>> Go to http://weewx.com/stations.html. Nothing is displayed. The GET 
>> request to  /api/v2/stations/?limit=2000 is also returning a 502. So, like 
>> you said, seems like a server issue…
>> rich
>>
>> On Sunday, 21 May 2023 at 16:22:54 UTC-4 Tom Keffer wrote:
>>
>>> Oops. Missed that! Thanks, Rich.
>>>
>>> Not sure why the registry would return that error. Try debug=2 in 
>>> weewx.conf, restart weewxd, let it run for a reporting cycle of two, then 
>>> post the log. Option debug=2 will log the full URL used for the GET to the 
>>> registry. 
>>>
>>>
>>>
>>> On Sun, May 21, 2023 at 12:53 PM bell...@gmail.com  
>>> wrote:
>>>
>>>> Tom, 
>>>> I think the 502 is from station registry. Nothing is displaying on the 
>>>> map and GET stations is returning a 502
>>>> rich 
>>>>
>>>> On Sunday, 21 May 2023 at 11:59:08 UTC-4 Tom Keffer wrote:
>>>>
>>>>> I don't know anything about the windguru uploader. You can try asking 
>>>>> the author.
>>>>>
>>>>> I will say that "Bad Gateway" usually means a problem with a load 
>>>>> balancing server, or something like that. It could be a problem on the 
>>>>> windguru end.
>>>>>
>>>>> There's also a pending "pull request 
>>>>> <https://github.com/claudobahn/weewx-windguru/pull/4>" that updates 
>>>>> how authentication is done. Perhaps that's the problem? Don't know. You 
>>>>> can 
>>>>> give it a try.
>>>>>
>>>>> -tk
>>>>>
>>>>> On Sun, May 21, 2023 at 8:47 AM seano...@gmail.com  
>>>>> wrote:
>>>>>
>>>>>> Thank you for the replies and suggestions. The logging is now working 
>>>>>> to /var/log/weewx.log
>>>>>>
>>>>>> When I run weewx directly I can see the sensor data coming in. It 
>>>>>> seems like it's just the final step when it uploads the data to windguru 
>>>>>> that it is failing. I have confirmed that the station details are 
>>>>>> correct. 
>>>>>> When I ping windguru.cz, there is a reply. Any ideas?
>>>>>>
>>>>>> 2023-05-21 19:35:41  weewx[3859] DEBUG weewx.reportengine: Report 
>>>>>> 'RSYNC' not enabled. Skipping.
>>>>>> 2023-05-21 19:35:44  weewx[3859] DEBUG weewx.restx: WindGuru: Failed 
>>>>>> upload attempt 2: Server response: b'ERROR (no data)'
>>>>>> 2023-05-21 19:35:45  weewx[3859] DEBUG weewx.restx: StationRegistry: 
>>>>>> Failed upload attempt 2: HTTP Error 502: Bad Gateway
>>>>>> 2023-05-21 19:35:50  weewx[3859] DEBUG weewx.restx: WindGuru: Failed 
>>>>>> upload attempt 3: Server response: b'ERROR (no data)'
>>>>>> 2023-05-21 19:35:50  weewx[3859] ERROR weewx.restx: WindGuru: Failed 
>>>>>> to publish record 2023-05-21 19:35:00 +04 (1684683300): Failed upload 
>>>>>> after 
>>>>>> 3 tries
>>>>>> 2023-05-21 19:35:51  weewx[3859] DEBUG weewx.restx: StationRegistry: 
>>>>>> Failed upload attempt 3: HTTP Error 502: Bad Gateway
>>>>>> 2023-05-21 19:35:51  weewx[3859] ERROR weewx.restx: StationRegistry: 
>>>>>> Failed to publish record 2023-05-21 19:35:00 +04 (1684683300): Failed 
>>>>>> upload after 3 tries
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sunday, May 21, 2023 at 3:43:15 PM UTC+4 Tom Keffer wrote:
>>>>>>
>>>>>>> I have never been able to get system logging from Python to work on 
>>>>>>>

Re: [weewx-user] Problems with weewx on MacOS

[seano...@gmail.com]

Thanks Tom for all your help with this. Really appreciate it.

I will look into this further and also try and ask the author.

On Sunday, May 21, 2023 at 7:59:08 PM UTC+4 Tom Keffer wrote:

> I don't know anything about the windguru uploader. You can try asking the 
> author.
>
> I will say that "Bad Gateway" usually means a problem with a load 
> balancing server, or something like that. It could be a problem on the 
> windguru end.
>
> There's also a pending "pull request 
> <https://github.com/claudobahn/weewx-windguru/pull/4>" that updates how 
> authentication is done. Perhaps that's the problem? Don't know. You can 
> give it a try.
>
> -tk
>
> On Sun, May 21, 2023 at 8:47 AM seano...@gmail.com  
> wrote:
>
>> Thank you for the replies and suggestions. The logging is now working to 
>> /var/log/weewx.log
>>
>> When I run weewx directly I can see the sensor data coming in. It seems 
>> like it's just the final step when it uploads the data to windguru that it 
>> is failing. I have confirmed that the station details are correct. When I 
>> ping windguru.cz, there is a reply. Any ideas?
>>
>> 2023-05-21 19:35:41  weewx[3859] DEBUG weewx.reportengine: Report 'RSYNC' 
>> not enabled. Skipping.
>> 2023-05-21 19:35:44  weewx[3859] DEBUG weewx.restx: WindGuru: Failed 
>> upload attempt 2: Server response: b'ERROR (no data)'
>> 2023-05-21 19:35:45  weewx[3859] DEBUG weewx.restx: StationRegistry: 
>> Failed upload attempt 2: HTTP Error 502: Bad Gateway
>> 2023-05-21 19:35:50  weewx[3859] DEBUG weewx.restx: WindGuru: Failed 
>> upload attempt 3: Server response: b'ERROR (no data)'
>> 2023-05-21 19:35:50  weewx[3859] ERROR weewx.restx: WindGuru: Failed to 
>> publish record 2023-05-21 19:35:00 +04 (1684683300): Failed upload after 3 
>> tries
>> 2023-05-21 19:35:51  weewx[3859] DEBUG weewx.restx: StationRegistry: 
>> Failed upload attempt 3: HTTP Error 502: Bad Gateway
>> 2023-05-21 19:35:51  weewx[3859] ERROR weewx.restx: StationRegistry: 
>> Failed to publish record 2023-05-21 19:35:00 +04 (1684683300): Failed 
>> upload after 3 tries
>>
>>
>>
>> On Sunday, May 21, 2023 at 3:43:15 PM UTC+4 Tom Keffer wrote:
>>
>>> I have never been able to get system logging from Python to work on the 
>>> Mac. I'm sure it can be done --- I just don't know how. If you Google 
>>> around, apparently others have struggled to get it to work as well.
>>>
>>> Instead, I just log to a rotating file. See the section *Logging to 
>>> rotating files 
>>> <https://github.com/weewx/weewx/wiki/WeeWX-v4-and-logging#logging-to-rotating-files>*
>>>  in 
>>> the Wiki. The example logs to /var/log/weewx.log, which will require 
>>> root privileges. Another option is to log to 
>>> /Users/Shared/weewx/weewx.log, or some other place where you don't need 
>>> those privileges.
>>>
>>>
>>>
>>> On Sun, May 21, 2023 at 2:47 AM Graham Eddy  wrote:
>>>
>>>> tom did not say that 4.10.2 removed [Logging], he did ask you to remove 
>>>> that section temporarily, to get it to use default, in case your own 
>>>> content of that section was wrong. tom said that you were using a specific 
>>>> item (i think it was ‘rotate’) that was removed in 4.10.2 and thus causing 
>>>> your runtime error
>>>>
>>>> i think in macOS the default behaviour is to log under 
>>>> /var/log/system.log
>>>>
>>>> once the default configuration is working, no doubt you will add some 
>>>> entries to [Logging] to use a file of your choice, such as 
>>>> /var/log/weewx.log
>>>> *⊣GE⊢*
>>>>
>>>> On 21 May 2023, at 7:33 pm, seano...@gmail.com  
>>>> wrote:
>>>>
>>>> However, I am still having some problem and I'm struggling to identify 
>>>> exactly what because I'm not sure how to check the logs on MacOS. I'm 
>>>> sorry 
>>>> for the noob question, but can someone please guide me on where weewx is 
>>>> logging to? I can confirm that it is not /var/log/weewx.log or 
>>>> /var/tmp/weewx.log. Originally I had added a [Logging] section in 
>>>> weewx.conf but now the weewx 4.10.2 has removed that functionality I am 
>>>> not 
>>>> sure how else to log weewx output to a different file.
>>>>
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "weewx-user" group

Re: [weewx-user] Problems with weewx on MacOS

[seano...@gmail.com]

Thank you for the replies and suggestions. The logging is now working to 
/var/log/weewx.log

When I run weewx directly I can see the sensor data coming in. It seems 
like it's just the final step when it uploads the data to windguru that it 
is failing. I have confirmed that the station details are correct. When I 
ping windguru.cz, there is a reply. Any ideas?

2023-05-21 19:35:41  weewx[3859] DEBUG weewx.reportengine: Report 'RSYNC' 
not enabled. Skipping.
2023-05-21 19:35:44  weewx[3859] DEBUG weewx.restx: WindGuru: Failed upload 
attempt 2: Server response: b'ERROR (no data)'
2023-05-21 19:35:45  weewx[3859] DEBUG weewx.restx: StationRegistry: Failed 
upload attempt 2: HTTP Error 502: Bad Gateway
2023-05-21 19:35:50  weewx[3859] DEBUG weewx.restx: WindGuru: Failed upload 
attempt 3: Server response: b'ERROR (no data)'
2023-05-21 19:35:50  weewx[3859] ERROR weewx.restx: WindGuru: Failed to 
publish record 2023-05-21 19:35:00 +04 (1684683300): Failed upload after 3 
tries
2023-05-21 19:35:51  weewx[3859] DEBUG weewx.restx: StationRegistry: Failed 
upload attempt 3: HTTP Error 502: Bad Gateway
2023-05-21 19:35:51  weewx[3859] ERROR weewx.restx: StationRegistry: Failed 
to publish record 2023-05-21 19:35:00 +04 (1684683300): Failed upload after 
3 tries



On Sunday, May 21, 2023 at 3:43:15 PM UTC+4 Tom Keffer wrote:

> I have never been able to get system logging from Python to work on the 
> Mac. I'm sure it can be done --- I just don't know how. If you Google 
> around, apparently others have struggled to get it to work as well.
>
> Instead, I just log to a rotating file. See the section *Logging to 
> rotating files 
> <https://github.com/weewx/weewx/wiki/WeeWX-v4-and-logging#logging-to-rotating-files>*
>  in 
> the Wiki. The example logs to /var/log/weewx.log, which will require root 
> privileges. Another option is to log to /Users/Shared/weewx/weewx.log, or 
> some other place where you don't need those privileges.
>
>
>
> On Sun, May 21, 2023 at 2:47 AM Graham Eddy  wrote:
>
>> tom did not say that 4.10.2 removed [Logging], he did ask you to remove 
>> that section temporarily, to get it to use default, in case your own 
>> content of that section was wrong. tom said that you were using a specific 
>> item (i think it was ‘rotate’) that was removed in 4.10.2 and thus causing 
>> your runtime error
>>
>> i think in macOS the default behaviour is to log under /var/log/system.log
>>
>> once the default configuration is working, no doubt you will add some 
>> entries to [Logging] to use a file of your choice, such as 
>> /var/log/weewx.log
>> *⊣GE⊢*
>>
>> On 21 May 2023, at 7:33 pm, seano...@gmail.com  
>> wrote:
>>
>> However, I am still having some problem and I'm struggling to identify 
>> exactly what because I'm not sure how to check the logs on MacOS. I'm sorry 
>> for the noob question, but can someone please guide me on where weewx is 
>> logging to? I can confirm that it is not /var/log/weewx.log or 
>> /var/tmp/weewx.log. Originally I had added a [Logging] section in 
>> weewx.conf but now the weewx 4.10.2 has removed that functionality I am not 
>> sure how else to log weewx output to a different file.
>>
>>
>> -- 
>> 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/ADD2976B-D69E-4BD4-A23F-FA1D439063DC%40geddy.au
>>  
>> <https://groups.google.com/d/msgid/weewx-user/ADD2976B-D69E-4BD4-A23F-FA1D439063DC%40geddy.au?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/c18a02bc-6371-49a8-ad07-42e794b524e9n%40googlegroups.com.

Re: [weewx-user] Problems with weewx on MacOS

[seano...@gmail.com]

As an update to this, I uninstalled Pillow 9.5.0 and then installed Pillow 
9.4.0 and now the error is gone.

However, I am still having some problem and I'm struggling to identify 
exactly what because I'm not sure how to check the logs on MacOS. I'm sorry 
for the noob question, but can someone please guide me on where weewx is 
logging to? I can confirm that it is not /var/log/weewx.log or 
/var/tmp/weewx.log. Originally I had added a [Logging] section in 
weewx.conf but now the weewx 4.10.2 has removed that functionality I am not 
sure how else to log weewx output to a different file.

Appreciate the help, thanks.

On Sunday, May 21, 2023 at 12:52:13 PM UTC+4 seano...@gmail.com wrote:

> Hi Tom,
>
> Thanks for the reply. You are right, I removed the [Logging] section from 
> the weewx.conf file and then it ran successfully and I can see all the 
> output. Now I am running into another problem where the data is not being 
> posted to windguru. Please can you check the output here 
> <https://u.pcloud.link/publink/show?code=XZyMg6VZnvhMyWUEdMmUAIivQYom78uVLRUy>
>  
> and give me your opinion of what is wrong? I also posted a small part of it 
> below. Thanks in advance. 
>
> 'None', 'humidex': 'None', 'inDewpoint': 'None', 'maxSolarRad': 'None', 
> 'outHumidity': 'None', 'outTemp': 'None', 'outTempBatteryStatus': '2.76', 
> 'pressure': 'None', 'radiation': '692', 'rain': '0.0', 'rainRate': '0.0', 
> 'usUnits': '1', 'UV': '9.85', 'windBatteryStatus': '2.76', 'windchill': 
> 'None', 'windDir': '35', 'windrun': 'None'
> REC:2023-05-21 10:30:00 +04 (1684650600) 'altimeter': 'None', 
> 'appTemp': 'None', 'barometer': 'None', 'cloudbase': 'None', 'dateTime': 
> '1684650600', 'dewpoint': 'None', 'ET': '0.0008638609251008569', 
> 'heatindex': 'None', 'humidex': 'None', 'inDewpoint': 'None', 'interval': 
> '5.0', 'maxSolarRad': 'None', 'outHumidity': 'None', 'outTemp': 'None', 
> 'outTempBatteryStatus': '2.7618', 'pressure': 'None', 'radiation': '471.6', 
> 'rain': '0.0', 'rainRate': '0.0', 'usUnits': '1', 'UV': 
> '7.0125', 'windBatteryStatus': '2.7618', 'windchill': 'None', 
> 'windrun': 'None'
>
> Traceback (most recent call last):
>   File "/Users/Shared/weewx/bin/weewx/reportengine.py", line 197, in run
> obj.start()
>   File "/Users/Shared/weewx/bin/weewx/reportengine.py", line 385, in start
> self.run()
>   File "/Users/Shared/weewx/bin/weewx/imagegenerator.py", line 42, in run
> self.gen_images(self.gen_ts)
>   File "/Users/Shared/weewx/bin/weewx/imagegenerator.py", line 114, in 
> gen_images
> image = plot.render()
>   File "/Users/Shared/weewx/bin/weeplot/genplot.py", line 222, in render
> self._renderDayNight(sdraw)
>   File "/Users/Shared/weewx/bin/weeplot/genplot.py", line 266, in 
> _renderDayNight
> sdraw.rectangle(((xleft,self.yscale[0]),
>   File "/Users/Shared/weewx/bin/weeplot/utilities.py", line 442, in 
> rectangle
> self.draw.rectangle(box_scaled, **options)
>   File "/usr/local/lib/python3.10/site-packages/PIL/ImageDraw.py", line 
> 294, in rectangle
> self.draw.draw_rectangle(xy, fill, 1)
> ValueError: y1 must be greater than or equal to y0
>
> On Saturday, May 20, 2023 at 3:40:00 PM UTC+4 Tom Keffer wrote:
>
>> By default, V4.10.2 does not include a 'rotate' logging handler. It has 
>> to be added.
>>
>> By any chance, do you have a [Logging] section in weewx.conf? If so, what 
>> does it say?
>>
>> On Sat, May 20, 2023 at 1:38 AM seano...@gmail.com  
>> wrote:
>>
>>> Hi,
>>>
>>> I have done many successful installations of weewx on raspberry pi and I 
>>> previously installed weewx on MacOS successfully. About a month ago, the 
>>> MacOS station stopped reporting so I have been troubleshooting it. I can't 
>>> figure out what is going on because I am very poor with python. Can anyone 
>>> give me any suggestions? I have tried to remove and reinstall python3 using 
>>> brew - currently version 3.10.8 is running when I type 'python3 --version'.
>>>
>>> I also updated weewx to 4.10.2 and from what i can see everything is 
>>> installed and working, including all dependencies. But still when I 
>>> run 'sudo python3 ./bin/weewxd weewx.conf' I get python errors. Please can 
>>> someone see below and give me any suggestions? Thank you
>>>
>>> apple@Mac-mini weewx % sudo python3 ./bin/weewxd weewx.conf
>>> Traceback (most recent call last):
>>>   File 
>>> "/usr/local/Cellar/pyt...@3.10/3.10.8/Frameworks/Python.framework/Versions/3.10/lib/python3.10/logging/config.py",
>>>  
&g

Re: [weewx-user] Problems with weewx on MacOS

[seano...@gmail.com]

Hi Tom,

Thanks for the reply. You are right, I removed the [Logging] section from 
the weewx.conf file and then it ran successfully and I can see all the 
output. Now I am running into another problem where the data is not being 
posted to windguru. Please can you check the output here 
<https://u.pcloud.link/publink/show?code=XZyMg6VZnvhMyWUEdMmUAIivQYom78uVLRUy> 
and give me your opinion of what is wrong? I also posted a small part of it 
below. Thanks in advance. 

'None', 'humidex': 'None', 'inDewpoint': 'None', 'maxSolarRad': 'None', 
'outHumidity': 'None', 'outTemp': 'None', 'outTempBatteryStatus': '2.76', 
'pressure': 'None', 'radiation': '692', 'rain': '0.0', 'rainRate': '0.0', 
'usUnits': '1', 'UV': '9.85', 'windBatteryStatus': '2.76', 'windchill': 
'None', 'windDir': '35', 'windrun': 'None'
REC:2023-05-21 10:30:00 +04 (1684650600) 'altimeter': 'None', 
'appTemp': 'None', 'barometer': 'None', 'cloudbase': 'None', 'dateTime': 
'1684650600', 'dewpoint': 'None', 'ET': '0.0008638609251008569', 
'heatindex': 'None', 'humidex': 'None', 'inDewpoint': 'None', 'interval': 
'5.0', 'maxSolarRad': 'None', 'outHumidity': 'None', 'outTemp': 'None', 
'outTempBatteryStatus': '2.7618', 'pressure': 'None', 'radiation': '471.6', 
'rain': '0.0', 'rainRate': '0.0', 'usUnits': '1', 'UV': 
'7.0125', 'windBatteryStatus': '2.7618', 'windchill': 'None', 
'windrun': 'None'
Traceback (most recent call last):
  File "/Users/Shared/weewx/bin/weewx/reportengine.py", line 197, in run
obj.start()
  File "/Users/Shared/weewx/bin/weewx/reportengine.py", line 385, in start
self.run()
  File "/Users/Shared/weewx/bin/weewx/imagegenerator.py", line 42, in run
self.gen_images(self.gen_ts)
  File "/Users/Shared/weewx/bin/weewx/imagegenerator.py", line 114, in 
gen_images
image = plot.render()
  File "/Users/Shared/weewx/bin/weeplot/genplot.py", line 222, in render
self._renderDayNight(sdraw)
  File "/Users/Shared/weewx/bin/weeplot/genplot.py", line 266, in 
_renderDayNight
sdraw.rectangle(((xleft,self.yscale[0]),
  File "/Users/Shared/weewx/bin/weeplot/utilities.py", line 442, in 
rectangle
self.draw.rectangle(box_scaled, **options)
  File "/usr/local/lib/python3.10/site-packages/PIL/ImageDraw.py", line 
294, in rectangle
self.draw.draw_rectangle(xy, fill, 1)
ValueError: y1 must be greater than or equal to y0

On Saturday, May 20, 2023 at 3:40:00 PM UTC+4 Tom Keffer wrote:

> By default, V4.10.2 does not include a 'rotate' logging handler. It has to 
> be added.
>
> By any chance, do you have a [Logging] section in weewx.conf? If so, what 
> does it say?
>
> On Sat, May 20, 2023 at 1:38 AM seano...@gmail.com  
> wrote:
>
>> Hi,
>>
>> I have done many successful installations of weewx on raspberry pi and I 
>> previously installed weewx on MacOS successfully. About a month ago, the 
>> MacOS station stopped reporting so I have been troubleshooting it. I can't 
>> figure out what is going on because I am very poor with python. Can anyone 
>> give me any suggestions? I have tried to remove and reinstall python3 using 
>> brew - currently version 3.10.8 is running when I type 'python3 --version'.
>>
>> I also updated weewx to 4.10.2 and from what i can see everything is 
>> installed and working, including all dependencies. But still when I 
>> run 'sudo python3 ./bin/weewxd weewx.conf' I get python errors. Please can 
>> someone see below and give me any suggestions? Thank you
>>
>> apple@Mac-mini weewx % sudo python3 ./bin/weewxd weewx.conf
>> Traceback (most recent call last):
>>   File 
>> "/usr/local/Cellar/pyt...@3.10/3.10.8/Frameworks/Python.framework/Versions/3.10/lib/python3.10/logging/config.py",
>>  
>> line 565, in configure
>> handler = self.configure_handler(handlers[name])
>>   File 
>> "/usr/local/Cellar/pyt...@3.10/3.10.8/Frameworks/Python.framework/Versions/3.10/lib/python3.10/logging/config.py",
>>  
>> line 723, in configure_handler
>> klass = self.resolve(cname)
>>   File 
>> "/usr/local/Cellar/pyt...@3.10/3.10.8/Frameworks/Python.framework/Versions/3.10/lib/python3.10/logging/config.py",
>>  
>> line 383, in resolve
>> name = s.split('.')
>> AttributeError: 'NoneType' object has no attribute 'split'
>>
>> The above exception was the direct cause of the following exception:
>>
>> Traceback (most recent call last):
>>   File "/Users/Shared/weewx/./bin/weewxd", line 249, in 
>> main()
>>   File "/Users/Shared/weewx/./bin/weewxd", line 98, in main
>> weeutil.logger.setup(options.log_label, config_dict)
>>   File "/Users/Shared/weewx/bi

[weewx-user] Re: ValueError: y1 must be greater than or equal to y0 in fresh installed weewx 4.10.2

[seano...@gmail.com]

Hi,

I seem to be having this same error but I don't understand exactly how to 
rectify it. Please can you explain in a simple way how to apply the patch?

Appreciate it, thank you.

On Wednesday, April 12, 2023 at 1:01:59 AM UTC+4 Marius Schamschula wrote:

> I ran into the same error after a routine update to FreeBSD 13.1 packages.
>
> I applied the patch and reinstalled weewx 4.10.2, and all is again working 
> as expected!
>
> On Tuesday, April 4, 2023 at 2:33:53 AM UTC-5 c s (224) wrote:
>
>> Thank you very much for digging deeper! My solution will then be to 
>> simply install an older version of the Pillow library. Thanks a lot!
>>
>> c s (224) schrieb am Montag, 3. April 2023 um 13:18:39 UTC+2:
>>
>>> Hello,
>>>
>>> I have just installed weewx as described here: 
>>> https://weisser-zwerg.dev/posts/ecowitt-gw2000-weewx-docker
>>>
>>> And I run into an error that prevents the images from being drawn:
>>>
>>> weewx-weewx-1  | Apr  3 13:11:03 weewx[20] ERROR 
>>> weewx.reportengine:   Generator terminated 
>>> weewx-weewx-1  | Traceback (most recent call last): 
>>> weewx-weewx-1  |   File "/home/weewx/bin/weewx/reportengine.py", 
>>> line 197, in run 
>>> weewx-weewx-1  | obj.start() 
>>> weewx-weewx-1  |   File "/home/weewx/bin/weewx/reportengine.py", 
>>> line 385, in start 
>>> weewx-weewx-1  | self.run() 
>>> weewx-weewx-1  |   File "/home/weewx/bin/weewx/imagegenerator.py", 
>>> line 42, in run 
>>> weewx-weewx-1  | self.gen_images(self.gen_ts) 
>>> weewx-weewx-1  |   File "/home/weewx/bin/weewx/imagegenerator.py", 
>>> line 114, in gen_images 
>>> weewx-weewx-1  | image = plot.render() 
>>> weewx-weewx-1  | ^ 
>>> weewx-weewx-1  |   File "/home/weewx/bin/weeplot/genplot.py", line 
>>> 222, in render 
>>> weewx-weewx-1  | self._renderDayNight(sdraw) 
>>> weewx-weewx-1  |   File "/home/weewx/bin/weeplot/genplot.py", line 
>>> 266, in _renderDayNight 
>>> weewx-weewx-1  | sdraw.rectangle(((xleft,self.yscale[0]), 
>>> weewx-weewx-1  |   File "/home/weewx/bin/weeplot/utilities.py", 
>>> line 442, in rectangle 
>>> weewx-weewx-1  | self.draw.rectangle(box_scaled, **options) 
>>> weewx-weewx-1  |   File 
>>> "/opt/venv/lib/python3.11/site-packages/PIL/ImageDraw.py", line 294, in 
>>> rectangle 
>>> weewx-weewx-1  | self.draw.draw_rectangle(xy, fill, 1) 
>>> weewx-weewx-1  | ValueError: y1 must be greater than or equal to y0
>>>
>>> I have followed the complete set-up process as described in "WeeWX: 
>>> Installation using setup.py", except that I do use a conda environment and 
>>> pip packages rather than the OS packages:
>>>
>>> > mamba create -n weewx python=3.9
>>> > conda activate weewx
>>> > pip3 install configobj paho-mqtt pyserial pyusb Cheetah3 Pillow ephem 
>>> > wget https://weewx.com/downloads/weewx-4.10.2.tar.gz
>>> > tar -xzvf weewx-4.10.2.tar.gz
>>> > cd weewx-4.10.2
>>> > python3 ./setup.py build
>>> > python3 ./setup.py install
>>> > # create the weewx.conf.patch from here: 
>>> https://weisser-zwerg.dev/posts/ecowitt-gw2000-weewx-docker/
>>> > patch -p1 weewx.conf < weewx.conf.patch
>>> > wget -O weewx-mqtt.zip 
>>> https://github.com/matthewwall/weewx-mqtt/archive/master.zip
>>> > ./bin/wee_extension --install ./weewx-mqtt.zip
>>> > wget -O weewx-interceptor.zip 
>>> https://github.com/matthewwall/weewx-interceptor/archive/master.zip
>>> > ./bin/wee_extension --install ./weewx-interceptor.zip
>>> > # ---
>>> > ./bin/weewxd
>>>
>>> I still run into the exact same problem. I've tried several 
>>> modifications to the config file, but cannot figure out what causes this 
>>> problem. I've also added some print statement to tell me more about the 
>>> issue around the drawing of the rectangle:
>>> def rectangle(self, box, **options):
>>> """Draw a scaled rectangle.
>>> box: A pair of 2-way tuples, containing coordinates of opposing corners
>>> of the box.
>>> options: passed on to draw.rectangle. Usually contains 'fill' (the color)
>>> """
>>> box_scaled = [(coord[0] * self.xscale + self.xoffset + 0.5,
>>> coord[1] * self.yscale + self.yoffset + 0.5) for coord in box]
>>> try:
>>> self.draw.rectangle(box_scaled, **options)
>>> print("Draw rectangle succeeded.")
>>> except:
>>> print("Draw rectangle failed:")
>>> print(box)
>>> print(box_scaled)
>>> print(f"self.xscale: {self.xscale}, self.xoffset: {self.xoffset}, 
>>> self.yscale: {self.yscale}, self.yoffset: {self.yoffset}\n")
>>> pass
>>>
>>> And I get results as follows:
>>> # ((1680429600, 1029.60001), (1680457455, 1030.10001))
>>> # [(44.01851851865649, 144.49709), (216.6138955116, 
>>> 24.4970896)]
>>> # self.xscale: 0.004465020576131688, self.xoffset: -7503109, 
>>> self.yscale: -240.0, self.yoffset: 247248
>>>
>>> Do you have any clues on how to resolve this?
>>>
>>>
>>> Thanks!
>>>
>>>

-- 
You received this message because you are 

[weewx-user] Problems with weewx on MacOS

[seano...@gmail.com]

Hi,

I have done many successful installations of weewx on raspberry pi and I 
previously installed weewx on MacOS successfully. About a month ago, the 
MacOS station stopped reporting so I have been troubleshooting it. I can't 
figure out what is going on because I am very poor with python. Can anyone 
give me any suggestions? I have tried to remove and reinstall python3 using 
brew - currently version 3.10.8 is running when I type 'python3 --version'.

I also updated weewx to 4.10.2 and from what i can see everything is 
installed and working, including all dependencies. But still when I 
run 'sudo python3 ./bin/weewxd weewx.conf' I get python errors. Please can 
someone see below and give me any suggestions? Thank you

apple@Mac-mini weewx % sudo python3 ./bin/weewxd weewx.conf
Traceback (most recent call last):
  File 
"/usr/local/Cellar/python@3.10/3.10.8/Frameworks/Python.framework/Versions/3.10/lib/python3.10/logging/config.py",
 
line 565, in configure
handler = self.configure_handler(handlers[name])
  File 
"/usr/local/Cellar/python@3.10/3.10.8/Frameworks/Python.framework/Versions/3.10/lib/python3.10/logging/config.py",
 
line 723, in configure_handler
klass = self.resolve(cname)
  File 
"/usr/local/Cellar/python@3.10/3.10.8/Frameworks/Python.framework/Versions/3.10/lib/python3.10/logging/config.py",
 
line 383, in resolve
name = s.split('.')
AttributeError: 'NoneType' object has no attribute 'split'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/Users/Shared/weewx/./bin/weewxd", line 249, in 
main()
  File "/Users/Shared/weewx/./bin/weewxd", line 98, in main
weeutil.logger.setup(options.log_label, config_dict)
  File "/Users/Shared/weewx/bin/weeutil/logger.py", line 139, in setup
logging.config.dictConfig(log_dict)
  File 
"/usr/local/Cellar/python@3.10/3.10.8/Frameworks/Python.framework/Versions/3.10/lib/python3.10/logging/config.py",
 
line 811, in dictConfig
dictConfigClass(config).configure()
  File 
"/usr/local/Cellar/python@3.10/3.10.8/Frameworks/Python.framework/Versions/3.10/lib/python3.10/logging/config.py",
 
line 572, in configure
raise ValueError('Unable to configure handler '
ValueError: Unable to configure handler 'rotate'
apple@Mac-mini 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/298c4f09-6ad2-40af-90c6-4469811ac778n%40googlegroups.com.

[weewx-user] Tempest to Windguru reporting incorrect wind speed

[seano...@gmail.com]

Hi,

I have a weather station with Raspberry Pi and a WeatherFlow Tempest 
sensor. It has been working perfectly for a few months. Suddenly it is 
reporting an incorrect wind speed on windguru. On the Weatherflow app for 
iPhone it says 10 knots which is accurate according to the reality. 
However, on windguru it's showing 15-18 knots, or something like that. In 
other words, higher than it really is. I've had this issue in the past with 
a kph/mph conversion error within python. Could it be something like this?

It's just very strange because a few days ago it was accurate and I didn't 
make any change or update to the Raspberry Pi. Is anyone else having this 
issue?

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/ec9bc572-5431-474f-aea7-0478ef3d83b1n%40googlegroups.com.

Re: [weewx-user] Re: Broadcast to weewx from Weatherflow tempest station

[seano...@gmail.com]

Just a quick update on this...

I managed to get my weather flow tempest weather station broadcasting to 
windguru. This was done by using the weewx extension 
https://github.com/captain-coredump/weatherflow-udp

Thanks for all the support. And a big thank you to everyone involved in 
creating this amazing software.

-- 
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/77934d3f-8ea9-4b92-a641-18cfe4fe63c3n%40googlegroups.com.

Re: [weewx-user] Re-installed weewx using setup.py and now it won't start at boot

[seano...@gmail.com]

Just a quick update.

One last attempt to get weewx running at boot before I drive out and format 
the microsd card to start fresh. I followed the below article to 
automatically run weewx using systemd and it is working now! Thanks for all 
the support.

https://github.com/weewx/weewx/wiki/systemd

-- 
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/ecb10915-8d72-4484-bc4b-99adea19e707n%40googlegroups.com.

[weewx-user] Re-installed weewx using setup.py and now it won't start at boot

[seano...@gmail.com]

Hi,

I originally had weewx installed using the DEB package which was fine. With 
the intention of using multiple instances of weewx for different stations, 
I have uninstalled that and then I re-installed weewx using setup.py to the 
/home/weewx/

It works perfectly when I run it directly in terminal using *sudo 
./bin/weewxd* but I have not been able to add the script to *init.d/weewx* 
in order for it to run at boot. I have followed the instructions 
at https://weewx.com/docs/setup.htm but weewx will not start at boot and 
after boot, even if I manually run sudo /etc/init.d/weewx start it does 
nothing. I can tell because I'm tailing the log file and nothing happens. 
Run it manually, it starts collecting data perfectly.

I used the default file from /weewx/utils/weewx.debian and copied it to 
/etc/init.d/weewx and I did not make any changes. Is there something else 
I'm supposed to do. The weewx installation was done to the default 
/home/weewx directory.

Would appreciate any suggestions.

-- 
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/9cfe9263-c54c-47f3-9ed5-f2197bb7696en%40googlegroups.com.

[weewx-user] weewx reporting incorrectly?

[seano...@gmail.com]

Hi,

I had a problem before were rtl-sdr got updated and something changed, then 
suddenly weewx was receiving an incorrect unit and converting incorrectly 
and as a result of that, windguru was reporting wind that was much stronger 
that it really was. I seem to be having the same problem again

This is the station in Cape Town: https://www.windguru.cz/station/2655
You can see the log here 
. 
At the same time you can see a screenshot of the same data being displayed 
by windguru here 

.

The different is very big, tail is reporting "wind_avg_km_h" : 33.284 and 
windguru is reporting something like 26 knots. I feel like the same problem 
that happened before is happening again.

Is anyone else experiencing this?


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8cd0d5fd-9d60-4aab-86a7-630f313b1395n%40googlegroups.com.

[weewx-user] Broadcast to weewx from Weatherflow tempest station

[seano...@gmail.com]

Hi,

After many months of not being able to identify why an Acurite 5-in-1 
randomly goes offline or broadcasts a zero wind speed when the wind is 
often above 10 knots, I have decided to try a different station. I have 
purchased a weather flow tempest which works really well using the app.

I am wondering if there is any way to take the weather information from 
this station and get it onto WindGuru? If anyone has any suggestions, 
please let me know.

Thanks,
Sean.

-- 
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/18e0c6dc-eda7-4384-9a92-1711e3565c3an%40googlegroups.com.

[weewx-user] Acurite 5-in-1 and rtl_sdr odd behavior

[seano...@gmail.com]

I have a Acurite 5-in-1 and a raspberry pi with an SDR adaptor that 
receives the packets which are then interpreted by weewx and uploaded to 
windguru. There is something weird happening that does not make sense to me.

Randomly, for a reason that I cannot understand, the weather station will 
start reporting 0 knots, this will happen for a random amount of time and 
then it'll start reporting correctly again. You can see the behavior on the 
graph https://www.windguru.cz/station/2146

The station going offline is me turning it off and waiting a while before 
turning it on again. Maybe 3 or 4 times in the last 2 months I have found 
the unique property identifier had changed, so I alter it in weewx.conf and 
then it works again.

If I tail weewx then you can see the wind_speed property reporting 0 here 

.

But then I stop weewx (sudo service weewx stop) and then run rtl directly 
using:

sudo PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/sdr.py 
--cmd="rtl_433 -M utc -F json"]

you can see it's reporting a wind_speed that is *not* 0 here 


Can anyone help me understand what is going on here?

-- 
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/0f0964db-4e34-40fb-9a88-50fee74f447bn%40googlegroups.com.

[weewx-user] Re: Acurite 5in1 and rtl_sdr

[seano...@gmail.com]

Hi All,

Thanks for the feedback, very much appreciated.

@mksm... thanks, I will try your suggestions. Funny because I was 
originally told to use a 17cm antenna, I'm surprised to hear you mention 
31cm ??

Regarding the SDR, it is a solution to capture the broadcasts from the 
Acurite 5n1 sensor directly, ie. no need for the weather display. You can 
read more here: https://github.com/weewx/weewx/wiki/sdr-rpi-recipe 
Actually, I have build 3 weather stations and the first one is using the 
acurite display which then connects to the pi via USB cable, and I found it 
to have a lot of challenges to keep it online. Even with a USB hub for 
continuous power, it goes offline often and needs a certain procedure to 
get things online again. When I learnt about the SDR solution I was really 
hopeful that it would be a 100% reliable solution but I'm disappointed to 
find that there are still challenges, although less than with the display 
option.

Thanks,
Sean.

-- 
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/b0d592dd-8d66-456f-a45e-5e4f2db49b19n%40googlegroups.com.

Re: [weewx-user] Re: Acurite 5in1 and rtl_sdr

[seano...@gmail.com]

*UPDATE*:

After 3 days of working perfectly, the pi stopped receiving from the 
weather sensor and has not received a single transmission in 48 hours. When 
I close weewx and run rtf_433 directly, no sensors are seen either. Today I 
collected the devices and brought them home and then plugged them in, they 
work perfectly. Back to the drawing board.

My latest theory is that somewhere nearby, someone has powered on a device 
that transmits at the same 433mhz frequency and it is blocking the Acurite 
sensor transmissions from reaching the Raspberry Pi. Now I just need to 
prove it. I feel like the answer lies in using the Pi + SDR dongle and 
running gnuradio companion to a) prove my theory is true or false and b) 
help me to locate the device causing this trouble.

Does anyone know if the Acurite 5-in-1 devices can be modified to transmit 
at a different frequency?

-- 
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/e4a50783-20e3-42ec-b1ee-45732aba61d3n%40googlegroups.com.

Re: [weewx-user] Re: Acurite 5in1 and rtl_sdr

[seano...@gmail.com]

Hi Clay,

Thanks a lot for the suggestion. Funny enough that same day you replied I 
decided to move the raspberry pi across the room and I'm amazed to see that 
the problem appears to be solved immediately.

I have been watching the weewx.log for months and now after moving the pi I 
can see more regular and consistent logging of the packets than before.. it 
used to be all over the place. But now, it receives a packet every 18 
seconds without fail. So yes, I think you are right, the pi was in an area 
that had some kind of electronic or magnetic interference.

Thanks again!

On Tuesday, January 26, 2021 at 11:38:29 PM UTC+4 cl...@n7qnm.net wrote:

> Hi, Sean – I have a 5-in-1, and it normally sends every 20-30 seconds.  
> However,  I had to buy one of the Acurite repeaters to get a reliable 
> connection to my base, I have lots of metal between the sensor and my 
> receiver, AND I’m a ham radio operator with LOTS of RF devices, so I’m in 
> an “RF-Rich” environment.I’d recommend looking at the signal strength 
> bars on your base; and making sure your base is receiving correctly.
>
>  
>
> Good luck!
>
>  
>
> Clay
>
>  
>
>  
>
> *From:* weewx...@googlegroups.com  *On Behalf 
> Of *seano...@gmail.com
> *Sent:* Monday, January 25, 2021 1:22 AM
> *To:* weewx-user 
> *Subject:* [weewx-user] Re: Acurite 5in1 and rtl_sdr
>
>  
>
> Hi,
>
>  
>
> Just a quick nudge about this. The Acurite 5-in-1 and the SDR are working, 
> but there are still times when minutes or hours can pass where the SDR is 
> not receiving any packets from the sensor, and therefore no broadcasts to 
> wind guru. Has anyone got any good ideas on troubleshooting this? Here is a 
> lot of the last few hours 
> https://u.pcloud.link/publink/show?code=XZiEH8XZD0glneQHykh8633IJuS6Xbc3fyzk
>
>  
>
> It's just so strange that sometimes the sensor will send a packet every 
> 20-seconds, and other times a few minutes will pass without a packet being 
> received. One would think that the packets should be consistent and regular.
>
>  
>
> Does anyone have any insight into how the Acurite 5-in-1 sensor sends 
> packets - should it be at a set time every x seconds, or is erratic normal?
>
>  
>
> I don't understand SDR much, could there be another device nearby that is 
> interfering with the receiving of packets?
>
>  
>
> Pulling my hair out trying to troubleshoot this problem!!
>
>  
>
> Thanks,
>
> Sean.
>
> -- 
> 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/2965896c-090b-4e59-a2ef-52dcfe744fa8n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/2965896c-090b-4e59-a2ef-52dcfe744fa8n%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/afa4bae5-c62c-497c-a1a9-70fb74f58990n%40googlegroups.com.

[weewx-user] Re: Acurite 5in1 and rtl_sdr

[seano...@gmail.com]

Hi,

Just a quick nudge about this. The Acurite 5-in-1 and the SDR are working, 
but there are still times when minutes or hours can pass where the SDR is 
not receiving any packets from the sensor, and therefore no broadcasts to 
wind guru. Has anyone got any good ideas on troubleshooting this? Here is a 
lot of the last few 
hours 
https://u.pcloud.link/publink/show?code=XZiEH8XZD0glneQHykh8633IJuS6Xbc3fyzk

It's just so strange that sometimes the sensor will send a packet every 
20-seconds, and other times a few minutes will pass without a packet being 
received. One would think that the packets should be consistent and regular.

Does anyone have any insight into how the Acurite 5-in-1 sensor sends 
packets - should it be at a set time every x seconds, or is erratic normal?

I don't understand SDR much, could there be another device nearby that is 
interfering with the receiving of packets?

Pulling my hair out trying to troubleshoot this problem!!

Thanks,
Sean.

-- 
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/2965896c-090b-4e59-a2ef-52dcfe744fa8n%40googlegroups.com.

[weewx-user] Re: Acurite 5in1 and rtl_sdr

[seano...@gmail.com]

Thanks for the replies. I'm still scratching my head about this issue. A 
few weeks ago i installed a wifi plug onto the power line of the Raspberry 
Pi and i have been experimenting... whenever i see the station losing 
signal and having a breakup in the reporting (ie. *user.sdr: lines=[]*) 
then i power off the Raspberry Pi using the wifi switch which gives it a 
hard power off. I leave it off for 1 minute then power it back on and so 
far, every single time i do that, the raspberry pi starts receiving a 
signal from the Acurite5-in-1 again.

Currently, i am led to believe the RTL-SDR dongle i think i've installed (this 
one 
<https://www.amazon.com/gp/product/B01HA642SW/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8=1>)
 
is actually faulty. Because a software reset doesn't bring it back online, 
but a hard reset always does. Would be curious to know if anyone else has 
experienced anything like this? My next step is to purchase a new RTL-SDR 
dongle and see if it solves the problem.

Thanks,
Sean.

On Friday, October 30, 2020 at 6:37:00 PM UTC+4 RobbH wrote:

> My suspicion is that this happens because of unusual propagation 
> conditions such as "tropospheric ducting," which may be associated with 
> unusual weather or sunspot activity, among other factors. There are 
> occasions when distant radio or TV signals can be received briefly, 
> sometimes stronger than local stations. The same conditions might affect 
> the frequencies used by weather sensors.
>
> I have a rooftop 5in1 for wind and rain measurements and a 
> temperature/humidity sensor in the back yard, both connected through an 
> Acurite bridge. Sometimes Weewx stops receiving data from one sensor, while 
> the other continues to work for a time. Then the other sensor will go 
> silent, as well, and shortly afterward the first sensor will reappear. 
> Eventually, the second sensor also reconnects.
>
> The time difference suggests to me that the outages are caused by 
> something in motion, which could be an atmospheric condition. I can't rule 
> out the possibility that there's some sort of local source of interference, 
> though.
>
> I'm sure there are people reading this forum who know more about RF than I 
> do, so it would be great to hear their opinions about this.
>
> On Thursday, October 29, 2020 at 8:03:02 AM UTC-4 Peter Whisker wrote:
>
>> I find the same occurs on my FineOffset HP1000 clone - it happens to the 
>> device receiver.
>>
>> My (unproven) theory is that the signals from the external and internal 
>> sensors which come every 16 seconds drift with respect with each other 
>> until they end up being transmitted at exactly the same time and the 
>> receiver can not discriminate them. After half a day or so the situation 
>> recovers and is fine for a month or more.
>>
>> Peter
>>
>> On Thursday, October 29, 2020 at 4:12:29 AM UTC seano...@gmail.com wrote:
>>
>>> Hi,
>>>
>>> My station has been running weewx + rt_sdr for a year and all is working 
>>> well. Weewx receives the station data and broadcasts it to windguru. 
>>> However, there is an occasional problem that happens and i can't figure out 
>>> what the cause is. All of a sudden, rtl_433 stops receiving from the sensor 
>>> for hours at a time.
>>>
>>> During those periods, when i run: 
>>> *sudo tail -f /var/log/weewx.log*
>>>
>>> All i see is:
>>> *user.sdr: lines=[]*
>>>
>>> If you leave it, it eventually comes back online itself. I can confirm 
>>> that during that time there was no loss of power or internet - because i 
>>> can still connect to the pi and manage it. Also, weather station has new 
>>> batteries, so that is not the problem. I have a feeling that the problem is 
>>> happening with the realtek SDR dongle. Because a power reset sometimes 
>>> fixes the problem - and a physical removal of the USB dongle into a 
>>> different USB port seems to fix the problem immedaitely.
>>>
>>> I've even tried a python script to eject the USB device which also seems 
>>> to help. But in order to do this i first need to disable rtl_433 in the 
>>> weewx.conf, then reboot, then run rtl_433 on its own until it sees the 
>>> sensor, then re-enable rtl_433 in weewx.conf and reboot. That is usually 
>>> the process to fix it immediately, so it definitely feels to me like a 
>>> software issue.
>>>
>>> Any ideas?
>>>
>>> Thanks,
>>> Sean
>>>
>>

-- 
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/6aba7684-4bab-4866-b5d8-21c00f0c18c1n%40googlegroups.com.

[weewx-user] Re: weewx generates reports in simulator mode, but not in SDR mode

[seano...@gmail.com]

Just an update, i think i worked it out...

My [[sensor_map] did not have an underscore between sensor and map.

It's working now.

On Friday, December 18, 2020 at 5:24:02 PM UTC+4 seano...@gmail.com wrote:

> Hi,
>
> I have built a few weather stations so i'm familiar with the process but 
> for some reason i can't understand why weewx is not generating reports when 
> set to SDR mode. Because it works as soon as i change it into simulator 
> mode.
>
> In simulator mode i can use a local computer to browse 192.168.1.123/weewx 
> and i see the reports. When i switch to SDR, that same link does not show 
> the reports, just a file structure.
>
> From what i see and understand, the SDR adaptor is receiving the 
> transmission from the sensor correctly. I have already used the correct 
> identifiers in the [[sensor_map]] section of the weewx.conf - to me it only 
> looks like weewx is not generating reports. Would appreciate if anyone can 
> see anything that i am missing?
>
> weewx.conf
>
> https://u.pcloud.link/publink/show?code=XZIEH8XZnNUlXWDEYnj5qJ2HU4pqLQuv91RV
>
> weewx.log
>
> https://u.pcloud.link/publink/show?code=XZiEH8XZD0glneQHykh8633IJuS6Xbc3fyzk
>

-- 
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/1f04834a-f8bf-48ad-a3c5-b6cf1de5f4f7n%40googlegroups.com.

[weewx-user] weewx generates reports in simulator mode, but not in SDR mode

[seano...@gmail.com]

Hi,

I have built a few weather stations so i'm familiar with the process but 
for some reason i can't understand why weewx is not generating reports when 
set to SDR mode. Because it works as soon as i change it into simulator 
mode.

In simulator mode i can use a local computer to browse 192.168.1.123/weewx 
and i see the reports. When i switch to SDR, that same link does not show 
the reports, just a file structure.

>From what i see and understand, the SDR adaptor is receiving the 
transmission from the sensor correctly. I have already used the correct 
identifiers in the [[sensor_map]] section of the weewx.conf - to me it only 
looks like weewx is not generating reports. Would appreciate if anyone can 
see anything that i am missing?

weewx.conf
https://u.pcloud.link/publink/show?code=XZIEH8XZnNUlXWDEYnj5qJ2HU4pqLQuv91RV

weewx.log
https://u.pcloud.link/publink/show?code=XZiEH8XZD0glneQHykh8633IJuS6Xbc3fyzk

-- 
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/afe10679-8c51-4b66-87bf-6eb9a4a2399bn%40googlegroups.com.

[weewx-user] Acurite 5in1 and rtl_sdr

[seano...@gmail.com]

Hi,

My station has been running weewx + rt_sdr for a year and all is working 
well. Weewx receives the station data and broadcasts it to windguru. 
However, there is an occasional problem that happens and i can't figure out 
what the cause is. All of a sudden, rtl_433 stops receiving from the sensor 
for hours at a time.

During those periods, when i run: 
*sudo tail -f /var/log/weewx.log*

All i see is:
*user.sdr: lines=[]*

If you leave it, it eventually comes back online itself. I can confirm that 
during that time there was no loss of power or internet - because i can 
still connect to the pi and manage it. Also, weather station has new 
batteries, so that is not the problem. I have a feeling that the problem is 
happening with the realtek SDR dongle. Because a power reset sometimes 
fixes the problem - and a physical removal of the USB dongle into a 
different USB port seems to fix the problem immedaitely.

I've even tried a python script to eject the USB device which also seems to 
help. But in order to do this i first need to disable rtl_433 in the 
weewx.conf, then reboot, then run rtl_433 on its own until it sees the 
sensor, then re-enable rtl_433 in weewx.conf and reboot. That is usually 
the process to fix it immediately, so it definitely feels to me like a 
software issue.

Any ideas?

Thanks,
Sean

-- 
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/fbd66625-0ca8-42e3-b250-805b7e1ea228n%40googlegroups.com.