System Setup
- PC: Windows Server / Windows 10 system
- HASS.Agent Version: Latest (2022.14.0)
- Home Assistant Version: Core 2025.10.0 (Supervisor on qemux86-64)
- MQTT Broker: Mosquitto (core-mosquitto, port 1883)
- Integration: HASS.Agent integration installed via HACS
- Goal: Use PC’s default speakers (ceiling speakers) as a Home Assistant
media_playerfor TTS and automation playback - Problem: HASS.Agent connects fine via MQTT and shows all sensors/buttons, but no media_player entity ever appears.
What Works
- HASS.Agent connects successfully to MQTT broker
- MQTT discovery messages publish correctly for all sensors/buttons
- PC is visible in HA under MQTT → Devices
- Local API (port 5115) responds (
http://localhost:5115/api/infoand/api/connectionreturn “Method Not Implemented,” confirming listener is up) - Satellite Service shows Running under Windows Services
- Other functions (buttons, sensors, hotkeys, commands) appear and work normally
What Doesn’t Work
- No
media_playertopic ever publishes to MQTT (homeassistant/media_player/WIN-XXXX/config) - No
media_playerentity ever created in Home Assistant - “Enable Media Player Functionality” in HASS.Agent doesn’t trigger MQTT publish
- Re-enabling or restarting HASS.Agent doesn’t help
- Local API access works but doesn’t register to HA
- Tried both MQTT mode and Local API mode — neither registers
Fixes / Steps Already Tried
- Verified HASS.Agent integration installed via HACS (latest version)
- Removed and re-added integration multiple times
- Updated Home Assistant core, supervisor, and all add-ons
- Verified Mosquitto credentials and connection (
mosquitto_subtest confirms comms) - Checked discovery prefix (
homeassistant) matches on both ends - Toggled Media Player ON/OFF, saved config, restarted HASS.Agent
- Manually installed and verified
HASS.Agent.Service.exe(Local API service) is running - Confirmed Windows Firewall allows inbound/outbound TCP 5115
- Restarted both HASS.Agent app and HA several times
- Ran
ha supervisor repair,ha core restart, and confirmed supervisor healthy - Verified via
ha resolution infothat all checks pass - Tried both MQTT autodiscovery and manual configuration
- Confirmed via
mosquitto_subthat all button topics appear — still no media player topic - Verified Windows audio output devices (Realtek speakers are default and functional)
Observed Behavior
- HASS.Agent publishes topics like:
homeassistant/button/WIN-XXXX_ToggleClouds/config
but never publishes:
homeassistant/media_player/WIN-XXXX/config
- The Media Player tab in HASS.Agent only shows an enable checkbox — no device output selector
- Accessing
http://localhost:5115/api/mediareturns “Connection refused” - Attempting to reinstall or repair HASS.Agent Service sometimes yields “path not found”
Goal
I just want Home Assistant to detect my PC’s default speakers (via HASS.Agent) as a media_player entity for automations (TTS, doorbell sounds, ambient playback), without breaking my other audio setups like the rainforest background loop.
Questions / Help Needed
- Why won’t HASS.Agent publish the
media_playerdiscovery topic even when MQTT + Local API are working? - Is there a known version mismatch between HASS.Agent (2022.14.0) and the HACS integration?
- Can the media_player entity be forced manually (via MQTT discovery)?
- Could the Windows Server environment or audio session permissions block the registration?
- Any reliable workaround (DLNA, Browser Mod, etc.) to route HA audio through local PC speakers permanently?
Screenshots / Diagnostics
ha resolution info+ha supervisor infoconfirming system healthy- MQTT logs showing button/sensor topics but no media_player topic
localhost:5115test page results- Windows Services showing HASS.Agent Satellite Service running
- Audio output list (Realtek speakers = default)
Summary
Everything in HASS.Agent works perfectly except the media_player entity.
MQTT and Local API are healthy, integration installed, all discovery topics publishing except the one that actually creates the media player.
Would really appreciate any insight from anyone who’s dealt with this — or confirmation if this feature is currently broken with the latest builds.