Hi,
is someone using the SimpleMovingAverageFilter with activated “timeBasedUpdates”?
-
SimpleMovingAverageFilter time based
-
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Thx, I had a look on this. I know the function already. My current device had the default config (update based calculation).
My idea was now it get the avg of a value of the last 5 minutes. This is my config.
When I do so, then my device gets updated one time only, after the specified time. A 2nd, 3rd… time will be not updated.
Example:
14:00:30 Recreated device
14:05:30 1st update
14:10:30 NO 2nd update
14:15:30 No 3rd update
.
.
.But I don’t want to exclude that I misinterpret the function…
-
@ortin This is a bug. I am working on this
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Works like a charm!
-
I have a little addition to this, though not time based:
SimpleMovingAverageFilter, size 144, input is a temperature updating once every 10 minutes so that means the output is an average covering circa the last 24 hours.
Now I’ve added a Min and Max stats to the list. I expected them to be the Min and Max values within those 144 samples. But as far as I can see, it’s never refreshed. I’ve been looking at a maximum value of 26 degrees (the sensor is a fridge thermometer) for over a year now. And I’m very sure the last time that temperature occurred was after last years holiday when we thawed out the fridge
Can you take a look into this as well?
