GW1000 and" CMD_READ_STATION_MAC"

[gert.a...@gmail.com]

Hi

Running RPI 4, Weewx 4.2 and GW1000 latest version and suddenly this appears. Any ideas what's going on?

The combination has been running stable, so my best quest it might be a hardware problem or? 

Never seen this before and couldn't find anything on the net.

Nov 30 16:30:32 raspberrypi weewx[537] ERROR user.gw1000: Failed to obtain response to command 'CMD_READ_STATION_MAC' after 3 attempts

Nov 30 16:30:32 raspberrypi weewx[537] ERROR weewx.engine: Import of driver failed: Failed to obtain response to command 'CMD_READ_STATION_MAC' after 3 attempts (<class 'user.gw1000.GW1000IOError'>)

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****  Traceback (most recent call last):

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/weewx/engine.py", line 109, in setupStation

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****      self.console = loader_function(config_dict, self)

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/user/gw1000.py", line 1293, in loader

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****      return Gw1000Driver(**config_dict[DRIVER_NAME])

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/user/gw1000.py", line 1568, in __init__

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****      super(Gw1000Driver, self).__init__(**stn_dict)

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/user/gw1000.py", line 767, in __init__

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****      debug_wind=self.debug_wind)

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/user/gw1000.py", line 1870, in __init__

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****      lost_contact_log_period=lost_contact_log_period)

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/user/gw1000.py", line 2276, in __init__

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****      self.mac = self.get_mac_address()

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/user/gw1000.py", line 2407, in get_mac_address

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****      return self.send_cmd_with_retries('CMD_READ_STATION_MAC')

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/user/gw1000.py", line 2532, in send_cmd_with_retries

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****      raise GW1000IOError(_msg)

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL weewx.engine:     ****  user.gw1000.GW1000IOError: Failed to obtain response to command 'CMD_READ_STATION_MAC' after 3 attempts

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL __main__: Unable to load driver: Failed to obtain response to command 'CMD_READ_STATION_MAC' after 3 attempts

Nov 30 16:30:32 raspberrypi weewx[537] CRITICAL __main__:     ****  Exiting...

Gert

[Bill Arthur]

I saw this today, too.
For some reason weewx can't contact your GW1000.  Without the GW1000 connecting weewx won't start.
Either the wrong IP in weewx.config, or the GW1000 needs to be set up (again?) on your WiFi.
If you haven't already assigned the GW1000 a static IP in your router, now is a good time.

[vince]

On Monday, November 30, 2020 at 2:58:31 PM UTC-8 wa4...@gmail.com wrote:

I saw this today, too.
For some reason weewx can't contact your GW1000.  Without the GW1000 connecting weewx won't start.
Either the wrong IP in weewx.config, or the GW1000 needs to be set up (again?) on your WiFi.
If you haven't already assigned the GW1000 a static IP in your router, now is a good time.

Always a good idea to reserve a static address via your router, even if the computer/station works via DHCP.

Note - the gw1000 will reboot if it fails to reach the Ecowitt servers (or a NTP server) too often or for too long a period.  They have a couple watchdog timers in the firmware that can't be turned off.  While it can be faked on your LAN to prevent this, the gateway will still reboot if you lose your home wifi for too long, as it thinks lack of connectivity to Ecowitt means the hardware needs to reboot itself (which is not true of course, but they do what they do I guess...)

[gjr80]

The error shows that the driver could not contact your GW1000 for some reason, once the driver had everything required to connect to the GW1000 the GW1000 did not respond. It could have happened for any number of reasons; the GW1000 driver may have been using an incorrect address when trying to connect to the GW1000,  the GW1000 may have changed address or the network may have experienced a problem. Impossible to say more without knowing exact config details both of the driver and your GW1000/network config.

Things to try. You could set loop_on_init = True in weewx.conf so that WeeWX will wait 60 seconds when the driver fails to load and then try again. If the issue is transient in nature this may work but if it is something more permanent then it likely will just cause WeeWX to loop indefinitely. You could try configuring your network such that the GW1000 uses a static IP rather than having the GW1000 driver locate the GW1000 via network broadcast.

Gary

[gert.a...@gmail.com]

Hi

Thank to All and your good suggestions.

I have configured a static IP-address for the GW1000 and the RPI. I have also rebooted the RPI and the Gateway and now it seems to work again.

Thanks again.

Gert