[OBSOLETE] Aeotec Home Energy Meter Gen 5 composite DTH

beyercj22 · March 7, 2018, 12:19pm

After about 12 hours of use, I am now getting the Sync Incomplete message. Previous suggestions in this post didn’t help resolve the issue. Any suggestions?

Raw Description zw:Ls type:3101 mfr:0086 prod:0102 model:005F ver:1.31 zwv:3.92 lib:03 cc:5E,86,72,98,56 ccOut:5A sec:32,60,70,59,85,7A,73 role:05 ff:9000 ui:9000 epc:2 ep:[‘3101 32’]

From the Live Log:
fe86ec0e-9c87-4a74-b171-dc766e3307d2 7:12:50 AM: info Aeotec HEM Gen5 - encapsulating command using Secure Encapsulation, command: MeterGet(reserved00: 0, reserved202: 0, scale: 5)
fe86ec0e-9c87-4a74-b171-dc766e3307d2 7:12:50 AM: info Aeotec HEM Gen5 - encapsulating command using Secure Encapsulation, command: MeterGet(reserved00: 0, reserved202: 0, scale: 4)
fe86ec0e-9c87-4a74-b171-dc766e3307d2 7:12:50 AM: info Aeotec HEM Gen5 - encapsulating command using Secure Encapsulation, command: MeterGet(reserved00: 0, reserved202: 0, scale: 2)
fe86ec0e-9c87-4a74-b171-dc766e3307d2 7:12:50 AM: info Aeotec HEM Gen5 - encapsulating command using Secure Encapsulation, command: MeterGet(reserved00: 0, reserved202: 0, scale: 0)
fe86ec0e-9c87-4a74-b171-dc766e3307d2 7:12:50 AM: info Aeotec HEM Gen5 - executing refresh()

cben0ist · March 22, 2018, 5:38pm

[UPDATE:For no apparent reason that issue just got fixed by itself after ~12h of failing…]

First, thank you for that amazing work on the DTH. Gen 5 received and installed yesterday. I hove some values on both clamps and the main but still that “Sync incomplete” status on my side too.
device securely instaled:

zw:Ls type:3101 mfr:0086 prod:0102 model:005F ver:1.31 zwv:3.92 lib:03 cc:5E,86,72,98,56 ccOut:5A sec:32,60,70,59,85,7A,73 role:05 ff:9000 ui:9000 epc:2 ep:[‘3101 32’]

Logging on:

