Only getting pywws.weatherstation:live_data missed

[runge....@googlemail.com]

Hi,

i have a big problem since today morning, my live log only returns:

2024-08-18 20:07:04:pywws.weatherstation:live_data missed

all the time.

The base station shows the data just fine on the display, what i recognized is that the memory seems to be empty. See attached picture.

Checking the station with sudo pywws-testweatherstation also returns data:

22:58:04:pywws.logger:pywws version 24.2.0, build 1709 (8444adb)
0000 55 aa 01 81 a7 df 15 01 01 12 00 15 01 01 12 00 05 20 02 20 09 00 00 00 00 00 00 01 00 00 00 01
0020 94 27 a7 26 00 00 00 00 00 00 02 15 01 01 12 00 41 23 c8 00 00 00 46 2d 2c 01 64 80 c8 00 00 00
0040 64 00 64 80 a0 28 80 25 a0 28 80 25 00 b4 00 00 68 01 00 0a 00 f4 01 12 00 c0 c6 2d 0a 02 0e 98
0060 03 00 4b 41 56 46 f6 00 e7 00 d6 00 a2 00 d6 00 a2 00 b1 00 83 00 a2 26 73 26 96 27 93 27 1f 00
0080 47 00 40 00 00 a4 80 28 80 05 02 40 00 35 01 3b 12 0f 15 00 01 92 06 35 09 01 12 00 15 01 01 1a
00a0 01 15 01 01 12 02 1d 05 01 16 56 17 01 49 12 5d bd 03 11 12 04 35 41 11 12 18 15 01 01 92 04 15
00c0 01 01 9a 1c 15 01 05 37 03 35 25 01 13 02 14 03 01 1a 03 15 41 09 12 01 15 01 01 12 22 55 11 61
00e0 12 8c 15 03 29 12 71 15 11 01 32 00 75 09 23 14 00 15 07 01 12 84 17 03 41 12 00 15 03 01 12 62

And data looks fine checking with sudo pywws-testweatherstation -d.

Also the data is changing when doing pywws-testweatherstation -d.

I restarted my raspberry, updated pywws to the latest version and also tried one older version.

Nothing helped.

Anyone has had such an error before?

Any Ideas? Some internal battery of the base station?

Or a USB issue?

Here is a part of the livelog:

2024-08-18 20:00:42:pywws.logger:pywws version 24.2.0, build 1709 (8444adb)
2024-08-18 20:00:42:pywws.logger:Python version 3.9.2 (default, Feb 28 2021, 17:03:44)
[GCC 10.2.1 20210110]
2024-08-18 20:00:42:pywws.weatherstation:using pywws.device_pyusb1
2024-08-18 20:00:44:pywws.calib:Using user calibration
2024-08-18 20:00:45:pywws.logdata:Synchronising to weather station
2024-08-18 20:01:17:pywws.weatherstation:status {'lost_connection': False, 'rain_overflow': False}
2024-08-18 20:01:27:pywws.weatherstation:live_data missed
2024-08-18 20:02:15:pywws.weatherstation:live_data missed
2024-08-18 20:03:04:pywws.weatherstation:live_data missed
2024-08-18 20:03:51:pywws.weatherstation:live_data missed
2024-08-18 20:04:06:pywws.weatherstation:live_data log extended
2024-08-18 20:04:39:pywws.weatherstation:live_data missed
2024-08-18 20:05:06:pywws.weatherstation:live_data log extended
2024-08-18 20:05:27:pywws.weatherstation:live_data missed
2024-08-18 20:06:13:pywws.weatherstation:live_data log extended
2024-08-18 20:06:15:pywws.weatherstation:live_data missed
2024-08-18 20:07:04:pywws.weatherstation:live_data missed
2024-08-18 20:07:06:pywws.weatherstation:live_data log extended

Thanks and best regards,

Stefan

[runge....@googlemail.com]

As far as i can see my base station stopped logging data.

Is there any way to fix it?

What is a good replacement today for my wetherstation?

Any recommendations?

Thanks and best regards,

Stefan

[Jim Easterbrook]

'pywws-testweatherstation -d' shows the "fixed block" data, which should
not change very much. Try 'pywws-testweatherstation -d -h 5' or
'pywws-testweatherstation -d -l' to see the actual weather data that
should be changing.

> I restarted my raspberry, updated pywws to the latest version and also
> tried one older version.
> Nothing helped.
> Anyone has had such an error before?
> Any Ideas? Some internal battery of the base station?

Try resetting the base station. I suspect it's not writing data to the
correct part of its memory.

--
Jim Easterbrook <http://www.jim-easterbrook.me.uk/>

[Jim Easterbrook]

On 19/08/2024 10:34, 'runge....@googlemail.com' via pywws wrote:
>
> thanks for your answer.
> Sure i resetted the station.
> The memory icon on the base station seems not to fill.
>
> Executing the command pywws-testweatherstation -d -l returns data (but
> also has 11:21:34:pywws.weatherstation:invalid ptr value 000114):

This looks like a broken weather station. All I can suggest is to keep
resetting it until it starts behaving properly. Taking the batteries out
for longer (e.g. 5 minutes) might help.

[runge....@googlemail.com]

Hi Jim,

i do not even have batteries in at the moment.
Just powering by USB.

Taking batteries out you mean the batteries of the base station, right?
The base station seems to receive data just fine the displayed data looks right and it is changing.

But it seems not to write to memory.

I resettet the base station yesterday and today a lot and it did not change the behavior.
Also had the station unplugged for longer than 5 minutes.

So i think the base stations memory is perhaps broken?

It is always the same message when i execute  pywws-testweatherstation -d -l:
11:44:41:pywws.weatherstation:invalid ptr value 000114
11:44:42:pywws.weatherstation:status {'lost_connection': False, 'rain_overflow': False}
11:45:10:pywws.weatherstation:setting sensor clock 22.2699
0114 09:45:10 {'delay': 1, 'hum_in': 64, 'temp_in': 22.8, 'hum_out': 51, 'temp_out': 23.3, 'abs_pressure': 993.1, 'wind_ave': 0, 'wind_gust': 0, 'wind_dir': 4, 'rain': 28.5, 'status': {'lost_connection': False, 'rain_overflow': False}}
11:49:55:pywws.weatherstation:station is not logging data
11:50:01:pywws.weatherstation:station is not logging data

What is this pywws.weatherstation:invalid ptr value 000114?

Any suggestion for a new station?

Thanks and best regards,
Stefan

[Jim Easterbrook]

On 19/08/2024 10:50, 'runge....@googlemail.com' via pywws wrote:
>
> i do not even have batteries in at the moment.
> Just powering by USB.
>
> Taking batteries out you mean the batteries of the base station, right?

Removing batteries and unplugging USB, i.e. switching off all power to
the base station.

> The base station seems to receive data just fine the displayed data
> looks right and it is changing.
>
> But it seems not to write to memory.

Yes, or it keeps writing it to the same, wrong, address.

> I resettet the base station yesterday and today a lot and it did not
> change the behavior.
> Also had the station unplugged for longer than 5 minutes.
>
> So i think the base stations memory is perhaps broken?

It's probably worth trying again.

> Any suggestion for a new station?

I think the only ones currently made that are compatible with pywws have
all the external sensors integrated into one unit. I like to have my
wind sensors high up, temperature sensor in a screen, and rain sensor
clear of obstructions such as trees.

[richar...@gmail.com]

Hello,

I've had the base station fail before (for me it was the pressure sensor which just stopped working), I found this supplier which provides replacement parts for pywws compatible stations. From the picture you provided it appears you  have a station which has a solar sensor, so I think this console should work: https://greenfrogscientific.co.uk/replacement-console-for-aercus-instruments-ws3083-ws3085/

[runge....@googlemail.com]

Thanks for the link, i will check.

But since my station is +10 years old and all parts seems to have aged i would prefer to by a completely new station with outside sensors.

My station is mounted in the garden free from any trees or other things on a 3 meter pole.

