I want to share a reproducible issue I encountered with the Seestar S50 after updating to Seestar System version 26.1 and Software/App version 3.0.0.
After the update I noticed how my subframes captured with the Seestar changed and showed a very noisy pattern, see left for before and right image for after the update:


I tried to integrate these files with PixInsight but it already stalled/failed on the Debayer step with the error message:
No valid PSF signal samplex on channel ...
Also the Subframeselector could not load multiple subs at once so I made a script to meassure them with astropy to confirm my hypothesis that somehow the calibration on these files was off - not that I let it print Reject on corupt files:

Post-update frame has 55% of all pixels pinned to the minimum value (0 after BZERO/BSCALE scaling). Given BZERO=32768, this corresponds to raw stored values saturating at the minimum possible signed 16-bit value (−32768) at extremely high frequency, which is consistent with excessive pedestal subtraction / black-level miscalibration / clipping introduced by firmware.
This kind of clipping systematically destroys faint stellar signal and PSF sampling, explaining why PixInsight cannot generate valid PSF signal samples during debayer/PSF detection.
Tested it on 3 different nights, different targets in good conditions with bortle 4. Problem seems to be more pronounced when i have the LP filter on I can also meassure a difference in SNR in IRCUT subs compared to subs before the update :/
Unfortunately I have already seen many reports on social media for this and I already made a bug report on 12/19 on this. I think this is a real issue as it destroys the data and already made me lose 3 imaging nights because of this error.
I made this post so other users can find the issue and see that they are not alone.
Thank you for looking into this ZWO.