Anybody know how to change disable/change the reporting interval of these devices?
There’s no need to have power reports generated every second in any of my use cases.
3 Likes
power reports flooding my activity feed. I cant find anything. scrolling takes ages.
1 Like
i deleted and repaired mine, the problem went away…
mine are 3 days new zigbee outlets. i think it is feature not fail.
1 Like
doesn’t matter, mine was brand new. reporting every second isn’t a feature, the device didn’t configure correctly/completely when it paired.
how often they should report?
mine only report when the load changes, but I haven’t studied it.
True… but fractional load changes (e.g., a PC that ramps the CPU up and down), create a lot of events…
agreed, my devices connected to outlet fluctuate based on external influence.
I just want to turn it off.
Looks like easiest way is to change device type to custom type.
1 Like
It’s brutal. I have two, reporting every momentary fluctuations load on landscape lighting from dusk to midnight. There’s no way to modify this?
1 Like
You’ll need to edit the configure section of the devicetype, specifically the “Zcl global send-me-a-report” line. I couldn’t figure out which devicetype is actually being used for these as there’s 3 in the ST Github.
In that Zcl line, after the 0x29 starts the reporting parameters. The ‘1’ means it will report as fast as every second, it’s the minimum reporting interval. The ‘600’ means it will report at least every 10 minutes regardless of whether anything changed. The number in the bracket is the minimum change that will be reported. I’m not sure how that value converts to an actual power value, but it seems to be very small.
Once you customize the devicetype, I think you’ll need to reset and re-pair the outlet. If you so without removing it from ST it should join back as the same device and get the new configure commands.
Thanks for this… I feel like the newb I am, but does this involve creating a new device type or editing the existing? If editing, how can I find the code for the device? I’ve looked at the api and can’t seem to find it. Thanks
and if picking new code from github, which did you use?
You can check what devicetype it’s using by looking at the device info in My Devices section of the IDE, then look in the ST public Github repo that has all the devicetypes. You would edit that code and use it to create a new devicetype in the IDE. Assign the device to the new code, then reset and re-pair. It should re-pair using the new devicetype and get the updated configuration.
Hi
I was hoping someone could let me what steps to follow to how to “reset and re-pair the device”. I attempted to make the changes proposed to the send-me-a-report line by creating my own custom device type (under My Device Types) and linking it to the Smartthings outlet - device (under My Devices). Ideally if I can get the min change in value to work as expected I would be ecstatic (i.e. the proposed example below). Unfortunately, no matter what I change, the outlet does not change it’s reporting frequency. Note - I have changed all of the last 3 values (i.e. min report time, max and change in value) with no success (not illustrated above) I even commented out the code and republished to see if no reporting would take place but still no change to the device.
I unplugged device for 2 min and replugged in but nothing. How do I reset and re-pair the device… (delete it from all smartapps, delete the device and start again??).
Original Code: “zcl global send-me-a-report 0x0B04 0x050B 0x29 1 600 {05 00}”,
Proposed Code: “zcl global send-me-a-report 0x0B04 0x050B 0x29 1 600 {100}”,
I would greatly appreciate some assistance in this matter.
I have attempted to follow the instructions in FAQ: An Overview of Using Custom Code in SmartThings to no avail.
Hi Kennet
One quick fix for your new code line. Instead of {100} at the end, you’ll want to use {64 0000}. The zigbee code uses hex formatting, so 100 = 64 and you need the zeros after because there’s a 2nd payload input for timeout period.
To reset, unplug the outlet. Then while holding the button, plug the outlet in. When the LED comes on, release the button. It should now be reset. Start the Connect New Device procedure in the app and give it a few minutes. It probably won’t register that a new device is connected since the outlet already exists in your setup. (If you have Live Logging in the IDE up while the app searches for new devices, you should be able to see it rejoin.)
Below is the manual for the outlet mentions the reset procedure, although doesn’t call it that.
https://support.smartthings.com/hc/en-us/article_attachments/203008000/Outlet_Booklet_US.pdf
Thanks Scott! I think I finally got it working thanks to your assistance. I am getting significantly less activities in my “Recently” section. I will continue to tweak to try and reduce it further.
Here is the code to only display once an hour, Go to IDE and add device handler.
Then delete your connected smart outlet and re connect it and it should connect using the new device handler
https://graph.api.smartthings.com/ide/devices
to reset/reconnect device:
from sticks18 “To reset, unplug the outlet. Then while holding the button, plug the outlet in. When the LED comes on, release the button. It should now be reset. Start the Connect New Device procedure in the app and give it a few minutes. It probably won’t register that a new device is connected since the outlet already exists in your setup. (If you have Live Logging in the IDE up while the app searches for new devices, you should be able to see it rejoin.)”
/**
* Copyright 2015 SmartThings
*
* 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.
*
* SmartPower Outlet (CentraLite)
*
* Author: SmartThings
* Date: 2015-08-23
*/
metadata {
// Automatically generated. Make future change here.
definition (name: "SmartPower Outlet", namespace: "smartthings", author: "SmartThings") {
capability "Actuator"
capability "Switch"
capability "Power Meter"
capability "Configuration"
capability "Refresh"
capability "Sensor"
// indicates that device keeps track of heartbeat (in state.heartbeat)
attribute "heartbeat", "string"
fingerprint profileId: "0104", inClusters: "0000,0003,0004,0005,0006,0B04,0B05", outClusters: "0019", manufacturer: "CentraLite", model: "3200", deviceJoinName: "Outlet"
fingerprint profileId: "0104", inClusters: "0000,0003,0004,0005,0006,0B04,0B05", outClusters: "0019", manufacturer: "CentraLite", model: "3200-Sgb", deviceJoinName: "Outlet"
fingerprint profileId: "0104", inClusters: "0000,0003,0004,0005,0006,0B04,0B05", outClusters: "0019", manufacturer: "CentraLite", model: "4257050-RZHAC", deviceJoinName: "Outlet"
fingerprint profileId: "0104", inClusters: "0000,0003,0004,0005,0006,0B04,0B05", outClusters: "0019"
}
// simulator metadata
simulator {
// status messages
status "on": "on/off: 1"
status "off": "on/off: 0"
// reply messages
reply "zcl on-off on": "on/off: 1"
reply "zcl on-off off": "on/off: 0"
}
preferences {
section {
image(name: 'educationalcontent', multiple: true, images: [
"http://cdn.device-gse.smartthings.com/Outlet/US/OutletUS1.jpg",
"http://cdn.device-gse.smartthings.com/Outlet/US/OutletUS2.jpg"
])
}
}
// UI tile definitions
tiles(scale: 2) {
multiAttributeTile(name:"switch", type: "lighting", width: 6, height: 4, canChangeIcon: true){
tileAttribute ("device.switch", key: "PRIMARY_CONTROL") {
attributeState "on", label: '${name}', action: "switch.off", icon: "st.switches.switch.on", backgroundColor: "#79b821", nextState: "turningOff"
attributeState "off", label: '${name}', action: "switch.on", icon: "st.switches.switch.off", backgroundColor: "#ffffff", nextState: "turningOn"
attributeState "turningOn", label: '${name}', action: "switch.off", icon: "st.switches.switch.on", backgroundColor: "#79b821", nextState: "turningOff"
attributeState "turningOff", label: '${name}', action: "switch.on", icon: "st.switches.switch.off", backgroundColor: "#ffffff", nextState: "turningOn"
}
tileAttribute ("power", key: "SECONDARY_CONTROL") {
attributeState "power", label:'${currentValue} W'
}
}
standardTile("refresh", "device.power", inactiveLabel: false, decoration: "flat", width: 2, height: 2) {
state "default", label:'', action:"refresh.refresh", icon:"st.secondary.refresh"
}
main "switch"
details(["switch","refresh"])
}
}
// Parse incoming device messages to generate events
def parse(String description) {
log.debug "description is $description"
// save heartbeat (i.e. last time we got a message from device)
state.heartbeat = Calendar.getInstance().getTimeInMillis()
def finalResult = zigbee.getKnownDescription(description)
//TODO: Remove this after getKnownDescription can parse it automatically
if (!finalResult && description!="updated")
finalResult = getPowerDescription(zigbee.parseDescriptionAsMap(description))
if (finalResult) {
log.info finalResult
if (finalResult.type == "update") {
log.info "$device updates: ${finalResult.value}"
}
else if (finalResult.type == "power") {
def powerValue = (finalResult.value as Integer)/10
sendEvent(name: "power", value: powerValue)
/*
Dividing by 10 as the Divisor is 10000 and unit is kW for the device. AttrId: 0302 and 0300. Simplifying to 10
power level is an integer. The exact power level with correct units needs to be handled in the device type
to account for the different Divisor value (AttrId: 0302) and POWER Unit (AttrId: 0300). CLUSTER for simple metering is 0702
*/
}
else {
sendEvent(name: finalResult.type, value: finalResult.value)
}
}
else {
log.warn "DID NOT PARSE MESSAGE for description : $description"
log.debug zigbee.parseDescriptionAsMap(description)
}
}
def off() {
zigbee.off()
}
def on() {
zigbee.on()
}
def refresh() {
sendEvent(name: "heartbeat", value: "alive", displayed:false)
zigbee.onOffRefresh() + zigbee.refreshData("0x0B04", "0x050B")
}
def configure() {
zigbee.onOffConfig() + powerConfig() + refresh()
}
//power config for devices with min reporting interval as 1 seconds and reporting interval if no activity as 10min (600s)
//min change in value is 01
def powerConfig() {
[
"zdo bind 0x${device.deviceNetworkId} 1 ${endpointId} 0x0B04 {${device.zigbeeId}} {}", "delay 200",
"zcl global send-me-a-report 0x0B04 0x050B 0x29 6400 6401 {64 0000}", //The send-me-a-report is custom to the attribute type for CentraLite
"send 0x${device.deviceNetworkId} 1 ${endpointId}", "delay 500"
]
}
private getEndpointId() {
new BigInteger(device.endpointId, 16).toString()
}
//TODO: Remove this after getKnownDescription can parse it automatically
def getPowerDescription(descMap) {
def powerValue = "undefined"
if (descMap.cluster == "0B04") {
if (descMap.attrId == "050b") {
if(descMap.value!="ffff")
powerValue = zigbee.convertHexToInt(descMap.value)
}
}
else if (descMap.clusterId == "0B04") {
if(descMap.command=="07"){
return [type: "update", value : "power (0B04) capability configured successfully"]
}
}
if (powerValue != "undefined"){
return [type: "power", value : powerValue]
}
else {
return [:]
}
}
2 Likes
Thanks, Bud…
But save me from diff-ing… What do did you change?
//power config for devices with min reporting interval as 1 seconds and reporting interval if no activity as 10min (600s)
//min change in value is 01
def powerConfig() {
[
“zdo bind 0x${device.deviceNetworkId} 1 ${endpointId} 0x0B04 {${device.zigbeeId}} {}”, “delay 200”,
“zcl global send-me-a-report 0x0B04 0x050B 0x29 6400 6401 {64 0000}”, //The send-me-a-report is custom to the attribute type for CentraLite
“send 0x${device.deviceNetworkId} 1 ${endpointId}”, “delay 500”
]
}
2 Likes