Transparent Blue custom theme

No, that is YAML in the transparentblue.yaml theme file
See here: JOHLC/transparentblue: A transparent blue theme for Home Assistant (github.com)

thanks this works very nicely with my home assistant kde widgets.

1 Like

Question. I now have 5 cut up images of my background. Can I use the full background but give the start end x,y coordinators?

I am not sure

the code in this theme for position of the background comes right before the base64 string that this the background image

lovelace-background: 'center / cover no-repeat fixed url(etc.....)

But I do not know the valid options for each

Hello! I released an update to this today. It restores the transparent sidebar as well as the more info dialog box.

Let me know what you think.

Release v2023.12.2 - Return of the bling · JOHLC/transparentblue (github.com)

Hi @JOHLC
I love yor theme, too. But i have found an issue maybe (or obviously) in it: see here Tapping dashboard tabs accidently hits buttons - #6 by JohnFLoki

I followed the suggestion to try another theme and the other theme i use, which is a bit more simple (no transparency), and since then this issue did not occur. So might there really be some “z index” in it even though i couln’t find one?

Br, Jo

Very strange – can’t say I have ever experienced this on any of my devices. I also tried my best just now to replicate it and was not able to.

As far as a z index goes, this theme does not have that configured. Possibly this is something with card-mod or a custom card that you use? (if you use either of these)

strange… I had to include a verification taps even to the buttons, as accidently in the nights I was opening the garage doors at frost (and plants being in there)…
Let me switch back to the theme to see if this still / again happens - I have not seen it since quite some time now

2026.01.1 - Happy New Year! :tada:

Hello and Happy New Year! :tada:

I just wanted to drop in and say thank you to everyone who uses the Transparent Blue theme.
I keep seeing it pop up in random videos and communities across the internet, and I honestly think that’s pretty cool.
I recently even found it referenced on a French blog. Salut, French users! Ça va? :fr:

Hope you all have a great new year,
@JOHLC

Release Summary:
This release focuses on improved readability and UI consistency across Home Assistant, introduces new and updated color variables, and delivers a major repository cleanup. It also includes documentation enhancements, workflow updates, and HACS validation fixes to improve long-term maintainability and contributor experience.

What’s Changed

:art: Theme & UI Improvements

  • Improved overall readability across Home Assistant to align with recent color variable changes.
    • Added new color variables for:
      • Text states
      • Neutral fill
    • Primary and neutral UI states
  • Improved contrast and readability for secondary UI elements (e.g., overflow/action menus).
  • Updated theme styling to support the latest Home Assistant automation editor.

:broom: Repository Maintenance & Quality

  • Comprehensive repository cleanup and standardization:
    • Fixed all YAML formatting issues and resolved yamllint errors.
    • Simplified and corrected .yamllint configuration.
    • Added a proper .gitignore covering OS, IDE, build, and temporary files.
  • Updated GitHub Actions workflow:
    • Upgraded actions/checkout from v2 to v4.

:page_facing_up: Documentation Improvements

  • Major README overhaul:
    • Improved structure, clarity, and consistency.
    • Updated badges, screenshots, and installation instructions.
    • Added contributing, support, sponsors, compatibility, and beta version sections.
    • Updated screenshots
  • Improved issue templates:
    • Bug report template now captures more context.
    • Feature request template expanded
  • Added a pull request template to standardize contributions.
  • Security policy with supported version guidance.

:package: HACS & Metadata Fixes

  • Fixed HACS validation issues:
    • Corrected render_readme type and later removed it entirely to comply with current HACS requirements.
  • Cleaned up hacs.json formatting and validation errors.
  • Minor cleanup to tracker.json to resolve duplication and formatting issues.

Full Changelog: