PMTeam@ZWO
Thank you for your reply, but I find one aspect of your explanation particularly troubling.
Presenting the decision to roll back to version 2.5.2 as a matter of user preference seriously misrepresents what many experienced ASIAIR users have been reporting.
People who have relied on ASIAIR for years do not go through the inconvenience of downgrading simply because they prefer an older version. They do so because essential functions have become less reliable. That is not a matter of preference. It is a serious regression.
You now tell us that version 3.1 includes internal stability fixes that are not mentioned in the release notes. But why not? If reliability is your highest priority, surely those corrections deserve more attention than a list of relatively minor new features.
Which reliability issues have actually been fixed in version 3.1? Which remain unresolved?
Software bugs are understandable. What is much harder to understand is the reluctance to acknowledge their seriousness and communicate transparently about their resolution.
ZWO has built a successful ecosystem over many years because users trusted ASIAIR to work reliably. Dismissing their concerns as personal preferences while leaving stability fixes undocumented undermines that trust.
And once that trust is lost, recovering it may be much harder than fixing the software itself.
I sincerely hope ZWO understands that this approach risks damaging its own future.