borski / ha-lucidmotors Goto Github PK

Would be nice to stick the release notes link somewhere as well.

Maybe an AlarmControlPanel entity if that's not too overkill

"Charge Limit" slider allows setting of any integer value 0-100%. Setting it to anything <50% (not allowed on vehicle) generates error "Failed to call service number/set_value. StatusCode.INVALID_ARGUMENT: Key: 'SetChargeLimitRequest.ChargeLimit' Error:Field validation for 'ChargeLimit' failed on the 'min' tag"

Should be restricted to valid values for the vehicle, which is 50-100%.

Make it similar to the HA Tesla integration, which limits the slider to 50-100% only. (see screenshot)

I'm seeing warnings like the following in the logs:

2024-02-19 14:30:48.211 WARNING (MainThread) [homeassistant.components.climate] Entity None (<class 'custom_components.lucidmotors.climate.LucidClimate'>) implements HVACMode(s): off, heat_cool and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/borski/ha-lucidmotors/issues

It says to report this as a bug, so that's what I'm doing. Thanks in advance for your continued help.

TPMS sensors report "unknown" when car is not in use. Would be helpful to cache most recent values and keep them persistent while car is off.

Hello this integration is not working for non-US accounts...is there a way to make it work?

Thanks.

The salesforce service returns service appointments with dates.

When I woke up this morning, I was surprised to find that the garage door was open. It turns out that at 4:12:15 AM my car's device location changed to "home", but it never left the garage. The location change fired off my automation to open the garage door, leaving it open. I got push notifications after 30 minutes (a separate automation), but didn't see them till I got up.

Checking the log book I see that the car was first reported as "not_home" at 12:12:15 AM, then at "home" almost exactly 4 hours later. Also just after the "home" event I see this one:

Lucid AIR Power state  changed to Cloud 2

Just in case I checked for other log events and none of the other doors or windows were opened. Also there were no camera event around these times.

Maybe what happened was a reset of some kind on the Lucid service side that generated the spurious not_home /home events?

I can work around this by making my automation smarter. I'm reporting the issue here in case there's something that could be done at the integration level to deal with Lucid service availability issues.

Note that I can't prove that there was a Lucid service issue. In the log file the only Lucid entry is this unrelated problem:

2024-02-19 14:30:48.211 WARNING (MainThread) [homeassistant.components.climate] Entity None (<class 'custom_components.lucidmotors.climate.LucidClimate'>) implements HVACMode(s): off, heat_cool and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/borski/ha-lucidmotors/issues

I can report the climate issue separately, if that helps.

I'm assuming a "charge" switch would work for that. Otherwise a pair of buttons? Uses charging_service.StartSession and StopSession I think.

PI 4

Core
2023.11.2
Supervisor
2023.11.3
Operating System
11.1
Frontend
20231030.2

Could not configer in Intergrations tried rebooting installing uninstall and install again no go

Error
Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

Unable to install package lucidmotors @ git+https://github.com/nshp/python-lucidmotors: ERROR: Cannot install lucidmotors==0.1.0 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

trip_service.ShareTripRequests takes a list of waypoints and sends a route to the car. Not sure how this would look in HA land.

Not a huge deal, but I think the frunk and trunk should be Cover entities of type Door rather than Locks. This would mainly just make the buttons correct - you're not unlocking the trunk, you're opening it.

Number entity supports displaying as a slider, that would probably look best

Sensor "sensor.{vehiclename}_charge_session_time_remaining" reports back an oddly formatted value... not something very human readable like other sensors. Mine reports '1092:15:00', however this is when there's no charge session running, so not sure if the formatting is odd only for the case of no charging in process, or always. Haven't checked it during a charge session