'Aeon HEM V1 Laundry Driver' is NOW working on Hubitat

ogiewon · November 12, 2019, 2:29pm

Sorry, I have no clue about the Z-Wave commands. Those are all original from Mike Maxwell's SmartThings DTH, which I simply ported to Hubitat.

Is there any chance that the errors started recently as a result of a firmware update? My main hub, that runs the Aeon HEM v1, is still running 2.1.5 due to some changes in how the Hampton Bay Fan Controller was changed in 2.1.6. I am waiting for an upcoming fix before upgrading.

SmartHomePrimer · November 12, 2019, 2:32pm

I'll inquire with @mike.maxwell. Thanks.

No, my main hub is still running 2.1.3.125 !

GatVlieg · January 24, 2020, 2:59pm

Is anybody else getting this error message?

groovy.lang.MissingPropertyException: No such property: scale for class: hubitat.zwave.commands.meterv5.MeterSupportedGet on line 63 (parse)

I am using what I believe is the latest version (no versioning info in the driver code) Driver header as follows:

Subject to correction, this only started (or well, to be more precise, I only noticed it for the first time) after upgrading to the most current HE version.

Thanks in advance

Edit: Based on the error timestamp, I can assure everybody that nobody was doing laundry! And yet it just happened. This is the most recent occurrence; has happened a few times since doing the upgrade

SmartHomePrimer · January 24, 2020, 3:04pm

Do you have the v1 HEM? The driver isn’t for the latest HEM devices.

GatVlieg · January 24, 2020, 3:06pm

Yes, v1 HEM. It has been working fine since ST days, then with the modded driver in HE for a very long time.

SmartHomePrimer · January 24, 2020, 3:10pm

Might be the device. I have had to exclude and rejoin both of mine every so often. Less since adding a repeater.

You might first try just disabling the Z-Wave radio in HE for a minute, then re-enable it. That fixed an unresponsive Z-Wave device for me once before.

GatVlieg · January 24, 2020, 3:14pm

My Z-Wave network is rock solid. From day 1 it has lived in 1 location only. It was intially joined to ST, excluded, & then joined to HE. Absolutely no mesh issues.

While I cannot disregard your comment outright (weird things have happened!), the actual error doesn't support this argument.

I post the following from the code in case it may benefit anybody in trying to diagnose this issue:

SmartHomePrimer · January 24, 2020, 3:18pm

In my earlier post in this thread, I had a weird issue out of blue too. I don’t recall the fix though. It wasn’t software related. I think I ended up just excluding and re-joining the device. But I would try just turning the Z-Wave radio off for at least 10 seconds and turn it back on. It’s easy and won’t cause any issues, but might fix them.

GatVlieg · January 24, 2020, 3:27pm

Sure, it is easy enough to do, and will do so in due course. The problem is also of such a nature that it may take days to manifest itself...

Just as an aside, no bearing on the current issue itself:
I am also currently forced (via a RM rule) to reboot my hub at 4AM daily now. I am regrettably one of the many suffering in silence with this issue. I was so happy at one point when I thought that I am being spared this issue, but alas, this was not to be; my issue started after I applied the second to last update. I will call my setup "mature", in that I have not added any new devices in over a year, and only tweak RM rules occasionally, so my issue is NOT a "you keep messing with it" issue. One may ask why I keep updating the firmware if all works... Simple - most folks (including HE staff) will not assist unless you are the latest firmware. I know, I tried.

SmartHomePrimer · January 24, 2020, 3:29pm

Why not roll back if you suspect the platform is to blame?

SmartHomePrimer · January 24, 2020, 3:38pm

Not a true statement. I am still running 2.1.3.125 on my main hub. I have update in the course of troubleshooting to see if it resolved the issue, and rolled back when it didn’t, but have never been denied support due to my platform version.

GatVlieg · January 24, 2020, 4:52pm

Respectfully we will have to disagree on the latest version & getting support from HE. My experience was exactly the opposite of yours, where I was 2 revisions behind, started experiencing an issue & was explicitly told to bring it up to the latest revision; if my memory serves me correct I was told the error line numbers (as displayed in my log) no longer match with the latest code.

SmartHomePrimer · January 24, 2020, 5:14pm

So not to be disrespectful either, truly, but then why didn’t you just comply with their request and see if it solved the issue? If it didn’t, you could then tell them it didn’t and roll back to the version you feel comfortable with. That’s the whole reason they don’t force automatic platform updates on you like SmartThings does, and why they built the system to allow you to roll back.

What you’re describing sounds more like they offered support and identified an issue that they believed a platform update would resolve. Not that they refused to offer you any support until you updated, which is how your earlier post reads.

ogiewon · January 24, 2020, 7:32pm

I believe the latest firmware version (2.1.8) brought with it some changes to how Z-Wave devices are handled. I wonder if any of these changes could have broken this Driver? I am tagging @mike.maxwell to see if he has any ideas.

Mike - the driver in question is one of your old ones from ST, that you assisted me in porting to Hubitat back in the early days.

Here is the current code from my GitHub repository. Please advise any changes that may be required due to the Z-Wave changes in 2.1.8. Thanks!

github.com

ogiewon/Hubitat/blob/master/Drivers/aeon-hem-v1-laundry.src/aeon-hem-v1-laundry.groovy

/*
Custom Laundry monitor device for Aeon HEM V1 

  https://raw.githubusercontent.com/ogiewon/Hubitat/master/Drivers/aeon-hem-v1-laundry.src/aeon-hem-v1-laundry.groovy
  
  originally written by Mike Maxwell for SmartThings
  
  modified by Dan Ogorchock to work with Hubitat

  2018-05-26  Dan Ogorchock  Added optional delay parameter to add debounce feature to prevent multiple events
  2019-03-15  Dan Ogorchock  Tweaked for v2.0.7 compatibility
  2019-07-14  Matt Baran     Added separate debounces for Washer/Dryer
  2020-01-24  Dan Ogorchock  Attempt to prevent errors in logs

*/

metadata {
	definition (name: "Aeon HEM V1 Laundry DTH", namespace:	"MikeMaxwell", author: "Mike Maxwell", importUrl: "https://raw.githubusercontent.com/ogiewon/Hubitat/master/Drivers/aeon-hem-v1-laundry.src/aeon-hem-v1-laundry.groovy") 
	{
        capability "Configuration"

This file has been truncated. show original

mike.maxwell · January 24, 2020, 9:19pm

This isn't related to the command class changes, try changing this:

if (cmd.commandClass == 50)

to this:

if (cmd.commandClass == 50 && cmd.command == 2)

ogiewon · January 24, 2020, 9:56pm

@GatVlieg - I have made Mike's recommended change to the code in my GitHub repository. Please give it a try and let us know if it resolves the issue you've been seeing.

Thanks @mike.maxwell!

GatVlieg · January 25, 2020, 12:37am

Thanks @ogiewon & Mike

I WILL IMPLEMENT THE CHANGES NEXT - AGAIN - HAVE NOT DONE SO.

Just out of interest, my wife did laundry today and it threw these additional errors:
(again, I have NOT implemented the recommended changes yet)

Now to implement the recommended change...

danabw · July 31, 2020, 9:26pm

@GatVlieg - did you ever get this working again?

I'm still using Mike's driver in ST and was planning on using it when my C7 arrives.

danabw · August 6, 2020, 1:13am

@ogiewon - not sure what I'm misunderstanding (usually a lot) but I've added your driver, added my Aeon HEM V1 (that I had been using w/the same driver on SmartThings for years), but I can't figure out how to use this w/WebCore in Hubitat.

I have some laundry pistons that I've imported into into WebCore on Hubitat from SmartTHings WebCore, but when I choose the Aeon HEM as the device, I don't have the option for button 1/button 1 push or held as I did in SmartThings.

There is a "pushed button" option for the Aeon HEM, but no "Held button." And I'm not clear on how I would use the Pushed Button option.

Is this driver just not compatible w/WebCore in Hubitat, and I need to use Rule Machine instead? I do see the Aeon HEM V1 as a button device, for example, in the Simple Automation Rules app, so the driver button options appear to be there, but WebCore doesn't see them...

ogiewon · August 6, 2020, 1:21am

I don’t use webCoRE, so I am not sure whether or not it was properly updated to handle Hubitat’s tweaks to how Button devices work.

For now, try using one of the built-in Hubitat Apps, like Notifications or Rule Machine as a test to get things working. If things work as expected, then you could ask the folks that have been supporting webCoRE on Hubitat how to make it work there as well.