**HYBRID VOICE EVALUATION LAB SYSTEM* Testing Strategies, Output Procedures, and Final Evaluation Report Templates*
PART 1: ENGINEERING LAB TEST STRATEGY
1.1 Rationale for the Hybrid Lab Ecosystem
This laboratory strategy establishes a repeatable framework for measuring the performance of a voice pipeline bridging consumer-grade hardware with localized backend infrastructure. By utilizing a Google Home Mini as a satellite and routing timing checkpoints through Google Cloud Stations alongside Local Home SDK execution blocks, we can isolate latency variances introduced by token authentication, wide-area network routing, and private container execution environments (hosted within Proxmox VE). This benchmarking paradigm serves to inform production tradeoffs between open-source models (Whisper/Piper) and standardized mass-market audio engines.
1.2 Hybrid Network & Topology Pathing
The audio path initiates at the Google Home Mini array. The local wake-word trigger kicks off telemetry metrics. The signal travels via WAN to Google Home Cloud Cloud-to-Cloud stations, executing timing hooks before passing the intents down to the private Proxmox Linux Bridge (vmbr) interfaces. Here, local voice components (Home Assistant, Wyoming, Piper) take over to handle underlying device states, before routing the acoustic response payload back to the hardware device.
PART 2: STEP-BY-STEP LAB OUTPUT PROCEDURES
Procedure 2.1: Timing Calibration & Video Prep
1. Synchronize the Proxmox local host and your network routers to a Stratum-1 NTP server.
2. Spin up a millisecond console clock on a test-bench screen using: watch -n 0.05 date +"%T.%3N"
3. Focus the lab camcorder to cover the status LED of the Google Home Mini and the timing monitor.
Procedure 2.2: Telemetry Capture Sequence
Execute these capture loops on the Proxmox host to catch the incoming Cloud Station packets:
# Capture incoming WAN execution intents hitting the
private bridge interface
tcpdump -s 0 -nn -w /tmp/google_hybrid_run.pcap -i vmbr1
port 10400 or port 8123
# Monitor microsecond container group execution
metrics
while true; do echo "$(date +%s.%N) $(cat
/sys/fs/cgroup/lxc/[HA_CT_ID]/cpu.stat | grep
usage_usec)" >> /tmp/proxmox_cpu.log; sleep 0.02;
done
PART 3: SAMPLE RUN EVALUATION & FINAL REPORT
Below is an official sample execution report generated under the prescribed lab guidelines. This serves as a master template for tracking comparisons across divergent hardware platforms and model depths.
| Test Execution ID | RUN-2026-HYBRID-004 |
|---|---|
| Physical Satellite | Google Home Mini (Gen 1 Hardware Matrix) |
| Timing Engine | Google Home Setup / Cloud Stations Pipeline |
| Private Backend Environment | Proxmox VE v8.x / LXC Isolated Containers |
| AI Models Under Evaluation | Whisper-Base (STT) / Piper-Medium (TTS) |
3.1 Core Telemetry Timeline Delta Breakdown
| ID | Milestone Checklist | Absolute Timestamp (NTP Source) | Delta (ms) | Source Log Channel |
|---|---|---|---|---|
| T0 | Vocal Wake Word Concluded | 12:04:15.000 | 0 | Camcorder Audio Profile |
| T1 | On-Device Processing & Light Trigger | 12:04:15.220 | 220 | Camcorder Video Frame |
| T2 | Cloud Station Handshake Received at Host | 12:04:15.540 | 320 | Wireshark Packet Log |
| T3 | Proxmox HA Container CPU Micro-Spike | 12:04:15.565 | 25 | Host Cgroup System Metrics |
| T4 | Intent Executed / Return Payload Emitted | 12:04:16.115 | 550 | Wyoming Container Output |
| T5 | Speaker Emits Audio Feedback Response | 12:04:16.435 | 320 | Camcorder Audio Profile |
3.2 Performance Visualization & Architecture Comparisons
Based on data visualized through stacked metrics, the total voice-to-voice execution loop clocked at 1,435 milliseconds. The primary delay remains within the Cloud Station processing pipeline (T2 - T1 = 320ms) and the regional Whisper processing envelope (T4 - T3 = 550ms). Conversely, the Proxmox virtual backend layer showed minimal overhead, indicating highly efficient inter-container routing.