A post was split to a new topic: [Edge drivers] Issue with Z-Wave Lock driver (Schlage BE469ZP)
Just to make it clear, all of the Edge drivers here (on the channel) are stock/standard drivers, meaning we donāt have to install ANY of those prior to 30/09 transition, right?
The drivers in the invitation shared above, belong to the beta channel. If your devices use stock DTH by default (this means that they get paired with them and you didnāt select that specific device type in the IDE), they will be migrated by the engineering team.
Hereās more info about the devicesā transition, there are different options depending on each deviceās situation.
2 Likes
A post was split to a new topic: [Edge drivers] Cannot enroll to SmartThings Beta Channel
Iāve confirmed one of my monoprice multi-sensors is not covered by the z-wave sensor edge driver fingerprint set. On installation, it continues to default to the āAEON Multipurpose Sensorā DTH - which works fine.
Is this the right thread to request adding support for the device?
Its fingerprint info is: zw:S type:2001 mfr:0109 prod:2002 model:0203 ver:4.84 zwv:3.52 lib:06 cc:71,85,80,72,30,86,31,70,84
thanks
@georgeh Some of monoprice devices are covered by stock driver, some of them have wrong profile and some are not. Recessed door/window sensor works fine, Garage door (tilt) sensor has temperature capability in itās profile, even that device doesnāt. 4in1 works fine.
It could be that they are using generic profiles
None of monoprice devices have settings in stock driver(s).
I am pretty sure that @RBoy will come up with custom drivers soon
Do you know which stock edge driver should be used for the monoprice recessed door/window sensor? I tried disconnecting/reconnecting and it did not seem to work. Do I need to install oe of the ZmartThings Edge drivers?
thanks!
1 Like
Hi, @georgeh
I cannot find the DTH with the name āAEON Multipurpose Sensorā, thereās only one called āAeon Multisensorā.
Is that the value you see assigned in the field ātypeā in the IDE? I mean this one:
If so, it would seem you have a custom DTH registered there, can you check, please?
Also, is your device similar to this one? The product type ID (2002) is the same but not the model (0203).
Correct (my bad, a typo), IDE type field is indeed āAeon Multisensorā.
I do not think this is a custom DTH, rather one of the available stock DTHs. (I rechecked my IDE and no corresponding custom driver exists.)
The actual physical device is cosmetically similar to the one you referenced, but they do appear to be different models. I have a several of the Monoprice multisensors; this particular one (0203) and some of their model 0205 ā but none of the model 0202. I know 0203 behaves a bit differently from the 0205 modelā¦ my 0205 model currently uses the stock DTH āZ-Wave Plus Motion/Temp Sensorā, but that did not work properly on the 0203. The Aeon Multisensor DTH does seem to work fine for me on my 0203.
For the Monoprice 15268 (Vision) recessed door/window sensor (0109-2022-2201) SmartThings assigned the ācontact-battery-tamperalertā Edge driver from the āSmartThings Drivers (Beta)ā channel without any problem. Similarly the Monoprice 15270 Door/Window sensor (0109-2001-0106) got the ābase-contactā driver from the same channel.
I donāt see this driver in the SmartThings Drivers (Beta) channel. The only contact there is zigbee. Anyway, the Z-wave sensor @milandjurovic71 pointed me to seems to work. Thanks.
Indeed - mine was not. But since a working stock DTH for it does exist I am hoping that ST will add support to their generic edge driver per my request.
The driverId is d58d8432-ea22-4d38-8300-2bd75fdf1358 - itās āZ-Wave Sensorā in the āSmartThings Drivers (Beta)ā channel. Sorry about my confusing suggestion before - I have a lot to learn.
1 Like
Hi, @georgeh
I am Andres, a member of the Developr Support team.
We are taking a look into this. We will keep you updated.
Thanks. Just an update FYI, Iāve recently hacked a copy of the Zooz 4-in-1 edge sensor and am now using it on the device (by adding the devicesā fingerprints to a local copy of the driver I tweaked).
I tried using the AEON Multisensor in same way, but it did not behave well (motion inactive delays on the order of 20minutes), but the Zooz seems to work well (other than a bogus luminance tile since that feature is not supported on the monoprice device). It would still be nice to have a viable stock edge driver though.
Hi - Iām an end user, not a developer, trying to find what will be an officially supported Edge driver that can be used instead of the bjpierron Simulated Alexa switch that will be going away with the transition. I have installed the Smartthings Drivers (Beta) channel as well as the Virtual Switch driver, but I cannot figure out how to create a device with the driver. Would appreciate direction f someone knows what to do. Also, will these drivers automatically transition to GA versions from Beta or will I have to to do something to change when they become āofficialā, Thanks!
There are several community-Created edge drivers for virtual devices that work well to trigger Alexa routines and to otherwise substitute for the bjPierron DTH.
You can find them on the quick browse lists in the community-created wiki and look for the list for virtual devices.
If you have any further questions, just ask in the author thread for the edge driver you are working with. 
Thanks for the quick reply. I have seen those but based on the channel description, it seemed that the SmartThings Drivers (Beta) channel would be āofficiallyā supported by Smartthings. Is that Virtual Switch not desirable?
It depends on what you want to use it for.
@bjpierron initially created that virtual device DTH so that it would be BOTH a sensor and a switch. When you turn on the switch, the sensor looks like it opened. Turn off the switch, the sensor looks like it closed.
That was important because at the present time you cannot trigger an Alexa routine from a switch of any kind, virtual or physical. You can only trigger from a sensor or a lock. So people who wanted to use the virtual device to trigger an Alexa routine needed the @bjpierron version.
The community-created virtual devices have that same capability. Itās very easy to turn them on and off by voice or from an automation, but they also have the sensor capability so that they can trigger an Alexa routine.
If you donāt need the Alexa routine trigger functionality, you just need a virtual switch that turns on and off, you can use the official version. So itās up to you.