Closed osnwt closed 1 year ago
Post a minimal test card where you faced the issue.
type: entities
entities:
- type: custom:template-entity-row
entity: input_number.health_charge_threshold
I see no issues (Chrome, Win10):
Works in iOS Companion App as well. Cannot test in Safari.
Not sure this is a correct way:
frontend:
extra_module_url:
...
- /hacsfiles/lovelace-template-entity-row/template-entity-row.js
I saw neither until some update. Well, it seem the only way is to try on a fresh system.
As for the correct installation way, it was taken from here: https://github.com/thomasloven/lovelace-template-entity-row
Then from here: https://github.com/thomasloven/lovelace-card-mod#installing
Would be great to update the manual where it suggests to install it as a module, but below shows an example of installation as a resource.
Then from here: https://github.com/thomasloven/lovelace-card-mod#installing
That was about card-mod.
Btw, I myself using HACS, no issues...
But that was also about "installing as a module", no?
And this worked few months with no issues.
As for the correct installation way, it was taken from here: https://github.com/thomasloven/lovelace-template-entity-row
That's a different thing https://www.home-assistant.io/dashboards/dashboards/#resources
Wow, it was a bit confusing due to different configs where both refer to a "module":
lovelace:
resources:
- url: /hacsfiles/lovelace-template-entity-row/template-entity-row.js
type: module
frontend:
extra_module_url:
- /hacsfiles/lovelace-card-mod/card-mod.js
But after changing like above, everything now works!
Thanks a lot!
Since one of past updates my dashboard stopped showing template rows. Nothing was changed/added to the configuration.
Console shows series of the following errors:
Interesting, sometimes it still shows all, and no such errors logged. But most of the time it does not work.
Tested with MacOS Safari and MacOS Chrome - exactly the same issue.
Do you have any ideas why it can misbehave? If not, I should try to bisect versions and try to find the one caused this change. But maybe it's something already known.
All cards installed as modules:
In Safari: