I can’t tell if this is a theoretical question or an actual issue you have having. If the latter it could also be your procedure. A debug level zwave log might shed some light on it.
Theoretically devices included from other applications are in the NVM of the Z-stick, so should be discoverable in OH (or when changing to another OH) with the following provisions.
- they need to also be in the OH ZW database
- If a battery device, it may need to be woken up to be discovered
- If including with S0 security (supported by OH ZW) some have been able to copy the key from the including app into OH (or the new OH) to get them discovered. The recommended procedure is to include the device in OH with the key on the OH controller UI page (advanced tab).
- If included with S2 security (not supported by OH ZW) they will never be discovered.
- They need to be included in Zwave “Classic” (nodes numbers less than 256). OH ZW does not support long range inclusion with greater than 8 bit nodes.
If this is an actual issue and a new controller, one thing to check is the SDK of the controller. See this