Homeassistant.loader still loading zha when removed from configuration.yaml

I am running HA on Docker and using a VirtualBox VM for testing, pulling the same config files used on my production instance. As I don’t have a zigbee radio connected to the test rig I wanted to reduce the spurious errors in the logs so I removed the following section from my configuration.yaml file

zha:
  usb_path: /dev/ttyUSB1
  database_path: /config/.storage/zigbee.db

However I still get the following items in the log:

INFO (SyncWorker_1) [homeassistant.loader] Loaded zha from homeassistant.components.zha

ERROR (MainThread) [homeassistant.config_entries] Error setting up entry /dev/ttyUSB1 for zha
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/serial/serialposix.py", line 290, in _reconfigure_port
    orig_attr = termios.tcgetattr(self.fd)
termios.error: (25, 'Not a tty')

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
<snip>
  File "/usr/local/lib/python3.7/site-packages/serial/serialposix.py", line 293, in _reconfigure_port
    raise SerialException("Could not configure port: {}".format(msg))
serial.serialutil.SerialException: Could not configure port: (25, 'Not a tty')

I don’t understand how the loader is still even trying this service if I removed it from the config. Is this setup being ghosted elsewhere on my system?

Check your integrations, it’s probably still installed. The new install method uses the ui and stores the config in .storage, not configuration.yaml. I ran into this when I moved to an rpi4.

ahh, yes, thanks for the pointer @PrairieSnpr - I found that information repeated inside the .storage folder in the core.config_entries file so I did used the following command, restarted and all was fine.

mv .storage/core.config_entries{,.`date +%y%m%d`}