Energy Cost Calculator

[swade]

Anyone else still using this App? I really like the app, but for a long time I would get erroneous readings from the 7 Aeotec Smart Energy Switch's I use. I have tried different device types over the last 18 months with no solution. The erroneous readings are random, very occasional - like 1 or 2 a month, and from different devices. The erroneous readings are also random and if I catch it right away I am able to erase it the but it skews the totals. This has been more of a nuisance and it seemed I didn't have the time to resolve until for some reason, now.

I searched the forum and to my great surprise I see the App is no longer maintained, and the author moved over to SmartThings. I sure hope he is happy!.

I have spent a few hours reviewing the code and made a couple of very minor changes to see it can solve my issues and ignore the erroneous device readings. I will be closely monitoring to see if this fixes my problem.

If you have modified the app and are willing to share I would appreciate it. Also, if you have had similar issues or different ones and would like to share that would be great.

[No Longer Maintained] Energy Cost Calculator

What is this? An app for calculating energy costs. The app leverages the new table method provided by Bruce to give a nice graphical display of costs per device and totals. The cost value for each device, along with the total, can be mapped to a hub variable. The hub variables can be used to display the cost in a dashboard tile or have a connector device created for sharing via Maker API. The energy consumption and cost values are updated anytime there is an energy update from any device, when…

[thebearmay]

Went out and looked at the code, assuming all you need is max value check per reading per device the code at https://raw.githubusercontent.com/thebearmay/hubitat/refs/heads/main/energyCostCalc/EnergyCalculatorPlus.groovy should work.

[swade]

I made a change to the max value check that was already in the code but then added a check on max cost allowed to prevent anything else getting through.

Of course, your change is more elegant, and I may just add it to mine!

Still wondering if anyone else is still using the app and seeing similar issues I was having. I even switched out devices to see if it was an individual device issue, but it was not.

Hoping these changes will resolve what I have been seeing.

[swade]

@thebearmay while I was updating my version with yours I think I spotted an error. The comparison should both be on energyCheck.

Here is your comparison

if(energyCheck > 500 || currentEnergy > settings["${maxVal$devId}"]) {

and I think it should be this

if(energyCheck > 500 || energyCheck > settings["${maxVal$devId}"]) {

Just mentioning in case someone else grabs your updated code.

[thebearmay]

energyCheck appears to be a total energy for the time period check, while currentEnergy is the value of event.

[swade]

The value of the event currentEnergy is the device's total since it was reset to zero. In the app each day it gets the last value of the prior day and stores it as daystart for each device. On each event during the day, it subtracts the daystart from device total energy (currentEnergy) to get energy for that point in the day. This is what is displayed and used to increment week and month values.

You can look at the apps states and see the energies map that stores each device's values.

[thebearmay]

I moved the check to the event handler instead of where it was - logic should do exactly what I intended in the first place now.