Hi,
since I've seen that the underlying issue has been discussed a few times here (in English, but I'm sure the same happened in German), let me propose, here as well, what I just proposed to Shelly, by means of the dedicated form on their website:
In order to partially overcome the big functional limitation resulting from the current very high (0.5C) lower bound for the temperature variation threshold, let me suggest to implement in FW the possibility to trigger a device wakeup and a status update/report when a programmable temperature (absolute, not variation) threshold is crossed, even better if two different absolute thresholds could be set (one for a rising temperature, one for a dropping temperature). This would support the implementation of a kind of "interrupt-driven" temperature control, rather than a "polling-based" one. No need to say that those thresholds should be programmable from the outside of the device through one of the existing APIs, in addition to the web GUI.
Ciao, Nicola.
