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

Mike (@mike.maxwell),

Trying to move over some of my last few devices from ST to Hubitat. I am still running a version of your 'Aeon HEM V1 Laundry Driver' to monitor my washer and dryer. This Driver sends button 'pushed' events that I use to then send text messages to my our cell phones. It has been working great for a very long time, so I 'd like to replicate the functionality on Hubitat.

I am not very well versed in Z-Wave Drivers, so I would very much appreciate your assistance.

I have made the obligatory physicalgraph to hubitat changes, as well as tweaking the events for the button pushed messages to comply with Hubitat's methodolgy. But, I am still getting an error in my logs, and the individual power readings from each probe are not being populated. The error I see is the following, repeating every time the Aeon SMart Energy Meter sends data:

[dev:556](http://192.168.1.144/logs#dev556)2018-02-24 00:01:17.571:errorNo signature of method: hubitat.zwave.commands.multichannelv3.MultiChannelCmdEncap.encapsulatedCommand() is applicable for argument types: (java.util.LinkedHashMap) values: [[48:1, 49:1]] on line 50

[dev:556](http://192.168.1.144/logs#dev556)2018-02-24 00:01:17.471:errorNo signature of method: hubitat.zwave.commands.multichannelv3.MultiChannelCmdEncap.encapsulatedCommand() is applicable for argument types: (java.util.LinkedHashMap) values: [[48:1, 49:1]] on line 50

[dev:556](http://192.168.1.144/logs#dev556)2018-02-24 00:01:17.427:errorNo signature of method: hubitat.zwave.commands.multichannelv3.MultiChannelCmdEncap.encapsulatedCommand() is applicable for argument types: (java.util.LinkedHashMap) values: [[48:1, 49:1]] on line 50 

UPDATE: Here is the current working code. You need to be on 1.0.2.702 or newer firmware for this driver to work. For those not familiar with this driver, it allows you to select a wattage threshold for your washer and dryer independently (one per Aeon HEM V1 clamp.) When the value drops the threshold, it sends a Button Pushed Event (i.e. 'pushed 1' for the washer and 'pushed 2' for the dryer.) You can then use a Hubitat 'Button Controller' to subscribe to these events and send SMS messages, turn on lights, etc...

Thanks,
Dan

2 Likes

@ogiewon Thanks for bringing this up as I try the same and had no luck. I second this request.

1 Like

@mike.maxwell. Any thoughts on how to fix this Driver?

its on my list for tomorrow, along with a few other things…

1 Like

Thanks!

So we’re missing a few back end bits, notably the encapsulatedCommand method that goes along with MultiChannelCmdEncap
In any event I’ve added that function and got this driver working, bad news obviously is that it won’t be available until the next platform update.

1 Like

@mike.maxwell that ok. Thanks for the update.

@mike.maxwell did this get updated also?

1 Like

Yes, it should work now, though I’ve not tested it in my production environment.

I just tried my Aeon v1 power meter with the 701 firmware. I am still getting the same error as shown below

[dev:612](http://192.168.1.144/logs#dev612)2018-03-03 06:29:36.049:error No signature of method: hubitat.zwave.commands.multichannelv3.MultiChannelCmdEncap.encapsulatedCommand() is applicable for argument types: (java.util.LinkedHashMap) values: [[48:1, 49:1]] on line 51

[dev:612](http://192.168.1.144/logs#dev612)2018-03-03 06:29:36.028:info mc3v cmd: MultiChannelCmdEncap(bitAddress:false, command:2, commandClass:50, destinationEndPoint:0, parameter:[33, 100, 0, 0, 0, 1, 0, 30, 0, 0, 0, 0], res01:false, sourceEndPoint:2)

[dev:612](http://192.168.1.144/logs#dev612)2018-03-03 06:29:36.026:trace Parse received zw device: 10, command: 600D, payload: 02 00 32 02 21 64 00 00 00 01 00 1E 00 00 00 00

@ogiewon did you get this working?

Not yet. Going to need @mike.maxwell’s assistance to get this one working, I believe.

	def encapsulatedCommand = cmd.encapsulatedCommand([0x30: 1, 0x31: 1])

This line (the one before 51) seems to be missing a designation for the command between the first ( and [.

An example from another spot is
def cmd = zwave.parse(description, [0x31: 1, 0x32: 1, 0x60: 3])

@mike.maxwell @leeonestop

I have successfully tested this Driver (in the original post) with the latest 1.0.2.702 firmware!

Thanks Mike for getting this sorted out! This is my last Z-Wave device on ST. I used a spare Aeon HEM V1 to test with. So I should be able to simply swap out the electronics later this week and set up a SMS alert based on the button pushed events.

1 Like

@ogiewon what device driver are you using for the Aeon HEM V1?

I have just added my slightly modified version to my GitHub Repository. I have this working and sending SMS text messages to my phone. To get the SMS messaging working, I added a new “Button Controller” App and configured it to monitor this device for Button 1 Pushed - Send “Washer is Done!” SMS message, and Button 2 Pushed - Send “Dryeris Done!” SMS message.

Be aware that Hubitat only supports a maximum of 10 SMS text messages per day. Their upcoming Phone App will support Push Notifications that will not have this restriction.

@ogiewon Thanks for the info and device code. I have installed your device handler as I was using it in Smartthings. The only problem that I had was my washer/dryer power fluctuated through the cycle and I got notified a lot.

I just updated the version of this driver in my GitHub repository. I noticed it was not always detecting my dryer as being ‘on’ when the wattage was above the threshold. I added some ‘.toInteger()’ statements to make sure the comparison was all being done with numerical values. Afterwards, it seems to be working fine.

@ogiewon I have the same problem . Thanks I updated your code.

1 Like

@ogiewon have you got this working with rule machine? I still not up and running? Apparently I have miss something.