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.
On 23.07.2023 20:43, [email protected] wrote:
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 ??
On Sunday, 23 July 2023 at 17:02:12 UTC+1 vince wrote:
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 ?
On Sunday, July 23, 2023 at 6:58:47 AM UTC-7 [email protected] wrote:
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
On Sunday, 23 July 2023 at 13:22:51 UTC+1 Graham Eddy wrote:
laptop can ping gw1000.
pi cannot ping gw1000.
can laptop ping pi? and pi ping laptop?
*⊣GE⊢*
On 23 Jul 2023, at 9:56 pm, [email protected]
<[email protected]> wrote:
i have pinged other IP address on my net work and the PI
gets response its only the GW1000 its have an issue with
On Sunday, 23 July 2023 at 12:51:15 UTC+1
[email protected] <http://gmail.com/>wrote:
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 from192.168.1.248 <http://192.168.1.248/>:
bytes=32 time=5ms TTL=255
Reply from192.168.1.248 <http://192.168.1.248/>:
bytes=32 time=3ms TTL=255
Reply from192.168.1.248 <http://192.168.1.248/>:
bytes=32 time=3ms TTL=255
Reply from192.168.1.248 <http://192.168.1.248/>:
bytes=32 time=3ms TTL=255
Ping statistics for192.168.1.248 <http://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
On Saturday, 22 July 2023 at 21:19:13 UTC+1 vince wrote:
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.
--
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 [email protected].
To view this discussion on the web
visithttps://groups.google.com/d/msgid/weewx-user/131679f4-e4fa-4c90-9baa-712b9cb14f70n%40googlegroups.com
<https://groups.google.com/d/msgid/weewx-user/131679f4-e4fa-4c90-9baa-712b9cb14f70n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/c964f7f6-77c9-44f4-bedf-03842c729ec8n%40googlegroups.com
<https://groups.google.com/d/msgid/weewx-user/c964f7f6-77c9-44f4-bedf-03842c729ec8n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/2370ddfa-76f3-d769-e5aa-f06cd592970a%40gmail.com.
