What's new
By:

Home Assistant Automations

Yes, I did the same and the integration is working again.
 
borski said:
Try now. I just pushed v1.0.10.

HA updated some versions and made my evening very annoying, but it’s fixed now. :)
Click to expand...

Thank you and @segbrk so much for all your time and energy for the community. You all are so AMAZING! Hope I can one day buy a drink (or a couple) for you guys!
 
I have an automation set up with ratgdo so that the garage door will open when my car enters my Home zone. Last night at 3AM, it got triggered even though my car was in the garage (already Home) all night. This has happened multiple times. I looked at the HA Logbook and confirmed that my automation was triggered by the Lucid entering the Home zone.

The automation ran yesterday when I came home so HA knew that the car was in the Home zone. I have another automation to close the garage door when it exits the Home zone, and the Logbook does not have an event of the car leaving the Home zone last night.

I'm at a loss how this automation was triggered last night. Any ideas on how to debug this?
 
Dslee68 said:
I have an automation set up with ratgdo so that the garage door will open when my car enters my Home zone. Last night at 3AM, it got triggered even though my car was in the garage (already Home) all night. This has happened multiple times. I looked at the HA Logbook and confirmed that my automation was triggered by the Lucid entering the Home zone.

The automation ran yesterday when I came home so HA knew that the car was in the Home zone. I have another automation to close the garage door when it exits the Home zone, and the Logbook does not have an event of the car leaving the Home zone last night.

I'm at a loss how this automation was triggered last night. Any ideas on how to debug this?
Click to expand...
This has been a common problem. Occasionally the API will error or fail to respond, which shows in Home Assistant as e.g. "Lucid Air XYZ has become unavailable." The location changes from Home to ???, then back when the API starts responding. One suggestion would be to add a condition to your automation, "If Lucid Air Power state is Drive" to make sure your car is actually driving and not just popping around in its sleep.
 
Thanks. I'm trying to add this condition but I'm not seeing "Drive" as an available state. I only have "Unavailable" or "Unknown" (see below).

1731618332925.webp
 
Anyone having issues getting things like the Garage Door to trigger with HA. I've messed around with this so much but still can't seem to get it to trigger


YAML: 
alias: Open Garage When Car Arrives Home
description: >-
  Opens the garage door when the car enters the zone, is in drive or reverse,
  and the garage door is closed.
triggers:
  - device_id: XXXX
    domain: device_tracker
    entity_id: XXXX
    type: enters
    trigger: device
    zone: zone.home
conditions:
  - condition: or
    conditions:
      - condition: state
        entity_id: sensor.lucid_air_gear_position
        state: drive
      - condition: state
        entity_id: sensor.lucid_air_gear_position
        state: reverse
  - condition: state
    entity_id: cover.garage_door
    state: closed
actions:
  - device_id: XXXX
    domain: cover
    entity_id: XXXX
    type: open
mode: single

The car is definitely being detected but the automation simply won't trigger. The reason I have "Drive" or "Reverse" as a requirement was because one day the car was just sitting in the garage and the door just randomly opened.

1732733817043.webp
 
HC_79 said:
Anyone having issues getting things like the Garage Door to trigger with HA. I've messed around with this so much but still can't seem to get it to trigger


YAML: 
alias: Open Garage When Car Arrives Home
description: >-
  Opens the garage door when the car enters the zone, is in drive or reverse,
  and the garage door is closed.
triggers:
  - device_id: XXXX
    domain: device_tracker
    entity_id: XXXX
    type: enters
    trigger: device
    zone: zone.home
conditions:
  - condition: or
    conditions:
      - condition: state
        entity_id: sensor.lucid_air_gear_position
        state: drive
      - condition: state
        entity_id: sensor.lucid_air_gear_position
        state: reverse
  - condition: state
    entity_id: cover.garage_door
    state: closed
actions:
  - device_id: XXXX
    domain: cover
    entity_id: XXXX
    type: open
mode: single

The car is definitely being detected but the automation simply won't trigger. The reason I have "Drive" or "Reverse" as a requirement was because one day the car was just sitting in the garage and the door just randomly opened.

