Why Won't My Home Assistant Integration Work?
- Integration not installed/added
- Discovery blocked (network/mDNS)
- Wrong credentials in the config flow
Problem Description
A Home Assistant integration you installed is not working — devices aren't showing up or the integration shows an error. Verify the integration is properly installed and configured in Settings > Devices & Services. The integration may need API keys, credentials, or specific network access. This guide covers checking installation status, credentials, and logs.
Why This Happens in Real Homes
An integration that isn't working usually comes down to one of a few things: it's not actually added, HA can't discover or reach the device, or the credentials in the config flow are wrong. Custom integrations also have to be installed via HACS before they appear to add.
Start in Settings > Devices & Services: confirm the integration is added, and if discovery fails, check HA and the device are on the same network/VLAN with mDNS not blocked. Enter credentials carefully, restart HA after adding, and verify your specific device model is supported; the logs pinpoint the rest.
Symptoms
- Devices not showing up
- Integration not in the list
- Discovery fails
- Config flow errors
- Some devices missing
- Integration greyed out
- No entities created
- Works partially
Recognize these? Here's what usually causes it.
Common Causes
- Integration not installed/added
- Discovery blocked (network/mDNS)
- Wrong credentials in the config flow
- Device not on the same network/VLAN
- Custom integration not installed via HACS
- HA needs a restart
- Unsupported device/model
- Version mismatch
Most fixes happen in the first 3 steps.
Check HA Community forums for known integration issues after updates.
Tools & Requirements
These tools will help you complete this fix.
As an Amazon Associate we earn from qualifying purchases.
Step-by-Step Solution
Verify the integration is properly installed
Go to Settings > Devices & Services. Check if the integration appears in the list. If not, it may not be installed. Click Add Integration and search for it. Some integrations require configuration.yaml entries rather than UI setup — check the Home Assistant documentation for the specific integration. HACS integrations require downloading from HACS first and restarting Home Assistant before they appear in the Add Integration search.
Check for version compatibility
Some integrations require specific Home Assistant versions. After a major Home Assistant update, an integration may break until the integration developer releases a compatible version. Check the integration's GitHub repository or documentation page for version requirements. For HACS integrations, check the repository's issues tab for reports of breaking changes. For core integrations, check the Home Assistant release notes for known breaking changes.
Review the configuration
Many integration issues stem from configuration errors. Go to the integration page and click Configure (or Reconfigure). Verify all settings: API keys, IP addresses, usernames, ports. Common mistakes: using HTTP instead of HTTPS (or vice versa), wrong port number, API key with leading/trailing spaces copied from a website, or using a token that expired. For YAML-configured integrations, use Developer Tools > YAML > Check Configuration to validate syntax.
Check device firmware and compatibility
Some integrations require specific firmware versions on the hardware device. For example, older Shelly firmware may not support the newer Gen2 API that the Home Assistant integration expects. Update the device firmware through the manufacturer's app or web interface. After updating, reload the integration in Home Assistant. Also check if the specific product model is supported — not all models from a brand are covered by every integration.
Remove and re-add the integration
If the integration is stuck in a broken state: go to Settings > Devices & Services > click the integration > three-dot menu > Delete. This removes the integration and all associated entities. Then re-add it fresh: Add Integration > search and configure. This creates a clean configuration without leftover state from the previous setup. Note: removing the integration deletes entity history and any automations referencing those entities need to be updated with the new entity IDs.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.
Place your hub in a central location in your home, elevated off the floor and away from your WiFi router by at least 3 feet. This provides the best Zigbee and Z-Wave signal coverage to all corners of your house.
Home Assistant issues that only appear after restart are a well-known quirk — triggers that require prior state history simply can't fire until that history rebuilds.
- Integration not installed/added
- Discovery blocked (network/mDNS)
- Wrong credentials in the config flow
- Device not on the same network/VLAN
- Custom integration not installed via HACS
Before you go — try one of these (they fix most cases).
Most popular upgrades chosen by Home Assistant owners.
Home Assistant Connect ZWA-2 | Connect Z-Wave devices to ...
Zooz 800 Series Z-Wave Long Range GPIO Module ZAC93 LR (U...
Home Assistant Connect ZBT-2 | Connect Zigbee, Thread, or...
As an Amazon Associate we earn from qualifying purchases.
Official Manufacturer Manual
Home Assistant provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Home Assistant.
Source: home-assistant.io
Need More Help? Home Assistant Support
Note: The contact information below connects you directly to Home Assistant's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.
