Is this what are you looking for?
1 Like
exact, but I want to be able to use this in automations running local. If I use this time, it goes to the cloud
1 Like
I’m already checking with the corresponding team if they can provide more info about it. I’ll keep you updated.
Update:
So, the team mentioned this will be definitely supported local and they’re already working on that but there’s no ETA yet.
CC @niquini
4 Likes
Perfect. Thanks!
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
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.