Is it possible? Probably. Is someone interested in porting it? No clue. It’s probably a complete rewrite and a ton of work to reverse engineer that device.
Fair enough
Thanks for thr integration, it's pretty sweet! I've tried to invoke the "push" action, both as a button on the dashboard and directly in the device and got the following error:
error groovyx.net.http.HttpResponseException: status code: 422 on line 229 (method handleFeed)
422 is "unprocessable entry", so I wondered if PetSafe broke the API?
I've had this app installed for six months or so, but I'm just now getting around to really using it to trigger automations. I noticed today in my variable list "hopperStatus : full" but the pet feeder is actually out of food and the app lists the status as "out of food." Everything else seems to be updating just fine. Feeding schedule and amounts are properly reflected in the device. Last feeding time lists today. I relinked the app and ran a repair through HPM, but nothing seems to fix that variable. Is anyone else having problems with getting the hopper status properly updated?
@dman2306 do you know what could be causing this?
The fed notifications have been on repeat all day.
Android app and PetSafe integration both seem fine.
Cheers
I just re-installed this app, after a small break, and this issue is still there.
It is just consistently repeating notifications every minute, even with notifications turned off.
Unfortunately, the developer of this app is no longer active in the community, so this app is no longer being maintained AFAIK.
Hi everyone,
Having one of these pet feeders, I was bummed to see that this integration is no longer maintained. However, I sat down over the course of a few nights and built my own. It's heavily based on the existing work by @dman2306 but I also borrowed some ideas from other service integrations. It is now parent-child architecture, with the parent essentially being your Petsafe account and the child devices are the feeders.
Here is the code on Github: GitHub - grussr/hubitat-petsafe-wifi: Controls petsafe wifi things. Note this is some really terrible alpha code, as I was Just Trying To Make It Work. Let me know if you encounter any issues.
Todos: add scoopfree litter box integration, clean up the code.
3 Likes
How’s the code working for you? I’m asking because we’re debating buying the feeder.
Just picked up one of the feeders but not having any luck with the new code. Here is the errors I am getting from the logs:
dev:4262023-02-07 16:49:05.485errorgroovyx.net.http.HttpResponseException: status code: 400, reason phrase: Bad Request on line 174 (method setEmail)
dev:4262023-02-07 16:48:51.396errorgroovy.lang.MissingMethodException: No signature of method: com.hubitat.hub.executor.LogWrapper.Error() is applicable for argument types: (java.lang.String) values: [status code: 401, reason phrase: Unauthorized]
Tried logging out of both the app and the new code request, that's probably what caused the Unauthorized error as I was never actually logged in. Tried a couple different times to set email in the device without any luck. Just throws the same error.
Will it work with the litterbox?
According to the available code from the post by @rpgruss, not quite yet. The layout is there, and I would assume being worked on but as it stands, it does not support the litter box.
1 Like
The Sure Petcare (Connect) for hubitat keeps notifying me that my dogs been fed I would only like it to notify me one time.
How do I fix this?
@rpgruss Ryan, you still around these parts? Would love to know where this stands. I’m debating buying a pet feeder.
Before I found this thread I reached out to Petsafe after buying one of the feeders (which has been working great so far to be honest, if a bit noisy).
They came back that the current generation of the feeders does not have the API support and such that the previous model did because they changed the way it works. However, they were debating about whether they would attempt to add it back in or an equivalent. To me... that is a polite way of saying "nope" in most cases.
But I will keep hoping and just use the feeder with the built-in capabilities as is.
1 Like
Hmm, this is weird. I just called PetSafe and also did the live-chat. And they claimed that current PetSafe Smart Feeders do have API support enabled. I don't know how to reconcile that with what @snell learned. To be fair, I never quite trust what these support teams say, so I'm not sure what to believe. I did purchase a unit and it's arriving tomorrow. I'll try it out and see what happens. Will let you know.
1 Like
Ha! So weird. I emailed support. It took a bit because they said they had to wait for engineering to respond. Hopefully it works!
Is anybody still using this app, either the original @dman2306 version or the new @rpgruss device driver?
Here's what I've learned so far today in trying it out with a new Smart Feeder we just purchased:
- When I use @rpgruss's device driver, I get the same error as @nzeroesc (see error messages a few messages above in this thread)
- I suspected this might be because @snell was right (and I was wrong!) -- i.e., the PetSafe API was longer operational.
- To test this theory, I tried @dman2306's app -- and while I can't get the app to operate, it does successfully create the feeder device and pull in all the attributes (e.g., schedule etc.) from the PetSafe app. This suggests to me that the API is working.
- So I went back to @rpgruss's device driver, but I just can't get past the initial step of submitting the email address (userID) to the PetSafe API.
Curious if anyone has any ideas? I'm thinking about setting up a Home Assistant instance so I can do better dashboarding. If I do, I'll try to add this device on that platform. Dunno for sure.
Help?!
So, my thought is the API is still there. Before seeing these are started some work on my own driver for it and it DOES respond to some stuff. But I wonder how well the newest version of devices support it, or if they changed the API structure a bit. That could easily explain why some things work and some things do not. I have had to deal with similar stuff on my own API drivers. If the company changes the structure of the API or adds a new version section that only works with a newer device... you can lose all sorts of functionality until that difference is understood. It may even only be new models that use it and only for certain functions even.
The Blink API is very much a mess of old and new areas...
