Metering Switch Status Report Speed not instant? (Aeon Labs Smart Energy Switch)

Just bought a “Aeon Labs Smart Energy Switch” to play with and it appears that the Status Report is not instant, and I was wondering if this was adjustable or if any other Metering Switches give an instant status update.

To test, i plugged in a lamp and it reads 100W, i turn off the lamp and it’ll take about 1 minute before it reports 0W to the App. Which to me looks like the normal polling cycle. I would of thought that the metering switch would of sent an update on power change When it happened. So I can trigger events right when it happens, not some time later…

2 Likes

@ChadCK,

You can either use ST’s default device type (tap the Configure tile to make sure reporting is set up right), or you can try using my device type that tweaked settings to report every 15 seconds. You can tweak the settings to only report after a threshold of change is met. Comments in the Configure section will help you understand what to change.

https://github.com/constjs/SmartThings-Devices/blob/master/aeon_smart_switch_v2.device.groovy

Here’s what you’d change in that code to enable selective reporting when watts change by 2 or 1% :

zwave.configurationV1.configurationSet(parameterNumber: 3, size: 1, scaledConfigurationValue: 1).format(),      // Disable selective reporting, so always update based on schedule below <set to 1 to reduce network traffic>
zwave.configurationV1.configurationSet(parameterNumber: 4, size: 2, scaledConfigurationValue: 2).format(),     // (DISABLED by first option) Don't send unless watts have changed by 50 <default>
zwave.configurationV1.configurationSet(parameterNumber: 8, size: 1, scaledConfigurationValue: 1).format(),     // (DISABLED by first option) Or by 10% <default>
1 Like

That looks awesome, why doesn’t smartthings work on making their device handlers better. I know the community driven DH’s are awesome but because they are custom device handlers we aren’t allowed to run local? Why, hoping that SmartThings atleast changes that, we should be able to run the code locally or start dedicating on making the device handlers robust and amazing :wink:

So I looked at the code, so of the first 3, to enable the 2nd or 3rd options does the first need to be 1 or 0, i know it says disabled by the first option, so wasn’t sure what that first one needed to be so 2nd/3rd is not disabled.

I’m assuming the 2nd option, change by 50 is an actual change of 50 watts not a percentage. With the percent being in the 3rd option, can that but changed to be higher then just 10%, like like a change of 50%, what would it be for that.

i’m also assumign 4-5 and 6-7 are linked options? saying combined energy in watts Every 15 Seconds? is that what it is stating? What are the defaults for those, and what else do they affect.

8-9, what are these doing?

 1 // Disable selective reporting, so always update based on schedule below <set to 1 to reduce network traffic>
 2 // (DISABLED by first option) Don't send unless watts have changed by 50 <default>
 3 // (DISABLED by first option) Or by 10% <default>
 4 // Combined energy in Watts
 5 // Every 15 Seconds (for Watts)
 6 // Combined energy in kWh
 7 //  every 60 seconds (for kWh)
 8 // Disable report 3
 9 // Disable report 3

Thanks Again, this is looking better, i’ll try playing with it later today or tomorrow :smile: