Closed ghost closed 5 years ago
Need to correct above: Also raw editor is not usable - no file gets opened and screen stays empty.
I was able to replicate your initial issue, in that the UI editor does not show the badges once a null has been inserted. However, I'm not able to replicate the inability to open the raw editor.
Replicating the first one already is good, right? I will try to check the other issue. Probably it was temporary. It happened twice to me. I suggest to potentially split the two issues. I an happy to investigate further and create a new ticket when having more details. Whatbis your preferred way?
I think it is good as is. An issue with the badges UI editor
Possibly related; compute-unused-entities fails if a badge is null as it doesn't check for undefined before trying to access the entity
@bigcookie commented on Mar 19, 2019, 6:03 PM UTC:
Home Assistant release with the issue: 0.89.1
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.): Docker
Component/platform: Lovelace UI
Description of problem: By accident I had a badge entered through the configuration UI (enable view configuration by tapping top right corner and select configuration), then click "edit" icon for view, click "Badges" tab, add badge entity. I was able by deleting and adding to have an "empty entity" field between the already entered and the last entity. Saving works and an empty badge is shown in the UI at the correct place. When now entering the configuration UI to change the badges, the list is completely empty - no entity is shown, nor is a field shown to enter a new entity. I selected as next step the "raw configuration access" - the shown file was empty. Reloading the page still kept the error for the UI configurator, but I could access the raw configuration and remove the badge entity ith value "- null". Now all works again.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant): view raw configuration lines (copied only the first lines) - issue is in fourth last line, which I removed to make it work again.Traceback (if applicable): n.a.
Additional information: The issue came most likely due to timing/refresh/updating issues and I was too fast. Request is: when saving, HA should not store badges with "null" value.
This issue was moved by MartinHjelmare from home-assistant/home-assistant#22190.