Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

closure_state not correct #156

Open
AlanJohnWilliams opened this issue May 22, 2024 · 2 comments
Open

closure_state not correct #156

AlanJohnWilliams opened this issue May 22, 2024 · 2 comments

Comments

@AlanJohnWilliams
Copy link

Hi! I just pulled together a few dashboard views of the Rivian integration data and started automating locking of my truck when at home. I'm noticing that closure_state doesn't always reflect closure status correctly. See track below for the last 6 hours where clearly doors have been opened but closure_state remains off. (I have also checked the raw entity results in HA to make sure it isn't an issue with my FLUX query or Grafana dashboard.

image
@tmack8001
Copy link
Collaborator

My child decided to trigger a long term test of my closure notification and auto locking feature on my trucks while out of town on a business trip.

My Rivian shows "open" and "closed" for this enclosure state fine (as pictured below).

Could you please provide a bit more context to your installation environment and entity that you are showing "off" and "on" statuses for.

Screenshot_20240522-192957.png

@AlanJohnWilliams
Copy link
Author

Hi @tmack8001 ,

The specific sensor is binary_sensor.sulley_closure_state created by the integration. If I look at binary_sensors for specific doors, they seem to change state as expected, eg binary_sensor.sulley_door_front_left, but binary_sensor.sulley_closure_state remains unchanged.

Here is a view of the history panel showing that the front left door has been opened and closed, but sulley_closure_state stays closed/off:

image

In this time range, sulley_closure_state doesn't change at all, but over other periods I do see it changing, but not always when another opening changes.

I've currently worked around this by creating a group for all the Rivian doors/windows that I want to monitor. this group works as expected (with perhaps the added benefit of not tracking the rear tailgate or tonneau cover.

group:
  sulley_secure_state:
    name: Sulley Secure Status of Doors and Opennings
    entities: 
      - binary_sensor.sulley_door_front_left
      - binary_sensor.sulley_door_front_right
      - binary_sensor.sulley_door_rear_left
      - binary_sensor.sulley_door_rear_right
      - binary_sensor.sulley_window_front_left
      - binary_sensor.sulley_window_front_right
      - binary_sensor.sulley_window_rear_left
      - binary_sensor.sulley_window_rear_right
      - binary_sensor.sulley_front_trunk
      - binary_sensor.sulley_gear_tunnel_right
      - binary_sensor.sulley_gear_tunnel_left

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants