/lovelace/start:0:0 Uncaught - Where to start to get rid of this error?

Configuration Frontend
1

I keep getting this in my logging. Where can I get this gone?

Logger: frontend.js.latest.202101277
Source: components/system_log/__init__.py:190
First occurred: 1:17:45 PM (2 occurrences)
Last logged: 1:42:25 PM

http://192.168.1.142:8123/lovelace/start:0:0 Uncaught
2

Hate to reply to self… but is there anyone able to direct me?

3

Restart the host, and its done :wink:

4

Nope not done

5

@sender I have had the same error for a few days now. Don’t know what is causing it…

Question: did you deinstall anything in the last few days/weeks?

6

Nope did not

7

Ever get rid of this? I have it also.

8

Same here, can’t seem to get rid of it.

9

Add me to the list. Difficult to debug with so little info.

10

Having the same issue as well.

11

Having the same.
Any way to get rid off it?

12

same here /10char

13

…/lovelace?homescreen=1:0:0 Uncaught

Yep. Steady stream. There are a few topics relating to this, none of them seem to have any answers.

14

I also have this and think it’s to do with the large update to the browser_mod component. Did anyone else update that?

15

Getting this error a lot.
Do not have browser_mod.
Using Chrome (Win10x64).

16

I have it now as well. Cannot access HA remotely or via the duckdns domain. Only able to connect via http://homeassistant.local:8123. Have restarted, issue remans. Was working fine this morning. Frustrating.

Could this be the problem? From nginx log…

[1/30/2022] [3:22:08 PM] [SSL      ] › ✖  error     Error: Command failed: /usr/bin/certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation  
Challenge failed for domain [domain].duckdns.org
Failed to renew certificate npm-1 with error: Some challenges have failed.
All renewals failed. The following certificates could not be renewed:
  /etc/letsencrypt/live/npm-1/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
    at ChildProcess.exithandler (child_process.js:308:12)
    at ChildProcess.emit (events.js:315:20)
    at maybeClose (internal/child_process.js:1048:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
17

I have it as well. The browser console reports an issue which says, that mod-card have already been loaded. But I declared the component definitely only once

To whom it may concern, I solved the issue.
Check this: everytime when reload a dashbord I have uncaugt errors · Issue #11494 · home-assistant/frontend (github.com)

18

This doesn’t work for me. I have a single template for all custom buttons since I started using this component, still getting this. Not sure if it’s related to the button or a camera glance view. I guess I’ll have to disable different elements to get to the one triggering this.

19

I have this problem too, for quite some time:

Logger: frontend.js.latest.202301040
Source: components/system_log/__init__.py:256
First occurred: 8:35:59 PM (2 occurrences)
Last logged: 8:35:59 PM

http://192.168.1.8:8123/lovelace/default_view:0:0 Uncaught

I think the people who developed Home Assistant should step in and provide some guidance on how to track down these issues. HA is a fine tool, but in way too many situations it throws error messages that does not contain any clue as to why, what or where. It’s almost becoming like Microsoft:

Something went wrong!

20

I am getting this exact error. Just started a couple of weeks ago. Anyone find a fix?
thanks