To be clear, this is NEW, errant behavior. This was not happening more than a couple .xxx releases of 2.2.4 ago (e.g., I didn't notice it on earlier betas).
Normally, this screen appears rather rapidly (just a couple seconds or so). Thus, this isn't due to too many devices making it slow al the time.
I have 67 Z-Wave Devices on that page.
I was seeing hangs prior to the .141 update and after. This latest occurrence with the 500 error, happened after the .141 update--which required a boot within the past few hours.
I had done a complete shutdown, power off, wait, and restart yesterday.
Understood. I noticed (and reported) the 500 error starting in 2.2.4.135
I have only seen it with the first load of the zwave details page and usually within 10-15 minutes after restarting. I figured something during startup was taking some time to complete.
Something seems like it got wonky about .135 or so.
That's about when I started seeing ALL KINDS of things getting bottled up (not regularly--just sporadically). Hopefully, they can sort out what might have changed in that window.