SmartThings Community

Troubleshooting Aeon Labs Home Energy Meter v1


(ocpd+adhd+alz+md+hfa+fms+lol=me :)) #21

At present (after waiting about 5 or 10 minutes), it shows nothing at all for one of them, and for the other one, it only has this…

d0be44f7-4fe9-40f9-9f30-a9843202ac7a 4:23:47 PM: debug Aeon Home Energy Meter configuring device


#22

Hi @sgnihttrams,

No question is stupid, trust me! I would tap on Configure just to make sure it’s set to report fairly quick. With my device type, it’s every 15 seconds. That can also be changed to just about anything. You don’t need to do anything on the device when tapping Configure.

Since you have some type of live log entry, it tells me that at least the device is paired. What we need to do now is see how well it’s paired.

If you’re using the device type I created above, what does the log show when you tap on either/both Reset tiles?

Next, let’s change 1 line of code to give us a little more debug info. Find line 105 in the code. It should look like this:

// log.debug "Parse received ${description}"

Now, remove the “//”. Save and “Publish for Me”. Almost immediately the log should start to show the raw data being sent from the HEM to ST. If not, tap of Refresh. Can you tell me what the logs show?

Also, what does the device detail look like in the IDE? Does it look something like this:


(ocpd+adhd+alz+md+hfa+fms+lol=me :)) #23

@johnconstantelo
I will take it one step at a time…

NOTE: Before I noticed this response from you, I went to the Aeon Labs site, downloaded the firmware and updated just now to see if that would help at all.

Now, your msg…

Done.

2b599c24-2f06-4602-babe-92f3137f5e69 9:05:44 AM: error groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method java.math.BigDecimal#multiply.
Cannot resolve which method to invoke for [null] due to overlapping prototypes between:
[class java.lang.Character]
[class java.lang.Number] @ line 131
2b599c24-2f06-4602-babe-92f3137f5e69 9:05:43 AM: debug My Aeon Home Energy Monitor v3 reset kWh/Cost values
2b599c24-2f06-4602-babe-92f3137f5e69 9:05:40 AM: error groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method java.math.BigDecimal#multiply.
Cannot resolve which method to invoke for [null] due to overlapping prototypes between:
[class java.lang.Character]
[class java.lang.Number] @ line 131
2b599c24-2f06-4602-babe-92f3137f5e69 9:05:40 AM: debug My Aeon Home Energy Monitor v3 reset max/min values
2b599c24-2f06-4602-babe-92f3137f5e69 9:05:22 AM: error groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method java.math.BigDecimal#multiply.
Cannot resolve which method to invoke for [null] due to overlapping prototypes between:
[class java.lang.Character]
[class java.lang.Number] @ line 131

2b599c24-2f06-4602-babe-92f3137f5e69 9:12:36 AM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 9:12:22 AM: error groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method java.math.BigDecimal#multiply.
Cannot resolve which method to invoke for [null] due to overlapping prototypes between:
[class java.lang.Character]
[class java.lang.Number] @ line 131
2b599c24-2f06-4602-babe-92f3137f5e69 9:12:22 AM: debug Parse received zw device: 10, command: 3202, payload: 21 64 00 00 00 00 00 3C 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 9:12:21 AM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 9:12:06 AM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 9:11:51 AM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 9:11:36 AM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 9:11:22 AM: error groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method java.math.BigDecimal#multiply.
Cannot resolve which method to invoke for [null] due to overlapping prototypes between:
[class java.lang.Character]
[class java.lang.Number] @ line 131
2b599c24-2f06-4602-babe-92f3137f5e69 9:11:22 AM: debug Parse received zw device: 10, command: 3202, payload: 21 64 00 00 00 00 00 3C 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 9:11:22 AM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00


#24

@sgnihttrams, that is excellent info, thanks for posting that. I just saw your reply as I was heading out for a couple hours, so give me just a little bit of time. As soon as I get back I’ll jump on this for you.


#25

@sgnihttrams I couldn’t wait…

For some reason, the default kWhCost value isn’t working. Do me a favor and Edit the device, and provide a cost value in the Preference. Anything will work, even 0. You can also do the in the IDE by clicking Edit.

Headed out now before my wife really gets upset…


(ocpd+adhd+alz+md+hfa+fms+lol=me :)) #26

