A little more detail to my post above.
In the past (released v1.4 from January), whenever I tried to connect to my home mesh network, I could see the ASIAIR on my router's tables. I had in fact be able to reserve an IP address on my router for the Raspberry Pi's MAC address.
However, ASIAIR would time out with a connection failure and asked for the network password again. And fails again, etc.
With the ASIAIR v1.4.1 (9) Beta (firmware 466), ASIAIR successfully connects.
In fact, I can even start the iOS ASIAIR app before even powering up the ASIAIR (original) hardware. With the iPad connected to the home network, the app just sits and wait in the ASIAIR splash screen. Once the ASIAIR hardware finishes booting, the app automatically detects the ASIAIR on my home network and places the app into the first screen (the one with cameras, focuser and mount selections).
But there is something that I have not been able to explain -- contrary to the documentation, the ASIAIR (in Station Mode) actually switches itself to the 5 GHz band to connect to my eero mesh network, and the ASIAIR also appears as a 5 GHz connection when I looked at the eero's router tables.
Since it is actually working on 5 GHz instead of 2.4 GHz, I am not going to worry about it.
In case there is a signal quality problem (I have not been able to test outdoors because of the persistent rains), my fallback is to directly (Ethernet) connect the ASIAIR to a travel router, which then acts as an extender to my mesh network, thus using the WiFi antenna in the travel router instead of the antenna in the ASIAIR.
Right now, I have two very workable solutions.
One day, I may drill some holes in the wall of the house to install a weatherproof RJ-45 connector and I can then wire the ASIAIR directly to one of the mesh routers -- the speed that you get from direct Ethernet connection is highly addictive :-).
Clear skies,
Chen