info Aeotec HEM Gen5 Sync Incomplete
info Aeotec HEM Gen5 - Executing syncCheck()
info Aeotec HEM Gen5 - Parameter timeGroup2 value is 120 expected 120
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: ConfigurationReport(configurationValue: [0, 0, 0, 120], parameterNumber: 112, reserved11: 0, scaledConfigurationValue: 120, size: 4)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [112, 4, 0, 0, 0, 120], commandClassIdentifier: 112, commandIdentifier: 6, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 70 06 70 04 00 00 00 78
info Aeotec HEM Gen5 - Parameter group3 value is 0 expected 0
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: ConfigurationReport(configurationValue: [0, 0, 0, 0], parameterNumber: 103, reserved11: 0, scaledConfigurationValue: 0, size: 4)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [103, 4, 0, 0, 0, 0], commandClassIdentifier: 112, commandIdentifier: 6, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 70 06 67 04 00 00 00 00
info Aeotec HEM Gen5 - Parameter group2 value is 0 expected 0
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: ConfigurationReport(configurationValue: [0, 0, 0, 0], parameterNumber: 102, reserved11: 0, scaledConfigurationValue: 0, size: 4)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [102, 4, 0, 0, 0, 0], commandClassIdentifier: 112, commandIdentifier: 6, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 70 06 66 04 00 00 00 00
info Aeotec HEM Gen5 Sync Incomplete
info Aeotec HEM Gen5 - Executing syncCheck()
info Aeotec HEM Gen5 - Parameter group1 value is 2 expected 2
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: ConfigurationReport(configurationValue: [0, 0, 0, 2], parameterNumber: 101, reserved11: 0, scaledConfigurationValue: 2, size: 4)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [101, 4, 0, 0, 0, 2], commandClassIdentifier: 112, commandIdentifier: 6, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 70 06 65 04 00 00 00 02
info Aeotec HEM Gen5 - Parameter thresholdClamp2 value is 10 expected 50
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: ConfigurationReport(configurationValue: [0, 10], parameterNumber: 6, reserved11: 0, scaledConfigurationValue: 10, size: 2)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [6, 2, 0, 10], commandClassIdentifier: 112, commandIdentifier: 6, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 70 06 06 02 00 0A
info Aeotec HEM Gen5 - MeterReport received, ep: 0 value: 0.321 kWh
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: MeterReport(deltaTime: 4, meterType: 1, meterValue: [0, 0, 1, 65], precision: 3, previousMeterValue: [0, 0, 1, 65], rateType: 1, scale: 0, scale2: false, scaledMeterValue: 0.321, scaledPreviousMeterValue: 0.321, size: 4)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [33, 100, 0, 0, 1, 65, 0, 4, 0, 0, 1, 65], commandClassIdentifier: 50, commandIdentifier: 2, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 32 02 21 64 00 00 01 41 00 04 00 00 01 41
info Aeotec HEM Gen5 - MeterReport received, ep: 0 value: 0.202 A
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 0, 0, 202], precision: 3, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 5, scale2: false, scaledMeterValue: 0.202, scaledPreviousMeterValue: 0.000, size: 4)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [161, 108, 0, 0, 0, 202, 0, 0, 0, 0, 0, 0], commandClassIdentifier: 50, commandIdentifier: 2, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 32 02 A1 6C 00 00 00 CA 00 00 00 00 00 00
info Aeotec HEM Gen5 - MeterReport received, ep: 0 value: 120.647 V
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 1, 215, 71], precision: 3, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 4, scale2: false, scaledMeterValue: 120.647, scaledPreviousMeterValue: 0.000, size: 4)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [161, 100, 0, 1, 215, 71, 0, 0, 0, 0, 0, 0], commandClassIdentifier: 50, commandIdentifier: 2, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 32 02 A1 64 00 01 D7 47 00 00 00 00 00 00
info Aeotec HEM Gen5 - MeterReport received, ep: 2 value: 0.224 kWh
debug Aeotec HEM Gen5 - Parsed MultiChannelCmdEncap MeterReport(deltaTime: 121, meterType: 1, meterValue: [0, 0, 0, 224], precision: 3, previousMeterValue: [0, 0, 0, 223], rateType: 1, scale: 0, scale2: false, scaledMeterValue: 0.224, scaledPreviousMeterValue: 0.223, size: 4)
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: MultiChannelCmdEncap(bitAddress: false, command: 2, commandClass: 50, destinationEndPoint: 0, parameter: [33, 100, 0, 0, 0, 224, 0, 121, 0, 0, 0, 223], sourceEndPoint: 2)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [2, 0, 50, 2, 33, 100, 0, 0, 0, 224, 0, 121, 0, 0, 0, 223], commandClassIdentifier: 96, commandIdentifier: 13, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 60 0D 02 00 32 02 21 64 00 00 00 E0 00 79 00 00 00 DF
info Aeotec HEM Gen5 - MeterReport received, ep: 1 value: 0.097 kWh
debug Aeotec HEM Gen5 - Parsed MultiChannelCmdEncap MeterReport(deltaTime: 120, meterType: 1, meterValue: [0, 0, 0, 97], precision: 3, previousMeterValue: [0, 0, 0, 97], rateType: 1, scale: 0, scale2: false, scaledMeterValue: 0.097, scaledPreviousMeterValue: 0.097, size: 4)
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: MultiChannelCmdEncap(bitAddress: false, command: 2, commandClass: 50, destinationEndPoint: 0, parameter: [33, 100, 0, 0, 0, 97, 0, 120, 0, 0, 0, 97], sourceEndPoint: 1)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [1, 0, 50, 2, 33, 100, 0, 0, 0, 97, 0, 120, 0, 0, 0, 97], commandClassIdentifier: 96, commandIdentifier: 13, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 60 0D 01 00 32 02 21 64 00 00 00 61 00 78 00 00 00 61
info Aeotec HEM Gen5 - MeterReport received, ep: 2 value: 0.145 A
debug Aeotec HEM Gen5 - Parsed MultiChannelCmdEncap MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 0, 0, 145], precision: 3, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 5, scale2: false, scaledMeterValue: 0.145, scaledPreviousMeterValue: 0.000, size: 4)
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: MultiChannelCmdEncap(bitAddress: false, command: 2, commandClass: 50, destinationEndPoint: 0, parameter: [161, 108, 0, 0, 0, 145, 0, 0, 0, 0, 0, 0], sourceEndPoint: 2)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [2, 0, 50, 2, 161, 108, 0, 0, 0, 145, 0, 0, 0, 0, 0, 0], commandClassIdentifier: 96, commandIdentifier: 13, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 60 0D 02 00 32 02 A1 6C 00 00 00 91 00 00 00 00 00 00
info Aeotec HEM Gen5 - MeterReport received, ep: 1 value: 0.057 A
debug Aeotec HEM Gen5 - Parsed MultiChannelCmdEncap MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 0, 0, 57], precision: 3, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 5, scale2: false, scaledMeterValue: 0.057, scaledPreviousMeterValue: 0.000, size: 4)
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: MultiChannelCmdEncap(bitAddress: false, command: 2, commandClass: 50, destinationEndPoint: 0, parameter: [161, 108, 0, 0, 0, 57, 0, 0, 0, 0, 0, 0], sourceEndPoint: 1)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [1, 0, 50, 2, 161, 108, 0, 0, 0, 57, 0, 0, 0, 0, 0, 0], commandClassIdentifier: 96, commandIdentifier: 13, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 60 0D 01 00 32 02 A1 6C 00 00 00 39 00 00 00 00 00 00
info Aeotec HEM Gen5 - MeterReport received, ep: 1 value: 120.582 V
debug Aeotec HEM Gen5 - Parsed MultiChannelCmdEncap MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 1, 215, 6], precision: 3, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 4, scale2: false, scaledMeterValue: 120.582, scaledPreviousMeterValue: 0.000, size: 4)
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: MultiChannelCmdEncap(bitAddress: false, command: 2, commandClass: 50, destinationEndPoint: 0, parameter: [161, 100, 0, 1, 215, 6, 0, 0, 0, 0, 0, 0], sourceEndPoint: 1)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [1, 0, 50, 2, 161, 100, 0, 1, 215, 6, 0, 0, 0, 0, 0, 0], commandClassIdentifier: 96, commandIdentifier: 13, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 60 0D 01 00 32 02 A1 64 00 01 D7 06 00 00 00 00 00 00
info Aeotec HEM Gen5 - MeterReport received, ep: 0 value: 0.321 kWh
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: MeterReport(deltaTime: 11, meterType: 1, meterValue: [0, 0, 1, 65], precision: 3, previousMeterValue: [0, 0, 1, 65], rateType: 1, scale: 0, scale2: false, scaledMeterValue: 0.321, scaledPreviousMeterValue: 0.321, size: 4)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [33, 100, 0, 0, 1, 65, 0, 11, 0, 0, 1, 65], commandClassIdentifier: 50, commandIdentifier: 2, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 32 02 21 64 00 00 01 41 00 0B 00 00 01 41
info Aeotec HEM Gen5 - MeterReport received, ep: 0 value: 0.202 A
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 0, 0, 202], precision: 3, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 5, scale2: false, scaledMeterValue: 0.202, scaledPreviousMeterValue: 0.000, size: 4)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [161, 108, 0, 0, 0, 202, 0, 0, 0, 0, 0, 0], commandClassIdentifier: 50, commandIdentifier: 2, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 32 02 A1 6C 00 00 00 CA 00 00 00 00 00 00
info Aeotec HEM Gen5 - MeterReport received, ep: 0 value: 120.596 V
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 1, 215, 20], precision: 3, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 4, scale2: false, scaledMeterValue: 120.596, scaledPreviousMeterValue: 0.000, size: 4)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [161, 100, 0, 1, 215, 20, 0, 0, 0, 0, 0, 0], commandClassIdentifier: 50, commandIdentifier: 2, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 32 02 A1 64 00 01 D7 14 00 00 00 00 00 00
info Aeotec HEM Gen5 - MeterReport received, ep: 0 value: 0.202 A
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 0, 0, 202], precision: 3, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 5, scale2: false, scaledMeterValue: 0.202, scaledPreviousMeterValue: 0.000, size: 4)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [161, 108, 0, 0, 0, 202, 0, 0, 0, 0, 0, 0], commandClassIdentifier: 50, commandIdentifier: 2, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 32 02 A1 6C 00 00 00 CA 00 00 00 00 00 00
info Aeotec HEM Gen5 - MeterReport received, ep: 0 value: 120.583 V
debug Aeotec HEM Gen5 - Parsed SecurityMessageEncapsulation into: MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 1, 215, 7], precision: 3, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 4, scale2: false, scaledMeterValue: 120.583, scaledPreviousMeterValue: 0.000, size: 4)
debug Aeotec HEM Gen5 - Parsed: SecurityMessageEncapsulation(commandByte: [161, 100, 0, 1, 215, 7, 0, 0, 0, 0, 0, 0], commandClassIdentifier: 50, commandIdentifier: 2, reserved13: 0, secondFrame: false, sequenceCounter: 0, sequenced: false)
debug Aeotec HEM Gen5 - Parsing: zw device: 32, command: 9881, payload: 00 32 02 A1 64 00 01 D7 07 00 00 00 00 00 00
info Aeotec HEM Gen5 - encapsulating command using Secure Encapsulation, command: ConfigurationGet(parameterNumber: 103)
info Aeotec HEM Gen5 - encapsulating command using Secure Encapsulation, command: ConfigurationSet(configurationValue: [0, 0, 0, 0], defaultValue: false, parameterNumber: 102, reserved11: 0, scaledConfigurationValue: 0, size: 4)
info Aeotec HEM Gen5 - encapsulating command using Secure Encapsulation, command: ConfigurationGet(parameterNumber: 6)
info Aeotec HEM Gen5 - encapsulating command using Secure Encapsulation, command: ConfigurationSet(configurationValue: [0, 0, 0, 2], defaultValue: false, parameterNumber: 101, reserved11: 0, scaledConfigurationValue: 2, size: 4)
info Aeotec HEM Gen5 - encapsulating command using Secure Encapsulation, command: ConfigurationSet(configurationValue: [0, 50], defaultValue: false, parameterNumber: 6, reserved11: 0, scaledConfigurationValue: 50, size: 2)
info Aeotec HEM Gen5 - encapsulating command using Secure Encapsulation, command: ConfigurationGet(parameterNumber: 5)
info Aeotec HEM Gen5 - encapsulating command using Secure Encapsulation, command: ConfigurationSet(configurationValue: [0, 50], defaultValue: false, parameterNumber: 5, reserved11: 0, scaledConfigurationValue: 50, size: 2)
info Aeotec HEM Gen5 - Executing updated()
info Aeotec HEM Gen5 - sending config.

