-
-
Notifications
You must be signed in to change notification settings - Fork 208
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
v6: documentation on PUT /clients/ is not complete #1943
Comments
Additionally I found out that a call to delete a client is also not working for me (while e.g. deleting a group works fine). It's throwing a 404. The web interface seems to use |
This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days. |
The issue is still there. |
This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days. |
I still have the issue |
Sorry for this to have gone unnoticed for so long, I moved it into the correct repository now. extra
|
The point you've mentioned have been fixed in the code. Feel free to reopen/comment if you find something we've talked about here not having been fixed. |
Got it working, thanks for the reply! |
Versions
Branch is development-v6
Platform
Expected behavior
The API states the only fields are 'comment' and 'groups'. However, it looks like the web interface also sends a field 'client' (unclear to me what this is) and 'enabled', like this:
{"client":"00360032003a00390043003a00310034003a00450033003a00310035003a00330045","groups":[1],"comment":"Test Device","enabled":false}
Actual behavior / bug
Without a correct client field, it looks like Pi-hole creates a new client instead of updating an existing one. It's also unclear what the 'enabled' field means that the web interface sends (could just be a bug?).
Furthermore, the GET /clients endpoint also returns a 'name' property for a client which is undocumented as well. I'm not sure if this has to be send for PUT requests as well.
Additional context
This issue is about the new v6 API.
The text was updated successfully, but these errors were encountered: