GW1000 0.1.0b12 bugs ??

[Tim Tuck]

Hi Gary,

I've just been testing a new install of weewx 4.1.1 and I've found that
the GW1000 driver is not populating the radiation and pm2_5 fields of
the database. I'm viewing the database with DB browser for SQLite.

Running the driver on the command line I see the data being collected...

timt@metoffice:~$ PYTHONPATH=/usr/share/weewx python3 -m user.gw1000
--test-driver --ip-address=172.20.1.16
Using configuration file /etc/weewx/weewx.conf

Interrogating GW1000 at 172.20.1.16:45000

2020-09-19 12:18:15 AEST (1600481895): UV: 8, dateTime: 1600481895,
dayRain: 0.8, daymaxwind: 3.1, inHumidity: 51, inTemp: 27.0,
lightning_distance: 27, lightning_last_det_time: 1600249489,
lightning_strike_count: None, luminosity: 95573.0, monthRain: 18.8,
outHumidity: 64, outTemp: 22.4, pm2_52: 20.0, pm2_52_24hav: 75.0,
pressure: 1022.2, rain: None, rainRate: 0.0, relbarometer: 1022.2,
soilMoist1: 42, soilMoist2: 28, soilMoist3: 25, soilMoist4: 30,
stormRain: 0.0, usUnits: 17, uvradiation: 313.8, weekRain: 1.0,
wh41_ch1_batt: None, wh41_ch2_batt: 4, wh51_ch1_batt: 0, wh51_ch2_batt:
0, wh51_ch3_batt: 0, wh51_ch4_batt: 0, wh57_batt: 5, wh65_batt: 0,
windDir: 62, windGust: 1.5, windSpeed: 1.0, yearRain: 1107.8
2020-09-19 12:19:15 AEST (1600481955): UV: 8, dateTime: 1600481955,
dayRain: 0.8, daymaxwind: 3.1, inHumidity: 51, inTemp: 27.1,
lightning_distance: 27, lightning_last_det_time: 1600249489,
lightning_strike_count: 0, luminosity: 98378.0, monthRain: 18.8,
outHumidity: 63, outTemp: 22.6, pm2_52: 20.0, pm2_52_24hav: 75.0,
pressure: 1022.3, rain: 0.0, rainRate: 0.0, relbarometer: 1022.3,
soilMoist1: 42, soilMoist2: 28, soilMoist3: 25, soilMoist4: 30,
stormRain: 0.0, usUnits: 17, uvradiation: 313.8, weekRain: 1.0,
wh41_ch1_batt: None, wh41_ch2_batt: 4, wh51_ch1_batt: 0, wh51_ch2_batt:
0, wh51_ch3_batt: 0, wh51_ch4_batt: 0, wh57_batt: 5, wh65_batt: 0,
windDir: 286, windGust: 2.0, windSpeed: 1.3, yearRain: 1107.8
2020-09-19 12:20:15 AEST (1600482015): UV: 4, dateTime: 1600482015,
dayRain: 0.8, daymaxwind: 3.1, inHumidity: 51, inTemp: 27.1,
lightning_distance: 27, lightning_last_det_time: 1600249489,
lightning_strike_count: 0, luminosity: 44190.0, monthRain: 18.8,
outHumidity: 62, outTemp: 22.7, pm2_52: 20.0, pm2_52_24hav: 75.0,
pressure: 1022.6, rain: 0.0, rainRate: 0.0, relbarometer: 1022.6,
soilMoist1: 43, soilMoist2: 28, soilMoist3: 25, soilMoist4: 30,
stormRain: 0.0, usUnits: 17, uvradiation: 140.0, weekRain: 1.0,
wh41_ch1_batt: None, wh41_ch2_batt: 4, wh51_ch1_batt: 0, wh51_ch2_batt:
0, wh51_ch3_batt: 0, wh51_ch4_batt: 0, wh57_batt: 5, wh65_batt: 0,
windDir: 19, windGust: 1.0, windSpeed: 0.6, yearRain: 1107.8

timt@metoffice:~$ sudo wee_extension --list
Extension Name    Version   Description
Belchertown       1.2       A clean modern skin with real time streaming
updates and interactive charts. Modeled after BelchertownWeather.com
GW1000            0.1.0b12  WeeWX driver for GW1000 WiFi gateway.
timt@metoffice:~$

I've also noticed that once the sun goes down the uvradiation field
disappears altogether

timt@metoffice:~$ PYTHONPATH=/usr/share/weewx python3 -m user.gw1000
--test-driver --ip-address=172.20.1.16
Using configuration file /etc/weewx/weewx.conf
debug level is '1'

IP address obtained from command line options
Port number obtained from station config

Interrogating GW1000 at 172.20.1.16:45000

2020-09-21 17:53:28 AEST (1600674808): UV: 0, dateTime: 1600674808,
dayRain: 0.0, daymaxwind: 4.6, inHumidity: 44, inTemp: 26.9,
lightning_distance: None, lightning_last_det_time: None,
lightning_strike_count: None, luminosity: 0.0, monthRain: 31.3,
outHumidity: 56, outTemp: 26.8, pm2_52_24hav: 9.0, pressure: 1002.8,
rain: None, rainRate: 0.0, relbarometer: 1002.8, soilMoist1: 44,
soilMoist2: 30, soilMoist3: 28, soilMoist4: 39, stormRain: 0.0, usUnits:
17, weekRain: 12.5, wh41_ch1_batt: None, wh41_ch2_batt: 4,
wh51_ch1_batt: 0, wh51_ch2_batt: 0, wh51_ch3_batt: 0, wh51_ch4_batt: 0,
wh57_batt: 5, wh65_batt: 0, windDir: 37, windGust: 1.0, windSpeed: 0.6,
yearRain: 1120.3
2020-09-21 17:53:58 AEST (1600674838): UV: 0, dateTime: 1600674838,
dayRain: 0.0, daymaxwind: 4.6, inHumidity: 44, inTemp: 26.9,
lightning_distance: None, lightning_last_det_time: None,
lightning_strike_count: 0, luminosity: 0.0, monthRain: 31.3,
outHumidity: 56, outTemp: 26.8, pm2_52_24hav: 9.0, pressure: 1002.8,
rain: 0.0, rainRate: 0.0, relbarometer: 1002.8, soilMoist1: 44,
soilMoist2: 30, soilMoist3: 28, soilMoist4: 39, stormRain: 0.0, usUnits:
17, weekRain: 12.5, wh41_ch1_batt: None, wh41_ch2_batt: 4,
wh51_ch1_batt: 0, wh51_ch2_batt: 0, wh51_ch3_batt: 0, wh51_ch4_batt: 0,
wh57_batt: 5, wh65_batt: 0, windDir: 37, windGust: 1.0, windSpeed: 0.6,
yearRain: 1120.3
^C/usr/share/weewx/user/gw1000.py:2128: DeprecationWarning: isAlive() is
deprecated, use is_alive() instead
  if self.thread.isAlive():
timt@metoffice:~$


regards

Tim

[Graham Eddy]

pm2_52 and wh41_ch2_batt (corresponding battery) and giving good values.
pm2_5 is absent and wh41_ch1_batt is None. is that sensor charged and working (eg shows fine in WS View)?
and what is your [[field_map]] or [[field_map_extensions]]?

> --
> 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/4cad6328-c3d2-023d-572c-52af72d1abad%40skybase.net.

[gjr80]

Tim,

The GW1000 driver does not provide WeeWX field radiation, those folks that want radiation from th GW1000 are deriving radiation from WeeWX field luminosity. This is done through the WeeWX StdCalibrate service by placing an entry in weewx.conf under [StdCalibrate] [[Corrections]] as follows:

[StdCalibrate]

    ....

    [[Corrections]]

        ....

        radiation = luminosity/126.7 if luminosity is not None else None

Interesting regarding uvradiation disappearing after sun down. The GW1000 driver just decodes and provides the data/obs returned by the GW1000 API. If uvradiation data is available from the GW1000 the API response includes an identifying code and the data, if there is no uvradiation data the identifying code and data are absent. Whilst the GW1000 driver knows broadly what sensor suites are present it does not know exactly what individual sensors are present at any point in time, so the driver takes the view that if uvradiation data is not included in the API response then a uvradiation field should not be included in the emitted loop packet. (However, if the API included uvradiation data that was in fact 0 when the sun was down then the loop packet emitted by the driver would contain a uvradiation field that is 0).

You could run the driver directly with the --live-data and --debug=3 options to obtain the raw API response. If you could do a run when the sun is up and again later when the sun is down and if you post the log output from each I could confirm that the uvradiation data is not in the sun down response. The command you would need to run is:

$ PYTHONPATH=/usr/share/weewx python3 -m user.gw1000 --live-data --debug=3

This should result in a number of entries in your WeeWX log that include numerous hex digit pairs.I especially need to see the line starting 'sensor data is'.

As for your PM2.5 sensor I will wait until you reply to Graham's post.

Gary

[Tim Tuck]

Hi Graham,

I have my PM sensor on ch2, it was on ch1 until a battery change and it
moved itself and I was too lazy to move it back.

The

[[field_map]]

is the default and I also tried the following...

 [[field_map_extensions]]
        uvradiation = radiation
        pm2_52 = pm2_5

which didn't change the result.

I thought I'd tackle the radiation problem 1st before worrying too much
about the pm2.5 sensor and data. I'll go change its channel  now :)

regards

Tim

[Tim Tuck]

Hi Gary,

OK.... I thought the uvradiation field from the sensor corresponded to the radiation field in the DB given luminosity was a separate field in its own right.

I'll go make those changes to see what I get. I'll  move the PM2.5 sensor back to ch1 and see if the data appears in the DB.

I'll also do the debug thing and report.

thanks

Tim

[gjr80]

On Tuesday, 22 September 2020 at 07:52:28 UTC+10 ti...@skybase.net wrote:

OK.... I thought the uvradiation field from the sensor corresponded to the radiation field in the DB given luminosity was a separate field in its own right.

No, the GW1000 API provides two UV related obs; one labelled UV that is a value in microwatts per square metre (I believe the GW1000 UV values are in the order of 10s of thousands of microwatts per square metre whereas the WeeWX field radiation field is of the order of 100s of watts per square metre) and one labelled UVI which is an index from 0 to 15. The UVI field is mapped by default to the WeeWX UV field and the GW1000 UV field is mapped to WeeWX field uvradiation (because the  GW1000 UVI field is mapped to WeeWX field UV the GW1000 UV field needed to be mapped to another field name so hence uvradiation). The GW1000 light field (Ecowitt term) in lux is (by default) mapped to the WeeWX field luminosity.

I'll go make those changes to see what I get. I'll  move the PM2.5 sensor back to ch1 and see if the data appears in the DB.

In terms of getting an observation from a station saved to the WeeWX database it is a simple case of getting a number of holes to line up in the cheese. First the driver needs to obtain and  decode the sensor value from the station. Then the driver needs to map this sensor value to a field name in the loop packet/archive records emitted by the driver. Finally, the field name in the loop packet/archive record emitted by the driver must exist in the WeeWX database schema. If all three of these conditions are met and all things being equal, the data will be saved to database, if one of the conditions is not met the data will not be saved to database. Consider the light data from the GW1000. The driver reads this data from the API, decodes it and saves it in a field named 'light'. The driver's default field map maps the GW1000 light field to the WeeWX luminosity field. The GW1000 driver emits loop packets containing a field named luminosity that contains the GW1000 light data. If the WeeWX database schema contains the field luminosity (eg if the wview_extended schema is being used) then the luminosity value will be stored in the database. There are a few other parts to the machine but that is it in its simplest form. If the user was using the old wview schema that does not include luminosity then the luminosity value would not be saved to database.

 If you consider your PM2.5 sensor. If your sensor connected to channel 1 your PM2.5 data would appear in the GW1000 field pm251. The default field map maps pm251 to WeeWX field pm2_5. If you are using the wview_extended schema then the PM2.5 data would be saved to database in the pm2_5 field. If your sensor connected to channel 2 your PM2.5 data would appear in the GW1000 field pm252. The default field map maps pm252 to WeeWX field pm2_52. If you are using the wview_extended (or the wview) schema there is no pm2_52 field so the PM2.5 data would not be saved to database. How to fix? The easiest approach will be to make sure your sensor always maps to the same channel. You could add all possible PM2.5 fields to your database schema, at least you won't miss any data but if your sensors change channels (say after a GW1000 firmware update or reset) you won't know which data is from which sensor. Do not attempt to map every PM2.5 channel to WeeWX field pm2_5, even if you only have one sensor it will almost certainly cause issues within the driver.

Similar but slightly different for the PM2.5 battery state data.

I hope the above explains somewhat how things work and why you are seeing what you are seeing.

Gary

[Tim Tuck]

Hi Gary,

Thanks for your concise explanation, I think I understand now :)

I have both radiation and my PM2.5 fields being populated now and
reading back data from them.

Please find attached my log snippets as requested.

Interestingly the uvradiation field is there this time around when
running the driver test so I don't know why it was absent before!

regards

Tim

[Larry]

I have had three crashes of Weewx on my Raspberry Pi Zero W in past few weeks .

Here is the log I have now - not sure if it is the right one you would need to gather any clues.

Any help on what I should do is appreciated

Thanks 

Larry

 sudo tail -f /var/log/syslog