So combined sensors do not really matter for me.

I now also tried resetting the station with pressing the arrow up button for 30 seconds and i cleared the memory by pressing history and when in history enter. CLR is displayed besides the memory indicator. Pressing enter now for 5 seconds deletes the memory.

But until now i also just see one entry written to history. 

It seems the station is not able to write to history anymore.

Perhaps + 10 years of usage did break the eeprom?

Thanks for all you help all the time and the great software. 

Let's see if my new station will also support pywws.

I would prefer it a lot to have the data locally, but it seems newer stations just work with the cloud.

I will update if there are any news or i got it working again.

Best regards,

Stefan

[Jim Easterbrook]

On 19/08/2024 13:28, richar...@gmail.com wrote:
>
> From the picture you
> provided it appears you  have a station which has a solar sensor, so I
> think this console should work:

Ah, I didn't see the picture (on email from Google Groups). For a solar
station 0x0114 (276) is not an invalid pointer, it's the next one after
0x0100 (256) which is where the readings store begins.

Try leaving 'pywws-testweatherstation -d -l' running for half an hour or
more. Check the values are sensible and that the "delay" value
increments every minute or so.

My weather station is rather old and needs its "fixed block" values
correcting after a reset. The 'pywws-setweatherstation' command has a
'-d' option to set sensible defaults (and clear the alarms mine sets
itself) and the '-r' option allows you to reset the read period.

[richar...@gmail.com]

Fair enough on possibly wanting to purchase a new system, the same supplier also sells complete systems: https://greenfrogscientific.co.uk/aercus-instruments-ws3085-wireless-weather-station/

That system uses the same base station as the previous link I sent, I use the same base station with pywws and have had no issues.

[Jim Easterbrook]

On 19/08/2024 17:44, richar...@gmail.com wrote:
> Fair enough on possibly wanting to purchase a new system, the same
> supplier also sells complete systems:
> https://greenfrogscientific.co.uk/aercus-instruments-ws3085-wireless-weather-station/

"This device is not recommended for 24/7 connection to a computer for
live weather reading." - at least they know about the USB lockup problem!

[runge....@googlemail.com]

Hi,

thanks for all the help and links.

My base station is now running for over 3 hours but when i press history only 1 value is stored in the history of the base station. 

I think it is the root cause for my problem that the memory is broken, not writable?

if i call pywws-testweatherstation -d -l, i just get this information, no delay values are printed.

