I wasn’t talking to you.
It’s perfect, it laughs at you every time because it’s going to fail.
2 Likes
No but I asked a valid question re the logs as I’d not thought of looking there - or do you mean you are not talking to me full stop? 
Ah ok, not full stop. Just thought you thought I was talking to you.
Those logs are not stored in a file. They are only in memory. You can only access them from the UI.
EDIT: They might be stored as a file in the supervisor container, but getting there would be a bitch… I think.
Seems like I get this:
cmdline: git fetch --depth=1 --update-shallow -v origin
stderr: 'fatal: unable to access 'https://github.com/hassio-addons/repository/': Could not resolve host: github.com'.
What are you running for OS?
well it seems like your nameserver isn’t properly resolving your hostname if you can’t get to github. But you can’t fix that with hassio. And it appears as if it thinks you have the correct hostname. 
Phew 
Ok thanks. Trying to find why my system has suddenly started locking up. Might be to do with the USB SSD 
.
should I open an issue? or anything?
Not sure what would come out of it. It seems to only be your install. It could be anything.
Home Assistant 0.105.2 w/ Supervisor 199
Frontend version: 20200130.2 - latest
I encountered the following three issues so far with this release.
- 1x Nuki errors. It was working with all previous versions.
- 2x User interface issues
Nuki
Fri Feb 07 2020 13:19:11 GMT+0100 (Central European Standard Time)
Setup of lock platform nuki is taking over 10 seconds.
and
Log Details (ERROR)
Fri Feb 07 2020 13:19:21 GMT+0100 (Central European Standard Time)
Error while setting up nuki platform for lock
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 421, in _make_request
six.raise_from(e, None)
File "<string>", line 3, in raise_from
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 416, in _make_request
httplib_response = conn.getresponse()
File "/usr/local/lib/python3.7/http/client.py", line 1344, in getresponse
response.begin()
File "/usr/local/lib/python3.7/http/client.py", line 306, in begin
version, status, reason = self._read_status()
File "/usr/local/lib/python3.7/http/client.py", line 267, in _read_status
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
File "/usr/local/lib/python3.7/socket.py", line 589, in readinto
return self._sock.recv_into(b)
socket.timeout: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 449, in send
timeout=timeout
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 720, in urlopen
method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
File "/usr/local/lib/python3.7/site-packages/urllib3/util/retry.py", line 400, in increment
raise six.reraise(type(error), error, _stacktrace)
File "/usr/local/lib/python3.7/site-packages/urllib3/packages/six.py", line 735, in reraise
raise value
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 672, in urlopen
chunked=chunked,
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 423, in _make_request
self._raise_timeout(err=e, url=url, timeout_value=read_timeout)
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 331, in _raise_timeout
self, url, "Read timed out. (read timeout=%s)" % timeout_value
urllib3.exceptions.ReadTimeoutError: HTTPConnectionPool(host='192.168.2.242', port=8080): Read timed out. (read timeout=20)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 159, in _async_setup_platform
await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/nuki/lock.py", line 55, in setup_platform
devices = [NukiLock(lock) for lock in bridge.locks]
File "/usr/local/lib/python3.7/site-packages/pynuki/pynuki.py", line 188, in locks
for l in self.list():
File "/usr/local/lib/python3.7/site-packages/pynuki/pynuki.py", line 136, in list
return self.__rq('list')
File "/usr/local/lib/python3.7/site-packages/pynuki/pynuki.py", line 122, in __rq
result = requests.get(url, params=get_params, timeout=self.requests_timeout)
File "/usr/local/lib/python3.7/site-packages/requests/api.py", line 75, in get
return request('get', url, params=params, **kwargs)
File "/usr/local/lib/python3.7/site-packages/requests/api.py", line 60, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 533, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 646, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 529, in send
raise ReadTimeout(e, request=request)
requests.exceptions.ReadTimeout: HTTPConnectionPool(host='192.168.2.242', port=8080): Read timed out. (read timeout=20)
UI issues
Furthermore, the available entries of the left side panel are not always updated anymore in portrait mode. I have to twist/turn tablet and/or phone to force reload the remaining entries (portrait to landscape).
Also the upper blue topbar sometimes disappears on smaller screens (ipad 10-11 inch, phone 6.x inch). Normally you will make pull down gesture within the Chrome browser to load the topbar. That is not working anymore.
I’m always in for improvements.
Just a bit sad I have hours of work to get some stuff just like it worked before.
This one seems a real pain… Where I first had a nice visual of lights that are on:
I now get this:
And I’m not sure how to fix this.
So in basic:
Pressing on the tablet puts the gray circle (state-icon) on the screen, pressing on another place will disable the grey background with the weird shaped lighting, and I get to see the icon like it was before…
Home Assistant Core isn’t just HA(C) in a VENV. It’s just the name of the basic core component, which can be installed in many different ways. If installed in a VENV where you don’t have the Supervisor panel, then that note is irrelevant. When it’s part of the larger Home Assistant install (previously called hassio) where you do have the Supervisor panel, then you need the Home Assistant Core piece of that setup to be at least 0.105 to see the new icons.
when trying to update ioperating system in 104.3
20-02-07 18:20:47 WARNING (MainThread) [hassio.hassos] Can't fetch versions from https://github.com/home-assistant/hassos/releases/download/3.9/hassos_ova-3.9.raucb:
20-02-07 18:20:47 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished coro=<HassOS.update() done, defined at /usr/src/hassio/hassio/hassos.py:149> exception=HassOSUpdateError()>
Traceback (most recent call last):
File "/usr/src/hassio/hassio/hassos.py", line 160, in update
int_ota = await self._download_raucb(version)
File "/usr/src/hassio/hassio/hassos.py", line 110, in _download_raucb
raise HassOSUpdateError()
hassio.exceptions.HassOSUpdateError
upgrade (now from 104.3 to 105.2)
Stuck with this error message
2020-02-07 20:34:02 ERROR (SyncWorker_18) [concurrent.futures] exception calling callback for <Future at 0x7f5516607410 state=finished returned NoneType>
Traceback (most recent call last):
File "/usr/local/lib/python3.7/concurrent/futures/_base.py", line 324, in _invoke_callbacks
callback(self)
File "/usr/local/lib/python3.7/asyncio/futures.py", line 365, in _call_set_state
dest_loop.call_soon_threadsafe(_set_state, destination, source)
File "/usr/local/lib/python3.7/asyncio/base_events.py", line 732, in call_soon_threadsafe
self._check_closed()
File "/usr/local/lib/python3.7/asyncio/base_events.py", line 479, in _check_closed
raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed
2020-02-07 20:34:02 ERROR (SyncWorker_13) [concurrent.futures] exception calling callback for <Future at 0x7f550f64df90 state=finished returned NoneType>
Traceback (most recent call last):
File "/usr/local/lib/python3.7/concurrent/futures/_base.py", line 324, in _invoke_callbacks
callback(self)
File "/usr/local/lib/python3.7/asyncio/futures.py", line 365, in _call_set_state
dest_loop.call_soon_threadsafe(_set_state, destination, source)
File "/usr/local/lib/python3.7/asyncio/base_events.py", line 732, in call_soon_threadsafe
self._check_closed()
File "/usr/local/lib/python3.7/asyncio/base_events.py", line 479, in _check_closed
raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed
2020-02-07 20:34:02 ERROR (SyncWorker_2) [concurrent.futures] exception calling callback for <Future at 0x7f551582d7d0 state=finished returned NoneType>
Traceback (most recent call last):
File "/usr/local/lib/python3.7/concurrent/futures/_base.py", line 324, in _invoke_callbacks
callback(self)
File "/usr/local/lib/python3.7/asyncio/futures.py", line 365, in _call_set_state
dest_loop.call_soon_threadsafe(_set_state, destination, source)
File "/usr/local/lib/python3.7/asyncio/base_events.py", line 732, in call_soon_threadsafe
self._check_closed()
File "/usr/local/lib/python3.7/asyncio/base_events.py", line 479, in _check_closed
raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed
The context was the ability to see the new icons in the Supervisor panel. There’s no such thing in Core (as anyone who runs the generic docker or venv version can attest) so the original statement should’ve simply been this:
Please note, you need to be running Home Assistant
Core0.105 to see the new icons.
Indisputably true; the Supervisor panel (and its new icons) is a feature of Home Assistant (The Artist Formerly Known As Hass.io), not Core.
I feel that’s a moot point because if you install Home Assistant 0.105 it will, by default, contain Core 0.105 (and not some other version). To see those new Supervisor icons, you need to be running Home Assistant 0.105.
I feel that’s a moot point because if you install Home Assistant 0.105 it will, by default, contain Core 0.105 (and not some other version). To see those new Supervisor icons, you need to be running Home Assistant 0.105.
I guess the entire picture isn’t clear, at least to me. AFAIK, Home Assistant is now a combination of Home Assistant Core, Supervisor, maybe OS (is the alternative install on generic Linux of [formerly hassio] considered Home Assistant now?). In any case, what is the version of Home Assistant now? Does it align with Core, Supervisor, OS, or something else?
Anyway, maybe not a topic for discussion on the release notes. Maybe just need to wait until things are finalized and the picture becomes more clear.
Hi,
I’ve updated to 105.2 using docker image but I get a lot of error:
home-assistant | return schema(data)
home-assistant | File "/usr/src/homeassistant/homeassistant/helpers/config_validation.py", line 659, in validator
home-assistant | value = config[key]
home-assistant | TypeError: string indices must be integers
home-assistant |
I have a buch of other errors like this. It looks like all the include_dir_merge_list are failing since update
Any Idea ?
Is there any documentation on the updated configuration panel (especially the devices section). I’m looking to see how I’d need to label/update my automations to show up next to the devices they affect/use.