just the same on 6 & 7 as with 3 & 4.
what I have noticed is that after about 10-15 seconds after the door sensor is closed the temp and humi readings return to the correct level most of the time. now and again they just sit maxed out until the battery goes to sleep after 60 seconds (that I have set in autoexec.bat) and just stay there until the door is opened again..
I think it may need a juicy autoexec.bat to force a reading from the sht when the door sensor is opened or closed and poss every 10 mins or so to read them all and publish to mqtt for my home assistant system...
I have been reading the example autoexec.bat files you supplied and got a rough (prob not working version) started.
// start drivers
startDriver Battery
startDriver DoorSensor
startDriver SHT3X
//hold button to get into safe mode
addEventHandler OnHold 20 SafeMode
// press button to take temp & humi reading
addEventHandler OnClick 20 // no idea what goes here.
// wait for wifi to become WIFI_STA_CONNECTED
waitFor WiFiState 4
Battery_Setup 2500 4200 2.29 2400 4096
battery_measure
publishFloat "voltage" $CH4/1000
publishFloat "battery" $CH4/25
// extra wait
delay_s 5
// measure
SHT_Measure
// send data
publishFloat "temperature" $CH2/10
publishFloat "humidity" $CH3
// wait for mqtt data sending to complete
delay_s 5
// sleep for 120 seconds and then wake up (from blank state)
DeepSleep 120
No idea if this is even close as my good old dos/basic code was forgot about 20 years ago the last time I needed to write a windows batch file to backup an hdd to cd, I vowed never to dig into it again.
Edit :-0 simply removing the door sensor form the config and rebooting turns it into a normal temp humidity sensor and putting the magnet to the sensor as if the door is closed does not trigger the over reading on the temp or humidity so I think random noise from activating the hall sensor used for the door can be ruled out. but then it points to how the driver for the door sensor is doing its magic (the door sensor is still active and loaded in autoexec.bat)