Improve device information visibility in WebUI and hbbr.out logs for non-logged-in custom PRO clients (connection type: "incoming")

[Loremipsumdolorsitametconsetetur]

I’m a RustDesk PRO user and would like to suggest an enhancement regarding the visibility of device information for clients not logged in (connection type: "incoming"), especially in the hbbr.out logs. This would also improve the information displayed in the WebUI.

Problem: Currently, devices that connect using a custom client with connection type “incoming” (i.e. no user logged in) only show the IP address in the WebUI under “Devices” and in the logs. However, in dynamic environments with DHCP, IP addresses can frequently change and are not ideal for identifying devices. This is also a problem when troubleshooting and in audits.

Suggested solution: If possible the device name should instead/additionally be retrieved from the device and logged.

Background: In our setup, only admins have user accounts and are logged into RustDesk. Regular employees use a custom RustDesk client in unattended mode (connection type: "incoming") without logging in and get dynamic IPs via DHCP. Therefore, we rely heavily on the visibility of device-specific information for troubleshooting and in audits.

Is there an alternative way to ensure device information is sent to the server without requiring users to log in? If not, thank you very much for considering this feature!

[Loremipsumdolorsitametconsetetur]

Update: This "problem" only exists for each device for the first connection. This first connection isn't properly logged as described above. During the first connection, username + devicename are logged for devices using a custom client with connection type “incoming” (i.e. no RustDesk user logged in). After that, the WebUI properly logs and shows connections under "Logs -> Connection" in addition to the hbbr.out logs.