Enable custom colors for all numeric values (also outside of 0-100 range)

[amsterjanis]

Since the component can be used for other entity types than just battery (and the readme even includes such examples) I think it makes sense to remove the restriction of 0-100 range for custom colours.

This will enable full functionality when using for negative temperatures, zigbee link quality, disk space etc.

[maxwroc]

Thanks for contribution!

[maxwroc]

Merged it too fast... now when looked at the full code:

• There is a condition below which checks whether the step value is greater than 100. So if you have a different color for 500 and 1000 it won't work. The only reason why it didn't fail in the test is that the additional step/color was missing (between 100 and 1000)
  https://github.com/maxwroc/battery-state-card/blob/3bae17c6bf67fddbb958ad4098d74b75b8426eb3/src/colors.ts#L30C48-L30C67
• If the gradient flag is true then it will fail as well - the getColorInterpolationForPercentage requires number in 0-100 range

I'll need to revert this change. Sorry

[maxwroc]

BTW You can always overwrite the 0-100 value by using value_override. As it was done in the mentioned examples. Not the ideal solution but working

[maxwroc]

Ok I have looked at this again and as I have mentioned we have two problems:

• the first one can be fixed easily just by removing this condition and maybe later adjusting the threshold finding logic few lines below (if needed)
• the second one with the gradient we can take the value range which user provided in steps and treat them as the maximum supported range, this way any incoming value can be converted to 0-100 based on such supported range e.g.

color:
  steps:
    - value: -3
      color: #ff0000
    - value: 0
      color: #ffff00
    - value: 7
      color: #00ff00
  gradient: true

• -3 will be treated as 0
• 0 as 30
• 7 as 100

And this is what will be passed to the getGradientColors , so the gradient can be calculated properly