Error 0:0 Uncaught every time

Configuration
21

I don’t have any, I use HACS and the installed modules goes into lovelace resources.
Are things configured both in lovelace resources and in configuration. yaml ?

22

I don’t know, I followed the instructions.

UPDATE: it looks like we have to choose!

There is stated “While card-mod can be installed as a lovelace resource, some functionality will benefit greatly from it being installed as a frontend module instead.”

… instead …

23

So, I can safely remove the resources? I saw there’s HACS parameter at the entry:

Screenshot_20230307-183725
Screenshot_20230307-1837251080×2340 145 KB

24

Yeah as long as it’s in your configuration.yaml then you can remove from resources

1 Like
25

I dont have any extra_url in my configuration yaml. Just references in the dashboard.
You can prevent the messages with setting up logger to the following:

logger:
  default: warning
  logs:
    #on every access from the mobile app there is an unought error. we dont want this
    frontend.js.latest: critical

Hope this will get fixed :slight_smile:

pOpY

26

Removing the resources broke cards that used it (error cannot find card type, something like this), even though I have the extra_module_url in the configuration.yaml. So, I put them back.

Removed the extra_module_url from the configuration.yaml doesn’t cause issue, but it doesn’t fix the Uncaught error.

27

Thank you my friend, that was the problem.

One week now, and error looks gone :+1:

1 Like