Any help is appreciated.
Thanks

aniceberg · July 5, 2018, 9:16pm

I’m about to purchase the HEM Gen 5 and wished to understand-- can this DTH help me to identify which of my home devices are consuming energy? Or can it only show me the load for any given subpanel in which I have the monitor installed?

Also, can anyone confirm that it works with firmware v1.31?

siwilson · July 6, 2018, 9:06am

I have had a 3-clamp Gen5 running faultlessly for over 2 months now. It reports the total load for each clamp so you would not easily be able to identify which specific devices are contributing to the total load. Not sure what firmware version. I can check later.

Nitrousbird · July 10, 2018, 9:56pm

I’m in the market for something that will do whole home current/wattage draw analysis per circuit. Will this accomplish this (without a huge learning curve).

Sense and a couple of it’s competitiors will do it but I’m not looking to spend $300+. Goal is to simply see which items are killing my electric bill and what adjustments I need to make.

I get I’ll need to install the device handler and the front end code; no biggie But is the data useful enough to narrow down to at least the draw per circuit?

Automated_House · July 10, 2018, 10:04pm

no it isn’t.

siwilson · July 11, 2018, 11:29am

This is the raw description of the one I have installed. I can’t get direct access to the device as it’s overseas.

zw:Ls type:3101 mfr:0086 prod:0002 model:005F ver:1.02 zwv:4.34 lib:03 cc:5E,86,56,72,98,5A sec:32,60,8E,70,59,85,7A,73 role:05 ff:9000 ui:9000 epc:3 ep:[‘3101 32,59,5E,98’]

Does this show Firmware 1.02?

rabramov · July 19, 2018, 6:30pm

Hi,

From some reason the Watt meter on the main panel stops updating ocasionally. The current could be 3 amps while showing 3500W.
The 3 amp is consistent with the 2 probes readings and the Watts reading is consistent in both probs.
Only the main panel numbers are off.

Any idea why it happens?
Thanks,
Ron

Ryan7777 · August 1, 2018, 6:58pm

TLDR WARNING:

My gen 5 - 2 clamp keeps freezing. At first it would do it any time there was any kind of power outage - but seemed to work as long as that didn’t happen - now it does it all the time!

I’ve removed it and re-included it 15 or 20 times now, it will either fail to update or update with some bogus number and then never respond again until the next time I struggle to get it to include properly.

It pains me to have to rip out the device handlers and start from scratch just in the off chance it may or likely won’t fix something.

I make sure to do secure inclusion, but even that seems to be hit or miss. It doesn’t seem like the double press of the action button really matters, it seems to lean towards secure inclusion, but a few times it came up unsecure and didn’t seem to care that I was tapping the button twice, and yes I am sure the button was pressed, no extra bounce.

I have mine hard wired to a spare breaker and I am positive neural and live are right and the clamps are right so I think the unit is just bad. I did have it in the box, but getting it there to mess with it was troublesome. I work in high voltage electronics for a living so I’m well aware of the dangers of that, but it was more of a hassle than anything else. Now it looks like garbage with wires sticking out between the box cover and the wall until I decide if I want to fight finishing the installation with a j-box and all that.

