Fix bug: IP address sometimes truncated, causing connection failures (e.g., '127' instead of '127.0.0.1')

[stex2005]

Bug Description

Sometimes the IP address is truncated when connecting to the robot, making it impossible to connect to rosbridge and related services. For example, instead of using the full 127.0.0.1, the system attempts to connect using 127, which fails.

Evidence

Steps to Reproduce

0. WSL + Cursor
1. Attempt to connect to the robot using the full 127.0.0.1 address via the interface or API.
2. Observe that the system attempts to use the truncated address 127 instead of the full address.
3. Connection to rosbridge and similar services fails.

Expected Behavior

The system should use the full IP address as provided, such as 127.0.0.1, ensuring a successful connection.

Actual Behavior

The IP address is sometimes truncated (e.g., to 127), resulting in connection failure.
Unable to connect to rosbridge and possibly other networked services.
Users see misleading errors suggesting the IP or port is unreachable when the issue is a malformed address.

Suggested Fix

• Verify where the ip address is truncated
• Review and correct the logic that parses or validates IP addresses to ensure the full address string is used.
• Add additional validation to catch malformed or incomplete IP addresses before attempting a connection.

[stex2005]

After thorough debugging, this looks like an AI allucination.
Adding an "ip: 127.0.0.1" entry in the config file for each robot helped not allucinate and pick the non truncated IP.