Post Requests for Edge Drivers Here (community-created)

A post was merged into an existing topic: [ST Edge] Personal Tuya Devices - Generic EF00 Device

Request to locate or create Edge driver for: Quirky Tripper, an old Wink contact sensor.

I have attempted to find an edge driver for many months, and finally got impatient and tried to do a manual transition from DTH, hoping it would pair with an existing stock or community Edge driver, but when I added it is joined as a “Zigbee Thing” using Mariano’s Thing driver. The only other available edge driver option is the stock ST Thing driver.

Below is the info from @Mariano_Colmenarejo Thing edge driver -


I was previously using Mitch Pond’s DTH, with this info from the IDE -


I have a total of four Trippers, which I use on my Windows for home security, thus why I previously attempted to wait for an auto-transition by ST. But now that I am unable to restore the prior DTH I have a strong desire to quickly reenable their functionality, if possible, or replace them with new compatible contact sensors.

Thank you to any and all that can offer suggestions for how to enroll and enable my (old) Wink Quirky Tripper sensors!

Hi @manuelceja

Added to this driver version

───────────────────────────────────────────────────
 Name         Zigbee Contact Mc
 Version      2023-01-07T19:43:32.386865249
───────────────────────────────────────────────────
- id: "Sercomm Corp./Tripper"
    deviceLabel: Sercomm Open/Closed Sensor
    manufacturer: Sercomm Corp.
    model: Tripper
    deviceProfileName: contact-battery-profile
2 Likes

@Mariano_Colmenarejo - Thank you, very much!

I added my remaining Trippers, but they joined as Things - It appears that the problem is that updated driver has not propagated to my hub, it shows that the driver version is still the prior one: “2022-1229T10:05:06….”.

After I noticed this on the first additional sensor, I reset the hub, and then tried adding the remaining sensors, plus re-adding the prior ones, but the hub still has the prior version of the driver, even after rebooting it. :frowning:

I will check periodically to see if the driver version has been added. When it has, or if it does not within 12 hrs, I will report back here. That said, I am optimistic that they will work as intended once the driver updates on my hub.

Thanks again!!!

:slight_smile:

3 Likes

Request for zigbee blind edge driver. Cold someone help please?

Thanks a lot!

Try @w35l3y driver for TUYA cluster EF00. [ST Edge] Personal Tuya Devices - Generic EF00 Device

1 Like

@Mariano_Colmenarejo - Success! (mostly!?)

When I replied earlier I had failed to add the ‘Zigbee Contact Mc’ driver; that is the reason the Trippers did not onboard correctly when I first tried. :man_facepalming:t4:. I have now corrected that.

I installed the needed driver from your channel and then changed the driver for the Trippers. Two out of the four began to register and work a few moments after the driver change - Yay!

Unfortunately the other two show that they are ‘Connected’ in the app, but the details pane show an Exclamation mark inside of a circle in the Contact Sensor box. I have put new batteries in them with no change in their status, they are not registering triggers (sensor trips).

It could be that these two devices have gone faulty, they are all about 11-13 years old! Or it could be that it is related to them being from two different generations :thinking: Quirky/GE made some (small) hardware change at some point, between the pairs that I have. Although they all previously worked with the DTH. :man_shrugging:t4:

I will keep troubleshooting: delete, re-pair, trigger, etc and hope for the best!

Meanwhile, I now have at least the two that now function as they should - Thank you!!!

1 Like

I need three separate drivers, thank you in advance!:

  1. Monoprice RGBW zwave+ bulbs #27482 (manual)
  2. GoControl zwave bulbs LB60Z-1 (manual)
  3. GoControl virtual 3-way switch WT00Z5-1 (manual) - this switch allows direct pairing to zwave things (the #2 bulbs above in my case)

I’ve tried other RGBW drivers for #1, but none of them take when including.

Is anyone working on Edge drivers for the CoopBoss by John Rucker? (see CoopBoss-H3Vx and CoopBoss is certified! Chicken coop door controller for SmartThings)

John had gotten the coop boss “Works with SmartThings” certified and did a great job with development and manufacturing it with a small-batch manufacturer. Sad it will stop working soon. If you have a knack for developing - I’d even be happy to contribute some $$ to retain some basic functionality post-groovy. PM me if you have one and are in the same boat, or are interested in writing a driver for it!

I may be mistaken, but I believe coopboss requires not just a device type handler, but also a smartapp.

If so, that’s a whole different kind of project. There are no “edge apps” and it’s not as simple as just writing into a new language. Edge drivers run on your own hub, but for the second generation smartapps (which some people now call “endpoint apps“) a new way to host it and authorize it. It can certainly be done, but it is more complex, so rather than including that request in this thread, I suggest you start a new thread, may be something as simple as “Coopboss after Groovy?” And see if you can get some people interested in coming up with a new version for the new architecture. :thinking:

1 Like

Ah yes, you are right John. Will do - thanks! Edit: For anyone who is seeing this thread, I’ve created a new post, as John suggested - right here.

Looking for an Edge driver for a UEI XHS1-UE Xfinity Motion sensor found here.

I can get it recognized by adding the fingerprint info to a custom copy of the Zigbee Motion Driver but the device goes into an offline state after about 30 minutes. Only way to get it back online is to remove/reinstall the batteries. I believe this was a problem with the DTH drivers as well and had something to do with the device’s firmware. Hoping this can be overcome now since these sensors have a greater range than your typical mini-motion sensors.

Hi @unforgiven73

Added to this driver version

───────────────────────────────────────────────────
 Name         Zigbee Motion Sensor Mc
 Version      2023-01-09T20:11:49.098849587        
───────────────────────────────────────────────────
- id: "Universal Electronics/URC4470BC0-X-R"
    deviceLabel: Motion Sensor
    manufacturer: Universal Electronics Inc
    model: URC4470BC0-X-R
    deviceProfileName: motion-temp-battery
1 Like

Thanks when is this driver expected to be ready

Hi @Janardhan_Reddy
I do not understand what you mean.
This device that the post you replied to points to works with the driver since September 11, 2022

Do you mean this device or another?

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Contact Mc                    │
│ Version     │ 2022-09-11T17:24:43.117613104        │
└─────────────┴──────────────────────────────────────┘
  - id: "Visonic/MCT-370 SMA"
    deviceLabel: Tyco Open/Closed Sensor
    manufacturer: Visonic
    model: MCT-370 SMA
    deviceProfileName: contact-profile

I have a Tyco sensor which no longer reports correct temperature. It does let me know when it’s open or closed.

Can anyone point me to a new file so I can add it to smart app In Smartthings. Thx.

Are there any edge drivers for the first alert smoke detector and carbon monoxide detector known as “ZCOMBO”?

Any updates on the driver for this?
Seems some confuse the HS-FS100-W (water) with the light sensor HS-FS100-L

1 Like

The stock Edge Zwave Smoke Alarm driver works fine for these. I have several using it today.

2 Likes

Any chance of a driver for the Tuya zy-m100 presence sensor?