Lutron Caseta RA3 always turns on at 100%

[rwagoner]

The problem

When turning a RadioRA 3 light off and back on a from Home Assistant, the level always goes to 100%. In the Home Assistant developer tools I do see the brightness attribute attribute set to appropriate dimmed level when the light is on. When the light is turned off the brightness attribute goes to null. The integration async_turn_on function has code to check the brightness before setting it to 255. It appears this was to restore the previous state.

I know at my previous house with RadioRA 2 when I turned a light off, it would turn back on to the previous value. However I do not recall what happened with the brightness attribute once the light was turned off.

Would there be an issue leaving the brightness attribute set when the light is turned off so the state could be restored?

What version of Home Assistant Core has the issue?

core-2025.2.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

lutron_caseta

Link to integration documentation on our website

https://www.home-assistant.io/integrations/lutron_caseta/

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @swails, @danaues, @eclair4151, mind taking a look at this issue as it has been labeled with an integration (lutron_caseta) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of lutron_caseta can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign lutron_caseta Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

lutron_caseta documentation
lutron_caseta source
_{^{(message by IssueLinks)}}

[rwagoner]

This might need to be changed to a feature request. Upon further digging I was using the the lutron integration with my RadioRA 2 system, while RadioRA 3 uses the lutron_caseta integration. The lutron integration has a _prev_brightness variable so it can return the last known brightness when the light is turned on. It would be great to add configurable option to the integration for the default turn on setting to include 1-100% or last state.

[CloCkWeRX]

I think you are pretty much right.

core/homeassistant/components/lutron/light.py

Line 100 in 30a6a6a

def _update_attrs(self) -> None:

is where the other compontent snapshots the brightness

core/homeassistant/components/lutron/light.py

Line 67 in 30a6a6a

def turn_on(self, **kwargs: Any) -> None:

is where it reapplies it.

While in the lutron_caseta one:

core/homeassistant/components/lutron_caseta/light.py

Line 190 in 30a6a6a

if color is None and brightness is None:

[CloCkWeRX]

Did you want to see if #138578 works for you?

[rwagoner]

Sure, what's the recommended way to test? I cloned the repo and copied the lutron_caseta directory to custom_components, however it doesn't appear override the built-in lutron_caseta module.

[rwagoner]

@CloCkWeRX Thanks for working on adding this! I was able to test the component by adding a version field to the manifest.json and changing the dev docker build due to #138201.

Bad news is it isn't working as expected. Any light I haven't touched goes to 100% the first time it is turned on. From then on, the light always turns on to 50%. This makes sense _prev_brightness defaults to Null, then must be going to 0 when the light is turned off. I should have some time later today to see if I can get it working. I do think if we should go to 255 vs 255 /2 to follow the previous behavior of 100% if the value is unknown.

[rwagoner]

I got it figured out. The issue was async_turn_on and async_turn_off both call async_set_brightness so _prev_brightness was being set to 0. I also handled the scenario when the light level is changed at the device. Since the changes are minimal I'm going to include the diff here. Hopefully that is ok.

index d634703b267..9deb9135d5e 100644
--- a/homeassistant/components/lutron_caseta/light.py
+++ b/homeassistant/components/lutron_caseta/light.py
@@ -140,7 +140,12 @@ class LutronCasetaLight(LutronCasetaUpdatableEntity, LightEntity):
     @property
     def brightness(self) -> int:
         """Return the brightness of the light."""
-        return to_hass_level(self._device["current_state"])
+        brightness = to_hass_level(self._device["current_state"])
+
+        if brightness != 0:
+            self._prev_brightness = brightness
+
+        return brightness

     async def _async_set_brightness(
         self, brightness: int | None, color_value: LutronColorMode | None, **kwargs: Any
@@ -149,7 +154,9 @@ class LutronCasetaLight(LutronCasetaUpdatableEntity, LightEntity):
         if ATTR_TRANSITION in kwargs:
             args["fade_time"] = timedelta(seconds=kwargs[ATTR_TRANSITION])

-        self._prev_brightness = brightness
+        if brightness is not None and brightness != 0:
+           self._prev_brightness = brightness
+
         if brightness is not None:
             brightness = to_lutron_level(brightness)

@@ -165,7 +172,9 @@ class LutronCasetaLight(LutronCasetaUpdatableEntity, LightEntity):
                 seconds=kwargs[ATTR_TRANSITION]
             )

-        self._prev_brightness = brightness
+        if brightness is not None and brightness != 0:
+            self._prev_brightness = brightness
+
         if brightness is not None:
             brightness = to_lutron_level(brightness)

@@ -183,10 +192,9 @@ class LutronCasetaLight(LutronCasetaUpdatableEntity, LightEntity):
         if ATTR_BRIGHTNESS in kwargs:
             brightness = kwargs.pop(ATTR_BRIGHTNESS, None)
         elif self._prev_brightness == 0:
-            brightness = 255 / 2
+            brightness = 255
         else:
             brightness = self._prev_brightness
-        self._prev_brightness = brightness

         color: LutronColorMode | None = None
         hs_color: tuple[float, float] | None = kwargs.pop(ATTR_HS_COLOR, None)```

[rwagoner]

I just saw the lutron component has #137127 open to make the default value configurable for the integration when the previous light level is unknown. It would be great to add to this PR as well.

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.