when renaming a hub's robot sometimes hubrobotname is not updated in robot.cfg
search cancel

when renaming a hub's robot sometimes hubrobotname is not updated in robot.cfg

book

Article ID: 416463

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

You have renamed a robot, which also happens to be a hub, by changing the robot name in the Infrastructure Manager controller GUI  and the rename does not appear successful, and the hub is not properly reconnecting after restart.

Upon examining the robot.cfg you note that the "robotname" key has changed, but "hubrobotname" retains the old value.

This issue happens intermittently, most of the time it works fine but approximately 1 out of 5 renames fail.

Environment

DX UIM 23.4.3 and higher
hub/controller 23.4.3+

 

Cause

defect - "robotname" key incorrectly being added to hub.cfg

Resolution

On occasion it has been observed that an extra "robotname" key is mistakenly being added to hub.cfg when changing the robot's name at the controller.   

This will be resolved in DX UIM 23.4.7  (CU7) - tentative ETA March/April 2026.

As a workaround:

1. Rename robots by shutting them down, and editing the robotname key in robot.cfg directly, rather than using the GUI to rename them.  This seems to avoid the issue.
2. After renaming any robot which is also a hubrobot, check if the "robotname" key has been added to hub.cfg,and if so, remove it.