SmartThings Community

NEW: Aeon Home Energy Monitor v2 Device

dth_powermeter

(Barry) #368

Bummer - it really screws up my Ecobee Thermostat Suite, because it displays the (somewhat meaningless) gibberish states I use to select from the 20 or so Thermostat Operating State icons I display.

But Monday is better than never - so, thanks!

(Now, if we could just get the Android thermostat multiAttributeTile to display the same operating state text in the bottom row as the iOS one again, AND maybe get icon sizes and font sizes to be the same on both iOS and Android, THEN I’d be a happy camper!)

:slight_smile:


(Steve) #369

Actually, if you’re willing to do some hacking, you could try something like unit: '', label: '${unit}'. Notice the single quote and not the double quote. The mobile apps should parse anything within ${} as a variable on state. What’s currently happening is that label is being defaulted to label: '${name}', which ends up parsing state.name into the label. So if you’re not using unit or labelIcon or some other rarely used attribute on state, you might be able to get an empty string to render. This is of course pretty hacky, and will ultimately not be needed beyond this weekend, but that’s how it works. I am a little confused as to why label: '' is getting overridden, but I’ll dig in and figure it out.

As for the icons and fonts in the mobile apps, I can file some bugs, but I can’t promise that they’ll get prioritized as quickly as you might like.


(Barry) #370

On the labels, I’ll just wait for it to go back to the way it was. For some states, I DO specify a label, others I don’t.

I will note that something has caused the thermostat MultiAtributeTile to show the SmartThings icon instead of the water drops icon for the Humidity display…

On icons and fonts, it really makes SmartThings look shoddy on Android, and given that Samsung is deeply invested in Android, I’d think someone would want to put in the extra effort to make it look as good as iOS - with the exception being that the font used for values doesn’t auto-scale on iOS as it used to, so the text always seems to exceed the size of the icon (like trying to display “Hum 45%”).

Finally, the worst Android offender is the Thermostat multiAttributeTile - and it is aggravating because I managed to get it prioritized and fixed once, but it reverted recently. It’s a bit complicated, but here’s the deal:

On iOS, the text at the bottom/middle of the box will say “Heating at 70” when the thermostat operating state is “idle”, and “Heating to 70” when the thermostat operating state is “heating.” I use this to display the ACTUAL temperature that will cause a demand for heat, as in “Heating at 69.5” (my Ecobee Suite allows one to choose how many decimal points are displayed for all temperatures). On Android, this currently shows “Heating to 69.5” - it always says “Heating to ##” (note, all this is also true for “Cooling at/to”…). This one I’d REALLY like to get fixed (again)…

Thanks for listening!


(Ron Talley) #371

How do you know if it’s v2? I’m looking at this one…


(Barry) #372

Aeon HEM V2/Gen 2 has an AC plug, doesn’t run on batteries…


(Barry) #373

It looks like something has caused every single temperature colored device, including those supplied by SmartThing, to now show only Grey background, no matter the value…it this possibly a side-effect of the fix installed yesterday?


(Steve) #374

Definitely. These issues should be cleared up now, though. You can read more about it here: Recent Tile Bugs (2.14.0)


(Mike) #375

Looks good now, thanks :+1:


#376

This may be a stupid question, but what is the repository name so I can integrate it into smartthings?


(Barry) #377

As I noted earlier, I am not actively managing this device anymore. It was developed before the SmartThings GitHub integration, and as such is not structured to be integrated into smartthings. Just the good old copy/paste approach, I’m afraid. But it isn’t changing any more, at least not until SmartThings fixes the things that are broken in the UI (font sizes used to scale, now they don’t; things work very differently on Android and iOS, etc.).


#378

Ok, thanks for the quick reply. I searched this discussion but did not find that. It seems to be working well enough. I am using an android phone. At least with your handler I can see usage from each leg.


Aeon hem v2 stops updating smartthings
#379

Hey Terminal, how did you get the KWH’s to reset. Reset is not working for me either?


(Mike) #380

I modified the device handler. Inside the reset command of the DTH I moved the following line outside of the CMD definition. See below:

return zwave.meterV2.meterReset().format() // Reset all values
pause(1000)
def cmd = delayBetween( [
//zwave.meterV2.meterReset().format(), // Reset all values
zwave.meterV2.meterGet(scale: 0).format(), // Request the values we are interested in (0–>1 for kVAh)
zwave.meterV2.meterGet(scale: 2).format(),
zwave.meterV2.meterGet(scale: 4).format(),
zwave.meterV2.meterGet(scale: 5).format()
], 1000)

I remarked out the line that says reset all values and put it above as a stand alone statement.
I wrote a smartapp that calls the reset command on the 29th of the month, that is when my meter is read. It seems to work.

Maybe someone knows why the line had to be moved out, I just know it works this way and would not the other.


#381

@storageanarchy, Would you be willing to commit this change?


#382

This worked great, thanks. Toom me a minute to find haha.


(Omar D Ruiz Morales) #383

I read the past month invoice and divide my $ by kw to get the kw cost. In my case is .22 cents. Then in the device handle I modified for my use I write the cost and it display and forecast $


(Omar D Ruiz Morales) #384

Each time you reset the meter on setting you have to change the last reading on the meter and the cicle date.

Mine I reset it when I receive the invoice. Then I go to the settings and change values and start fore casting the next month.

I used it about a year and the diferences from the forecasting and the real invoice is aabout 3$.

Is working fine for me!


(Brock Haymond) #385

Hey all! Its been a while! I just updated my code for the V1 version, fixed a couple bugs, and update the color scheme to something a little more eco friendly.

Note: I have hid the battery as I imagine most people don’t run these off batteries and the 0% battery can be annoying. I also did some other trimming down to simplify the interface for us V1ers who don’t have as much data to display. Also, the wattage coloring goes all the way to red at 3000 watts so depending on how much your home uses (mine is very low) you might want to adjust the table upwards.

            backgroundColors:[
                [value: "0",    color: "#1DB100"],
                [value: "500",  color: "#61D836"],
                [value: "1000", color: "#88FA4E"],
                [value: "1500", color: "#F8BA00"],
                [value: "2000", color: "#FF968D"],
                [value: "2500", color: "#FF644E"],
                [value: "3000", color: "#EE220C"]


(Eric) #386

thank you for the update.

I am afraid to touch mine since it mostly works.

I noticed only one zinger value (spurious reading in the billions of watts I think) in the past couple years.

OOPS I see now your header says v2 but your screenshot and preface is v1.


(Scott) #387

Could you share a copy of your DTH??