lg-washer-keeps-dropping-wifi-connection-solved/

[utterances-bot]

LG Washer keeps dropping wifi connection, solved!

https://wasteofserver.com/lg-washer-keeps-dropping-wifi-connection-solved/

[tsrubar]

Reading through this, I'm not sure I have the same problem. The WiFi light is not on and I do not receive notifications of the cycle finishing. However, I am able to remote start, pause, set options and get status for the entire time. So it appears the WiFi is working but the light is not lit. Anyone else have that problem?

This really is different. In my case, indicator on washing machine is off and in all it is in status Disconnected and isnt possible to do anything with it.

[frankielc]

Hi @nuc4and20, that story is incredible. And your hypothesis for the washer makes perfect sense. I've gone the way of the original post, as described on https://wasteofserver.com/lg-washer-keeps-dropping-wifi-connection-solved/ and I'm having a crash every 3 to 4 months on an isolated network.

Between phones, lights, ESP32, etc I've got 45 devices currently connected to the network (per pfsense DHCP server).

Do let us know how it works out for you using the method of flipping wifi's!

[frankielc]

@weirdwanda I think that's by design. Mine is the same. Attached image of panel.

[enygren]

My washer worked fine until it stopped connecting. Separate SSID and new firmware doesn't seem to help. Doing a tcpdump shows that it tries to make a TLS connection to the cloud service and the handshake fails. I wonder if the washer has a time synchronization issue so is failing to validate the server certificate?

[frankielc]

Hi @enygren! That's a new one. Thanks for reporting. How long have you been experiencing that? Mine is working as expected, with the needed reset every once in a while. It actually hasn't failed in the last 7 months. Let's see how long it will go this time.

[nuc4and20]

My washer and dryer were put on a separate VLAN and SSID on 3/22. So far so good. I tried a separate SSID on the same subnet and it failed in a couple of weeks. I think the VLAN is the answer. A VLAN is a broadcast domain. Every station in a broadcast domain sees all the broadcast traffic (a completely normal part of Ethernet and Wi-Fi). I think our problem is that the washer's driver software uses memory to keep track of who's-who and doesn't release the memory after some suitable time. On an Ethernet switch, MAC table aging time is typically 300 seconds. Switches run for years without exhausting the memory pool. By limiting the number of devices seen in the collision domain, the VLAN limits the number of addresses to keep track of. If we were using a Cisco switch, I would use the command "show mac-address table" to see how many device entries are in the table. Maybe someone has a wireless adapter that Wireshark can use to monitor the WLAN.

[frankielc]

Couldn't agree more @nuc4and20! I should have made that explicitly clear on the original post. Different SSID but also different subnet. Currently on holiday, but will fix it (and credit you) when I get back. Thanks!

[enygren]

Mine worked fine for perhaps 2-3 months then earlier this year it stopped connecting. Trying to reconnect it or switch its network fails with "NS". Looking at a tcpdump, it has an IP address just fine and tries to make a TLS 1.2 connection to "common.lgthinq.com" but aborts the connection with a TLS Alert 21 during the handshake. (Looks like the server cert is an OV wildcard valid from 2020-07-20 to 2022-10-18 using a KICA root.)

[jmcivil]

Thanks for the great thread...I have a relatively new LG washer/dryer...like others the dryer connects fine but the washer drops after a day or so...power cycle is the only way to get it back. my firmware is 6.41 and V1.9.168_RT which seems to be newer and still has the issue...installed dedicated access point and SSID - same issue...haven't tried VLAN or fixed IP...guess I will try that next and open case with LG...I do have a lot of IOT devices on my LAN so perhaps this is some limitation in the IP stack of the washer it is encountering as suggested...all suggestions welcome!

[finder39]

Can confirm this is still happening with 6.43. I just moved it to its own SSID and subnet for the first time. Will report back when it fails again

[nuc4and20]

My 'private' WLAN with its own SSID, VLAN-subnet with only two clients is at 90 days without a problem.  Got my fingers crossed that your new setup will be just as solid.  Nick

[jmcivil]

Just thought I would share - since my unit was new I scheduled a service call. The Tech arrived and I explained what was going on - he instantly shared that it was a known issue and there was no fix...he logged the ticket with the details. I am moving on to trying a dedicated VLAN...

[ghost]

Yeah, I’ve had mine on a network in which it can’t see or talk to anything else. Been solid for 6 months without an issue.

Sent from my iPhone

On Jun 28, 2022, at 3:15 PM, jmcivil @.***> wrote:

 Just thought I would share - since my unit was new I scheduled a service call. The Tech arrived and I explained what was going on - he instantly shared that it was a known issue and there was no fix...he logged the ticket with the details. I am moving on to trying a dedicated VLAN...

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[frankielc]

@bulldozer73 I have to be more specific about it being a dedicated network. The way it's written, people get the feeling it's just a matter of changing the SSID. Nonetheless, even on a dedicated VLAN it will fail; nonetheless it sure is less annoying.

@jmcivil thanks for the info. If the technician says there's no fix available should be something down to the hardware used. Just makes me wonder what kind of testing was done in-house to let something like this slide.

[truerock2]

I've been wrestling with my wife's new LG washer WT7400CV and dryer DLE7400VE. I assumed that the IOT Wi-Fi on those 2 LG products would be unstable - because most IOT devices are unstable. The LG washer and dryer do not use registered MAC addresses and they do not broadcast host names. The LG products are obviously a pathetically implemented piece of technology.

Anyway, I have the washer stable and accessible via the LG ThinQ app. The dryer Wi-Fi drops about every-other day.

I've supported and developed thin-servers and thin-networks for decades. The idea that thousands of manufacturers would somehow get their various IOT technologies to work together was completely ridiculous and I feel bad about the millions of hours consumers have wasted on IOT. Even looking at Apple products - where they obviously do not cut corners on their implementations - it's obvious that Apple does not understand what good thin-product design would be.

But, there is good news. There is a consortium developing standards that I know will have a positive impact on IOT - it's called Matter:

https://csa-iot.org/all-solutions/matter/

I am not buying any IOT tech unless it just comes built in with whatever TV or refrigerator, etc we happen to be buying. IOT barely works and essentially does not work. I do think rhat the situation will become better in the near future.

So if you enjoy tinkering with tech - like I do - it is interesting to look at how a LG washer/dryer support Wi-Fi connectivity. I don't expect it to actually work.

[nuc4and20]

I don't expect it to work, either, It's not like WiFi allows me to do anything important. But still, it's nice when stuff works. And it has been fun figuring out what's going on. I'm surprised that your washer is stable and the dryer is unstable. This is the opposite of what we've been hearing. So something changed at LG although the QA department is still blissfully unconcerned. Two thoughts:

1 - When I was working in warehouses, trying to get Symbol handheld scanners to work with Cisco APs, our wireless engineer (a CCIE and all that and a really bright guy with tons of experience) told us that the driver for the WLAN card in the scanner was critical and they were notoriously difficult to troubleshoot. But we kept on buying the gear and making do. Has anyone returned an LG product because WiFi doesn't work? I doubt it.

2 - The "Things" part of the internet has always been a wild place. We had a firewall between our business network and our process information network (where the Things lived.) It was not there to protect the Things - they were the problem. There were dozens of viruses on the process information network and we never succeeded in removing 100% of them. Techs with thumb drives kept bring the viruses back in. The process engineers dealt with this by hardening their devices or even removing them from the network. Perhaps nobody expects the stuff to work very well.

My "WasherFi" network is 2.4GHz-only, on its own VLAN, has two client devices and has been solid for 131 days so far!

[SpencerLN]

Mine worked fine for perhaps 2-3 months then earlier this year it stopped connecting. Trying to reconnect it or switch its network fails with "NS". Looking at a tcpdump, it has an IP address just fine and tries to make a TLS 1.2 connection to "common.lgthinq.com" but aborts the connection with a TLS Alert 21 during the handshake. (Looks like the server cert is an OV wildcard valid from 2020-07-20 to 2022-10-18 using a KICA root.)

@enygren I've been having the exact same issue since earlier this year - same TLS alert during the handshake. Any chance ever found a solution for this?

If anyone else happens to stumble upon this, I eventually created a new LG ThinQ account and the washing machine magically worked when connecting to that new account. There must have been something account specific going on server-side where the LG server was rejecting the connection from the washer. Fwiw, my LG dryer continued to work fine the entire time on the old account.

[leoshusar]

I've got new AC PM09SP and I couldn't connect it to my IoT network at all. UniFi showed it got IP but then ThinQ failed to communicate with it.

What for some reason helped for me, was just changing the subnet IP from 192.168.2 to 192.168.X (not even 1), as soon as I changed the number and reconnected it, it got new IP and worked for several hours now without dropping.

I have noticed that when it was on the 192.168.2 network, tcpdump showed it didn't even try to communicate with servers. It just got IP and then complete silence. UniFi showed it's still connected and I could've ping it, but the ping times were around 1000 ms. As soon as I changed the number from 2 to 3 or 4, it worked 100%. Even completely different subnet like 10.0.2. Ping times now are <5 ms.

I don't have any firewall blocking on the 2 subnet and my firmware is clip_hna_v1.9.168. I'll see how it goes from now, but it looks promising. I'm glad I don't have that many IoT devices yet with fixed IP so this was easy change.

And one more thing I noticed, when it was on the 2 subnet, UniFi showed Tx Rate 1 Mbps. Now it's 72:72 Mbps.

[truerock2]

leoshusar,

That is extremely interesting information.

As we know, the 192.168.1.xxx subnet is the subnet used by default for almost all local home networks. I think 192.168,2,xxx is often used by default for a parallel subnet for things like network device administration. Also, I'm guessing a lot of IOT devices are thinking they want to use 192.168.2.xxx for a separate subnet - but, obviously there is a possibility that other devices on the network are also thinking they are going to use 192.168.2.xxx for their own purposes - and, that might cause a conflict between various devices on the network.

Perhaps if it were possible to organize a home network so all the LG IOT devices were on one subnet and all the Samsung IOT devices were on a different subnet and all of the Apple IOT devices were on their own subnet, etc. - perhaps that would make IOT work better?

Perhaps this is one of the reasons IOT technology is unstable?

[nuc4and20]

leoshusar,

I don't think the subnet address is part of this problem. My "everybody" WLAN (and wired network, too) uses the 192.168.123.0 subnet. My washer dropped the connection after about two weeks. There are about two dozen devices on that subnet at all times.

My "WasherFi" WLAN uses 192.168.143.0 subnet on VLAN143, tunneled from the AP to the router. Only the LG washer and dryer use this VLAN. The connections have been stable for 198 days so far. But FRANKIE reported that his VLAN solution crashed after 10 months, so we'll see.

When I used a separate D-Link router/switch/AP, it had 192.168.0.0 subnet. The connection never dropped but I wanted a more "elegant" solution, like a REAL network with VLANs all that. :-)

When the LG App is first configuring the wireless connection I think it uses a fallback address for a temporary local connection, I think Franie said it was 192.168.1.80. But the app handles that: it connects the phone Wi-Fi to the washer Wi-Fi, hands off your WLAN name and password, disconnects from the setup mode and reconnects through the cloud to the washer (which has has shifted to your wireless subnet.) At that point, it's on whatever subnet you use and if there are a bunch of other users, it seems to drop out in about two weeks.

I wonder what was going on with the 192.168.2.0 network...

[bltg0]

Thank you for this post. I upgraded to LG washer & dryer separates months ago and I've been plagued by this issue since day one, but for some reason, it only affected the washer -the dryer and later purchased dishwasher have never dropped their connections. Reading this post also made me wonder if a similar issue i've been experiencing with other devices like 2 Levoit humidifiers and my Tonal home gym could have been due to the situation you described. My previous router setup includes 3 eero pro's in mesh config, but had also read that Tonal does not work well with mesh systems, so I set out to implement a less elegant solution: Add a separate stand-alone wifi router configured with its own SSID. This new wifi network would coexist with the eero network and would be dedicated to providing connectivity only 4 devices: the LG washer, 2 humidifiers & Tonal gym. I also reserved 192.168.1.80 for the washer. Having made these changes almost a week ago I have not had any connectivity issues on any of the 4 devices since - normally they would seem to drop connection within 30 minutes ofter being plugged into main power. I also took other steps to ensure connectivity: of the 4 devices being served by my new network, tonal is the only one requiring high bandwidth, so I installed the router is the same room as tonal and connect it to the 5GHz band, the other 3 devices are on other levels of the home, so those are connected to the 2.4GHz band. Even if I have to reboot devices periodically, Im still happy with this solution as its infinitely better than the prior state of things.

[frankielc]

Hi @bltg0 your issues with the other devices do look pretty identical to the one described with the LG Washer. If your network system allows for VLANs - where you can make usage of traffic isolation - that would be the ideal setup, as you could place each of the faulty IoT devices in its own "world" with as little traffic as possible. Very glad it helped!

