VIZIO SmartCast
vizio
The VIZIO SmartCast integration allows you to control SmartCast-compatible TVs and sound bars (2016+ models) locally from Home Assistant.
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
media_player | TV | Needs its own HomeKit Bridge in accessory mode |
remote | TV remote (activities) | Needs its own HomeKit Bridge in accessory mode |
binary_sensor | Sensor (motion, contact, leak, smoke…) |
1 report below say how a device from this integration behaves in the Home app.
What people report
Vizio SmartCast TVs work over the local API, but firmware or integration changes in 2026.9 broke setup on older models until patched.
- Works3
- Partly works2
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Older Vizio SmartCast TVs (two models) | Works | Setup failed in 2026.9.0 after remote platform added; fixed in 2026.9.1Saved copyThe problem After updating to HA 2026.9.0, the Vizio SmartCast integration fails to set up for two older Vizio TV models, while a newer model (V405-H9) works fine on the same network. The integration shows "unable to connect" during setup, even though the TV's port 7345 is reachable (TCP connect succeeds). This appears to be caused by the new remote platform added in PR #165820, during setup, `get_remote_keys_list()` likely fails because the `vizaio` library connects to port 443 instead of the configured port, crashing the entire integration setup (not just the remote entity). ### What … Excerpt saved from GitHub on 2026-10-23. | Issue #181309 · 2026-09 | |
| Vizio M65Q7-H1 | Works | Would not integrate; fixed in 0.118.1Saved copyThe problem Purchased a new Vizio TV, model number M65Q7-H1. I followed the VIZIO integration steps and used pyvizio on my Mac to connect and generate an authentication token for my new TV. I added the contents to the config.yaml. After restarting, I was able to see the VISIO card pop up in the integrations page (there was no automatic pop up in the integration page prior to adding the config). It was filled out properly with the IP address, port, and authentication token that was provided from pyvizio. However, when I click submit, I get "Failed to connect" in red text under the name section … Excerpt saved from GitHub on 2026-10-23. | Issue #43375 · 2020-11 | |
| Vizio V405-H9 | Works | Worked fine on 2026.9.0 while older models failedSaved copyThe problem After updating to HA 2026.9.0, the Vizio SmartCast integration fails to set up for two older Vizio TV models, while a newer model (V405-H9) works fine on the same network. The integration shows "unable to connect" during setup, even though the TV's port 7345 is reachable (TCP connect succeeds). This appears to be caused by the new remote platform added in PR #165820, during setup, `get_remote_keys_list()` likely fails because the `vizaio` library connects to port 443 instead of the configured port, crashing the entire integration setup (not just the remote entity). ### What … Excerpt saved from GitHub on 2026-10-23. | Issue #181309 · 2026-09 | |
| Vizio SmartCast TVs | Partly works | Queries scfs.vizio.com for app names; blocking it breaks setup, maintainer says mostly localSaved copyThe problem pyvizio tries to query App Names by querying `scfs.vizio.com` which is in the Cloud, not Local. When access to `scfs.vizio.com` is blocked the Vizio integration fails to initialize and logs this error: ``` Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 444, in async_setup result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/vizio/init.py", line 72, in async_setup_entry await coordinator.async_config_entry_first_refresh() File … Excerpt saved from GitHub on 2026-10-23. | Issue #110232 · 2024-02 | |
| Vizio TV | Partly works | Partly in Home Wrong state set after update; remote volume stopped working | Exposed to HomeKit for Apple TV remote volumeSaved copy… update (not sure which one) I've been noticing strange issues with the HomeKit integration. I've noticed issues with two separate device types. One being a Vizio TV and one being a Z-wave smart plug. I'm not sure if these are actually separate issues but it feels to me like they might be due to the same root issue. TV The TV is exposed to HomeKit so that I can change the volume in the Apple TV remote app. This has worked great until recently. At first I thought it might be an issue with Vizio since the TV just had a major update but now I'm not so sure. The issue is that any action taken in … Excerpt saved from GitHub on 2026-10-23. | Issue #104643 · 2023-11 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local polling
Talks to the device on your network, asking it for updates every so often.
Found automatically over
- Bonjour (zeroconf)
Details
| Installs (analytics) | 3,959 (0.56%) |
|---|---|
| Quality scale | Platinum |
| Added in | Home Assistant 0.49 |
| Set up in the UI | Yes |
| Maintainers | @raman325 |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
