Edge Driver for ZWN-SC7 Enerwave 7 Button Scene Controller?

Request for Edge Driver for ZWN-SC7 Enerwave 7 Button Scene Controller

  • currentButton: 7
  • manufacturer: Wenzhou MTLC Electric Appliances Co.,Ltd.
  • networkSecurityLevel: ZWAVE_LEGACY_NON_SECURE
  • numButtons: 7

zw:L type:0202 mfr:011A prod:0801 model:0B03 ver:1.05 zwv:3.42 lib:02 cc:2D,85,86,72

Matt Franks Groovy Driver Below


  • ZWN-SC7 Enerwave 7 Button Scene Controller
  • Author: Matt Frank based on VRCS Button Controller by Brian Dahlem, based on SmartThings Button Controller
  • Date Created: 2014-12-18
  • Updated: 2017-05-10 update DT to support pushed as @ady624
  • Last Update: 2021-01-26 update by Tim Grimley to work in new Smartthings app
  • 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.
  • 2016-09-30 Modified to allow for correct event value “pushed” and added numberOfButtons as per ST documentation


import groovy.transform.Field
import groovy.json.JsonOutput

metadata {
// Automatically generated. Make future change here.
definition (name: “ZWNSC7 Enerwave Scene Master”, namespace: “mwav3”, author: “Tim Grimley”) {
capability “Actuator”
capability “Button”
capability “Configuration”
capability “Indicator”
capability “Sensor”

    attribute "currentButton", "STRING"
    attribute "numButtons", "STRING"
    attribute "numberOfButtons", "NUMBER"

fingerprint deviceId: "0x0202", inClusters:"0x21, 0x2D, 0x85, 0x86, 0x72"
fingerprint deviceId: "0x0202", inClusters:"0x2D, 0x85, 0x86, 0x72"

preferences {
  	input "forceupdate", "bool", title: "Force Settings Update/Refresh?", description: "Toggle to force settings update", required: false


simulator {
status “button 1 pushed”: “command: 2B01, payload: 01 FF”
status “button 2 pushed”: “command: 2B01, payload: 02 FF”
status “button 3 pushed”: “command: 2B01, payload: 03 FF”
status “button 4 pushed”: “command: 2B01, payload: 04 FF”
status “button 5 pushed”: “command: 2B01, payload: 05 FF”
status “button 6 pushed”: “command: 2B01, payload: 06 FF”
status “button 7 pushed”: “command: 2B01, payload: 07 FF”
status “button released”: “command: 2C02, payload: 00”

tiles {
standardTile(“button”, “device.button”, width: 2, height: 2) {
state “default”, label: " ", icon: “st.unknown.zwave.remote-controller”, backgroundColor: “#ffffff
state “button 1”, label: “1”, icon: “st.Weather.weather14”, backgroundColor: “#79b821
state “button 2”, label: “2”, icon: “st.Weather.weather14”, backgroundColor: “#79b821
state “button 3”, label: “3”, icon: “st.Weather.weather14”, backgroundColor: “#79b821
state “button 4”, label: “4”, icon: “st.Weather.weather14”, backgroundColor: “#79b821
state “button 5”, label: “5”, icon: “st.Weather.weather14”, backgroundColor: “#79b821
state “button 6”, label: “6”, icon: “st.Weather.weather14”, backgroundColor: “#79b821
state “button 7”, label: “7”, icon: “st.Weather.weather14”, backgroundColor: “#79b821


    // Configure button.  Syncronize the device capabilities that the UI provides
standardTile("configure", "device.configure", inactiveLabel: false, decoration: "flat") {
  state "configure", label:'', action:"configuration.configure", icon:"st.secondary.configure"


main "button"
details (["button", "configure"])


// parse events into attributes
def parse(String description) {
log.debug “Parsing ‘${description}’”

def result = null

def cmd = zwave.parse(description)
if (cmd) {
result = zwaveEvent(cmd)
return result


// Handle a button being pressed
def buttonEvent(button) {
button = button as Integer
def result =

updateState("currentButton", "$button")

if (button > 0) {
    // update the device state, recording the button press
    result << createEvent(name: "button", value: "pushed", data: [buttonNumber: button], descriptionText: "$device.displayName button $button was pushed", isStateChange: true)

    // turn off the button LED
    result << response(zwave.sceneActuatorConfV1.sceneActuatorConfReport(dimmingDuration: 255, level: 255, sceneId: 0))

else {
// update the device state, recording the button press
result << createEvent(name: “button”, value: “default”, descriptionText: “$device.displayName button was released”, isStateChange: true)

    result << response(zwave.sceneActuatorConfV1.sceneActuatorConfReport(dimmingDuration: 255, level: 255, sceneId: 0))



// A zwave command for a button press was received
def zwaveEvent(physicalgraph.zwave.commands.sceneactivationv1.SceneActivationSet cmd) {

// The controller likes to repeat the command… ignore repeats
if (state.lastScene == cmd.sceneId && (state.repeatCount < 4) && (now() - state.repeatStart < 2000)) {
log.debug “Button ${cmd.sceneId} repeat ${state.repeatCount}x ${now()}”
state.repeatCount = state.repeatCount + 1
else {
// If the button was really pressed, store the new scene and handle the button press
state.lastScene = cmd.sceneId
state.lastLevel = 0
state.repeatCount = 0
state.repeatStart = now()



// A scene command was received – it’s probably scene 0, so treat it like a button release
def zwaveEvent(physicalgraph.zwave.commands.sceneactuatorconfv1.SceneActuatorConfGet cmd) {



// The controller sent a scene activation report. Log it, but it really shouldn’t happen.
def zwaveEvent(physicalgraph.zwave.commands.sceneactuatorconfv1.SceneActuatorConfReport cmd) {
log.debug “Scene activation report”
log.debug “Scene ${cmd.sceneId} set to ${cmd.level}”



// Configuration Reports are replys to configuration value requests… If we knew what configuration parameters
// to request this could be very helpful.
def zwaveEvent(physicalgraph.zwave.commands.configurationv1.ConfigurationReport cmd) {

// The VRC supports hail commands, but I haven’t seen them.
def zwaveEvent(physicalgraph.zwave.commands.hailv1.Hail cmd) {
createEvent([name: “hail”, value: “hail”, descriptionText: “Switch button was pressed”, displayed: false])

// Update manufacturer information when it is reported
def zwaveEvent(physicalgraph.zwave.commands.manufacturerspecificv2.ManufacturerSpecificReport cmd) {
if (state.manufacturer != cmd.manufacturerName) {
updateDataValue(“manufacturer”, cmd.manufacturerName)



// Association Groupings Reports tell us how many groupings the device supports. This equates to the number of
// buttons/scenes in the VRCS
def zwaveEvent(physicalgraph.zwave.commands.associationv2.AssociationGroupingsReport cmd) {
def response =

log.debug "${getDataByName("numButtons")} buttons stored"

if ((getDataByName(“numButtons”) != “$cmd.supportedGroupings”) || (getDataByName(“numberOfButtons”) != (int) cmd.supportedGroupings)) {
updateState(“numButtons”, “$cmd.supportedGroupings”)
updateState(“numberOfButtons”, (int) cmd.supportedGroupings)
log.debug “${cmd.supportedGroupings} groups available”
response << createEvent(name: “numButtons”, value: cmd.supportedGroupings, displayed: false)
response << createEvent(name: “numberOfButtons”, value: cmd.supportedGroupings, displayed: false)

    response << associateHub()

else {
response << createEvent(name: “numButtons”, value: cmd.supportedGroupings, displayed: false)
response << createEvent(name: “numberOfButtons”, value: cmd.supportedGroupings, displayed: false)
return response

// Handles all Z-Wave commands we don’t know we are interested in
def zwaveEvent(physicalgraph.zwave.Command cmd) {

// handle commands

// Create a list of the configuration commands to send to the device
def configurationCmds() {
// Always check the manufacturer and the number of groupings allowed
def commands = [
zwave.sceneControllerConfV1.sceneControllerConfSet(groupId:1, sceneId:1).format(),
zwave.sceneControllerConfV1.sceneControllerConfSet(groupId:2, sceneId:2).format(),
zwave.sceneControllerConfV1.sceneControllerConfSet(groupId:3, sceneId:3).format(),
zwave.sceneControllerConfV1.sceneControllerConfSet(groupId:4, sceneId:4).format(),
zwave.sceneControllerConfV1.sceneControllerConfSet(groupId:5, sceneId:5).format(),
zwave.sceneControllerConfV1.sceneControllerConfSet(groupId:6, sceneId:6).format(),
zwave.sceneControllerConfV1.sceneControllerConfSet(groupId:7, sceneId:7).format()


commands << associateHub()



// Configure the device
def configure() {
def cmd=configurationCmds()
log.debug(“Sending configuration: ${cmd}”)
return cmd


def initialize() {
sendEvent(name: “numberOfButtons”, value: 7, displayed: false)
sendEvent(name: “supportedButtonValues”, value:JsonOutput.toJson([“pushed”]), displayed:false)


//Update Settings
def updated() {

sendEvent(name: "supportedButtonValues", value:JsonOutput.toJson(["pushed"]), displayed:false)
sendEvent(name: "numberOfButtons", value: 7, displayed: false)



// Associate the hub with the buttons on the device, so we will get status updates
def associateHub() {
def commands =

// Loop through all the buttons on the controller
for (def buttonNum = 1; buttonNum <= integer(getDataByName("numButtons")); buttonNum++) {

      // Associate the hub with the button so we will get status updates
      commands << zwave.associationV1.associationSet(groupingIdentifier: buttonNum, nodeId: zwaveHubNodeId).format()


return commands


// Update State
// Store mode and settings
def updateState(String name, String value) {
state[name] = value
device.updateDataValue(name, value)

// Get Data By Name
// Given the name of a setting/attribute, lookup the setting’s value
def getDataByName(String name) {
state[name] ?: device.getDataValue(name)

//Stupid conversions

// convert a double to an integer
def integer(double v) {
return v.toInteger()

// convert a hex string to integer
def integerhex(String v) {
if (v == null) {
return 0

return Integer.parseInt(v, 16)

// convert a hex string to integer
def integer(String v) {
if (v == null) {
return 0

return Integer.parseInt(v)

(I moved this to its own thread because you posted the full text of the Groovy DTH instead of just a link to it.

I am the author of the request thread so I read every post there multiple times. But when I say “read,” I really mean “listen to.” I am quadriparetic and rely on a screen reader. So long posts of code are both timeconsuming and very difficult for me.

If you would like to add another post to the request thread limited to the device details and a link to the Groovy dth, that would be fine.

Thanks for understanding.)

Thanks, I reposted with a link to the groovy DTH.

1 Like