[weewx-user] Re: Request for assistance - GW2000/WS90

['Jon Fear' via weewx-user]

Gary,

jon@weewx:~$ sudo PYTHONPATH=/usr/share/weewx/user python3 -m api_data 
--run --i 
 p-address=192.168.10.16
CMD_BROADCAST (12):
Sending broadcast packet 'FF FF 12 03 15' to '255.255.255.255:46000'
Received broadcast response 'FF FF 12 00 27 E8 68 E7 12 8B 0F C0 A8 0A 
10 AF   C8 17 47 57 32 30 30 30 
41 2D 57 49 46 49 38 42 30 46 20 56 32 2E 31 2E 34 82'
Received broadcast response 'FF FF 12 00 27 E8 68 E7 12 8B 0F C0 A8 0A 
10 AF   C8 17 47 57 32 30 30 30 
41 2D 57 49 46 49 38 42 30 46 20 56 32 2E 31 2E 34 82'
Discovered device: {'mac': 'E8:68:E7:12:8B:0F', 'ip_address': 
'192.168.10.16  ', 'port': 
45000, 'ssid': 'GW2000A-WIFI8B0F V2.1.4'}
CMD_READ_FIRMWARE_VERSION (50):
 sending: FF FF 50 03 53
received: FF FF 50 12 0E 47 57 32 30 30 30 41 5F 56 32 2E 31 2E 34 B9
Device appears to be a 'GW2000'
CMD_READ_ (30):
 sending: FF FF 30 03 33
received: FF FF 30 0B 01 01 62 5F BB 36 27 01 17
CMD_READ_SENSOR_ID_NEW (3C):
 sending: FF FF 3C 03 3F
received: FF FF 3C 01 5B 00 FF FF FF FF FF 00 01 FF FF FF FF FF 00 02 
00 03   00 39 FF 00 03 00 00 C6 
AA 8D 03 04 FF FF FF FF 00 00 05 00 00 00 35 00 03 06 00   
00 00 C1 00 04 07 00 00 00 29 00 04 08 FF FF FF 
FF 00 00 09 FF FF FF FF 00 00 0 
 A FF FF FF FF 00 00 0B FF FF FF FF 00 00 0C FF FF FF FF 00 00 0D FF FF FF 
FF 00   00 0E FF FF FF FF 1F 00 
0F FF FF FF FF 1F 00 10 FF FF FF FF 1F 00 11 FF FF FF FF   
1F 00 12 FF FF FF FF 1F 00 13 FF FF FF FF 1F 00 
14 FF FF FF FF 1F 00 15 FF FF F 
 F FF 1F 00 16 00 00 00 A1 05 04 17 FF FF FF FF 0F 00 18 FF FF FF FF 0F 00 
19 FF   FF FF FF 0F 00 1A 00 01 
1E 83 05 03 1B FF FF FF FF 0F 00 1C FF FF FF FF 0F 00 1D   
FF FF FF FF 0F 00 1E FF FF FF FF 0F 00 1F FF FF 
FF FF FF 00 20 FF FF FF FF FF 0 
 0 21 FF FF FF FF FF 00 22 FF FF FF FF FF 00 23 FF FF FF FF FF 00 24 FF FF 
FF FF   FF 00 25 FF FF FF FF FF 
00 26 FF FF FF FF FF 00 27 FF FF FF FF 0F 00 28 FF FF FF   
FF FF 00 29 FF FF FF FF FF 00 2A FF FF FF FF FF 
00 2B FF FF FF FF FF 00 2C FF F 
 F FF FF FF 00 2D FF FF FF FF FF 00 2E FF FF FF FF FF 00 2F FF FF FF FF FF 
00 30   00 42 94 81 A4 04 A2
CMD_READ_RAINDATA (34):
 sending: FF FF 34 03 37
received: FF FF 34 17 00 00 00 00 00 00 00 00 00 00 00 0B 00 00 00 0C 
00 00   00 0C 6E
CMD_READ_RSTRAIN_TIME (55):
 sending: FF FF 55 03 58
received: FF FF 55 04 00 59
CMD_READ_RAIN (57):
 sending: FF FF 57 03 5A
received: FF FF 57 00 54 0E 00 00 10 00 00 00 00 11 00 00 00 0B 12 00 
00 00   0C 13 00 00 00 0C 0D 00 
00 0F 00 64 80 00 00 83 00 00 00 00 84 00 00 00 0F 85 00   
00 00 0F 86 00 00 00 0F 81 00 0C 87 00 64 00 64 
00 64 00 64 00 64 00 64 00 64 0 
 0 64 00 64 00 64 88 00 00 00 E5
jon@weewx:~$


Hope this helps

Jon
On Wednesday, 20 April 2022 at 05:58:10 UTC+1 gjr80 wrote:

