Bug 445064

SUMMARY
KStars 3.5.5 Stable is no longer reliable. Benchmark settings cannot be trusted. There is a disconnect between what you ask and what you get.
For example, My QSI ambient air temperature and preset cooling temperature differences cannot exceed 47deg C so -20deg is a good setting for nightime capture, but during the daytime  -20deg  setting on a 30deg day will bring up 100% Cooling, therefore the temperature rises above the critical setting of -20deg C

STEPS TO REPRODUCE
1. To eliminate operating system fault I am using Stellar Mate SD Cards on 2 RPi's. As a server and as a controller.
2. Select "Enforce Temperature before Capture"
3. Select an unreachable temperature, say -30deg C,  


OBSERVED RESULT
as the cooling demand passes 100% and just take lots of frames...
Please note 
1)  that the Temperature tick is still green and the camera ignores the enforce command.
2)  No alerts or alarms are issued
EXPECTED RESULT
I Expect Ekos to use my input settings, 
Control and modify the outputs 
Raise alarms and alerts when it cannot comply

SOFTWARE/OS VERSIONS
Stellar Mate SD cards in 2 Raspberry Pi's
Also on my macOS: 

ADDITIONAL INFORMATION
This is one of a number of issues where input settings are lost or ignored rather than being saved, so this is a formal "Stake in the sand" for me to document how KStars ver 3.5.5 has become unreliable.
Others are Pegasus Focuser settings, QSICamera sensor settings, QSI Camera rotation settings, Guide camera settings...
Until ver 3.5.5 stable I had fun doing astronomy, but it has become unworkable as a simple guiding crash will make an SD Card unusable.
Thanks for what you do.. just having a bad day here. (No captures all last night)
Len