So how many issues HE get accused off are actually a mesh issues (tagging @bobbyD to give us an estimate on that)? I recon a lot. And again and again people are pointed to the documentation and some to the zigbee routing table. But for the average Joe this is difficult to deal with. And before you know it you are pointed to get a sniffer or an xbee. But, that is just not the solution in my opinion. Because it's far too advanced for average Joe.
So my question is this, wouldn't it be a fantastic thing if HE made us a build in tool for both meshes to analyze them and give us some proper and understandable sense of what's going on? I think that would save the community and HE support a ton of issues. And yes, I know it's a long turn investment unlike a lot of other new features. But it would mean that support wouldn't have to grow in resources exponentially when more customers arrive from other platforms. Which has all kinds of benefits in the long run.
To give an example I'll show how this is done by Athom Homey: https://user-images.githubusercontent.com/3584214/35084193-106c945e-fc23-11e7-8876-23a44b1f4d92.png