The only suggestion that I can make is to telnet to port 3000 of the door’s IP address, to confirm that it answers and that you are using the correct IP address…
Yeah that works fine (unfortunately?). I’m also very careful to terminate the session cleanly before trying to run my integration, as these doors are apparently very temperamental about only having 1 client connected.
I’m thinking something is broken with the config workflow and I’m hoping someone else here can share how to manually configure in YAML files?
1 Like
Is this still an active functioning product? I need to replace our current dumb dog door, and think that even though the high tech door is a bit pricey if it can integrate to HA that would be amazing for our home.
Thank you!
@corporategoth’s driver is actively being maintained, and AFAIK High Tech Pet is still in business. They are also still selling repair parts on their web site.
My only tip is to look at YouTube for “hacks” to make standard coin cell batteries work in the collar ultrasonic transmitter, because their proprietary replacement batteries are pricey…
Thank you for your reply, I was considering their rechargeable collar that is now available.
What rechargeable collar? The only one that I see is the rechargeable shock collar for the invisible fence, which for some reason is also listed under the power pet door…
It does indeed also work with the pet door. And the charge does last quite a while (a month-ish?) … and then you just pop it on the charger overnight and put it back on, and back in business. It’s what I’m using now.
Interesting! Don’t know if the $125 TCO will pan out versus generic coin cell batteries in our case, especially with our aging OCD psycho dog…
I moved house a year and a half ago. Had to get a new power pet door (since the old one was embedded in the wall of the old house).
So got this collar with the new door, and I’m happy that I don’t need to keep replacing batteries or tearing apart the ‘proprietary’ cells to put in generic batteries. This is much easier.
1 Like
Has there been any further development? I was wondering if you are experiencing the same thing I do when I use these commands. If I open the door, it will not respond to the next command for approx. 7 seconds. It seems the door is timing out and resetting allowing the next command to be heard. I am assuming there is either something else needed in the command to close it out and ready it for the next command or it needs to answer the door’s feed back communication for it to verify state. Anyone solve this?
I wrote this in Hubitat and it has an issue where when I open the door then try to close it immediately it will not respond for 7 seconds or so.
import groovy.json.JsonOutput
metadata {
definition (name: "WiFi Dog Door Controller", namespace: "Wifidogdoor", author: "Brad Martin") {
capability "Switch"
}
}
preferences {
input name: "doorIp", type: "text", title: "Dog Door IP Address", required: true
input name: "doorPort", type: "number", title: "Dog Door TCP Port", defaultValue: 3000, required: true
}
def installed() {
log.debug "Installed with settings: ${settings}"
initialize()
}
def updated() {
log.debug "Updated with settings: ${settings}"
initialize()
}
def initialize() {
// Initialization logic if needed
}
def on() {
log.debug "Switch turned ON - Opening door and holding it open"
sendCommand(["cmd": "OPEN_AND_HOLD", "msgId": 812, "dir": "p2d"])
sendEvent(name: "switch", value: "on")
}
def off() {
log.debug "Switch turned OFF - Closing door"
sendCommand(["cmd": "CLOSE", "msgId": 815, "dir": "p2d"])
sendEvent(name: "switch", value: "off")
}
private sendCommand(Map command) {
def hostAddress = "${settings.doorIp}:${settings.doorPort}"
def jsonCommand = JsonOutput.toJson(command)
log.debug "Sending JSON Command to ${hostAddress}: ${jsonCommand}"
try {
def hubAction = new hubitat.device.HubAction(
jsonCommand,
hubitat.device.Protocol.LAN,
[type: hubitat.device.HubAction.Type.LAN_TYPE_RAW, destinationAddress: hostAddress]
)
sendHubCommand(hubAction)
} catch (Exception e) {
log.error "Error sending command: ${e.message}"
}
}
There’s your problem! 
Try telnetting directly to port 3000 on the door, and see if there is a delay in responding to the commands. Also watch the dialog coming back from the door, and make sure that Hubitat’s sendHubCommand() is able to handle that returned info and isn’t just doing a blind send.
If it works from telnet, then it is obviously a Hubitat issue best asked on their forums. @corporategoth’s HA integration and some ugly shell scripts that I wrote prior to his awesome integration do not have any delay problems…