Hampton Bay Penrose - Night Light Mode

[SlyBlueFox]

The device

https://www.homedepot.com/p/Hampton-Bay-PENROSE-24-in-SMART-Matte-Black-Perforated-LED-Vanity-Light-Wireless-Powered-by-Hubspace-2700K-5000K-Night-Light-Mode-C06021201A/334246489#see-more-details

Model # C06021201A

Features

Most features work perfectly (color, color temperature, brightness, effects and effect speed), the only thing I don't see is the ability to activate "Night Light Mode" that illuminates a small secondary portion of the light fixture with a dim warm light. This is different from the Nightlight effect.

I believe I have found the feature under "color-mode" in the debug logs

            {
                "functionClass": "color-mode",
                "type": "category",
                "schedulable": true,
                "functionInstance": null,
                "_opts": {
                    "values": [
                        "circadian-rhythm",
                        "night-light",
                        "sequence",
                        "white",
                        "color"
                    ],
                    "categoryValues": [
                        {
                            "name": "circadian-rhythm",
                            "values": [
                                "10"
                            ]
                        },
                        {
                            "name": "night-light",
                            "hints": [
                                "no-brightness"
                            ],
                            "values": [
                                "5"
                            ]
                        },
                        {
                            "name": "sequence",
                            "values": [
                                "2"
                            ]
                        },
                        {
                            "name": "white",
                            "values": [
                                "0"
                            ]
                        },
                        {
                            "name": "color",
                            "values": [
                                "1"
                            ]
                        }
                    ]
                }
            },

Datadump

_dump_hs_devices.json

Additional information

I have attached screenshots and photos below to help explain the Night Light Mode vs the Night Light Effect, since they are named the same thing which could be a bit confusing.

I am more than happy to test or help in any other way I can. Thank you for the amazing work on this integration!

Night Light "Mode"

Screenshot

### Photo

Night Light "Effect"

Screenshot

### Photo

[SlyBlueFox]

I took a run at this and have a working implementation on a fork. Wanted to write up exactly what was done and why so you can decide whether you'd like a PR, or would rather reimplement it yourself.

Heads-up on provenance: this was written with AI assistance (Claude Code). Totally understand if you'd prefer to rewrite it in your own hand rather than merge AI-authored code, the writeup below should give you everything you need either way.

What it does

These fixtures expose a night-light color-mode that's distinct from the existing nightlight sequence effect. I implemented it as a dedicated on/off light entity (ColorMode.ONOFF), e.g. light.vanity_bar_light_night_light, rather than a light effect — precisely because the sequence-based "nightlight" effect already exists and these are genuinely different things. Enabling it puts the fixture into night-light; disabling it returns the fixture to whatever it was before.

No aioafero change is needed — LightController.set_state already passes color_mode through.

Device quirks found during on-device testing (the important part)

Most of the code is shaped by how the hardware actually behaves:

1. The fixture powers on in its stored color-mode, then applies a new one → a white flash before night-light appears. Fix: when the light is off, set the mode while it's still off, then power on ("mode-before-power").
2. Sending a color-mode change as part of (or alongside) turning off makes the fixture briefly illuminate that mode → a white flashbang when disabling night light. Firm rule adopted: turn-off never carries a color-mode.
3. The device has a single active color-mode field. While night-light is on, that field is night-light, so the main light's power toggle would resume night-light. Fix: reset the stored mode back to the pre-night-light mode on the main light's next turn-on (again mode-before-power), not on turn-off (which would violate rule number 2).
4. base.update emits HA state from the cloud's PUT response. A mode-only PUT comes back with power: on, which caused the main light entity to flicker on→off until the next poll. Avoided by never doing a mode-only PUT around turn-off.
5. Power-state preservation: the entity records whether the light was on before night-light so it restores correctly instead of forcing the light on (another flashbang source).

To coordinate rule number 3 between the two entities, the pre-night-light mode is stashed in a small dict on HubspaceBridge.

Footprint

• light.py — the HubspaceNightLight entity, a supports_night_light() helper, the main-light turn-on reset, and platform wiring.
• bridge.py — one documented dict for the shared "previous mode" state.
• tests/test_light.py — coverage incl. regression guards that assert turn-off never sends a color-mode and that enabling/resetting always selects the mode before powering on.
• tests/device_dumps/light-penrose.json — an anonymized dump of the real fixture.
• switch.py is untouched.

All tests pass and ruff is clean on the changed files. Every edge case above is commented inline at its decision point.

Compare / diff: main...SlyBlueFox:Hubspace-Homeassistant:penrose-nightlight

Fork/branch: SlyBlueFox/Hubspace-Homeassistant@penrose-nightlight. Happy to open a PR if you'd like it, adjust the approach, or just leave this as a reference for your own implementation — your call.