Sep 22 21:23:34 pizerowx weewx[701] CRITICAL __main__:     ****  Waiting 60 seconds then retrying...
Sep 22 21:24:34 pizerowx weewx[701] INFO __main__: retrying...
Sep 22 21:24:34 pizerowx weewx[701] INFO __main__: Using configuration file /etc/weewx/weewx.conf
Sep 22 21:24:34 pizerowx weewx[701] INFO __main__: Debug is 0
Sep 22 21:24:34 pizerowx weewx[701] INFO weewx.engine: Loading station type GW1000 (user.gw1000)
Sep 22 21:25:01 pizerowx weewx[701] ERROR gw1000: user.gw1000: Failed to detect GW1000 ip address and/or port after 3 attempts
Sep 22 21:25:01 pizerowx weewx[701] ERROR weewx.engine: Import of driver failed: Failed to detect GW1000 ip address and/or port after 3 attempts (<class 'user.gw1000.GW1000IOError'>)
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****  Traceback (most recent call last):
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/engine.py", line 103, in setupStation
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****      self.console = loader_function(config_dict, self)
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/user/gw1000.py", line 1136, in loader
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****      return Gw1000Driver(**config_dict[DRIVER_NAME])
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/user/gw1000.py", line 1415, in __init__
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****      super(Gw1000Driver, self).__init__(**stn_dict)
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/user/gw1000.py", line 762, in __init__
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****      debug_wind=self.debug_wind)
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/user/gw1000.py", line 1630, in __init__
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****      lost_contact_log_period=lost_contact_log_period)
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/user/gw1000.py", line 2017, in __init__
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****      raise GW1000IOError(_msg)
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****  GW1000IOError: Failed to detect GW1000 ip address and/or port after 3 attempts
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL __main__: Unable to load driver: Failed to detect GW1000 ip address and/or port after 3 attempts
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL __main__:     ****  Waiting 60 seconds then retrying...
Sep 22 21:23:34 pizerowx weewx[701] CRITICAL weewx.engine:     ****      lost_contact_log_period=lost_contact_log_period)
Sep 22 21:23:34 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/user/gw1000.py", line 2017, in __init__
Sep 22 21:23:34 pizerowx weewx[701] CRITICAL weewx.engine:     ****      raise GW1000IOError(_msg)
Sep 22 21:23:34 pizerowx weewx[701] CRITICAL weewx.engine:     ****  GW1000IOError: Failed to detect GW1000 ip address and/or port after 3 attempts
Sep 22 21:23:34 pizerowx weewx[701] CRITICAL __main__: Unable to load driver: Failed to detect GW1000 ip address and/or port after 3 attempts
Sep 22 21:23:34 pizerowx weewx[701] CRITICAL __main__:     ****  Waiting 60 seconds then retrying...
Sep 22 21:24:34 pizerowx weewx[701] INFO __main__: retrying...
Sep 22 21:24:34 pizerowx weewx[701] INFO __main__: Using configuration file /etc/weewx/weewx.conf
Sep 22 21:24:34 pizerowx weewx[701] INFO __main__: Debug is 0
Sep 22 21:24:34 pizerowx weewx[701] INFO weewx.engine: Loading station type GW1000 (user.gw1000)
Sep 22 21:25:01 pizerowx weewx[701] ERROR gw1000: user.gw1000: Failed to detect GW1000 ip address and/or port after 3 attempts
Sep 22 21:25:01 pizerowx weewx[701] ERROR weewx.engine: Import of driver failed: Failed to detect GW1000 ip address and/or port after 3 attempts (<class 'user.gw1000.GW1000IOError'>)
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****  Traceback (most recent call last):
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/engine.py", line 103, in setupStation
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****      self.console = loader_function(config_dict, self)
Sep 22 21:25:01 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/us
Sep 22 21:26:01 pizerowx weewx[701] INFO __main__: Using configuration file /etc
Sep 22 21:26:01 pizerowx weewx[701] INFO __main__: Debug is 0
Sep 22 21:26:01 pizerowx weewx[701] INFO weewx.engine: Loading station type GW10
Sep 22 21:26:27 pizerowx weewx[701] ERROR gw1000: user.gw1000: Failed to detect
Sep 22 21:26:27 pizerowx weewx[701] ERROR weewx.engine: Import of driver failed:
Sep 22 21:26:27 pizerowx weewx[701] CRITICAL weewx.engine:     ****  Traceback (
Sep 22 21:26:27 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/us
Sep 22 21:26:27 pizerowx weewx[701] CRITICAL weewx.engine:     ****      self.co
Sep 22 21:26:27 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/us
Sep 22 21:26:27 pizerowx weewx[701] CRITICAL weewx.engine:     ****      return
Sep 22 21:26:27 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/us
Sep 22 21:26:27 pizerowx weewx[701] CRITICAL weewx.engine:     ****      super(G
Sep 22 21:26:27 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/us
Sep 22 21:26:27 pizerowx weewx[701] CRITICAL weewx.engine:     ****      debug_w
Sep 22 21:26:27 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/us
Sep 22 21:26:27 pizerowx weewx[701] CRITICAL weewx.engine:     ****      lost_co
Sep 22 21:26:27 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/us
Sep 22 21:26:27 pizerowx weewx[701] CRITICAL weewx.engine:     ****      raise G
Sep 22 21:26:27 pizerowx weewx[701] CRITICAL weewx.engine:     ****  GW1000IOErr
Sep 22 21:26:27 pizerowx weewx[701] CRITICAL __main__: Unable to load driver: Fa
Sep 22 21:26:27 pizerowx weewx[701] CRITICAL __main__:     ****  Waiting 60 seco
Sep 22 21:27:27 pizerowx weewx[701] INFO __main__: retrying...
Sep 22 21:27:27 pizerowx weewx[701] INFO __main__: Using configuration file /etc/weewx/weewx.conf
Sep 22 21:27:27 pizerowx weewx[701] INFO __main__: Debug is 0
Sep 22 21:27:27 pizerowx weewx[701] INFO weewx.engine: Loading station type GW1000 (user.gw1000)
Sep 22 21:27:53 pizerowx weewx[701] ERROR gw1000: user.gw1000: Failed to detect GW1000 ip address and/or port after 3 attempts
Sep 22 21:27:53 pizerowx weewx[701] ERROR weewx.engine: Import of driver failed: Failed to detect GW1000 ip address and/or port after 3 attempts (<class 'user.gw1000.GW1000IOError'>)
Sep 22 21:27:53 pizerowx weewx[701] CRITICAL weewx.engine:     ****  Traceback (most recent call last):
Sep 22 21:27:53 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/engine.py", line 103, in setupStation
Sep 22 21:27:54 pizerowx weewx[701] CRITICAL weewx.engine:     ****      self.console = loader_function(config_dict, self)
Sep 22 21:27:54 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/user/gw1000.py", line 1136, in loader
Sep 22 21:27:54 pizerowx weewx[701] CRITICAL weewx.engine:     ****      return Gw1000Driver(**config_dict[DRIVER_NAME])
Sep 22 21:27:54 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/user/gw1000.py", line 1415, in __init__
Sep 22 21:27:54 pizerowx weewx[701] CRITICAL weewx.engine:     ****      super(Gw1000Driver, self).__init__(**stn_dict)
Sep 22 21:27:54 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/user/gw1000.py", line 762, in __init__
Sep 22 21:27:54 pizerowx weewx[701] CRITICAL weewx.engine:     ****      debug_wind=self.debug_wind)
Sep 22 21:27:54 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/user/gw1000.py", line 1630, in __init__
Sep 22 21:27:54 pizerowx weewx[701] CRITICAL weewx.engine:     ****      lost_contact_log_period=lost_contact_log_period)
Sep 22 21:27:54 pizerowx weewx[701] CRITICAL weewx.engine:     ****    File "/usr/share/weewx/user/gw1000.py", line 2017, in __init__
Sep 22 21:27:54 pizerowx weewx[701] CRITICAL weewx.engine:     ****      raise GW1000IOError(_msg)
Sep 22 21:27:54 pizerowx weewx[701] CRITICAL weewx.engine:     ****  GW1000IOError: Failed to detect GW1000 ip address and/or port after 3 attempts
Sep 22 21:27:54 pizerowx weewx[701] CRITICAL __main__: Unable to load driver: Failed to detect GW1000 ip address and/or port after 3 attempts
Sep 22 21:27:54 pizerowx weewx[701] CRITICAL __main__:     ****  Waiting 60 seconds then retrying...

[gjr80]

Thanks Tim. I guess we give it the benefit of the doubt, the debug info you provided showed the raw uv/uvi data was there both after sunrise and after sunset.

Gary

[Larry]

okay I just checked with WSview and notice it isn't seeing the weather station . I guess that is the problem. Seems like these issues happened after the last Ecowitt updates.

I repowered the GW1000 and it came back to life and WSView now sees it again.

The lights were all on the GW1000 - not sure what made it crash .

Larry

[gjr80]

Larry,

So I guess the GW1000 driver picked up the GW1000 again? If the WSView app doesn't pick p the GW1000 then the driver probably doe snot have much chance either. I believe there have been a few issues after firmware updates, I have been getting into the habit of verifying everything is working after a firmware update.

From the log extract you posted the driver appears to have been doing what it should have on loss of contact with/being unable to contact the GW1000.

Gary

[Larry]

Yes Gary - as soon as I cycled power to the GW1000 - then Weewx connected up to it again on it's next retry  and works fine again.  I have had it crash 3 times in past month though I did not pay close attention to find the cause . I will from now on. Thanks for your efforts developing the driver.

Larry