Resolving errors in HA logs

Every so often I revisit the logs to find a host of new errors. My HA configuration is more or less steady-state in that I have the automations and integrations I want and don’t think I’ll be adding any more anytime soon. I do come up with a need for a new template sensor now and again, and sometimes I’ll tweak a Node-RED flow if I find a need to. None of this should contribute to HA errors or warnings, but they crop up and as they do I’d like to take care of them.

Here’s one that I’m seeing and I don’t know why:

Logger: frontend.js.latest.202203012
Source: components/system_log/__init__.py:190
First occurred: March 29, 2022, 9:29:00 PM (23 occurrences)
Last logged: 7:50:00 AM

https://xx.xx.xx.xx:xxxx/config/dashboard:0:0 Uncaught
https://URL:xxxx/front-door-tablet/main_front_door_tablet:0:0 Uncaught
https://URL:xxxx/frontend_latest/core.7854b248.js:1:9245 Uncaught Error: Suspend promise not set
https://URL:xxxx/frontend_latest/app.b83d2076.js:850:203632 Error: Failed to execute 'define' on 'CustomElementRegistry': the name "button-card-action-handler" has already been used with this registry
https://URL:xxxx/front-door-tablet/front_door_camera_front_door_tablet:0:0 Uncaught

These URLs are all pointing to different in-use Lovelace views. Not sure where they’re coming from.

I thought maybe we could post up HA errors in this thread and help each other resolve them.

Check the Frontend GitHub repository for any existing reports of the same problem. If none exist, consider reporting it there (because that’s where developers track and fix reported bugs).

1 Like

Thanks–looks like this was reported on core-2022.2.8. I’m on core-2022.3.8, so it’s likely still being worked.