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
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.
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.
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.
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.