I went ahead and installed 2 of them and use my Sonos to announce when the doors open. Works perfectly. The custom device worked without a hiccup. Instantly paired as the correct device. Thanks for the advice. So I got 8 sensors for $5.00 a piece. I couldn’t be happier.
I have these on my V2 hub and they work without a problem.
Just connected one to my ST v2 hub, and one to my Wink hub. I can see the firmware version in the Wink app, where can I see the firmware version in SmartThings of the tripper? I’m trying to determine if I need to disconnect all these trippers from my ST hub back to wink temporarily to get the upgrade or if they already have latest firmware.
Is there a way to tell without having to remove these from my ST hub and connect them to Wink?
Also, I assume the moment these connect to Wink, they upgrade firmware? If not, they may already be on latest tripper 5.1b21 as that’s what it showed in Wink the moment I connected one.
Sorry for the stupid question but is there a link to the latest version of the code that everybody is using for this custom device type as I couldn’t find any links in the OP of this thread and searching through the thread posts I noticed several links to code. I’m just looking for the latest and greatest that everyone is using! 
Also as a quick question, I noticed there are some complaints on Amazon about the range on these being horrible so has anyone experienced any issues with putting the sensors on a different floor other than the hub?
Just purchased 2 of these and pretty excited to see them work since they are at a fantastic price compared to the rest of the door/window sensors!
Thanks!
I haven’t had any range issues using this on different floors. My hub is in my basement and I use one of these on the second floor. I have a pretty strong ZigBee mesh with several repeaters (lights, outlets). A lot of it would depend on radio interference and building materials in your house. The usual complaint is about battery life, since these use a smaller battery.
1 Like
Your awesome, thanks @mitchp!
It would be awesome @Stanislav if you can update the OP with the link @mitchp mentioned since I actually came to this thread from Amazon since these trippers are one of the, if not thee, cheapest route to go for door/window contact sensors and from reading the product comments, it was mentioned they aren’t 100% compatible with SmartThings unless using a custom device type so I searched and arrived here.
So an update after getting the devices and adding them to ST, I have the following feedback regarding these devices (and most of it is similar to issues others have had)…
- Using the code that @mitchp provided, I was easily able to add a new Device Type
- However when clicking the Save button, I noticed an infinite spinning loading gif next to the device type name so I opened up the Chrome dev tools and the console log indicated a JS registerType or registrationType undefined error (can’t remember the actual name sorry)
- I then proceeded to click Publish and set the Location
- Then clicked the My Device Types (even after warnings that it’s not saved even though it wouldn’t let me save it haha) and noticed it appeared but without a description so right away that might be a good indication it was corrupted but it existed so I proceeded to the pairing
- Tried pairing following the instructions, and like already mentioned in a post above, nothing happened or showed up in the list so using the above advice I quit the app and reopened it
- Then went to the Marketplace section of the app (star icon at bottom-right of the bottom toolbar) and went to Not Yet Configured and noticed, like mentioned in a post above, it showed up as Thing so I knew something was definitely wrong at this point
- Went back to the dev site, removed both of the Thing devices, removed the device type that I added earlier from @mitchp code to refresh everything
- Now I started from scratch again and got the same JS error but tried going back into the device following multiple actions/clicks I can’t remember haha and got it to finally save without error. Published again and set the location.
- Followed the instructions to unpair the devices (not sure if needed) which involved opening the devices, holding a button, taking battery out, then inserting the battery, then releasing the button
- After releasing the button which then put the device into repairing mode, I set ST to look for devices and this time it showed correctly for the device type that @mitchp provided
From there, everything worked and it’s already working for a lightbulb in my system! I didn’t try adding the device type in other browsers such as IE, Firefox, Safari, etc, etc.
Hope this helps anyone else!
Those complaints are from people that refuse to buy what is needed. you can not use just the hub and the door sensors and get unlimited range. you need repeaters in the house and the only things that are repeaters are devices that have AC mains power. SmartThings wall plug wart switches, some of the zigbee lightbulbs that support ZHA completely etc…
The best repeaters are the Smartthings brand single outlet relays as they are brand agnostic and repeat everything.
1 Like
Ahh thanks for the update!
New guy here…
I saved the code, can you give me a walk thru on how to add this please?
Thank you!
Hi @Daniel1 - to get an unofficial device on ST the community often creates custom “device types”. That is what @mitchp posted a link to. Here is a guide on how to set it up on your system: FAQ: An Overview of Using Custom Code in SmartThings
Hey @Daniel1, I don’t know if you got a chance to take a look at the troubleshooting steps I followed but I’ll provide my post below again if you didn’t already read it so that it may initially help you out. If it doesn’t and by “walk thru” you are referring to getting these tripper devices recognized by the SmartThings hub then let me know and I can provide more basic steps for you to follow 1-by-1.
If you do need that just please let me know what you have already tried though (aka what you mean by you “saved the code”) and etc as I’m assuming at this point you might have already went to the link that @dc1515 provided and took care of adding/saving/publishing the new device type in the developer graph api site and at this point you are just looking to get the trippers recognized but we won’t know unless you explain a tiny bit more what you’ve already done! 
I was able to get 2 Quirky Trippers to “just work” by adding a new device type in the IDE using “from code”, pasting the latest code from @mitchp. Thank you!
Yes… Thanks for all of the help. I got them working great.
Here’s another question though;
Do these use more battery power then other devices?
nope. but they have the smallest battery of all devices. so expect to replace the coin cells every 2-3 months.
Oh and the batteries that come in them new are 1/2 dead already. Quirky bought the cheapest china coin cells they could find.
I noticed that the batteries were way down in just 10 days. I think I read somewhere that these had good battery life… and then I remembered that was someone talking about Aeon’s devices 
.
If you use the batteries that come in the box, nope. Quirky put in really cheap no brand china batteries. Every single one with the battery in the box lasted from 5 days to 15 days. brand new energizer’s last what seems to be about 60 days on heavy use doors and 120 days on seldom used doors.
Anyone want to buy two Quirky door sensors?
You wont be able to sell them for much, I just bought a ton of them for $10.00 a box. The clearance prices all over the country is dropping like a rock.
You might be able to get about $20 for them on ebay, the really low clearance prices have not hit ebay sellers yet.
@mitchp I’m unable to get your code to work when attempting to copy+paste it to the myapp section on developers. I get this error : groovy.lang.MissingMethodException: No signature of method: script14551631271211035396360.metadata() is applicable for argument types: (script14551631271211035396360$_run_closure1) values: [script14551631271211035396360$_run_closure1@5a69bf0f]
Possible solutions: getMetadata(), getState(), setState(java.lang.Object), metaClass(groovy.lang.Closure)