organization of the text next to the icon.

[iorifly]

Let me see if I got it. I need to change the custom.css file. Where is it located?

in the css folder. I only have the main.css file

[doubleT]

Create a file named “custom.css” and put the code from above inside it.

[iorifly]

@doubleT said in organization of the text next to the icon.:

.module.MMM-homeassistant-sensors table {
border-spacing: 0;
}

nothing happened. This is the same way. He did not create the lines.

[doubleT]

Yeeeeah … what about the one above that? The 2nd part. ;)

[sdetweil]

@iorifly take the .module prefix off, not needed

[iorifly]

@sdetweil ok

[iorifly]

@doubleT

excuse. LOL

I did not understand.

[doubleT]

The content of the custom.css should be:

.module.MMM-homeassistant-sensors table tr td:nth-of-type(2) {
    test-align: left;
}
.module.MMM-homeassistant-sensors table tr:nth-of-type(3) td,
.module.MMM-homeassistant-sensors table tr:nth-of-type(6) td {
    border-bottom: 1px solid white;
}
.module.MMM-homeassistant-sensors table {
    border-spacing: 0;
}

All of it. Not just the last part.

[iorifly]

@doubleT said in organization of the text next to the icon.:

.module.MMM-homeassistant-sensors table tr td:nth-of-type(2) {
test-align: left;
}
.module.MMM-homeassistant-sensors table tr:nth-of-type(3) td,
.module.MMM-homeassistant-sensors table tr:nth-of-type(6) td {
border-bottom: 1px solid white;
}
.module.MMM-homeassistant-sensors table {
border-spacing: 0;
}

.MMM-homeassistant-sensors table tr td:nth-of-type(2) {
    test-align: left;
}

.MMM-homeassistant-sensors table tr:nth-of-type(3) td,
.module.MMM-homeassistant-sensors table tr:nth-of-type(6) td {
    border-bottom: 1px solid white;
}

.MMM-homeassistant-sensors table {
    border-spacing: 0;
}

[doubleT]

@sdetweil I don’t have any modules with uper case letters (MMM- …) at the moment. Can you confirm the module class name is with uper case letters or is it changed to lower case?

In this situation, with a unique module name, it’s ok to identfy the module without the .module but in general I’d say it’s best practice that if you want to address a specific module, you describe it as precise as possible.
E.g. there might be a module “image_frame” that you want to address but there’s also a module that somewhere within its structure has one div with the class “image_frame” that you don’t want to address. Then it’s absolutely necessary to address the target with .module.image_frame