If this was mentioned before, I must have missed it somehow.
It’s possible that the temperature value used to create temperature events on the hub needs to be using a different data type. Right now, if the user hasn’t turned on the “Display temperature as integer” option in the preferences, then the temperature value is passed on a
float number with 0.1 decimal precision. If the “Display temperature as integer” option has be turned on, then the value is passed on as an
The hub event handler in theory should be able to handle either of those data types for the temperature value, but if it can’t that would explain why the Humidity Alert! SmartApp isn’t being triggered.
When I have time, I will take a look at the latest temperature sensor device handlers on the SmartThings public repository, and also the Humidity Alert! code, if available to view, and publish an update to the Xiaomi / Aqara Temp-Humidity DTHs if needed.
Honestly I don’t know what is expected for the new SmartThings Samsung Connect mobile app, because the developer documentation isn’t completed. Also, the device handler preferences are completely unavailable in the new mobile app, making it far less useful than the old SmartThings “Classic” m mobile app at this time.