I am was having some issues with my mobile service, turns out when using mobile data Google Home app works fine but SmartThings app doesn’t.
While it’s my data provider’s fault (maybe they’ve introduced CGNAT or some weird proxies), I’ve just found out the issues are exclusive to IPv4-only services (like SmartThings) since IPv6 services work fine (Google Home).
Would be nice to support IPv6 in the app, which I guess means supporting it in api.smartthings.com which is IPv4 only.
Edit: mobile provider has fixed the IPv4 routing, still, the post wasn’t about this particular issue but preventing future ones and supporting IPv6 like other services do.
1 Like
Possible workaround until the SmartThings cloud/API supports IPv6: install Tailscale on your Android TV or HA box and your smartphone.
1 Like
Well, I hope my mobile provider fixes their network stuff since it affects more services and webs, but most engineers must be on summer holiday now since they’re taking their time.
For now my workaround is using Google Home when out of home if I need to change anything or check the state. SmartThings push notifications like alarms and that stuff arrive fine since those are handled by the native Android push notification service run by Google.
Still, adding IPv6 support to SmartThings would be beneficial and a way to skip NATs, CGNATs and potential issues like the one I’m experiencing now.
Edit: The mobile provider has fixed it already, after three days! But again, the purpose of the request was not fixing this particular issue but preventing future ones.
2 Likes