Smart devices randomly go offline and back online from hour to hour
Have “Trashcan” version of T-Mobile Gateway attached to TP-Link M55 3 Mesh Router system. Suspect that CGNAT to NAT connections is causing smart device (WIFI) addressing issues to come and go from hour to hour on M55 Mesh Router. I have an Orbi 2 Unit Mesh router from our previous condo and have switched it into the system in place of the M55 router with similar addressing issues there also. We used the Orbi Mesh at the old condo with similar very occasional addressing issues. The new condo has double the square feet of the old and three times as many smart WIFI bulbs due to the fact that every light fixture in every room uses 3 bulbs instead of 1 bulb. And, I can often get 2 of the 3 bulbs in the same fixture working fine and one that is offline. I am using Google Home to manage everything. And when something goes offline I can sometimes fix it by going into the appropriate Govee or Feit or Tuya or Lumary app and finagling until it is found and online. (This works most often with Tuya devices.) The addressing issue got so bad that the main M55 router suddenly lost connection to the gateway. Resetting all of the M55 Mesh Routers cured this but addressing issues soon took over the mesh relatively quickly. I went so far as to fully implement the M55 Mesh Backhaul system by making ethernet cable connections between all 3 M55 Mesh Routers. This eliminated the possibility that the routers were too far apart and creating addressing errors that way. SO, THE QUESTION IS … Have I missed something? IF NOT … Is it in fact the CGNAT to NAT issue that did not become obvious when we were in the old smaller less smart bulb dense condo? IF SO … How to fix that?