Skip to content
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

Aqara C1 Pet Feeder PETC1-M01 #7667

Closed
1 task done
mcormick opened this issue Mar 15, 2024 · 5 comments
Closed
1 task done

Aqara C1 Pet Feeder PETC1-M01 #7667

mcormick opened this issue Mar 15, 2024 · 5 comments

Comments

@mcormick
Copy link

Is there already an existing issue for this?

  • I have searched the existing issues and there is none for my device

Product name

Aqara Smart Pet Feeder C1

Manufacturer

Aqara

Model identifier

aqara.feeder.acn001

Device type to add

Other

Node info

node_info

Endpoints and clusters

clusters

Basic

cluster_basic

Further relevant clusters

Power Configuration

N/A

On/Off

cluster_onoff

Level Control

N/A

Color Control

N/A

Thermostat

N/A

Simple Metering

N/A

Electrical Measurement

N/A

Groups

cluster_groups

Identify

cluster_identify

Lumi Specific

cluster_lumi_specific_1
cluster_lumi_specific_2
cluster_lumi_specific_3

Otau

cluster_otau

Scenes

cluster_scenes

Time

cluster_time

@mcormick
Copy link
Author

@SwoopX
Copy link
Collaborator

SwoopX commented Mar 15, 2024

Duplicate of #6595, therefore closing

@SwoopX SwoopX closed this as not planned Won't fix, can't repro, duplicate, stale Mar 15, 2024
@mcormick
Copy link
Author

Rucksichtlos closing a new request because a 1.5 year old one was already closed, without satisfying result I might add? Surely this could be looked into again with all the work that has been done in deCONZ in the months thereafter? Also, the new cluster screenshots differ to a certain degree from this original request. Politely requesting a reopening of either this, or the old request and a serious look into possible support for this device.

@francescopeloi
Copy link

@SwoopX kindly tagging you to see if you agree with the above message?

@SwoopX
Copy link
Collaborator

SwoopX commented Mar 20, 2024

Apologies, but I do not understand what is reckless in this regard. We have rules here and give guidance on what to do prior to raising new device requests. This is available on the one hand to point the potential requestor at what to do before putting work into creation of an issue (which admittedly can be rather extensive depending on the device), and on the other hand to not unnecessarily blow up the number of device issues per se and/or scatter any device relevant information over various issues. Specifically the latter is very inconvenient and error prone and this just makes the lives of the developers harder as it needs to be.

It is unfortunate that the result of the already available issue is unsatisfying for you, but this is not an acceptable justification. You're always free to request re-opening issues and welcome to contribute with newly available or missing information to resume work. Please do note though that often information about functionality, issues or blockers is already documented in the respective issues.

Thanks for understanding!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants