Stuck on "Loading data" since update to 0.61

Configuration
1

I am unable to load the front end since updating to 0.61. I’m running Home Assistant on a Raspberry Pi (Raspbian) using the pip installer.

This is the error I am getting:

2018-01-16 19:52:04 ERROR (MainThread) [aiohttp.access] Error in logging
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/helpers.py", line 554, in __get__
    return inst._cache[self.name]
KeyError: 'remote'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/helpers.py", line 521, in log
    for key, value in fmt_info:
  File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/helpers.py", line 513, in <genexpr>
    for key, method in self._methods)
  File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/helpers.py", line 473, in _format_a
    ip = request.remote
  File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/helpers.py", line 556, in __get__
    val = self.wrapped(inst)
  File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/web_request.py", line 321, in remote
    peername = transport.get_extra_info('peername')
  File "/usr/lib/python3.5/asyncio/sslproto.py", line 306, in get_extra_info
    return self._ssl_protocol._get_extra_info(name, default)
  File "/usr/lib/python3.5/asyncio/sslproto.py", line 546, in _get_extra_info
    return self._transport.get_extra_info(name, default)
AttributeError: 'NoneType' object has no attribute 'get_extra_info'

Other threads like this one and this one suggest removing any mention of Broadlink Switches. I do use these so took them out my config but alas I still have the issue.

Does anyone else have this or have any ideas?

2

Hi @Dullage

I get exactly that error in the log now, but I am able to load the front end.
It looks like I mainly get that error when closing the browser.

I have no idea what the issue could be, all appears to be working ok in my case, just that the log gets bigger unless I clear it out manually regularly

3

:disappointed_relieved: this inconsistency make trouble shooting harder.

I’m going to try creating a new db file, that tends to fix a lot of things. I’ll report back shortly…

1 Like
4

Nope. A rebuild of the db file had no effect :cry:.

5

oh :frowning:

I have been looking in to a potential lead with encryption and using a domain name to access. Do you use either / both?

6

Yup both. SSL (LetsEncrypt) on a custom domain.

7

ah, same here

so similarities:

hassbian build
raspberry pi
updated to 0.61
SSL with LetEncrypt
custom domain

not sure how this helps right now, but I am testing an updated config

just shutting down now, will empty log, start up, then report back

1 Like
8

I just had another scan of the reported issues and can’t see anything.

9

ok, so the good news is, my installation still works, the bad news is that it did not stop the errors

basically I had in my configuration.yaml for base_url domain.com:8123, but in reality I use domain.com:1234 (a different port).
I updated the port in the base_url to match what I actually browse to, but it did not stop the errors

no idea where to next

10

There were several other platforms which had the same issue as broadlink which was causing this.

todoist, snapcast, and mopar. Do you have any of those?

11

for me, no

12

Yeah, actually the log suggests a different issue than what broadlink was showing.

13

I only get entries in the log after I close the browser
then I get a new set of the entry above

14

I have a similar setup as well. I use iptables to route traffic across ports.

Yes I do, Snapcast and I have also seen:

2018-01-16 19:07:01 ERROR (MainThread) [homeassistant.loader] Unable to find component snapcast

I’ll try disabling that.

Where did you spot this @anderson110?

15

It was discussed in the pull request on github that fixed the broadlink problem.

https://github.com/home-assistant/home-assistant/pull/11677

1 Like
16

I have my front end back :smiley:!

Albeit without Broadlink and Snapcast. The latest step of disabling Snapcast seemed to do it.

I still have that same error in the log though.

17

I am not sure I fully understand that, but if the updated .py files were the only platforms / components with the issue with the Domain, I don’t use any of those, so at least my issue is probably not that

18

@anderson110, do you get a new error in the log as above, each time your close your browser?
sorry, meant for @Dullage

19

Yup. I’ve just tested this and it does seem to be logged upon browser closure.

20

ok great (I think :slight_smile: ) at least we are pretty consistent with each other in our installations and time or new error in log

where now? :slight_smile: