Lovelace in yaml mode "Custom element doesn't exist"

Configuration
1

Good day, Community!
I am trying to show a custom “weather-card”, downloaded using HACS. Card sources are located to the path: “/home/homeassistant/.homeassistant/www/community/weather-card”. But Lovelace does not see her.
Снимок
My config files:
configuration.yaml

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Text to speech
tts:
  - platform: google_translate

lovelace:
  mode: yaml

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml


# Light control on the kitchen
#light: !include kitchen_leds.yaml
switch: !include KITCHEN/switches.yaml
sensor: !include KITCHEN/sensors.yaml

ui-lovelace.yaml

title: Home Assistant
resources:
  - url: /local/community/weather-card.js

views:
  - path: default_view
    title: Главная
    panel: true
    badges:
      - entity: binary_sensor.updater
      - entity: person.aleksei
      - entity: sun.sun
    cards:
      - type: horizontal-stack
        cards:
          - type: 'custom:weather-card'
            entity: weather.home_assistant
            number_of_forecasts: '5'
            hourly_forecast: false
.
.
.

I tried to use different paths to the “weather-card.js” file:

  • url: /local/weather-card.js
  • url: /hacsfiles/weather-card.js
  • url: /local/weather-card.js

resources:

  • url: /local/weather-card.js
    type: js

But none of this works. Please tell me what am I doing wrong?

2

Solution: remove all characters “similar” to space and insert spaces manually …
I spent a lot of time on this. It is very uncomfortable. It would be nice to do configuration based on JSON, for example - it would be much more convenient …

3

Can you explain the solution more? Where did you have to remove and re-add “spaces”?

I’m having the same issue with ha-card-weather-conditions. Seems too weird to be a coincidence?

4

Me too having the same problem with custom ha-card-weather-conditions.
I opened an issue about this, hoping the developer will fix it asap.
Do you know how, in the meantime, to downgrade to previous release?