Thank you for the photos of the Deco units. Are both the v1.26 and v1.20 units currently in use (one connect to the IG, one as a mesh satellite) or were you testing with the IG connected to each one independently to test against each hardware version?
I am currently testing with a matched pair of v2.60 units (they came packaged together) which I have not been able to replicate the issue on yet but I will continue to test and should have some update to share tomorrow 
Thankyou, for continuing to follow up on this.
I had (4) x20 pucks/mesh in service (1) was the router-the other (3) were part of the mesh. I had them and the Invisagig running together without incident, for (14 )months.
Then when I started having this problem (about 1 month ago) I purchased a (2) pack of W6000 Deco pucks, I made (1) of the W6000 the router, and added the other to the mesh system, I did NOT use the orginial x20, that was the (router) should I say NOT added back into the mesh system.
The same problem persisted.
I want to say that he IG, settings you suggested, DID HELPâas the lack of not passing data has become not near as frequentâmaybe once a day, or day and a half.
I have NOT used the VPN since we changed the IG settingsâthe (auto connect) for TMOâwas?? not playing well??
I will say the system had been running for about 24 hours, and I was in my shop, my phone notified me that the wifi had stoped/droppedâbut it was an hour or so before getting back to office, and it was working. I guess the watchdog fixed it!
Hi @rockyinmo ,
I appreciate your patience as I work through my testing. I have sent you a DM to get some additional info from you which should help me along to [hopefully] a solution for you
Ryan. Iâm looking all overâI do not know how, where to DM?
If you click on your âRâ in the orange circle at the top right of your screen you will get a dropdown menu, click on the envelope there to view your Inbox. From there you can view messages and reply:
I did send you a message in (messenger)
Thank you! It looks like your UI is zoomed in and so it seems the envelope icon for Inbox may be hidden but the first notification link in your screenshot should take you to my message and allow you to reply:
No worries, in any case I received the info I needed thank you!
(FYI, I removed your reply with the info here since it contained a device identifier)
I am very late to this conversation, but also started to have problems between my IG (connected to TMHI) and a series of Deco pucks.
Direct connect of a PC or Mac directly to the IG, and everything was fine. The IG showed normal connections to T-mobile, etc. etc. However, when I connected a PC or Mac via the Deco units â whether wired, or wireless â I got no WAN connections whatsoever. DNS was verified, local IP assignment to the PC/Mac was verified, etc. etc.
When looking at the Deco units, they were constantly assigned a WAN IP of 192.0.0.1. Uh⌠that ainât right! I powered everything off, then powered it back on a minute later. Guess what? No dice.
Powered everything off for 5 minutes, , then powered it back on a minute later. Guess what? No dice.
Finally, I powered the whole stack off for 3 hours. Powered it back on⌠bingo bango. Everything works.
My theory? Something in the Deco borked, and it lost the WAN assignment from the IG. During my âshort reboot timesâ, the IG was still holding the same TMI IP address, and when it passed that onto the Deco, the Deco has some sort of craptastic NAT going on, and it kept everything at the 192.0.0.1. It was only after I powered the IG off long enough for T-mobile to give me a new WAN IP, did the Deco come back to life and start working.
Am I all wet on this ? Itâs working now⌠but the prospect of 3-hour âdowntimeâ to power stuff off and wait for TMI IP reassignment kinda stinks.
Having said all that, the Invisagig is literally better than sliced bread. It is the catâs pajamas. Full stop.
Hello,
As for why it would not pass WAN traffic I would have to test and see if I can duplicate, I have a few Decos here. I do know that sometimes they like to have a manual DNS entry of 192.168.225.1 but generally that doesnât effect the data traffic.
Here is an explanation on the 192.0.0.x address: Why Does My Device Receive a 192.0.0.x , 192.168.225.x, 10.172.72.x , or Other Private IPv4 Address?
T-Mobile thing.
Try setting the InvisaGig to 5G NSA, SA disabled under the Connection configuration and see if it happens any more. This does disable the use of SA bands, and may be more desirable to have SA, but it does also eliminate the 192.0.0.x interface the modem can create when on SA mode.
T-Mobile is rolling out new changes to the way they handle static IPs and Iâm starting to think SA use as well. Many people are reporting odd connection issues on multiple modems on Tmobile, but not a ton of people.
You could blow me over with a feather. I have no idea why 5G NSA/ no SA made a difference, but it did. 
I need to think about thisâŚ
(In the meantime, thank you! I was thinking of all sorts of creative ways to through another router in front of the Deco or something, but obviously thatâd only gum up the works even more)
5G NSA, SA disabled, forces the T-Mobile network to stop using the IPv6 only connection that seems to break a lot of services including some select routers. IT can also hop back and forth between SA and NSA automatically if your location has odd signal quality or edge strength. annnnddd ⌠For some reason the Decos really donât like that IP proxy interface (192.0.0.x).
Side note, total opinion, not a big fan of Deco, I prefer their Archer routers. I hate being forced to use an app on my phone to set any meaningful settings, and even then itâs limited and clunky almost always. The Archer line lets you everything and more in the browser, and they tend to work better as well. They do have a n app but you donât even have to install it at all.
/2cents 
In playing with it today, clearly the SA disabled is more consistent in the initial connection, but unless itâs just a crazy coincidence of timing, the speed is woefully crappy with SA disabled.
Iâm using a very âchattyâ and latency-intolerant application to access some database stuff, and NSA-only doesnât seem like itâs going to cut the mustard.
I do get SA connections and they hold pretty stable â but getting the first connection after a power-down or modem reset is like a 30+ minute endeavor.
Playing with it more this afternoonâŚ
(p.s. Maybe I should just toss the Deco and get something different)
Check the bands itâs using and start playing with turning off bands and finding out which one(s) are pulling you down. Here b71 and n71 both are terrible for my speeds. Other places 71 is a life saver, so itâs not one size fits all with bands, but a little playing with them should get you optimized.
Here is an old video I did (I need to update): https://www.youtube.com/watch?v=tpsAdwBqt7w
