GW1000 stopped working

[zasp...@gmail.com]

 Hi

After running a GQ1000 for around 8 weeks it has stopped working at 03:15 am so I wasn’t around at that time of the morning fiddling. it just stopped for some reason

 

After it stopped reviving data

I have rebooted the GW1000 and the pi

Upgraded the GW1000 firmware

Tried the sd card in another pi

Used a backup image from 3 weeks ago that worked fine then

Weewx cant see the GW1000 nothing works

I have run

python -m user.gw1000 --test-driver

no data is being picked up, previously you could see what information was being received

I thought maybe the GW100 had failed or not working

But  the ecowitt webpage is receiving data

 

Any ideas ?

 

 

 

 

 

Jul 22 09:06:13 raspberrypiwx weewx[771] DEBUG __main__: Initializing engine

Jul 22 09:06:13 raspberrypiwx weewx[771] INFO weewx.engine: Loading station type GW1000 (user.gw1000)

Jul 22 09:06:15 raspberrypiwx weewx[771] DEBUG user.gw1000: Failed to obtain response to attempt 1 to send command 'CMD_READ_STATION_MAC': timed out

Jul 22 09:06:16 raspberrypiwx postfix/qmgr[863]: 0FFBEDF431: from=<p...@raspberrypiwx.home>, size=967, nrcpt=1 (queue active)

Jul 22 09:06:16 raspberrypiwx postfix/pickup[4522]: E45F4DF429: uid=1000 from=<pi>

Jul 22 09:06:16 raspberrypiwx postfix/cleanup[7600]: E45F4DF429: message-id=<202307220806...@raspberrypiwx.home>

Jul 22 09:06:27 raspberrypiwx weewx[771] DEBUG user.gw1000: Failed to obtain response to attempt 2 to send command 'CMD_READ_STATION_MAC': timed out

Jul 22 09:06:39 raspberrypiwx weewx[771] DEBUG user.gw1000: Failed to obtain response to attempt 3 to send command 'CMD_READ_STATION_MAC': timed out

Jul 22 09:06:39 raspberrypiwx weewx[771] ERROR user.gw1000: Failed to obtain response to command 'CMD_READ_STATION_MAC' after 3 attempts

Jul 22 09:06:39 raspberrypiwx weewx[771] ERROR weewx.engine: Import of driver failed: Failed to obtain response to command 'CMD_READ_STATION_MAC' after 3 attempts (<class 'user.gw1000.GWIOError'>)

Jul 22 09:06:39 raspberrypiwx weewx[771] CRITICAL weewx.engine:     ****  Traceback (most recent call last):

Jul 22 09:06:39 raspberrypiwx weewx[771] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/weewx/engine.py", line 119, in setupStation

Jul 22 09:06:39 raspberrypiwx weewx[771] CRITICAL weewx.engine:     ****      self.console = loader_function(config_dict, self)

Jul 22 09:06:39 raspberrypiwx weewx[771] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/user/gw1000.py", line 1674, in loader

Jul 22 09:06:39 raspberrypiwx weewx[771] CRITICAL weewx.engine:     ****      return GatewayDriver(**config_dict[DRIVER_NAME])

Jul 22 09:06:39 raspberrypiwx weewx[771] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/user/gw1000.py", line 2111, in __init__

Jul 22 09:06:39 raspberrypiwx weewx[771] CRITICAL weewx.engine:     ****      super(GatewayDriver, self).__init__(**stn_dict)

Jul 22 09:06:39 raspberrypiwx weewx[771] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/user/gw1000.py", line 968, in __init__

Jul 22 09:06:39 raspberrypiwx weewx[771] CRITICAL weewx.engine:     ****      debug=self.debug)

Jul 22 09:06:39 raspberrypiwx weewx[771] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/user/gw1000.py", line 2436, in __init__

Jul 22 09:06:39 raspberrypiwx weewx[771] CRITICAL weewx.engine:     ****      log_unknown_fields=log_unknown_fields, debug=debug)

Jul 22 09:06:39 raspberrypiwx weewx[771] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/user/gw1000.py", line 5847, in __init__

Jul 22 09:06:39 raspberrypiwx weewx[771] CRITICAL weewx.engine:     ****      debug=debug)

Jul 22 09:06:39 raspberrypiwx weewx[771] CRITICAL weewx.engine:     ****    File "/home/weewx/bin/user/gw1000.py", line 4578, in __init__

Jul 22 09:06:39 raspberrypiwx weewx[771] CRITICAL weewx.engine:     ****      self.mac = self.get_mac_address()

Jul 22 09:06:39 raspberrypiwx weewx[771] CRITICAL weewx.engine:     ****    File 

[Rainer Lang]

can you see the live data in the WS View Plus app or in the WebUI/embedded webpage (IP address of your GW1100 in the browser URL field) ?

maybe the IP of your GW1100 changed, which won't keep it from posting to ecowitt.net, but if it is now different from what is written in weewx.conf, weewx won't recieve anything

please post the syslog of the weewx startup procedure, best for one archive interval, so we can see what the Ecowitt Gateway driver feedback is

did you make your IP address of the GW1100 static (WebUI, device settings) ? - you better do !
or alternatively make a so-called IP/MAC address binding of the current DHCP provided IP in your router
making it static from within the WebUI is in my experience the better version, but both work
(whenever you make changes inside WS View Plus or the WebUI, make sure you see the "success" message after pressing "save" or "apply"

--
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/2af26648-63ca-47f3-b70f-e6315b9a40f3n%40googlegroups.com.

[zasp...@gmail.com]

hi

the ip address 192.168.1..248 

has not changed its in my weewx.confg 

i can log in with chrome on that address

and my router has a fixed ip for this mac address

what i dont understand is why my raspi image from 3 weeks ago will not work thats strange

my syslog attached

thanks for your help

[Rainer Lang]

the message is clear:
DEBUG user.gw1000: Failed attempt 1 to send command 'CMD_READ_STATION_MAC': [Errno 101] Network is unreachable

you have an issue reaching your GW1100 from the weewx server

at first glance that's neither a weewx nor a GW1100 issue - it looks like an issue in your local network infrastructure.

Also, I hope that your IP address for the GW1100 is 192.168.1.248 and NOT, as you write, 192.168.1..248 (if in weewx.conf you have 192.168.1..248 then that's not not a valid IP address !!
It might just be a typo (error while typing) at your end, but worth checking.

Can you reach your router and the GW1100 on the operating system level of your RPi ?

ping 192.168.1.1 would/should reach the router

ping 192.168.1.248
should reach the GW1100 unless your router has some policy active which doesn't allow that
or
traceroute 192.168.1.248
should give you the IP addresses of the devices (router/switch ...) on the network path between your device (RPi) and the destination device (GW1100)

Depending on which router you have, some router set by default a tag which doesn't allow WLAN/WiFi devices to communicate inside the local network - you have to explicitly allow that, often by removing a tagged/ticket box.

It's not impossible that your image is faulty and you might need to flash that image again.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/86b4f30b-2901-46e9-842a-9f6df8bb1d42n%40googlegroups.com.

[vince]

Lets see your [GW1000] stanza from weewx.conf please.  If your 'gateway' address is 192.168.1.148 then it should look something like the following:

[GW1000]
    ip_address = 192.168.1.148
    port = 45000
    poll_interval = 20
    driver = user.gw1000

Your gateway should also respond to a ping from your weewx box.   Log into the weewx box and try "ping -n 192.168.1.148" and verify that you can get a response.

[zasp...@gmail.com]

hi 

from my weewx.confg

[GW1000]
    # This section is for the Ecowitt Gateway driver.
   
    # How often to poll the API, default is every 20 seconds:
    poll_interval = 20
   
    # The driver to use:
    driver = user.gw1000
    ip_address = 192.168.1.248
    port = 45000
    [[field_map_extensions]]
        extraTemp10 = temp10
        wxSensor30 = light

however you are correct its a network issue

if i ping from my laptop

C:\Windows\System32>ping 192.168.1.248

Pinging 192.168.1.248 with 32 bytes of data:
Reply from 192.168.1.248: bytes=32 time=5ms TTL=255
Reply from 192.168.1.248: bytes=32 time=3ms TTL=255
Reply from 192.168.1.248: bytes=32 time=3ms TTL=255
Reply from 192.168.1.248: bytes=32 time=3ms TTL=255

Ping statistics for 192.168.1.248:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 5ms, Average = 3ms

if i ping from my PI

pi@raspberrypiwx:~ $ ping -n 192.168.1.248
PING 192.168.1.248 (192.168.1.248) 56(84) bytes of data.
From 192.168.1.242 icmp_seq=1 Destination Host Unreachable
From 192.168.1.242 icmp_seq=2 Destination Host Unreachable
From 192.168.1.242 icmp_seq=3 Destination Host Unreachable
From 192.168.1.242 icmp_seq=4 Destination Host Unreachable
From 192.168.1.242 icmp_seq=5 Destination Host Unreachable
From 192.168.1.242 icmp_seq=6 Destination Host Unreachable
From 192.168.1.242 icmp_seq=7 Destination Host Unreachable
From 192.168.1.242 icmp_seq=8 Destination Host Unreachable
From 192.168.1.242 icmp_seq=9 Destination Host Unreachable

i have no idea why laptop can ping the GW1000 but my PI cant

[zasp...@gmail.com]

i have pinged other IP address on my net work and the PI gets  response its only the GW1000 its have an issue with

[Graham Eddy]

laptop can ping gw1000.

pi cannot ping gw1000.

can laptop ping pi? and pi ping laptop?

⊣GE⊢

-- 
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/131679f4-e4fa-4c90-9baa-712b9cb14f70n%40googlegroups.com.

[zasp...@gmail.com]

hi

laptop  can ping PI

Pi cannot ping laptop

connected up a second PI (created with a different image file)

Laptop can ping PI

Pi cannot ping laptop

PI cannot ping 192.168.1.248 the GW1000

i can SSH into both PI's

[zasp...@gmail.com]

weewx reported the log at 3:15am so i checked the last time that bt updated the router firmware that was 1-july 23 so i cant blame the router

[Graham Eddy]

can pi1/pi2 ping each other?

what are the IP addrs/netmask for laptop, gw1000, pi1 and pi2?

⊣GE⊢

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/8b7a9f80-12cb-4f18-b889-eb8b75b4922fn%40googlegroups.com.

[vince]

What are the ip addresses of 'each' laptop, pi, and gw1000 on your network ?

You definitely have a network issue.

I have seen this kind of thing when local DNS is broken.  Do you possibly run a pihole or some other kind of internal DNS server ?

[zasp...@gmail.com]

Hi

Laptop information

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . : home
   Description . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6235
   Physical Address. . . . . . . . . : B4-B6-76-01-EC-99
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.156(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 23 July 2023 10:27:09
   Lease Expires . . . . . . . . . . : 24 July 2023 10:29:13
   Default Gateway . . . . . . . . . : 192.168.1.254
   DHCP Server . . . . . . . . . . . : 192.168.1.254
   DNS Servers . . . . . . . . . . . : 127.0.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

PI weewx

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.242  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::148a:46fd:4ac9:e7b0  prefixlen 64  scopeid 0x20<link>
        inet6 2a00:23c4:9402:8f01:13da:6dac:cd41:7029  prefixlen 64  scopeid 0x0<global>
        inet6 fd00::1:8d4a:e62c:d18b:de48  prefixlen 64  scopeid 0x0<global>
        ether dc:a6:32:38:98:da  txqueuelen 1000  (Ethernet)
        RX packets 2921761  bytes 3720208567 (3.4 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1849890  bytes 918345739 (875.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

PI second

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.94  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::f227:28d7:543b:e89f  prefixlen 64  scopeid 0x20<link>
        inet6 fd00::1:31a3:d46c:62cc:5f7  prefixlen 64  scopeid 0x0<global>
        inet6 2a00:23c4:9402:8f01:7656:850a:5d26:1be2  prefixlen 64  scopeid 0x0<global>
        inet6 fd00::1:36c5:e8c1:657d:d85a  prefixlen 64  scopeid 0x0<global>
        inet6 2a00:23c4:9402:8f01:a8f0:3a46:764a:9005  prefixlen 64  scopeid 0x0<global>
        ether dc:a6:32:06:87:03  txqueuelen 1000  (Ethernet)
        RX packets 31185  bytes 28290241 (28.2 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 18891  bytes 2106606 (2.1 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

i dont know how to get the netmask of the GW1000

its ip address is 192.168.1.248

i used advanced IP scanner to ping it from the laptop

Pinging 192.168.1.248 with 32 bytes of data:

Reply from 192.168.1.156: Destination host unreachable.
Request timed out.
Reply from 192.168.1.156: Destination host unreachable.
Request timed out.
Reply from 192.168.1.156: Destination host unreachable.
Request timed out.
Reply from 192.168.1.248: bytes=32 time=447ms TTL=255

Reply from 192.168.1.248: bytes=32 time=3ms TTL=255

Reply from 192.168.1.248: bytes=32 time=4ms TTL=255
Reply from 192.168.1.248: bytes=32 time=9ms TTL=255

Reply from 192.168.1.248: bytes=32 time=3ms TTL=255

Reply from 192.168.1.248: bytes=32 time=2ms TTL=255
Reply from 192.168.1.248: bytes=32 time=7ms TTL=255
Reply from 192.168.1.248: bytes=32 time=2ms TTL=255
Reply from 192.168.1.248: bytes=32 time=2ms TTL=255
Reply from 192.168.1.248: bytes=32 time=2ms TTL=255
Reply from 192.168.1.248: bytes=32 time=11ms TTL=255

initially it wont ping then it succeeds why ??

[Rainer Lang]

you have to do some proper network analysis - this whole story is neither a GW1000 nor a weewx issue.
And I doubt that "just out of the air" it all stopped and went wrong.
Something must have (been) changed in the network configuration.

"Upgraded the GW1000 firmware"
that means you must have used the WS View Plus app and are now on firmware 1.7.6
That also means that a mobile device inside your local network (your smartphone, tablet ...) can contact the GW1000 via port 45000 (that's what WS View Plus does)
The issue is then between your RPi, your router and the GW1000. I assume the "culprit" is your router (some of its configuration).
Can you ping the GW1000 from your router ?
Routers usually allow to issue/send ping and traceroute commands.
And can you ping your RPi from your router ?

Have you checked if your router has some special flag/option/button/tag (in fact a firewall feature)
where a specific WLAN device (here your GW1000) is allowed to communicate with other devices in the local network ?
I asked this already earlier but you didn't reply to the question

"i dont know how to get the netmask of the GW1000"

the GW1000 has received its subnet information (netmask) from your router's DHCP server
it should be correct - it's most likely 192.168.1.1/24 (or 255.255.255.0),
and the router (the DHCP server of the router) will provide the gateway information and usually names itself as DNS server
This must all be correct - otherwise the GW1000 could not successfully post to ecowitt.net

"But  the ecowitt webpage is receiving data"

that clearly tells that the GW1100 is properly connected to your router and posts to the internet

"initially it wont ping then it succeeds why ??"

something (some network element) was sleeping in your local network, it needed the ping to wake up - these things happen

If nothing works (I don't know what your infrastructure is like - is your router at the same time the WLAN access point or not etc.),
but I would suggest that you connect your router directly with a LAN cable to the RPi
(you hopefully have a more modern one which has a LAN/Ethernet interface; you didn't tell us which models you use)
and see what it gives.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/c964f7f6-77c9-44f4-bedf-03842c729ec8n%40googlegroups.com.

[vince]

On pi 1 make sure you can ping pi 2

On pi 2 make sure you can ping pi 1

From each try to ping the gateway

From each try to ping your windows box

From your windows box try to ping each pi

From your windows box try to ping the gateway

From each pi try to ping the gw1000

From the windows box try to ping the gw1000

You might also try "traceroute -n" from the pi rather than "ping -n".  If you are on the same network you should see no hops to get between any combination of the systems.   You might also try "netstat -in" on each pi.

Lastly, you might try resetting your router to clear its arp cache.

I can't speak to using Windows as I haven't needed to do so in well over two years :-)

[zasp...@gmail.com]

finally sorted it

6 months ago i made a backup copy/file of my router settings

i reinstalled the back up into the router and now the pi and hence weewx can see the GW1000

something has corrupted the router 

thanks for the advice and all the help

[Graham Eddy]

windoze xp was my last - i bet it hasn’t improved since

⊣GE⊢