Aeon Labs ZW095-A - Z-Wave Plus - Home Energy Meter Gen 5

Devices & Integrations Connected Things
63

Hi everyone

Question 1) :

@Dillon_Miller, does the code need any adjustments to work with reporting positive and negative values for homes equipped with a PV solar system? The manufacturer mentions that there is a parameter that by default only reports the absolute value:

If install on my main service lines and my solar system is generating more than I consume, what will this device report?
Answer: Looking in the manual available here: https://aeotec.freshdesk.com/support/solutions/articles/6000088070-gen5-6
Parameter number 2 shown on page 6 can be set to the following settings.
0 = report power, energy absolute value;
1 = report positive/negative power, report the algebraic sum energy;
2 = report positive/negative power, only report energy positive part (consuming electricity);
3 = report positive/negative power, only report energy negative part (generating electricity);
I do not have any power generation so I cant say it works, but the option is there. see less
By Amazon Customer on January 28, 2017

Link:
https://www.amazon.com/forum/-/Tx1NZTFLA1OSHTW/ref=ask_dp_dpmw_al_hza?asin=B00XD8WZX6

Q 2) Also, does anyone know if there is code to reset the kWh generated every day at a certain time (e.g. midnight or sunrise/sunset)?

Thanks!

Z

1 Like
64

hi Z_Ali.

I did have to modify the code to set parameter 2 to 1 to show negative values and it appears to be working.

I forked to code here https://gist.github.com/herbcarroll/3132225494bcf3b801d34ae7dd080245

1 Like
65

Thanks @herbcarroll!

Question for you: At the end of each day (or whichever unit of time that you use between resets) are you seeing a single cumulative value tile that represents the sum of both positive and negative power amounts reported? Or is there a way to view two sums (two tiles); the sum of all positive power generated separately from the sum of all negative power generated?

Thanks!

Z_Ali

66

Hi @Z_Ali

IMG_2938.PNG1242×2208 130 KB

This is what Im seeing now on a clear day. The total seems right. I would be expecting to push about 2kW into the grid .

My panels are producing over 3kW (see image of my device handler for my solar envoy below) and my house isn’t running anything significant and runs between 0.6kW and 1kW, so the Total seems right but I have no idea how to read the Pole’s are what they mean and Im not 100% convinced they’re in my box correctly. I just made sure the have the clamps in opposite directions.

IMG_2939.PNG1242×2208 134 KB

67

Thanks again, @herbcarroll . I appreciate the reply!

I added the lines of code where you set the parameterNumber 2 to a value of 1 in the device handler code and published the code to myself, but I still see no negative numbers in the smart things app either during the day or the night. Is there something I have to restart or some action I need to do to have the changes implemented? Thanks

Z_Ali

68

Yes. Try changing a setting in the device configuration. That will cause the configure routine to get executed.

69

Thanks! I will try that. Hopefully when the sun rises tomorrow I will see a change in the sign from positive to negative.

70

I just received my HEM the other day and installed it using the custom DH from Dylan. However it seems that I only get data populated for Volts and the Current on L1 and L2. I can’t see any wattages for either the total or each leg. Pressing the confit button doesn’t seem to do anything. Under the event tab I can see voltage data coming in every 5-6 seconds but rarely any data for the current and wattage.

Now here’s the interesting part. As soon as I got to work and connected to WIFI there
boom
data came right in. Difference now is that it is not polling the voltage data constantly like at home but exactly those data that have been configured in the app. (60,30,6)

Someone with similar experiences? Appreciate the support or feedback

71

@Easyschnucki - Are you sure you have the hardware installed correctly? Are the arrows facing opposite directions on the mains? I havent experienced the situation that you’re describing myself, so I’m just trying to think of what might be causing unusual readings. One thing that I I will mention is that pressing the Configure button may not do exactly what you think it should do, its more like a “Send current configuration values to the controller” type of function. To actually change configuration values you hit the gear icon on the top right, change your values, press Done, and then “apply” them by pressing the Configure button with the wrench/socket icon.

