In the SmartThings app under drivers it shows z-wave sensor
Seems to work
Is there a way to test the new Edge drivers on a one hub, but not others that are controlling the same device types using the same custom device handler?
Like many others, I’m using RBoy’s Rental Lock Automator that leverages their “Universal Z-Wave Lock With Alarms” custom device handler across several hubs, using the same Schlage lock model. I see that lock’s fingerprint (003B/634B/504C) is listed in the list of Edge drivers page, but I can’t see how I would test these new Edge drivers on just one of my hubs without removing the custom device handler from my account and impacting the same lock models across all other hubs that are in active use managing guest check in/out user codes.
I’ve seen folks advise commenting out the specific make/model of that lock from my current Groovy device handler, but since I’m using that same make/model of lock across all ST hubs, I’m assuming that would immediately impact all locks using this custom device handler at the same time, which is what I’m specifically trying to avoid so I can logistically manage migrations on a day other than the crazy busy New Year’s Eve holiday.
How are others handling the logistics here?
that method of commenting out the fingerprints has been removed as they continue the process of decommissioning IDE.
Forget it then. I’ll create a whole new ST account, add the hub to that separate account, and test from there with fresh edge drivers. I pity anyone starting in an AirBnB over this holiday.
1 Like
Anyone have any thoughts?
I have a new 2.5 Ecolink zwave garage door tilt sensor. I have added it twice to ST and both times it did not add with an edge driver. I have the ST Z-Wave switch driver and ST z-wave sensor driver installed. Anyone have any thoughts why this tilt sensor device will not pair with an Edge driver?
2 Likes
Thank you so much. That worked this time.
2 Likes