I have a simple use case for the ZS - using it as a Tidal Connect bridge to my DAC over wifi. But I have exactly the same issues as others, with frequent disconnections, and an inability to re-connect. I have tried all of the fixes described so far in this forum, but to no avail. As an ex-software engineer I couldn't help but try to localise the issue.
I used the Tidal app. Now, it isn't a connection issue as the other Chromecast devices are seen, albeit the list may take a few seconds to populate. The ZS connection can take 10 minutes to appear. Frequently, on trying to connect, it has a go and times out. A number of attempts are then required. This suggest that ZS is not responding to peer-to-peer requests, or is heavily loaded (doing what, it is a powerful processor!).
I used different android and iOS devices to see if it was the OS stack or chipset implementations, such as low-power modes. Still didn't work.
I tried the DNS settings to 8.8.8.8. Didn't work, and couldn't see how it would affect it anyway.
Turned everything off on the ZS, including queued playlists to see if it was a processor loading or memory issue. Still didn't work.
Tried a wired connection to a wifi repeater. Still didn't work.
However, when trying to connect directly via wifi (mode 1) it frequently STILL fails to connect. This suggests that it isn't the Tidal app that is the issue.
It is definitely the ZS not loading the network stack, or managing the request thread from a peer, either through prioritisation or because of processor overload. Others have made the same comment a long time ago and it should have been addressed by now.
Given that this is a fundamental aspect of its design, why hadn't it been tested before it was sold! Even in my simple use case, I have spotted a number of other software-related issues, and, combined with 57 pages of bug-reports above, in my experience such flaky software is down to poor software design, poor development discipline and a lack of quality and testing.
So when are iFi going to stop the development of new products and divert focus into getting a new software issue released?