PetSafe SmartDoor Model HPA15-13808 (DTH in post 27)

Devices & Integrations
, ,
102

I had already removed the door from the Iris hub in attempts to pair with the SmartThings hub again. It shouldn’t still be paired to the Iris hub, but I’ll see about trying to factory reset the door. Thanks!

1 Like
103

According to the support article for the door, resetting it is as simple as five mode-reset button presses, which I’ve definitely done a few times. Still no luck getting ST to detect the door, as a “Thing” or otherwise.

Update:

I was finally able to get it to pair. It popped up as a “Thing”, unsurprisingly. Changed the DTH, and I was good to go!

No idea if this will help anyone else, or not, but I ended up resetting the door maybe 5 or 6 times in a row (pushing mode-reset 5 times in 5 sec, then as soon as the blue light flashed, did that again, 5 or 6 times in a row), all while having my phone search for a new Thing. Then all of a sudden, “Thing” pops up.

I guess for anyone else still trying to make this door work with SmartThings, try resetting the door a LOT while you’re searching for a new Thing.

Cheers!

1 Like
104

Just following up again, in case anyone is using this / can help with some errors. Every 2 days or less, it seems, the door stops being able to be controlled by SmartThings. The lock/unlock status reports correctly, as does the battery percent. Locking and unlocking don’t work, though. The messages I’m getting in live logging are as follows:

3:47:39 PM: trace read attr - raw: 68EF0C01010A0000003002, dni: 68EF, endpoint: 0C, cluster: 0101, size: 0A, attrId: 0000, result: success, encoding: 30, value: 02
3:47:39 PM: trace read attr - raw: 68EF0C01010A0000003002, dni: 68EF, endpoint: 0C, cluster: 0101, size: 0A, attrId: 0000, result: success, encoding: 30, value: 02
3:47:30 PM: trace SmartShield(clusterId: 0x0101, command: 0x20, data: [0x03, 0x02, 0xef, 0x00, 0xff, 0xff, 0xff, 0xff, 0xff, 0x03, 0x6f, 0x75, 0x74], destinationEndpoint: 0x01, direction: 0x01, isClusterSpecific: true, isManufacturerSpecific: false, manufacturerId: 0x0000, messageType: 0x00, number: null, options: 0x0100, profileId: 0x0104, senderShortId: 0x68ef, sourceEndpoint: 0x0c, text: null)
3:47:30 PM: trace catchall: 0104 0101 0C 01 0100 00 68EF 01 00 0000 20 01 0302EF00FFFFFFFFFF036F7574
3:47:10 PM: trace SmartShield(clusterId: 0x0101, command: 0x20, data: [0x02, 0x0e, 0xff, 0x00, 0xff, 0xff, 0xff, 0xff, 0xff], destinationEndpoint: 0x01, direction: 0x01, isClusterSpecific: true, isManufacturerSpecific: false, manufacturerId: 0x0000, messageType: 0x00, number: null, options: 0x0100, profileId: 0x0104, senderShortId: 0x68ef, sourceEndpoint: 0x0c, text: null)
3:47:10 PM: trace catchall: 0104 0101 0C 01 0100 00 68EF 01 00 0000 20 01 020EFF00FFFFFFFFFF
3:47:10 PM: trace catchall: 0104 0101 0C 01 0100 00 68EF 01 00 0000 20 01 020EFF00FFFFFFFFFF

105

My guess is this may be due to the platform changes in zigbee insecure rejoin that were introduced sometime last year.

106

Should Insecure Rejoin be on or off? For me it’s set to on. The door randomly started working again, as it tends to do. Sometimes it needs to get put back into pairing, then “added” again. The device is never “found” again, but the double-flashing blue light goes away and it starts working. Or it just starts working on its own again like it did today.

Cheers!

107

You ever get this done? I did. I ended up replacing the door slab, installing the petsafe door, and then paired with ST using the above device handler.

I just replaced the batteries for the first time, but now I can’t get then battery level to update in the app. Still reporting 0% even though it’s functioning fine now. I have a bunch of automations connected to the dog door device, so I’m loathe to delete and recreate the thing.

Anyone have any ideas about how to update the reported battery level? I’ve already gone into the Thing screen, hit save, hit refresh, etc. No luck. I’ve had this same problem with various devices over time.

108

Well, I somewhat gave up on getting ST to lock and unlock the door and have just been relying on the pet collar transmitter. Although it appears paired, the door consistently just reads “Locked” and pressing the unlock buttons has been inconsistent at best (I think I got it to unlock once but couldn’t get it to relock). Looking at the device history it just shows a single poll command sent to the door once every evening.

After two months and going through two sets of D batteries, I followed some instructions online and created wooden dowel battery “blanks” and hooked up the ends to a stripped USB cable, plugged in to a 5v 2amp power supply and the core functions of the door (lock and unlock with pet collar transmitter) have worked fine. (The 5v USB is close enough to 6v from 4x 1.5v D batteries in series, it seems)

I’d love to be able to see the exact times that the door unlocked for the dog to go out, but I’m not certain that’s even a feature of this device handler even if it’s working well?

109

Mine is reporting zero battery life as well. I know the new app is having problems it may be showing on the classic side as well.

110

I am a novice with device handlers but I took a zigbee lock and changed around the clusters. My battery shows up now. I am unable to test it until I’m off work.

