NEW: Aeon Home Energy Monitor v2 Device

Am I missing something with all the devicetypes for this device? Why are all the attributes strings? Aren’t watts a number? Amps? If the argument is that they have units, it seems ST supports that.

I’m not a real coder, I’ve done some very simple stuff, but this seems to go against my innate desire to treat a number as a number.

And I say this because these strings all have newlines in them presumably to make the interface nicer to look at. But if that breaks the interface, then it’s not nicer, is it? :smile:

1 Like

@bridaus you are correct with the value as the string. I just went through and removed the word after the value and now it works. However the color does not change on the tile. The device does report back in with the value and word such as 2000 watts. I’m no developer here just a system admin so I can fumble my way around through code so I’ll continue to see what I can do to asses this. I wonder if it might need some sort of regex or something.

Received this gem from Aeon technical support:

the HEM is configurable to show negative numbers as they do appear. You will need to set parameter 2 [1 byte dec] to 1. By default, this is set to 0 which reports the absolute value instead.

Woohoo!

@bridaus would this allow the value returned by the HEM to just be the straight value and not value + text? If so what needs to be changed in the device type?

Could someone if they have it share they’re code for automatically resetting the device after X number of days? I’d like to have mine reset on the last day of the month if thats possible.

i’ve got two HEM v2, they are reporting every 5-6 seconds, how can i adjust the report interval? Device ignores kWh/Detail report seconds settings.

log:
eac79b6e-53ac-4d53-b643-c1388529b86c 9:03:38 AM: debug Parse returned L2 Power: 3318 Watts
b580e793-59f1-4359-9eb9-9112836e079e 9:03:38 AM: debug Parse returned L2 Power: 435 Watts
eac79b6e-53ac-4d53-b643-c1388529b86c 9:03:38 AM: debug Parse returned L1 Power: 3708 Watts
b580e793-59f1-4359-9eb9-9112836e079e 9:03:38 AM: debug Parse returned L1 Power: 538 Watts
eac79b6e-53ac-4d53-b643-c1388529b86c 9:03:38 AM: debug Parse returned Total Power: 7026 Watts
b580e793-59f1-4359-9eb9-9112836e079e 9:03:38 AM: debug Parse returned Total Power: 972 Watts
b580e793-59f1-4359-9eb9-9112836e079e 9:03:33 AM: debug Parse returned L2 Power: 432 Watts
eac79b6e-53ac-4d53-b643-c1388529b86c 9:03:32 AM: debug Parse returned L2 Power: 3317 Watts
b580e793-59f1-4359-9eb9-9112836e079e 9:03:32 AM: debug Parse returned L1 Power: 523 Watts
eac79b6e-53ac-4d53-b643-c1388529b86c 9:03:32 AM: debug Parse returned L1 Power: 3600 Watts
eac79b6e-53ac-4d53-b643-c1388529b86c 9:03:32 AM: debug Parse returned Total Power: 6917 Watts
b580e793-59f1-4359-9eb9-9112836e079e 9:03:32 AM: debug Parse returned Total Power: 952 Watts
eac79b6e-53ac-4d53-b643-c1388529b86c 9:03:27 AM: debug Parse returned L2 Power: 3315 Watts
eac79b6e-53ac-4d53-b643-c1388529b86c 9:03:27 AM: debug Parse returned L1 Power: 3596 Watts
eac79b6e-53ac-4d53-b643-c1388529b86c 9:03:27 AM: debug Parse returned L2 Current: 26.66 Amps
eac79b6e-53ac-4d53-b643-c1388529b86c 9:03:26 AM: debug Parse returned L1 Current: 28.95 Amps
b580e793-59f1-4359-9eb9-9112836e079e 9:03:26 AM: debug Parse returned L2 Current: 4.18 Amps
b580e793-59f1-4359-9eb9-9112836e079e 9:03:26 AM: debug Parse returned L1 Power: 532 Watts
b580e793-59f1-4359-9eb9-9112836e079e 9:03:26 AM: debug Parse returned Total Power: 966 Watts
eac79b6e-53ac-4d53-b643-c1388529b86c 9:03:26 AM: debug Parse returned Total Power: 6912 Watts
eac79b6e-53ac-4d53-b643-c1388529b86c 9:03:26 AM: debug Parse returned Total Current: 55.60 Amps
b580e793-59f1-4359-9eb9-9112836e079e 9:03:26 AM: debug Parse returned Total Current: 9.68 Amps
b580e793-59f1-4359-9eb9-9112836e079e 9:03:20 AM: debug Parse returned L2 Power: 434 Watts
eac79b6e-53ac-4d53-b643-c1388529b86c 9:03:20 AM: debug Parse returned L2 Power: 3318 Watts
eac79b6e-53ac-4d53-b643-c1388529b86c 9:03:20 AM: debug Parse returned L1 Power: 3604 Watts
b580e793-59f1-4359-9eb9-9112836e079e 9:03:20 AM: debug Parse returned L1 Power: 530 Watts
b580e793-59f1-4359-9eb9-9112836e079e 9:03:20 AM: debug Parse returned Total Power: 964 Watts
eac79b6e-53ac-4d53-b643-c1388529b86c 9:03:20 AM: debug Parse returned Total Power: 6921 Watts

1 Like

I’m guessing that line 835 is causing my network to be flooded. Can perameter# 113 be added as a user configurable setting?

line 835: zwave.configurationV1.configurationSet(parameterNumber: 113, size: 4, scaledConfigurationValue: 6).format() // every 6 seconds

Also reset doesn’t reset total kWh, only the individual min and max for voltage, amps, watts.

I haven’t been following this thread closely but I would like to mention I had correspondence with Aeon after having problems with my device freezing and no longer sending data to the hub and he mentioned that many of the reporting times should be much longer than 60 seconds.

Here’s what he suggested changing:

1 Like

Did they give any indication on if this 240second allowance also applies if one is using the delta wattage mode?

No idea, I have lost much interest in this device now that it only reports every 4mins.

Mine works fine at every 6 seconds.

I am not sure what @bridaus does that all his stuff works. Did ya pay 199 dough instead of 99$?:wink: we should audit his devices! ;!)

Mine works every 6 seconds until it doesn’t. Then it comes back to life a few days later.

So, if you look closely, the app reports the REAL numbers as proper values, only posts the DISPLAY values as strings to that the UI can be optimized.

Unfortunately, SmartThings has not been able to make formatted strings work on Andriod for more than a year now - but the implementation works fine on IOS. If you don’t like my implementation, then by all means, change it…that’s the beauty of Open Source…

The Aeon engineer doesn’t know his own device - been running every 6 second updates for more than a year without problem.

The trick is that you can’t ask for EVERYTHING at 6 second intervals…you need to ask for different groups at different intervals (so I’ve learned). I run with L1/L2/Total Watts every 6 seconds; everything else reports at 30 or 60 seconds for me…works great with PlotWatt that way.

If I get a few minutes free from converting my 211 SmartThings and Apps over to my V2 Hub, I’ll update the AEON to allow configurable timings that work again. But I’ll not remove the formatting that breaks Android ST Mobile - that’s a problem SmartThings needs to solve…

Just to be clear, I LOVE your implementation. It’s just that I needed Android support, solar and calibration. It absolutely is the beauty of open source. I wish I was better at github, I’d try to help with small forks/merges and updating one type, that’s the only downside to open source is the splitting of the code base.

Credit to you for the updates to the ST device to get it where it is, all I did was based on your great work, and I thank you for it. If ever I’m not helping, or I can help more, let me know… HA is my favorite hobby, and I can sort of code…

Also, I was considering adding a switch for the differential reporting to the device, just to make sure that ST cloud isn’t having to support a lot of these with a lot of reporting. It’s the most active device in my logs by far. Debate is whether 5 or 10 watt reporting differential is too granular or not granular enough. Haven’t had time to test/think about it much.

I think I didn’t do any real editing during the unstable period. I think that’s how I escaped this issue in all seriousness. If I could have paid more for insurance against poltergeists, I probably would have, they are scary.

i’ve got two electric panels so i have two aeon meters. at 6 seconds it appears it is just too much data on my network or too much data gets backloged on the meter and they crash.

i’ve set 12 seconds and have not seen a crash/no data sent since.

how do i reset total kwh, reset doen’t?

Thank you for your efforts! Wonderful device handler!

Anybody know if the color changes are working with the latest android release? I haven’t had a chance to go uncomment the code yet.