Xiaozhi ESP32 Server Java

Created By
joey-zhoua year ago
小智ESP32的Java企业级管理平台,提供设备监控、音色定制、角色切换和对话记录管理的前后端及服务端一体化解决方案
Overview

What is Xiaozhi ESP32 Server Java?

Xiaozhi ESP32 Server Java is an enterprise-level management platform developed for the Xiaozhi ESP32 project, providing an integrated solution for device monitoring, tone customization, role switching, and conversation record management.

How to use Xiaozhi ESP32 Server Java?

To use the platform, users need to deploy the server locally or via Docker, connect their ESP32 devices, and access the management interface through a web browser.

Key features of Xiaozhi ESP32 Server Java?

  • Comprehensive device management with real-time monitoring
  • Customizable voice tones and cloning capabilities
  • Role switching for different AI interactions
  • Persistent conversation history management
  • Support for multiple IoT devices and real-time communication

Use cases of Xiaozhi ESP32 Server Java?

  1. Managing smart home devices through voice commands.
  2. Customizing voice interactions for different applications.
  3. Monitoring device status and performance in real-time.
  4. Analyzing conversation data for insights and improvements.

FAQ from Xiaozhi ESP32 Server Java?

  • Can I use this platform for multiple devices?
    Yes! It supports multiple devices connecting simultaneously.

  • Is there a mobile version available?
    The platform is responsive and can be accessed via mobile browsers.

  • What technologies are used in this project?
    It uses Spring Boot for the backend and Vue.js for the frontend, with MySQL and Redis for data storage.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
joey-zhou
Star
476
Language
Java
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago