Jeff Brown

I noticed this in the beta release notes. Not sure whether it is relevant but it sounds superficially related: https://developers.home-assistant.io/blog/2024/04/25/always-reload-after-successful-reauth-flow/

I observed this today while trying out the extension for the first time. I got a double echo at first, then I got a triple echo (!) after unplugging the...

Yup, that sounds like what I’m seeing. Is there any way the firmware could be improved to recover from loss of the client? Perhaps an upper bound on how long...

I'm glad you like it. I'm somewhat tempted to hard fork the project and publish a new version under a different name and I'd like to contact the original author...

Oh that’s weird. I haven’t observed this behavior before. What cards are you putting into the template? Anything interesting in the logs?

How strange! I'm sorry, I'm unable to reproduce this issue. I'm on the same version of Home Assistant so what browser are you using? I'm on Chrome.

@iceboundflame I've uploaded a new version 1.0.4 with an attempt to fix the issue by treating the incoming config object as immutable. I don't know why I can't reproduce it...

I've already posted the release. You might need to ask HACS to update the repository information. https://github.com/j9brown/decluttering-card/releases

I've done that and more over here: https://github.com/j9brown/victron-hacs (I'll have to look into submitting some pull requests. I just made these changes for my own benefit.)

Switching forks should maintain history. Home Assistant has no way to distinguish where the code came from. Here’s how I would do it: - Make a full backup of Home...