pywws-testweatherstation -d -l
19:36:06:pywws.logger:pywws version 24.2.0, build 1709 (8444adb)
{'abs_pressure': 992.5,
 'alarm': {'abs_pressure': {'hi': 1040, 'lo': 960},
           'dewpoint': {'hi': 10, 'lo': -10},
           'hum_in': {'hi': 65, 'lo': 35},
           'hum_out': {'hi': 70, 'lo': 45},
           'illuminance': 300000,
           'rain': {'day': 150, 'hour': 3},
           'rel_pressure': {'hi': 1040, 'lo': 960},
           'temp_in': {'hi': 20, 'lo': 0},
           'temp_out': {'hi': 30, 'lo': -10},
           'time': '12:00',
           'uv': 10,
           'wind_ave': {'bft': 0, 'ms': 18},
           'wind_dir': 0,
           'wind_gust': {'bft': 0, 'ms': 10.4},
           'windchill': {'hi': 20, 'lo': 0}},
 'alarm_1': {'bit0': False,
             'bit3': False,
             'hum_in_hi': False,
             'hum_in_lo': False,
             'hum_out_hi': False,
             'hum_out_lo': False,
             'time': False,
             'wind_dir': False},
 'alarm_2': {'pressure_abs_hi': False,
             'pressure_abs_lo': False,
             'pressure_rel_hi': False,
             'pressure_rel_lo': False,
             'rain_day': False,
             'rain_hour': False,
             'wind_ave': False,
             'wind_gust': False},
 'alarm_3': {'dew_point_hi': False,
             'dew_point_lo': False,
             'temp_in_hi': False,
             'temp_in_lo': False,
             'temp_out_hi': False,
             'temp_out_lo': False,
             'wind_chill_hi': False,
             'wind_chill_lo': False},
 'current_pos': 256,
 'data_changed': 0,
 'data_count': 1,
 'date_time': '2015-01-01 12:09:00',
 'display_1': {'alarm_time': False,
               'clock_12hr': False,
               'date_mdy': False,
               'pressure_rel': False,
               'show_day_name': False,
               'show_year': True,
               'time_scale_24': False,
               'wind_gust': False},
 'display_2': {'rain_day': False,
               'rain_hour': True,
               'rain_month': False,
               'rain_total': False,
               'rain_week': False,
               'temp_out_chill': False,
               'temp_out_dew': False,
               'temp_out_temp': True},
 'display_3': {'alarm_illuminance_hi': False,
               'alarm_uv_hi': False,
               'bit3': False,
               'bit4': False,
               'bit6': False,
               'bit7': False,
               'illuminance_fc': False,
               'illuminance_wm2': False},
 'lux_wm2_coeff': 0,
 'magic_0': 85,
 'magic_1': 170,
 'max': {'abs_pressure': {'date': '2035-01-01 13:00:00', 'val': 992.5},
         'dewpoint': {'date': '2024-08-19 19:26:00', 'val': 11.4},
         'hum_in': {'date': '2015-01-01 12:10:00', 'val': 65},
         'hum_out': {'date': '2024-08-19 19:31:00', 'val': 41},
         'illuminance': {'date': '2015-01-01 12:00:00', 'val': 92135.2},
         'rain': {'day': {'date': '2055-09-23 16:00:00', 'val': 0.6},
                  'hour': {'date': None, 'val': 19.2},
                  'month': {'date': None, 'val': 115.2},
                  'total': {'date': '2015-01-01 12:20:00', 'val': 4915.8},
                  'week': {'date': None, 'val': 307.2}},
         'rel_pressure': {'date': None, 'val': 1013.2},
         'temp_in': {'date': '2024-08-19 17:23:00', 'val': 25.5},
         'temp_out': {'date': None, 'val': 25.6},
         'uv': {'date': '2015-01-01 12:00:00', 'val': 4},
         'wind_ave': {'date': '2064-08-19 17:21:00', 'val': 1.7},
         'wind_gust': {'date': '2024-10-19 17:13:00', 'val': 4.1},
         'windchill': {'date': '2035-01-11 12:19:00', 'val': 25.6}},
 'min': {'abs_pressure': {'date': '2015-03-01 12:03:00', 'val': 992.5},
         'dewpoint': {'date': None, 'val': 11.4},
         'hum_in': {'date': None, 'val': 64},
         'hum_out': {'date': '2015-01-01 20:00:00', 'val': 41},
         'rel_pressure': {'date': '2015-03-01 12:20:00', 'val': 1013.2},
         'temp_in': {'date': '2023-05-01 16:09:00', 'val': 25.1},
         'temp_out': {'date': '2032-10-19 19:33:00', 'val': 25.6},
         'windchill': {'date': None, 'val': 25.6}},
 'rain_factor_raw': 33025,
 'read_period': 5,
 'rel_pressure': 1013.2,
 'settings_1': {'bit3': False,
                'bit4': False,
                'pressure_hPa': True,
                'pressure_inHg': False,
                'pressure_mmHg': False,
                'rain_in': False,
                'temp_in_F': False,
                'temp_out_F': False},
 'settings_2': {'bit5': False,
                'bit6': False,
                'bit7': False,
                'wind_bft': False,
                'wind_kmph': True,
                'wind_knot': False,
                'wind_mph': False,
                'wind_mps': False},
 'timezone': 0,
 'unknown_01': 0,
 'unknown_18': 0,
 'wind_factor_raw': 57255}
min -> temp_out -> {'val': 25.6, 'date': '2032-10-19 19:33:00'}
alarm -> hum_out -> {'hi': 70, 'lo': 45}
rel_pressure -> 1013.2
abs_pressure -> 992.5
19:36:09:pywws.weatherstation:status {'lost_connection': False, 'rain_overflow':                                                                                                                                                                             False}
19:36:09:pywws.weatherstation:station is not logging data
19:36:10:pywws.weatherstation:station is not logging data
19:36:10:pywws.weatherstation:station is not logging data
19:36:11:pywws.weatherstation:station is not logging data
19:36:12:pywws.weatherstation:station is not logging data
19:36:13:pywws.weatherstation:station is not logging data
19:36:13:pywws.weatherstation:station is not logging data
19:36:14:pywws.weatherstation:station is not logging data
19:36:15:pywws.weatherstation:station is not logging data
19:36:15:pywws.weatherstation:station is not logging data
19:36:16:pywws.weatherstation:station is not logging data
19:36:17:pywws.weatherstation:station is not logging data
19:36:18:pywws.weatherstation:station is not logging data
19:36:18:pywws.weatherstation:station is not logging data
19:36:19:pywws.weatherstation:station is not logging data
19:36:20:pywws.weatherstation:station is not logging data
19:36:20:pywws.weatherstation:station is not logging data
19:36:21:pywws.weatherstation:station is not logging data
19:36:22:pywws.weatherstation:station is not logging data
19:36:23:pywws.weatherstation:station is not logging data
19:36:23:pywws.weatherstation:station is not logging data
19:36:24:pywws.weatherstation:station is not logging data
19:36:25:pywws.weatherstation:station is not logging data
19:36:25:pywws.weatherstation:station is not logging data
19:36:26:pywws.weatherstation:station is not logging data
19:36:27:pywws.weatherstation:station is not logging data
19:36:27:pywws.weatherstation:station is not logging data
19:36:28:pywws.weatherstation:station is not logging data
19:36:29:pywws.weatherstation:station is not logging data
19:36:30:pywws.weatherstation:station is not logging data
19:36:30:pywws.weatherstation:station is not logging data
19:36:31:pywws.weatherstation:station is not logging data
19:36:32:pywws.weatherstation:station is not logging data
19:36:32:pywws.weatherstation:station is not logging data
19:36:33:pywws.weatherstation:station is not logging data
19:36:34:pywws.weatherstation:station is not logging data
19:36:35:pywws.weatherstation:station is not logging data
19:36:35:pywws.weatherstation:station is not logging data

[runge....@googlemail.com]

Ok, now i got one line with data but the timestamp is old:

19:49:53:pywws.weatherstation:status {'lost_connection': False, 'rain_overflow': False}
19:49:53:pywws.weatherstation:station is not logging data
19:49:54:pywws.weatherstation:station is not logging data
19:49:54:pywws.weatherstation:station is not logging data
19:49:55:pywws.weatherstation:station is not logging data
19:49:56:pywws.weatherstation:station is not logging data
19:49:56:pywws.weatherstation:station is not logging data
19:49:57:pywws.weatherstation:setting sensor clock 21.7364
0100 17:49:57 {'delay': 1, 'hum_in': 67, 'temp_in': 24.8, 'hum_out': 70, 'temp_out': 20.5, 'abs_pressure': 991.6, 'wind_ave': 0, 'wind_gust': 0.3, 'wind_dir': 14, 'rain': 28.5, 'status': {'lost_connection': False, 'rain_overflow': False}}
19:49:57:pywws.weatherstation:station is not logging data
19:50:42:pywws.weatherstation:station is not logging data
19:50:48:pywws.weatherstation:station is not logging data
19:50:49:pywws.weatherstation:station is not logging data
19:50:50:pywws.weatherstation:station is not logging data
19:50:51:pywws.weatherstation:station is not logging data
19:50:51:pywws.weatherstation:station is not logging data
19:51:30:pywws.weatherstation:station is not logging data
19:51:36:pywws.weatherstation:station is not logging data
19:51:37:pywws.weatherstation:station is not logging data
19:51:38:pywws.weatherstation:station is not logging data
19:51:39:pywws.weatherstation:station is not logging data
19:51:39:pywws.weatherstation:station is not logging data
19:52:18:pywws.weatherstation:station is not logging data
19:52:24:pywws.weatherstation:station is not logging data
19:52:25:pywws.weatherstation:station is not logging data
19:52:26:pywws.weatherstation:station is not logging data
19:52:27:pywws.weatherstation:station is not logging data
19:52:27:pywws.weatherstation:station is not logging data

[Jim Easterbrook]

On 19/08/2024 18:37, 'runge....@googlemail.com' via pywws wrote:
>
> thanks for all the help and links.
> My base station is now running for over 3 hours but when i press history
> only 1 value is stored in the history of the base station.
> I think it is the root cause for my problem that the memory is broken,
> not writable?

It does seem that way.

> if i call pywws-testweatherstation -d -l, i just get this information,
> no delay values are printed.
> pywws-testweatherstation -d -l

[snip]
>  'read_period': 5,

That is the expected 5 minutes.

[snip]

> 19:36:09:pywws.weatherstation:station is not logging data
> 19:36:10:pywws.weatherstation:station is not logging data
> 19:36:10:pywws.weatherstation:station is not logging data
> 19:36:11:pywws.weatherstation:station is not logging data

[snip]

I would expect something to happen every 48 seconds if any data at all
is being received. Unfortunately when pywws has decided the station is
not logging data it skips reading anything, to try and avoid a USB lockup.

You may need to do 'pywws-testweatherstation -d -h 1' every five minutes
or so, and look at the "Recent history" at the end, to see if the data
is being updated at all.

[Jim Easterbrook]

On 19/08/2024 18:53, 'runge....@googlemail.com' via pywws wrote:
> Ok, now i got one line with data but the timestamp is old:
> 19:49:53:pywws.weatherstation:status {'lost_connection': False,
> 'rain_overflow': False}

> 19:49:56:pywws.weatherstation:station is not logging data
> 19:49:57:pywws.weatherstation:setting sensor clock 21.7364
> 0100 17:49:57 {'delay': 1, 'hum_in': 67, 'temp_in': 24.8, 'hum_out': 70,
> 'temp_out': 20.5, 'abs_pressure': 991.6, 'wind_ave': 0, 'wind_gust':
> 0.3, 'wind_dir': 14, 'rain': 28.5, 'status': {'lost_connection': False,
> 'rain_overflow': False}}
> 19:49:57:pywws.weatherstation:station is not logging data

That's not old, it's UTC. The other debugging info has local time zone
time stamps. The data looks OK, and it must have changed as pywws
detected a change and set the sensor clock. The real test is what
happens when the 'delay' reaches 5 (or maybe 30). It should reset to
zero and then start writing data to the next address, so you would get a
line starting 0114.

[runge....@googlemail.com]

Hi Jim,

recent history seems not to change:

Recent history
0x0100 2024-08-19 20:50:00
{'abs_pressure': 991.6,
 'delay': 1,
 'hum_in': 67,
 'hum_out': 70,
 'rain': 28.5,
 'status': {'lost_connection': False, 'rain_overflow': False},
 'temp_in': 24.8,
 'temp_out': 20.5,
 'wind_ave': 0,
 'wind_dir': 14,
 'wind_gust': 0.3}

Recent history
0x0100 2024-08-19 21:03:00
{'abs_pressure': 991.6,
 'delay': 1,
 'hum_in': 67,
 'hum_out': 70,
 'rain': 28.5,
 'status': {'lost_connection': False, 'rain_overflow': False},
 'temp_in': 24.8,
 'temp_out': 20.5,
 'wind_ave': 0,
 'wind_dir': 14,
 'wind_gust': 0.3}

Recent history
0x0100 2024-08-19 21:09:00
{'abs_pressure': 991.6,
 'delay': 1,
 'hum_in': 67,
 'hum_out': 70,
 'rain': 28.5,
 'status': {'lost_connection': False, 'rain_overflow': False},
 'temp_in': 24.8,
 'temp_out': 20.5,
 'wind_ave': 0,
 'wind_dir': 14,
 'wind_gust': 0.3}

