Beta 3.8.8

[Krenstik]

Hi,

well, I download last beta and I get a new colours, or it do not takes my one...

before:

beforea.jpg (189.36 KiB) Viewed 597 times

new beta:

after.png (344.75 KiB) Viewed 597 times

[Lokonli]

I was a bit late my release notes.

There are two changes in 3.8.8.
The dial ring coloring now by default starts at 0, instead at the lower left.
You can see that in your dial in the lower left (Balkon)

If you want to have the old behavior, add the following block parameter to the block definition in CONFIG.js:

Code: Select all

   splitdial: false

The second change is in the coloring for some dial rings. This is in fact a bug fix: intended coloring was not applied correctly.
The side effect is that you have to add !important to the custom color definitions in custom.css. For instance like:

Code: Select all

.dial .bar.primary,
.dial .fill.primary {
    border-color: #d81b90 !important;
}

.dial .bar.secondary,
.dial .fill.secondary {
    border-color: #15ca33 !important;
}

[Krenstik]

HI,

regarding: The dial ring coloring now by default starts at 0, instead at the lower left.

May they start also with other value?

Rest I will try during next days....

[Lokonli]

HI,

regarding: The dial ring coloring now by default starts at 0, instead at the lower left.

May they start also with other value?

Rest I will try during next days....

Current behavior:
Normally the ring coloring will start from the min value, except 'splitdial' is set to true.
If splitdial is set to true then the start value of the ring coloring is 0.
If min<0 then splitdial is set to true by default.

On you question for another start value:
Currently you can start the ring coloring from the min value or from 0. Can you describe a use case for which you would like to see a different start value?

[Krenstik]

It was just idea, for the temp or CO2 meter....

For ex. ppm under 1400 green, up to 1400 red.

Or temp under 21 blue, up to 21 green and over 24 red

[Lokonli]

Changing the color based on passing a certain threshold value already is supported via the 'setpoint' block parameter.

More fancy coloring can be achieved via deviceHook functionality.