When setting up the ASIAIR Plus for the first time - don't have any other devices connected to it.
Remember - don't power you mount from the power output of the ASIAIR Plus. Power your mount with its own power supply.
Also - depending on the model of camera - you MAY also need to do the same for the camera.
In your case - turn it off with the switch on the ASIAIR Plus. Unplug the power supply cord from the ASIAIR Plus. Unplug the power supply for the ASIAIR Plus from the power socket.
Leave it like this for 5 minutes.
Now, plug the power supply into the power socket. Plug the power supply into the ASIAIR Plus.
4. Make sure nothing else is connected to the ASIAIR Plus.
Now, on your device that has the ASIAIR App, make sure the ASIAIR App isn't running in the background (that it has been closed off). For Android that involves pressing the home button then closing the app if it is still running. For Apple, depending on the device, it is either pressing the Home button or swiping up from the bottom, then closing off the app.
On this same device go to WiFi settings and tell it to Forget the ASIAIR WiFi.
Restart your device.
Now turn on the power supply to the ASIAIR Plus. Then turn on the ASIAIR Plus power switch.
Wait a minute and you should hear a beep sound. Wait 5 minutes.
Now see if you can connect to the ASIAIR WiFi using your device that will be running the ASIAIR App.
If you see a prompt to stay connected - make sure you select that - so it stays connected. Otherwise your device will want to connect to your home WiFi.
If you have an iPad or iPhone with mobile data you may have to turn off mobile data as well.
Now launch the ASIAIR App and connect to your ASIAIR Plus.
Now continue with the setup. If it happens again - make a note of exactly what caused it to happen and, in the app itself, from the "Enter Device" screen, I think if you tap and hold on the ASIAIR picture it will allow you to extract log file(s) as well. @Tech@ZWO @PMTeam@ZWO will need to confirm this.
Once you have the logs and knowledge of what caused it - submit a ticket to ZWO to have it investigated and attach your log file(s) with it.