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

v6: documentation on PUT /clients/ is not complete #1943

Open
jojost1 opened this issue Mar 1, 2024 · 5 comments
Open

v6: documentation on PUT /clients/ is not complete #1943

jojost1 opened this issue Mar 1, 2024 · 5 comments

Comments

@jojost1
Copy link

jojost1 commented Mar 1, 2024

Versions

  • Pi-hole: v5.17.3-288-g760f903d
  • AdminLTE: v5.19-700-gda7c0efb
  • FTL: vDev-bffd2bd
    Branch is development-v6

Platform

  • OS and version: Debian
  • Platform: Raspberry Pi

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.

@jojost1
Copy link
Author

jojost1 commented Mar 1, 2024

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 /clients:batchDelete always, so I can't check what's going on.

Copy link

github-actions bot commented Apr 1, 2024

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.

@github-actions github-actions bot added the stale label Apr 1, 2024
@jojost1
Copy link
Author

jojost1 commented Apr 1, 2024

The issue is still there.

@github-actions github-actions bot removed the stale label Apr 1, 2024
Copy link

github-actions bot commented May 2, 2024

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.

@github-actions github-actions bot added the stale label May 2, 2024
@jojost1
Copy link
Author

jojost1 commented May 2, 2024

I still have the issue

@github-actions github-actions bot removed the stale label May 2, 2024
@DL6ER DL6ER transferred this issue from pi-hole/pi-hole May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant