Why does my Deco P9 mesh (or the Deco app) have such a bad memory?
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
When I first set up my Deco P9 mesh I was really impressed by the fact that I could see which clients had connected to which nodes, how much bandwidth was being used, etc. But now I just don't trust these details at all. Firing up the Deco app shows that my girlfriend's iPad is connected to one node, yet she has been away from the house visiting her mother for the past four days. I also see that one of my Ring cameras is connected to the same node, yet it was reconfigured to connect to a totally separate (non-mesh) 2.4GHz AP in the garage last weekend. My iPhone (which is barely 5' from the main node) is showing as being connected to one of the slave nodes and a Wi-Fi dimmer that I sold on eBay weeks ago is still showing as being connected!
C'mon TP-Link, get this app sorted!
@TP-Link Thanks for the quick reply. The problem doesn't appear to be app related. I refreshed the app on my iPad and the outdated list of connected clients remained unchanged. I then switched over to my iPhone and I see the same behaviour, though different client lists are displayed on the iPhone and iPad. I then tried to reboot the main Deco via the app and received the error message below. Attempting to reboot the two slave units also results in the same error. Switching from the iPhone to the iPad didn't make any difference. It would seem that the only way to reboot the Decos is by cycling the power. Is there anything else you would like me to try before I power-cycle the Decos?
