hui-weather-forecast-card: TypeError: o.setConfig is not a function

[Mariusthvdb]

The problem

Inspector showing this error:

Environment

• Home Assistant Core release with the issue: 0.111.2
• Last working Home Assistant Core release (if known): not sure
• Operating environment (Home Assistant/Supervised/Docker/venv): Home Assistant
• Integration causing this issue:
• Link to integration documentation on our website:

Problem-relevant configuration.yaml

Traceback/Error logs

Additional information

though most of the time inspector errors arise on a separate view, this errors show even when not a single forecast card is currently displayed. Not sure what yaml to post because of that.

Seems to happen in Safari/Mac, dont see it in Chrome

[bramkragten]

I guess this is some custom thing, can you try disabling all custom?

[Mariusthvdb]

isn't this the core weather-forecast card ?

I am not aware of any custom card with this name, nor am I using this in eg an entities card, with the prefix hui: and suffix -card or as hui_element: at all...

only using this card like:

  - type: weather-forecast
    entity: weather.openweathermap

the 2 other weather integrations in my setup: dark_sky and buienradar

still, today I havent seen this anymore, without changing anything to these cards/configs. Maybe it was a cache thing, that got cleaned up during several restarts.

let me please check this for another day or so, and Ill close if not re-appearing?

[bramkragten]

I highly doubt that stack trace is correct. Click the filename top right and see where it takes you.

[Mariusthvdb]

got it back again, on a page with the same error, but in a markdown card:

clicking that takes to:

on another page with a markdown card, I get this:

without a red card in the frontend.

[bramkragten]

Seems like it is hui-element.js

[Mariusthvdb]

ok, Ill ask Thomas about this then. Puzzling thing is the relation with the hue-weather-forecast-card though. Would you have any lead on how that could be originated?

[bramkragten]

We made some changes to source mapping that might cause to not always be right, not sure.