Automation disables when scheduling very warm colors (e.g. 1000K)

[Soakedcardinal]

Scheduling very warm color temperatures (≤2000K) in Kelvin disables automation, even though lights display the correct color.

Steps to Reproduce:

1. Schedule a Hue bulb or strip in Kelvin to 1000K (or any value below 2000K).
2. Observe that the bulb shows the correct deep red/orange color.
3. Kelvin disables automation, reporting the light was changed manually.

Cause:

• Kelvin checks ct (color temperature) to verify schedule compliance.
• Hue API caps reported state ct to 500
• Kelvin detects a mismatch between scheduled ct and reported ct, disabling automation even though the actual color is correct (?)

Expected Behavior:

• Kelvin should detect the light’s color mode (XY vs. CT) and only disable automation if the actual color does not match the scheduled color.

Suggested Action:

• Check/Update validation logic to account for XY color mode when ct is above API-supported limits, preventing false automation disables.