Any idea what this is trying to tell me?

Configuration
1

I am running 62.1 with Hassio on a Pi2.

I see others are reporting similar stuff…

Everything seems ok, but i am getting a bunch of this in the logs:

2018-02-05 19:58:12 ERROR (MainThread) [frontend.js.latest.201801300] http://xxxxxxxx.duckdns.org:8123/frontend_latest/core-41bb07102212e1ea8b6668370a877b92.js:1:6880 TypeError: t is undefined

I am also getting them for my ip address as well:

2018-02-05 20:40:06 ERROR (MainThread) [frontend.js.latest.201801300] http://192.168.1.6:8123/frontend_latest/core-41bb07102212e1ea8b6668370a877b92.js:1:6880 TypeError: t is undefined
2

I see this errors when i “Reload Groups” in the Configuration Tab.

3

Does the error always end with “TypeError: t is undefined”? or does the “t” spot it spell out a word vertically when combined with the other errors?

4

Always the same:

2018-02-06 17:17:14 ERROR (MainThread) [frontend.js.latest.201801300] http://192.168.xxx.xxx:8123/frontend_latest/core-41bb07102212e1ea8b6668370a877b92.js:1:6880 TypeError: t is undefined
2018-02-06 17:17:14 ERROR (MainThread) [frontend.js.latest.201801300] http://192.168.xxx.xxx:8123/frontend_latest/core-41bb07102212e1ea8b6668370a877b92.js:1:6880 TypeError: t is undefined
...

Looks like the error raises for every group i have.

5

Petro, I will have to look when it happens again. Had not thought of that. I have not triggered it again, but the system does have some kind of small memory leak now after 62.1 and Mosquito addon install. But hey, it will run with the addon and the stock broker hosed my system to the point it would not boot. No errors out of the addon broker. :slight_smile:

6

me too. after it happens, it removes a bunch of groups from my front end until I restart HASS

7

Do you have groups in packages?
I’ve seen this only with packages and had to restart on every group change.
Yesterday i removed all and after “Reload groups” i’ve seen this errors. :slightly_smiling_face:

8

Now that you mention it… my group.all_automations goes away. I have it load on a card so I can enable and disable if I want to. When it happens the card is empty until I reload automations. I have had to reboot once to get them back.

9

nope. not using packages at this time.

10

these are the ones that disappear for me too. I actually lose all the cards that have all_switches, all_lights, all_automations

11

… and all_scripts, all_covers, all_devices.
The groups also disappear from the Dev Tool/states tab.

12

that is certainly strange

13

Ah, I only have the all-autos one exposed on the front end, so I would not have noticed any of the others.

14

Caught this at boot and it failed to boot with the error:

2018-02-06 22:56:49 ERROR (SyncWorker_0) [homeassistant.util.yaml] while scanning for the next token
found character '\t' that cannot start any token
  in "/config/configuration.yaml", line 93, column 41
2018-02-06 22:56:49 ERROR (MainThread) [homeassistant.bootstrap] Error loading /config/configuration.yaml: while scanning for the next token
found character '\t' that cannot start any token
  in "/config/configuration.yaml", line 93, column 41

Not sure what util.yaml would be but the line in my config.yaml at 93 was perfect.

Maybe related?

15

You have a tab in there somewhere, in line 93 maybe?

16

No, just checked that and the lead characters are all spaces… Also the line above.

17

You need to check the end of the line. column 41

18

I did and it is clean… rebooted and the error went away… with no config change.

19

Found an open issue about the group problem.