
- #Tcl roku tv mac address bug update#
- #Tcl roku tv mac address bug upgrade#
- #Tcl roku tv mac address bug windows#
I moved her phone to the 5Ghz network too, but the problem remained. Then my wife got home, and as soon as she got in, the switches started to flash the green light. When I moved my phone to the 5Ghz only (leaving all the Kasa devices on the 2.4Ghz), all the devices connected quickly and worked perfectly. I realized that my phone was causing the problem (Samsung S20). Playing more (wifi analyzers, static IPs, optimal channels, etc.) eventually led me to the solution (for me at least). After playing around a lot with both the devices and the network, the conclusion was the problem was the network and not the devices.
#Tcl roku tv mac address bug upgrade#
Unfortunately for me the upgrade never worked and I was stucked with the situation.
#Tcl roku tv mac address bug update#
The common solution I found was to update the firmware to the beta version provided, using the tool linked in those pages. I looked quite a bit online and I found several posts here on the forum with similar problems (I posted this in a couple of different threads to reach more people). They were never "available" on the app and constantly looking for the connection, blinking green.

I had 4 smart dimmers (HS220) and a power switch (HS300) that started to give me a lot of problems. POTENTIAL SOLUTION Hello, I recently had the same issue. Personally, I hope TP-Link offers rebates or refunds to all of us that had to hack our devices online properly. This was one of the more awful setup experiences I have had with a smart home device. This way the firmware updated and it prevented any reboot loop problems. With the replacement one, we skipped the normal setup and went straight to these instructions straight out of the box (using the hotspot). We ended up returning that switch and replacing it with another. The reset button never worked for us for this switch - it was rebooting every 10-15 seconds, which was too soon for the factory reset to take over even after we turned off the offending wifi router (an Xfinity cable modem). We didn't know about the nonstop rebooting bug, and went through the setup wizard, which failed at the end of course, and got stuck in the endless reboot loop. However - we got fully completely stuck with the first switch that we purchased.
#Tcl roku tv mac address bug windows#
We didn't have to use the Windows update tool to upgrade the firmware. In fact, the switch auto-updated to the correct firmware edition once we were able to get it set up, using the double hotspot situation. Thank you This is the solution that fixed our setup issue. House is only 2 years old so its very modern wiring. If anyone has any suggestions or insights I'm game to try. I'm going to try to connect them to a different wireless network all together (hotspot'ed iphone) to see if it is indeed the network they're connecting to that is the issue. I don't have any LG but I do have 3 TCL Roku TVs. I saw in another thread where someone has HS220 V2 issues when connected to the same network as an LG TV. Network is a 4 access point system, TP-Link EAP245 (3x V1 and 1x V3 HW) Wireless Access points, powered by an 8 Port TP-Link POE Switch. Additionally I have an indoor and outdoor TP Link Kasa Cameras. I have two Smart Plugs and 4 HS220 HW Ver 1 smart dimmers. Now like many others, I have several other TP Link Kasa smart gear. With the green/amber flash of the wifi logo in the out-of-box state, the switch and dimmer functions correctly as expected and the switches do not constantly reboot.Īll goes haywire as soon as they are connected to my Wireless network. Surprisingly, the switches work just fine NOT setup to wifi. Until i get to do that tomorrow, I did a factory reset. I double checked neutral and ground lines are making good contact and secure with wire nut.Īfter a long chat session with TP-Link support, we're going to try them in a different single pole switch. I've double checked my wiring and all connections are to the correct lines (ground, neutral, hot/line, load). Both are exhibiting the same constant rebooting flaw.

I commented on an old thread but wanted to start a new one to see if anyone has a solution.
