Change Update Interval to match thermostats

[LordMike]

Just occurred to me. HA will auto-poll every 30 seconds by default. I'm not sure which frequency the thermostats are running in, but we could match it (its likely a lot more than 30s). This would save requests from HA.. :)

[LordMike]

I found the time to dump my states database and see how often my thermostats changed their value. In general, I found the lowest time (when changes happen most often) to be around 1 minute - actually pretty spot on.

There are two outliers - one which has an update after 25s - this is a room I often check on, so I think by pressing the thermostat, it triggers an update which would explain the low time.

The other outlier, 2mins at its lowest, is a room in the middle of the house with a solid heating arrangement - so its temperature might not swing as much .. It might also be that when a room is not heating, that the thermostat reports back more rarely.

id	changes	lowest	average
climate.rum21_stortbad	225	00:01:02.0465580	00:25:29.4356243
climate.rum3_vaerelse1	91	00:01:00.8324650	01:00:34.3646783
climate.rum2_kontor	110	00:00:59.5918380	00:52:53.7293073
climate.rum22_kokken	162	00:01:01.7318380	00:35:07.6614189
climate.rum20_lillebad	218	00:00:25.3511280	00:25:50.0180966
climate.rum30_entre	114	00:01:01.7458730	00:50:53.8539543
climate.rum31_gang	118	00:01:59.7404850	00:46:39.1744603
climate.rum5_vaerelse2	23	00:01:01.0502700	03:51:35.2614937
climate.rum1_stue	146	00:01:02.7483790	00:38:23.5806165
climate.rum4_sovevaerelse	142	00:02:01.7622900	00:39:45.1926934

[LordMike]

I'd be safe in saying, with the above, that we can change the poll interval to 60 seconds, or even more.

[LordMike]

.. I just noticed that ofc. the data would read a multiple of 30s updates - as that's what it got. I'll change my interval to 5-10s to see the data tomorrow. Damn. :P