There isn't any built in mechanism or out of the box method for a robot to be aware of a local IP rotation and automatically "fix itself" with a automatic update of the IP.
As the controller doesn't have the ability to detect such a change, when the IP address rotates to a new IP it doesn't recover by itself but i needs some manual or scripted operations.
The scripted actions should be based on the following concepts and procedures:
1. Stop the Nimsoft Robot Watcher service
2. In IM, Remove the redundant robot entry from the hub (via deletion of robot.sds or removerobot callback)
Related KB: Change of ip address of robot or hub