@herbcarroll - Unfortunately changing the configs didnt actually cause any values to change signs from positive to negative or vice versa for me. Just as a clarification, are you actually seeing different signs during the day and night? Like if you see positive values during the day when you are producing more than you consume, do you see negative values at night when it is impossible to produce? Or alternatively if your signs are flipped - if you see negative values during the day, do you see positive values at night? I know for a fact that around midday I produce more than I consume, and so I am sending energy to the grid but at night when there is only consumption from the grid I still see the same sign as during the day when I push energy to the grid.

Thanks

72

Z-Ali

Jupp Hardware is fine. I just though it’s odd that upon installation I only get half the data and then once I’m gone and not connected to my home network then it works as desired. It’s been fine ever since. Thanks for your thoughts


73

Hello Everyone. I just installed this handler. The Logs in IDE show:

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 248

Also when clicking the configure button in the app, “Error refreshing page displays”

Any ideas?

74

has anyone logging current, current1, and current2 had current report fine but current1 and current2 report as text? i’m getting values in my smartapp but am having trouble logging the values as numbers. seems to be getting "\ " in front of the number so it appears to be a string. not sure where to narrow it down.

using an Aeon HEM Gen5, influxdb 1.1.1, and grafana for graphing. i’m thinking it has to do with how the data value is sent to influxdb but since the attributes are defined as “numbers” that data sending to influx appears to be generic (data sent is same as for current & current is fine), i’m trying to narrow down any logical places to look. data seems to be reported to smartthings as numbers (2nd pic), but i’m not sure if that is correct.

Screen Shot 2017-04-28 at 7.19.16 AM.jpg717×112 16.9 KB

originally used codersaurs smartapp (modified a little bit for clamp1 clamp2 reporting and attribute definition as numbers), https://github.com/codersaur/SmartThings/tree/master/smartapps/influxdb-logger

and the DTH from https://gist.github.com/DuncanIdahoCT

75

Hi all,

Sorry I’ve been absent from this thread. Life happens
 I’m going to do a code review after the latest ST firmware and app updates and see if I can clean some issues up with the DH.

As an aside
 My HEM5 device periodically stops reporting even though it seems to be perfectly fine in the ST app. The solution (in the past, before the latest ST Hub/App updates) when this happens has been to initiate a replace of the device from inside the settings option of the ST app HEM device screen. Then I turn it off and wait say
 30s plug it back in and press the zwave action button on the HEM so that it can be picked up as a new(replacement) device. While this means you’ll basically see a stats reset in the device tiles, it prevents the need to remove the device from all related smart apps or other far flung IFTT triggers or polling services and then re-add it to all those placed. i.e. it retains the device ID in the ST graph. Anyone having unexplained troubles with the unit or if it never really worked the first time you added it, you may want to use the replace option.

My ST device connectivity experiences in general
 for some reason I have to replace or completely recreate random ST devices around my house now and then (maybe every 3-4 months) for really no good reason that I can ever come up with. There is one light switch that has been particularly troublesome. It simply vanishes, leaving the smartapps wondering where it went, and Alexa/IFFT have an orphaned object that won’t work
 I have replaced the physical switch and swapped it with another that has never had issue and it continues to either stop responding or completely disappear (bizarre right?) from the whole system. I believe it has something to do with the ST object database, perhaps when there is a glitch in an IFTT trigger operation or other ST API call it causes the ST object to glitch out and vaporize itself. No idea


I mention the above because that it tells me that some of our interesting or unexplained problems with the HEM may not be anything specific to the HEM. It could simply be a zwave network glitch related to the ST Hub or some other ST cloud/db/api problem that causes the HEM to
 stall for lack of better word. I’m sure we’re all doing similar secondary polling of the HEM data off to some reporting site such as Initial State or something like old plottwatt and our devices are added to other smartapps like ActionTiles, etc
 I have never had issue with simple devices that I add to simple SmartApps. I only have connectivity or stall issues with devices (simple like switches or complicated like the HEM) when they’re added to complicated API based SmartApps.

I’ll try to be more active now that life has calmed some for me.

