Does anyone else find it cumbersome that when you go to lifecycle a room system (codec) in an existing Control Hub Workspace, you have to first remove/delete the old codec from the workspace before you can register the new codec to avoid having the workspace put both devices into "companion mode"?
The use case for this is having a Workspace that is current service and you want to "pre-configure/register" a replacement codec for the existing Workspace to minimize the downtime for the room when your integrator swaps out the hardware. It would be very useful to be able to register the replacement codec to the Workspace (while leaving the in-service codec in place) and then box up the replacement codec so it's ready to go out of the box when swapping the hardware.
Trying to register two codecs to the same workspace today results in both codecs being put into "companion mode" which isn't how the devices will work in the room. I submitted an idea for this functionality a year ago, but did not get any support for it. Anyone else running into this sort of issue when lifecycling existing rooms/workspace with new Cisco room systems?
https://ciscocollaboration.ideas.aha.io/ideas/COLLAB-I-23265
