WebJun 10, 2024 · so did you remove HACS integration, create a new token, and re-add it? I am not sure where I have to input the token! Edit: removed integration, re-added with a new token! WebJun 10, 2024 · Unfortunately when adding a version it caused HACS to flag the Lovelace element as not loaded properly. Removing the version in the Resource definition also fixed the "problem". It seems the HACS logic uses the exact Resource definition string when doing the validation, and does not ignore the version like it should (?) to be in line with …
GitHub - dangreco/threedy: Home Assistant card to …
WebJun 14, 2024 · Installation details Description Value HACS version 1.1.0 aiogithubapi version 1.0.4 Home Assistant version 0.111.2 Installation method for HA venv pip Checklist [ X] I'm running the newest version... WebCould not load tags. Nothing to show {{ refName }} default. View all tags. Name already in use. A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. ... HACS. Frontend > Config Editor Card. Manual. Enable "Advanced Mode" from your user ... t1one - тапочка remix
Installed card is not added to Lovelace resource · …
WebFrontend development WebJun 8, 2024 · I used a custom card and have now deleted it (tried also re-instaling it and delete it again). I have also checked the raw-file for the rotel-card.js entry, and in other pages contain the card, - which it does not. Getting this message in HACS: "Not loaded in Lovelace You have 1 Lovelace elements that are not loaded properly in Lovelace" And … WebJun 7, 2024 · Frontend; Documentation; Bot; Other; Checklist. This Feature Request only contain 1 request (if you have multiple open multiple feature requests). The idea. Mix of feature request and frontend issue. If HACS knows that there are not loaded elements, it would be nice if the not loaded elements would be listed. A good description of what you … t1 on sage