This doesn't work in Firefox. It is a known bug, and its resolution is dependent on the resolution of a number of other bugs. If you use Firefox, see the approach @william2 described.
Edge will respond to it the way you expect, even without the "!important" keyword, BUT inspecting the page will show the parser indicates it should NOT be displaying it.
CSS is amazing, but it can tie your brain in knots with ease. Try to not get frustrated by it. I have personally spent hours trying to figure out how to select a particular element, so I could modify it for a special situation.
QQ: does anyone know why the tiles that use the template 'variable string' don't honor the following CSS (it works fine for every other template I've used):
There's likely a good reason... but I would need to look at it in more detail to provide an accurate answer. My suggestion would be to get familiar with drilling through the dashboard structure in what is commonly referred to as the Developer Tools, at least in Chrome. If you drill into the structure and come down to the point of the tiles you will hopefully see the references to classes and make some links to how the Custom CSS is applied. If you are somewhat new, then it would be understandable that it makes no sense.... (The reason behind my utility in this space that I have neglected in recent times...)
If you are still stuck in the next couple of days, give me a poke and I can provide some more detailed instructions on what I am describing.
@limeypride I just found your question. I have used a number of variable tiles and encountered this same issue.
The reason it doesn't work is the structure of the variable tile is a bit different from the device tiles. I put to gether a quick dashboard to demonstrate this.
Be sure to change the tile number, 14 in my case, to the tile number of your vaiable tile.
I also noticed in my work on putting together this reply that there is a built-in method for renaming the tile. Clicking on the tile will give you the opportunity to rename the variable. Fortunately, it renames it everywhere it is used. In actuality the variable has an index reference that is the used behind the scenes, so the name is merely used to help the human keep track of its purpose easier.
Note to self to add this to the "hide tile titles" option in my CSS Editor. Like most of the features of the editor, I am simply implementing the hard work of others here.... Nice work @wayne.pirtle .
I am trying to add a gradient background to my dashboard. I did this once and, for the life of me, cannot remember what I did to make it work. Did anyone else do this?
The background of the dashboard I expect is a slightly different element that needs to be targeted, compared to the tiles, but the CSS references should still be relevant.
I'm pretty sure I've done this before as well, so will try and take a look after work.
You could try either adding the gradient code to the background color option in the dashboard Options, or set the background color and then look for it in the dashboard source to find the element to target in the custom CSS.
@Tree.Log - I wasn't suggesting to update the JSON directly, just update the configuration in, what I now realise I quoted as the incorrect tab of Options, it should have been Grid.
If my memory is right, I think I avoided the CSS option previously for my own dashboard and produced a JPG with a gradient applied and used that as a background image.
At this time of night that is likely my suggestion.... Perhaps by the weekend I (or hopefully others) may have a better solution.
EDIT: Try adding something like this to the Custom CSS ....
Wonderful, thank you for pointing me in the right direction! I like doing an offset radial gradient that mimics the look of the Home.app. I ended up with this;
#app {background-image: radial-gradient(ellipse at 85% 90%, #fdbb2d, #b21f1f, #1a2a6c);
At some point, I'd love to make a green CRT-like dash with line art buttons, or maybe a mnemonic diagram like in this Chernobyl control panel:
I had a weather dashboard that's been running fine the past few months with a black background and tiles with a 0.7 alpha, but about 2 days ago these red tiles which mark the single tiles started to show up behind my Dashboard tiles. Not sure if something changed on the Hubitat software side to do this, but it doesn't show up on other Dashboards. Anyone have a solution or idea if some kind of CSS is being ignored? Thanks!
I’ve got the same thing on one of mine. My wife was just asking me what’s going on with the dashboard… I didn’t even realized she ever looked at it or used it! lol
Nope, no Smartly here, but this particular dashboard is being used on an old Fire tablet using Fully Kiosk Browser to display it via a local Dashboard link. I don't see the red tiles when I view it on my laptop's web browser or my Android phone though. Did we unlock a special KITT mode?
I guess I'll see if I can get this old tablet to update so it is compatible. If that doesn't work, maybe I need to make one big dummy tile that is all black that the other tiles overlap.
I got it to work. It's truly the most kludgy way, but reminds me of the old days of "we can't get this error window to go away, let's just put a background color window over it so you don't see it anymore."
I uploaded a 1x1 black (or whatever bg color you want) pixel image file to the Hubitat through the file manager. Then I found the lowest numbered tile on that Dashboard and changed it to an Image tile using the 1x1 pixel as the Image. I moved that tile to position top left and then changed its size to match the whole dashboard.
Last thing was to make a new replacement tile duplicating the old function of the tile that was used to create the background. I attached a photo with the image tile 1 column smaller than the dashboard to show it successfully covering up all the other red blocks.
Anyone know how I can align the Groups on the left to be left aligned?
I'm also struggling with getting the keypad to fill the entire tile that it's sitting in. The top and bottom padding doesn't seem to go away regardless of what I set in the CSS.