I thought it was correct before with what was in there for the default, but it wasn’t. So, I made the modification so that it now has my correct kwh charge in there.


#27

Cool. Can you capture live event logs again to see if the error generated by line 131 has gone away?


(ocpd+adhd+alz+md+hfa+fms+lol=me :)) #28

@johnconstantelo
When I looked just now, it shows this…

2b599c24-2f06-4602-babe-92f3137f5e69 12:14:07 PM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:13:52 PM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:13:37 PM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:13:23 PM: debug Parse received zw device: 10, command: 3202, payload: 21 64 00 00 00 00 00 3C 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:13:22 PM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:13:07 PM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:12:52 PM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:12:37 PM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:12:23 PM: debug Parse received zw device: 10, command: 3202, payload: 21 64 00 00 00 00 00 3C 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:12:22 PM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:12:07 PM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:11:52 PM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:11:37 PM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:11:23 PM: debug Parse received zw device: 10, command: 3202, payload: 21 64 00 00 00 00 00 3C 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:11:22 PM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:11:07 PM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:10:52 PM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:10:37 PM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:10:23 PM: debug Parse received zw device: 10, command: 3202, payload: 21 64 00 00 00 00 00 3C 00 00 00 00
2b599c24-2f06-4602-babe-92f3137f5e69 12:10:22 PM: debug Parse received zw device: 10, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00


#29

@sgnihttrams Ok, that’s progress!

Here’s what mine looks like (after removing the //):

command: 3202, payload: 21 74 00 13 79 3C 00 00 00 00 4E 2B

Everything after “payload” changes as the meter’s data changes. What your data is telling me is that the device itself isn’t sending anything for some reason.

Before we try excluding and re-incuding the device to ST (forces a complete reset of the device), can you please verify a couple things?

EDIT: I just saw your note on the firmware update. I didn’t do that for mine since at one tine there was a problem I remember reading about. If all else fails, you may need to exclude and reinclude it since I’m not sure what the firmware change does/impacts anything once it’s install after joining a hub.

  1. The clamps in the electrical box are properly and securely clamped around each feed.

  2. The connection for the clamps at the bottom of the device are plugged and screwed all the way in.

  3. On the device itself, does the red light stay on constantly, or do you see it blink every so often?


(ocpd+adhd+alz+md+hfa+fms+lol=me :)) #30

@johnconstantelo

OK…here’s where my stupid shines brightest…I’m not using it like that. :blush:

I saw elsewhere how people were able to use both clamps separately to track power usage (at least on and off which is all I really care about in this immediate case) of two different devices.

So, that’s what I’m trying here.

However, in order to get a good handle on whether or not they are even working at all, I guess I will take this one out and connect it to the house mains. It’s just such a PITA having the breaker box outside, and not all open and easily accessible like in the product documentation pics.

If there is any chance you’d be able/willing to help me figure out the way I’d really like to use it, I will do whatever steps you want. Otherwise, let me know and I’ll go the route of testing on the house mains.

Oh…the light is on constant, and I have already removed and reconnected them, and have already unplugged and replugged/screwed-down each of the plugs.

Your thoughts?


#31

@sgnihttrams,

I found this note in Aeon’s documentation:

After a successful upgrade, remove all power from the HEM (USB and batteries) and exclude/remove the HEM from the old network.

Please make sure you do that, if you haven’t already. Then reinclude back to ST.

Ah OK. That would explain perhaps why payloads are empty. But since you updated the firmware, and if you didn’t exclude/reinclude, there’s no way to be sure. Can you verify you’ve done that, and if not, can you?

Also, I do remember reading a discussion about getting individual readings from each clamp instead of the HEM as a whole. Aeon’s documentation does say how to configure certain parameters to make that possible, but I haven’t spent any time with those. I’ve opted for their metering switch for most of my major appliances.

Also, in your first post above where you called in a support ticket to ST, I’m pretty sure this will take very low priority since you’re using a custom device type and are trying some more advanced device modifications beyond what ST’s “out of the box” device type will do. That’s why they told you to reach out to the community.

I don’t know if you should go to that extent. Based on what I’ve seen, your meter is working. You probably need to exclude and reinclude since you updated the firmware. I think because how you want to use them, and the parameters set in my device type, you won’t see any data.

I did a search in GitHub and found this device type:

https://raw.githubusercontent.com/Jmtyra/Aeon-HEM-v2/master/Aeon%20HEMv2.groovy

I believe the original code was for the HEM v1, but it’s been modified for HEM v2, as well as individual clamps. You could remove the comments from line 58 and comment out line 60 and see how that works.

I’ve included the developer of that code, @Jmtyra, for any insight. Sounds like they may have more experience with the parameters needed for individual clamp reporting.


(ocpd+adhd+alz+md+hfa+fms+lol=me :)) #32

@johnconstantelo
I did a complete removal and repairing of the one that I did the firmware update on already, earlier today.
So, not sure if doing it again would do any good, but I will, just in case.

On the device type thing…ya, I have tried several other device types, and nothing results in either of them reporting anything at all.

I even found a thread where they made a new device type for the HEM v1 that allows you to read both clamps separately, but no-go on either of mine.

If there is anything else that anyone can think of to try, I will do it.

As for SmartThings support, yep, I totally understand they’re overloaded. That said, I also know they are actually reaching out to me. I got another response today…they checked in to see how things are going, and mentioned that they saw I am trying your device type in there right now.

They didn’t have anything else to offer as of yet, but I’m not expecting it in the short-run with said workload, etc.

Seriously though, for my sanity if nothing else, I think the next step should be to connect to mains and see what we get. At least then we’ll know whether or not it is working in the originally intended state.

I really appreciate your assistance here, and will look for your donate link once I’m past this hurdle (whether that’s with an actual solution, or if I end up sending them back for refund).


#33

LOL, too funny. I’m always glad to help, so don’t worry about a donations link. It would be a good idea to get those clamps on your mains, and at least validate that the device is a good one. Keep me posted on what you do and how things turn out.


(ocpd+adhd+alz+md+hfa+fms+lol=me :)) #34

Thanks, man. I will connect it to the mains tomorrow and let you know…


(Charles) #35

Newbie here with a newbie issue. I picked up one of these of Amazon, but I’m not sure if I have v1 or v2. It’s labeled as Model DSB09104-ZWUS. It has a mini-USB power port as well as 4 AA batteries.

Can someone identify the version?

Am I right to believe it’s my choice whether to use the transformer-USB or the batteries for power? Any experience with how long the batteries might last?

Finally, and most importantly, I’m having no luck pairing it. I installed @johnconstantelo v3 device type. Then, at Marketplace: Connect new device, the (Android) app spins while the HEM flashes red.

Rather than just search for any new device, should I explicitly try to pair this particular device? If so, I’m not seeing it listed anywhere - should I see it in the Marketplace devices?

Thanks for any help.


(ocpd+adhd+alz+md+hfa+fms+lol=me :)) #36

@CAL7

Version info = not sure. I will check mine to see and get back to you though.
Generally speaking, if it was cheap ($40 or less), it’s v1, and if expensive (~$80-100), v2.

My understanding on power source is this…if it’s on battery, it won’t be able to act as repeater for the z-wave mesh, and it won’t report as often.

For pairing, you need to find the little black button on the inside. Once you put ST into pairing mode, click it once, and it should pair.

Obviously, I’m noobish here too though. So, take my responses above in that context. :slight_smile:


(Charles) #37

@sgnihttrams Thanks for the info.

As far as I can tell, both the hub and the HEM are in pairing mode (green flash on hub, red flash on HEM). But they aren’t seeing each other. At least for now, I am suing the USB power.


(ocpd+adhd+alz+md+hfa+fms+lol=me :)) #38

@CAL7 OK. I assume it’s a slow blink (though, I guess you wouldn’t know if you haven’t seen the other blink). If you haven’t done it yet, you need to click the little black button inside the device (you must open it to get to it).

If you’ve tried that and it’s still not working, you may need to run through an ‘Exclude’ first and then try pairing again.

If you don’t know how to do the exclude, let me know.


(Charles) #39

I would characterize it as a slow blink (after pressing the back button).

Frankly, include / exclude on Z-Wave seems like a black science to me. I have tried: 1) using a minimote, using a wink hub to exclude.

No assurances I’m doing that right, but I tried and the red blink is all I’ve got.

Appreciate all the help. Thanks.


#40

Use the ST app on your phone to do a general exclude, and when it starts press the button on the HEM. Afterwards, go ahead and include it back to ST.

If it’s blinking, it should be waiting be included; but to be safe go ahead and exclude it again. Reboot your hub afterwards as well, as good measure.