Thanks…that was my fear that the ID would change and i have to find rename all nodes…
however after a reboot i now have all zwave nodes “uninitialized”…and only my old controller “online”…
What can i do…remove old controller and add new and find replace all IDs in configs?
If you didn’t use the new controller, then everything should be the same as original…
not here…i now had to remove the old stick. did accept the new controller…now of course all zwave devices fly in the inbox…my ID now is 512 and not hexcryptical stuff…lets hope changing ID makes all play music again 
It looks like you used the new coordinator. If you didn’t use the new controller, then everything should be the same as original…
no, i did not touch the new controller from the inbox until i realized that my zwave devices do not initialize anymore…so i started to remove the old controller and add the new one…
should this work or is this now an even worth situation…like i can use the new ID to get my zwave nodes up in the air again?
I’m not completely sure I understand the state of your system - to me, if the ID of the controller is now something like 512 as you state above, then you are using the new controller. If that’s not the case, then I don’t know why the controller got renamed, so I’m not sure I can really comment.
You probably are best to reinitialise with one controller or the other.
Again…
1.) i realized that a new device is in the inbox (the NEW controller). did not touch it.
2.) my zwave ndoes do not initialize with the old controller…did not touch anything at that point.
3.) as you said it should work, but it did not, - my last resort was to remove the OLD controller and accept your new controller from the inbox, which brougt in the 512-ID…
My question now, is it that simple like before to update all items with the new ID in the channel and all should work again?
Either way, if you have a new controller, with a new ID (512) then somehow, you have accepted the new controller.
You are probably best to just use it - it’s up to you though.
I’m seeing exactly the same… Currently have my original controller thing showing as Online, the new ZWave Plus USB Dongle sitting in the Inbox, as yet untouched and all zwave device things now show as uninitialized.
Original controller
Inbox
Device
Any ideas why??
Yes - it’s the same reason as I explained above.
In my case it was not as the way Chris mentioned - “leave it untouched”. With original controller all zwave items were dead…even after a while or after a reboot.
my last resort was to REMOVE the original controller and accept the new one…after that i changed all channels to the new ID and now i’m in “healing” means trying to reactivate and entry/update all association settings which have been lost with this re-entry of all zwave items with their new channel path…
Chris, can you explain what has changed now with the new controller?
Nothing has changed.
All that has happened is the is a discovery process that gets some information from the OS, checks the PIDs to decide if this is a ZWave stick. If it is, it adds the thing to the inbox. If you do nothing, then nothing changes. Ignore the thing, and nothing changes.
Simples 
Just ignore it, and don’t change to using the new controller. Or change to the new controller if you prefer, and then you will simply need to add all the things back as the original ones won’t work.
I’ve done nothing and something has changed though… None of my devices are working now and all are showing UNINITIALIZED - HANDLER_CONFIGURATION_PENDING
This is absolutely not true! I had a system update yesterday and all Z-wave devizes stopped working. No one went into the PaperUI and no one accepted the new USB device. My old serial interface was online but none of the devices were available.
This is a true bug! I have tried every other way to get it working without success. As the spouse is coming home and we have a dark house, I had to add the USB device and now it finds my devices. But with that I will need to rename all devices. Not so fun at all.
It is important that this is sorted out for other users.
It is not a bug - but it is an issue that needs to be understood, but I don’t think there is anything that can be done to resolve it.
The issue here is that if you have auto approve enabled, then the system will create a new dongle - automatically. This will cause a race condition on startup, and it’s then a 50/50 chance that the system won’t work.
This is why in the latest update notes that were issues for M4, I recommended deleting all things, including the controller. It is the only way around this that I am aware of.
What about if auto approve is NOT enabled and yet the new device still appears in the inbox and all zwave devices stop working??
What is the issue you’re reporting exactly? I’m not really sure what your issue is without further information?
Hi @chris!
Wow, I’m so sorry to see that the USB controller discovery feature is causing so many troubles 
At first I thought that the feature will really help new users (and I hope that it is helping), but it’s being a pain in the ass for already working networks.
@Mark_Webster the appearance of a new device in the inbox should not affect the already working Z-Wave devices, this cannot be the root of the problem.
The problem that we are facing here is the following one: as the Z-Wave USB controller doesn’t provide a unique identifier to the OS, the binding “sees” a new device even if the Thing is already configured. In any case, the solution should be pretty easy and shouldn’t cause any trouble: just ignore it.
Anyway, for the new upcoming openHAB 2.4 release, we should recommend deleting all Z-Wave things: the nodes and the controller. It should only take 5 minutes to import all things again and link the already created items. It’s not the best solution, but it should solve all problems forever.
Best regards,
Aitor
That is what I already wrote in the 2.4 M4 release updates -:
Major changes have been merged to support features such as security. All things must be deleted and re-added. Refer to ZWave binding updates for further information.
