@DeanGibson 

I'm experiencing the same issue and even got my netgear gateway device replaced in case it was the problem. I can't connect smart plugs without the SSID disappearing from my phone and crashing the devuce. However I noticed if I link my gateway to my old TP Link router it is able to connect the plugs just fine. Which is annoying because the whole reason I bought a gateway device was to upgrade from my old modem and router devices!

Hi folks, am having the exact same issue with my two KASA HS303 smart power strips and trying to connect them to a Netgear AX3000 RAX40 wifi router. 

I have tried to connect each of them one by one, but both of them cause my router to completely crash. I have to factory reset the power strips in order for my wireless SSIDs to come back up and stop the router from constantly crashing and rebooting.

Is there any fix for this? I have so many other smart plugs, smart speakers and so forth (mostly running on the 2.4ghz band) and they've never caused any router crashes. 

Although I do believe the router is partially to blame, but has anyone else managed to get these things to connect at all?

@itsmehuey I've not been able to fix.  Return back to Bestbuy and got another brand which is working fine.

@CptKebec you replaced the power plugs or did you replace the router? It seems in my case that the culprit is the Netgear RAX40 router.

@phiebing I am having the same problem with the blue cave wifi router. i get the system log

Oct 12 19:40:03 kernel: [  660.180000] 
Oct 12 19:40:10 logserver[1308]: [2822690715] [_parse_log:1180]: wlan0: Fatal Error in file: "TsManagerRecipient.c"; Fatal Print: TS Manager Recipient Fatal
Oct 12 19:40:30 logserver[1308]: [2842893146] [on_sigterm:830]: Received SIGTERM: shutting down
Oct 12 19:40:30 logserver[1308]: [2842893432] [main_loop:470]: Waking up to process signal
Oct 12 19:40:30 logserver[1308]: [2842898088] [main:1375]: Terminated
Oct 12 19:40:30 kernel: [  687.240000] [MTLKD] Unloading rtlog_netdev
Oct 12 19:40:32 kernel: [  689.030000] [MTLKD] Allocated netdev rtlog0 addr 7a0f8000
Oct 12 19:40:32 logserver[14289]: [2844773765] [main:1277]: Lantiq Log Server v. 5.4.0.0.105.exported.be31e448a865.REL_5.4.0
Oct 12 19:40:32 logserver[14289]: [2844774576] [main:1296]: Port not specified. Assuming default: 2008
Oct 12 19:40:32 logserver[14289]: [2844774833] [create_mother_socket:72]: Binding to all interfaces on port 2008
Oct 12 19:40:32 logserver[14289]: [2844775221] [main:1332]: Using string configuration data file: /tmp/fw_scd_file.scd
Oct 12 19:40:32 kernel: [  689.380000] [MTLKD] PCIE bus ChipID is:0x0810 address is:0xf837c060
Oct 12 19:40:32 logserver[14289]: [2845187501] [main_loop:462]: No connections - going to sleep
Oct 12 19:40:33 kernel: [  689.950000] [cbm] { cbm_queue_flush : 3647 }out QOCC 0
Oct 12 19:40:33 kernel: [  690.000000] [MTLKD] PCIE bus ChipID is:0x0810 address is:0xf437c060
Oct 12 19:40:33 kernel: [  690.580000] [cbm] { cbm_queue_flush : 3647 }out QOCC 0
Oct 12 19:40:59 kernel: [  715.950000] 
Oct 12 19:41:08 kernel: [  725.880000] 

Then my internet stops working and have to reset both modem and router

zacman95 wrote

@phiebing I am having the same problem with the blue cave wifi router. i get the system log

 

Oct 12 19:40:03 kernel: [  660.180000] 
Oct 12 19:40:10 logserver[1308]: [2822690715] [_parse_log:1180]: wlan0: Fatal Error in file: "TsManagerRecipient.c"; Fatal Print: TS Manager Recipient Fatal
Oct 12 19:40:30 logserver[1308]: [2842893146] [on_sigterm:830]: Received SIGTERM: shutting down
Oct 12 19:40:30 logserver[1308]: [2842893432] [main_loop:470]: Waking up to process signal
Oct 12 19:40:30 logserver[1308]: [2842898088] [main:1375]: Terminated
Oct 12 19:40:30 kernel: [  687.240000] [MTLKD] Unloading rtlog_netdev
Oct 12 19:40:32 kernel: [  689.030000] [MTLKD] Allocated netdev rtlog0 addr 7a0f8000
Oct 12 19:40:32 logserver[14289]: [2844773765] [main:1277]: Lantiq Log Server v. 5.4.0.0.105.exported.be31e448a865.REL_5.4.0
Oct 12 19:40:32 logserver[14289]: [2844774576] [main:1296]: Port not specified. Assuming default: 2008
Oct 12 19:40:32 logserver[14289]: [2844774833] [create_mother_socket:72]: Binding to all interfaces on port 2008
Oct 12 19:40:32 logserver[14289]: [2844775221] [main:1332]: Using string configuration data file: /tmp/fw_scd_file.scd
Oct 12 19:40:32 kernel: [  689.380000] [MTLKD] PCIE bus ChipID is:0x0810 address is:0xf837c060
Oct 12 19:40:32 logserver[14289]: [2845187501] [main_loop:462]: No connections - going to sleep
Oct 12 19:40:33 kernel: [  689.950000] [cbm] { cbm_queue_flush : 3647 }out QOCC 0
Oct 12 19:40:33 kernel: [  690.000000] [MTLKD] PCIE bus ChipID is:0x0810 address is:0xf437c060
Oct 12 19:40:33 kernel: [  690.580000] [cbm] { cbm_queue_flush : 3647 }out QOCC 0
Oct 12 19:40:59 kernel: [  715.950000] 
Oct 12 19:41:08 kernel: [  725.880000] 

Then my internet stops working and have to reset both modem and router

@zacman95 i got mine working finally.. netgear released a firmware update (albeit a beta firmware) for me to test and now the router no longer crashes when i try to establish a connection. am able to fully get the smart power strips to connect and can control the individual outlets on the power strip.

@zacman95 I have a Asus Blue Cave router and experienced the same issue as you with a log that looks very similar.  I updated the router firmware and still had the issue.  The smart plug would try to connect, then all connected clients would get booted off then try to get back on and then the router would crash necesitating a restart.  I was also having intermitant connectivity with Meros smart plugs.  Anyway, I just bought a new TP link router (no this isn't an advertisement) and everything connected just fine.  Maybe my router was just getting old???

@DeanGibson 

I have the V3 version of the smart plug and a TPLink Archer C2700.  Same problem with default settings.  Reported this to TPLink support 5 months ago.  No firmware updates have been made available.  I also have a newer phone.  Seems like the plug acquires the Wifi connection info but whatever is in the exchange between the plug in the router causes the router to self protect or something and shuts off the 2G wifi.

@jasondabsher Wish I had found this thread when I was searching about this product.  Just crashed my whole network.  Not worth the headache and am taking back tomorrow.