Post Requests for Zigbee Edge Drivers Here (community-created)

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:

image

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.

@Mariano_Colmenarejo @niquini @Coelhorj

4 Likes

Hi Team,

I have these devices that I am not able to make work with smartthings edge drivers:

  1. 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.

  2. zigbee Smartthing Button
    → I tried the generic ST zigbee-button, but it does not pick up and it goes to the old DTH.

  3. zigbee Ikea Button
    → I tried the generic ST zigbee-button, but it does not pick up and it goes to the old DTH.

  4. 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 :wink: )

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 :slight_smile:

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

Hi guys,

I have a Zigbee Smart Knob I want to use as a on/off switch as well as a dimmer.

I need a driver for Smartthings as I don’t have a Zigbee hub. Would any of you be able to help please?

Brand Name: Aubess
Data * application: 43

  • endpointId: 01
  • manufacturer: _TZ3000_4fjiwweb
  • model: TS004F
  • zigbeeNodeType: SLEEPY_END_DEVICE
    Raw Description 01 0104 0104 01 06 0000 0001 0003 0004 0006 1000 08 0019 000A 0003 0004 0005 0006 0008 1000

Link to the Device on AliExpress: Tuya ZigBee Smart Knob Button Switch Wireless Scene Controller Smart Life App Smart Home Automation Scenario For Tuya Devices |Smart Home Control| - AliExpress

Thanks in advance!
Regards,
Riaan

This should help. The exact description may be out of date, but the basic process is the same for today’s Groovy DTHs.(Edge Drivers, of course, are installed differently.)

[OBSOLETE] FAQ: An Overview of Using Custom Code in SmartThings (SmartThings Classic, Groovy Code)

1 Like

Thanks, the things you quoted are the ones I figured out so far :slight_smile:
But I learned many more tricks from the topic provided! It’s like a nice basic summary of getting started with device handlers and apps.

1 Like

Need an Edge Driver for ZWave Locks - Yale specifically but a universal would be fine.

What’s the hold up on this? A zigbee driver exists.

1 Like

I’m not really sure what you’re basing this statement on - perhaps you could provide a source if you believe this to be true. There’s nothing stopping someone from writing a custom edge driver for a z-wave device of any type right now.

1 Like

I would think it’s just a matter of someone making one, but I’m not an expert.

It does seem that Z-Wave drivers are lagging behind.

I wonder if that is a result of Z-Wave seemingly being left out of Matter.

I was going by what staff have told me previously regarding Zwave security and edge drivers in the current Beta, but I may have misunderstood. I’ve withdrawn my post above.

Do you know of anyone who has a working edge driver for a Z wave lock?

Yes. My Kwikset 910 is unlocking and locking happily on an edge driver that I threw together in five minutes this morning. ST has defined the default z-wave behaviors for the lock capability, so the most basic shell of a driver that does nothing but declare capabilities is enough to have a working z-wave lock driver.

Thank you.

1 Like

Awesome, thanks for the correction! :sunglasses:

1 Like

That model doesn’t support S2 security, right? The S2 process is a little different for locks than other device classes, I’m just wondering if that has anything to do with the holdup on the official driver. Or if it’s just a case of too much to do and not enough time to do it in. :thinking:

Nayelz is going to track the official version for us, I’m sure they will have one eventually.

It doesn’t, and I don’t have a newer S2 model to test on. I can’t say I’m up to speed on the specifics of S2 Access Control vs the implementation for other devices, but S2 works on other devices and non-S2 locks work, so I currently have no reason to doubt.

I think it’s just too much to do, and locks being toward the end of the list. There are signs that development is still happening on them - the default handler file for the lockCodes capability is date stamped 1/26, the same day that the latest Lua libraries were posted. The lock default handler file also is one of the more recently updated. No new ST drivers have been posted since 1/26, so we’re probably due for some more to drop.

Keep calm… They’re coming.

1 Like

would you care to share your driver?

1 Like