I am a little surprised you aren’t using the DTH shown here [EDGE] Tuya Leak Sensor TS0207 ** NOT RECOMMENDED ** as that is for your exact device.
1 Like
In fact, initially he was recognized as “thing”. I manually changed the DHT to this everspring flood sensor as instructed by a youtuber in Brazil and it worked.
This DHT that speaks is custom.
I’m preferring to use drivers or even changing devices that use custom DHT, for fear of smartthings changes.
In case, if a native DHT works (even if apparently it is intended for zwave), I prefer to use it.
But, I’d be much happier if I could get a driver (it’s the future, after all) to make the sensor work.
I changed the category of profile switch-level to Switch and now you can select more icons in app.
I tested in my bulb and now appears this
Is this what you wanted?
┌─────────────┬──────────────────────────────────────┐
│ Name │ Zigbee Light Multifunction Mc │
│ Version │ 2022-01-27T17:45:49.524536 │
└─────────────┴──────────────────────────────────────┘
1 Like
The DTH that @orangebucket mentioned seems to be the most correct for that device.
I have seen that @veonua, have already included your device fingerprints in a driver.
If it works for you, that would be perfect.
If it doesn’t work for you, we try to include it in the driver I have for the ST sensor and centralite, but the only thing left to check is what attribute it uses to send the battery report, the voltage or remaining %. The DTH uses both and does not specify what each model uses.
Hey Guys. (in special @Mariano_Colmenarejo almost Zemismart Partner! 
)
Fresh Zemismart Multi Channel Switch just arrived and i would like to post here for any interested DEV since probably will interest a lot of users:
Zemismart Tuya Zigbee Smart Wall Light Switch with Neutral 1 2 3 4 Gangs - KES-606US-L1
Working DHT (developed to other model, touch)- 1,2,3 and 4 GANGS
/*
- Zemismart Zigbee Switch Touch (Switch)
- Copyright 2020 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.
/
public static String version() { return “v0.0.2.20200426” }
/
- 2020/04/26 >>> v0.0.2.20200426 - Support to old Jemi swtich version
- 2020/04/25 >>> v0.0.1.20200425 - Initialize
*/
import java.lang.Math
metadata {
definition(name: “Zemismart Zigbee Switch Touch (Switch)”, namespace: “niquini”, author: “Wanderson Niquini”, ocfDeviceType: “oic.d.switch”, vid: “generic-switch”) {
capability “Actuator”
capability “Configuration”
capability “Refresh”
capability “Health Check”
capability “Switch”
command "childOn", ["string"]
command "childOff", ["string"]
// Zemi ZigBee Multi Switch
fingerprint endpointId: "10", profileId: "0104", inClusters: "0000, 0003, 0004, 0005, 0006", manufacturer: "Feibit Inc co.", model: "FB56+ZSW1GKJ2.7", deviceJoinName: "Zemi Zigbee Switch"
fingerprint endpointId: "10", profileId: "0104", deviceId: "0002", inClusters: "0000, 0005, 0004, 0006", outClusters: "0000", manufacturer: "Feibit Inc co.", model: "FB56+ZSW1HKJ2.5", deviceJoinName: "Zemi Zigbee Switch 1"
fingerprint endpointId: "10", profileId: "0104", deviceId: "0002", inClusters: "0000, 0003, 0004, 0005, 0006", manufacturer: "Feibit Inc co.", model: "FB56+ZSW1IKJ2.7", deviceJoinName: "Zemi Zigbee Switch 1"
fingerprint endpointId: "0B", profileId: "C05E", inClusters: "0000, 0004, 0003, 0006, 0005, 1000, 0008", outClusters: "0019", manufacturer: "FeiBit", model: "FNB56-ZSW02LX2.0", deviceJoinName: "Zemi Zigbee Switch 1"
fingerprint endpointId: "01", profileId: "C05E", inClusters: "0000, 0004, 0003, 0006, 0005, 1000, 0008", outClusters: "0019", manufacturer: "FeiBit", model: "FNB56-ZSW03LX2.0", deviceJoinName: "Zemi Zigbee Switch 1"
fingerprint endpointId: "0B", profileId: "C05E", inClusters: "0000, 0004, 0003, 0006, 0005, 1000, 0008", outClusters: "0019", manufacturer: "3A Smart Home DE", model: "LXN-2S27LX1.0", deviceJoinName: "Zemi Zigbee Switch"
fingerprint endpointId: "01", profileId: "C05E", inClusters: "0000, 0004, 0003, 0006, 0005, 1000, 0008", outClusters: "0019", manufacturer: "3A Smart Home DE", model: "LXN-3S27LX1.0", deviceJoinName: "Zemi Zigbee Switch"
}
preferences {
input type: "paragraph", element: "paragraph", title: "Version", description: version(), displayDuringSetup: false
}
// 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"
}
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.light.on", backgroundColor: "#00A0DC", nextState: "turningOff"
attributeState "off", label: '${name}', action: "switch.on", icon: "st.switches.light.off", backgroundColor: "#ffffff", nextState: "turningOn"
attributeState "turningOn", label: '${name}', action: "switch.off", icon: "st.switches.light.on", backgroundColor: "#00A0DC", nextState: "turningOff"
attributeState "turningOff", label: '${name}', action: "switch.on", icon: "st.switches.light.off", backgroundColor: "#ffffff", nextState: "turningOn"
}
}
standardTile("refresh", "device.refresh", inactiveLabel: false, decoration: "flat", width: 2, height: 2) {
state "default", label: "", action: "refresh.refresh", icon: "st.secondary.refresh"
}
main "switch"
details(["switch", "refresh"])
}
}
def installed() {
log.debug “installed()”
def endpointCount = getEndpointCount()
if (endpointCount == 1) {
// for 1 gang switch - ST Official local dth
setDeviceType(“ZigBee Switch”)
} else if (endpointCount > 1){
def model = device.getDataValue(“model”)
if (model == ‘FB56+ZSW1HKJ2.5’ || model == ‘FB56+ZSW1IKJ2.7’) {
device.updateDataValue(“endpointId”, “10”)
}
// for multi switch, cloud device
createChildDevices()
}
updateDataValue(“onOff”, “catchall”)
refresh()
}
def updated() {
log.debug “updated()”
updateDataValue(“onOff”, “catchall”)
refresh()
}
def parse(String description) {
Map eventMap = zigbee.getEvent(description)
Map eventDescMap = zigbee.parseDescriptionAsMap(description)
if (!eventMap && eventDescMap) {
eventMap = [:]
if (eventDescMap?.clusterId == zigbee.ONOFF_CLUSTER) {
eventMap[name] = "switch"
eventMap[value] = eventDescMap?.value
}
}
if (eventMap) {
def endpointId = device.getDataValue("endpointId")
log.debug "eventMap $eventMap | eventDescMap $eventDescMap"
if (eventDescMap?.sourceEndpoint == endpointId) {
log.debug "parse - sendEvent parent $eventDescMap.sourceEndpoint"
sendEvent(eventMap)
} else {
log.debug "parse - sendEvent child $eventDescMap.sourceEndpoint"
def childDevice = childDevices.find {
it.deviceNetworkId == "$device.deviceNetworkId:${eventDescMap.sourceEndpoint}"
}
if (childDevice) {
childDevice.sendEvent(eventMap)
} else {
log.debug "Child device: $device.deviceNetworkId:${eventDescMap.sourceEndpoint} was not found"
def parentEndpointInt = zigbee.convertHexToInt(endpointId)
def childEndpointInt = zigbee.convertHexToInt(eventDescMap?.sourceEndpoint)
def childEndpointHexString = zigbee.convertToHexString(childEndpointInt, 2).toUpperCase()
def deviceLabel = "${device.displayName[0..-2]}"
def deviceIndex = Math.abs(childEndpointInt - parentEndpointInt) + 1
createChildDevice("$deviceLabel$deviceIndex", childEndpointHexString)
}
}
}
}
private getEndpointCount() {
def model = device.getDataValue(“model”)
switch (model) {
case 'LXN-2S27LX1.0' : return 2
case 'LXN-3S27LX1.0' : return 3
case 'FNB56-ZSW02LX2.0' : return 2
case 'FNB56-ZSW03LX2.0' : return 3
case 'FB56+ZSW1HKJ2.5' : return 2
case 'FB56+ZSW1GKJ2.7' : return 1
case 'FB56+ZSW1IKJ2.7' : return 3
default : return 0
}
}
private void createChildDevices() {
log.debug(“createChildDevices of $device.deviceNetworkId”)
def endpointCount = getEndpointCount()
def endpointId = device.getDataValue(“endpointId”)
def endpointInt = zigbee.convertHexToInt(endpointId)
def deviceLabel = “${device.displayName[0…-2]}”
for (i in 1..endpointCount - 1) {
def endpointHexString = zigbee.convertToHexString(endpointInt + i, 2).toUpperCase()
createChildDevice("$deviceLabel${i + 1}", endpointHexString)
}
}
private void createChildDevice(String deviceLabel, String endpointHexString) {
def childDevice = childDevices.find {
it.deviceNetworkId == “$device.deviceNetworkId:$endpointHexString”
}
if (!childDevice) {
log.debug(“Need to createChildDevice: $device.deviceNetworkId:$endpointHexString”)
addChildDevice(“smartthings”, “Child Switch Health”, “$device.deviceNetworkId:$endpointHexString”, device.hubId,
[completedSetup: true, label: deviceLabel, isComponent: false])
} else {
log.debug(“createChildDevice: SKIP - $device.deviceNetworkId:${endpointHexString}”)
}
}
private getChildEndpoint(String dni) {
dni.split(“:”)[-1] as String
}
def on() {
log.debug(“on”)
zigbee.on()
}
def off() {
log.debug(“off”)
zigbee.off()
}
def childOn(String dni) {
log.debug(“child on ${dni}”)
def childEndpoint = getChildEndpoint(dni)
def endpointInt = zigbee.convertHexToInt(childEndpoint)
zigbee.command(zigbee.ONOFF_CLUSTER, 0x01, “”, [destEndpoint: endpointInt])
}
def childOff(String dni) {
log.debug(“child off ${dni}”)
def childEndpoint = getChildEndpoint(dni)
def endpointInt = zigbee.convertHexToInt(childEndpoint)
zigbee.command(zigbee.ONOFF_CLUSTER, 0x00, “”, [destEndpoint: endpointInt])
}
/**
- PING is used by Device-Watch in attempt to reach the Device
- */
def ping() {
return refresh()
}
def refresh() {
def cmds = zigbee.onOffRefresh()
def endpointCount = getEndpointCount()
if (endpointCount > 1) {
def endpointId = device.getDataValue("endpointId")
def endpointInt = zigbee.convertHexToInt(endpointId)
for (i in 1..endpointCount - 1) {
def endpointValue = endpointInt + i
cmds += zigbee.readAttribute(zigbee.ONOFF_CLUSTER, 0x0000, [destEndpoint: endpointValue])
}
} else {
cmds += zigbee.readAttribute(zigbee.ONOFF_CLUSTER, 0x0000, [destEndpoint: 0xFF])
}
return cmds
}
def poll() {
refresh()
}
def healthPoll() {
log.debug “healthPoll()”
def cmds = refresh()
cmds.each { sendHubCommand(new physicalgraph.device.HubAction(it)) }
}
def configureHealthCheck() {
Integer hcIntervalMinutes = 12
if (!state.hasConfiguredHealthCheck) {
log.debug “Configuring Health Check, Reporting”
unschedule(“healthPoll”)
runEvery5Minutes(“healthPoll”)
def healthEvent = [name: “checkInterval”, value: hcIntervalMinutes * 60, displayed: false, data: [protocol: “zigbee”, hubHardwareId: device.hub.hardwareID]]
// Device-Watch allows 2 check-in misses from device
sendEvent(healthEvent)
childDevices.each {
it.sendEvent(healthEvent)
}
state.hasConfiguredHealthCheck = true
}
}
def configure() {
log.debug “configure()”
configureHealthCheck()
//other devices supported by this DTH in the future
def cmds = zigbee.onOffConfig(0, 120)
def endpointCount = getEndpointCount()
if (endpointCount > 1) {
def endpointId = device.getDataValue("endpointId")
def endpointInt = zigbee.convertHexToInt(endpointId)
for (i in 1..endpointCount - 1) {
def endpointValue = endpointInt + i
cmds += zigbee.configureReporting(zigbee.ONOFF_CLUSTER, 0x0000, 0x10, 0, 120, null, [destEndpoint: endpointValue])
}
} else {
cmds += zigbee.configureReporting(zigbee.ONOFF_CLUSTER, 0x0000, 0x10, 0, 120, null, [destEndpoint: 0xFF])
}
cmds += refresh()
return cmds
}
Important info.
ST will find as Thing and user should install this Device Handler above;
It will recognize and enable the main channel and other 2,3 and 4 as CHILD DEVICES.
However, for better response, user should edit the properties of the device and change again the DHT to ZigBee Multi Switch
Obtained info after all:
Added to this driver version
┌─────────────┬──────────────────────────────────────┐
│ Name │ Zigbee Multi Switch Mc │
│ Version │ 2022-02-15T22:03:26.391426 │
└─────────────┴──────────────────────────────────────┘
- id: "TS0004/_TZ3000_a37eix1s"
deviceLabel: TS0004 Switch
manufacturer: _TZ3000_a37eix1s
model: TS0004
deviceProfileName: four-switch
2 Likes
Found it! But…
Same issues as original Device Handler.
Casually slow or no response channels. Sometimes network connectivity is lost.
Small indicative LEDs are OFF when switch is ACTIVE
Blue when INACTIVE when should be reverse
The “problem solution” at groovy is edit and change again the DHT to ZigBee Multi Switch
Maybe at this last one code will be the answer;
BTW, At Tuya is provided the condition for last state as on, off or last status.
Is that possible at ST?
New info!
Just received another DHT code from manufacter and this one worked fine:
Integrated ZigBee Switch by Woobooung
Tested and runs flawless, correcting LED issue;
What about a new driver, @Mariano_Colmenarejo ? Maybe with extra “last state” options per channel, as Tuya do.
I understand the joke!, but I am not a partner of any manufacturer, I am not going to solve the problems of any of them. I try to buy devices that work with the platform I want to use and if they don’t work I return them, tell them why and and buy another. 
We are in the Beta phase for developers of the new platform.
I am not a developer, I am a user who, while learning to solve his own problems, tries to collaborate, making drivers available to others to migrate the devices that we already have in groovy and that manufacturers or smartthings not going to convert to adriver, since they are out from the market.
I appreciate your trust in me, but with maintaining the drivers that I have shared I already have enough work.
The manufacturers are the ones who decide which platform they want to be on, the tools are available to everyone, surely there are developers here willing to work for those who want to enter this platform.
Of course, if they sell devices to us and don’t spend anything on their integration, much better!!!
The driver has the basic functions, possibly yesterday it didn’t work well because there was a problem in the platform.
The control of the LEDs is done by the device itself.
Status adjustments after a power loss, I don’t know how Tuya does it. I tried it on my devices with the standard method, cluster 0x0006 and attribute 0x4003 and it didn’t work for me, it gave an unsupported attribute error, but on Tuya it works fine.
Solution that I do, I buy a Tuya hub for less of €20 and I configure the switch as I wish, I uninstall it from Tuya and install it in smartthings.
5 Likes
Great!
yes, was a joke!
I understand, just didnt know your kind of “focus” on it, maybe as a future developer for any business or just for fun.
Hope we keep “crossing devices” good for both…
I appreciate and salute a lot your kindness and efforts for fellow community members.
Good tip about Tuya “pre prog”
Gracias hombre!
2 Likes
Hey.
I´ve contacted Zemismart and suggested them to find a good drivers developer before Groovy shutdown as you said!
But was thinking… maybe this one could fit at your new Zigbee Multi Switch Zemismart v2
could we try? if works fine, you keep. Otherwise i return it and you may “clean” again the driver
Added to this version
┌─────────────┬──────────────────────────────────────┐
│ Name │ Zigbee Multi Switch Zemismart v2 │
│ Version │ 2022-02-18T11:11:03.904553 │
└─────────────┴──────────────────────────────────────
- id: "TS0004/_TZ3000_a37eix1s"
deviceLabel: TS0004 Switch
manufacturer: _TZ3000_a37eix1s
model: TS0004
deviceProfileName: four-switch
my friend… i will test it now
Added as THING. Didnt get the driver v2.
I already had it installed; Tried to uninstall to reinstall but got this error message:
Please take discussion of issues with existing drivers to the author thread for that driver (or start a new thread for that driver if one doesn’t already exist).
This topic should only have two posts per device: one requesting the driver and one with a link to the driver thread.
Otherwise it gets too hard for other people to read.
Thank you.
4 Likes
Hi Team,
I have these devices that I am not able to make work with smartthings edge drivers:
-
z-wave switch Inovelli nzw30
→ I tried the generic ST z-wave switch, but it does not pick up and it goes directly to the old DTH. -
zigbee Smartthing Button
→ I tried the generic ST zigbee-button, but it does not pick up and it goes to the old DTH. -
zigbee Ikea Button
→ I tried the generic ST zigbee-button, but it does not pick up and it goes to the old DTH. -
z-wave Aeotec Open/Closed Sensor
→ I tried the generic ST zwave-sensor drivers and I was able to add the device. Here are the logs:
2022-02-24T15:03:00.185709617+00:00 TRACE Z-Wave Sensor Setup driver zwave_sensor with lifecycle handlers:
DeviceLifecycleDispatcher: zwave_sensor
default_handlers:
driverSwitched:
init:
added:
doConfigure:
infoChanged:
child_dispatchers:
DeviceLifecycleDispatcher: zwave_sensor -> zooz 4 in 1 sensor
default_handlers:
child_dispatchers:
DeviceLifecycleDispatcher: zwave_sensor -> Vision motion detector
default_handlers:
doConfigure:
child_dispatchers:
DeviceLifecycleDispatcher: zwave_sensor -> fibaro flood sensor
default_handlers:
doConfigure:
child_dispatchers:
DeviceLifecycleDispatcher: zwave_sensor -> zwave water temp humidity sensor
default_handlers:
child_dispatchers:
DeviceLifecycleDispatcher: zwave_sensor -> glentronics water leak sensor
default_handlers:
added:
child_dispatchers:
DeviceLifecycleDispatcher: zwave_sensor -> homeseer multi sensor
default_handlers:
added:
infoChanged:
init:
child_dispatchers:
DeviceLifecycleDispatcher: zwave_sensor -> fibaro door window sensor
default_handlers:
init:
doConfigure:
added:
infoChanged:
child_dispatchers:
DeviceLifecycleDispatcher: zwave_sensor -> fibaro door window sensor -> fibaro door window sensor 1
default_handlers:
doConfigure:
added:
child_dispatchers:
DeviceLifecycleDispatcher: zwave_sensor -> fibaro door window sensor -> fibaro door window sensor 2
default_handlers:
added:
child_dispatchers:
DeviceLifecycleDispatcher: zwave_sensor -> sensative_strip
default_handlers:
doConfigure:
child_dispatchers:
DeviceLifecycleDispatcher: zwave_sensor -> enerwave_motion_sensor
default_handlers:
doConfigure:
child_dispatchers:
DeviceLifecycleDispatcher: zwave_sensor -> aeotec multisensor
default_handlers:
child_dispatchers:
DeviceLifecycleDispatcher: zwave_sensor -> aeotec multisensor -> aeotec multisensor 6
default_handlers:
child_dispatchers:
DeviceLifecycleDispatcher: zwave_sensor -> aeotec multisensor -> aeotec multisensor 7
default_handlers:
child_dispatchers:
DeviceLifecycleDispatcher: zwave_sensor -> Water Leak Sensor
default_handlers:
child_dispatchers:
2022-02-24T15:03:00.201298950+00:00 TRACE Z-Wave Sensor Setup driver zwave_sensor with Capability handlers:
CapabilityCommandDispatcher: zwave_sensor
default_handlers:
switch:
on
off
colorControl:
setColor
refresh:
refresh
child_dispatchers:
CapabilityCommandDispatcher: zwave_sensor -> zooz 4 in 1 sensor
default_handlers:
child_dispatchers:
CapabilityCommandDispatcher: zwave_sensor -> Vision motion detector
default_handlers:
child_dispatchers:
CapabilityCommandDispatcher: zwave_sensor -> fibaro flood sensor
default_handlers:
child_dispatchers:
CapabilityCommandDispatcher: zwave_sensor -> zwave water temp humidity sensor
default_handlers:
child_dispatchers:
CapabilityCommandDispatcher: zwave_sensor -> glentronics water leak sensor
default_handlers:
child_dispatchers:
CapabilityCommandDispatcher: zwave_sensor -> homeseer multi sensor
default_handlers:
child_dispatchers:
CapabilityCommandDispatcher: zwave_sensor -> fibaro door window sensor
default_handlers:
refresh:
refresh
child_dispatchers:
CapabilityCommandDispatcher: zwave_sensor -> fibaro door window sensor -> fibaro door window sensor 1
default_handlers:
child_dispatchers:
CapabilityCommandDispatcher: zwave_sensor -> fibaro door window sensor -> fibaro door window sensor 2
default_handlers:
child_dispatchers:
CapabilityCommandDispatcher: zwave_sensor -> sensative_strip
default_handlers:
child_dispatchers:
CapabilityCommandDispatcher: zwave_sensor -> enerwave_motion_sensor
default_handlers:
child_dispatchers:
CapabilityCommandDispatcher: zwave_sensor -> aeotec multisensor
default_handlers:
child_dispatchers:
CapabilityCommandDispatcher: zwave_sensor -> aeotec multisensor -> aeotec multisensor 6
default_handlers:
child_dispatchers:
CapabilityCommandDispatcher: zwave_sensor -> aeotec multisensor -> aeotec multisensor 7
default_handlers:
child_dispatchers:
CapabilityCommandDispatcher: zwave_sensor -> Water Leak Sensor
default_handlers:
child_dispatchers:
2022-02-24T15:03:00.219846617+00:00 TRACE Z-Wave Sensor Setup driver zwave_sensor with Z-Wave handlers:
ZwaveDispatcher: zwave_sensor
default_handlers:
BATTERY:
REPORT
SENSOR_MULTILEVEL:
REPORT
SWITCH_COLOR:
REPORT
WAKE_UP:
NOTIFICATION
SWITCH_BINARY:
REPORT
SWITCH_MULTILEVEL:
REPORT
NOTIFICATION:
REPORT
SENSOR_ALARM:
REPORT
BASIC:
REPORT
SENSOR_BINARY:
REPORT
child_dispatchers:
ZwaveDispatcher: zwave_sensor -> zooz 4 in 1 sensor
default_handlers:
NOTIFICATION:
REPORT
SENSOR_MULTILEVEL:
REPORT
child_dispatchers:
ZwaveDispatcher: zwave_sensor -> Vision motion detector
default_handlers:
NOTIFICATION:
REPORT
child_dispatchers:
ZwaveDispatcher: zwave_sensor -> fibaro flood sensor
default_handlers:
SENSOR_BINARY:
REPORT
SENSOR_MULTILEVEL:
REPORT
SENSOR_ALARM:
REPORT
BASIC:
SET
child_dispatchers:
ZwaveDispatcher: zwave_sensor -> zwave water temp humidity sensor
default_handlers:
NOTIFICATION:
REPORT
child_dispatchers:
ZwaveDispatcher: zwave_sensor -> glentronics water leak sensor
default_handlers:
NOTIFICATION:
REPORT
child_dispatchers:
ZwaveDispatcher: zwave_sensor -> homeseer multi sensor
default_handlers:
BASIC:
SET
child_dispatchers:
ZwaveDispatcher: zwave_sensor -> fibaro door window sensor
default_handlers:
CONFIGURATION:
REPORT
NOTIFICATION:
REPORT
child_dispatchers:
ZwaveDispatcher: zwave_sensor -> fibaro door window sensor -> fibaro door window sensor 1
default_handlers:
SENSOR_ALARM:
REPORT
child_dispatchers:
ZwaveDispatcher: zwave_sensor -> fibaro door window sensor -> fibaro door window sensor 2
default_handlers:
NOTIFICATION:
REPORT
child_dispatchers:
ZwaveDispatcher: zwave_sensor -> sensative_strip
default_handlers:
CONFIGURATION:
REPORT
child_dispatchers:
ZwaveDispatcher: zwave_sensor -> enerwave_motion_sensor
default_handlers:
WAKE_UP:
NOTIFICATION
child_dispatchers:
ZwaveDispatcher: zwave_sensor -> aeotec multisensor
default_handlers:
NOTIFICATION:
REPORT
child_dispatchers:
ZwaveDispatcher: zwave_sensor -> aeotec multisensor -> aeotec multisensor 6
default_handlers:
CONFIGURATION:
REPORT
child_dispatchers:
ZwaveDispatcher: zwave_sensor -> aeotec multisensor -> aeotec multisensor 7
default_handlers:
CONFIGURATION:
REPORT
child_dispatchers:
ZwaveDispatcher: zwave_sensor -> Water Leak Sensor
default_handlers:
BASIC:
SET
child_dispatchers:
2022-02-24T15:03:00.301072284+00:00 TRACE Z-Wave Sensor Received event with handler _resync
2022-02-24T15:03:00.319470284+00:00 TRACE Z-Wave Sensor Received event with handler environment_info
2022-02-24T15:03:00.344538950+00:00 TRACE Z-Wave Sensor Found DeviceLifecycleDispatcher handler in zwave_sensor
2022-02-24T15:03:00.350744950+00:00 DEBUG Z-Wave Sensor Aeotec Open/Closed Sensor device thread event handled
2022-02-24T15:03:00.357137284+00:00 TRACE Z-Wave Sensor Received event with handler environment_info
2022-02-24T15:03:00.372506950+00:00 DEBUG Z-Wave Sensor Z-Wave hub node ID environment changed.
2022-02-24T15:03:00.387651617+00:00 TRACE Z-Wave Sensor Received event with handler device_lifecycle
2022-02-24T15:03:00.393968950+00:00 INFO Z-Wave Sensor <ZwaveDevice: b9e6a9b9-b124-489c-9792-de33065b5baf [44] (Aeotec Open/Closed Sensor)> received lifecycle event: added
2022-02-24T15:03:00.405878617+00:00 TRACE Z-Wave Sensor Found DeviceLifecycleDispatcher handler in zwave_sensor
2022-02-24T15:03:00.413714950+00:00 INFO Z-Wave Sensor <ZwaveDevice: b9e6a9b9-b124-489c-9792-de33065b5baf [44] (Aeotec Open/Closed Sensor)> emitting event: {"component_id":"main","attribute_id":"tamper","capability_id":"tamperAlert","state":{"value":"clear"}}
2022-02-24T15:03:00.432577617+00:00 DEBUG Z-Wave Sensor Aeotec Open/Closed Sensor device thread event handled
2022-02-24T15:03:00.438708284+00:00 TRACE Z-Wave Sensor Received event with handler device_lifecycle
2022-02-24T15:03:00.446941284+00:00 INFO Z-Wave Sensor <ZwaveDevice: b9e6a9b9-b124-489c-9792-de33065b5baf [44] (Aeotec Open/Closed Sensor)> received lifecycle event: doConfigure
2022-02-24T15:03:00.467171617+00:00 TRACE Z-Wave Sensor Found DeviceLifecycleDispatcher handler in zwave_sensor
2022-02-24T15:03:00.483584617+00:00 TRACE Z-Wave Sensor Found CapabilityCommandDispatcher handler in zwave_sensor
2022-02-24T15:03:00.499818951+00:00 INFO Z-Wave Sensor <ZwaveDevice: b9e6a9b9-b124-489c-9792-de33065b5baf [44] (Aeotec Open/Closed Sensor)> sending Z-Wave command: {args={}, cmd_class="BATTERY", cmd_id="GET", dst_channels={}, encap="AUTO", payload="", src_channel=0, version=1}
2022-02-24T15:03:00.515207617+00:00 TRACE Z-Wave Sensor Z-Wave command(5aae3718) queued for radio transmission: CC:Battery, CID:0x02
2022-02-24T15:03:00.522132284+00:00 INFO Z-Wave Sensor <ZwaveDevice: b9e6a9b9-b124-489c-9792-de33065b5baf [44] (Aeotec Open/Closed Sensor)> sending Z-Wave command: {args={sensor_type="DOOR_WINDOW"}, cmd_class="SENSOR_BINARY", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x0A", src_channel=0, version=2}
2022-02-24T15:03:00.537483284+00:00 TRACE Z-Wave Sensor Z-Wave command(52c2f830) queued for radio transmission: CC:Sensor Binary, CID:0x02
2022-02-24T15:03:00.543345617+00:00 DEBUG Z-Wave Sensor Aeotec Open/Closed Sensor device thread event handled
2022-02-24T15:03:00.560168951+00:00 DEBUG Z-Wave Sensor Aeotec Open/Closed Sensor device thread event handled
2022-02-24T15:03:00.737160951+00:00 TRACE Z-Wave Sensor Z-Wave command(5aae3718) transmit status: TRANSMIT_COMPLETE_OK
2022-02-24T15:03:00.928716617+00:00 TRACE Z-Wave Sensor Received event with handler device_lifecycle
2022-02-24T15:03:00.969343951+00:00 INFO Z-Wave Sensor <ZwaveDevice: b9e6a9b9-b124-489c-9792-de33065b5baf [44] (Aeotec Open/Closed Sensor)> received lifecycle event: infoChanged
2022-02-24T15:03:00.981357284+00:00 TRACE Z-Wave Sensor Found DeviceLifecycleDispatcher handler in zwave_sensor
2022-02-24T15:03:00.987319617+00:00 DEBUG Z-Wave Sensor Aeotec Open/Closed Sensor device thread event handled
2022-02-24T15:03:01.199150284+00:00 TRACE Z-Wave Sensor Z-Wave command(52c2f830) transmit status: TRANSMIT_COMPLETE_OK
2022-02-24T15:03:01.304545618+00:00 TRACE Z-Wave Sensor Received event with handler unnamed
2022-02-24T15:03:01.314520284+00:00 INFO Z-Wave Sensor <ZwaveDevice: b9e6a9b9-b124-489c-9792-de33065b5baf [44] (Aeotec Open/Closed Sensor)> received Z-Wave command: {args={sensor_value="DETECTED_AN_EVENT"}, cmd_class="SENSOR_BINARY", cmd_id="REPORT", dst_channels={}, encap="S0", payload="\xFF", src_channel=0, version=1}
2022-02-24T15:03:01.330232284+00:00 TRACE Z-Wave Sensor Found ZwaveDispatcher handler in zwave_sensor
2022-02-24T15:03:01.336562951+00:00 WARN Z-Wave Sensor Attempted to generate event for b9e6a9b9-b124-489c-9792-de33065b5baf.main but it does not support capability Water Sensor
2022-02-24T15:03:01.342925284+00:00 TRACE Z-Wave Sensor Found ZwaveDispatcher handler in zwave_sensor
2022-02-24T15:03:01.349649618+00:00 INFO Z-Wave Sensor <ZwaveDevice: b9e6a9b9-b124-489c-9792-de33065b5baf [44] (Aeotec Open/Closed Sensor)> emitting event: {"component_id":"main","attribute_id":"contact","capability_id":"contactSensor","state":{"value":"open"}}
2022-02-24T15:03:01.367467284+00:00 TRACE Z-Wave Sensor Found ZwaveDispatcher handler in zwave_sensor
2022-02-24T15:03:01.375484284+00:00 WARN Z-Wave Sensor Attempted to generate event for b9e6a9b9-b124-489c-9792-de33065b5baf.main but it does not support capability Motion Sensor
2022-02-24T15:03:01.381768284+00:00 TRACE Z-Wave Sensor Found ZwaveDispatcher handler in zwave_sensor
2022-02-24T15:03:01.387753284+00:00 TRACE Z-Wave Sensor Found ZwaveDispatcher handler in zwave_sensor
2022-02-24T15:03:01.393844618+00:00 WARN Z-Wave Sensor Attempted to generate event for b9e6a9b9-b124-489c-9792-de33065b5baf.main but it does not support capability Temperature Alarm
2022-02-24T15:03:01.400266951+00:00 DEBUG Z-Wave Sensor Aeotec Open/Closed Sensor device thread event handled
2022-02-24T15:03:01.743984951+00:00 TRACE Z-Wave Sensor Received event with handler unnamed
2022-02-24T15:03:01.756770951+00:00 INFO Z-Wave Sensor <ZwaveDevice: b9e6a9b9-b124-489c-9792-de33065b5baf [44] (Aeotec Open/Closed Sensor)> received Z-Wave command: {args={battery_level=100}, cmd_class="BATTERY", cmd_id="REPORT", dst_channels={}, encap="S0", payload="\x64\x00", src_channel=0, version=1}
2022-02-24T15:03:01.779505618+00:00 TRACE Z-Wave Sensor Found ZwaveDispatcher handler in zwave_sensor
2022-02-24T15:03:01.786483284+00:00 INFO Z-Wave Sensor <ZwaveDevice: b9e6a9b9-b124-489c-9792-de33065b5baf [44] (Aeotec Open/Closed Sensor)> emitting event: {"component_id":"main","attribute_id":"battery","capability_id":"battery","state":{"value":100}}
2022-02-24T15:03:01.804320618+00:00 DEBUG Z-Wave Sensor Aeotec Open/Closed Sensor device thread event handled
Unfortunately, it does not update the state when I open/close the door. Here are the logs I see:
2022-02-24T17:08:58.886744690+00:00 TRACE Z-Wave Sensor Received event with handler unnamed
2022-02-24T17:08:58.923132023+00:00 INFO Z-Wave Sensor <ZwaveDevice: b9e6a9b9-b124-489c-9792-de33065b5baf [44] (Bedroom Closet Door)> received Z-Wave command: {args={value=255}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="S0", payload="\xFF", src_channel=0, version=1}
2022-02-24T17:08:58.980097357+00:00 DEBUG Z-Wave Sensor Aeotec Open/Closed Sensor device thread event handled
2022-02-24T17:09:04.055340692+00:00 TRACE Z-Wave Sensor Received event with handler unnamed
2022-02-24T17:09:04.079770026+00:00 INFO Z-Wave Sensor <ZwaveDevice: b9e6a9b9-b124-489c-9792-de33065b5baf [44] (Bedroom Closet Door)> received Z-Wave command: {args={value=0}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="S0", payload="\x00", src_channel=0, version=1}
2022-02-24T17:09:04.102034359+00:00 DEBUG Z-Wave Sensor Aeotec Open/Closed Sensor device thread event handled
However, there is no update in the Smarthitng App, neither triggers any routine when i open/clsoe the Door.
I also noticed there is a “Tamper Alert” which I haven’t seen before and I don’t know what is the purpose of it. (this makes me think that perhaps it picked up the wrong driver).
> Does anyone know if these devices are suported or how I can get the right driver for each of them? (it seems to me that I am using quiet standards devices )
Thanks a lot!
Diego
In this thread have a link to my Channel with the ST zigbee Button Mc driver with custom temperature interval reports
2 Likes
Thanks a lot @Mariano_Colmenarejo! This works for the Smartthing Button.
BTW, now my Smartthing motion sensors are being detected as a Button, not a big deal since I change the driver later on and it works fine.
Now I need to sort out the other 3… Step by step
1 Like
It must be because I added a generic fingerprints because someone had pairing problems and was pairing to the DTH.
i will remove it
1 Like