Allowing for sleep_brightness to be set to 0

[jaynis]

This PR updates the sleep_brightness range from 1–100 to 0–100, enabling zero as a valid value. It allows lights to remain off when they receive turn_on calls during sleep mode and thus can prevent specific lights (e.g. ceiling lights) from turning on. This eliminates the need of special logic when e.g. turning on lights with motion sensors during night time.

[basnijholt]

Sorry it took me so long to get to this. I've been a bit overwhelmed by the number of AI-assisted PRs opened here recently, and I've also been spending nearly every spare hour on my biggest project so far, MindRoom.

I'm very supportive of using AI for coding, but many of these PRs still need careful human review because even plausible-looking changes can introduce subtle breakage. That backlog made me postpone reviewing them for a while.

I've now done a batch review with Codex / GPT-5.5 (xhigh). This comment is AI-assisted, but I've reviewed the concern before posting it.

One issue before this can be merged: making sleep_brightness: 0 valid is incomplete on current main, because the split-command path still drops falsey brightness values.

Specifically, _split_service_call_data filters split data with if service_data.get(attribute), so with separate_turn_on_commands: true a brightness value of 0 is filtered out and the brightness command can be skipped. That means this new setting may not actually keep the light at zero brightness in the scenario where separate turn-on commands are needed.

The zero-value handling in #1460 fixes the underlying pattern by checking is not None. Could you either include that fix here, make this PR depend on/merge after #1460, and ideally add a regression test for sleep_brightness=0 with separate_turn_on_commands=True?

[jaynis]

Hi @basnijholt and thank you for your review. I have implemented the mentioned changes and kindly ask you to take another look.