Sincere apologies for the delay in replying.
Although the point is moot since the release of 2.3.1 and the possibility to disable Guest (or 'Demonstration') mode, a photograph is available, taken today, of the two devices, both running 2.2.0 on Android 14, both unable to acquire Control (the button is greyed-out on both). Unfortunately when attempting to attach to this message, the forum responds with "Oops. something went wrong. Please refresh the page and try again." Several attempts resulted in the same error message.
However, if a recreation attempt is still envisaged, the method is as follows :
0) On a LAN, enable access for the S50's Station Mode.
1) On a PC (Windows 11) establish a network shared folder at the LAN-assigned address pointing to the 'My Works' directory on the S50's storage,
2) On both Android devices that have visibility to the S50's network, disable automatic network connection,
3) Power on the S50,
4) Connect both Android devices to the S50's network,
5) Attempt to connect either of the Android devices as a Controller. Both will fail.
5) Disable the PC's network,
6) One or other of the Android devices will now be able to acquire Control.
It is apparent that the S50 believes the PC, having pre-emptively connected its network share, to be its Controller, which it is not of course.
As noted above, all this is now moot since 2.3.1. But it could all have been avoided if the ZWO app had actually stated which device had control at the point where the failure to acquire it occurred, which it did not.
Regards.