Help with an error that I can't seem to track down the cause

Configuration Frontend
1

I keep getting this error in the logs whenever I try to trigger a script to start an irrigation schedule.

Couple things to note that have me scratching my head.

  1. I am on Windows 11 not 10
  2. I have cleared browser cache, I’ve tried incognito mode, and have also used Edge to test instead of Chrome and it still pops the same error each time.

Home Assistant has been restarted for good measure and I’ve gone through HACS to verify there are no duplicate downloads of Mushroom cards and have also redownloaded the latest versions of each.

Logger: frontend.js.modern.202505313

Source: components/system_log/init.py:331

First occurred: 5:51:21 PM (11 occurrences)

Last logged: 6:22:56 PM

Uncaught error from Chrome 137.0.0.0 on Windows 10 Error: Failed to execute ‘define’ on ‘CustomElementRegistry’: the name “focus-trap” has already been used with this registry A.define (src/scoped-custom-element-registry.ts:180:12) /hacsfiles/advanced-camera-card/card-855fd26e.js:75:3686

Uncaught error from WebKit 605.1.15 on iOS 18.5 Error: Failed to execute ‘define’ on ‘CustomElementRegistry’: the name “mushroom-select” has already been used with this registry message (node_modules/core-js/modules/web.dom-exception.stack.js:26:24) src/scoped-custom-element-registry.ts:181:8 /hacsfiles/lovelace-mushroom-better-sliders/mushroom.js:29:67 n (/hacsfiles/lovelace-mushroom-better-sliders/mushroom.js:1:964) module code (/hacsfiles/lovelace-mushroom-better-sliders/mushroom.js:569:67)

Uncaught error from WebKit 605.1.15 on iOS 18.5 Error: Failed to execute ‘define’ on ‘CustomElementRegistry’: the name “focus-trap” has already been used with this registry message (node_modules/core-js/modules/web.dom-exception.stack.js:26:24) src/scoped-custom-element-registry.ts:181:8 module code (/hacsfiles/advanced-camera-card/card-855fd26e.js:75:3692)

Uncaught error from Edge 137.0.0.0 on Windows 10 Error: Failed to execute ‘define’ on ‘CustomElementRegistry’: the name “mushroom-select” has already been used with this registry A.define (src/scoped-custom-element-registry.ts:180:12) /hacsfiles/lovelace-mushroom-better-sliders/mushroom.js:29:61 /hacsfiles/lovelace-mushroom-better-sliders/mushroom.js:29:76 n (/hacsfiles/lovelace-mushroom-better-sliders/mushroom.js:1:963) /hacsfiles/lovelace-mushroom-better-sliders/mushroom.js:569:66

Uncaught error from Chrome 137.0.0.0 on Windows 10 Error: Failed to execute ‘define’ on ‘CustomElementRegistry’: the name “mushroom-select” has already been used with this registry A.define (src/scoped-custom-element-registry.ts:180:12) /hacsfiles/lovelace-mushroom/mushroom.js:23:126 Kr (/hacsfiles/lovelace-mushroom/mushroom.js:1:15090) /hacsfiles/lovelace-mushroom/mushroom.js:286:46391

2

Hello JerryAC,

137.0.0.0 is suspicious…

It is likely supposed to be 127.0.0.0 as that is a reference to the local host machine the software is running on.

Not sure what the 137 thing is but it feels to me like a typo somewhere.

I don’t so Windows, though, so I could be wrong.

3

The PC I’m using to access HA is on Windows. Home Assistant itself is running HASSOS on a Proxmox VM. The 127.x.x would make sense for loopback but not sure how that would also even come into play here.

4

Well 137.0.0.0 is a public address that belongs to the US air force, so that is very likely wrong.

5

i believe the 137.0.0.0 is the Chrome version

2 Likes
6

1000097792
10000977921080×828 104 KB