I am in the unfortunate position of having ongoing Zwave issues. We still haven't got to the bottom of it, but support has been excellent as usual and I'm sure we will sort it out.
During the process of trying to find the issue, I have realised that there is a lot more diagnostic information available from the hub than users are able to see. I realise that some of it may be commercially sensitive, or that some information my be inappropriate to give out to users (a little knowledge being a dangerous thing etc), but I do think there is information there that could be beneficial to give out.
For example now that I avidly watch the live logs during Zwave repair, I can spot which nodes are not repairing properly. I have had a couple that don't get beyond the "Repair setting SUC route" stage. If you are not watching the logs though, you would never know that. Maybe after a Zwave repair, there could be a report sheet generated highlighting faults? A message along the lines of "Node XX did not give the correct response and was not included in the repair process" would be really helpful in pinpointing any problems.
Also, support can obviously view additional error logs that users can't see. Although they been brilliant, because I am in the UK there is always a large chunk of my day when even the hardworking support guys at Hubitat are asleep. This makes it hard for me to change and test anything without seeing the error logs.
I'm just wondering if a basic "System Health Check" feature could be implemented that you run if you are having problems. It could highlight any problems in the hub generally (eg apps giving error messages) or Zwave nodes not behaving as expected without giving away anything commercially sensitive.
Apart from helping users, it would surely take some load off of support?
