Error 0:0 Uncaught every time

Ricks88 · December 22, 2021, 10:16am

2021-12-22 11:09:43 ERROR (MainThread) [frontend.js.latest.202112200] https://homeassistant.local:8123/lovelace/overzicht?homescreen=1:0:0 Uncaught
Hello,

I keep getting these error messages, every time i open home assistant page. or app.

I can not find where they are coming from:

2021-12-22 11:09:43 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.browser_mod_e7ad451e_9671929b (<class 'custom_components.browser_mod.sensor.BrowserModSensor'>) implements device_state_attributes. Please report it to the custom component author.

2021-12-22 11:10:33 ERROR (MainThread) [frontend.js.latest.202112200] https://homeassistant.local:8123/lovelace/overzicht:0:0 Uncaught

And when logging in to the app:

2021-12-22 11:18:13 WARNING (MainThread) [homeassistant.helpers.entity] Entity sensor.browser_mod_fcdfe6e0_8f8db666 (<class 'custom_components.browser_mod.sensor.BrowserModSensor'>) implements device_state_attributes. Please report it to the custom component author.
2021-12-22 11:18:15 ERROR (MainThread) [frontend.js.latest.202112200] https://192.168.1.100:8123/m-lovelace/overzicht?external_auth=1:0:0 Uncaught

What do they mean, and can i fix them?

Aleksei_Piatkin · December 29, 2021, 8:54am

same here

dapuzz · January 1, 2022, 10:57pm

The warning is not related. Can you paste the complete error?

I have this one:

2022-01-01 23:45:15 ERROR (MainThread) [frontend.js.latest.202112200] http://192.168.178.90:8123/frontend_latest/core.47513876.js:1:6969 TypeError: n.callback is not a function. (In ‘n.callback(s.event)’, ‘n.callback’ is undefined)

Is it the same?

Ricks88 · January 3, 2022, 11:35am

its all i can see:

2022-01-03 12:28:05 ERROR (MainThread) [frontend.js.latest.202112290] https://homeassistant.local:8123/lovelace/overzicht?homescreen=1:0:0 Uncaught
2022-01-03 12:28:11 ERROR (MainThread) [frontend.js.latest.202112290] https://homeassistant.local:8123/lovelace/overzicht?homescreen=1:0:0 Uncaught
2022-01-03 12:34:54 ERROR (MainThread) [frontend.js.latest.202112290] https://homeassistant.local:8123/lovelace/overzicht?homescreen=1:0:0 Uncaught

drjjr · January 11, 2022, 1:08pm

I get the same error whenever I refresh a lovelace panel. Been getting it for a long time. Doesn’t matter which dashboard I refresh.

2022-01-11 07:07:09 ERROR (MainThread) [frontend.js.latest.202112291] http://192.168.0.21:8123/system-monitor/system?kiosk:0:0 Uncaught

Sjorsa · January 14, 2022, 6:02pm

Same issue here, even when I make a completely empty fresh panel, even on different dashboards.

paulius2k · January 26, 2022, 7:21am

Something is cached, which does not work normally anymore.
Do a complete reload of the dashboard page with SHIFT+F5.

pOpY · April 23, 2022, 2:46pm

Same issue here, mutliple lines of

2022-04-22 20:34:34 ERROR (MainThread) [frontend.js.latest.202204050] https://homeassistant.local:8123/lovelace/0?external_auth=1:0:0 Uncaught
2022-04-22 20:34:34 ERROR (MainThread) [frontend.js.latest.202204050] https://homeassistant.local:8123/lovelace/0?external_auth=1:0:0 Uncaught

Any hints i can solve the issue?

thx

sender · September 4, 2022, 6:16pm

BUMP

https://myurl/lovelace/start?external_auth=1:0:0 Uncaught

HA_n00b · February 10, 2023, 3:47pm

BUMP

Logger: frontend.js.latest.202302020
Source: components/system_log/__init__.py:254
First occurred: 10:41:50 (15 occurrences)
Last logged: 16:27:22

* https://ha.XXXXXX.net/lovelace/default_view?external_auth=1:0:0 Uncaught
* http://192.168.XXX.204:8123/lovelace/default_view:0:0 Uncaught

robertjan · February 27, 2023, 12:28pm

BUMP

Logger: frontend.js.latest.202302020
Source: components/system_log/init.py:254
First occurred: 26 februari 2023 om 13:23:49 (48 occurrences)
Last logged: 13:19:45
"

*********:8123/lovelace-tablet/0?hide_sidebar:0:0 Uncaught
*********/lsc2-priscilla/0?kiosk:0:0 Uncaught
*********/lovelace/0:0:0 Uncaught"

conorlap · March 6, 2023, 10:37pm

+1 for this!

Edit: removing duplicates from both lovelace resources & configuration.yaml (extra_module_url) solved my issues!

miky_italy · March 7, 2023, 9:06am

Here too.
On every view, if I refresh the browser, the error appears.

miky_italy · March 7, 2023, 9:10am

Found the problem, in lovelace resources I had a duplicate, deleted it, and now no more errors

pOpY · March 7, 2023, 9:36am

Can you please go into detail how you solved the issue?

miky_italy · March 7, 2023, 10:07am

Use browser, 3 dots on the top right, edit dashboard, again 3 dots, manage resources
Look for duplicates.

HA_n00b · March 7, 2023, 12:09pm

There’s no duplicate in my case, and still this issue popping up from time to time.

conorlap · March 7, 2023, 12:21pm

Do you have any cards added under ‘frontend’ in your configuration.yaml?

Example:

frontend:
  extra_module_url:
    - /local/community/frigate-hass-card/frigate-hass-card.js

HA_n00b · March 7, 2023, 3:30pm

Yes I do, but this is normal I think.

conorlap · March 7, 2023, 3:45pm

If they only exist in your configuration.yaml it’s fine but if the same cards are also referenced under Dashboard Resources then I think it causes issues.