111
112

Nice job. I will test as well, probably tomorrow, and let you know.

BTW, I’m still on classic in case it matters.

113

I’m on classic too. I tested the lock unlock works fine haven’t tested the battery function yet.

114

Danielle, just tried that zigbee lock DTH, but the link above is dead. Can you repost?

115
1 Like
116

Danielle, just tried that DH. The battery level instantly changed from 0% to 27%. Looks like the battery level monitor works. I’ll watch it over the next few days. And I’ll probably replace the batteries pretty soon. We’ll see how it goes. But at least it looks promising. Thanks for your help with this!

117

I’m a little late to the party, but the device handler by sticks18 can be easily modified to report battery correctly again. (at least it worked for me.)

The method that reads:
private getBatteryResult(rawValue) {

//log.debug 'Battery'
def linkText = getLinkText(device)
def result = [ name: 'battery' ]

def volts = rawValue / 10
def descriptionText
if (volts > 6.5) {
	result.descriptionText = "${linkText} battery has too much power (${volts} volts)."
}
else {
	def minVolts = 4.0
	def maxVolts = 6.0
	def pct = (volts - minVolts) / (maxVolts - minVolts)
	result.value = Math.min(100, (int) pct * 100)
	result.descriptionText = "${linkText} battery was ${result.value}%"
}
return result

}

You can change the 2 lines:
def pct = (volts - minVolts) / (maxVolts - minVolts)
result.value = Math.min(100, (int) pct * 100)
to:
def pct = (((volts - minVolts) / (maxVolts - minVolts)) * 100)
result.value = Math.min(100, (int) pct)

Sorry for the poor formatting.

1 Like
118

Thanks for the suggestion. I made the edit…in a few weeks or months when my battery drains, I’ll let y’all know how it worked out.

119

I am trying to pair my Petsafe Smart Door. It has been in pairing mode for over a day. I added the device type handler from Sticks… no device is ever found to do anything else. I also added the device handler that you posted. I’m just wondering which one is the right one to use… and would that cause a conflict since I have added both? I have been able to connect other iris things to smartthings… just not the dog door… it is constantly trying to pair.

120

I’ve had the same problem off and on almost every time I need to change the batteries. It could stay in pairing mode for days with no luck. Or sometimes, at random, it pairs within seconds.

You don’t actually need to have the device handler installed or set up before pairing the door (if you don’t, it’ll probably come up as a “thing” that you can assign later). I haven’t figured out any surefire way to actually make the door reliably pair with smartthings.

Some time ago, after a lot of frustration, I bought an Iris hub and had just as much trouble getting it to pair with that, and their support couldn’t figure out why. That makes me think it’s an issue with the door, rather than an issue with the hub. I’ve had just as much of a problem with the v3 hub, v2 hub, and Iris hub.

Best of luck to you - I wish I had better news.

121

Thanks sparks18 - the code is awesome. Fyi folks the door is still available direct from the manufacturer, I got it a few days back. I hope they don’t stop making this model, as they just shut down iris servers too. Yes it has 4 LEDs as the giveaway plus mentions iris. pairing was a breeze but then the issues started as I did not have this device handler loaded to after much research I learned that I had to use the smartthings IDE site to reassign the handler from the default it picked to the one in this thread. Took me several hours to figure that out and my way around the IDE, and manually copying the code in as the GitHub pull thing did not work for me. Key learning is this is a device handler not an app, so in the ST IDE use the My Device Handler not the my apps tab.

Here is what I needed to do, in the order i should have done it to make life easier:

    • First log into your ST IDE account, it has your smartthings hub already linked
    • in the “My device handler” tab (top) then select “Create new device handler” then select “from code” and then paste in the code
      There is a nicer way to do this with linking the GitHub, which i could do but did not get it to work so went with the above manual past.
      I feel there is more to this step but its not coming to me, hopefully some one can chime in to fill in the missing steps (if any)
    • Pair the device - using the mode-reset button (not the learn button, that one is only for the collar rf learn) for 5 seconds (must be done in the first 5 seconds after power up) also seems to get done automatically if the door has never been paired.
      3.5 * blue light blinks while you have ST app search for the device it then calls it a “thing”
    • in the ST IDE “My devices” tab (top) select the dog door and click on the name (first column) then at the bottom of the new page click on edit. Insure the type is “PetSafe Smart Door” <-- because I paired before having the device handler loaded up this was wrong think it showed “thing”
      Thats it, enjoy.

By the way non of my lights are on and it works with the RF dog transmitter and with the app. App shows lock/unlock status and allows changing status. also shows battery, but that is not working quite right. Note I have it with both the old and the new ST app.

Battery indicator fix, thanks to Mpark12345 is working :slight_smile: Note: It took a while to actually show the 90% that its at now, was stuck at 0% for about an hour.

Thanks again to all that have contributed. Hope we can continue to work this as it seems with Iris there were a few other cool features like: Which pets are in and out (out of a total of 5) based on which way the flap opened and which RF tag had unlocked it. I only have one pup, but it would be great to know if she is in or out. Am open to testing things and collecting any info if someone can help make the code as I have not been coding in over 25 years. I do see a word “direction” in the live logs seems interesting, will try out some test cases with the RF collar and see if I can decode anything.

Thanks again to all!!