Believe it if not, I'm still using this Z-Wave controller. It was functioning well on my C-3 hub using the bigpunk6 & KeithR @keithriley device handler. But the C-3 died and I switched everything over to a C-7.
Pairing this strange beast was always a challenge. I excluded it, then included it and things seemed good. But I could not load the device -I get this page:
I tried again, so now I have two versions named PE653New and Switch Binary. Both give that same infinite loading page circle and never show the devices.
Logs are non-existent since no events actually occur. The device driver seems to be intact. I've never run into the Hubitat web interface refusing to load a page. Even if the device has an issue, the page should load so this strikes me as being more of a problem than just a bad device.
I am trying to pair a multi wave controller, the Intermatic PE653, to my C-7. It was running perfectly well on my C-3 before it died. I acknowledge this is a niche device long out of manufacturer's support and certainly not supported by Hubitat.
But... my problem, although initiated by this device, is not about device pairing, etc. My problem is focused on the C-7 web interface hanging. If I click the newly created device, the device web page does not load. This should not happen regardless of the nature of the device.
The PE653 responds to the Hubitat Z-Wave exclude/include and creates parent and child devices that I can see in the device list. But there's no way to inspect the actual device to see what's going on.
Please give me any ideas to diagnose this problem. Thank you.
Yes, all the other Z-Wave pages load normally. I'm including two screenshots: 1) the entire Z-Wave details although it may be difficult to see the details, 2) a close up screen shot of the last three Z-Wave devices.
The first device, of the three, is Switch Binary. When the PE653 was first included, this is the name that it chose for itself. It has 8 child devices which are correct and must have determined them from the previous C-3 working entries. Below, I'll include a screen shot of these devices.
Second is the PE953 (not to be confused with the above PE653) which is a remote controller. The configuration of that is strange and I don't understand it. Although it is paired to the Hubitat hub I do not use it at all with Hubitat - it just controls the main device (PE653).
Third is Pe653nn. This was after my latest attempt to exclude the earlier pairing and include it anew. All exclude/include operations went seemingly perfect and quickly. Although I paired it in the same manner as the first attempt, this one did not create any child devices.
Only thing I can think of is press F12 to open the developer console then try to open the device page. Look in the top corner of the developer windows to see if there are any errors (red circle with X).
Also what platform version is the hub running? You can see it in Settings > Hub Details
And I noticed under the Network tab when I load the defective page (device id 3234) it gets a 500 network error. This is usually some variant of an internal server error. With a 500 error it seems inevitable that the web page would hang.
