Topic: HP2550 Wifi Issues.

[Phil23]

For some reason I don't seem to be able to connect to my Wifi over the past few weeks.

I've seen lost connections before, but at this point I just can't get it online again.
This morning I can see 49 devices connected to my Omada Network & one's not getting an IP.
(

Got a suspicion it could be an ESP issue that I've seen with other devices.
Something to do with Multiple AP's with same SSID's.

Anyone had issues or know of a resolution?

Apparently the Wifi libraries that work correctly Scan then sort the Identical SSID's by signal strength & then use BSSID  to connect to the strongest one rather than a random from the list.

[eliteweathernz]

Hi,

I had a similar issue, I found mine would not connect to wifi following a wifi firmware update.

I reached out to Ecowitt, nothing we tried was able to bring the wifi connectivity back.
They have since sent out a new console as the wifi module on the console is now bricked/failed.

Can you see any SSIDs when you try the wifi scan function in the console settings??

[Gyvate]

when you have some sort of mesh setup, this can create issues.
When you bring your console close to your main WLAN router / access point, does it still not connect ?
Has your router run out of IP addresses for assigning via DHCP ?
Do you also use a 5 GHz WLAN with the same SSID (to be avoided) ?
If this happened after a WiFi firmware upgrade of the console, a reboot of your WLAN access point / router may help.


 

[Phil23]

When you bring your console close to your main WLAN router / access point, does it still not connect ?

It may be 3m from the nearest AP & probably 6 from the next. (Wifi congestion is bad here).

Has your router run out of IP addresses for assigning via DHCP ?

No, as most devices have reservations.
In my old age I hate Static IP's where avoidable.
Much prefer  Assigned IP's from a server so I can see where every thing lives

And not assigned by Router; DHCP is Assigned by one on by 3 Win Servers. The Server has a reservation of xx.xx.xx.232 for the console.
(This comes back to the ESP devices issues I mentioned originally),

Do you also use a 5 GHz WLAN with the same SSID (to be avoided) ?

I run both bands, but with XXXX-2G & XXXX-5G SSIDS.

If this happened after a WiFi firmware upgrade of the console, a reboot of your WLAN access point / router may help.

I do feel it came about with a firmware a version or so back, not the latest I did in the last day or so.

[Gyvate]

there were some reports in the forum in this respect. A DNS server issue was also involved. Maybe some router cache needs to be flushed and rebuilt. After a router reboot the connect would work again in a stable manner in the reported case (@hiljolodewijk).

[eliteweathernz]

there were some reports in the forum in this respect. A DNS server issue was also involved. Maybe some router cache needs to be flushed and rebuilt. After a router reboot the connect would work again in a stable manner in the reported case (@hiljolodewijk).

Hey Gyvate,
In my case I can’t even get the console to register any SSIDs in the wifi scan area.
It’s not visible to any other devices either.
Ecowitt support said it’s likely a bad partition on the wifi module and when the firmware update took place it completely f**ked it for a better word.

[Gyvate]

but at least they are sending you a replacement as far as I have understood 
shit happens ... that's the Nature of the Beast

[eliteweathernz]

Yeah they were very quick to offer a replacement which was nice, to boot it will be the new HP2560 console not the HP2550

[Phil23]

Not much more I can think of.
It is definately a DHCP issue I think as the Omada Controller confirms it's MAC & there's no IP.
That should come from a Windoes DHCP as 192.168.XXX.232

All my AP's have current firmware.
Might be a case of rebooting the lot & see;
There's 7 AP's & 3 switches in the link to the closest AP's, but if there were issues there all the other devices would be experiencing issues.

2 GW10/1100's, Airlinks, & a few other wired & Wifi devices, but all getting the Addresses from the same reservation pool.

Omada shows me this history which gives a loose indication of when the issues began.

[Phil23]

Still haven't Progreesed much on a resolution for this, but managed to roughly identify a bit of my upgrade timeline.

Looks like I downloaded 1.7.8 to my PC on 26/06/2022, would assume I installed it on the same day.
Data appears to have stopped after 5:45am on 17/04/2022.
Potentially after a power interuption.

1.8.0 was downloaded 22/04 & didn't change anything.

Cheers.

[Phil23]

Two last ditch attempts,
Added a new SSID to my Omada Network, assigned it to a single AP, etc, etc,
No change still fails to get an IP address.

2nd thing I tried was connection it to my 4G Mobile Router.
https://www.telstra.com.au/internet/mobile-broadband/prepaid/telstra-pre-paid-4gx-wifi-plus

Again, the 4G shows the EW connected by I don't think it's getting an IP as the console is still not showing the relevant connected icons.

[Phil23]

In my case I can’t even get the console to register any SSIDs in the wifi scan area.
It’s not visible to any other devices either.
Ecowitt support said it’s likely a bad partition on the wifi module and when the firmware update took place it completely f**ked it for a better word.

Mine can still scan all the Wifi AP's but just stays in the "Connecting" state on the Wifi Screen.

Think I can rule out an update causing it due to the 5:45am data stop.

Having now tried it on a different AP, I'm pretty sure the Wifi layer connection is happening OK,
it's the next layer of getting an IP address that has fallen apart.

Where do I go from here?
Request replacement & how?

I actually purchase two complete units.
This first one on 15th June 21 & a second one on 25th July 21, so both still in Warranty.

[Phil23]

Emailed Ecowitt about my issue a day or so back, Sunday maybe.

Looks like a replacement is now on it's way.
Would have to say the Customer experience so far is just superb.
No email Ping Pong, just stated the issue in detail & they seem to have dealt with it.

Will now watch to see how the tracking number moves forward.

[kheller2]

While you wait you could do a tcpdump on the windows side looking at the DHCP packets to see if you ever get a request from the weather console MAC address for an IP. 

[Phil23]

to boot it will be the new HP2560 console not the HP2550

There was no mention of a 2650 in my discussions with EW. Offered a choice of a replacement console or a GW1100.
Went with the console as who knows if the other Wireless side might fail next.

While you wait you could do a tcpdump on the windows side looking at the DHCP packets...

Was thinking along those lines, but wasn't sure where to start.
Have looked at a few means of checking now & will try if I get a chance.
DHCP Server is a Win2008R2 DC.

[Phil23]

While you wait you could do a tcpdump on the windows side looking at the DHCP packets to see if you ever get a request from the weather console MAC address for an IP.

Decided to have a look at this yesterday afternoon. Not sure yet what it means but the last lines repeat indefinately.
Dump taken from my 2008R2 Server that does my DHCP.

Code: [Select]

17:07:26.492306 40:f5:20:xx:xx:xx (oui Unknown) > Broadcast Null Supervisory, Receiver not Ready, rcv seq 64, Flags [Poll], length 46
17:07:26.492306 b4:99:ba:xx:xx:xx (oui Unknown) > 40:f5:20:xx:xx:xx (oui Unknown) Null Unnumbered, dm, Flags [Final], length 46
17:07:26.492306 00:11:0a:xx:xx:xx (oui Unknown) > 40:f5:20:xx:xx:xx (oui Unknown) Null Unnumbered, dm, Flags [Final], length 46
17:07:31.161306 40:f5:20:xx:xx:xx (oui Unknown) > Broadcast Null Supervisory, Receiver not Ready, rcv seq 64, Flags [Poll], length 46
17:07:41.293306 40:f5:20:xx:xx:xx (oui Unknown) > Broadcast Null Supervisory, Receiver not Ready, rcv seq 64, Flags [Poll], length 46

40:f5:20:xx:xx:xx Is the Ecowitt
b4:99:ba:xx:xx:xx Is My LaserJet P3015DN
00:11:0a:xx:xx:xx Is My LaserJet 2300DN

Not sure why traffic would be going from the printers to the Console, maybe just Broadcast packets.

https://www.google.com/search?q=Broadcast+Null+Supervisory%2C+Receiver+not+Ready

[Phil23]

New Console arrived today.

I assume the backup that the old one does to the SD card is not of any use?
Didn't notice a restore option.

Assume I need to just enter all required options, but also manually edit the Sensor ID's so they all appearin in the correct order as per the old Console/GW1000/GW1100.

[Gyvate]

New Console arrived today.

I assume the backup that the old one does to the SD card is not of any use?
Didn't notice a restore option.

there is no restore option - hence there is no use of this backup for restore (but maybe for other purposes depending on your use case) - I would just do a full backup and migrate the SD card to the new console

Assume I need to just enter all required options, but also manually edit the Sensor ID's so they all appearin in the correct order as per the old Console/GW1000/GW1100.

correct

[Phil23]

All done, but with one notable issue.

Wifi on the new console all connected fine & then matched all previous settings.

On going to Lat & Long, I found them defaulted in the original console.
That is a setting I definitely set as I occasionally looked at Sunrise/Set etc.

Maybe that & Wifi issues point to some sort of NVram failure in a particular area.