Unfortunately, "Customers don't read" can be true as evidenced in my Starting over with setup of new C-8 thread. I thought I could just pick up from when I had my C-5 setup. After all, how much could things have changed, 
. I've used the replies I've received to bootstrap me back to a starting point and will read and be more intentional as I go on my C-8.
1 Like
Glad to hear you're getting a restart in the right direction.
Anyone who claims they've never been in your shoes, has never worn shoes.
2 Likes
@jtp10181
I don't see an option to just remove the old device. It forces you to use the "Exclude and Remove" option.
What is the DNI of that device, is it valid and is it n the zwave details?
@jtp10181 - I tried to follow your instructions above and updated the DNI with "_OLD." So no, it isn't valid anymore.
They must have changed something with the removal. You will have to do the exclude from there and wait for it to time out so you can remove it.
I tried this in the past, but I just upgraded to 2.4.1.164.. so I tried it again. But after 4 hours, the button didn't change and I couldn't remove the device.
I just tested on a zwave device and I get this after about 30 seconds
You are not getting this additonal message?
Does the logs show exclusion was started?
I haven't seen that option, so I dug into it, and it seems I get a 500 error when it checks the delete status endpoint (/device/zwave/deleteStatus/406):
My Hub :
Platform version: 2.4.1.164
Hardware version: C-8 Pro
Diagnostics tool version: 1.1.131
I tried rebooting and looking through the logs for related errors, but I haven't found anything that stands out.
Check this post with a link to the work around
The hex code of the DNI was causing the 500 errors!
Thank you.
