Renamed the HA host PC - HA still discovers the old PC name
Home Assistant is running as a VM on a Windows PC. I had initially named my Window host PC "HomeAssistant-PC" and had installed HASS.Agent. I renamed the Windows PC "HASS-PC" (shorter name). I uninstalled HASS.Agent from the Windows PC and cleared all directories (I think) and reinstalled. But Home Assistant continues to show "Discovered / HomeAssistant-PC / HASS.Agent / ADD IGNORE" and after manually adding "HASS-PC" to HASS.Agent it shows the "HASS-PC" as unavailable. Also, I see this (see below) in the logs for "HomeAssistant-PC" which may be a clue (?). I've deleted all entries in MQTT related to "HomeAssistant-PC" but entries come back. So, I'm guessing there is something I have not properly cleaned from HASS-PC.
Logger: homeassistant.config_entries Source: config_entries.py:855 First occurred: 4:03:31 PM (1 occurrences) Last logged: 4:03:31 PM
Error unloading entry HomeAssistant-PC for notify Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 855, in async_unload result = await component.async_unload_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/notify/init.py", line 126, in async_unload_entry return await hass.data[DATA_COMPONENT].async_unload_entry(entry) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in async_unload_entry raise ValueError("Config entry was never loaded!") ValueError: Config entry was never loaded
Solution
Never mind. I just restarted Home Assistant (again - not for the 1st or 2nd time) and now it sees "HASS-PC" not "HomeAssistant-PC". So, I think the problem is resolved. Sorry for the premature post.