^^^^^^^^^^^ I did this and it worked. Not sure why a company would make a device that would cripple a huge % of your customer's smart home setups. I only have a chromescast but it's how I watch TV without shelling out for a smartTV. Of course, there's no obligation to support any third party products but come on, Google is the largest evil tech company in the world and a vast quantity of your customer's use those products on a daily basis - maybe it would have been good to do some QA before releasing a device this gimped. TPG is selling its customers a product that they clearly know won't be compatible with third party devices (without mcguyvering a solution) and, unless I missed what should be MASSIVE print on the device specs, they haven't at least done the service of telling us before we buy.  After sifting through multiple threads about this topic on this community where the TPG tech team's response was "lol sorry", I'm surprised to see that it was the costomers doing their own trouleshooting - multiple customers. Frankly, it isn't good enough that the customers had to find this solution. This was a simple process and could have been communicated by the TPG tech team if they stoped to think how the router's guest netowork setting functioned. It's literally solved by setting up a guest network on your router. TPG's responses have all stated that you can't do this. @reh06 managed to figure it out. Well done mate, maybe you should be head of the TPG tech team. Might get some actual help for customers that way.   @TPG please pass this on to your customer relations team so your processes can be reviewed. This was a failure.    ... View more