BT remain unavailable / old issues still in the log

[steffenberthold]

I used BT for pp. one year wihout any problems. Since one week they went "unavailable" and I observed the the real thermostates from Fritz!SmartHome disappeared. The integration did not find any devices anymore. This changed automatically after the upgrade to HA OS Version 17.3 yesterday. Now I see the real thermostates again with same entity names. So far so good, but it seems the BT integration does not recognize them. I deleted all the BTs that I had (7) and began to integrate again. I attach the log from the first one. The set up worked fine but I see the BT "unavailable" while the real thermostate is ok (online, provides values). I checked the log and found nothing strange except at the end an old issue from last week (reg. "Kinderzimmer" - ond of the previous BTs). But there is no such BT anymore, I deleted all today and the only the that I set up is the one you see in the log. I suppose there is still some garbage anywhere? Thank you

Description

Steps to Reproduce

1. delete all BTs, download integration again
2. setup new BT

Expected behavior:

Actual behavior:

BTs are "unavailable"

Versions and HW

Home Assistant:
Better Thermostat:

TRV(s):

Debug data

diagnostic data

{
  YOUR DEVICE DIAGNOSTICS JSON OUTPUT HERE
}

debug log

graphs

Additional Information

[

config_entry-better_thermostat-01KR13W7KRRYVRR4FJQMQAA2XP.json

](url)

[cl445]

Drafted #1998 for the secondary symptom — the stale repair-issue entries that survived deleting a BT instance. async_remove_entry was not implemented, so the invalid_external_temperature_* / invalid_window_state_* / missing_entity_* / degraded_mode_* issues stayed in HA's registry after the BT was gone. The PR cleans them up on entry removal.

The main complaint (newly created BT immediately unavailable while the underlying TRV reports values) is not addressed by that PR. A debug log covering the startup of the affected BT entity would help pin it down — most likely candidates from code reading are the startup() wait loop and the _finalize_startup() call right before _available = True is set.