Happy new year to everyone!
Seems I’ve seen some strange behavior while watching the insights graphs for my heating. This is what I do on new years eve 
I’m using a Fibaro Power Plug to switch on my floor heating pump. While this works like a charm (incl. controlling the mixer temp via some flows), I’ve noticed that the switching of this plug sometimes causes many graphs (temperature, humidities, powers) to show some strange jumps in their value which seems to get interpolated in the insights graps.
E.g. outside air temp from Ecowitt weather station jumps from -6°C to -1.5°C then back to -6°C within 2 minutes.
here are some screenshots:
or the solar heating collector temp:
or boiler temps:
While this is not nice - and I like to know where this is coming from, it’s no showstopper. But Theres now the situation that the fibaro plug for the floor heating pump is certainly off (as its warm) - but insights does report it as bein on in the graph. This means the graph is not reliable - only detectable by doing some debugging by scrolling through the history or spotting ‘glitches’ in other graphs.
Heres the ‘suspicious’ plug in insights:
And the status and history (switched off since 1h):
The funny thing is that this seems to be triggered by switching from ‘last 6h’ to ‘last hour’ because some hours before it was working nicely:
In the upper graph the pink and magenta switching does not happen in the second on time of the pump plug (green) as it is not on, but the graph indicates it wrongly.
I’ve also seen several red ‘timeout’ messages in the insight graphs bottom area - only when scaling for ‘last hour’ and scrolling through the various graphs - that becomes a necessity hence there is no way to sort them.
The app consumes moderate memory
App performance in the Dev tools show nothing unexpected (i think)
Has anyone seen similar behavior while using insights - is there a way to fix this or debug?
Any feedback is very welcome.
best regards and happy 2026!
Update: found some memory clean-up with 100% CPU load in Homey statistics insights happened at that time:
