(EDGE Driver-Mc): Zigbee Drivers for Motion, Open/Close, Moisture, Smoke-Co Sensors and others Devices

ST motion and plug are still pairing with stock dth.
Ecolink pairs and works with exception of battery data.
TS0001 paired as a “thing” as it did originally and has to change to ZigBee switch in IDE and did work as intended on the stock dth.

Mmm…I haven’t seen comments about issues pairing Sonoff devices from other devs, but it could be the case for the _TX3000_hktqahrq manufacturer
But @Paul_Oliver, please verify the fingerprint values of both devices in the Hub events when the device is paired.

  1. Got to the IDE and select “My Hubs”
  2. Tap on “List Events” (it is the penultimate option in the table)
  3. The paint event is before the “deviceAdd” event. Eg.

Hi @Mariano_Colmenarejo Thanks for coming back to me on this.

I’ve followed your instructions, but it’s still not connecting beyond “Checking…” stage.
Any other suggestions I can try?

I notice in the Settings that there is an option to change the icon. Could you please add water valve to these options too?

Thank you so much for all your support with this.

@Hendo25,

I think not Will work, does not have cluster 0006 and have tuya cluster EF00.

Works with zigbee switch DTH?

Is this what you are looking for:

zbjoin: {“dni”:“1ED7”,“d”:“847127FFFE281752”,“capabilities”:“8E”,“endpoints”:[{“simple”:“01 0104 0100 01 06 0000 0003 0004 0005 0006 1000 01 1000”,“application”:null,“manufacturer”:“SONOFF”,“model”:“01MINIZB”},{“simple”:“F2 A1E0 0061 01 00 01 0021”,“application”:null,“manufacturer”:null,“model”:null}],“parent”:0,“joinType”:1,“joinDurationMs”:11029,“joinAttempts”:1}

Name Value
archivable true
commandId 0
date 2021-11-03 3:01:06.000 PM EDT (2021-11-03T19:01:06.000Z)
description zbjoin: {“dni”:“1ED7”,“d”:“847127FFFE281752”,“capabilities”:“8E”,“endpoints”:[{“simple”:“01 0104 0100 01 06 0000 0003 0004 0005 0006 1000 01 1000”,“application”:null,“manufacturer”:“SONOFF”,“model”:“01MINIZB”},{“simple”:“F2 A1E0 0061 01 00 01 0021”,“application”:null,“manufacturer”:null,“model”:null}],“parent”:0,“joinType”:1,“joinDurationMs”:11029,“joinAttempts”:1}
displayed false
eventSource HUB
hubId db86d2e4-3209-409c-b36b-f613d7b32bcb
id 6add9514-021b-48ea-97dd-fc9f9d6fd803
isStateChange false
isVirtualHub false
linkText Home Hub
locationId f5ed0b5a-6249-4e72-bea7-2736f235e817
name zbjoin: {“dni”:“1ED7”,“d”:“847127FFFE281752”,“capabilities”:“8E”,“endpoints”:[{“simple”:"01 0104 010
rawDescription
translatable false
unixTime 1635966066000
value zbjoin: {“dni”:“1ED7”,“d”:“847127FFFE281752”,“capabilities”:“8E”,“endpoints”:[{“simple”:“01 0104 0100 01 06 0000 0003 0004 0005 0006 1000 01 1000”,“application”:null,“manufacturer”:“SONOFF”,“model”:“01MINIZB”},{“simple”:“F2 A1E0 0061 01 00 01 0021”,“application”:null,“manufacturer”:null,“model”:null}],“parent”:0,“joinType”:1,“joinDurationMs”:11029,“joinAttempts”:1}
viewed false

Hi @Mariano_Colmenarejo - ok, thank you.

I have not got this working with any DTH yet.

I have reviewed this thread - How to connect Tuya compatible 2 gangs Zigbee Switch module
and
[Device Handler] Moes 2 and 3 gang Zigbee wall switch ( cluster EF00) - #6 by johnconstantelo

and tried different DTH. Not working.

I can see this device works in Home Assistant, but nothing for Smartthings yet.

Thank you for trying.

1 Like

@nayelyz,
I do not quite understand what is happening so there are more problems to match the drives when the devices have full or generic fingerprints in DTH Stokcs.

The ST motion sensor motionv5 is in the dth stock smartsense motion sensor

fingerprint inClusters: "0000,0001,0003,000F,0020,0402,0500", outClusters: "0019", manufacturer: "SmartThings", model: "motionv5", deviceJoinName: "Motion Sensor", mnmn: "SmartThings", vid: "SmartThings-smartthings-SmartSense_Motion_Sensor"

I can’t see the ST plug outlet4 on the zigbee switch or zigbee switch power

Has something changed in the Hub?

Did you configure these values in your driver’s fingerprints, @Mariano_Colmenarejo? Along with the uppercase manufacturer?

1 Like

Yes, this data

  - id: "SONOFF/01MINIZB"
    deviceLabel: SONOFF Switch
    manufacturer: SONOFF
    model: 01MINIZB
    deviceProfileName: single-switch

But don’t they have priority to match drivers over stock DTHs?

Yes, that’s correct, but if they’re paired to stock DTHs, it means the matching fingerprint is not found in any driver installed. Let’s review the things we need to check:

  • The fingerprint must match the one in the device’s DTH, if there’s no DTH, then you need to look at the Hub events (instructions here).
  • The driver must be assigned again to the channel when it’s updated (package and publish). Remember that for the users invited, updates might take a few hours to be effective.
  • If you add more fingerprints to your driver, and only some of them are failing, then the device has a specific issue
  • If all new fingerprints are not working (even after the automatic update), then, something might be wrong with the driver’s update.

@Mariano_Colmenarejo and @nayelyz

I just got the Sonoff Mini to pare as a driver using the “ZigBee Switch mc” driver, but it is not functioning.

The app shows it stuck in the ON position, but the light connected to it is off.

If I operate the dumb switch connected to the Sonoff Mini the light goes on and off and the app shows the correct status. After the manual switch operation the app can be used for a few cycles before it gets stuck in the ON position with the light off. In addition the icon does not change.

If tried uninstalling and reparing the mini, rebooting the hub, closing the app, clearing the cache, force stopping the app. I did each of the above multiple times and nothing helps.

I also tried to operate it via an Automation and that did not work.

The only thing that works is cycling the dumb switch, but that only fixes the app for 1 to 3 cycles.

EDIT: After several hours the icon changed to a bulb, but the switch still can NOT be operated from the app or automations.

@Mariano_Colmenarejo, @nayelyz

The Tuya TZ3000 switch pared as a driver on the 1st try using the “ZigBee Switch mc” driver. I was able to change the icon and it works as expected.

Thanks again for your help.

1 Like

I think this is very important to keep in mind for users who are already using a driver and have requested or want to use other devices added later to that driver.

  • Once published, they have to wait for the automatic driver update for several hours.
  • If you want it to be faster, you should uninstall the hub driver and reinstall the new version.
    This implies not having devices paired to the driver to uninstall it.

You can check the version of the driver (Date and time of creation of the driver) in details of the hub, menu driver, select a driver

The Sonoff Mini seems to be working as expected this morning (12 hrs after the change) and the icon change is sticking.

Thanks again

EDIT: I spoke to soon. It is stuck in the on position again.

So the TS0001 is now working correctly, however, the ewelink switch toggles on/off but only after refreshing the device page…otherwise the icon sticks at on or off and spins.
Still no pairiing with ST Outlet or ST v2 motion sensor

Glad to hear it!

however, the ewelink switch toggles on/off but only after refreshing the device page…otherwise the icon sticks at on or off and spins.

Try following it, there are times that they do not pair well.
Install the zigbee switch Mc (OLD) driver, it does not have custom capabilities.
In the switch, details, menu driver, choose another driver.
Choose the one that shows you, it will appear zigbee switch Mc (OLD)
click on use this driver.

Exit the app, clear the cache and reopen to see if that works.

If it works fine, and you want to, reinstall the zigbee switch Mc driver following the same steps.

I’m going to add the fingerprints from the stock dht, but smartthings should fix that if there is a driver with the fingerprints, choose the driver and not the DTH

@troy_owens,

Added theses fingerprints for zigbee motion sensor MC and zigbee switch power Mc

zigbeeGeneric:
  - id: "outletv4"
    deviceLabel: "Zigbee SmartTings outletv4"
    zigbeeProfiles:
      - 0x0104
    deviceIdentifiers:
      - 0x0002
    clusters:
      server:
        - 0x0000
        - 0x0003
        - 0x0004
        - 0x0005
        - 0x0006
        - 0x0009
        - 0x000F
        - 0x0B04
      client:
        - 0x0019
    deviceProfileName: power-meter
zigbeeGeneric:
  - id: "motionv5"
    deviceLabel: "Zigbee SmartTings motionv5"
    zigbeeProfiles:
      - 0x0104
    deviceIdentifiers:
      - 0x0402
    clusters:
      server:
        - 0x0000
        - 0x0001
        - 0x0003
        - 0x000F
        - 0x0020
        - 0x0402
        - 0x0500
      client:
        - 0x0019
    deviceProfileName: motion-temp-battery

Tried what you suggested… Same behavior