> For the complete documentation index, see [llms.txt](https://docs.hamina.com/hamina/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hamina.com/hamina/simulation/wired-clients.md).
# Wired Clients
Add cameras, computers, printers and more.
## Placing Wired Clients
1. To place a wired client, locate the **Network** section on the left, click on the **Network Infrastructure** > **Client device** tool. This will open the **Add Client Device** pane on the right.
2. In the **Add Client Device** pane, choose the appropriate type of wired device.
3. Click on the map to place the client device.
## Customizing Wired Clients
You can define a custom Name and Power allocation for client devices. Custom names work [just like custom AP names](/hamina/simulation/access-points.md#renaming-access-points).
{% hint style="success" %}
When it comes to the estimated cable length for Wired Clients they are assumed to be at floor level. There is no additional cable added to the estimate to account for mounting/positioning height of the client.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.hamina.com/hamina/simulation/wired-clients.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
