These are my choices:
Feature requests (Don’t post feature requests in the issue trackers. Thanks!)
Issue tracker Home Assistant Core
Issue tracker Home Assistant Frontend
Issue tracker Home Assistant Supervisor
Issue tracker Home Assistant Operating System
Issue tracker website & documentation
Not sure which is considered main?
Home assistant core
Core - Core is the heart of all of this.
Frontend - Lovelace, the UI
Supervisor - the Supervisor, for the thing previously called Hass.io and now called Home assistant
Operating system - previously HassOS, the OS for the Supervisor images
Website - well, not that 
You didn’t have to tag me to get that message across champ. I got your point. I hope you understand mine.
Fantastic set of updates! Especially the NOT condition and HomeKit cameras.
Added my cameras, but have noticed the CPU on my HASS server is in overdrive. Anyone else or is this to be expected?
Thanks
Just doing a clear cache hard reload fixes this.
I understand this and I opened an issue under core. What I don’t understand whether the issue is a front end issue as the frontend is not opening correctly. When I shutdown and restart I assume nothing new is installed. It is like something is not stopped and started correctly on an update? Shutdown stops and starts everything. This has worked every time for me since .103. Ha host reboot works sometimes.
Wow, 0.110 break everything and stuck in the safe mode… thanks and my wife is throwing a fit, a great way to ruin my morning.
EDIT: The culprit is Custom Header that was installed with HACS and I had to remove it for now.
All is well.
I know it can be frustrated from time to time. Why do you rely so much on a system that is still in beta? If I where you I would not update right away when a release hit the streets if it’s so important to you.
I got everything working until I try to access via web, once I do, it crashes, with this error:
2020-05-20 10:27:09 ERROR (MainThread) [root] Uncaught exception
Traceback (most recent call last):
File "av/container/output.pyx", line 22, in av.container.output.close_output
File "av/container/core.pyx", line 267, in av.container.core.Container.err_check
File "av/error.pyx", line 328, in av.error.err_check
File "av/container/pyio.pyx", line 39, in av.container.pyio.pyio_write_gil
TypeError: 'NoneType' object is not callable
I’m getting the following error:-
Invalid config for [alarm_control_panel.manual]: [pending_time] is an invalid option for [alarm_control_panel.manual]. Check: alarm_control_panel.manual->pending_time. (See ?, line ?).
alarm_control_panel:
- platform: manual
name: Alarm
code: !secret alarm_control_panel_manual_code
code_arm_required: false
pending_time: 30
delay_time: 0 #20
trigger_time: 4
disarmed:
trigger_time: 0
armed_home:
arming_time: 0
delay_time: 0
If I change ‘pending_time: 30’ to ‘arming_time: 30’ as per the release notes and restart, the alarm_control_panel disappears from home assistant.
The guide here https://www.home-assistant.io/integrations/manual has this as a suggested configuration:-
alarm_control_panel:
- platform: manual
name: Home Alarm
code: '1234'
pending_time: 30
arming_time: 30
delay_time: 20
trigger_time: 4
disarmed:
trigger_time: 0
armed_home:
arming_time: 0
delay_time: 0
What am I missing or is this a bug with the alarm_control_panel in 0.110?
Thanks
Remove pending_time entirely from your config. You should only be using arming_time
Tried a incognito window to rule out a browser cache issue, same error. Also hassio ha container reboot, same error.
Nice work, faster loads, ISY integration was seamless no issue just worked, love the not feature-removed a ton from my automations, I need to find a calendar, and custom header needs to be updated but overall so far it is looking good.
I’ll post anything else I find as I work through everything.
Thank you guys.
Daikin AC not working
Logger: homeassistant.components.daikin.config_flow
Source: components/daikin/config_flow.py:77
Integration: Daikin AC ([documentation](https://www.home-assistant.io/integrations/daikin), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+daikin%22))
First occurred: 11:31:47 PM (1 occurrences)
Last logged: 11:31:47 PM
ClientError
Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 967, in _create_direct_connection traces=traces), loop=self._loop) File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 830, in _resolve_host self._resolver.resolve(host, port, family=self._family) File "/usr/local/lib/python3.7/site-packages/aiohttp/resolver.py", line 30, in resolve host, port, type=socket.SOCK_STREAM, family=family) File "/usr/local/lib/python3.7/asyncio/base_events.py", line 792, in getaddrinfo None, getaddr_func, host, port, family, type, proto, flags) File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run result = self.fn(*self.args, **self.kwargs) File "/usr/local/lib/python3.7/socket.py", line 752, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno -2] Name does not resolve The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/daikin/config_flow.py", line 77, in _create_device password=password, File "/usr/local/lib/python3.7/site-packages/pydaikin/daikin_base.py", line 75, in factory await appl.update_status(appl.HTTP_RESOURCES[:1]) File "/usr/local/lib/python3.7/site-packages/pydaikin/daikin_base.py", line 168, in update_status self.values.update(await self._get_resource(resource)) File "/usr/local/lib/python3.7/site-packages/pydaikin/daikin_base.py", line 144, in _get_resource return await self._run_get_resource(resource) File "/usr/local/lib/python3.7/site-packages/pydaikin/daikin_base.py", line 155, in _run_get_resource async with self.session.get(f'http://{self._device_ip}/{resource}') as resp: File "/usr/local/lib/python3.7/site-packages/aiohttp/client.py", line 1012, in __aenter__ self._resp = await self._coro File "/usr/local/lib/python3.7/site-packages/aiohttp/client.py", line 483, in _request timeout=real_timeout File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 523, in connect proto = await self._create_connection(req, traces, timeout) File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 859, in _create_connection req, traces, timeout) File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 971, in _create_direct_connection raise ClientConnectorError(req.connection_key, exc) from exc aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 192.168.1.163,:80 ssl:None [Name does not resolve]
Well none of my picture or header pictures are showing anymore didnt see anything to do with images in breaking changes.
Yes, it is set correctly. HA is in sync.
Headers on entity card show up if you edit the card then save but as soon aas you refresh the page they disappear again.
I have this same problem. If I enter in to configure UI and then close, it’s back to 3 columns but if I close and reopen in Chrome, it’s back to two. Did you resolve this? I’ve cleared cache, just in case.