Okay, I have spent many hours for over 2 weeks working with @bobbyD trying to resolve this issue w/o success that I am ready to give up, but thought I would reach out to the tech community first. So, my HE C7 is out of the box new and this is a fresh installation using new Z-Wave devices. I have never been able to discover any Z-Wave devices (I only have Z-Wave devices now) from the start after registration and update. In fact, only if I downgrade to version 2.2.3.119 can I even see "Z-Wave Details", etc. otherwise the Error 500 will come up using version 2.2.4.158 when trying to status the radio.
Working with @bobbyD, I have followed the Documentation to perform an unknown number of Soft Resets, Full Resets, Shutdowns (and power removed), Restarts, Disable/Enable Radio, using diagnostic tools, etc., etc. I have just performed the update again to version 2.2.4.158 and the Z-Wave radio is completely unresponsive. This had been a real challenge to resolve, but at this late stage I just would like for it to work. I would be grateful if anyone has any suggestions or recommendations?
Also, do you have the Z-Wave Region set to the correct location, to match the frequency of the Z-Wave devices that you're trying to pair? What devices are you trying to pair?
No, unfortunately, I can't get to this page after the 2.2.4.158 update. After a long pause it times out and I eventually get the same error 500 message:
Hi there, I haven't heard from you, and didn't realize you were back home. I see that you've sent me a few updates in the past few days. I'll look at your hub again and will get back to you. Last time I suggested Soft Reset, but based on your recent emails, it sounds like you have performed a Full Reset. Unfortunately, doing so erased historical data from your hub so we would not be able to trace back what might have happened.
Thanks Bobby. It'll be easy enough to recreate as I am back to where we started from originally with 2.2.4.158 and an unresponsive Z-Wave radio. I can perform another Soft Reset or any recommended troubleshooting steps that may resolve this.