Thank you. I disabled then enabled ipv6 in my router’s settings. That seems to have fixed it.
I tried it, and found it to be very intermittent. One day it sees my SmartThings Thread network and one or two of my three Amazon Echos out of which one actually does run its Thread capability, on other days it doesn’t see them all. One day it does connect to the ST and shows me devices - how many of them is also somewhat random - and the other day it says it doesn’t have the credentials.
Conclusion: This sure is nice and useful, but reliability is nowhere near good as yet.
I’m no expert, but it seems the app is affected by your ISP router’s ipv6 settings.
The app froze on me again today. So I disabled wan ipv6 (I left lan ipv6 enabled), and the app is working again.
In fact, the diagnostic results for my thread network after disabling wan ipv6 were the best so far.
It seems there may be an issue with my router’s wan ipv6 implementation.
I had the app not open, so I disabled ipv6 on my router then it would open. Obviously this caused other problems for example my blinds went offline. So I re-enabled ipv6 and rebooted my router and points. This fixed the problem.
WOW. Thanks again. I pulled the csv through my Gemini (pro)
Also some nonsense, but still.
Still a mixed bag here. This week it decided it doesn’t know the credentials to my ST Thread network (it did before). But now it did detect my Amazon Thread network in full, confirming that my three Thread-capable Amazon Echos do run one common Thread network. Doesn’t have credentials for that one either.
The app wasn’t opening for me sometimes. So I sent feedback through the Play Store.
They must have tweaked something because it’s now opening and working reliably for me.
Anyway, you may want to send feedback.
It’s not going to find credentials for the Amazon Thread network because Amazon doesn’t share credentials through the credential sharing mechanisms in Android and iOS.
Additionally, as I posted previously, the diag tool incorrectly uses network name to identify the Thread network so if you change your network name and don’t commission a new device, it will be unable to find the credentials as well.
For the Amazon network I did expect the credentials issue; I’m still hoping for the day Amazon implements merging their Thread networks with non-Amazon ones.
For my ST network, I have not done anything to it between the tool being able to connect and it now not being able to connect.