I get that Zwave is kind of like the Wild West, and no offense to ClassicGOD - I think the work they have done is solid and amazing for free work (I am assuming), but I do take issue with Aeotec acting like their products device handler is up to whomever to write when SmartThings is as mature as it is.

These things are far too expensive - they should be doing the hardware and the handlers in house with some QA in their process and It should work out of the box!

And again I know that there are a lot of hubs out there and Zwave was likely never intended to be pushed this far- but dang. How do these companies stay in business selling utter crap, incomplete products?

I think my next approach short of giving up on it ever working is to crack it open and add a big, fat hold-up capacitor in a key place to get it over the shorter outages/glitches (should have one already, Aeotec…) - but if I can’t get it to work at all, there may be no point. Then it’s to the junk box with it.

If ClassicGOD is still lurking around, what is the minimum safe updates to maybe keep this from locking up? Are the defaults ok or can you give a list of all the settings in the app that are as fail safe as possible? I’d like some fine resolution so I can see when smaller loads are starting or stopping - if I have to wait for a 100W watt change to occur, it seems like I would be missing a lot of my low wattage devices?

Thanks for reading my rant!

Pablo_Dominguez · August 8, 2018, 7:51pm

Help ClassicGOD!!!

I´m using Aeotec HEM V1, Your DH´s

Main window Ok, but the child (Second clamp) show no info…

Any Idea??

ClassicGOD · August 8, 2018, 8:14pm

Hi, sorry I rarely check the forums since I had other stuff happen in my life. Try distributing all the events you are interested in between all 3 groups and then set the group time intervals so they have minimum overlap - for me it’s 20, 24 and 27sec. Also check what firmware you are running (I’m running ver:1.02 - you can find it in raw description in the Devices tab of the IDE) and if needed update the firmware.

ClassicGOD · August 8, 2018, 8:14pm

There is a separate handler for the older HEM version on my github - aeotec-hem-g2.groovy try using it.

Pablo_Dominguez · August 8, 2018, 10:12pm

Thanks a lot!

M-TOWN · September 14, 2018, 4:40pm

Hey ClassicGOD can you help me please? I bought an Hem Gen 5 with 3 clamps integrated it in ST but the values are not correct and in the new ST app there is no value and the device is not available the other thing is i want that every clamp is an own device can you say if this is working?

ClassicGOD · September 14, 2018, 4:57pm

Make sure you installed both aeotec-hem-gen5.groovy and aeotec-hem-gen5-child-device.groovy handlers and selected the Aeotec HEM Gen5 handler for the device in the IDE. After that go to configuration and click done to create the virtual devices for all clamps.

I’m not on the new app yet so I can’t verify if it’s working there.

M-TOWN · September 15, 2018, 5:24pm

I think i made all right but still the values are shit

M-TOWN · September 15, 2018, 5:26pm

M-TOWN · September 15, 2018, 5:27pm

M-TOWN · September 15, 2018, 5:29pm

siwilson · September 15, 2018, 5:32pm

Your Aeotec sensor is not included in secure mode. I had issues with mine when it wasn’t in secure mode. you need to exclude it and re-include in secure mode. Ideally this needs to be done next/near to the hub and you should press the button on the sensor twice for secure mode. Once its in secure mode things should improve.

[OBSOLETE] Aeotec Home Energy Meter Gen 5 composite DTH

Customers

Developers

Download the SmartThings App