If you are sure you don’t use that icon it’s probably due to this (from the release notes):
Please note: It is possible that custom integrations (also known as custom components) use deprecated icons. These can throw warnings that need to be addressed in the custom integration.
Speaking of ESPHome. I was using the mdi:hotel icon (now mdi:bed). I updated the ESPHome device config and then had to restart Home Assistant for the change to take effect.
I think I have a more serious issue, Templates do finally load as they did before update with NO modifications.
I timed a restart and it took over 10 minutes to fully load everything and clear the
Home Assistant is starting, not everything will be available until it is finished. message
Supervisor logs show
20-07-23 13:29:16 INFO (SyncWorker_2) [supervisor.docker.interface] Restart homeassistant/raspberrypi4-homeassistant
20-07-23 13:29:16 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Received message 8:1000 is not str
20-07-23 13:29:16 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed
20-07-23 13:29:40 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation in progress
20-07-23 13:29:57 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation done
20-07-23 13:30:02 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation in progress
20-07-23 13:30:12 INFO (MainThread) [supervisor.homeassistant] Updated Home Assistant API token
20-07-23 13:30:18 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation done
20-07-23 13:39:49 INFO (MainThread) [supervisor.homeassistant] Detect a running Home Assistant instance
20-07-23 13:39:50 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
20-07-23 13:39:50 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon
20-07-23 13:39:50 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running