Open robotpandarocket opened 7 months ago
I think this should be fixed by 3.4.0
version 3.4.0 doesn't work well my entire configuration got damaged after the update as well as the log page scrolls like never before
That's impressive. Updating a resource shouldn't change your configuration.
Could you check your configuration as soon as possible or I'll have to stop using it because clsi is pretty useless
I used a configuration based on CSS thanks to the card-mod. However, I updated and the initial configuration was not as before but totally changed. I tried to configure it on a totally empty server with no other configurations and the card mod always had the same problem. while if I use an older version it works correctly
I have no idea what you are trying to say.
You're going to have to show me something.
I don't know if the image is visible, this was before the update
and so after the update :(
I don't know how else to show it to you since I don't know anything about programming
The code (configuration) you're using, perhaps? And in what way that was changed.
My Home Assistant version: 2023.11.2
My lovelace configuration method (GUI or yaml): YAML
What I am doing: casting a dashboard
What I expected to happen: Dashboard to cast, even if the css doesn't render, no errors should be thrown.
What happened instead: Millions of system_log events (see below) swamped my events table (700mb -> 8gb in data base size)
Minimal steps to reproduce: Cast (using built in integration) dashboard with a card_mod card.
Error messages from the browser console:
By putting an X in the boxes ([]) below, I indicate that I:
[] Understand that this is a channel for reporting bugs, not a support forum (https://community.home-assistant.io/).
[] Have made sure I am using the latest version of the plugin.
[] Have followed the troubleshooting steps of the "Common Problems" section of https://github.com/thomasloven/hass-config/wiki/Lovelace-Plugins.
[] Understand that leaving one or more boxes unticked or failure to follow the template above may increase the time required to handle my bug-report, or cause it to be closed without further action.