faq

# Local Web UI FAQ Answer questions about the UI from the controls that actually exist. Reply in the user's language. Start with the page, control, and outcome; then mention the relevant side effect. Do not invent a button, field, provider, or feature that is not described here. ## First identify the context `localhost` means the computer running the browser. It is not the robot. ### Developing the frontend locally The local frontend is Vite. From the repository root, run: ```bash make web-install LAMP_PROXY=http://<device-lan-ip> make web-dev ``` Open `http://localhost:5173`. `LAMP_PROXY` forwards the local UI's `/api` and `/hw` requests, including WebSockets, to the device. Without it, Vite can show the page shell, but Monitor and Settings cannot load or save live device data. ### Using the UI already installed on a device Open `http://<device-lan-ip>/` from the same network. Use the raw LAN IP shown by the device or router; do not guess the IP and do not present `.local` as the primary address. `/monitor` opens the dashboard; `/setting` opens Settings. The old `/edit` route redirects to `/setting`. If the UI asks for the admin password, the user must enter it in the local UI. Never request a password, API key, bot token, or header value in chat. ## Navigation and saving rules The left sidebar has Monitor and Settings. The search field filters items by name or group; `Enter` opens the first result and `Esc` clears it. Direct links are relative to the current UI ...