Frontend error on logfile?

Configuration
1

Never seen this before:

2018-01-31 19:32:54 ERROR (MainThread) [frontend.js.latest.201801300] :0:0 Script error.
2018-01-31 19:32:54 ERROR (MainThread) [frontend.js.latest.201801300] :0:0 Script error.
2018-01-31 19:32:55 ERROR (MainThread) [frontend.js.latest.201801300] :0:0 Script error.
2018-01-31 19:32:55 ERROR (MainThread) [frontend.js.latest.201801300] :0:0 Script error.
2018-01-31 19:32:56 ERROR (MainThread) [frontend.js.latest.201801300] :0:0 Script error.
2018-01-31 19:32:56 ERROR (MainThread) [frontend.js.latest.201801300] :0:0 Script error.
2018-01-31 19:32:56 ERROR (MainThread) [frontend.js.latest.201801300] :0:0 Script error.
2018-01-31 19:32:57 ERROR (MainThread) [frontend.js.latest.201801300] :0:0 Script error.
2018-01-31 19:32:57 ERROR (MainThread) [frontend.js.latest.201801300] :0:0 Script error.
2018-01-31 19:32:57 ERROR (MainThread) [frontend.js.latest.201801300] :0:0 Script error.
2018-01-31 19:32:57 ERROR (MainThread) [frontend.js.latest.201801300] :0:0 Script error.
2018-01-31 19:32:57 ERROR (MainThread) [frontend.js.latest.201801300] :0:0 Script error.
2018-01-31 19:33:01 ERROR (MainThread) [frontend.js.latest.201801300] :0:0 Script error.
2018-01-31 19:33:01 ERROR (MainThread) [frontend.js.latest.201801300] :0:0 Script error.
2018-01-31 19:33:01 ERROR (MainThread) [frontend.js.latest.201801300] :0:0 Script error.
2018-01-31 19:33:03 ERROR (MainThread) [frontend.js.latest.201801300] :0:0 Script error.
2018-01-31 19:33:04 ERROR (MainThread) [frontend.js.latest.201801300] :0:0 Script error.

0.62.1

2

same errors here… 0.62.1

3

ditto.
not much to go on either…

4

got the same error. also with 0.62.1.
it seems that the log file fills with every click on the left panel, of the front end.

5

It can’t reproduce this when clicking on any tab on the left of the frontend.
I must say that I didn’t have this error since a day or two now.

6

anyone seen these flooding the log:

/frontend_latest/core-41bb07102212e1ea8b6668370a877b92.js:1:6881 TypeError: undefined is not an object (evaluating 't.attributes')

02
02933×693 140 KB

1 Like
7

I am now getting this after upgrading to 0.63.0 :frowning:

8

Seems the errors can be generated by some chrome extensions, if anyone else has these errors try disabling your extensions one at a time until you find the offending one.

9

i see a multitude of these errors, and not using Chrome…

10

You are using Firefox?

11

Safari, macOS, Hassio, 0.62.1

12

Try Firefox, see if the issue persists.

13

same problem here

TypeError: undefined is not an object (evaluating ‘t.attributes’)

0.63.3 macOS Safari

14

I’m getting the same error in chrome. 0.63.2. It only occurs when switching tabs inside Overview and the main tabs on the left. My errors seem to be linked to the custom ui. Seems like there was a .js update causing these possibly?

http://xxxxxxxxxxxxx/local/custom_ui/state-card-custom-ui-es5.html:1:2871 Uncaught TypeError: Cannot read property ‘querySelectorAll’ of null

15

I have the same problem on chrome

16

TypeError: undefined is not an object (evaluating ‘t.attributes’)

Problem is still occurring on macOS (v. 10.13.3) using Safari (v. 11.0.3) with Home Assistant (v. 0.65.5).

17

On mine it seems to be whenever I click reload groups in the frontend, I get 10 of the error lines each time I do that. I don’t see any missing functionality or anything, but the errors are worrisome.

18

On mine it seems to be whenever I click reload groups in the frontend, I get 10 of the error lines each time I do that.

Yup, same here.

19

I’m seeing the error in latest Safari, latest macOS whenever I load in the frontend interface; swapping tabs from and back to it will generate the error.

20

Same here, I get a lot of these errors
ERROR (MainThread) [frontend.js.latest.201804010] :0:0 Script error.
after reloading the groups.

When I open HA using http://localhost:8123/states?latest the errors are gone :thinking: