Hi,
configuration changes always trigger a reboot of all connected APs, taking about 40 seconds.
When you accept a second AP, it is added to the Configuration Daemon -> reboot. Since we already have a more recent AP firmware, the AP firmware is updated (taking about a minute), followed by a reboot. The old firmware additionally had a small bug, causing the AP to use the wrong MAC address during the DHCP request; since the new firmware no longer has that bug, the MAC address of the AP is new, resulting in a different IP address for the AP. The updated IP address is written to the Configuration Daemon -> final reboot.
Oh, and additionally: further AP firmware updates are tied to the ASG system update, therefore the AP will do the reboot during a time where the ASG connectivity is limited anyway. After a successful ASG system update, the AP will connect again, fetch the new firmware, do one additional reboot and be operational again, so this odyssey will not repeat itself (unless you acquire more access points shipped with that old firmware version).
