SmartThings Community

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

project_pets
dth_pets
project_animals

(Danielle) #73

i have mine paired right now no issues


#74

It sounds like it thinks it’s still paired to the iris coordinator. Zigbee devices can only have one coordinator. You would need to check the device manual to find out how to clear the old coordinator information before joining it to SmartThings.


(Jim Murray) #75

Unfortunately the literature pertaining to the door is a bit lacking and does not indicate a way to “default” the door. Since I purchased an Iris to test it out and it worked I have unpaired it with the Iris unit using the app interface and attempted pairing with ST several more times. No luck. Again, the indications on the door would have you believe it experienced a successful pairing as indicated by the three flashes, but ST stubbornly refuses to acknowledge it sees anything. After several more attempts at pairing with the ST I added it back to the Iris with no issues. Bizarre…


ZHA device pairs to Iris, won't pair to ST --help needed
#76

Did you have to do anything to reset the device before adding it back to Iris? If not, it had retained the information that Iris was its Coordinator, which would explain by it was not joining to SmartThings.

Most devices have two separate procedures, one to reset the device to all of the factory default for the configurable parameters, and a separate one to clear the coordinator information. This is what allows you to “reset” a device without having to remove it from the network and re-add it.

The following is the procedure in the manual that should clear the coordinator information:

Reset Instructions
.
You should perform a reset if the device has been force removed from the app or the device has pairing and/or connectivity issues. These reset steps will clear the door’s ZigBee configuration. It will not reset or remove any Smart Keys programmed to the door.
.
Step 1: Press the MODE-RESET button on the door five times in a row, once per second.
.
Step 2: Confirm the blue LINK light is blinking. It should blink twice every 2 seconds
.
Step 3: Reconnect the door by going to the dashboard’s upper-right Add (+) menu, then choosing Devices. The hub will triple beep once the door reconnects.

Except in step three, instead of doing that in the iris app, you’re going to do an add from the SmartThings app.

Also, make sure that the iris hub is powered off before you attempt this as otherwise the door may just re-join iris network. Once you have the door joined to the SmartThings network, you can then have both Iris and smartthings on power and it should be fine.


(Jim Murray) #77

Thanks JD. Yeah - the MODE-RESET button is what I have been using for all pairing attempts. If it is currently paired to the Iris, the behavior is exactly the same as when I have removed it via the app interface when trying to pair with ST. I know this is getting unclear, but essentially if I use the reset sequence mentioned above and then attempt to pair with ST, the lights go out relatively quickly and the door thinks it is paired with ST indicated by a triple flash on the door. It also no longer works in Iris. When I repeat this procedure with Iris doing the pairing the behavior of the door is EXACTLY the same except it shows up in the Iris app and works (and the Iris hub beeps to indicate pairing). In effect I have the door thinking it is pairing with ST, but ST never indicates it has seen anything. This behavior was identical before I went out last night to purchase the Iris to test the door’s functionality after failing with ST. The door was brand new in the box so there would have been no controller stored when I first began attempting the pair.


#78

Sometimes a device is paired with the test controller at the factory and then the Coordinator information is not fully cleared before the device it shipped. So sometimes you do need to do a reset even with a brand-new in the box device. It happens.

However, what you’re describing is definitely weird. The door sounds like it thinks it’s pairing, but it isn’t. I’m sure it’s very frustrating.

You have to open live logging and see exactly what messages are being exchanged with the smartthings hub and I don’t know if you want to go to that trouble.

Also, by chance, do you know if you have secure rejoin turned on? That’s the only other thing I can think of that might cause the join to fail.


(Jim Murray) #79

Heck yes I want to go to the trouble. I have a wife who doesn’t like home automation anyhow and every time I buy a new “needed” controller or accessory I catch an earful. This makes two this week! I’ll have a look in there and see what I can sniff out. Thanks once again for the continued help. I’m not sure anything I see in there can help you narrow the problem, but I’ll definitely give it a shot. I’m doubtful I’ll know what I’m looking at so I’ll probably need your help again. As an aside, I did try pairing with both the insecure rejoin on and off with the same results. It is on by default and remains there now, but I did try it with it off. Door appeared paired each time, but no acknowledgement from ST. Thanks again.


(Jim Murray) #80

Here are two pairing attempts - both ended with the door giving 3 quick flashes as if paired - Iris was powered off during these operations. It appears to me the ST never saw a thing:

0bdee359-c97c-426e-895f-6b69571200c7 6:41:06 PM: debug updated called
0bdee359-c97c-426e-895f-6b69571200c7 6:41:03 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:41:03 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:41:03 PM: debug scheduled run, numberOfRuns: 4
0bdee359-c97c-426e-895f-6b69571200c7 6:41:03 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:40:53 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:40:53 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:40:53 PM: debug scheduled run, numberOfRuns: 3
0bdee359-c97c-426e-895f-6b69571200c7 6:40:53 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:40:48 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:40:48 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:40:48 PM: debug scheduled run, numberOfRuns: 2
0bdee359-c97c-426e-895f-6b69571200c7 6:40:48 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:40:43 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:40:43 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:40:43 PM: debug scheduled run, numberOfRuns: 1
0bdee359-c97c-426e-895f-6b69571200c7 6:40:43 PM: debug No installed apps found, calling deviceDiscovery
0bdee359-c97c-426e-895f-6b69571200c7 6:40:43 PM: trace in migration code block
0bdee359-c97c-426e-895f-6b69571200c7 6:40:43 PM: trace calling migration script
0bdee359-c97c-426e-895f-6b69571200c7 6:40:43 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:40:42 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:40:42 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:40:42 PM: debug scheduled run, numberOfRuns: 0
0bdee359-c97c-426e-895f-6b69571200c7 6:40:42 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:40:38 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:40:38 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:40:38 PM: debug scheduled run, numberOfRuns: 13
0bdee359-c97c-426e-895f-6b69571200c7 6:40:38 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:40:32 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:40:32 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:40:32 PM: debug scheduled run, numberOfRuns: 12
0bdee359-c97c-426e-895f-6b69571200c7 6:40:32 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:40:32 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:40:32 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:40:32 PM: debug scheduled run, numberOfRuns: 11
0bdee359-c97c-426e-895f-6b69571200c7 6:40:32 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:40:30 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:40:17 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:40:17 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:40:17 PM: debug scheduled run, numberOfRuns: 10
0bdee359-c97c-426e-895f-6b69571200c7 6:40:17 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:40:07 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:40:07 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:40:07 PM: debug scheduled run, numberOfRuns: 9
0bdee359-c97c-426e-895f-6b69571200c7 6:40:07 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:39:58 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:39:58 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:39:58 PM: debug scheduled run, numberOfRuns: 8
0bdee359-c97c-426e-895f-6b69571200c7 6:39:57 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:39:57 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:39:57 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:39:57 PM: debug scheduled run, numberOfRuns: 8
0bdee359-c97c-426e-895f-6b69571200c7 6:39:57 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:39:53 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:39:53 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:39:53 PM: debug scheduled run, numberOfRuns: 7
0bdee359-c97c-426e-895f-6b69571200c7 6:39:53 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:39:43 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:39:43 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:39:43 PM: debug scheduled run, numberOfRuns: 6
0bdee359-c97c-426e-895f-6b69571200c7 6:39:43 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:39:42 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:39:42 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:39:42 PM: debug scheduled run, numberOfRuns: 5
0bdee359-c97c-426e-895f-6b69571200c7 6:39:42 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:39:32 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:39:32 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:39:32 PM: debug scheduled run, numberOfRuns: 4
0bdee359-c97c-426e-895f-6b69571200c7 6:39:32 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:39:22 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:39:22 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:39:22 PM: debug scheduled run, numberOfRuns: 3
0bdee359-c97c-426e-895f-6b69571200c7 6:39:22 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:39:17 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:39:17 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:39:17 PM: debug scheduled run, numberOfRuns: 2
0bdee359-c97c-426e-895f-6b69571200c7 6:39:17 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:39:12 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:39:12 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:39:12 PM: debug scheduled run, numberOfRuns: 1
0bdee359-c97c-426e-895f-6b69571200c7 6:39:12 PM: debug No installed apps found, calling deviceDiscovery
0bdee359-c97c-426e-895f-6b69571200c7 6:39:12 PM: trace in migration code block
0bdee359-c97c-426e-895f-6b69571200c7 6:39:12 PM: trace calling migration script
0bdee359-c97c-426e-895f-6b69571200c7 6:39:12 PM: trace in discovery
0bdee359-c97c-426e-895f-6b69571200c7 6:39:10 PM: debug updated called
0bdee359-c97c-426e-895f-6b69571200c7 6:39:07 PM: debug No devices to add, verified devices: [:]
0bdee359-c97c-426e-895f-6b69571200c7 6:39:07 PM: trace in ssdpDiscover
0bdee359-c97c-426e-895f-6b69571200c7 6:39:07 PM: debug scheduled run, numberOfRuns: 11
0bdee359-c97c-426e-895f-6b69571200c7 6:39:07 PM: trace in discovery
6:39:06 PM: info Waiting on events…
6:39:06 PM: info For past logs for individual things go to the My Devices section, find the device and click on the Events link on the device information page.
6:39:06 PM: info This console provides live logging of your SmartThings


