Wifi doesn't reconnect in Tapo products
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
After using these bulbs and other TP-Link Tapo products (namely cameras C200 and C310), I have noticed that these never try to reconnect to wifi if the wifi connection is not available or lost at any point during operation. That might happen during startup or during use.
Customer support has suggested resetting the devices and re-linking them to my TP-Link account, but that doesn't change anything. There's a flaw in the firmware of these devices making them pretty much unusable unless you're physically next to the device when you use them. Once they lose wifi for whatever reason, you need to physically power them off and power back on to make them connect to the wireless network.
This is not an issue with TP-Link Kasa plugs, so whoever made the firmware for those, good job. This only affects, most likely, the entire Tapo product line. Hopefully there will be a firmware fix in the near future.
1) number 1
Connection topology:
Modem
RJ45 cable to AX90
Wireless connection to bulbs and cameras
No APs in between, no extenders.
This doesn't happen daily, but rebooting the router managed to take one of the cameras offline. Bulbs managed to reconnect after some waiting, but one camera remained offline. It is reachable when connecting phone/tablet to the wifi (it has no ip):
smart connect is enabled. bulbs and camera have had this issue ever since i bought them.
>does camera still get an IP from router after router reboot?
It always gets an IP address, except when it goes "offline". The devices still get an IP address even then according to the router, but it doesn't show up in the Tapo app.
>do you need to reboot router a lot, how often does the issue happen?
Router and modem stays on 24/7 usually. Reboot is required if there's a firmware update or complete power off is needed on all devices if there's a scheduled power outage.
C200 MAC B4-B0-24-67-B1-C0
Zipped diagnose_log attached (when the camera had the described issue in the previous post) if that helps.
