07-10-2023 08:12 AM
There are various scenarios my team has encountered for needing to re-register or re-link devices back in Control Hub, after they've already been registered. One of the main examples we've encountered recently is during rebranding (when a user's email address gets changed), this causes the personalized device to stop communicating with Control Hub.
Our solution to fix this issue has been to:
This was fine up until Room OS 11.4, however none of the newer versions prompt to manually enter the provisioning server after the device reboots. We have had some success by still doing a provisioning reset and then connecting to the device IP and entering the provisioning servers manually. Is there a better way to get the devices to be recognized again by Control Hub?
Thanks.
08-10-2023 11:59 PM
Yes, there is a better way to get the devices to be recognized again by Control Hub. In newer versions of Room OS, the devices will no longer prompt you to manually enter the provisioning server after the device reboots. Instead, you can use the following steps to re-register or re-link the devices back in Control Hub:
Delete the device from Control Hub.
Go to the device and choose a provisioning option, to kick off a provisioning reset.
The device will reboot and automatically re-register or re-link with Control Hub using the new provisioning server settings.
The device will then be available in Control Hub and you can re-personalize it to the new email address.
This is the preferred method for re-registering or re-linking devices in newer versions of Room OS. It is more efficient and reliable than the previous method of manually entering the provisioning server settings.
Here are some additional tips for re-registering or re-linking devices in Control Hub:
Make sure that the device is connected to the network and has a valid IP address.
Make sure that the device is not in provisioning mode.
If you are having trouble re-registering or re-linking the device, you can try resetting the device to factory defaults.
08-11-2023 06:48 AM
Also, does that mean after we delete the device from Control Hub, we do not have to use Device Connector to relink it?
08-11-2023 06:46 AM
Our other issue we're running into is for devices where we configure on our work network, but then need to configure them to UCM with Expressway. How do we get these devices configured with their username and password for single sign-on with our expressway?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide