Device driver v1 for aeon smart switch 6 gen5

same here on one of my remote devices sol I cannot debug.

Changed right after the last firmware release… as for the one I have locally it is still working fine, but I updated the firmware on that one to ver 1.03… so it may be a combination of the 2 things. With the little debugging I put back in the app to try and find out what is going on … I don’t see another on even happening in the device type itself , So I assume it is a bug in the smartthings platform, but I will keep looking

here is the logging on my one switch that is showing the same behavior… as you can see after calling off.
nothing is turning it back on… so not sure what is going on

‎3‎:‎30‎:‎07‎ ‎PM: debug got voltage 125.013

ffee9288-8e60-4fa4-b923-d5bf790ddc7b ‎3‎:‎30‎:‎07‎ ‎PM: debug in meter report cmd = ‘MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 1, 232, 85], precision: 3, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 4, scale2: false, scaledMeterValue: 125.013, scaledPreviousMeterValue: 0.000, size: 4)’

ffee9288-8e60-4fa4-b923-d5bf790ddc7b ‎3‎:‎30‎:‎07‎ ‎PM: debug in parse got message string : 'zw device: 06, command: 3202, payload: A1 64 00 01 E8 55 00 00 00 00 00 00 00 00 00 00 ’

ffee9288-8e60-4fa4-b923-d5bf790ddc7b ‎3‎:‎30‎:‎07‎ ‎PM: debug got amperage = 0.000

ffee9288-8e60-4fa4-b923-d5bf790ddc7b ‎3‎:‎30‎:‎07‎ ‎PM: debug in meter report cmd = ‘MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 0, 0, 0], precision: 3, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 5, scale2: false, scaledMeterValue: 0.000, scaledPreviousMeterValue: 0.000, size: 4)’

ffee9288-8e60-4fa4-b923-d5bf790ddc7b ‎3‎:‎30‎:‎07‎ ‎PM: debug in parse got message string : 'zw device: 06, command: 3202, payload: A1 6C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ’

ffee9288-8e60-4fa4-b923-d5bf790ddc7b ‎3‎:‎28‎:‎19‎ ‎PM: debug in meter report cmd = ‘MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 0, 0, 0], precision: 3, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 2, scale2: false, scaledMeterValue: 0.000, scaledPreviousMeterValue: 0.000, size: 4)’

ffee9288-8e60-4fa4-b923-d5bf790ddc7b ‎3‎:‎28‎:‎19‎ ‎PM: debug in parse got message string : 'zw device: 06, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ’

ffee9288-8e60-4fa4-b923-d5bf790ddc7b ‎3‎:‎28‎:‎15‎ ‎PM: debug in meter report cmd = ‘MeterReport(deltaTime: 0, meterType: 1, meterValue: [0, 0, 0, 0], precision: 3, previousMeterValue: [0, 0, 0, 0], rateType: 1, scale: 2, scale2: false, scaledMeterValue: 0.000, scaledPreviousMeterValue: 0.000, size: 4)’

ffee9288-8e60-4fa4-b923-d5bf790ddc7b ‎3‎:‎28‎:‎15‎ ‎PM: debug in parse got message string : 'zw device: 06, command: 3202, payload: 21 74 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ’

ffee9288-8e60-4fa4-b923-d5bf790ddc7b ‎3‎:‎28‎:‎14‎ ‎PM: debug in zwave cmd handler dimmer events

ffee9288-8e60-4fa4-b923-d5bf790ddc7b ‎3‎:‎28‎:‎14‎ ‎PM: debug in parse got message string : 'zw device: 06, command: 2603, payload: 63 ’

ffee9288-8e60-4fa4-b923-d5bf790ddc7b ‎3‎:‎28‎:‎11‎ ‎PM: debug in zwave cmd handler dimmer events

ffee9288-8e60-4fa4-b923-d5bf790ddc7b ‎3‎:‎28‎:‎11‎ ‎PM: debug in parse got message string : 'zw device: 06, command: 2003, payload: 00 ’

ffee9288-8e60-4fa4-b923-d5bf790ddc7b ‎3‎:‎28‎:‎09‎ ‎PM: debug in off

ok new version…

Short of it. something in the last updates was confusing the dimmer level of the led that the switch is reporting with the
dimming level of the device connected to the switch (which it isn’t) so when reporting a level >0 and < 100
it was interpreting this as the switch being on … thus turning back on.

I have changed the code to ignore the dimming levels and only treat 0 as off and 255 as on,
I also removed the dimming bar as It wasn’t working anyway.

Let me know how your results are…

Also I believe the firmware update to 1.03 of the switch fixed this because the one I have at home (not remote) and have access to to flash the update, was not having any issues … only the remote one on the older firmware.

here is the new version

Awesome, great catch, thanks so much for all the hard work. I’ll put this new version in place and let you know if I see any problems.

EDIT: Working great so far, the switches are showing up correctly as ON or OFF respectively. Thanks again!

This is really great. Thanks for your work. I was futzing last night and noticed that the correct state is noted for the first couple changes, and then it’s almost like it exhausts or comes out of sync. If you wait a minute it catches up, but only sometimes. Could the device not be reporting back fast enough? I just wonder if this is a hardware issue either at the hub or the device, or whether there is a software tweak. I’ll try your newest version and see.

I am a little confused. I have the Aeon Smart Switch 6 (Gen 5) that doesn’t have dimming capability. When this thread was started the device code was really for this device because the dimming switch wasn’t released yet. But I suspect the code is now for the actual dimmer switch. Is that correct ?
If so I may start a new thread regarding the other smart switch without dimming pointing to my version of the code for that device.

no not sure what you mean the switch is supposed to have dimming. and allow dimming of the color led ring not a device connected to it… The code has the dimming support disabled as smartthings or version 1.0 of the firmware was interpreting the dimming and being dimming of the connected device which it is not.

OK that is the device I own. There are two switches one does dim the power connected. That is why the title of this thread is confusing.

Here are the two versions.

Switch with dimming nightlight

Switch with dimming ability
http://aeotec.com/z-wave-plug-in-dimmer

got ya same device as mine… something that Samsung did int he last update broke it and it was sending a dimming of 99 and was being interpreted as the connected device dimming and turning the switch back on… My versions of the switch with firmware 1.03 were not affected only the older… I removed/changed the dimming code to compensate for this.

I changed THE TITLE

doesn’t help that they both look the same!! Now I wonder what I have!!

not sure what you mean they don’t look the same at all… one is double wide euro only the other is single width.

Not that it matters, but they are identical. The picture here is from the dimmer link, and looks just like the switch. The other pictures on the dimmer page are of the plug while plugged in. It’s square

I don’t think the dimming version has been released yet. There’s a note at the bottom of the product page:

Smart Dimmer 6 is coming in 2015.
To find out when it’s released, subscribe to Aeotec’s newsletter by entering your information below.

But that’s it. It looks like it just received Z-Wave Certification at the end of September, so I would guess that means that retail availability should be starting at some point in the near future.

Larry,

The performance of the switch a great deal. Thanks so very much. I have a dumbass question, though… what is the “energy” versus “momentary” setting in the app?

Energy displays color based on energy level.
Monetary does the same but only for a few seconds after you switch on/off, then it goes dark.

1 Like

HEY cool! Thanks so much

@larry, how can I tell the firmware revision on the gen5 aeon switch. I do not see it listed in the smartthings dashboard device list.

How do I update the firwmware on them?

Thanks

@Lgkahn what is the configure button supposed to do? is there a way to turn off the LED all together with the switch on?

Great work BTW, This is really great stuff!

I have the version reporting in my device driver when I “refresh”
The code is
zwave.versionV1.versionGet().format(),
and of course you need to process the message
def zwaveEvent(physicalgraph.zwave.commands.versionv1.VersionReport cmd) {
log.debug “cmd:$cmd”
}

Full code here

A few options

  1. Set to moment (or momentary) which only displays the color for a few seconds when the switch is turned on/off.
  2. Set nightlight mode and set dim level to dark or select dark color. But this is always off not just for when the switch is on.

Unfortunately they don’t have a mode for “Light when off”, “Dark when On” which would be nice.

You could simulate this by altering your device code. Use nightlight mode, then send the dim setting for on = 0, off = 100. Wouldn’t be difficult but I would bet it might not work 100% of the time.

@Ron thanks for the feedback!

Has anyone been able to get the secure mode working? I’m unable to do any mesh repair and i’m not sure if this is the reason. Maybe my fault for expecting these would instantly work in a mesh and get the signal more than 10 meters away :confused: