Depends.
Currently I am not using UI for automations, helpers, template sensors.
As for integrations: some integrations now only have UI config - so I have to use UI config.
But I would choose yaml.
The reasons are:
With UI config I cannot use packages. Period. So this is a huge loss in functionality for me.
So, in short - I will keep using yaml as long as possible.
Yeah I still see it too. It feels slower than it
Used to be. Especially when moving around by different dashboards. I still see the error in those pictures incidentially .
Guys, i have issues with the hassio and supervisor intergration, it takes a long while now when i restart? is this known?
2023-09-07 22:20:08.395 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: hassio
2023-09-07 22:21:08.449 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: hassio
2023-09-07 22:21:08.919 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Supervisor for hassio
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/hassio/__init__.py", line 665, in async_setup_entry
await coordinator.async_config_entry_first_refresh()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 257, in async_config_entry_first_refresh
await self._async_refresh(
File "/usr/src/homeassistant/homeassistant/components/hassio/__init__.py", line 974, in _async_refresh
await self.hassio.refresh_updates()
File "/usr/src/homeassistant/homeassistant/components/hassio/handler.py", line 37, in _wrapper
data = await funct(*argv, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/hassio/handler.py", line 540, in send_command
request = await self.websession.request(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 560, in _request
await resp.start(conn)
File "/usr/local/lib/python3.11/site-packages/aiohttp/client_reqrep.py", line 899, in start
message, payload = await protocol.read() # type: ignore[union-attr]
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/streams.py", line 616, in read
await self._waiter
asyncio.exceptions.CancelledError: Global task timeout
2023-09-07 22:21:08.928 WARNING (MainThread) [homeassistant.bootstrap] Setup timed out for stage 1 - moving forward
Go to Settings > System > Repairs, click the overflow menu (three vertical dots) and select “Integration startup time”.
The list shows all of the integrations that have been loaded (and how long it took to load them). You’ll notice that the list contains far more entries than in Settings > Devices & Services > Integrations.
For example, Automation is an integration, so is Template, Group, Input Boolean, etc. Each has a corresponding web page (like the URL you posted).
My guess is that there was a design decision made to only show integrations (in the Integrations page) where the user has control over their configuration (unlike, for example, the Automation and Template integrations which have no user-configurable options).
i have the exact same error as you, have you resolved it?
Yep it is. Depending on the error (500 on GitHub = ratelimit) it will be auto fixed sooner or later with a restart.
a restart of what ? 
It’s not a problem in our systems or in 2023.9, I think it’s some weird random network issue somewhere. After recent HA restart the error is gone. But if I restart again, it probably will appear again…
IMO if some communication issue happens (as CRC error timeout etc), HA stops querying modbus registers. It’s needed to to call service modbus restart. My previous version was 2023.8.2; it worked well.
Hmm…i see, but I don’t agree about the configuration; they are configurable:
Ah…I just found out…they are also mentioned under helpers, and can also be added there 
I was doing it under intergrations 
Looks like an awesome update. Nothing that couldn’t have been done before but now with a lower barrier. That’s great. HA is very powerful and increasingly usable but still has a steep learning curve. Making it available to more people is a good thing.
Home Assistant. Just wait an hour
Does the new weather.forecast service poll the underlying provider, or a local cache that is updated on its own provider specific frequency? I’m limited to a maximum number of calls per day to openweathermap.
The entities you create via the Template integration are configurable. The Template integration itself is not configurable (nor is Automation, Input Boolean, etc and the others that aren’t displayed in the Integrations page).
They’ve been “missing” ever since the Integrations page was created (i.e. a long time ago); it has the earmarks of being by design rather than oversight.
If you feel strongly about it, post a Feature Request to have all of the loaded integrations listed in the Integrations page.
Use the modern format for template sensors and use icon.
Edit: Just realised you are probably talking about in the GUI.
Check DNSBL (and dnsbl logs) in pfsense - It has a whitelisting capability also. I had enabled it and took awhile to discover what was blocking some updates - /pfblockerng/pfblockerng_dnsbl.php in your pfsense instance.
New climate stuff in the Overview is cool and I can see it on my mini-split. But unfortunately this update no longer sees my Ecobee. Simply “unavailable.”
Try with
mdi
{% else %}
{% if (is_state xxxxxx
mdi
{% else %}
{% if (is_state xxxxxx
mdi
{% endif %}