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

[inetjnky]

I don't believe this is a driver issue... I may need to reach out to Aeotec directly to see whats going on.

Using the Basic zWave Tool, I've setup and am seeing the following parameters:

Based on this, Parameter 101 = Watts, Parameter 102 = KWH, and Parameter 103 = Amps
Parameters 111, 112, and 113 poll every 120 seconds.

Yet, whether I use this driver from @TechMedX or the built in driver in Hubitat, I'm getting the following for Power and Current:

I'm not sure the KWH calculations are correct either, I'm not using that much or perhaps its the cost amount I put in my settings. Either way, something isn't reporting properly and I am not able to determine why.

[inetjnky]

What do you mean repair non-secure? I'm on the C7.

[kahn-hubitat]

i meant remove and join non-secure

[TechMedX]

@inetjnky

repair non-secure?

When you pair to the C7 the device can pair with no security or S0 (not sure it does S2). You can see some of each here.

That voltage does not look right either. 2 million volts ouch! Hot stuff!

[inetjnky]

Yeah, I have an email in to aeotec.

[shawn.foist]

I just moved mine from a C-5 to my C-7 and it works fine. It is paired non-secure and running a driver that I found a while ago. I am not at home to look at the driver name but if you can't get it going let me know and I can tell you the author and even e-mail it to you if you need.

It is fully functional and the data is fed to a Google sheet for long term tracking that is graphed and fed into SharpTools.

[shawn.foist]

Makes for some good telemetry tiles. The data is incomplete because of the recent move to the C-7.

[halfrican.ak]

I believe the driver will need to be modified to work with S0 with the C7 as I was told by Hubitat Staff that there isn't a way to force it to pair non- secure on the C7, unlike the previous gen hubs.

[TechMedX]

@halfrican.ak you are most likely correct, which is why I said this above...

@TechMedX

Unless HE plans to fully support the device someday the juice just aint worth the squeeze anymore.

As for updating the driver unfortunately I wouldn't know where to begin since I'm not a dev. Without HE or someone else picking up the torch I think this device dies with the C7

[shawn.foist]

Mine is running fine on a C-7 with the driver available at;

https://gist.github.com/DuncanIdahoCT/deb2bafdd28af4fce3073b9d9f4ecafa

[inetjnky]

So yours is broken now on your C7?

[inetjnky]

Thanks Shawn, I’ll check it out. I got an email from support today. They recommended some changes to my parameters so I’m going to try that first.

[inetjnky]

When I try and import this into my C7 I'm getting the following errors:

unable to resolve class physicalgraph.zwave.Zwave @ line 93, column 4. unable to resolve class physicalgraph.zwave.Zwave @ line 97, column 4. unable to resolve class physicalgraph.zwave.commands.securityv1.SecurityMessageEncapsulation @ line 210, column 16. unable to resolve class physicalgraph.zwave.commands.securityv1.SecurityCommandsSupportedReport @ line 222, column 16. unable to resolve class physicalgraph.zwave.commands.configurationv1.ConfigurationReport @ line 226, column 16. unable to resolve class physicalgraph.zwave.commands.associationv2.AssociationReport @ line 230, column 16. unable to resolve class physicalgraph.zwave.commands.meterv3.MeterReport @ line 234, column 16. unable to resolve class physicalgraph.zwave.commands.multichannelv3.MultiChannelCmdEncap @ line 281, column 16. unable to resolve class physicalgraph.zwave.Command @ line 333, column 16. unable to resolve class physicalgraph.zwave.Command @ line 432, column 17.

[inetjnky]

@bobbyD what's the current status of support with the stock driver for the Aeon HEM Gen 5 on the C7? Supported or Not supported?

[TechMedX]

@inetjnky

broken now on your C7?

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

Maker API / Node Red error - Aeon Home Energy Meter (Gen 5)

In the process of moving from C4-C7, and I'm getting the following error on the above device. It worked fine on the C4, but now I get this error whenever I hit 'deploy' and the device does not have any attributes listed. The device does function in HE with @codahq community driver (yes I know Ben does not support HE anymore ) Any thoughts as to how I can get this devices talking to NR again? [image]

@halfrican.ak

I was told by Hubitat Staff that there isn't a way to force it to pair non- secure on the C7

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

[shawn.foist]

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.

[shawn.foist]

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

[inetjnky]

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.

[sdoane57]

@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.

[shawn.foist]

Activity monitor - logs in google sheets

I am about to migrate from Smartthings to Hubitat and I am doing a check if all the features that I currently have in ST can be achieved as well in HE. I have found most of them available but what I am still trying to find is a way to log the activity from my sensors, outlets etc to a google spreadsheet. So the question is if there is a way to log for example the power consumption from a power outlet to google sheets so I can track easily how much my fridge for example is consuming.

Look for the App code from Chuck Schwer