Downloaded the update.
It does seem to calculate the average correctly, but then I guess has an issue setting it or something. Still shows 64.5 on the dashboard.
Downloaded the update.
It does seem to calculate the average correctly, but then I guess has an issue setting it or something. Still shows 64.5 on the dashboard.
New version...
1.3.2 - 05/31/22 - Fixed issue with state.lastValue
When I check in HPM I don't see a new version.
Nope, as stated in the first post...
Brian - not sure why I can't figure this out...but I just noticed a log entry for a notification from a old child set up under Averaging Plus attempting to notify an old device I had set up (which failed of course).
I can't for the life of me figure out where I set that up. I am not seeing the field in Notifications section of your App. Haven't set up the Pushover Driver either.
I have no idea what you're talking about.
Going to have to show me a log or something.
That might make two of us.
If I have that Pushover set, where might I have configured TO WHERE that notification is getting pushed?
So, clue-less-ly I am looking for where I configured this message and the associated device(s) to send it to. I hope this isn't an update issue.
LOG ENTRY
Message:[AVE - temp - tank
ALERT devices in Tank are averaging a high temperature of 100.4F], was sent to Phone
Yeah,
well...
I was kinda thinkin it WAS
I'm running -
1.2.5 of Averaging Plus Child,
1.0.0 Parent,
and 2.3.2.134 of HE
and because of that I might be missing some things now eh?
Always be sure you're on the latest version. There is no sense troubleshooting an older version.
Noticed these updateversioninfo events appearing in the hub events log today - seems to be being updated every 5 seconds.. any ideas what could be causing this?
FYI- I’m on version 1.3.1 (rather than 1.3.2 referenced in your earlier post above). I’ve checked for updates in HACS and withing bundle manager but there doesnt seem to be any new versions available
It sends Bundle Manager its version info whenever the app runs.
What on earth is making this run every 5 seconds!? Now that's a problem.
So what exactly does the Max Delta value do? If I don't set it, the app complains about it.
But I can't figure out what it actually does. Right now the delta is -4 so I tried setting the max delta to 1 thinking the delta would change to -1 but nothing happened. I especially don't know what "only valid if Delta is too high or low" means. Valid in what way? Below, it says "Delta will only be used when it is too Low". Used where? By what? I see no way to actually do anything with this Max Delta.
Hi,
Would it be possible to add a time-based average option ? I don't want to average multiple sensors, I want to average the same sensor over time, to calculate a moving average, keeping a configurable number of previous records. There are two ways to calculate a moving average. One involves storing previous N values, and actually averaging them. Each time there is a new reading, you subtract the oldest reading from the average. The second approximates this by using the previously calculated average itself, so that you subtract /N from the average, before adding to it:
<moving_avg> = ((<moving_average> - <moving_avg>/N) + )/N
where N is the number of samples to keep (should be configurable).
Then, either there is a child device "refresh" action that triggers the next step and one does a periodic refresh in RM, or the app itself has a configurable refresh period.
I have already seen Average This, which does the above.... except the refresh only happens when a new reading is measured, rather than time-based.
Feature request :
I'm now using grafana and influx to plot data - in my most recent case I am graphing temperature fluctuations. My sensors provide 2 or 3 decimal places depending on the device. AP provides a decimal place of 1 with the round(1) function on line 463 and 493 of the Child App.
It was simple enough to mod these lines to round(2) but of course I'm only affecting the output of my averaged attribute. I don't use the weekly/today values personally, but I am sure others do.
Can you implement an enum array variable to apply to the outputs? I was thinking '1 2 or 3'. It would be ignored by the round being 'off' of course. Also, it may be correct to implement RoundingMode.HALF_UP for a more accurate rounding but at this detail level, I'm not sure it is the critical. TY for your work and time.
HI Guys, i cant seem to open any of @bptworld zip files from Git Hub. Please could someone paste the raw code for this app please into this thread. Appreciated....
I suppose this could be done but I'm assuming that these are the intellectual property of @bptworld , I'm not sure we are able to do this.
Maybe someone else would care to comment.
I understand. I'll use Variable math to accomplish the same outcome
The zip files should be able to be imported under the Bundles tab...
See post #2 in the Bundle Manager thread