Apology and Update on Version 2.4 Issues - Stable Version 2.3.3 Available

PMTeam@ZWO

Dear Astrophotographers,

We want to sincerely apologize that the release of our new version 2.4 has caused some bugs and issues for a number of users. We understand how frustrating this can be, especially when you're out under the stars, trying to capture the perfect shot. To everyone affected — thank you for your patience, and we’re truly sorry.

Right now, we’re working hard to fix these issues and will release an update as soon as possible. In the meantime, to help you get back to imaging smoothly, we’ve made the previous stable version 2.3.3 available for download:
iOS>https://testflight.apple.com/join/uQhfGyvn
Android>https://www.pgyer.com/air_last_version

Here’s a quick overview of the most commonly reported issues and what we’re doing about them:

False meridian flip (Fixed – currently in testing)
PA EXP limit too low (We’ll restore the v2.3.3 behavior, allowing up to 10s)
Exposure time resets to 10s/3s after reconnecting devices during Live / Autorun / Plan shooting (Fixed – currently in testing)
Flat preview image appears overexposed (Currently being fixed)
Android: White background on the home screen not suitable for night use (Will be updated to dark mode)
iOS: Cannot add LBN and other deep-sky objects in Plan mode (Already fixed)
Android: Celestial object filter not working (Currently being fixed)
Android: Unable to add new sequences in Autorun mode (Fixed – currently in testing)

If you encounter any other issues, please upload the runtime log under the "ASIAIR APP >About" Page when possible — this helps us identify and resolve problems faster.

Thank you all for your continued support and understanding. We really appreciate your passion for astronomy — and for using our app to explore the night sky.

The ASIAIR Team

9Ej7KtYy

PMTeam@ZWO is the canon r8 going to be able to run on the ASIAIR anytime soon. If not please tell me so I can sell my ZWO equipment.

sferlix

PMTeam@ZWO
Not sure it's a bug or not:

during PA, the sensor size and FOV size are reported as 0 x 0
filtering objects list on FOV returns zero objects.

bye

frank

magore

PMTeam@ZWO

I can confirm that for 2.4 that
ALL Sky Polar Align is still broken under the following test.

Time
3:30am UTC July 1st
11:30pm EDT June 30th
Location Waterloo Ontario Canada
N43° 27'
W80° 33'
First star: Deneb
(RA): 20h 41m 25s
(Dec): +45° 16' 49"
Note Deneb is above my NE horizon and is my lowest star in my eastern sky I can see due to trees.

Polar Alignment Results
Azimuth and Elevation continuously change quickly just by refreshing as others have reported over and over and over for SEVERAL YEARS now.

I am unable to pick a star lower in the sky to the east due to obstructions.

You can plug these numbers into the equations you are using and verify your current solutions are quite broken.

Please have someone look at the code itself. The bug should be quite obvious as the math required is not that complex to implement to resolve this for all situations that are being reported.

azskyguy

This is a good start but it doesn't cover all the anomalies I've seen and reported in 2.4. That includes:
Freezes during auto run where sequence just stops on 'loading'.
Guiding exposure drops to zero and can't be changed back. Camera needs to be rebooted. This is on an 'air' camera.
The new plate solve method designed for NB filters no longer works.
WiFi continuously drops out with computer close to the telescope.
The directory of targets has been made too complex and requires more clicks than it used to need.
What about these issues? Many prevent unattended imaging, which is a must have feature that has been taken away.

PMTeam@ZWO

azskyguy Freezes during auto run where sequence just stops on 'loading'.

This may be because the state of this area is not clear when trying to expose it again. We will optimize it in the next iteration.

azskyguy Guiding exposure drops to zero and can't be changed back. Camera needs to be rebooted. This is on an 'air' camera.

Regarding this issue, can you resubmit a log after the problem occurred? We have not received other similar feedback and need to know what happened

azskyguy The new plate solve method designed for NB filters no longer works.

If you use a filter, it is recommended that you increase the exposure time

azskyguy WiFi continuously drops out with computer close to the telescope.

Are you using a PC? Please submit the log for analysis

azskyguy The directory of targets has been made too complex and requires more clicks than it used to need.

At present, this catalog is more professional. In the next iteration, we will consider supporting two modes. The current one is list mode, and a new celestial body thumbnail mode will be added, which will focus more on celestial body pictures.

6h3g399i

Thank you ZWO for providing this. Just a question since I am using testflight for first time. I installed test flight and installed the asiair within it. I don’t know how to access 2.3.3 on the main page it displays as below where it says 2.4.9 on the top. Please share instructions on how to access 2.3.3

Corsair

6h3g399i This post will help you getting the right version of the APP on your Apple device via TestFlight: https://www.facebook.com/groups/1892753927536546/posts/3806593552819231/?comment_id=3806619869483266

Remember the firmware on the ASIAIR has to match the App version on your device.

You may need to do a reset of the firmware on the ASIAIR first.
You can do this by connecting to your ASIAIR with the ASIAIR App, going to the "i"/About screen, then selecting Reset Firmware.

Once reset, make sure you aren't connected to the ASIAIR and don't have the App open, uninstall the App from your phone, then install the version of the App you want from TestFlight.

You then connect to the ASIAIR, launch the App you installed from TestFlight, and you should be prompted to upgrade the firmware on the ASIAIR to match the version of the App on your phone.

PMTeam@ZWO

6h3g399i Hello. You can refer to the following post.
https://www.facebook.com/groups/ASIAIR/posts/3300730050090195

2t1f2k7P

Will you please allow owners of canon R3 cameras to connect their device to zwo asiair mini, if not just let us know so I can sold out the equipment and won't waste time anymore🙏🏻tnx

falconer

Corsair This worked perfectly. Thank you, sir.

DJCummins99

A couple things happened to me Sunday night: my guiding speed which I have set at 0.75X was reduced to 0.25X. The false Meridian flip caused me to lose a lot of subs while it sat there spinning and doing nothing. Several times it turned tracking off, but that might be due to the false meridian flips.

PMTeam@ZWO

DJCummins99 We have fixed the MF anomaly issue, but unfortunately we don't have the actual conditions to test it right now. If you are willing, would you be willing to help test whether the fix solves your problem? Thank you

Ceejay

Can somebody confirm that version 2.3.3 is referred to bij TestFlight as version 2.4.9?? If not, where on TestFlight do I find 2.3.3? I followed the advice above, including the Facebook one.

PMTeam@ZWO

Ceejay 2.4.9 is 2.3.3

deans

Why can't you just make 2.3 available as a new update and get rid of 2.4??? I am not going thru all this test flight crap. And before you jump in Corsair and say directions are out, we should not have to jump thru these stupid hoops. Just re-release 2.3 as a regular update. How hard can that be????
And it would take the pressure off ZWO to fix it so quickly.

Corsair

deans That all depends on Apple and Google and whether or not they would allow that on the App Store and Play Store respectively.

bobpowell@northstate

deans 100% agree! You could easily repackage 2.3.3 and call it 2.4.1 and maybe 2.4.0 would just go in the dustbin of history. This has been SO much trouble.

tyco

I didn't see these issues in your list I hope you can fix them:

The running status of the live stack does not display (i.e. the running number of images stacked)
The running status of flat frame rates, images and histogram does not display.
The histogram controls are buggy. Trying to make adjustments switches it to "Auto" mode

R0k9pZfT

tyco The running stack count is there, but in a different spot. It's in a drop-down near the upper right of the display. At least on Android it is. Histogram is awful now. Not even sure it's stacking.

PMTeam@ZWO

tyco Hello. Are you using iOS or Android? We have optimized the histogram in the repaired version and are currently testing it. Would you like to help see if the repaired version solves your problem? Thank you.

R0k9pZfT

I posted this in the other thread, but it seems that may be dead in favor of this. So to reiterate:

See the last couple posts in that thread, such as can't plate solve from saved images and issues with plate solving in general. I also need to make sure you're clear that live stacking does not perform properly either with random histogram behaviors or images not being stacked at all. I'm not sure exactly what it's doing but it's extremely inconsistent. But it's not destructive like random meridian flips. But given the live stacking in 2.3.3 works so well and processes images well for its purpose, I don't know why it was changed.

Also, from this point forward please pay attention to what people say in this feedback. You ignored so many issues in the beta thread. This is inexcusable. You must take things more slowly and as has been suggested you should have a routine of testing that thoroughly vetts firmware releases moving forward

PMTeam@ZWO

R0k9pZfT Thank you for reporting these bugs to us. We are actively fixing the bugs reported by everyone. Regarding the problem that you can't plate solve the images in the album, can you send us the original image for analysis? This way we can analyze and find the cause faster. Thank you

In addition, regarding the histogram problem, we have fixed and optimized it. The fixed version is currently being tested. Would you like to help test whether the fixed version can solve your problem? Thank you

R0k9pZfT

Also, keep the previous stable around for a while in the future. Allow it to be the fallback without needing to beg for it to be posted. I'd say keep 2.3.3 around until 2.4 is undoubtedly stable for a few point releases at least. Or keep 2.3.3 available until 2.5 is out and 2.4 is known to be stable. Post one stable, one new at all times!

PMTeam@ZWO

R0k9pZfT Will keep this link

4H29wipq

Another bug: on my 533MM PRO it says the resolution is 1504x1504 (which is half). Maybe it thinks I'm binning. But it's not. The actual images are the full res.

Image preview not loading in autorun mode (or at least not always).

Adding support for hardware that I don't own is fine, but breaking everything in the process is not.

PMTeam@ZWO

4H29wipq Hello. Does this happen after GoTo?

watcheroftheskies

As we are mid summer in nautical twilight here in the UK I personally won’t be using my gear to
Image for the next few months, I’m guessing if I just delete the app I can simply install the ( hopefully bug free) new version once it’s released?

R0k9pZfT

If you can, please pull 2.4 from the app stores so our devices aren't tempted to upgrade.