Home Assistant VLC integration removed is exactly what happened in the 2026.9 release: it needed direct access to a machine's audio hardware, something that only worked on the deprecated standalone Core install method. If your media_player entity vanished after updating, the fix is to set up the separate VLC via Telnet integration instead.
Why does the VLC integration disappear after updating?
- The old VLC integration is gone, not broken: Home Assistant 2026.9 removes it outright from Core rather than deprecating it gradually, so the entity and its config entry stop working the moment you update.
- It depended on direct hardware access: the integration ran VLC's Python bindings against the local sound card, which only made sense on the old standalone Core installation method that most users have already moved away from in favour of Home Assistant OS or Supervised.
- Nobody was maintaining it for modern installs: Home Assistant OS, Container and Supervised installations run in isolated environments without a shared audio device, so the integration had been quietly unusable for most people well before it was pulled.
Does this affect the VLC via Telnet integration too?
No — VLC via Telnet is unaffected and is the supported replacement. It talks to VLC over its network telnet interface instead of touching audio hardware directly, so it works identically on Home Assistant OS, Container, Supervised and Core installs. If you already use VLC via Telnet for a different player, nothing changes for you; this removal only affects the plain VLC integration.
Fix 1: Enable VLC's telnet interface
On the machine running VLC (a PC, NAS or media server, not Home Assistant itself), open VLC's preferences and turn on the telnet interface: Tools > Preferences > Show settings: All > Interface > Main interfaces, tick Telnet, then set a password under the Lua section (or the Telnet sub-section, depending on your VLC version). Restart VLC after saving. If you run VLC headless via the command line, add --extraintf telnet --telnet-password yourpassword to the launch command instead. Confirm it worked by opening a terminal and running telnet <vlc-host> 4212 — if you get a password prompt, the interface is live.
Fix 2: Open the right port and set an English locale
VLC's telnet interface listens on port 4212 by default, so add a firewall rule on the VLC host allowing inbound connections on that port from your Home Assistant server's IP address. Separately, if VLC is running on a non-English locale, volume commands sent over telnet can fail silently because of decimal separator differences between locales — Home Assistant's own documentation recommends setting the VLC host to an en_US locale before launching VLC to avoid this. You'll know it worked if volume slider changes in Home Assistant actually move VLC's volume rather than doing nothing.
Fix 3: Add the VLC via Telnet integration in Home Assistant
In Home Assistant, go to Settings > Devices & services > Add integration, search for VLC media player via Telnet, and enter the host address, port and the password you set earlier. Home Assistant creates a new media_player entity for it — this will have a different entity ID from your old VLC entity, so update any dashboards, scripts or automations that referenced the old one by its exact entity ID. You'll know the fix worked when the new entity shows VLC's current playback state and responds to play/pause/volume commands from the Home Assistant media player card within a second or two.
What can't VLC via Telnet do that the old integration could?
The main gap is media type support: VLC via Telnet's media_player.play_media action only supports the music media type for now, so if you were pushing video files or streams directly through Home Assistant automations, test that specific workflow after migrating rather than assuming parity. Playback, pause, volume, seeking and now-playing metadata all work the same as before. If your setup leaned heavily on casting video content rather than controlling a music player, a dedicated Google Cast integration or a Kodi-based setup may fit better than either VLC integration.
How do you stop this kind of breakage catching you out again?
Read the breaking changes section of each release before updating, not after — Home Assistant lists every removed or changed integration at the top of its monthly release post, and the 2026.9 release also dropped the vacuum battery_level property and renamed several LLM tool names, so VLC wasn't the only entity worth checking. Take a full backup from Settings > System > Backups before every update so you can roll back in seconds if an integration you depend on turns out to be affected. We cover the rest of what changed, including the new Matter network map and security dashboard alerts, in our full Home Assistant 2026.9 breakdown, and if media playback is a bigger part of your setup than just VLC, our Home Assistant media player guide covers the other integrations worth knowing.
