The only thing that the old ZA module doesn't do correctly is Volume FB. everything else is working as it used to. I have a site with a AZ3000 or AZ5000 that's been trouble-free for a year.
The AZ1000's are 'red-headed step-children' (Apologies to red-heads!) and we won't be using them again, but the control set *seemed* to be fine.
FTR, this issue could very well be something in Crestron FW or the code, as Both AVRs were offline with both the S#/web-socket and the TPC Client.
*** My post is just to make sure that there are no other items that people might have found...
Here's the primary differences that we found with the AZ-series vs the ZA-series and the Crestron Sony STR-ZA series user module.
- Volume feedback doesn't work properly as a 'Bug' in the ZA firmware response strings was fixed in the AZ-series but the ZA S# module cannot be updated since apparently no one at Crestron knows where the source code is...:( As mentioned, I'm just using a parallel TCP client (Port 33336d) to receive the volume FB. I refuse to use the CCD or Package files...
- The Web-Gui, which was one of the best elements of this line still works well; however, unlike the ZA series, you cannot access the Web-Gui on the AZ if the unit is in standby. The unit needs to be turned on via front panel or a remote command (from any source including the Crestron interface if working). then you can browse to all things... It's exhausting with all the different ways that manufacturers can make things difficult...there seems to be no end!! The AZ Web-Gui has been change and as usual not for the better. many people just do not know how to think logically anymore but it doesn't stop them from changing things, just to change things, IMO...
- Also, with the AZ1000 units, we seemed to have an issue using Static IP addresses and had to revert to Reserved DHCP, which also concerns us... It matters not as I would not use the 1000 chassis. A Sony support person told me as such also...