[bltg0]

Hi @bltg0 your issues with the other devices do look pretty identical to the one described with the LG Washer. If your network system allows for VLANs - where you can make usage of traffic isolation - that would be the ideal setup, as you could place each of the faulty IoT devices in its own "world" with as little traffic as possible. Very glad it helped!

I know a VLAN setup would have been ideal, but honestly I just wanted to eliminate the eero APs from the equation, they already caused me too much time and frustration..Also Im not sure they support the kind of VLAN config that would have been necessary. Also given that the problematic devices don't ever change location, I didn't need them to have mesh connectivity that eero is really great at providing. Im using a much less expensive Nighthawk router for my secondary network and its doing a great job...full signal strength everywhere. Thanks again for the great resource you shared!

[JSracer]

have been fighting this for months, wifi light will drop off the washer powering on. strange the application shows status, and all the information, i had the washer/ drier on a guest network, but after reading this, the washer now is solo on its own isolated guest network. router is a asus ax86u, washer is a WM4500HBA that's a couple months old. I'll see if isolating helps, it has always been on a guest network, started with isolated cams, then different with intranet for other devices on that guest. now its solo, no intranet. dryer seems good, but occasionally wont notify, or keep track of previous cycle. I do have other routers i can utilize if needed, ac86u, n66u, and a glinet beryl I travel with. I'll keep in mind setup a new lg account, if still fighting things. my main subnet is 192.168.2 . was going round and round for 5 weeks with 1:1 chat.. sigh.. lol (not sure if my washer is the same, or chasing the same issue, wifi light drops out after X time, but the application shown washer status and all the connected information. heck can hold the remote start and that works. just no wifi light... and if I hold the button on the machine for wifi it will ding after a few seconds, but the light does not turn back on. reboot router I think gets it back, yesterday light was off for the first load, no notification, and no sync load for the dryer setting, but the app showed remaining time and all of that stuff.. 2nd load was fine, light on, working as designed... washer sat unused since earlier in the week.. not sure if this is the same problem as others, or if the application says disconnected, mine never has said that)

[frankielc]

Hi @JSracer,

Don't give the LED light too much attention. As you can read above, the main issue really is with the machine disconnecting from Wi-Fi and not connecting again.

As you say, the issue happens when on the App you see the machine as "disconnected" and, whatever you do - plug it on/off - it just won't reconnect to Wi-Fi unless you do a hard reset.

Nonetheless, it may help your case. Do keep us posted! ;)

[truerock2]

Reading some of the latest posts to this thread.

I'm thinking perhaps this issue is related to ThinQ connectivity to LG servers.

My LG appliances spoof their hostname, ip address and MAC address - so, it is very difficult to track the cause of the disconnect problem. My Linksys router isn't able to handle the LG appliances as just normal clients. The Linksys router is just noting a stub it logs as "networkDevice" - I think. I think the LG appliances are using my Wi-Fi network as anonymous, untrackable devices.

I do notice that the LG servers are not able to keep the usage log up to date. The LG server-side logs miss something like about 10% of the time the dryer or washer are used. So, maybe the LG servers go off-line and the LG appliances shut down their wi-fi connection?

[enygren]

I did manage to fix the issue by fully deleting my washer from the app (and thus from ThinQ) and following through some of the reset instructions and then re-adding. I haven't had issues since (but still have a separate SSID only used by the washer and a few other devices).

[JSracer]

I did manage to fix the issue by fully deleting my washer from the app (and thus from ThinQ) and following through some of the reset instructions and then re-adding. I haven't had issues since (but still have a separate SSID only used by the washer and a few other devices).

So from the app, delete the washer.... then did you power cycle the washer for the reset? Then you added the washer again to the application?? Just trying to get a game plan if / when it acts up again.. (what were your symptoms before this?) Thanks!

[nuc4and20]

I think this still fits the "separate VLAN as well as separate SSID" solution. A physically separate network, like when I had a D-Link router with its own subnet and SSID mounted over the laundry machines, or a VIRTUALLY separate network with separate VLANs and subnets for the laundry, IoT devices, general users like my Ubiquiti network seem to work equally well. If I'm right about the nature of the problem, solution is to give the LG washer the smallest possible collision domain (the fewest devices). Once I separated the traffic, my problems went away. VLANs are just a more elegant way to do it. And it's been fun figuring it out. 

Nick

