Lutron Caseta will report the opposite entity state after restart or reload

Question

Lutron Caseta will report the opposite entity state after restart or reload

iCSpotRun opened this issue 6 months ago · 2 comments

The problem

After restarting Home Assistant, or reloading the Integration, Lutron Caseta 'cover' entities (on RA3 at least), will report the opposite state that they are actually in. i.e. A cover that is 'closed' will report as 'open' after restart and vice versa.

The problem doesn't seem to affect all Lutron Caseta devices. In my case, only covers are impacted. Lights and Switches seem unaffected.

What version of Home Assistant Core has the issue?

core-2024.7.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Lutron Caseta

Link to integration documentation on our website

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

Diagnostics information

home-assistant_lutron_caseta_2024-07-05T17-24-19.860Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

Answer 1 · 2024-07-05T23:48:23.000Z

Hey there @swails, @bdraco, @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)}}

Answer 2 · 2024-08-28T13:09:44.000Z

This issue persists and prevents me from using conditions involving cover states since those states cannot be trusted