(Danielle) #81

put in a ticket to smartthings telling them you are having problems pairing a zigbee device. Last time I had the timeout problem (what you are having) they had to tweak somethings behind the scenes


(Shaun Arnold) #82

Did you ever get it to pair with ST? I’m having the exact same issue.


(Jim Murray) #83

Never did. Still using the Iris for control of that one device. I guess that’s fine since I don’t actuate the door that often, but it’s a pain having to open a separate app for that one device.


(Gabe Stover) #84

I’ve just received the HPA15-13808, and I’m having trouble getting SmartThings to recognize it at all. When I put the door in pairing mode, SmartThings never finds it. I contacted support to see if they could help, and they said in the live logging, that nothing was ever discovered or something to that effect. The CSR told me that some generations of Iris-branded devices will not operate with smartthings whatsoever. I’ve got the Iris keypad working just fine, but no matter what I do, SmartThings never finds the dog door as a device. Any pointers? Thanks in advance!


(Mark) #85

Did you install the custom device handler in post 27 above before trying to pair it?


(Gabe Stover) #86

Yep, sure did. I know I could pair it first and change it in the IDE afterwards, but wanted the device handler installed first. No luck getting SmartThings to see it to add it though


(Mark) #87

Did you check the live logging when trying to pair? Or St support did? I’m no zigbee expert, but if you post the logs here someone may be able to help.


(Gabe Stover) #88

I did look at live logging, as did ST support. I’m even less of a zigbee expert and the logs didn’t make a whole lot of sense to me. Support said that they could see that the hub was looking for devices, but didn’t find any. The door definitely showed that it was in pairing mode, according to its flashing light, but was never found as any type of device by ST. I’ve just ordered an Iris hub to see if it will pair to that, or if the door itself is defective. I’ll try pairing again when I have a chance, and post what the live logging says. Cheers!


#89

Sorry to drudge up a somewhat old thread, but I’m looking for a large pet door with some Zigbee or Zwave ST-compatible abilities. I can’t find the Zigbee version of this door for sale on Lowes.com, and am wondering if anyone has seen them locally, or if it seems like the product is discontinued/dead.

Are these doors still working ok for those who already have them, with the latest ST updates?


(Danielle) #90

Amazon has them

Petsafe smartdoor


#91

The Amazon listings that I have found don’t mention Zigbee, and Petsafe customer service says they’re not able to sell them (the Zigbee nodel) on their website but there may still be some in individual Lowes stores…


(Mark) #92

@Natec, any luck? I’m looking for the petsafe smartdoor that has the zigbee radio. Sounds like you are too. The Amazon listing claims it does NOT include a zigbee radio. I just put in an email to Petsafe customer service. I’ll let you know what I learn. May also try Lowes.