Intermittent disruptions in temperature measurements cause huge pid_d spikes about hasmartthermostat HOT 3 OPEN

OK, understood. I'll make some trials on my side.

from hasmartthermostat.

Hello, looking a the curves, I would rather think about a high sensor sampling rate or forced refresh rate of the PID.
You need to identify on your curves when the sensor returns a new value to see if the PID refresh is due to sensor or internal thermostat refresh.

from hasmartthermostat.

The PID is refreshing at every update of the temperature sensor. That's why the spike ends so soon. That's also why the spike is so high; pid_d isn't derived from the last temperature change, but from the last update of the temperature sensor, which is a much shorter timedelta. I don't see how a higher refresh rate (of what?) would help.

Once I restarted the shelly device it stopped disconnecting, and the spikes in pid_d also stopped. So this isn't a problem for me. I just wanted to report it, as it might be a problem for someone with an intermittently unavailable temperature sensor. It looks to me like the pid_dt comes from temperature update and not from temperature change. Or is unavailable -> available regarded as change?

from hasmartthermostat.