The values are also not the actual ones displayed by the station.

If i remove the power and reconnect the station i get new values.

But again the one new dataset is not changing. 

Recent history

0x0100 2024-08-19 21:25:00
{'abs_pressure': 991.6,
 'delay': 0,
 'hum_in': 66,
 'hum_out': 82,
 'rain': 28.5,
 'status': {'lost_connection': False, 'rain_overflow': False},
 'temp_in': 22.8,
 'temp_out': 16.9,
 'wind_ave': 0.3,
 'wind_dir': 14,
 'wind_gust': 0.7}

Recent history
0x0100 2024-08-19 21:37:00
{'abs_pressure': 991.6,
 'delay': 0,
 'hum_in': 66,
 'hum_out': 82,
 'rain': 28.5,
 'status': {'lost_connection': False, 'rain_overflow': False},
 'temp_in': 22.8,
 'temp_out': 16.9,
 'wind_ave': 0.3,
 'wind_dir': 14,
 'wind_gust': 0.7}

I think i always get one value after reset and than it is stuck.

It seems to write always to the first address and does not move on.

Thanks and best regards,

Stefan

[Chris Terran]

Hi --

I've had an Aercus 3085 running under pywws+raspberry pi 400 for over three years now, live logging to wunderground and FTPing to our site. It's OK, but there are occasional USB dropouts.

But a more annoying problem is corrupted data, which happens every so often (every couple of weeks perhaps, though it doesn't seem connected with memory filling up). This causes pywws to fail, and the only fix is to track down the problematic entry in the raw data, delete it, and then reprocess our entire run of data - 14 years' worth now, so this takes a while :-(

It would help if pywws-reprocess could be limited to, say, just do the most recent month, Any chance of that, Jim?

Our weather site is at www.vermilionsands.uk/weather2/

Best, Chris

.

--
You received this message because you are subscribed to the Google Groups "pywws" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pywws+un...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/pywws/ad0d62e5-16f9-450c-b1bb-7294eb8c2ef5%40jim-easterbrook.me.uk.

[Jim Easterbrook]

On 20/08/2024 09:15, Chris Terran wrote:
> I've had an Aercus 3085 running under pywws+raspberry pi 400 for over
> three years now, live logging to wunderground and FTPing to our site.
> It's OK, but there are occasional USB dropouts.
> But a more annoying problem is corrupted data, which happens every so
> often (every couple of weeks perhaps, though it doesn't seem connected
> with memory filling up). This causes pywws to fail, and the only fix is
> to track down the problematic entry in the raw data, delete it, and then
> reprocess our entire run of data - 14 years' worth now, so this takes a
> while :-(
> It would help if pywws-reprocess could be limited to, say, just do the
> most recent month, Any chance of that, Jim?

Yes, simply stop pywws, delete your 'calib' data as far back as the
problem, then restart pywws. It will reprocess the missing calibrated
data when it gets the first new logged data.

[runge....@googlemail.com]

Hi there,

I have been monitoring the station for the last 2 days.
The problem seems to be that the memory only stores the first entry after resetting the base station.
No new values are stored after that.
The display shows the correct values, but I cannot get them via USB.

I have now temporarily replaced it with a cheap weather station that communicates directly with wunderground.
And I get the data from wunderground for my smart home system.
This is not my preferred solution, but it works surprisingly well and stable.

So first of all I want to say a big thank you to all of you and especially to Jim.
Thanks for all your help.
My base station was slowly dying, first with some strange values and wrong pointers that Jim was able to help me get rid of with a calib module and some code improvements, but now it seems to be finally dead.
I loved pywws and it served me well.

I will see if I get a new base station or if you will have to live with the wunderground solution.

If that is the case, I can offer the outdoor modules that worked until the death of the base station to anyone who is interested.
I will start a thread when I am sure how to proceed.

Thanks again,
Stefan

[chris-t]

Ah, that's great! Will save a lot of faffing about. Many thanks!