Regards,
-Dillon

76

I installed this today along with the DTH from https://gist.github.com/DuncanIdahoCT. I have the two phase/two clamps on the two mains coming into the panel, I made sure to have one with the arrow facing up, one with the arrow facing down. I have tried switching the clamps from each pole, the results being the same except showing 0 values for one of the poles. Also, after all the breakers have been shut off (except the dedicated 20amp I have the HEM hardwires to), it still shows some wattage in one of the tiles, although according to my log and looking at the actual device on smart things, its reporting 0, as there is no usage. Pretty confused here, shouldn’t I see some activity for the second clamp on a standard US 2 phase 200amp service? Why would clamp direction even matter with AC power
then after shutting everything off, one tile will continue to say 330W when the actual is 0W

Here are the debug logs from my DTH:

a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:26 PM: debug Parsed 'zw device: 21, command: 9881, payload: 00 85 03 01 05 00 01 ’ to null
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:26 PM: debug —ASSOCIATION REPORT V2— Energy Meter (Shop) groupingIdentifier: 1, maxNodesSupported: 5, nodeId: [1], reportsToFollow: 0
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:26 PM: debug encapsulated: AssociationReport(groupingIdentifier: 1, maxNodesSupported: 5, nodeId: [1], reportsToFollow: 0)
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:26 PM: debug Parsed 'zw device: 21, command: 9881, payload: 00 70 06 71 04 00 00 00 06 ’ to null
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:26 PM: debug —CONFIGURATION REPORT V1— Energy Meter (Shop) parameter 113 with a byte size of 4 is set to [0, 0, 0, 6]
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:26 PM: debug encapsulated: ConfigurationReport(configurationValue: [0, 0, 0, 6], parameterNumber: 113, reserved11: 0, scaledConfigurationValue: 6, size: 4)
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:25 PM: debug Parsed 'zw device: 21, command: 9881, payload: 00 70 06 70 04 00 00 00 1E ’ to null
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:25 PM: debug —CONFIGURATION REPORT V1— Energy Meter (Shop) parameter 112 with a byte size of 4 is set to [0, 0, 0, 30]
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:25 PM: debug encapsulated: ConfigurationReport(configurationValue: [0, 0, 0, 30], parameterNumber: 112, reserved11: 0, scaledConfigurationValue: 30, size: 4)
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:25 PM: debug Parsed 'zw device: 21, command: 9881, payload: 00 70 06 6F 04 00 00 00 3C ’ to null
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:25 PM: debug —CONFIGURATION REPORT V1— Energy Meter (Shop) parameter 111 with a byte size of 4 is set to [0, 0, 0, 60]
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:25 PM: debug encapsulated: ConfigurationReport(configurationValue: [0, 0, 0, 60], parameterNumber: 111, reserved11: 0, scaledConfigurationValue: 60, size: 4)
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:24 PM: debug Parsed 'zw device: 21, command: 9881, payload: 00 70 06 66 04 00 18 00 08 ’ to null
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:24 PM: debug —CONFIGURATION REPORT V1— Energy Meter (Shop) parameter 102 with a byte size of 4 is set to [0, 24, 0, 8]
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:24 PM: debug encapsulated: ConfigurationReport(configurationValue: [0, 24, 0, 8], parameterNumber: 102, reserved11: 0, scaledConfigurationValue: 1572872, size: 4)
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:24 PM: debug Parsed 'zw device: 21, command: 9881, payload: 00 70 06 67 04 00 00 03 02 ’ to null
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:24 PM: debug —CONFIGURATION REPORT V1— Energy Meter (Shop) parameter 103 with a byte size of 4 is set to [0, 0, 3, 2]
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:24 PM: debug encapsulated: ConfigurationReport(configurationValue: [0, 0, 3, 2], parameterNumber: 103, reserved11: 0, scaledConfigurationValue: 770, size: 4)
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:23 PM: debug Parsed 'zw device: 21, command: 9881, payload: 00 70 06 65 04 00 00 18 05 ’ to null
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:23 PM: debug —CONFIGURATION REPORT V1— Energy Meter (Shop) parameter 101 with a byte size of 4 is set to [0, 0, 24, 5]
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:23 PM: debug encapsulated: ConfigurationReport(configurationValue: [0, 0, 24, 5], parameterNumber: 101, reserved11: 0, scaledConfigurationValue: 6149, size: 4)
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:22 PM: debug Parsed 'zw device: 21, command: 9881, payload: 00 70 06 08 01 05 ’ to null
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:22 PM: debug —CONFIGURATION REPORT V1— Energy Meter (Shop) parameter 8 with a byte size of 1 is set to [5]
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:22 PM: debug encapsulated: ConfigurationReport(configurationValue: [5], parameterNumber: 8, reserved11: 0, scaledConfigurationValue: 5, size: 1)
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:20 PM: debug Parsed 'zw device: 21, command: 9881, payload: 00 60 0D 01 00 32 02 21 64 00 00 00 00 00 40 00 00 00 00 ’ to null
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:20 PM: debug encapsulated: MultiChannelCmdEncap(bitAddress: false, command: 2, commandClass: 50, destinationEndPoint: 0, parameter: [33, 100, 0, 0, 0, 0, 0, 64, 0, 0, 0, 0], sourceEndPoint: 1)
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:19 PM: debug Parsed 'zw device: 21, command: 9881, payload: 00 60 0D 02 00 32 02 21 64 00 00 00 00 00 40 00 00 00 00 ’ to null
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:19 PM: debug encapsulated: MultiChannelCmdEncap(bitAddress: false, command: 2, commandClass: 50, destinationEndPoint: 0, parameter: [33, 100, 0, 0, 0, 0, 0, 64, 0, 0, 0, 0], sourceEndPoint: 2)
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:19 PM: debug Parsed 'zw device: 21, command: 9881, payload: 00 60 0D 02 00 32 02 A1 6C 00 00 00 00 00 00 00 00 00 00 ’ to null
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:19 PM: debug encapsulated: MultiChannelCmdEncap(bitAddress: false, command: 2, commandClass: 50, destinationEndPoint: 0, parameter: [161, 108, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], sourceEndPoint: 2)
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:18 PM: debug Parsed 'zw device: 21, command: 9881, payload: 00 60 0D 01 00 32 02 A1 6C 00 00 00 00 00 00 00 00 00 00 ’ to null
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:18 PM: debug encapsulated: MultiChannelCmdEncap(bitAddress: false, command: 2, commandClass: 50, destinationEndPoint: 0, parameter: [161, 108, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], sourceEndPoint: 1)
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:17 PM: debug Parsed 'zw device: 21, command: 9881, payload: 00 32 02 21 64 00 00 00 00 00 0D 00 00 00 00 ’ to [‘name’:‘energy’, ‘unit’:‘kWh’, ‘displayed’:false, ‘value’:0.000, ‘isStateChange’:false, ‘linkText’:‘Energy Meter (Shop)’, ‘descriptionText’:Energy Meter (Shop) energy is 0.000 kWh]
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:17 PM: debug encapsulated: MeterReport(deltaTime: 13, meterType: 1, meterValue: [0, 0, 0, 0], precision: 3, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 0, scale2: false, scaledMeterValue: 0.000, scaledPreviousMeterValue: 0.000, size: 4)
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:17 PM: debug Parsed 'zw device: 21, command: 9881, payload: 00 32 02 A1 6C 00 00 00 00 00 00 00 00 00 00 ’ to [‘name’:‘current’, ‘unit’:‘A’, ‘displayed’:false, ‘value’:0.000, ‘isStateChange’:false, ‘linkText’:‘Energy Meter (Shop)’, ‘descriptionText’:Energy Meter (Shop) current is 0.000 A]
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:17 PM: debug encapsulated: MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 0, 0, 0], precision: 3, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 5, scale2: false, scaledMeterValue: 0.000, scaledPreviousMeterValue: 0.000, size: 4)
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:06 PM: debug Parsed 'zw device: 21, command: 9881, payload: 00 32 02 A1 64 00 01 E3 F5 00 00 00 00 00 00 ’ to [‘name’:‘voltage’, ‘unit’:‘V’, ‘displayed’:true, ‘value’:123.893, ‘isStateChange’:true, ‘linkText’:‘Energy Meter (Shop)’, ‘descriptionText’:Energy Meter (Shop) voltage is 123.893 V]
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:06 PM: debug encapsulated: MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 1, 227, 245], precision: 3, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 4, scale2: false, scaledMeterValue: 123.893, scaledPreviousMeterValue: 0.000, size: 4)
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:05 PM: debug Sending configure commands - kWhCost ‘0.0685’, monitorInterval1 ‘60’, monitorInterval2 ‘30’, monitorInterval3 ‘6’
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:04 PM: debug Parsed 'zw device: 21, command: 9881, payload: 00 32 02 21 64 00 00 00 00 00 32 00 00 00 00 ’ to [‘name’:‘energy’, ‘unit’:‘kWh’, ‘displayed’:false, ‘value’:0.000, ‘isStateChange’:false, ‘linkText’:‘Energy Meter (Shop)’, ‘descriptionText’:Energy Meter (Shop) energy is 0.000 kWh]
a465e7ca-659a-4b27-abdf-8fa1518c427e 10:54:04 PM: debug encapsulated: MeterReport(deltaTime: 50, meterType: 1, meterValue: [0, 0, 0, 0], precision: 3, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 0, scale2: false, scaledMeterValue: 0.000, scaledPreviousMeterValue: 0.000, size: 4)

