hmm i never paid attention to it. You're right... the configuration doesn't seem to work properly.
I have an RM rule that refresh's the jscgs350 drivers, it's much better but still not 100%. Runs every 15 seconds. It seems to be working with your newer version, but it's like my HE hub simply ignores the HEM automated responses. Turns out I have 8 of them on HE right now, my graphs have been bad for a while now. 
This is one of only two things ST seems to do better than HE.
An example of buggy refresh's:
dev:5542018-09-22 10:03:58.839:debugrefresh cmds [320100, delay 100, 320110]
dev:5542018-09-22 10:03:58.838:debugRefreshed Energy Meter
dev:5542018-09-22 10:03:47.415:debug[powerLow:1412, powerValue:1427, powerHigh:1586, energyValue:0.377]
dev:5542018-09-22 10:03:43.696:debugrefresh cmds [320100, delay 100, 320110]
dev:5542018-09-22 10:03:43.694:debugRefreshed Energy Meter
dev:5542018-09-22 10:03:28.401:debugrefresh cmds [320100, delay 100, 320110]
dev:5542018-09-22 10:03:28.400:debugRefreshed Energy Meter
dev:5542018-09-22 10:03:13.198:debugrefresh cmds [320100, delay 100, 320110]
dev:5542018-09-22 10:03:13.194:debugRefreshed Energy Meter
dev:5542018-09-22 10:02:57.988:debugrefresh cmds [320100, delay 100, 320110]
dev:5542018-09-22 10:02:57.987:debugRefreshed Energy Meter
dev:5542018-09-22 10:02:42.736:debugrefresh cmds [320100, delay 100, 320110]
dev:5542018-09-22 10:02:42.735:debugRefreshed Energy Meter
dev:5542018-09-22 10:02:27.573:debugrefresh cmds [320100, delay 100, 320110]
dev:5542018-09-22 10:02:27.571:debugRefreshed Energy Meter
dev:5542018-09-22 10:02:18.296:debug[powerLow:1412, powerValue:1443, powerHigh:1586, energyValue:0.352]
dev:5542018-09-22 10:02:12.429:debugrefresh cmds [320100, delay 100, 320110]
dev:5542018-09-22 10:02:12.428:debugRefreshed Energy Meter
dev:5542018-09-22 10:01:57.282:debugrefresh cmds [320100, delay 100, 320110]
dev:5542018-09-22 10:01:57.280:debugRefreshed Energy Meter
dev:5542018-09-22 10:01:44.429:debug[powerLow:1412, powerValue:1443, powerHigh:1586, energyValue:0.352]
dev:5542018-09-22 10:01:43.868:debugrefresh cmds [320100, delay 100, 320110]
dev:5542018-09-22 10:01:43.867:debugRefreshed Energy Meter
dev:5542018-09-22 10:01:29.211:debug[powerLow:1412, powerValue:1443, powerHigh:1586, energyValue:0.329]
dev:5542018-09-22 10:01:28.715:debugrefresh cmds [320100, delay 100, 320110]
dev:5542018-09-22 10:01:28.714:debugRefreshed Energy Meter
Even Iris Outlets suck at this:
dev:7782018-09-22 10:03:44.902:infoBedroom North Outlet power is 19.8 watts
dev:7782018-09-22 10:01:57.399:infoBedroom North Outlet power is 21.8 watts
dev:7782018-09-22 10:01:56.177:infoBedroom North Outlet power is 20.6 watts
dev:7782018-09-22 09:47:50.826:infoBedroom North Outlet power is 19.6 watts
dev:7782018-09-22 09:45:56.004:infoBedroom North Outlet power is 20.9 watts
Just found and modified this version. I can get it to report 15 seconds interval now. probably go smaller but might flood the mesh.
/**
* Aeon HEM1
*
* Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
* in compliance with the License. You may obtain a copy of the License at:
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
* on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
* for the specific language governing permissions and limitations under the License.
*
* Aeon Home Energy Meter gen-1 (US)
*
* Updates:
* -------
* 02-15-2016 : Removed posting to the Activity Feed in the phone app and event log.
* 02-17-2016 : Fixed preferences for kWh cost from string to number.
* 02-20-2016 : Enabled battery reporting (parameter 103, value 1), and documented the parameters better.
* 02-21-2016 : Made certain configuration parameters changeable via device preferences instead of having to tweak code all the time.
* 02-22-2016 : Fixed kWh cost entry in Preferences not allowing decimals.
* 02-27-2016 : Changed date formats to be MM-dd-yyyy h:mm a.
* 02-29-2016 : Changed reportType variable from 0 to 1.
* 03-11-2016 : Due to ST's v2.1.0 app totally hosing up SECONDARY_CONTROL, implemented a workaround to display that info in a separate tile.
* 03-19-2016 : Added clarity for preferences.
* 03-21-2016 : Fixed issue when resetting energy would also reset watts.
* 03-25-2016 : Removed the \n from the two tiles for resetting watts and energy due to rendering issues on iOS
* 07-07-2016 : Check for wildly large watts value coming from the HEM and do not process them. Firmware updates should have resolved this.
* 08-10-2016 : Check for 0 or negative watts value coming from the HEM and do not process them. Firmware updates should have resolved this.
* 08-21-2016 : Created separate tiles to reset min and max instead of having a single tile for both values. Changed many tiles to different sizes.
* 08-27-2016 : Modified the device handler for my liking, primarly for looks and feel.
* 09-16-2016 : During the check for 0 or negative values, use the last power value (state.powerValue) instead of just a hard coded value.
* 10-17-2016 : Cleaned up code.
* 10-19-2016 : Provided comments in the code for iOS users to edit so that the rendering of text for certain tiles to work right. Changed default icon.
* 10-19-2016 : Added a new parameter in Preferences so that a user can specify the high limit for a watts value instead of hard coding a value. Related to the change on 7-7-2016.
* 11-22-2016 : Added resetMeter section that calls the other resets (min, max, energy/cost). This is for a SmartApp that resets the meter automatically at the 1st day of month.
* 01-08-2017 : Added parameter 12 and set it to 1. Accumulates kWh energy when Battery Powered.
* 01-08-2017 : Cleaned up code in the resetMeter section.
* 01-08-2017 : Added code for Health Check capabilities/functions, and cleaned up code in the resetMeter section.
* 01-18-2017 : Removed code no longer needed, and added another parameter in Preference to enable or disable the display of values in the Recently tab and device's event log (not Live Logs). Enabling may be required for some SmartApps.
* 01-20-2017 : Removed the check for 0w, but still don't allow negative values. Also removed all rounding, which now displays 3 positions right of the decimal.
* 02-11-2017 : Removed commands no longer needed. Documented what each attribute is used for. Put battery info into the main tile instead of a separate tile.
* 02-12-2017 : Combined the battery and no-battery version into a single DTH, cleaned up code, and general improvements.
* 02-13-2017 : Cleaned up code for battery message being displayed. If someone decides to display battery % while not having batteries installed Health Check will catch that and push low battery notifications until the user disables the display.
* 03-11-2017 : Changed from valueTile to standardTile for a few tiles since ST's mobile app v2.3.x changed something between the two.
* 03-26-2017 : Added a new device Preference that allows for selecting how many decimal positions should be used to display for WATTS and kWh. What's stored for the actual meter reading that's seen in the IDE for Power, and what's sent to SmartApps, has not changed.
* 03-29-2017 : Made changes to account for ST v2.3.1 bugs with text rendering.
* 04-28-2017 : Cleaned up code, and some formatting/tile layout changes for my liking.
* 05-18-2017 : Changed valueTile to standardTile to resolve font/rendering issues.
* 05-28-2017 : Sometimes the HEM will send a super low reading, like 0.04672386; which in that case the decimal position setting would not get applied if you used 3. That's been fixed.
* 05-30-2017 : Thanks to @barkis for the following changes: fixed number of decimal points display on iPhone app; fixed problem with kVAh units display; changed refresh() to immediately update values; reworked decimal place selection to remove 'else' branch that never executes; removed some un-needed temporary variables; code cleanup (trailing whitespace/converted leading spaces to tabs to shrink file size)
* 06-05-2017 : Some tweaks for the 2.4.0 release of the mobile app.
* 06-12-2017 : Updated code to make sure kWh or kVAh readings from the reader are larger that the previous reading. There should never be a smaller reading from the previous reading.
* 06-14-2017 : Updated to fix battery reports showing up in the Recently tab when they shouldn't.
* 06-19-2017 : Cleaned up code in the resetkwh() section.
* 06-29-2017 : Rolled back change from 6-12-2017 until I find a better method of checking.
* 09-27-2017 : Changed tile format for device min/max history to look like my Aeon and Zooz DTH's.
* 09-28-2017 : Changed history tile from "standard" to "value", and reduced the number of dashes so it works better for iOS.
* 10-04-2017 : Fixed reset issues with energy/kWh not resetting properly. (more of a workaround for now)
* 10-07-2017 : Fixed code for battery reports still going to the Recently tab in the mobile app even though the option not to send messages was enabled.
* 10-26-2017 : Added 2 new attributes to capture kWh and cost data before they're reset in case someone needs to refer back to them for any reason. These can be seen in the IDE and in the Recently Tab in the mobile app.
*
*/
metadata {
definition (name: "My Aeon Home Energy Monitor Gen1", namespace: "jscgs350", author: "SmartThings", ocfDeviceType: "oic.d.switch", mnmn: "SmartThings", vid:"generic-switch-power-energy")
{
capability "Energy Meter"
capability "Power Meter"
capability "Configuration"
capability "Sensor"
capability "Refresh"
capability "Polling"
capability "Battery"
capability "Health Check"
attribute "currentKWH", "string" // Used to show current kWh since last reset
attribute "currentWATTS", "string" // Used to show current watts being used on the main tile
attribute "minWATTS", "string" // Used to store/display minimum watts used since last reset
attribute "maxWATTS", "string" // Used to store/display maximum watts used since last reset
attribute "resetMessage", "string" // Used for messages of what was reset (min, max, energy, or all values)
attribute "kwhCosts", "string" // Used to show energy costs since last reset
attribute "batteryStatus", "string"
attribute "kWhLastReset", "number"
attribute "CostLastReset", "number"
command "resetkwh"
command "resetmin"
command "resetmax"
command "resetMeter"
fingerprint deviceId: "0x2101", inClusters: " 0x70,0x31,0x72,0x86,0x32,0x80,0x85,0x60"
}
preferences {
input "displayEvents", "boolean", title: "Display all power and energy events in the Recently tab and the device's event log?", defaultValue: false, required: false, displayDuringSetup: true
input "displayBatteryLevel", "boolean", title: "Display battery level on main tile and Recently tab?", defaultValue: true, required: false, displayDuringSetup: true
input "kWhCost", "string", title: "Enter your cost per kWh (or just use the default, or use 0 to not calculate):", defaultValue: 0.16, required: false, displayDuringSetup: true
input "wattsLimit", "number", title: "Sometimes the HEM will send a wildly large watts value. What limit should be in place so that it's not processed? (in watts)", defaultValue: 20000, required: false, displayDuringSetup: true
input "reportType", "number", title: "ReportType: Send watt/kWh data on a time interval (0), or on a change in wattage (1)? Enter a 0 or 1:", defaultValue: 1, range: "0..1", required: false, displayDuringSetup: true
input "wattsChanged", "number", title: "For ReportType = 1, Don't send unless watts have changed by this many watts: (range 0 - 32,000W)", defaultValue: 50, range: "0..32000", required: false, displayDuringSetup: true
input "wattsPercent", "number", title: "For ReportType = 1, Don't send unless watts have changed by this percent: (range 0 - 99%)", defaultValue: 10, range: "0..99", required: false, displayDuringSetup: true
input "secondsWatts", "number", title: "For ReportType = 0, Send Watts data every how many seconds? (range 0 - 65,000 seconds)", defaultValue: 15, range: "0..65000", required: false, displayDuringSetup: true
input "secondsKwh", "number", title: "For ReportType = 0, Send kWh data every how many seconds? (range 0 - 65,000 seconds)", defaultValue: 60, range: "0..65000", required: false, displayDuringSetup: true
input "secondsBattery", "number", title: "If the HEM has batteries installed, send battery data every how many seconds? (range 0 - 65,000 seconds)", defaultValue: 900, range: "0..65000", required: false, displayDuringSetup: true
input "decimalPositions", "number", title: "How many decimal positions do you want watts AND kWh to display? (range 0 - 3)", defaultValue: 3, range: "0..3", required: false, displayDuringSetup: true
}
}
def updated() {
// Device-Watch simply pings if no device events received for 32min(checkInterval)
sendEvent(name: "checkInterval", value: 2 * 15 * 60 + 2 * 60, displayed: false, data: [protocol: "zwave", hubHardwareId: device.hub.hardwareID])
state.displayDisabled = ("true" == displayEvents)
state.displayBattery = ("true" == displayBatteryLevel)
log.debug "updated (kWhCost: ${kWhCost}, wattsLimit: ${wattsLimit}, reportType: ${reportType}, wattsChanged: ${wattsChanged}, wattsPercent: ${wattsPercent}, secondsWatts: ${secondsWatts}, secondsKwh: ${secondsKwh}, secondsBattery: ${secondsBattery}, decimalPositions: ${decimalPositions})"
response(configure())
}
def parse(String description) {
// log.debug "Parse received ${description}"
def result = null
def cmd = zwave.parse(description, [0x31: 1, 0x32: 1, 0x60: 3, 0x80: 1])
// log.debug "Parse returned ${cmd}"
if (cmd) {
result = createEvent(zwaveEvent(cmd))
}
if (result) log.debug "Result returned ${result}"
if (state.displayBattery) {
def batteryStatusmsg = "USB power, batteries at ${device.currentState('battery')?.value}%"
sendEvent(name: "batteryStatus", value: batteryStatusmsg, displayed: false)
} else {
def batteryStatusmsg = "USB power"
sendEvent(name: "batteryStatus", value: batteryStatusmsg, displayed: false)
}
return result
}
def zwaveEvent(hubitat.zwave.commands.meterv1.MeterReport cmd) {
def dispValue
def newValue
def timeString = new Date().format("MM-dd-yy h:mm a", location.timeZone)
if (cmd.meterType == 33) {
if (cmd.scale == 0) {
newValue = cmd.scaledMeterValue
log.debug "newValue is ${newValue} and prevValue is ${state.energyValue}"
if (newValue != state.energyValue) {
if (decimalPositions == 2) {
dispValue = String.format("%3.2f",newValue)
} else if (decimalPositions == 1) {
dispValue = String.format("%3.1f",newValue)
} else if (decimalPositions == 0) {
dispValue = Math.round(cmd.scaledMeterValue)
} else {
dispValue = String.format("%3.3f",newValue) // default
}
dispValue += " kWh"
sendEvent(name: "currentKWH", value: dispValue as String, unit: "", displayed: false)
state.energyValue = newValue
BigDecimal costDecimal = newValue * (kWhCost as BigDecimal)
def costDisplay = "\$"
costDisplay += String.format("%3.2f",costDecimal)
sendEvent(name: "kwhCosts", value: costDisplay as String, unit: "", displayed: false)
if (state.displayDisabled) {
[name: "energy", value: newValue, unit: "kWh", displayed: true]
} else {
[name: "energy", value: newValue, unit: "kWh", displayed: false]
}
}
} else if (cmd.scale == 1) {
newValue = cmd.scaledMeterValue
if (newValue != state.energyValue) {
dispValue = newValue + " kVAh"
sendEvent(name: "currentKWH", value: dispValue as String, unit: "", displayed: false)
state.energyValue = newValue
if (state.displayDisabled) {
[name: "energy", value: newValue, unit: "kVAh", displayed: true]
} else {
[name: "energy", value: newValue, unit: "kVAh", displayed: false]
}
}
}
else if (cmd.scale==2) {
newValue = cmd.scaledMeterValue // Remove all rounding
if (newValue < 0) {newValue = state.powerValue} // Don't want to see negative numbers as a valid minimum value (something isn't right with the meter) so use the last known good meter reading
if (newValue < wattsLimit) { // don't handle any wildly large readings due to firmware issues
if (newValue != state.powerValue) { // Only process a meter reading if it isn't the same as the last one
if (decimalPositions == 2) {
dispValue = String.format("%3.2f",newValue)
} else if (decimalPositions == 1) {
dispValue = String.format("%3.1f",newValue)
} else if (decimalPositions == 0) {
dispValue = Math.round(cmd.scaledMeterValue)
} else {
dispValue = String.format("%3.3f",newValue) // default
}
if (newValue < state.powerLow) {
def dispLowValue = dispValue+"w on "+timeString
sendEvent(name: "minWATTS", value: dispLowValue as String, unit: "", displayed: false)
state.powerLow = newValue
def historyDisp = ""
historyDisp = "Minimum/Maximum Readings as of ${timeString}\n------------------------------------------------------\nPower Low : ${device.currentState('minWATTS')?.value}\nPower High : ${device.currentState('maxWATTS')?.value}\nMessages : ${device.currentState('resetMessage')?.value}"
sendEvent(name: "history", value: historyDisp, displayed: false)
}
if (newValue > state.powerHigh) {
def dispHighValue = dispValue+"w on "+timeString
def historyDisp = ""
sendEvent(name: "maxWATTS", value: dispHighValue as String, unit: "", displayed: false)
state.powerHigh = newValue
historyDisp = "Minimum/Maximum Readings as of ${timeString}\n------------------------------------------------------\nPower Low : ${device.currentState('minWATTS')?.value}\nPower High : ${device.currentState('maxWATTS')?.value}\nMessages : ${device.currentState('resetMessage')?.value}"
sendEvent(name: "history", value: historyDisp, displayed: false)
}
sendEvent(name: "currentWATTS", value: dispValue as String, unit: "", displayed: false)
state.powerValue = newValue
if (state.displayDisabled) {
[name: "power", value: newValue, unit: "W", displayed: true]
} else {
[name: "power", value: newValue, unit: "W", displayed: false]
}
}
}
}
}
}
def zwaveEvent(hubitat.zwave.commands.batteryv1.BatteryReport cmd) {
if (state.displayBattery) {
def map = [:]
map.name = "battery"
map.unit = "%"
map.displayed = true
if (cmd.batteryLevel == 0xFF) { // low battery message from device
map.value = 1
map.isStateChange = true
} else {
map.value = cmd.batteryLevel
map.isStateChange = true
}
sendEvent(name: "battery", value: map.value as String, displayed: true)
return map
} else {
def map = [:]
map.name = "battery"
map.unit = "%"
map.value = 99
map.displayed = false
map.isStateChange = true
sendEvent(name: "battery", value: map.value as String, displayed: false)
return map
}
}
def zwaveEvent(hubitat.zwave.Command cmd) {
// Handles all Z-Wave commands we aren't interested in
log.debug "Unhandled event ${cmd}"
[:]
}
def refresh() {
log.debug "Refreshed ${device.name}"
state.energyValue = -1 // force tile update
state.powerValue = -1
delayBetween([
zwave.meterV2.meterGet(scale: 0).format(),
zwave.meterV2.meterGet(scale: 2).format()
])
}
def poll() {
refresh()
}
// PING is used by Device-Watch in attempt to reach the Device
def ping() {
refresh()
}
def resetkwh() {
log.debug "${device.name} reset kWh/Cost values"
def timeString = new Date().format("MM-dd-yy h:mm a", location.timeZone)
def resetDisp = ""
resetDisp = "kWh value at time of last reset was ${device.currentState('currentKWH')?.value}"
sendEvent(name: "kWhLastReset", value: resetDisp, displayed: true)
resetDisp = "Costs at time of last reset was ${device.currentState('kwhCosts')?.value}"
sendEvent(name: "CostLastReset", value: resetDisp, displayed: true)
def historyDisp = ""
sendEvent(name: "resetMessage", value: "Energy Data (kWh/Cost) Reset On:\n"+timeString, unit: "", displayed: true)
sendEvent(name: "currentKWH", value: "", unit: "", displayed: false)
sendEvent(name: "kwhCosts", value: "", unit: "", displayed: false)
historyDisp = "Minimum/Maximum Readings as of ${timeString}\n------------------------------------------------------\nPower Low : ${device.currentState('minWATTS')?.value}\nPower High : ${device.currentState('maxWATTS')?.value}\nMessages : ${device.currentState('resetMessage')?.value}"
sendEvent(name: "history", value: historyDisp, displayed: false)
state.energyValue = 0
def cmd = delayBetween( [
zwave.meterV2.meterReset().format(),
zwave.meterV2.meterGet(scale: 0).format(),
zwave.meterV2.meterGet(scale: 2).format()
])
cmd
}
def resetmin() {
log.debug "${device.name} reset minimum watts value"
def historyDisp = ""
state.powerLow = 99999
def timeString = new Date().format("MM-dd-yy h:mm a", location.timeZone)
sendEvent(name: "resetMessage", value: "Watts Data Minimum Value Reset On:\n"+timeString, unit: "")
sendEvent(name: "minWATTS", value: "", unit: "", displayed: false)
historyDisp = "Minimum/Maximum Readings as of ${timeString}\n------------------------------------------------------\nPower Low : ${device.currentState('minWATTS')?.value}\nPower High : ${device.currentState('maxWATTS')?.value}\nMessages : ${device.currentState('resetMessage')?.value}"
sendEvent(name: "history", value: historyDisp, displayed: false)
def cmd = delayBetween( [
zwave.meterV2.meterGet(scale: 0).format(),
zwave.meterV2.meterGet(scale: 2).format()
])
cmd
}
def resetmax() {
log.debug "${device.name} reset maximum watts value"
def historyDisp = ""
state.powerHigh = 0
def timeString = new Date().format("MM-dd-yy h:mm a", location.timeZone)
sendEvent(name: "resetMessage", value: "Watts Data Maximum Value Reset On:\n"+timeString, unit: "")
sendEvent(name: "maxWATTS", value: "", unit: "", displayed: false)
historyDisp = "Minimum/Maximum Readings as of ${timeString}\n------------------------------------------------------\nPower Low : ${device.currentState('minWATTS')?.value}\nPower High : ${device.currentState('maxWATTS')?.value}\nMessages : ${device.currentState('resetMessage')?.value}"
sendEvent(name: "history", value: historyDisp, displayed: false)
def cmd = delayBetween( [
zwave.meterV2.meterGet(scale: 0).format(),
zwave.meterV2.meterGet(scale: 2).format()
])
cmd
}
def resetMeter() {
log.debug "Resetting all home energy meter values..."
def resetDisp = ""
resetDisp = "kWh value at time of last reset was ${device.currentState('currentKWH')?.value}"
sendEvent(name: "kWhLastReset", value: resetDisp, displayed: true)
resetDisp = "Costs at time of last reset was ${device.currentState('kwhCosts')?.value}"
sendEvent(name: "CostLastReset", value: resetDisp, displayed: true)
def historyDisp = ""
state.powerHigh = 0
state.powerLow = 99999
state.energyValue = 0
sendEvent(name: "minWATTS", value: "", unit: "", displayed: false)
sendEvent(name: "maxWATTS", value: "", unit: "", displayed: false)
sendEvent(name: "currentKWH", value: "", unit: "", displayed: false)
sendEvent(name: "kwhCosts", value: "Cost\n--", unit: "", displayed: false)
def timeString = new Date().format("MM-dd-yy h:mm a", location.timeZone)
sendEvent(name: "resetMessage", value: "HEM was reset on "+timeString, unit: "", displayed: true)
historyDisp = "Minimum/Maximum Readings as of ${timeString}\n------------------------------------------------------\nPower Low : ${device.currentState('minWATTS')?.value}\nPower High : ${device.currentState('maxWATTS')?.value}\nMessages : ${device.currentState('resetMessage')?.value}"
sendEvent(name: "history", value: historyDisp, displayed: false)
def cmd = delayBetween( [
zwave.meterV2.meterReset().format(),
zwave.meterV2.meterGet(scale: 0).format(),
zwave.meterV2.meterGet(scale: 2).format()
])
cmd
}
def configure() {
log.debug "${device.name} configuring..."
def cmd = delayBetween([
// Perform a complete factory reset. Use this all by itself and comment out all others below.
// Once reset, comment this line out and uncomment the others to go back to normal
// zwave.configurationV1.configurationSet(parameterNumber: 255, size: 4, scaledConfigurationValue: 1).format()
// Accumulate kWh energy when Battery Powered. By default this is disabled to assist saving battery power. (0 == disable, 1 == enable)
zwave.configurationV1.configurationSet(parameterNumber: 12, size: 1, scaledConfigurationValue: 1).format(),
// Send data based on a time interval (0), or based on a change in wattage (1). 0 is default and enables parameters 111, 112, and 113. 1 enables parameters 4 and 8.
zwave.configurationV1.configurationSet(parameterNumber: 3, size: 1, scaledConfigurationValue: reportType).format(),
// If parameter 3 is 1, don't send unless watts have changed by 50 <default> for the whole device.
zwave.configurationV1.configurationSet(parameterNumber: 4, size: 2, scaledConfigurationValue: wattsChanged).format(),
// If parameter 3 is 1, don't send unless watts have changed by 10% <default> for the whole device.
zwave.configurationV1.configurationSet(parameterNumber: 8, size: 1, scaledConfigurationValue: wattsPercent).format(),
// Defines the type of report sent for Reporting Group 1 for the whole device. 1->Battery Report, 4->Meter Report for Watt, 8->Meter Report for kWh
zwave.configurationV1.configurationSet(parameterNumber: 101, size: 4, scaledConfigurationValue: 4).format(), //watts
// If parameter 3 is 0, report every XX Seconds (for Watts) for Reporting Group 1 for the whole device.
zwave.configurationV1.configurationSet(parameterNumber: 111, size: 4, scaledConfigurationValue: secondsWatts).format(),
// Defines the type of report sent for Reporting Group 2 for the whole device. 1->Battery Report, 4->Meter Report for Watt, 8->Meter Report for kWh
zwave.configurationV1.configurationSet(parameterNumber: 102, size: 4, scaledConfigurationValue: 8).format(), //kWh
// If parameter 3 is 0, report every XX seconds (for kWh) for Reporting Group 2 for the whole device.
zwave.configurationV1.configurationSet(parameterNumber: 112, size: 4, scaledConfigurationValue: secondsKwh).format(),
// Defines the type of report sent for Reporting Group 3 for the whole device. 1->Battery Report, 4->Meter Report for Watt, 8->Meter Report for kWh
zwave.configurationV1.configurationSet(parameterNumber: 103, size: 4, scaledConfigurationValue: 1).format(), //battery
// If parameter 3 is 0, report every XX seconds (for battery) for Reporting Group 2 for the whole device.
zwave.configurationV1.configurationSet(parameterNumber: 113, size: 4, scaledConfigurationValue: secondsBattery).format()
])
cmd
}Hi Please let me know how can you monitor your furnace.
I put a HEM on the power going into it under the house. The AC I put in the panel. The Furnace was on a non dedicated circuit unfortunately.
Could you post only what lines were modified to get the 15 secs reporting? The reason I'm asking is I have the HEM Gen5 but I have the same problem, it reports something else that on the driver, probably looking what you did to correct the reporting interval I can modify my Gen5 driver and get better response,
please.
Thanks in advance.
With the new driver, it's just an input option to change the reporting.
Ok, I will try to find what you added, I don't know anything about groovy, so I will take long time to figure out.
here are the parameters that are of interest. When you push Configure, it sets these parameters. Your Gen5 might be different. If you have the manual for your Gen5 version, you can use mike's zwave tool to set specific parameters.
def configure() {
log.debug "${device.name} configuring..."
def cmd = delayBetween([
// Perform a complete factory reset. Use this all by itself and comment out all others below.
// Once reset, comment this line out and uncomment the others to go back to normal
// zwave.configurationV1.configurationSet(parameterNumber: 255, size: 4, scaledConfigurationValue: 1).format()
// Accumulate kWh energy when Battery Powered. By default this is disabled to assist saving battery power. (0 == disable, 1 == enable)
zwave.configurationV1.configurationSet(parameterNumber: 12, size: 1, scaledConfigurationValue: 1).format(),
// Send data based on a time interval (0), or based on a change in wattage (1). 0 is default and enables parameters 111, 112, and 113. 1 enables parameters 4 and 8.
zwave.configurationV1.configurationSet(parameterNumber: 3, size: 1, scaledConfigurationValue: reportType).format(),
// If parameter 3 is 1, don't send unless watts have changed by 50 <default> for the whole device.
zwave.configurationV1.configurationSet(parameterNumber: 4, size: 2, scaledConfigurationValue: wattsChanged).format(),
// If parameter 3 is 1, don't send unless watts have changed by 10% <default> for the whole device.
zwave.configurationV1.configurationSet(parameterNumber: 8, size: 1, scaledConfigurationValue: wattsPercent).format(),
// Defines the type of report sent for Reporting Group 1 for the whole device. 1->Battery Report, 4->Meter Report for Watt, 8->Meter Report for kWh
zwave.configurationV1.configurationSet(parameterNumber: 101, size: 4, scaledConfigurationValue: 4).format(), //watts
// If parameter 3 is 0, report every XX Seconds (for Watts) for Reporting Group 1 for the whole device.
zwave.configurationV1.configurationSet(parameterNumber: 111, size: 4, scaledConfigurationValue: secondsWatts).format(),
// Defines the type of report sent for Reporting Group 2 for the whole device. 1->Battery Report, 4->Meter Report for Watt, 8->Meter Report for kWh
zwave.configurationV1.configurationSet(parameterNumber: 102, size: 4, scaledConfigurationValue: 8).format(), //kWh
// If parameter 3 is 0, report every XX seconds (for kWh) for Reporting Group 2 for the whole device.
zwave.configurationV1.configurationSet(parameterNumber: 112, size: 4, scaledConfigurationValue: secondsKwh).format(),
// Defines the type of report sent for Reporting Group 3 for the whole device. 1->Battery Report, 4->Meter Report for Watt, 8->Meter Report for kWh
zwave.configurationV1.configurationSet(parameterNumber: 103, size: 4, scaledConfigurationValue: 1).format(), //battery
// If parameter 3 is 0, report every XX seconds (for battery) for Reporting Group 2 for the whole device.
zwave.configurationV1.configurationSet(parameterNumber: 113, size: 4, scaledConfigurationValue: secondsBattery).format()
])
cmd
}
1 Like
Thanks, I found parameter 3 is the key, on Gen5 driver is set to 1.
So n00bie question. Do I need a HEM on every individual thing I want to monitor or can I just put it on the mains and see what is going on based on wattage signature?
They are not intelligent. HEM or other power monitoring outlet on each circuit or device you want to monitor.
Thanks for the info.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
