Rapha

@jbtrystram , if you manually edit the .js file. you probably need to delete the .gz file. Also, don't forget to clear your browsers cache. It should work.

I just noticed it now, that is true. But when I made the PR, 10 months ago, HomeAssistant didn't have rounded corners on the cards, so that was no issue...

I just pushed a new commit to fix the border radius issue as well  No sharp corners anymore.

I can attest the issue that moya described is reproducible for me as well, same behavior, the cursor jumps one char. Another issue I found on top of that, is...

I got so frustrated by this. I have more bulbs still on the box to be installed, and now I have second thoughts on my support to the brand, I...

I've done more testing, I disabled HomeAssistant polling entirely to isolate the testing behavior. I've found that the V2 api endpoint is much more sensitive to being slow. Even on...

This issue was gone for a while but now is back again. Same behavior as the original post. My HomeAssistant is set to only poll the affected devices (V2 api,...

That is related to the pigbacking solution to have a UI editor for the card. The workaround solution is to EDIT another card, a regular vertical-stack. then come back to...

Actually, after spending time filling the bug and reading through the debug logs, I figured a workaround: to include `verify_ssl: false` inside the `form_submit` block ```yaml multiscrape: - resource: 'https://host/sensors'...

Maybe a better approach to not spam the code base with documentation commits and PRs, and also to take advantage of some github features, it would be better to do...