I just updated to the latest version, and I am unable to reproduce your issue. You might want to check to make sure your time configuration is still intact in your configuration file (check the documentation for more details). Also, I love your replicator. 
I found the issue. I created a bunch of sensors for my printer in the sensor.yaml file and somewhere, somehow, it screwed up the date/time sensors. It was strange because I was not getting a configuration error. I just happened to stumble across it when I started trying to add another sensor below the date/time ones
1 Like
Hi there! I have created a Stardate sensor entity, and I would like to replace the clock in the header with it. What would be the best way? Thanks!
I’ve spent the past couple of days implementing this on my HA dashboard and it is awesome.
Thanks so much for this!
The only slight glitch I have is a misalignment in a grid card
The section “Todays Financials” is a custom:layout-card with a layout_type: custom:grid-layout of 2 columns at 50% 50%
As you can see, the middle bar is misaligned with the header and footer. I suspect it’s a padding issue, but as I understand it, standard CSS styles may not work inside this theme. The yaml is shown below. Can anyone fix this for me please?
Thanks.
type: vertical-stack
cards:
- type: markdown
card_mod:
class: bar
content: '# Todays Financials'
- type: markdown
card_mod:
class: header-contained
content: '# '
- type: custom:layout-card
layout_type: custom:grid-layout
cards:
- type: gauge
card_mod:
class: middle
entity: >-
sensor.octopus_energy_electricity_xxxxxx_xxxxxxx_current_accumulative_cost
segments:
- from: -14
to: -13.5
color: '#04d916'
- from: -13.5
to: -13
color: '#16db18'
- from: -13
needle: true
min: -14
max: 10
name: Import Cost
- type: gauge
card_mod:
class: middle-right
entity: sensor.electricity_bill_today
segments:
- from: -14
to: -13.5
color: '#04d916'
- from: -13.5
to: -13
needle: true
min: -14
max: 10
name: Net Cost
- type: gauge
card_mod:
class: middle
entity: sensor.solar_accounting_outgoing_fixed_compensation
name: Export Value
min: -14
max: 10
needle: true
segments:
- from: -14
to: -13.5
color: '#04d916'
- from: -13.5
to: -13
color: '#16db18'
- from: -13
- type: gauge
card_mod:
class: middle-right
entity: >-
sensor.octopus_energy_gas_xxxxxxxxxx_xxxxxxxxx_current_accumulative_cost
needle: true
segments:
- from: 0
to: 0.25
color: '#04d916'
- from: 0.25
to: 0.5
color: '#16db18'
- from: 0.5
to: 0.75
color: '#29e11b'
- from: 0.75
to: 1
name: Gas Bill
min: 0
max: 10
layout:
width: 300
max_cols: 2
grid-template-columns: 50% 50%
- type: markdown
card_mod:
class: footer-contained
Hello!
I just gave it a try, and I love it.
That’s how my panel in my man cave now looks:
Thank you very much!
Bye
Tiggr
1 Like
beautiful! Definitely want this on a touchscreen
1 Like
Hi,
Something has changed for button card, following the update of Core 2024.2.0. The icons are no longer displayed correctly.
Before
After
Lots of the buttons are affected like this. An update to Lcars will hopefully solve it.
Hi, You can apply this solution before the official fixed comes out.
It doesn’t appear to solve the button icon problem, I still have an issue after the mods and re-starting ha. The icons on some buttons are lit when the light is off, and dim when the light is on! The pill button icons don’t change at all when toggling the functions.
How is everyone getting square badges at the top of the dashboard? I have tried every combination of allowable configuration. That looks way better than the circular badges.
Hi y’all!
After the new HA core and OS updates, my LCARS screen doesn’t show the 3 dot menu.
Has anyone else experienced this? Thanks!
1 Like
I changed the line in the Themes yaml (line 1083) to the following…
margin-right: -42px;
Ironic that’s it’s 42? IDK, but it works. 
I think if one changes that to any number and back to the original, it should fix it. I just changed it to -20 and it looks pretty good to me.
Hi all, sorry for the delayed announcement. The latest LCARS version, 2.2.4 addresses all of the issues introduced with Home Assistant 2024.2. Please update, and if you have any created any custom theme configurations, don’t forget to back them up and then comp them back in after updating!
Ooof, that’s a tricky one. I haven’t got any experience with layout-card yet, though lots of folks in the Discord community do and may have an answer for you.
Update - problem solved
Turned out the latest card-mod.js was the culprit. It introduced some kind of recursion. When I replaced that file with the ancient version from before the upgrade, everything fell into place again. What a relief! 
Sorry for bothering everyone…
Original post below…
I am facing the weirdest problem. This morning, I upgraded HA Core from 2023.6.3 to 2024.2.2 (long story why I had to put off updating for such an epic time, actually told elsewhere on this forum):
Core 2024.2.2
Supervisor 2024.02.0
Operating System 11.5
Frontend 20240207.1
The first thing I noticed was LCARS being broken. 
So, I’ve tried a couple of things:
- I replaced
lcars.yamlandlcars.jswith the current version from Github and restarted HA. No success. - I also replaced
card-mod.jswith the lasted version from Github and restarted HA. No success. - Both
.jsfiles are accessible through the browser (http://homeassistant:8123/local/plugins/lcars.js). - Of course, I also kept refreshing browsers, trying different browsers and different devices. No success.
The situation now looks like this. The LCARS icons are still present for the HA menu on the left hand side. Also, sound bits are working. However, the main part of the screen does not show LCARS at all.
Have I missed any other breaking changes during the past eight months? What might be the cause for this misery?
Please help! 
Those LCARS displays around the house have always made my day!
Hi, I run into this issue because I installed the LCARS theme.
There is a warning for a dublicate key for a color and in the configuration.yaml the inserts for time thrown an error on my installation, so that the frontend could not be loaded.
As workaround this can be deleting by deleting the lines in the configuration.yaml. One can do this in the HA console with vi or with SSH and other external tools when the configuration is externally accessable.
Duplicate key error will be fixed soon, but should not break the frontend UI. I’ve not heard about this from any other user.