state_translated - this is nice. Would it be possible to add additional String parameter , something like
{{ state_translated("sun.sun", "custom_message") }}
, so instead of default translation we could use our own custom word/message? If second parameter not defined it could then return default translation.
Thatās already been discussed. I can see it being added sometime in the future. Currently itās not supported. it would look like this state_translated("sun.sun", language='en') or state_translated("sun.sun", 'en')
That is very unlikely anytime soon. However it may be more likely inside timestamp_custom.
This is the first time ever that I couldnāt resist trying the beta on my production instance (and fear the wrath of my significant other 
). Iāve been trying it out some time and I am blown away by the beauty and ease of use of the new sections view.
Kudos to the team for this and all other improvements!
Love to see changes on the dashboard. Hope it will be as good as everything else you guys did in the past.
Will sections be auto populated like the default dashboard right now? Would love to see all areas with their assigned entities.
Canāt wait for all the other dashboard updates! 
The added state_translated function works only with a HA language which is set per a user in HA config. The original plugin of Piotr can give a localized state for another language (should be preloaded, see docs in this repo):
ct_state_translated("sun.sun", "en")
Sometimes it is usefulā¦
Iām not sure it was intended, but I think blank section with no cards visible and blank title should not be a placeholder. Then I can use conditional cards to show certain section or information dynamically. Besides, empty section placeholder doesnāt seem to match design.
And when using conditional cards, itās also a placeholder when it is disabled by not met conditions. It seems clearly not intended and it should be fixed.
Overall, I love the new release.
Strange, first time since several months, ha canāt find the march update. In the GUI, Ā« check for update Ā» doesnāt find anythingā¦ an idea please ? Thank you 
For interest, you can see the state of the builds here
and you can drill down for more detail.
My dashboard has been completed built with yaml as I wanted a title that spanned the page then individual cards underneath. I may need to rethink this approach as the gui and now drag and drop functionality may be winning me over.
have a look at thisā¦
The outliers button is such a small but awesome improvement. I would say I have spent hours in total looking for the erroneous values. So good!
Thank you! I could have sworn I did that, but apparently now. Itās showing up now.
Uneventful update for me.
I like the new script fields.
Alarmo fix has just been released.
Unfortunately no improvement in start up time for me, but it is not HAās fault.
So I ditched the Dahua integration as the dev no longer has time to work on it. A quick look at the core ONVIF integration seemed like it could do what I want. So I added that instead. Now the slowest integration is HAās fault
Still, it improved to under a minute now.
2 replies
Kudos to the UI folks. This is an awesome and lovely QOL feature!
Just to ask quickly; Iām not sure if this is a bug, browser support, 3rd-party extension or documentation wording issue but on Firefox the circled pencil āhandleā appears to be unclickable, the rest of the card is though! Anyone else finding that?
Regards,
K
I just made the mistake of hitting update whilst at workā¦ itās now stuck in a boot loop with not enough time in between for me to gain access to the log. 
EDIT: got a glimpse:
Supervisor log has this-
24-03-07 09:23:41 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:64475 ssl:default [Connect call failed ('172.30.32.1', 64475)]
Hi,
How are you connecting remotely? Nabu Casa? Cloudflare? Companion app?
Edit: fixed autocorrect. āMany Casesā ā āNabu Casaā
1 reply
Anyone else seeing an issue with the local todo list? Since the upgrade all my todo list items got removed and Iām getting the below error in the logs. If i try and recreate the items on the list they donāt get created when i click the add button. But if i open the file config.storage\local_todo.ha_actions.ics i see the items in there
Logger: homeassistant.components.todo
Source: helpers/entity_platform.py:350
integration: To-do list (documentation, issues)
First occurred: 09:25:06 (1 occurrences)
Last logged: 09:25:06
Logger: homeassistant.components.todo
Source: helpers/entity_platform.py:350
integration: To-do list (documentation, issues)
First occurred: 09:25:06 (1 occurrences)
Last logged: 09:25:06
Error while setting up local_todo platform for todo
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/ical/component.py", line 139, in __init__
super().__init__(**data)
File "/usr/local/lib/python3.12/site-packages/pydantic/main.py", line 341, in __init__
raise validation_error
pydantic.error_wrappers.ValidationError: 1 validation error for Todo
__root__
Failed to validate: 20240307T083444, errors: (["Expected DATE-TIME TZID value '+08' to be valid timezone", "Expected value to match DATE pattern: '20240307T083444'"]) (type=value_error)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 350, in _async_setup_platform
await asyncio.shield(awaitable)
File "/usr/src/homeassistant/homeassistant/components/local_todo/todo.py", line 71, in async_setup_entry
calendar = IcsCalendarStream.calendar_from_ics(ics)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/ical/calendar_stream.py", line 82, in calendar_from_ics
stream = cls.from_ics(content)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/ical/calendar_stream.py", line 69, in from_ics
return cls(**result)
^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/ical/component.py", line 139, in __init__
super().__init__(**data)
File "/usr/local/lib/python3.12/site-packages/pydantic/main.py", line 339, in __init__
values, fields_set, validation_error = validate_model(__pydantic_self__.__class__, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/main.py", line 1076, in validate_model
v_, errors_ = field.validate(value, values, loc=field.alias, cls=cls_)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/fields.py", line 895, in validate
v, errors = self._validate_sequence_like(v, values, loc, cls)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/fields.py", line 928, in _validate_sequence_like
r, ee = self._validate_singleton(v_, values, v_loc, cls)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/fields.py", line 1094, in _validate_singleton
value, error = field.validate(v, values, loc=loc, cls=cls)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/fields.py", line 884, in validate
v, errors = self._validate_singleton(v, values, loc, cls)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/fields.py", line 1101, in _validate_singleton
return self._apply_validators(v, values, loc, cls, self.validators)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/fields.py", line 1157, in _apply_validators
v = validator(cls, v, values, self, self.model_config)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/class_validators.py", line 337, in <lambda>
return lambda cls, v, values, field, config: validator(v)
^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/main.py", line 711, in validate
return cls(**value)
^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/ical/component.py", line 139, in __init__
super().__init__(**data)
File "/usr/local/lib/python3.12/site-packages/pydantic/main.py", line 339, in __init__
values, fields_set, validation_error = validate_model(__pydantic_self__.__class__, data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/main.py", line 1076, in validate_model
v_, errors_ = field.validate(value, values, loc=field.alias, cls=cls_)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/fields.py", line 895, in validate
v, errors = self._validate_sequence_like(v, values, loc, cls)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/fields.py", line 928, in _validate_sequence_like
r, ee = self._validate_singleton(v_, values, v_loc, cls)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/fields.py", line 1094, in _validate_singleton
value, error = field.validate(v, values, loc=loc, cls=cls)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/fields.py", line 884, in validate
v, errors = self._validate_singleton(v, values, loc, cls)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/fields.py", line 1101, in _validate_singleton
return self._apply_validators(v, values, loc, cls, self.validators)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/fields.py", line 1157, in _apply_validators
v = validator(cls, v, values, self, self.model_config)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/class_validators.py", line 337, in <lambda>
return lambda cls, v, values, field, config: validator(v)
^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pydantic/main.py", line 711, in validate
return cls(**value)
^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/ical/todo.py", line 203, in __init__
super().__init__(**data)
File "/usr/local/lib/python3.12/site-packages/ical/component.py", line 141, in __init__
raise CalendarParseError(f"Failed to parse component: {err}") from err
ical.exceptions.CalendarParseError: Failed to parse component: 1 validation error for Todo
__root__
Failed to validate: 20240307T083444, errors: (["Expected DATE-TIME TZID value '+08' to be valid timezone", "Expected value to match DATE pattern: '20240307T083444'"]) (type=value_error)
Anyone else seeing the Unifi Protect integration fail after upgrading to 2024.3.0? Was working flawlessly prior to the upgrade.
@sparkydave. Ouch. I donāt use that yet :-(. If you get any connectivity at all though, reboot the host from the Hardware section of the Settings. I had a minor issue upon installation where add-ons didnāt stop running and the core tried to start duplicates when it restarted. That often causes ingress tokens to be out of sync. A full reboot should clear that.
1 reply
Iāve currently killed power to it completely using a smart plug I have linked to Google for use in these situations. Iāll give a while then start up again. (my housemate is probably wondering why all the Google Homes would have been announcing āAssistant Relay Initiatedā over and over every time the add-on started at boot)
1 reply
Itās not looking goodā¦ itās been powered back up for a while now, no remote connection.
Nabu:
Looks like Iāll have work to do when I get home tonightā¦
Same here.
Nice update. Updating from the beta now.
My thermostat (Honeywell T6 ZWave), connected via the Hubitat integration, became unavailable with 2024.3.0. I restored from a 2024.2.5 backup and itās back again. Are there any other reported problems with thermostats?
My other Hubitat devices (switches and contact sensors) still worked fine with the latest update.
Updated to 2024.3. Everything works well, except for my Brother integration not finalizing the initializing phase. This stops Home Assistant from fully starting when it boots up. Canāt ask it to reboot. Have to delete or disable the Brother integration and shut down my entire VM to get Home Assistant to fully start
1 reply
Issue for the Brother integration:
During the video. You asked to Like.
And I would love to.
But how do I do that without logging in to YouTube?
or this should be a feature request?
You could or you could just wait. Since this is in experimental stage for now, Iām sure itāll get many more tweaks in the future.
Itās on the list. For now, use an horizontal stack card
You might be able to make template sensors to filter out these states so you donāt have to do this. Start a topic with your sensor details and the outlier details (history graphs).
I got excited when I read about the energy data export feature. But it is not working exactly as I would expect.
Clicking on download does nothing
I was hoping to download detailed data over the whole month/time period. Instead it downloads just very corase data used to generate the overall graph on the monthly view. I was hoping it will download the same detail as daily view but for the whole month - the data is in the database for sure as I can see any day detailed hour-to-hour.
For example download in monthly view just gives me very small spreadsheet with rows for my energy entities and 7 columns for each day (today is 7th day of the month) with overall daily consumption. That is it.
Some issues came up as wellā¦
This is more-info for an entity excluded from Recorder:
This whole graph has no sense - this is just a current value spanned to 24h.
Earlier the graph was initially empty (āno historyā) - and then only displayed a graph if changes took place while a user was looking at a graph (āstreamlined historyā).
yes, just update.
The script fields is an absolutely incredible! No more making 8 helper entities for me and all my roommates when wanting to add some new dashboard. Iām wondering, is it possible/planned to be able to change the text and/or icon of the run button? I.e. for adding items to a todo list, having the button say add may be more explanatory. I could also see ārunā scaring off less technically inclined users.
All the love and advances the frontend is getting are great. Canāt wait to see what other things this year will bring
Have you updated to Protect 3.x EA ? Thereās a known issue with it and a fix is coming. Even if you downgrade to 2.11 stable from the EA version HA Protect will still not work
1 reply
This release contains several improvement related to ZHA OTA updating. Seems the documentation is behind.
According some discussion on GitHub there should be a new option to connect the community Z2M OTA files
I like the Energy individual devices detail section, but is not easy to use on mobile when you have a lot of devices
Looks OK on a large screen
got similar situation, but in the end it reverts to previous version for me. Tried upgrade 2nd time and still Core cant start and supervisor logs tell me ācore NOT_RUNNINGā and after that time out on api/core/state.
Core log is not populating any info
Change logging to debug and now the upgrade went well. Dont get it. Will restart a few times with and without debug to see if that makes any difference
Section is a view type, not a card.
yes.mentioned the clutter in Beta.
devs are looking at adding a max_devices option, so we can at least bring the number down to the biggest users.
Makes me think now, the clutter could also be diminished if we could set a friendly name in the graphs legend.
Cant do that in the entity settings, because then it would be HA system wide.
just a name: option in the energy panel on the devices would help a lot.
Iāll add that to the discussion, maybe it can be considered
Just make a legend show/hidden.
A name of a device is supposed to be shown in a baloon.
experimenting with the great new feature of sections, and liking it a lot already. For now, Ive migrated some of my existing button-cards grids into these sections, and it looks real nice.
Not sure its the best use for Sections yet, and hoping to see some of the communities most creative ideas soon.
What I would love though is to change the .title styling of the sections grids:
Anything inside the sections can be styled with the existing tools.
It would be really helpful if we could customize those according to the themes we have, and was looking for a way to use card_mod. Guess that canāt be done, given itās not a cardā¦ unless I am completely missing the essentials walking the Dom in inspector.
2 replies
When I got home and powered the server back up with a monitor attached I found it was waiting in recovery mode. I just needed to hit Crtl D or whatever it was to continue with booting and itās been fine sinceā¦ Not sure what was going on but Iām now on 2023.3 with no further issues.
I created a new dashboard based on the sections. I noticed that the āUnused entitiesā option doesnāt work there, entities show up all the time even if they are used somewhere.
Did you update unifi protect (Not HA), to the beta? It the beta does not work with the HA integration.
Very nice update!! Nice work! 
it is available ? Statistics graph card - Home Assistant
and yes, its a fine example of what I meant for the new detailed graphs
1 reply
You need to create a local user in your UDMP
Jeez, youāre right, I never could make it work so far and, donāt ask me why, now I finally noticed that you have to put an entity: before the sensor entity to have it working. Thanks !
I wonder if the doc changed in the meantime.
And yes, I think this should apply to the new detailed energy graph, as well as the option to hide the header altogether because itās kind of heavy right now with this huge list taking over the page.
Hi!
Question: Can āscript user inputā be used like ātap_action confirmationā but allow for more choices? E.g. currently I have a button to open the front gate, and a confirmation which triggers a popup. I can either press OK or Cancel. Instead, Iād like to have 3 choices in this popup: Open, Open&Close, Cancel.
that really shouldnt happen on its own but the names are slugified I believe and I do see a dependency update for that in ths release. Not sure if that caused this change but I woudl say thats unexpected. The service call should only update when the device name is updated.
1 reply
Well, wellā¦
Move handle
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:156
First occurred: 18:06:50 (1 occurrences)
Last logged: 18:06:50
Detected that custom integration 'browser_mod' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/browser_mod/mod_view.py, line 24: hass.components.frontend.async_register_built_in_panel(, please report it to the author of the 'browser_mod' custom integration
Many rely heavily on browser_mod in their UI, especially with popups
Browser_modās development has not been active lately, so the question at this point is, what are the options/alternatives for handling popups with userās own contents?
1 reply
There be gremlins. All of a sudden my button (the script for which doesnāt seem to reproduce properly in the blockquote window):
cards:
- show_name: true
show_icon: true
type: button
icon: mdi:heat-wave
name: Boost Heating to 21C House
entity: input_button.boost_heating
tap_action:
action: call-service
service: tado.set_climate_timer
data:
time_period: ā00:45:00ā
temperature: 21
target:
entity_id:
- climate.ensuite
- climate.house_core
[etc]
show_state: false
for boosting heating complains:
Failed to call service tado/set_climate_timer. TadoClimate.set_timer() missing 1 required positional argument: ārequested_overlayā
You canāt specify both a timer and an overlay. But all of a sudden if you set a timer it seems to be demanding an overlay anyway. In the local parlance - whatās occurring?
The core update 2024.3 appears to have broken the Axis IP Camera integration as the integration now fails during startup.
Logger: homeassistant.config_entries
Source: config_entries.py:504
First occurred: 16:29:31 (1 occurrences)
Last logged: 16:29:31
Error setting up entry Garage for axis
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 504, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/axis/__init__.py", line 21, in async_setup_entry
api = await get_axis_device(hass, config_entry.data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/axis/device.py", line 261, in get_axis_device
await device.vapix.initialize()
File "/usr/local/lib/python3.12/site-packages/axis/vapix/vapix.py", line 144, in initialize
await self.initialize_api_discovery()
File "/usr/local/lib/python3.12/site-packages/axis/vapix/vapix.py", line 162, in initialize_api_discovery
await asyncio.gather(*[api.update() for api in apis if api.supported])
File "/usr/local/lib/python3.12/site-packages/axis/vapix/interfaces/api_handler.py", line 126, in update
obj_ids = await self._update()
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/axis/vapix/interfaces/api_handler.py", line 115, in _update
objects = await self._api_request()
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/axis/vapix/interfaces/port_management.py", line 31, in _api_request
return await self.get_ports()
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/axis/vapix/interfaces/port_management.py", line 36, in get_ports
return GetPortsResponse.decode(bytes_data).data
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/axis/vapix/models/port_management.py", line 221, in decode
data=Port.decode_to_dict(data["data"]["items"]),
~~~~~~~~~~~~^^^^^^^^^
KeyError: 'items'
UniFi OS - Dream Machines 3.2.12 (Official)
UniFi Network Application 8.1.111 (EA)
UniFi Protect Application 3.0.10 (EA) So, yes.
I know there is a warning with running Protect EA but it was only a warning and we could acknowledge. Was working great on previous HA 2024.2.x release just fine. Only when upgrading to HA 2024.3 is when things went south.
How soon before an update release to come out?
2 replies
2024.3 is showing me a repair for System Monitor
" Process sensors processor_use, memory_use, memory_free, memory_use_percent, disk_use_percent, disk_free, disk_use have been created as binary sensors and the sensors will be removed in 2024.9.0.
Please update all automations, scripts, dashboards or other things depending on these sensors to use the newly created binary sensors instead and press Submit to fix this issue."
binary_sensor.system_monitor_process_disk_free
binary_sensor.system_monitor_process_disk_use
binary_sensor.system_monitor_process_disk_use_percent
etc
The binary sensors only seem to allow me to start stop monitoring but donāt give any numbers when running? Change Add Process binary sensor in System Monitor by gjohansson-ST Ā· Pull Request #108585 Ā· home-assistant/core Ā· GitHub seems to detail the change but not how to use the sensors and the āSystem Monitorā documentation doesnāt list any changes.
Any help would be appreciated as to where Iām going wrong?
2 replies
Are there some sort of unstated/undocumented limits on the types or quantities of script fields that will show up in the more-info popup? Some of my scripts correctly show the script fields while others donāt show them.
My vacuum one for example, I see the fields when I open a script in the developer tools but not when I open a more-info popup on the dashboard. All I see is the Cancel & Run buttonsā¦
How it looks in the developer tools:
Calendar broken now since this new update?
Unable to parse date/time value: [ValueError(āExpected value to match DATE pattern: āāā), ValueError('Expected value to match DATE-TIME pattern: ')]
When trying to delete or modify events
Have a look at the GitHub issue I posted, the code owner replied
seems a bit weird as those sensors are still sensors and not binary_sensors, they should show the values of men /disk usage etc? see:
this is running 2024.4 dev, so definitely see to assume they still are there, and no repair at all.
there is a configuration button
that allows you to select several processes to track being active
to my understanding those were the former sensors, now turned into binaries
sorry for the dark images, changed to a lighter themeā¦
I donāt see how your question is related to this release thread so you should probably ask elsewhere, but as far as I know the answer is No. You could use a template sensor to adjust your values.
Iāve already set the sensors up through the UI, it is those sensors Iām getting the repair warning about and a binary sensor is useless for RAM free for example. Iāll try clearing it all out and running through the System Monitor setup again . . .I think Iāve found the issue, seems the percent usage sensors must have been leftover from the YAML setup even though they had been removed.
No idea why it created binary sensors?! Removing System monitor and setting it up again cleared everythign down and created the sensors as Iād expect them.
@madelena The new section layout looks great! I think you said in the stream to post feedback/feature requests under the release post. Iād like to suggest to make the number of columns editable. I have a widescreen display and half of my viewport is empty because I cant tell the layout to use more than 4 columns.
Actually, I think Iāve figured out where the bug is. It looks like the script fields donāt appear in the more-info popup when selector options are set up with label mapping, like below:
select:
options:
- label: Red
value: r
- label: Green
value: g
- label: Blue
value: b
As soon as I remove the mapping, they start working again.
Iāll work on submitting a bug report
Edit: scratch thatā¦ its not that simple to reproduce. I need to keep digging but it appears to be related to the selector mapping
1 reply
2024.3 affected on custom cards like stack-in-card & vertical-stack-in-card in part of a gap between cards in a stack.
Hope that these cards will be fixed/forked by someone.
Currently have to use card-mod to fixā¦