[Depreciated] Aeotec HEM (Gen 5) ZW095-A Driver

It does not work with Make API now (most likely a driver issue), so yes it is broken.

but it looks like @shawn.foist got it paired with no security. Inconsistency in the intel is hard to keep up with.

Don't know if it matters but I did a hard reset on the HEM after removing from the C-5 and before including on the C-7. Everything during the process was unremarkable so I don't have any tricks to share.

That's my bad, looks like it's a SmartThings driver that I had to adjust. Going to PM you.

Hard reset how? Holding the button in for 10 seconds? I’ve done that already multiple times. Interestingly enough I moved one of my HEMs back to my C4 with the same driver as we are using here and I’m still having the same issue. I’ve replied to Aeotec and waiting on a response.

@shawn.foist how are you feeding the data to Google sheets? This is what I really would like to do so that I can track day over day usage. Thanks in advance for any help you can provide.

Look for the App code from Chuck Schwer

Thanks. I'll check this out.

Hi All,

I'm currently developing a new driver for the Aeotec HEM Gen5 US variant. I've actually made some decent progress, but I've run into a few weird issues.

For reference, my device has firmware 1.35, recently purchased from Amazon.

The issues I'm seeing:

  • My commands are never encapsulated in via CRC16 regardless of the parameter setting on the device
  • I don't get usage reports, with or without the selective reporting enabled. I'm not even getting the message sent to the hub.

Any insight will be appreciated. I'll release the driver code when I get it finished.

I think it has something to do with the way the series 700 or C7 Z-wave works as compared to the C4. The driver works on my C4 but not on my C7. I'm not a dev so I'm just guessing from observations.

I use @csteele AM6 driver, that I see he converted to C7 security. I tagged him in case he has some insight that could help you convert this one (if that is the issue)

I just installed this driver and after a bit of swearing, parameter changes and couple of include/exclude cycles managed to get it working well. I just use it for power tracking and ideally voltage and current. I was finding for a couple of hours of playing with it that it could get the power reading initially but was not continuously updating. Almost gave up and re-included on defunct ST hub.

The settings of note that work for me are:

  • CRC-16 encapsulation: off
  • Selective reporting: off
  • Rpt Group 1: Watts HEM, Watts 1, Watts 2
  • Rpt Group 2: Voltage HEM, Voltage 1, Voltage 2
  • Rpt Group 3: Current HEM, Current 1, Current 2
  • Firmware v1.35

Strangely when I only selected one value in each Rpt Groups (HEM) it didn’t work. Only adding them all worked (I only have one clamp).

Anyway, it’s working now and pretty fast.

1 Like

Do you have a copy of that driver you can share? Not sure if it's public. I can read though it and see what he's doing.

Thanks. I had it very easy with the Aeotec MultiSensor 6 code because it was already funneling all ZWave traffic into a single place. I only had to change ONE method.

I changed this:

private command(hubitat.zwave.Command cmd) {
	if (state.sec) {
	    if (debugOutput) log.debug "Sending secure Z-wave command: ${cmd.toString()}"
	    return zwave.securityV1.securityMessageEncapsulation().encapsulate(cmd).format()
	} else {
	    if (debugOutput) log.debug "Sending Z-wave command: ${cmd.toString()}"
	    return cmd.format()

To This:

private command(hubitat.zwave.Command cmd) {
	    if (debugOutput) log.debug "Sending Z-wave command: ${cmd.toString()}"
	    return zwaveSecureEncap(cmd.format())
1 Like

Thanks for the snippet. I'll try the zwaveSecureEncap() method and see what happens.

What is the latest with this driver? I see one other thread discussing drivers for the Gen 5 HEM (Aeon Home Energy Meter ZW095-A) that seemed to have a promising 22-Apr-2020 post from @codahq with a link to github code but that link is 404-ing for me. Is that still the most functional driver maybe accessible via a different link?

But then there is activity on this thread in the last few weeks that sounds really encouraging. Thanks for the efforts of everyone involved thus far. I do note though that on this thread @viertaxa is working on a driver for the US gen 5 device (obviously, since presumably he is in the USA and that is what he needs and probably also immediately benefits the highest number of other people) but does anyone know how much change that is likely to require to support the single phase UK version of the Gen 5 HEM?

I'm trying to work out what my best path forward is here, try to install one of the various drivers already mentioned in the various threads and have a stab at doing whatever changes are necessary to get it working on my HE C7 or wait a while for a better starting point to get posted presumably on this thread?

Would you mind pming the driver to me as well?

I've released a BETA MVP driver for the Aeotec HEM Gen 5 over here:


A couple things to note:

  • This is BETA software, and is subject to be totally broken. I'm still testing it out myself, but more eyes are always appreciated.
  • This is a MVP. Minimal functionality has been achieved, but I'm not doing anything extra, like calculating dollar costs.
  • This is my first driver released to the public, so I've probably done some things incorrectly.

Please feel free to open an issue on my GitHub for support for the UK version here: https://github.com/viertaxa/hubitat. If you're open to working with me for testing and providing information, I believe we can relatively simply take care of the 1 phase variant.


Fantastic. Thanks. I have just filed an issue (feature request) for the addition of UK support under Github user name mtaun01 where I did also confirm that I'm happy to help with testing. Unless anyone tells me it's pointless I'll actually download the US version you linked to in the next few days anyway since I assume (or at least would hope) that the basics of pairing, polling etc are probably the same across all versions of the device so I might as well check that there are no weird version-differences anomalies regarding the basic "plumbing" even if the data I get back right now isn't valid for the UK device.

Well, that was painless! I installed the latest groovy file from your github repository, excluded and re-included my HEM-Gen5. Hubitat picked up the fingerprint and got the right device type and I see "power" and "energy" as the "Current States" on the Hubitat UI when I click into the device. The power looked plausible and I then toggled on and off a 2kW fan heater and the figure changed by pretty much exactly 2,000 on each on/off test so it seems to be reading the instantaneous power consumption just fine. I'm guessing that probably means that the energy readings are good too but I'll mess around a bit more later. So far this is all without changing any of the default settings.

Now that I have what look like accurate energy readings coming in I need to go down that rabbit hole of working out how I want to log them, display them, use them etc.

Honestly I'm such a technology enthusiast (some might say "victim") that I really didn't give any thought to any of that when I bought the device, I was buying other stuff from a home automation online retailer, needed to add more stuff to my order to get free delivery, saw the HEM listed and though "yeah, That looks cool. I'll get one of those too".

Thanks Taylor for helping me get at least the basics of my totally un-considered purchase up and running and moving me on to the next stage. In retrospect thank goodness this didn't turn out to be a complete waste of money.


Thank you very much for the driver. Iwas looking this monitor against the sense but not sure if there was a driver available. Now I can go easily with this.