Topic: WeatherLink IP

[Mattk]

Yes knowing the IP address the logger is set to is 99.9% of the battle with this one, without that this would be extremely difficult

[WiFiLogger]

Yes knowing the IP address the logger is set to is 99.9% of the battle with this one, without that this would be extremely difficult

20 min.

[chooka777]

I see, I just thought the ip scanner always would find the logger ip since it's plugged into the router.

[WiFiLogger]

I see, I just thought the ip scanner always would find the logger ip since it's plugged into the router.

Problem is. You need IT help with this problem, it is really not easy.
Internet in version IPv4 work with addresses 0.0.0.0 to 255.255.255.255
There are special regions in this pool of addresses:
10.0.0.0 - 10.255.255.255 –  (netmask: 255.0.0.0)
172.16.0.0 - 172.31.255.255 –  (netmask: 255.240.0.0)
192.168.0.0 - 192.168.255.255 – (netmask: 255.255.0.0)

This range of addresses are for your own private purpose used.
I don't know why but this address 172.* is not used by router, and there is a big problem with this address, because many network devices don't recognize this address as private.

Almost all routers(home network) works with netmast 255.255.255.0 this mean that network 192.168.0.0 is ablsolutely not 192.168.5.0.
192.168.* is ok, but with 10.* now is a party

You have thousands of network to scan.

No problem, because you should scan networks 10.0.0.x, 192.168.0.x, 192.168.1.x, 192.168.16.x, 192.168.100.x + some more.
Routers are made by lazy a**'es. They are almost use 10.0.0.x, or 192.168.0.x

[chooka777]

Is their any other away around this like trying to install the logger on a different computer with the software? Buying a new logger ( hope not cause that isn't a cheap solution) or contacting Davis to maybe delete the current logger from their system and start again as if I had just bought it?

[Mattk]

Is their any other away around this like trying to install the logger on a different computer with the software? Buying a new logger ( hope not cause that isn't a cheap solution) or contacting Davis to maybe delete the current logger from their system and start again as if I had just bought it?

No this is all on your end, this is a function of inside the logger, Davis can't help with this as it has nothing to do with them and nothing they can do, there's not need to buy a new logger, this one can be fixed.

[WiFiLogger]

I offered you remote support(free). If you don't like me, call for help kid from neighbourhood.
You need to have knowladge about IP networks. Davis won't help you, because your settings are not DHCP(auto), so your logger can't send any message to Davis, which knows your home network settings.
In fact: Davis has info about your previous network info, that could help.
IP logger is trully send to Davis your network info(all). Call them.

[Mattk]

....In fact: Davis has info about your previous network info, that could help....

But that would only be the WAN IP of the router be it the ISP or DNS

[chooka777]

Thanks matt I'm at work right now hopefully later today or tomorrow if I can't follow your previous instructions clearly

[WiFiLogger]

....In fact: Davis has info about your previous network info, that could help....

But that would only be the WAN IP of the router be it the ISP or DNS

No. Davis IP logger in Packet #1(while reboot) is sending local network settings: IP local, netmask, gateway. Then in Packet #6 is sending another time just local IP.
It is not HTTP data which is addon to HTTP request. It is data inside of the message.
So Davis knows what was the last local IP of this logger.
Problem is: those info are not really legal in some part of the world.