IMG_0938.PNG1242×2208 180 KB
IMG_0939.PNG1242×2208 179 KB

77

Only thing currently on, on this 200a service is a motion light and a porch light. I have the 2 clamps on each of the wires coming into my split phase panel, have the clamps going in the opposite direction too. Not sure what is going on or why this is giving me 0 readings for my L2 or second clamp.

IMG_0940.PNG1242×2208 180 KB

78

I have the same issue with the 2nd version of the HEM. However in my case all I have to do to get it to report data is power cycle it. I installed it in the outdoor’s electrical panel behind a dedicated breaker so it is easy to power cycle without opening the box. After a short period it starts reporting again. It used to drop out more frequently and I am not sure what contributed to lessening the frequency
 I modified the DTH substantially and I added more zwave devices closer by to make sure it was not related to signal issues. It has always appeared to me as the HEM was still keeping track of power usage but would simply stop reporting it to the ST app.

79

Hi, I’m new to Smartthings and was previously using Alarm.com’s app for everything. I have the Gen5 energy monitor installed and it was working well with Alarm.com. I seemed to pair to the smartthings fine as a Generic Zwave device and have the device handler added however I only see a few things on the app and can’t seem to do much. The configure button is doing nothing, and there is a blue circle on the main screen that just keeps spinning. I do see a reported KWH number but it does not update. If I swipe to the right, I see a history of the KWH every two minutes but that’s all. I don’t get all the stuff everyone else in this post is referring to (Amps etc.).

Can you help me figure this out?
Thanks,
Bob

80

Hi Again,
For some reason the handler now appears to be working. I’m getting readings now but don’t seem to be able to set the button on the dashboard to show current consumption rather than total energy. Is it possible to change that? Also, I thought there should be the ability to set different ways to visualize the energy (graphs etc). If I select the “gear” icon I get a page that says “something is wrong”“we can’t load your screen right now”.

Any help would be appreciated with these issues,
Thanks,
Bob

81

That’s a pretty panel

82

Guys it is now February 2018. Is this the most up to date code everyone is using? I am thinking about purchasing one of these (cause I don’t want to spend $350 for the others out there). Before I do, I just want to make sure it will do what I want it to. I just what to be able to see the power produced from the solar panels, the amount of power I used, the amount of power sold back to the grid, and the amount of power purchased from the grid.

This might not be possible since there is only one set of CTs and I think I would need one set for the Solar Panel wires and one set for the Grid wires. Any help or advice would be awesome. TIA