[nuc4and20]

I meant to say BROADCAST domain, the part of the network below the router, i.e. a subnet or VLAN.

[leoshusar]

I'm just coming with an update after 2 months. My solution I wrote about was changing the VLAN subnet from 192.168.2.0 to something different and... I haven't seen single drop since then, and if it dropped, it recovered itself without me noticing. Unifi says 3 weeks uptime (I updated and rebooted my AP 3 weeks ago). But my AC is logging temps into HA without any problems. I went from not working at all to no issue at all.

I was also checking my network multiple times if I maybe had some forgotten firewall rule that would block something on 192.168.2.0 network, but nothing. I have Unifi router so I can SSH into it and print every active configuration and then grep that IP, still nothing. I'm not saying the subnet number is the 100 % reason, just that after I checked everything I thought of, I didn't find anything in my network.

So, it currently has IP 10.0.2.6 and it's happily connected to my IoT VLAN with (so far) 12 other devices.

[dmelgar]

I've having similar issue. However it is NOT an issue with WiFI but an issue with the LG washer connecting to its servers. I can continue to get status from the washer even when it shows offline, but it will not send notifications. I have to reboot the washer almost every time I use it to get it to connect to LG servers. I'm disappointed that LG hasn't fixed this. I reported it to LG a year ago and tried to work with them to solve it, but it never went to engineering. Support managed to drop the ball.

[nuc4and20]

David,

Can you give some details on the situation? You say WiFi is not the issue:Is the WiFi icon lit on the washer control panel when it can’t connect to the LG servers? Can you ping the washer’s IP when it loses contact? Is the washer on its own VLAN (and SSID)? My washer has been trouble free since set up the separate VLAN (and SSID). It’s been quite a few months since I’ve had a connectivity problem.  

Nick

[verdi1987]

I recently started experiencing this issue with my WashTower after getting a new Asus Wi-Fi 6E router. I previously had a TP-Link Wi-Fi 5 router. In both instances, the washer was the only device on a separate 2.4 GHz network. The router is adjacent to the washer.

I am experiencing a myriad of issues. The ThinQ app would complain that the washer had no network connection, the on/off status of the washer was incorrectly reflected in the app, the cycle status was wrong, the app claimed washer was busy with another task, or the completion notification never arrived.

I then changed the network to an old AirPort in bridge mode (with the Asus still managing traffic), again with the washer on its own 2.4 GHz network, but the problems persisted.

In every instance where the app complained the washer lacked a network connection, the router showed it was indeed connected and had a strong connection.

Now I’m wondering if it’s not the router. Could it be the app? It was recently updated. Could it be that I was sharing the Home in ThinQ? I’ve since stopped sharing. Could it be because I gave it a fixed IP? It previously did not have one with my TP-Link. I’ve reverted it to a non-fixed IP.

I can go back to my TP-Link to see if that helps.

[frankielc]

@verdi1987 if you want to have a shot at debugging the root issue, try to isolate things and stay away from meddling with 3rd variables (like inserting the AirPort into the equation). I believe that yes, you should go back to the TP-Link to see how it behaves and go up from there.

[nuc4and20]

Can you give a few details of the network setup?

Is the “separate 2.4 GHz network” just a separate SSID or does it also include a separate VLAN with a different IP subnet (and, of course, a different gateway?)

Is an AirPort in “bridge mode” acting as an AP and using the IP address range as configured on the router?  

I think that if the AirPort is plugged into your router but in “normal” configuration with its own DHCP server and its own IP subnet that this might fix the problem.

When I first had the problem with my LG washer, I tried separate SSID, static IP address, etc. without success. I had a D-Link DIR-866L wireless router lying around and I plugged it into my main router and setup a separate network for the washer and put it in a cabinet by the washer.

Different SSID, different IP subnet and gateway. Problems went away. I thought it was a clumsy solution, so I finally figured out how to put VLANs on my Ubiquiti EdgeRouter X and give each SSID on my Ubiquiti Cloudkey its own address space. Works great.  

There is a fundamental bug in the LG washer’s WLAN card such that the card can’t handle listening to the ‘normal’ traffic on the network and after a while the MAC table on the card consumes all the memory and the card stops working. But this is not really a WiFi issue. It’s a network issue. The network just happens to be wireless.  

Nick 

[verdi1987]

Is the “separate 2.4 GHz network” just a separate SSID or does it also include a separate VLAN with a different IP subnet (and, of course, a different gateway?)

It’s just a separate SSID. A separate VLAN will be my next course of action if the issue persists.

Is an AirPort in “bridge mode” acting as an AP and using the IP address range as configured on the router?  

Correct. It’s acting as an access point with all management done by the router. The reason I connected the washer to it was to try to eliminate the Asus as the problem.

I think that if the AirPort is plugged into your router but in “normal” configuration with its own DHCP server and its own IP subnet that this might fix the problem.

Thanks. I will try this. For the time being, I’ve restored my previous config using the old TP-Link.

[verdi1987]

I went back to my TP-Link, and the Wi-Fi issues with the LG washer evaporated. I guess I’ll be sticking with TP-Link.

[frankielc]

Very peculiar @verdi1987. It obviously won't be a brand preference... so something must be different.

I'm assuming it's a 2.4GHz wifi network.

Is the encryption the same on the TP-Link and the others? This is obviously a completely different issue than the original one.

[verdi1987]

2.4 GHz and same encryption. I also tried every encryption standard with the Asus.

[frankielc]

2.4 GHz and same encryption. I also tried every encryption standard with the Asus.

Interesting @verdi1987. I guess you probably don't feel like wiresharking it to the packet level to try and see what's messing with the network card, and I can relate. I'm glad, at least, things are working for now.

[verdi1987]

Interesting @verdi1987. I guess you probably don't feel like wiresharking it to the packet level to try and see what's messing with the network card, and I can relate. I'm glad, at least, things are working for now.

I was thinking of sniffing the network, but I’ve since returned the Asus. Incidentally, I replaced the TP-Link Wi-Fi 5 router with a TP-Link 6E router, and it continues to be problem-free.

With the Asus, in addition to the issue with the LG washer, I experienced a somewhat similar issue with my Onkyo receiver. The receiver is connected via Ethernet to a switch. The Onkyo app would regularly fail to connect to the receiver when I had the Asus. As with the LG, things returned to normal upon switching back to the TP-Link.

I wonder if there was perhaps some multicast flooding happening with the Asus.

[frankielc]

Thanks for the extra information @verdi1987. May be useful to someone googling by!

[droopdog7]

Seems like I am kinda late to the party, but I've been researching like crazy for anything that can describe the issue I am having with my new LG appliance. But for me, it is my dryer that continuously drops the wifi signal. It stays on for about 45 seconds and then turns off for about 10 seconds. Does that all day long.

I just got the dryer less than a week ago, so the solution for me would seem to be straightforward (have Best Buy give me a new one). Unfortunately I got an open box dryer that was nearly half off. Best Buy will absolutely come get it and give me a new one, but I need to pay a new one price. Forget that.

I can find an open box one at a store but unfortunately I would need to drive to the store. And they won't honor the price I paid for the one I have. So anyway, I have an LG servicer coming by tomorrow. Hopefully they don't break my new machine.

[frankielc]

Hi @droopdog7, during the 45 seconds it's on, does it communicate properly with the servers? Can you use the LG app without issues?

[droopdog7]

It communicates while connected, but the disruption is well, disruptive. For instance, I tried multiple times to update a feature and couldn’t because it would disconnect before the update was done. Same for making other changes. If I can’t get them done in that time frame I get kicked out of the setting.

So to answer your question, technically possible but a hassle.

[frankielc]

@droopdog7 that definitely makes it unusable. It's a completely different problem, but please do keep us updated.

[droopdog7]

@droopdog7 that definitely makes it unusable. It's a completely different problem, but please do keep us updated.

@frankielc Figured I would return to give a final update. As it were, an LG tech came out and replaced the the part with the network card and it now works flawlessly. Doesn't help as far as the core issue, except I guess to speculate that the one I had was busted.

[steviloidz]

@droopdog7 how is it behaving now you have the part changed? Can you constantly ping the dryer even when it's on standby? Your issue sounds similar to mine (although it's a washing machine). If I power the washer on it'll be connected OK for a variable amount of time. When the washer is off it seems to put wifi to sleep, I can't ping it, when I power it back on it sometimes wakes up but often doesn't. I've tried Frankie's suggestions above and put it on it's own AP\SSID etc... (Thanks for maintaining this page by the ways Frankie!)

[droopdog7]

@frankielc Dryer has no issues at all. Doesn't matter if on or off, I can ping the dryer. I supposed I just had a bad network card.