When a controller that is at least 6.0.x or 6.1.x (beta) is configured with an IP or hostname under Device Management, the Inform URL that is generated under the site settings is invalid.

For example, if I have configured the Device Managment IP to be 192.168.13.102, in my site name of "test" it generates an Inform URL string of:

omada://192.168.13.102?dPort=29810&mPort=29814&omadacId=696cdf8f8934aa50a1530d68

I do not know if future devices are expected to be able to use the "omada://" string but the device doesn't seem to like that.  That's simple enough to remove from the string through.

The actual issue is that the value of "omadacId" is incorrect.  It is getting the Site ID setting and not the controller ID.  So if I try to put in:

192.168.13.102?dPort=29810&mPort=29814&omadacId=696cdf8f8934aa50a1530d68

I get a warning of "not hexidecimal" but if I swap out the incorrectly provided site ID "696cdf8f8934aa50a1530d68" with the controller ID, it accepts it and adoption works fine.

This at least happens with my EAP225(US) v3.0 (Firmware 5.1.7 Build 20240819 Rel. 44148) that I use for testing purposes, unsure if it happens with any other devices.

As a side note, it would be fantastic if there was some sort of option when adopting to be able to specify the Inform URL from the controller or auto configure the Inform URL from the controller if device management is configured so that the user does not have to login to the device being adopted and manually set it from the device.  Having that occur all from the controller would be a huge quality of life enhancement.