Preview | SmartThings-managed Edge Device Drivers

Thank you for explaining the invitations.

At this moment, is it possible for me to create my own channel, invite other users to it, and have them immediately start using the edge drivers I’ve added to it. (assuming their hub meets the requirements)

I’ll go through the documentation to figure out how to do all of that, but I just want to make sure that I fully understand what’s possible TODAY.


Enrollment in the beta drivers program has worked fine.

I have downloaded the zigbee smoke sensor driver.

I have seen that my Heiman EF-3.0 model is not in the driver fingerprints. There are the N-3.0 and older EM models.
I was using the modified dth with the fingerprint of this model and it works perfectly.

I have tried pairing it in the app and it re-pairs with the modified DTH, not the Beta driver.

I have erased the modified DTH and now it pairs as “thing” it does not pair with the Beta driver.

The beta driver is correctly installed in the hub.

Could the fingerprint file be modified to add the EF-3.0 model?

from the initial driver list, the only compatible device i have and i could try it’s a 5 bucks aqara zigbee water leak sensor…can i pull the trigger??? :slight_smile:

can you please publish any example with Zigbee binding table and settings?


1 Like

Yes, once you generate the invitation, it provides an URL that you can use to enroll your Hub and add the Driver shared in that channel:

Is it any way to create and control child devices?
Everybody is waiting for local execution version of “Zibee Multi Switch”.

1 Like

Where did you see the aqara sensor in the list?

In Edge Drivers they are handled as components of the main device, which is really the way that both the Zigbee and Zwave third-party protocols envision them. Parent/child being established as multiple devices was a smartthings construct, which is why so few of these devices worked out of the box with the platform.

See the following post and the next response to it:

Groovy is on the way out Smartthings Edge is the replacement - #29 by Chares


I don’t, but can’t we use the driver for any generic zigbee water leak sensor?

It’s so bad to hear that I could only make child ‘components’ instead of child ‘devices’.

Let’s say there’s a 2 gang switch, and

gang 1 is hooked up with “living room light” and
gang 2 is hooked up with “hallway light”

If it is implemented as child “components”, there’s no straight way to turn these lights via voice commands, such as “Bixby, turn on the hallway light” or “OK Google, turn on the hallway light”.

This is so bad. I’m using voice assistant A LOT… for turning on/off the lights that are hooked up with multi gang switches.

Until this problem is solved, I should be using groovy DTHs for Zigbee Multi Switches.

Are you sure? That’s not how it works on most other platforms, where you can activate individual end points without any issue.

I’m not saying that smartthings did it correctly, but just being done with endpoints shouldn’t be an issue under the protocol.

Using the smartthings example of a power strip with individually addressable sockets, I would expect Alexa to be able to turn on each one individually.

But again, I don’t know for sure how it was implemented in the new smartthings architecture.

@psbarrett @Automated_House

1 Like

As far as i understand no. It can only be used with the device fingerprints currently found in each beta driver.

Please someone correct me if am wrong.

Child component is like the architecture, for example, you can see in the Ikea 5 buttons.
Each of the 5 button is created as child ‘component’, and these components are rendered in one detailView panel altogether.

You cannot set individual names for these components, as you can’t do with Ikea 5 buttons.

In the same manner, if the multi gang switches are created with child ‘components’,
there’s no way to name those individual child component switches, like ‘hallway light’, ‘livingroom light’, which means, there’s no way to voice control those child switches.

In the addChildDevice() function in groovy DTH, there’s a argument named ‘iscomponent’ to choose whether the child is created as component or separate child device.
It seems that Edge Device Drivers don’t have any method to create separate child device, and that could be problem using voice assistants.


Well that sucks. :disappointed_relieved:

But I find it hard to believe that the multi component device manufacturers like @TheSmartestHouse and @Eric_Inovelli would find it acceptable if their multi button devices were not controllable by Alexa on a smartthings platform. And so far they’ve sounded pretty positive about the new system. Hmmmm….:thinking:

@erocm1231 , do you know if the components of a multi button device like the Inovelli Fan and Light Switch using an edge driver will be exposed to the voice assistants like Alexa and Bixby?

1 Like

@jody.albritton can you shed some light on this?

1 Like

@jody.albritton @smartthings can you shed some light on this?

If child “components” switches could be showing up as “separate switches” in Alexa or Google Assistant, the voice controlling might be possible, because, you could set the names of the devices in Alexa or Google Home app.

However, I use Samsung’s Bixby quite a lot, because it supports a lot of SmartThings capabilities so I could control all the details of the devices connected to SmartThings meticulously. I have 2 of Galaxy Home minis in my home.

Unlike Alexa or Google Assistant, which provides their own platform interfaces to rename or rearrange devices, Bixby is directly connected to SmartThings, so there would be no possible solution for Bixby.


@Augusto_Geovanny_Mar @Andremain

At present, you can’t switch non-edge drivers to use an edge driver, it will need to be joined with an edge driver fingerprint present. Of course, there’s no guarantee that the generic support at the base of the “category drivers” will support a device like the Aqara without some special support (I have no experience with this particular device but if it is like some of the other Xiaomi devices which are not Zigbee certified, they have some issues that won’t be magically fixed by using edge drivers, so YMMV).

If you or someone else wants to start playing around with that, the source for the drivers are available which you can start with as a base for development as you see fit in keeping with the license. SmartThingsCommunity/SmartThingsEdgeDrivers - drivers/SmartThings/zigbee-water-leak-sensor

1 Like

@SmartThings Any chance we will see more drivers for the beta? This is too limiting.

1 Like

Aren’t there simply two problems with component devices?

  1. Although components have names and labels, just the same as devices, there is no way to set the component labels dynamically at the ST end, and as yet no way to directly refer to components without going via the device itself. It may be that the need to support legacy devices has prevented this.

  2. The components are neither being mapped to multi-endpoint devices on the voice assistants, if indeed they have such a concept, and nor are they being mapped to individual devices. It is not clear what the obstruction is to one of these happening.

It is not that child devices are really necessary, it is just that components still haven’t effectively replaced them.

1 Like