BTHome Device Not Discovered in Home Assistant

Direct answer: BTHome discovery depends on receiving compatible Bluetooth advertisements; pairing the sensor to a phone is not enough. First verify the device is broadcasting BTHome data, move it close to a known-working Home Assistant Bluetooth adapter or proxy, and confirm the Bluetooth integration is healthy. Then check encryption, duplicate integrations, passive scanning, battery state, and whether a phone connection is suppressing advertisements. Do not delete working Bluetooth devices or reset the sensor until reception is proven.

This guide addresses a BTHome sensor that Home Assistant cannot discover. It is designed to preserve working configuration and evidence before any reset, deletion, or re-pairing. Work in order and stop when the first confirmed cause is corrected. Screens and menu labels can vary by Home Assistant release and installation method.

Symptoms and scope

Use the following signs to decide whether this guide matches your problem. Similar-looking failures can come from different layers, so record what still works as carefully as what fails.

The BTHome setup dialog reports that no devices were found.
The sensor appears in a vendor app but never in Home Assistant discovery.
A previously discovered sensor disappears after deletion and does not return.
The device is visible near one proxy but unavailable through another.
Measurements freeze even though the sensor display continues to change.

Most likely causes, ranked

Start with the causes that fit the evidence. Do not apply every fix at once: simultaneous changes make it impossible to know what solved the problem and can create a second failure.

1. The device is not using BTHome firmware or its broadcast mode is disabled.
2. The advertisement is encrypted and Home Assistant lacks the correct bind key.
3. The sensor is connected actively to a phone or vendor app and is no longer advertising as expected.
4. The adapter or Bluetooth proxy is unavailable, overloaded, too far away, or suffering 2.4 GHz interference.
5. Passive scanning, duplicate Bluetooth software, container permissions, or host hardware prevents reception.
6. The battery is weak, the advertising interval is long, or the device uses a model-specific activation sequence.

Safe diagnostic procedure

Before beginning, make a current backup when the procedure could affect configuration or stored data. Record the Home Assistant version, installation type, device or app version, the first failure time, and the last known working change. Redact secrets from every screenshot and log excerpt.

Step 1: Capture the exact failure

Identify the exact device model, firmware, and broadcasting format. A Bluetooth device is not automatically a BTHome device. Consult the manufacturer or firmware project documentation and confirm BTHome support, broadcast version, encryption status, and any button sequence needed to enable advertising.

Interpretation: if this step changes the symptom, repeat the same controlled test once before moving on. If nothing changes, restore any temporary setting and continue. Keep a short note of the time, action, and result; that record prevents circular troubleshooting.

Step 2: Protect the current state

Open Settings → Devices & Services → Bluetooth and confirm at least one scanner is healthy. Review the Bluetooth integration diagnostics and advertisements rather than assuming the host adapter works because another operating-system tool can see a name. Home Assistant needs usable BLE advertisements.

Step 3: Verify the affected layer

Move the sensor within one or two meters of a confirmed scanner or ESPHome Bluetooth proxy for a controlled test. Remove it from metal cabinets and away from USB 3 devices, Wi-Fi access points, and dense wiring. Wait longer than the configured advertising interval.

Step 4: Test the least-destructive cause

Close the vendor app and disconnect any phone that may hold an active BLE connection. Some devices reduce or stop advertisements during a connection. Disable phone Bluetooth briefly only as a test; do not unpair or reset until you know a phone connection is the cause.

Step 5: Inspect configuration and identity

Replace or test the battery when voltage is uncertain. Clean battery contacts and confirm polarity. A display can remain alive at a voltage too low for reliable radio transmission. After replacement, allow the device to complete its boot and advertisement cycle.

Step 6: Check network, power, or permissions

If encryption is enabled, obtain the bind key through the supported manufacturer or firmware process and enter it only in the proper integration flow. Never paste private keys into a public forum or screenshot. A wrong key may allow discovery while preventing useful measurements.

Step 7: Apply the narrow repair

Check for duplicate ownership. HACS BLE monitors, vendor integrations, operating-system services, or another Home Assistant instance may be consuming or duplicating the same data. Disable only one suspected conflict at a time, document the prior state, and restore it if the test changes nothing.

Step 8: Observe through a full cycle

For container installations, verify the supported Bluetooth access method, D-Bus mapping, permissions, and host adapter. For remote coverage, validate each proxy separately. Do not treat a proxy’s online status as proof that it is forwarding advertisements from this location.

Installation and environment branches

Home Assistant OS or appliance-style installs

New device never discovered: verify firmware format, advertising, proximity, and encryption first.

Container, network, or account variation

Deleted device will not return: check ignored discoveries, stale device entries, encryption, and whether the sensor still advertises; avoid deleting registry files manually.

Partial failure versus complete failure

Device works near the host only: improve proxy placement or RF conditions rather than changing the integration.

Multi-device or multi-hop environments

Multiple scanners report unstable data: examine source switching, proxy latency, duplicate integrations, and signal strength before forcing one path.

What not to do

Do not delete the integration, device, database, app registration, or proxy configuration merely because it is the fastest visible button. Deletion can remove evidence and create new entity identities.
Do not paste passwords, tokens, encryption keys, exact home coordinates, public URLs with credentials, or unredacted logs into a forum or support ticket.
Do not disable firewalls, TLS verification, authentication, or other security controls as a permanent workaround. A useful test must be narrow, timed, and reversed.
Do not make several network, software, and device changes together. Change one variable, observe the result, and keep the working rollback path.
Do not assume a restart is a diagnosis. A restart can temporarily hide timing, memory, radio, storage, or connectivity faults without correcting them.

Verification checklist

Watch the Bluetooth advertisement monitor or integration diagnostics until the device address or identifier appears repeatedly. Add the discovered BTHome device and confirm several fresh measurement changes, not merely a device card. Walk the sensor back to its intended location and observe it through multiple broadcast intervals. Restart Home Assistant and one proxy at a time; the device should recover without manual reconfiguration. Confirm automations use stable entity IDs and that timestamps continue advancing.

The original symptom is gone under the same conditions that previously reproduced it.
The relevant log has no new matching error after a normal update or restart cycle.
Related entities, history, automations, or remote access still work.
The repair survives one controlled restart of the affected component.
Temporary troubleshooting exceptions have been removed or documented.

Rollback and recovery

If a reset is necessary, first record the device model, firmware, bind key, calibration, advertising interval, entity IDs, and automation dependencies. Reset according to the device maker’s instructions, then restore BTHome broadcasting and encryption deliberately. If deletion caused the problem, restore from backup before editing internal registries by hand.

If the evidence points to failing hardware, a vendor outage, an upstream regression, or corrupted data that matters, stop improvising. Preserve the backup and diagnostic record, then escalate with the exact version, timestamp, error, minimal reproduction, and steps already tested. That produces a safer and faster answer than repeated resets.

Prevention

Place proxies for coverage, not merely where power is convenient.
Label and store bind keys securely.
Avoid running overlapping BLE integrations without a clear reason.
Use fresh batteries and realistic advertising intervals.
Keep Bluetooth proxies and Home Assistant versions compatible.
Document the scanner that normally hears each important sensor.

Schedule a brief review after the next Home Assistant update or device firmware change. Confirm that the repaired path still works, remove obsolete workarounds, and update your private documentation. Prevention is most effective when it records why a setting exists, not just its value.

Diagnostic worksheet

For a BTHome sensor that Home Assistant cannot discover, write down five facts before asking for help: the exact error, the first failure time, the last working time, the smallest action that reproduces it, and the layer that still works. Add the Home Assistant Core version, installation type, relevant device or app firmware, network path, and whether the issue survives a restart. This worksheet separates a repeatable defect from a transient outage.

If you observe: The BTHome setup dialog reports that no devices were found

Confirm when this began and whether it affects one entity, one device, one integration, or the whole installation. Compare the result on the same network and, when relevant, through the alternate path. Then use the matching diagnostic step above. Do not jump to recovery until the observation is repeatable or the logs identify the failing layer.

If you observe: The sensor appears in a vendor app but never in Home Assistant discovery

If you observe: A previously discovered sensor disappears after deletion and does not return

If you observe: The device is visible near one proxy but unavailable through another

If you observe: Measurements freeze even though the sensor display continues to change

Frequently asked questions

Should I delete and add everything again?

Usually not. Re-adding can change entity IDs, erase evidence, and hide the original cause. Use it only after backup, documentation, and the narrower checks in this guide.

Can I ignore the error if it starts working again?

A single brief interruption may be harmless, but a recurring error deserves timestamps and logs. Repetition after the same event often reveals a network, storage, power, permission, or token lifecycle problem.

Is updating Home Assistant always the fix?

No. Updates can contain fixes, but they also change dependencies and behavior. Read release notes, back up first, and match the error to a known fix before treating an update as diagnosis.

How much log information should I share?

Share the smallest relevant window around the failure, with secrets and personal data removed. Include versions and the exact action that caused the event. Avoid uploading complete logs publicly.

When should I escalate?

Escalate when safety, important data, repeated corruption, an upstream regression, or an account-side failure is involved, or when the least-destructive checks produce a clear error you cannot resolve.

Sources and review notes

Photo: Tim Witzdam on Unsplash. Last reviewed: September 22, 2026. Official documentation is the authority for supported configuration. Community and issue reports are useful for identifying recurring symptoms but do not prove that every installation has the same cause.

Continue with the Device Unavailable Diagnostic, the Smart-Home Diagnostic Decision Tree, or the Home Assistant Error Decoder when the symptom crosses more than one integration.

BTHome device not discovered in Home Assistant: Bluetooth troubleshooting