-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request]: PLAF109 / Polar Wet Food Feeder | Requesting additional controls/sensors #41
Comments
@lucromano the Polar Wet Feeder is already implemented. Is yours not showing up? Or are you wanting an feature request/enhancement of the device? |
oh yes, but didn't seem to have any 'actions' ie. opening/closing lid, rotating food etc. |
There's no option to actually action anything? Maybe I'm configuring it wrong. In any case, ideal features would be: P0
p1
p2
p3
happy to assist in dev :) |
I understand that a few of us have been looking into this and exploring what can be added, @lucromano. Since this is a relatively new device, not all API information has been made available yet. We appreciate your patience as we work through the details and determine what is fully accessible. |
I am available for this, if someone can bring me up to speed. |
@lucromano, here is what I know so far.
Also right now, it looks like @peterjeschke was working on some of it in #47 Just glancing at some of their code it looks like they were implementing the feeding plan/control for the device that may be viable to use for
We have API information for sound that might apply to this device here - #27 that we may be able to help. Hopefully that helps, let me know if you need any more info or anything else 😄 |
Yes, I have plans to implement more stuff for this device :) My next plan is to control schedules, but I'm not sure yet how to properly expose them to Home Assistant because they're dynamic. My initial thought was to create entities for each schedule, but that could clutter things up if you create and delete schedules often |
i have been thinking about it too. from what i have thought about, i think the best would be to have a sensor with some data - probably just if the schedule is active. but have all of the scheduled feedings in the attributes of the sensor. then have service calls that can add, delete, enable, or disable specific scheduled feeds based on the name or id of the scheduled feed in the attributes? then if service call is made, wait a min and call a refresh of the data to pull into attributes. in this way people could make automations to turn or off the next scheduled feed automatically by reading the attributes to find the next feed and use that name/id in the service call. you could have 1 sensor for todays schedule, and 1 sensor for all schedules. i really cant think of a better way to maintain the info. |
It seems we have another. @kevinpoitra has also been working on some enhancements in pull request #50 for this device. |
Hi! I received a PLAF109 for Christmas, however I'm displeased at the inability to add multiple feeding schedules for the same day through the official app - my cat eats twice a day, so I want to be able to open the food door once in the morning and once in the evening. As such, I started extracting API information from the app and implementing its controls into this integration. #50 adds the manual 'Feed now', 'Rotate food bowl', and 'Ring bell' controls available when no feeding schedules are set. My next PR will involve implementing the ability to set feeding schedules through this integration. |
@lucromano
I would prefer to focus on finding a way to finalize a method for controlling the scheduling. |
Device model name
Polar Wet Feeder
Device model number
AF05013841......
Device type
Feeder
What state, statistic or control do you want to be reported in the integration ?
entities
Available to help integrate the new device
The text was updated successfully, but these errors were encountered: