If the thresold is at 0.5 the wake up and info transmission is done at +0.6 it's totally unusable to control the heating of a room for example. I doubt that the user will be very happy with that ... especially since shelly are mostly used in home automation. this limitation makes no sense : a wake up at the exact value of the threshold would be a minimum and an option with a warning to check to go below 0.5 would be highly appreciated, maybe at least from an http get command ... Also a wake up every 3 minutes on power supply is useless and less efficient than a wake up on non limited threshold.
I bought 10 shelly plus h&t and will have to return them unfortunately because of a simple option not implemented and unavoidable ... it's a shame the object looks well designed but the software is not up to the task because of very questionable choices ...
We buy shelly for their quality of manufacture and their capacities of configuration, and more time passes, more we are restricted by the firmware...
When in doubt and because I really don't want to send back my 10 shelly plus h&t, would anyone know a way to bypass this counter productive limitation of the threshold ? a custom firmware maybe ?