> I'm presently working on adding support for the GW2000/WS90 to the GW1000 
> driver. Unfortunately the current release (1.6.4) of the Ecowitt gateway 
> API documentation has a number of errors relating to the GW2000/WS90. 
> Whilst I have been able to work around most of these errors, I am uncertain 
> if the revised driver will work robustly across the plethora of Ecowitt 
> setups I know are out there (in particular sites that have the WS90 and 
> another Ecowitt 'traditional' rain gauge). I also have also observed some 
> WS2000 behaviour that does no match the API documentation or indeed any of 
> the previous Ecowitt gateway devices and I am not sure if this is just my 
> device misbehaving or something wider.
>
> I would like to ask the Ecowitt GW2000/WS90 users for some help in running 
> a small python script to interrogate the GW2000. The script sends a number 
> of API commands to Ecowitt gateway devices on your network and the GW2000 
> and displays the raw data results on screen. It is the script output to the 
> screen that I am after. The script has no WeeWX dependencies but it does 
> require the python six module (this will already be installed if you are 
> running WeeWX v4.0.0 or later). The script can be downloaded and saved 
> anywhere (provided you alter the PY

[weewx-user] Request for assistance - GW2000/WS90

[gjr80]

I'm presently working on adding support for the GW2000/WS90 to the GW1000 
driver. Unfortunately the current release (1.6.4) of the Ecowitt gateway 
API documentation has a number of errors relating to the GW2000/WS90. 
Whilst I have been able to work around most of these errors, I am uncertain 
if the revised driver will work robustly across the plethora of Ecowitt 
setups I know are out there (in particular sites that have the WS90 and 
another Ecowitt 'traditional' rain gauge). I also have also observed some 
WS2000 behaviour that does no match the API documentation or indeed any of 
the previous Ecowitt gateway devices and I am not sure if this is just my 
device misbehaving or something wider.

I would like to ask the Ecowitt GW2000/WS90 users for some help in running 
a small python script to interrogate the GW2000. The script sends a number 
of API commands to Ecowitt gateway devices on your network and the GW2000 
and displays the raw data results on screen. It is the script output to the 
screen that I am after. The script has no WeeWX dependencies but it does 
require the python six module (this will already be installed if you are 
running WeeWX v4.0.0 or later). The script can be downloaded and saved 
anywhere (provided you alter the PYTHONPATH setting appropriately) or for 
convenience I suggest users download the script to /home/weewx/bin/user or 
/usr/share/weewx/user. There should be no sensitive data in the required 
output other than the local (not public) IP addresses of your Ecowitt 
gateway devices, but please check to satisfy yourself before 
sending/posting. If sending such info to me or posting here then please 
contact me via private message and we will see if we can work something out.

If you are a GW2000/WS90 user and would be willing to help out the 
following instructions should be followed:

1. download the script (change /home/weewx/bin/user to /usr/share/weewx/user 
if you have a WeeWX package install):

$ wget -P /home/weewx/bin/user 
https://raw.githubusercontent.com/gjr80/weewx-gw1000/api_1_6_4/bin/user/api_data.py

2. obtain the IP address of your GW2000

3. run the script(change /home/weewx/bin/user to /usr/share/weewx/user if 
you have a WeeWX package install):

$ PYTHONPATH=/home/weewx/bin python3 --run --ip-address=IP_ADDRESS

where IP_ADDRESS is the IP address of your GW2000. You may need to 
substitute python2 for python3 if you are running WeeWX under python2. You 
should see some output to screen similar to:

gary@bullseye30:~$ PYTHONPATH=/home/weewx/bin python3 -m user.api_data 
--run --ip-address=192.168.2.38
CMD_BROADCAST (12):
Sending broadcast packet 'FF FF 12 03 15' to '255.255.255.255:46000'
Received broadcast response 'FF FF 12 00 27 E8 68 E7 87 1C 5A C0 A8 02 
23 AF C8 17 47 57 31 31 30 30 43 2D 57 49 46 49 31 43 35 41 20 56 32 2E 31 
2E 33 D9'
Received broadcast response 'FF FF 12 00 26 DC 4F 22 58 B7 FF C0 A8 02 
24 AF C8 16 47 57 31 30 30 30 2D 57 49 46 49 42 37 46 46 20 56 31 2E 36 2E 
38 DF'
Received broadcast response 'FF FF 12 00 26 50 02 91 E3 FD 32 C0 A8 02 
25 AF C8 16 47 57 31 30 30 30 2D 57 49 46 49 46 44 33 32 20 56 31 2E 36 2E 
38 64'
Discovered device: {'mac': 'E8:68:E7:87:1C:5A', 'ip_address': 
'192.168.2.35', 'port': 45000, 'ssid': 'GW1100C-WIFI1C5A V2.1.3'}
Discovered device: {'mac': 'DC:4F:22:58:B7:FF', 'ip_address': 
'192.168.2.36', 'port': 45000, 'ssid': 'GW1000-WIFIB7FF V1.6.8'}
Discovered device: {'mac': '50:02:91:E3:FD:32', 'ip_address': 
'192.168.2.37', 'port': 45000, 'ssid': 'GW1000-WIFIFD32 V1.6.8'}
CMD_READ_FIRMWARE_VERSION (50):
 sending: FF FF 50 03 53
received: FF FF 50 12 0E 47 57 32 30 30 30 43 5F 56 32 2E 31 2E 34 BB

If you could capture this output as text (no images please) and either send 
to me privately or post here that would be appreciated.

Once finished you can delete api_data.py from the directory where it was 
saved.

thanks,
Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1314ef1e-7de8-48a6-9e8f-2633c7e75939n%40googlegroups.com.

[weewx-user] Re: weewx stopped creating new data after power outage

[gjr80]

Looks like a clear case of corrupt station memory, not unusual in a vantage 
station after a power loss. See the wiki article WeeWX generates HTML 
pages, but it does not update them 
.
 


Gary

On Wednesday, 20 April 2022 at 13:34:09 UTC+10 iams...@gmail.com wrote:

> I have been using weewx 4.5.1 more or less continuously since late 2019, 
> running on a Pi zero. I have had occasional problems, but they always seem 
> to be resolved by a restart or a system reboot.  There was a power outage 
> yesterday that shut down the power for several hours. After the power came 
> back, I have had no new data stored or displayed. Data during the power 
> outage was recovered though. Syslog indicates that weewx was very busy 
> after power was restored uploading the missing data to Wunderground, but 
> once that was done, it stopped creating new data. Every 5 minutes, it 
> creates a new report, but there is no new data in the database, no data 
> upload to Wundergound and no change to the images used to create the report 
> locally.
>
> It is as if the Vantage Pro weather station has stopped working, but as 
> far as I can tell, it is fine. I had the server in debug mode before this 
> happened, so it seems like there should be a smoking gun in Syslog, but I 
> don't see it. 
>
> Any ideas on what I should try to get back up and running? See below for a 
> Google drive link to the syslog file.  Thanks!
>
>
> https://drive.google.com/file/d/1uRIm29J9T8Dv2tAg7M1G6P7fKmaXpaCy/view?usp=sharing
>

-- 
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/bccfe931-a946-402c-8abe-181d6505c4c0n%40googlegroups.com.

[weewx-user] weewx stopped creating new data after power outage

[iams...@gmail.com]

I have been using weewx 4.5.1 more or less continuously since late 2019, 
running on a Pi zero. I have had occasional problems, but they always seem 
to be resolved by a restart or a system reboot.  There was a power outage 
yesterday that shut down the power for several hours. After the power came 
back, I have had no new data stored or displayed. Data during the power 
outage was recovered though. Syslog indicates that weewx was very busy 
after power was restored uploading the missing data to Wunderground, but 
once that was done, it stopped creating new data. Every 5 minutes, it 
creates a new report, but there is no new data in the database, no data 
upload to Wundergound and no change to the images used to create the report 
locally.

It is as if the Vantage Pro weather station has stopped working, but as far 
as I can tell, it is fine. I had the server in debug mode before this 
happened, so it seems like there should be a smoking gun in Syslog, but I 
don't see it. 

Any ideas on what I should try to get back up and running? See below for a 
Google drive link to the syslog file.  Thanks!

https://drive.google.com/file/d/1uRIm29J9T8Dv2tAg7M1G6P7fKmaXpaCy/view?usp=sharing

-- 
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/b74c92af-08ea-45ac-bdb3-1d40a4773700n%40googlegroups.com.

Re: [weewx-user] Moderation

[gjr80]

Actually I would not try posting the same reply repeatedly; what Google 
sees as spam now will still be seen as spam five minutes later. I have at 
times seen six, seven or even eight copies of the same post queued in the 
'Pending' folder. Just try once, or maybe twice and if nothing appears 
either wait (we will get to it eventually) or try rewording.

Gary

On Wednesday, 20 April 2022 at 07:27:25 UTC+10 jonfe...@googlemail.com 
wrote:

> Ok Thanks, Just try and try agin!
>
>

-- 
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/3c6d6484-63ef-4180-8552-605b4f839a60n%40googlegroups.com.

Re: [weewx-user] Publishing Issue

['John Kline' via weewx-user]

> Yeah, I can't figure out why WU updates every few seconds
WU has a rapid fire setting:
See:
https://weewx.com/docs/usersguide.htm#Wunderground
PWSweather has no such equivalent

> If I can figure out how to adjust the Vantage pro hardware setting…
See:
https://weewx.com/docs/hardware.htm#vantage_notes
wee_device --set-interval=MINUTES [config_file] [-y]


> On Apr 19, 2022, at 5:46 PM, Douglas Cote  wrote:
> 
> Yeah, I can't figure out why WU updates every few seconds, but PWS waits for 
> the archive every 30 mins. If the PWS update is specifically tied to the 
> hardware archive interval then that makes sense. I guess I didn't notice what 
> the hardware might have been set to when PWS was updating more frequently. If 
> I can figure out how to adjust the Vantage pro hardware setting that might 
> get things back to how they behaved previously. Thanks for all the assistance.
> 
>> On Sunday, April 17, 2022 at 10:12:58 PM UTC-4 jo...@johnkline.com wrote:
>> You must have been using a shorter archive interval when you observed more 
>> frequent PWS updates.  The updates happen, at most, every archive interval.  
>> There is an option to make them less frequent, by setting post_interval 
>> (see: https://weewx.com/docs/usersguide.htm#%5B%5BPWSweather%5D%5D).
>> 
 On Apr 17, 2022, at 6:56 PM, Douglas Cote  wrote:
 
>>> Previously, I was getting conditions posted to my PWSweather page every 
>>> minute or so. Now it only updates every 30 minutes, which appears to 
>>> coincide with the 30 minute archive interval. So, it's at least posting new 
>>> data to the site but not at the frequency I was expecting. The attached is 
>>> a filtered syslog showing the PWS publishing events today. I was going to 
>>> try changing the record_generation parameter to software to see if it makes 
>>> a difference. Thanks.
>> 
>>> 
>>> 
 On Sunday, April 17, 2022 at 6:31:20 PM UTC-4 tke...@gmail.com wrote:
 I'm not following. What is the odd behavior? That all sounds normal. 
 
> On Sun, Apr 17, 2022 at 11:31 AM Douglas Cote  wrote:
> Thanks very much. I got it to send updates to PWS but still seeing some 
> odd behavior. I think the 30 minute interval is the default in the VPro2 
> and have no need to change it. The other thing I noticed is the PWS 
> update will only send when archive processing runs. Thanks again.
> 
>> On Saturday, April 16, 2022 at 1:31:00 PM UTC-4 tke...@gmail.com wrote:
>> This is a good example of why it's so important to include the log.
>> 
>> Your problem is corrupted memory in your Vantage logger. It has nothing 
>> to do with PWSWeather. If you take a close look, you'll see that your 
>> HTML pages are not getting updated either. 
>> 
>> To fix, see the wiki section WeeWX generates HTML pages, but it does not 
>> update them.
>> 
>> Incidentally, your archive interval is 30 minutes. Did you want it that 
>> long?
>> 
>> -tk
>> 
>>> On Sat, Apr 16, 2022 at 9:32 AM Douglas Cote  wrote:
>>> Attached an updated log. The most recent start events are around 12:21 
>>> PM ET. I can see it reference posting to PWSweather but doesn't seem to 
>>> actually do it. Thanks.
>>> 
 On Saturday, April 16, 2022 at 10:37:28 AM UTC-4 tke...@gmail.com 
 wrote:
 Everything looks normal.
 
 How about a little more of the system log? Make sure debug=1, then 
 stop and restart weewxd. Wait until the first reporting cycle is 
 finished (usually 5 or 10 minutes), then post the log from startup. 
 
> On Sat, Apr 16, 2022 at 6:46 AM Douglas Cote  
> wrote:
> Thanks. I can't see where the issue is but I've attached debug output 
> and a bit of syslog. 
> 
>> On Thursday, April 14, 2022 at 6:39:38 AM UTC-4 tke...@gmail.com 
>> wrote:
>> Hard to debug without seeing the log. 
>> 
>> Most likely you have a configuration problem. Take a careful look at 
>> the [StdRESTful] section of weewx.conf. In particular, the 
>> [[PWSweather]] subsection. Is it enabled? Is the station and 
>> password correct? 
>> 
>> Also, make sure you have the number of brackets "[[..]]" correct. Is 
>> it running on into the next subsection?
>> 
>> -tk
>> 
>>> On Wed, Apr 13, 2022 at 7:44 PM Douglas Cote  
>>> wrote:
>>> After upgrading to weewx 4.7.0, it seems I can only publish to 
>>> Weather Underground whereas before I was publishing to PWSweather 
>>> as well. I thought maybe because I had tried to add OpenWeatherMap 
>>> as another publishing location it broke the PWS RESTful service. 
>>> When I commented out the user.owm.OpenWeatherMap RESTful service 
>>> definition and restarted weewx it was still refusing to publish to 
>>> PWS. I did

Re: [weewx-user] Publishing Issue

[Douglas Cote]

Yeah, I can't figure out why WU updates every few seconds, but PWS waits 
for the archive every 30 mins. If the PWS update is specifically tied to 
the hardware archive interval then that makes sense. I guess I didn't 
notice what the hardware might have been set to when PWS was updating more 
frequently. If I can figure out how to adjust the Vantage pro hardware 
setting that might get things back to how they behaved previously. Thanks 
for all the assistance.

On Sunday, April 17, 2022 at 10:12:58 PM UTC-4 jo...@johnkline.com wrote:

> You must have been using a shorter archive interval when you observed more 
> frequent PWS updates.  The updates happen, at most, every archive interval. 
>  There is an option to make them less frequent, by setting post_interval 
> (see: https://weewx.com/docs/usersguide.htm#%5B%5BPWSweather%5D%5D).
>
> On Apr 17, 2022, at 6:56 PM, Douglas Cote  wrote:
>
> Previously, I was getting conditions posted to my PWSweather page every 
> minute or so. Now it only updates every 30 minutes, which appears to 
> coincide with the 30 minute archive interval. So, it's at least posting new 
> data to the site but not at the frequency I was expecting. The attached is 
> a filtered syslog showing the PWS publishing events today. I was going to 
> try changing the record_generation parameter to software to see if it makes 
> a difference. Thanks.
>
>
>
> On Sunday, April 17, 2022 at 6:31:20 PM UTC-4 tke...@gmail.com wrote:
>
>> I'm not following. What is the odd behavior? That all sounds normal. 
>>
>> On Sun, Apr 17, 2022 at 11:31 AM Douglas Cote  wrote:
>>
>>> Thanks very much. I got it to send updates to PWS but still seeing some 
>>> odd behavior. I think the 30 minute interval is the default in the VPro2 
>>> and have no need to change it. The other thing I noticed is the PWS update 
>>> will only send when archive processing runs. Thanks again.
>>>
>>> On Saturday, April 16, 2022 at 1:31:00 PM UTC-4 tke...@gmail.com wrote:
>>>
 This is a good example of why it's so important to include the log.

 Your problem is corrupted memory in your Vantage logger. It has nothing 
 to do with PWSWeather. If you take a close look, you'll see that your HTML 
 pages are not getting updated either. 

 To fix, see the wiki section *WeeWX generates HTML pages, but it does 
 not update them 
 *
 .

 Incidentally, your archive interval is 30 minutes. Did you want it that 
 long?

 -tk

 On Sat, Apr 16, 2022 at 9:32 AM Douglas Cote  
 wrote:

> Attached an updated log. The most recent start events are around 12:21 
> PM ET. I can see it reference posting to PWSweather but doesn't seem to 
> actually do it. Thanks.
>
> On Saturday, April 16, 2022 at 10:37:28 AM UTC-4 tke...@gmail.com 
> wrote:
>
>> Everything looks normal.
>>
>> How about a little more of the system log? Make sure debug=1, then 
>> stop and restart weewxd. Wait until the first reporting cycle is 
>> finished 
>> (usually 5 or 10 minutes), then post the log from startup. 
>>
>> On Sat, Apr 16, 2022 at 6:46 AM Douglas Cote  
>> wrote:
>>
>>> Thanks. I can't see where the issue is but I've attached debug 
>>> output and a bit of syslog. 
>>>
>>> On Thursday, April 14, 2022 at 6:39:38 AM UTC-4 tke...@gmail.com 
>>> wrote:
>>>
 Hard to debug without seeing the log. 

 Most likely you have a configuration problem. Take a careful look 
 at the [StdRESTful] section of weewx.conf. In particular, the 
 [[PWSweather]] subsection. Is it enabled? Is the station and password 
 correct? 

 Also, make sure you have the number of brackets "[[..]]" correct. 
 Is it running on into the next subsection?

 -tk

 On Wed, Apr 13, 2022 at 7:44 PM Douglas Cote  
 wrote:

> After upgrading to weewx 4.7.0, it seems I can only publish to 
> Weather Underground whereas before I was publishing to PWSweather as 
> well. 
> I thought maybe because I had tried to add OpenWeatherMap as another 
> publishing location it broke the PWS RESTful service. When I 
> commented out 
> the user.owm.OpenWeatherMap RESTful service definition and restarted 
> weewx 
> it was still refusing to publish to PWS. I did have debug = 3 set for 
> a bit 
> but when looking at the output, weewx isn't even attempting to 
> publish to 
> PWSweather...it's ignoring it completely. Anyone see this behavior 
> before?
>
> Thanks,
> Doug
>
> -- 
> You received this message because you are subscribed to the Google 
> Group

[weewx-user] Re: wee_config --reconfigure returns UnicodeDecodeError: 'ascii' codec can't decode byte 0xff in position 0: ordinal not in range(128)

[kheller2]

It's also related to python2.   I installed 4.7 and most of the python3 
components on Centos7 forced installed the rpm for EL8.  Works good, and of 
course the config crashes if you use python2, but works with python3.   i 
will be building out a EL8 box soon.

On Tuesday, April 19, 2022 at 2:38:24 PM UTC-4 kheller2 wrote:

> Actually, the fix mentioned in #172 is not in my copy 
> of cheetahgenerator.py.  But even after adding it and recompiling it still 
> bombs out.
>
>
> On Monday, April 18, 2022 at 5:05:58 PM UTC-4 matthew wall wrote:
>
>> On Monday, April 18, 2022 at 11:11:59 AM UTC-4 kheller2 wrote:
>>
>>>   File "/usr/lib/python2.7/site-packages/configobj.py", line 1457, in 
>>> _handle_bom
>>> if not line.startswith(BOM):
>>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xff in position 0: 
>>> ordinal not in range(128)
>>>
>>
>> the first think i thought of was the BOM problem that was fixed in issue:
>>
>> https://github.com/weewx/weewx/issues/172
>>
>>

-- 
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/a9a76ccb-c89a-4783-a05f-2f13397c3da3n%40googlegroups.com.

Re: [weewx-user] Moderation

['Jon Fear' via weewx-user]

Ok Thanks, Just try and try agin!

On Tuesday, 19 April 2022 at 14:07:52 UTC+1 tke...@gmail.com wrote:

> No posts are moderated, but occasionally Google Groups will intern and 
> quarantine a post that it thinks looks suspicious. There is no way to turn 
> off this behavior. 
>
> All well and good, but it does not always tell the moderators that there 
> is something in quarantine, so a post can languish in purgatory for quite a 
> while.
>
> Wish I could do something about it, but that's the way it is!
>
>
>
>
> On Tue, Apr 19, 2022 at 6:04 AM 'Jon Fear' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> Hi
>>  
>> Are post to this group moderated or am I on probationary moderation? I am 
>> not seeing any of my posts regarding the new Wittboy and the potential 
>> driver here?
>>
>> Thanks
>>
>> Jon
>>
>> -- 
>> 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/25a9e50a-a651-4d6d-849a-70c6b2e64872n%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/422adf17-2f2e-44d1-8b31-2fb6ebb23437n%40googlegroups.com.

[weewx-user] Re: wee_config --reconfigure returns UnicodeDecodeError: 'ascii' codec can't decode byte 0xff in position 0: ordinal not in range(128)

[kheller2]

Actually, the fix mentioned in #172 is not in my copy 
of cheetahgenerator.py.  But even after adding it and recompiling it still 
bombs out.


On Monday, April 18, 2022 at 5:05:58 PM UTC-4 matthew wall wrote:

> On Monday, April 18, 2022 at 11:11:59 AM UTC-4 kheller2 wrote:
>
>>   File "/usr/lib/python2.7/site-packages/configobj.py", line 1457, in 
>> _handle_bom
>> if not line.startswith(BOM):
>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xff in position 0: 
>> ordinal not in range(128)
>>
>
> the first think i thought of was the BOM problem that was fixed in issue:
>
> https://github.com/weewx/weewx/issues/172
>
>

-- 
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/34b3bfbf-063b-40eb-8b6f-e7597d14c5cfn%40googlegroups.com.

[weewx-user] Re: WeeWx 4.7.0 and TE923 weather station running on a Pi4. Problem when restarting (sudo /etc/init.d/weewx restart or Pi reboot)

[Pierre-Yves]

Thanks Gary for feedback.
The config archive interval is correct.
[StdArchive]

# If the station hardware supports data logging then the archive 
interval
# will be downloaded from the station. Otherwise, specify it (in 
seconds).
archive_interval = 300

I don't where this '129' value come from
the weewx.conf is attached
PY

Le mardi 19 avril 2022 à 15:23:04 UTC+2, gary@gmail.com a écrit :

> You are going to need to post your weewx.conf, but the error says the 
> archive interval is 129, which is apparently not a supported value. Change 
> that to 300 (for 5 minutes) and see what transpires.
>
> Follow this link on how to post a help request:
> https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user
>
> On Tuesday, April 19, 2022 at 6:17:11 AM UTC-4 Pierre-Yves wrote:
>
>> Hello,
>>
>> After having made a small change to the weewx.conf (station website 
>> registration), I experienced problems for restarting, typing "sudo 
>> /etc/init.d/weewx restart". Same result when rebooting the PI4.
>> About 20 times, the restart failed with the following syslog messages :
>>
>> Apr 18 19:12:50 weewx weewx[2225] ERROR weewx.drivers.te923: Unrecognized 
>> archive interval '129'
>> Apr 18 19:12:50 weewx weewx[2225] INFO weewx.engine: Main loop exiting. 
>> Shutting engine down.
>> Apr 18 19:12:50 weewx weewx[2225] CRITICAL __main__: Caught WeeWxIOError: 
>> Unrecognized archive interval '129'
>> Apr 18 19:12:50 weewx weewx[2225] CRITICAL __main__:   Waiting 60 
>> seconds then retrying...
>>
>> Finally at 19:37:29, weewx restart succeeded and since works fine.
>>
>> I noticed also this syslog line :
>>
>> Apr 18 19:12:50 weewx weewx[2225] INFO weewx.drivers.te923: station time 
>> is 1650236400.0, computer time is 1650301970
>>
>> I do not understand why the station and computer timestamps are so 
>> different.
>>
>> Syslog is attached
>>
>> Any idea on what could cause that behavior ?
>>
>> Thanks a lot,
>>
>> Pierre-Yves
>
>

-- 
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/8a4f57c1-5e1d-4c10-a2cc-16bf5244bf45n%40googlegroups.com.
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2021 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 0

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 4.7.0

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = Roncière 91680 Courson-Monteloup

# Latitude in decimal degrees. Negative for southern hemisphere
latitude = 48.6001
# Longitude in decimal degrees. Negative for western hemisphere.
longitude = 2.1572

# Altitude of the station, with the unit it is in. This is used only
# if the hardware cannot supply a value.
altitude = 87, meter# Choose 'foot' or 'meter' for unit

# Set to type of station hardware. There must be a corresponding stanza
# in this file, which includes a value for the 'driver' option.
station_type = TE923

# If you have a website, you may specify an URL. This is required if you
# intend to register your station.
station_url = 
http://pybeauvais.free.fr/Meteo-Ronciere/belchertown/index.html

# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1

# Start of week (0=Monday, 6=Sunday)
week_start = 0

##

[TE923]
# This section is for the Hideki TE923 series of weather stations.

# The station model, e.g., 'Meade TE923W' or 'TFA Nexus'
model = IROX Pro X

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

[[sensor_map]]
outTemp = t_1
outHumidity = h_1
extraTemp1 = t_3
extraTemp2 = t_2

##

#   This section is for uploading data to Internet sites

[StdRESTful]

[[StationRegistry]]
# To register this weather station with weewx, set this to true,
# then fill

[weewx-user] Re: WeeWx 4.7.0 and TE923 weather station running on a Pi4. Problem when restarting (sudo /etc/init.d/weewx restart or Pi reboot)

[gary....@gmail.com]

You are going to need to post your weewx.conf, but the error says the 
archive interval is 129, which is apparently not a supported value. Change 
that to 300 (for 5 minutes) and see what transpires.

Follow this link on how to post a help request:
https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user

On Tuesday, April 19, 2022 at 6:17:11 AM UTC-4 Pierre-Yves wrote:

> Hello,
>
> After having made a small change to the weewx.conf (station website 
> registration), I experienced problems for restarting, typing "sudo 
> /etc/init.d/weewx restart". Same result when rebooting the PI4.
> About 20 times, the restart failed with the following syslog messages :
>
> Apr 18 19:12:50 weewx weewx[2225] ERROR weewx.drivers.te923: Unrecognized 
> archive interval '129'
> Apr 18 19:12:50 weewx weewx[2225] INFO weewx.engine: Main loop exiting. 
> Shutting engine down.
> Apr 18 19:12:50 weewx weewx[2225] CRITICAL __main__: Caught WeeWxIOError: 
> Unrecognized archive interval '129'
> Apr 18 19:12:50 weewx weewx[2225] CRITICAL __main__:   Waiting 60 
> seconds then retrying...
>
> Finally at 19:37:29, weewx restart succeeded and since works fine.
>
> I noticed also this syslog line :
>
> Apr 18 19:12:50 weewx weewx[2225] INFO weewx.drivers.te923: station time 
> is 1650236400.0, computer time is 1650301970
>
> I do not understand why the station and computer timestamps are so 
> different.
>
> Syslog is attached
>
> Any idea on what could cause that behavior ?
>
> Thanks a lot,
>
> Pierre-Yves

-- 
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/9537afa8-31be-4702-8d1c-f4cc2dda3c16n%40googlegroups.com.

Re: [weewx-user] Moderation

[Tom Keffer]

No posts are moderated, but occasionally Google Groups will intern and
quarantine a post that it thinks looks suspicious. There is no way to turn
off this behavior.

All well and good, but it does not always tell the moderators that there is
something in quarantine, so a post can languish in purgatory for quite a
while.

Wish I could do something about it, but that's the way it is!




On Tue, Apr 19, 2022 at 6:04 AM 'Jon Fear' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Hi
>
> Are post to this group moderated or am I on probationary moderation? I am
> not seeing any of my posts regarding the new Wittboy and the potential
> driver here?
>
> Thanks
>
> Jon
>
> --
> 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/25a9e50a-a651-4d6d-849a-70c6b2e64872n%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/CAPq0zECz6mV70w6jx-C7nCqpBLQ2jbw3PAgSyYrK2tEnD9%3D4PQ%40mail.gmail.com.

[weewx-user] Moderation

['Jon Fear' via weewx-user]

Hi
 
Are post to this group moderated or am I on probationary moderation? I am 
not seeing any of my posts regarding the new Wittboy and the potential 
driver here?

Thanks

Jon

-- 
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/25a9e50a-a651-4d6d-849a-70c6b2e64872n%40googlegroups.com.

Re: [weewx-user] Re: EcoWitt GW2000 - anyone working on a driver?

[Stephen Hocking]

When I compare the rainfall to other close by weather station on
wunderground, they've got 21mm to my 32mm.


On Tue, 19 Apr 2022 at 20:09, Stephen Hocking 
wrote:

> The phone app & web page is picking up the piezo rain just fine, but weewx
> doesn't seem to have any rain logged at all. I'm using the gw1000 driver -
> would using Werner's gw2000 pick this up? I'm assuming that I won't have to
> make another mod to weewx.conf beyond what installing the gw1000 has
> already done.
>
> [image: image.png]
>
> On Tue, 19 Apr 2022 at 16:17, Rainer Lang  wrote:
>
>> That's only a possibility if the GW2000 is the only console you have. If
>> your FOSHKplugin is already fed by another console ...
>> Want to install a second instance of FOSHKplugin ? Not trivial.
>> Also, the custom server doesn't provide you the same loop data which you
>> can get from the GW1000 driver.
>> But it's an alternative, if the GW2000 is the only console you have/use
>> with FOSHKplugin.
>>
>> Not sure why you were struggling, I use the GW1000 driver for a few weewx
>> instances and the interceptor for one - no issues which couldn't be solved
>> in a short time (and were usually due to a bad system setup or not knowing
>> your system (server) well enough).
>>
>> On 18.04.2022 21:54, Zsolt Máté wrote:
>>
>> Install FOSHKplugin and all your headaches are gone. I was struggling
>> with the drivers, interceptors, observers, whatnot, but ever since I've
>> installed it everything is back to normal.
>>
>> On Monday, April 18, 2022 at 4:41:05 AM UTC+12 xzei...@googlemail.com
>> wrote:
>>
>>> My modified driver from Gary (now named gw2000.py) supports the GW2000
>>> and GW1100 with Firmware V2.1.3 (piezo_rain)
>>> https://www.pc-wetterstation.de/weewx/gw2000.zip
>>> The piezo_gain_values are at the moment not supported.
>>> The hour piezo rain and hour rain aren't right, the pdf-docu isn't here
>>> correct, seems this values are gain factors
>>> I use the hail database value for  piezo rain (WS90)
>>> [[field_map_extensions]]
>>> rain_piezo = rain_piezo
>>> erain_piezo = erain_piezo
>>> rrain_piezo = rrain_piezo
>>> hrain_piezo = hrain_piezo
>>> drain_piezo = drain_piezo
>>> wrain_piezo = wrain_piezo
>>> mrain_piezo = mrain_piezo
>>> yrain_piezo = yrain_piezo
>>>
>>> hail = rain_piezo
>>> hailrate = rrain_piezo
>>> stephen...@gmail.com schrieb am Sonntag, 17. April 2022 um 06:46:23
>>> UTC+2:
>>>
 Hi Gary,

 I have abused my credit card and ordered a WH40 rainfall sensor (along
 with the AQ & lightning sensior), so that readings from both it & the piezo
 sensor can be compared. Will let you know when it turns up and is 
 installed.

 On Sun, 17 Apr 2022 at 13:52, Stephen Hocking 
 wrote:

> Hi Gary,
>
> I've just set up weewx with the gw1000 driver, and it appears to have
> picked up the gw2000 just fine - I'm getting observations coming in. I'm
> reassured, as a recent git pull of the rtl_433 code doesn't decode 
> anything
> from the sensors at all, and while going down that rabbit hole of banging
> on the code would be entertaining, I'm pretty sure that more talented 
> minds
> than mine are already on it.
>
> I currently have the WittBoy (with the aforementioned piezo rain
> detector) only at the moment, although I'm planning on ordering the indoor
> & outdoor air quality sensors, as well as the lightning one. This thing
> seems to be head & shoulders over the AcuRite Atlas I was using with the
> SDR driver (plus scraping pressure off the webpage on the Atlas hub).
>
> Please let me know if I can test any code for you.
>
> On Sun, 17 Apr 2022 at 11:05, gjr80  wrote:
>
>> The current GW1000 driver will speak to a GW2000 and should return
>> all obs except for WS90 rain and WS90 signal/battery states. I am working
>> on the v0.5.0 driver but the behaviour of the GW2000 API with various
>> combinations of the 'traditional' and 'piezo' rain gauges (Ecowitt's 
>> terms)
>> is not very clearly defined. I will likely need some assistance from 
>> GW2000
>> users with various rain gauge combinations to tie this down. WS90 signal
>> and battery states are already working in the v0.5.0 driver.
>>
>> Not sure how long the piece of string is.
>>
>> Gary
>> On Sunday, 17 April 2022 at 02:08:31 UTC+10 vince wrote:
>>
>>> A little searching here seems to indicate the gw1000 driver should
>>> possibly work for you.  Give it a try
>>>
>>> On Friday, April 15, 2022 at 11:10:06 PM UTC-7 stephen...@gmail.com
>>> wrote:
>>>
 From the web page the device serves up, it appears you can tell it
 to upload data  in ecowitt or wunderground format to your own 
 server/port.


 [image: image.png]
 --

   "I and t

Re: [weewx-user] Re: EcoWitt GW2000 - anyone working on a driver?

[Stephen Hocking]

The phone app & web page is picking up the piezo rain just fine, but weewx
doesn't seem to have any rain logged at all. I'm using the gw1000 driver -
would using Werner's gw2000 pick this up? I'm assuming that I won't have to
make another mod to weewx.conf beyond what installing the gw1000 has
already done.

[image: image.png]

On Tue, 19 Apr 2022 at 16:17, Rainer Lang  wrote:

> That's only a possibility if the GW2000 is the only console you have. If
> your FOSHKplugin is already fed by another console ...
> Want to install a second instance of FOSHKplugin ? Not trivial.
> Also, the custom server doesn't provide you the same loop data which you
> can get from the GW1000 driver.
> But it's an alternative, if the GW2000 is the only console you have/use
> with FOSHKplugin.
>
> Not sure why you were struggling, I use the GW1000 driver for a few weewx
> instances and the interceptor for one - no issues which couldn't be solved
> in a short time (and were usually due to a bad system setup or not knowing
> your system (server) well enough).
>
> On 18.04.2022 21:54, Zsolt Máté wrote:
>
> Install FOSHKplugin and all your headaches are gone. I was struggling with
> the drivers, interceptors, observers, whatnot, but ever since I've
> installed it everything is back to normal.
>
> On Monday, April 18, 2022 at 4:41:05 AM UTC+12 xzei...@googlemail.com
> wrote:
>
>> My modified driver from Gary (now named gw2000.py) supports the GW2000
>> and GW1100 with Firmware V2.1.3 (piezo_rain)
>> https://www.pc-wetterstation.de/weewx/gw2000.zip
>> The piezo_gain_values are at the moment not supported.
>> The hour piezo rain and hour rain aren't right, the pdf-docu isn't here
>> correct, seems this values are gain factors
>> I use the hail database value for  piezo rain (WS90)
>> [[field_map_extensions]]
>> rain_piezo = rain_piezo
>> erain_piezo = erain_piezo
>> rrain_piezo = rrain_piezo
>> hrain_piezo = hrain_piezo
>> drain_piezo = drain_piezo
>> wrain_piezo = wrain_piezo
>> mrain_piezo = mrain_piezo
>> yrain_piezo = yrain_piezo
>>
>> hail = rain_piezo
>> hailrate = rrain_piezo
>> stephen...@gmail.com schrieb am Sonntag, 17. April 2022 um 06:46:23
>> UTC+2:
>>
>>> Hi Gary,
>>>
>>> I have abused my credit card and ordered a WH40 rainfall sensor (along
>>> with the AQ & lightning sensior), so that readings from both it & the piezo
>>> sensor can be compared. Will let you know when it turns up and is installed.
>>>
>>> On Sun, 17 Apr 2022 at 13:52, Stephen Hocking 
>>> wrote:
>>>
 Hi Gary,

 I've just set up weewx with the gw1000 driver, and it appears to have
 picked up the gw2000 just fine - I'm getting observations coming in. I'm
 reassured, as a recent git pull of the rtl_433 code doesn't decode anything
 from the sensors at all, and while going down that rabbit hole of banging
 on the code would be entertaining, I'm pretty sure that more talented minds
 than mine are already on it.

 I currently have the WittBoy (with the aforementioned piezo rain
 detector) only at the moment, although I'm planning on ordering the indoor
 & outdoor air quality sensors, as well as the lightning one. This thing
 seems to be head & shoulders over the AcuRite Atlas I was using with the
 SDR driver (plus scraping pressure off the webpage on the Atlas hub).

 Please let me know if I can test any code for you.

 On Sun, 17 Apr 2022 at 11:05, gjr80  wrote:

> The current GW1000 driver will speak to a GW2000 and should return all
> obs except for WS90 rain and WS90 signal/battery states. I am working on
> the v0.5.0 driver but the behaviour of the GW2000 API with various
> combinations of the 'traditional' and 'piezo' rain gauges (Ecowitt's 
> terms)
> is not very clearly defined. I will likely need some assistance from 
> GW2000
> users with various rain gauge combinations to tie this down. WS90 signal
> and battery states are already working in the v0.5.0 driver.
>
> Not sure how long the piece of string is.
>
> Gary
> On Sunday, 17 April 2022 at 02:08:31 UTC+10 vince wrote:
>
>> A little searching here seems to indicate the gw1000 driver should
>> possibly work for you.  Give it a try
>>
>> On Friday, April 15, 2022 at 11:10:06 PM UTC-7 stephen...@gmail.com
>> wrote:
>>
>>> From the web page the device serves up, it appears you can tell it
>>> to upload data  in ecowitt or wunderground format to your own 
>>> server/port.
>>>
>>>
>>> [image: image.png]
>>> --
>>>
>>>   "I and the public know
>>>   what all schoolchildren learn
>>>   Those to whom evil is done
>>>   Do evil in return"W.H. Auden, "September 1, 1939"
>>>
>>>
>>> --
> You received this message because you are subscribed to the Google
> Groups "weewx-user" group.
> T

[weewx-user] Rainfall rate simulators

[Stephen Hocking]

Hi all,

Does anyone know of a device that given the appropriate amount of water,
can shower what lies below at known rain rates? The piezo rainfall sensor
on the WittBoy has what looks like a 5-band graphic equaliser, where at
differing bands of rain rates, you can multiply the rate by a
constant factor.

-- 

  "I and the public know
  what all schoolchildren learn
  Those to whom evil is done
  Do evil in return"W.H. Auden, "September 1, 1939"

-- 
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/CA%2BxzKjDG1T%2BZg8TyaxRT6xuJxSbLgAbcxRu4CD27WPDtnR6hoQ%40mail.gmail.com.

[weewx-user] WeeWx 4.7.0 and TE923 weather station running on a Pi4. Problem when restarting (sudo /etc/init.d/weewx restart or Pi reboot)

[Pierre-Yves]

Hello,

After having made a small change to the weewx.conf (station website 
registration), I experienced problems for restarting, typing "sudo 
/etc/init.d/weewx restart". Same result when rebooting the PI4.
About 20 times, the restart failed with the following syslog messages :

Apr 18 19:12:50 weewx weewx[2225] ERROR weewx.drivers.te923: Unrecognized 
archive interval '129'
Apr 18 19:12:50 weewx weewx[2225] INFO weewx.engine: Main loop exiting. 
Shutting engine down.
Apr 18 19:12:50 weewx weewx[2225] CRITICAL __main__: Caught WeeWxIOError: 
Unrecognized archive interval '129'
Apr 18 19:12:50 weewx weewx[2225] CRITICAL __main__:   Waiting 60 
seconds then retrying...

Finally at 19:37:29, weewx restart succeeded and since works fine.

I noticed also this syslog line :

Apr 18 19:12:50 weewx weewx[2225] INFO weewx.drivers.te923: station time is 
1650236400.0, computer time is 1650301970

I do not understand why the station and computer timestamps are so 
different.

Syslog is attached

Any idea on what could cause that behavior ?

Thanks a lot,

Pierre-Yves

-- 
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/4fa76929-7611-408a-acd3-b967cf810b29n%40googlegroups.com.
pi@weewx:~ $ tail -f /var/log/syslog

"Normal operation..."

Apr 18 19:05:16 weewx weewx[635] INFO weewx.manager: Added record 2022-04-18 
19:05:00 CEST (1650301500) to database 'weewx.sdb'
Apr 18 19:05:16 weewx weewx[635] INFO weewx.manager: Added record 2022-04-18 
19:05:00 CEST (1650301500) to daily summary in 'weewx.sdb'
Apr 18 19:05:19 weewx weewx[635] INFO weewx.cheetahgenerator: Generated 8 files 
for report SeasonsReport in 2.31 seconds
Apr 18 19:05:21 weewx weewx[635] INFO weewx.imagegenerator: Generated 28 images 
for report SeasonsReport in 2.45 seconds
Apr 18 19:05:21 weewx weewx[635] INFO weewx.reportengine: Copied 5 files to 
/var/www/html/weewx
Apr 18 19:05:21 weewx weewx[635] INFO weewx.cheetahgenerator: Generated 6 files 
for report SmartphoneReport in 0.20 seconds
Apr 18 19:05:22 weewx weewx[635] INFO weewx.imagegenerator: Generated 12 images 
for report SmartphoneReport in 0.78 seconds
Apr 18 19:05:22 weewx weewx[635] INFO weewx.reportengine: Copied 6 files to 
/var/www/html/weewx/smartphone
Apr 18 19:05:22 weewx weewx[635] INFO weewx.cheetahgenerator: Generated 1 files 
for report MobileReport in 0.07 seconds
Apr 18 19:05:22 weewx weewx[635] INFO weewx.imagegenerator: Generated 4 images 
for report MobileReport in 0.15 seconds
Apr 18 19:05:22 weewx weewx[635] INFO weewx.reportengine: Copied 2 files to 
/var/www/html/weewx/mobile
Apr 18 19:05:23 weewx weewx[635] INFO user.belchertown: version 1.2
Apr 18 19:05:28 weewx weewx[635] INFO weewx.cheetahgenerator: Generated 11 
files for report Belchertown in 5.61 seconds
Apr 18 19:05:28 weewx weewx[635] INFO weewx.reportengine: Copied 37 files to 
/var/www/html/weewx/belchertown
Apr 18 19:06:27 weewx weewx[635] INFO weewx.reportengine: ftpgenerator: Ftp'd 
82 files in 5.43 seconds

Apr 18 19:10:21 weewx weewx[635] INFO weewx.manager: Added record 2022-04-18 
19:10:00 CEST (1650301800) to database 'weewx.sdb'
Apr 18 19:10:21 weewx weewx[635] INFO weewx.manager: Added record 2022-04-18 
19:10:00 CEST (1650301800) to daily summary in 'weewx.sdb'
Apr 18 19:10:21 weewx weewx[635] INFO weewx.restx: AWEKAS: Published record 
2022-04-18 19:10:00 CEST (1650301800)
Apr 18 19:10:22 weewx weewx[635] INFO weewx.cheetahgenerator: Generated 7 files 
for report SeasonsReport in 1.30 seconds
Apr 18 19:10:23 weewx weewx[635] INFO weewx.imagegenerator: Generated 14 images 
for report SeasonsReport in 0.64 seconds
Apr 18 19:10:23 weewx weewx[635] INFO weewx.reportengine: Copied 0 files to 
/var/www/html/weewx
Apr 18 19:10:23 weewx weewx[635] INFO weewx.cheetahgenerator: Generated 6 files 
for report SmartphoneReport in 0.07 seconds
Apr 18 19:10:23 weewx weewx[635] INFO weewx.imagegenerator: Generated 6 images 
for report SmartphoneReport in 0.20 seconds
Apr 18 19:10:23 weewx weewx[635] INFO weewx.reportengine: Copied 0 files to 
/var/www/html/weewx/smartphone
Apr 18 19:10:23 weewx weewx[635] INFO weewx.cheetahgenerator: Generated 1 files 
for report MobileReport in 0.03 seconds
Apr 18 19:10:23 weewx weewx[635] INFO weewx.imagegenerator: Generated 4 images 
for report MobileReport in 0.15 seconds
Apr 18 19:10:23 weewx weewx[635] INFO weewx.reportengine: Copied 0 files to 
/var/www/html/weewx/mobile
Apr 18 19:10:26 weewx weewx[635] INFO weewx.cheetahgenerator: Generated 11 
files for report Belchertown in 2.73 seconds
Apr 18 19:10:26 weewx weewx[635] INFO weewx.reportengine: Copied 2 files to 
/var/www/html/weewx/belchertown
Apr 18 19:11:22 weewx weewx[635] INFO weewx.reportengine: ftpgenerator: Ftp'd 
56 files in 3.78 seconds

"Restarting

Re: [weewx-user] Weewx service stops randomly

[Graham Eddy]

you will probably get a lot more info from /var/log/syslog than 
/var/log/messages

> On 19 Apr 2022, at 2:12 pm, mup...@gmail.com  wrote:
> 
> I'm running weewx 4.5.1 with a Belchertown skin on a Raspberry pi. All was 
> working fine, but recently the service randomly stops. There is nothing in 
> the /var/log/messages other than normal reports.

-- 
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/56182BEC-D8F9-46A1-B27B-C14230F43373%40geddy.au.