-
Notifications
You must be signed in to change notification settings - Fork 416
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
New device: Catit Pixi Smart Fountain #216
Comments
Thanks, the data points are the "code" values in the request part of those json files. The API explorer has only one function I know of that returns dp_id attributes, and that is the last "Get Device Specification Attribute" function under the section "Device Control" near the end of the list. |
Thanks, code-points extracted below:
I'll check the device spec attribute stuff out now |
How's that? It looks like the chinese text ones aren't documented in here, but the rest is. |
ah, found the log in HA.
|
Closed with #217 |
Device: Catit Pixi Smart Cat Fountain
Note: Tuya isn't documented for this fountain anywhere - they use a branded app for this - but pairing works perfectly when configuring in the app, and all relevant settings work.
The functionality includes:
I'm not sure what "water time" and "water reset" are - there's no notifications to change the water as far as I can tell, just one that tells you when the water level is low.
Instructions:
https://www.catit.com/shared/Product-Manual_PIXI-Smart-Fountain_NA.pdf
API Explorer result:
Unfortunately, Home Assistant isn't giving me the datapoints in the logs - if somebody can direct me on how to go about that, that'd be great. They don't show up in the logs section at all - no results when it gives me the list of possible device-types - and my docker logs remain quiet.
I've put the data-points from the zigbee2mqtt instructions in the directory below. Each file is named for its option in the dropdown (apologies - some of these are in chinese - google translate seems to be helpful here) and each file includes the request at the top and then the response below it, in case that helps.
https://cloud.at.alexmaras.com/s/97soGDR77gZtobF
The text was updated successfully, but these errors were encountered: