> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-advanced/appendix/open-items.md). # Open items What this guide does not yet cover, and the questions it has left open. Each question is also marked where it arises, in a callout beginning **TODO**. Items are grouped by the area of the console they concern. ## Questions to answer ### Batteries * The unit of the **Battery Consumption by App** figure on the Batteries overview, and how a reader should compare two bars. * What a **% of Full Charge** above 100 means for one app in one cycle under **Top App Consumption**. * How a reader can tell whether a battery's capacity in milliamp hours was reported by the battery or estimated by AMIE. * How long a battery typically goes without reporting a capacity reading, and whether a persistent gap is worth acting on. * Why a group can show its handsets under **Managed Devices** while **Managed Batteries** and the call figures read **0**, and what an administrator should do about it. ### Devices * What the handset counts as being "in use" when it reports: handled, unlocked, on a call, or off its charger. * Where a handset's name and tags are set. Nothing in the console sets them, and many handsets read **Spectralink** or **Auto-registered device** followed by the serial number. * Which network adapter the **MAC** value on Device details belongs to. * What makes a handset reachable for messages and log-collection requests, and what an administrator can do about one that reads as not reachable. * What a device without credentials represents under **Managed Devices**, and whether the Dashboard and Devices overview counts are expected always to agree. ### Performance * Which networks are excluded from the Performance figures, and how an administrator can see the list. * Whether the dropped and missed packet definitions from the previous guide still apply. * Whether a long handoff is attributed to the access point the call moved to or the one it moved from. * What "the same part of the Space" means to a reader when calls are grouped on the Performance screen. * Why some call records carry an all-zeros access point address. ### Alerts * How **Days Open** and **Created** relate for a reader, and whether they are ever meaningfully different. ### Settings and users * What a **Service User** is. Every row on the **Users** tab reads **No**. * Whether an administrator can resend the password-setup email, and what a new user who let the 48 hours pass should do. * How a user's role or group is changed, and how a user is removed, until the console offers it. * How a group is renamed, moved or deleted, until the console offers it. ### Sign-in and planning * How long an enrollment ID remains usable, and whether the console can show when one expires. ## Features not yet available The console shows these controls but they do not yet do anything, or are labeled **Coming soon**. Each is marked on its page. The guide will describe them when they work. | Screen | Control | | ------------------- | ------------------------------------------------------------------------------------------------------------------ | | Devices inventory | **Export**, **Delete Selected**, **Move to Group**, **+ Add device** | | Batteries inventory | **Filters**, **Export**, **Group** column, **+ Add Tag**, paging beyond the first 50 batteries, removing a battery | | Battery details | The **Last Device** link | | Performance | The **Tag** filter | | Sites | **View Floorplans**, the **Active** badge, **Delete** on a site | | Access Points | **Upload Access Points**, **Export** | | Settings | **Save Changes**, **Cancel**, **Timezone**, **Default page size** | | Groups | The trash icon (deleting a group) | | Users | **Export**, removing or editing a user | | Sidebar | **Site View**. On narrow screens, the bottom bar works only for **Dashboard** | ## Pages still to write or rewrite * **Sites**, **Access Points**, **Alerts** and **Trend sparklines** are thinner than the rest of the guide and carry no screenshots. * **My Profile**, reached from the user menu, has no page. * The Performance line chart has no Charts reference page. * Metrics reference pages are missing for **Available Licenses**, **Device Status**, **Call Volume** and **Call Minutes**, **Long Handoff** time, and the **In-Use** and **Daily Usage** figures. * A "Getting the most out of AMIE Advanced" section — task-led guides across screens — is planned but not started. * Screenshots are missing for the **Settings**, **Group Details**, **Groups**, **Users** and **Licenses** tabs and their dialogs. --- # 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.spectralink.net/amie-advanced/appendix/open-items.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.