View attachment 24832
Click to expand...
I think your "drive" and "reverse" just need to be title-case, "Drive" and "Reverse" - pretty sure it is case sensitive. Also, if you go to your automation and click TRACES, you can step through exactly what happened when it was last triggered to see why conditions are failing.
 
I just installed this, and it seems that even after I've been away from the car for a while, there is a sound coming from the car. Does this stop the car from "going to sleep"? Also, I tried to set up an automation to warn me when the battery was below 60%, but even though the battery is at 72%, it fired. Here is the yaml, can you see anything wrong with it?
- id: '1734025992822'
alias: Lucid Battery Low
description: Lucid battery below 60%
triggers:
- trigger: numeric_state
entity_id:
- sensor.lucid_air_remaining_battery_percent
below: 60
 
DanHi said:
I just installed this, and it seems that even after I've been away from the car for a while, there is a sound coming from the car. Does this stop the car from "going to sleep"? Also, I tried to set up an automation to warn me when the battery was below 60%, but even though the battery is at 72%, it fired. Here is the yaml, can you see anything wrong with it?
- id: '1734025992822'
alias: Lucid Battery Low
description: Lucid battery below 60%
triggers:
- trigger: numeric_state
entity_id:
- sensor.lucid_air_remaining_battery_percent
below: 60
Click to expand...
Unless you’re telling the car to unlock or something, Home Assistant won’t keep it awake. The car does just make noises sometimes. Battery conditioning things will run automatically if it’s hot/cold, and it wakes up a little bit every 2 hours to report status.

I don’t immediately see anything wrong with your automation. Check the Traces like I mentioned in the post before yours to see what triggered it?
 
DanHi said:
I just installed this, and it seems that even after I've been away from the car for a while, there is a sound coming from the car. Does this stop the car from "going to sleep"? Also, I tried to set up an automation to warn me when the battery was below 60%, but even though the battery is at 72%, it fired. Here is the yaml, can you see anything wrong with it?
- id: '1734025992822'
alias: Lucid Battery Low
description: Lucid battery below 60%
triggers:
- trigger: numeric_state
entity_id:
- sensor.lucid_air_remaining_battery_percent
below: 60
Click to expand...
You can check the status (and see the history for the status) of the car in HA; it will tell you if it has been asleep, for how long, in what state, etc.

Your automation looks fine enough to me. Run a trace.
 
The trace looks fine (see below). If the integration doesn't keep the car awake, how can the triggers happen?

And I do think the car was just pre-conditioning (it was cold that morning) so I think that was the noise I was hearing.
 
DanHi said:
The trace looks fine (see below). If the integration doesn't keep the car awake, how can the triggers happen?
Click to expand...
The car wakes up by itself every few hours to upload and download to the cloud.
Your trace data doesn't show up in your post!
 
Sorry, it's early still!

trigger: numeric_state
entity_id:
- sensor.lucid_air_remaining_battery_percent
below: 60
 
DanHi said:
Sorry, it's early still!

trigger: numeric_state
entity_id:
- sensor.lucid_air_remaining_battery_percent
below: 60
Click to expand...
Someone who knows more than I may correct this, but I believe the automation triggered because remaining_battery_percent changed. Take a look at the automation's decision tree on the left to see its progress through your automation. It should have bailed out upon deciding that the new remaining_battery_percent was not below 60.

HA trigger tree.webp
 
You must log in or register to reply here.

Similar threads

Fargoboy
Lucid integration for home assistant
Replies
6
Views
238
segbrk
S
Murcie
Software Improvements and Features Suggestions
4 5 6
Replies
102
Views
4K
Steveinarizona
S
A
The API shows a value named "battery health level". What is it?
2
Replies
20
Views
2K
ME2U
ME2U
D
Brief review of latest OTA and long road trips
Replies
1
Views
290
Haggy
Haggy
V
Known errors ( please list)
Replies
4
Views
636
Cosmo Cruz
C
Back
Top