Samsung / Google smartwatch app for Lucid Motors' vehicles

I use a Garmin too, so let me know if you do!
In case you missed, I made something!

 
In case you missed, I made something!

Thank you!!! I'll give it a go as soon as I get my car back
 
I agree it's a great idea, but if there are folks having issues with the key fobs, phone app, and the card, there'll be situations where adding the watch app on top of the 3 still won't eliminate the problem...
The fob and the card work through a different mechanism than the watch app.
If the car and the watch both have internet connectivity, the WearOS app will work.
 
The fob and the card work through a different mechanism than the watch app.
If the car and the watch both have internet connectivity, the WearOS app will work.
In the case of my Garmin app, the watch can't make the connection directly, so the watch has to be in range of the phone (or A phone that it's paired to), and the phone has to have Internet connectivity, and the car has to have Internet connectivity. And Lucid's API service has to be up and working.

Not the ideal but it seems to work so far and it's there as a last ditch option if locked the phone/fob in the car and don't have the key card.
 
It just dawned on me that these watch apps will be a super handy option for the folks who keep complaining that the car locks with the key/phone left in the car.

As long as your phone is still on and has cell service, problem solved.
Bluetooth is all that should be needed?
Watch Bluetooth to phone
Phone Bluetooth to car?
 
Bluetooth is all that should be needed?
Watch Bluetooth to phone
Phone Bluetooth to car?
I don't think there any way to force the phone initiate or control anything with the car over Bluetooth, especially when the car is asleep.

The control I'm doing is just using the public (unofficial/unsupported) API then let Lucid's cloud wake up the car and send commands in the same way their own app does. None of that happens over Bluetooth.
 
I don't think there any way to force the phone initiate or control anything with the car over Bluetooth, especially when the car is asleep.

The control I'm doing is just using the public (unofficial/unsupported) API then let Lucid's cloud wake up the car and send commands in the same way their own app does. None of that happens over Bluetooth.
Wake up is localized if I conjecture about the architecture. You can still manage the car from your phone even with no cell service.
I can use the lucid app on my watch, which interacts with my iPhone (watch has no cell service).

So I’m guessing it has to be Bluetooth in one variation or another.
 
You can still manage the car from your phone even with no cell service
I could be wrong (wouldn't be the first time), but I don't think that's true. I mean the car will unlock when it sees the phone's Bluetooth (either passively or on a press of the door handle), but I really don't think there's any control actions communicated over Bluetooth.

Either the car recognizes your phone's Bluetooth and is willing to unlock, or it doesn't.
 
I've 'released' v0.2.0 of the garmin watch app. Gave the watch app some actual icons and more information. The phone app now grabs the car's status every 5 minutes and pushes the data to the watch. Though to be clear, if the car is asleep, it does NOT wake the car - and whatever information it grabs from Lucid is based on the last time the car uploaded data to lucid.
It also lets you set the climate on/off and choose the target temperature

The main screen also shows the inside/outside temperature reported by the car.

1793053466141.webp
1793053480130.webp
1793053456771.webp
 
Could a mod please retitle this thread to "Samsung / Google smartwatch app for Lucid Motors' vehicles"?
I'm about to release a new version of my watch app (details tomorrow) and am wondering if the term WearOS isn't widely understood.
Thanks in advance.
 
Could a mod please retitle this thread to "Samsung / Google smartwatch app for Lucid Motors' vehicles"?
I'm about to release a new version of my watch app (details tomorrow) and am wondering if the term WearOS isn't widely understood.
Thanks in advance.
Done.
 
I've pushed a new version (1.1.1) of the watch app, and it is available for installation. The major changes from v1.0.20 are:
1) Changed the Lucid email/password login screens to lessen the difficulty on some watch types.
2) Revised the confirmation dialogs for a better experience on some watch types.
3) Added the ability to tap on the charging power text to stop charging, with a confirmation dialog.
4) Color-coded the charging power display area to differentiate Plugged in, Charging, and RangeXChange states.
5) Color-coded the battery state-of charge display to reflect low charge <=20% and high charge >=80%.
6) Replaced all app icons with new artwork.
7) App has been renamed "Lucid Access".
8) Added a license file to the Github repository, open-sourcing the app for others to build on.

Current testers can update their watch app by uninstalling the prior version and installing the new one:
1) On the watch, access the watch's app list (Pixel watch - double press the crown), then scroll down to the "Lucid Cars" app bar and long-press it. Select Uninstall.
2) On the phone, find the app installation URL that I sent you for the initial install, click on it, and press install. You shouldn't have to log in again.

Remaining issues:
1) On app startup, a login screen with two choices sometimes pops up and disappears on its own after a second or so.
2) After pressing a frunk/door lock/trunk button, there is often a lag of several seconds to a minute before the button icons correctly reflect the state of the car. Until this is resolved, I'd suggest using these actions only within sight of the vehicle, and being patient about watching for the update.

I'll try to work on both of these in the coming week.
For reference, this is at https://github.com/DeaneG1967/Lucid-Motors-WearOS-Companion-App

If anyone would like to install this on their Android watch, send me a DM with your gmail address.
 

Attachments

  • watch_media_2026-10-27_11_00_22.webp
    watch_media_2026-10-27_11_00_22.webp
    11 KB · Views: 7
  • watch_media_2026-10-27_11_03_34.webp
    watch_media_2026-10-27_11_03_34.webp
    14.7 KB · Views: 7
  • watch_media_2026-10-27_10_08_09.webp
    watch_media_2026-10-27_10_08_09.webp
    17.4 KB · Views: 8
  • watch_media_2026-10-27_15_17_21 (1).webp
    watch_media_2026-10-27_15_17_21 (1).webp
    15.9 KB · Views: 8
  • watch_media_2026-10-27_10_56_22.webp
    watch_media_2026-10-27_10_56_22.webp
    13.3 KB · Views: 10
Last edited:
@DeaneG I'm totally stealing the color change idea for battery level! 😂

You might want to consider using "Access for Lucid" as the name, I believe (though not a lawyer) that ("for FOO") is a commonly accepted way of avoiding trademark issues.
 
I had some issues with text entry on the Galaxy Watch 7 and had Claude Code take a run at the problem. Watching it pull down the source, create the build environment, walk me through how to enable wireless debugging so it could push the re-built app up there, and then actually send the keystrokes to do its own testing was _wild_. It's drafted the patch for easy merging for @DeaneG.

@borski, you'd be proud :) The PR is here: https://github.com/DeaneG1967/Lucid-Motors-WearOS-Companion-App/pull/12

The fact that it handled all the forking, generation of PRs and even took the screenshots I requested during testing is truly astounding. It even killed developer mode and disabled the debugging access that is had upon request.

Attached are screenshots of the next logging flow, which updates the password entry screen to show the email address so that if your login fails, you can easily see if the email was what you intended.

If you are using the existing app and can't enter anything more than a single letter before the preview screen stops visually responding, hang in there, this should fix it.
 

Attachments

  • login_1_start.webp
    login_1_start.webp
    8.6 KB · Views: 5
  • login_2_email_keyboard.webp
    login_2_email_keyboard.webp
    10.8 KB · Views: 5
  • login_3_password_step.webp
    login_3_password_step.webp
    10.3 KB · Views: 4
I had some issues with text entry on the Galaxy Watch 7 and had Claude Code take a run at the problem. Watching it pull down the source, create the build environment, walk me through how to enable wireless debugging so it could push the re-built app up there, and then actually send the keystrokes to do its own testing was _wild_. It's drafted the patch for easy merging for @DeaneG.

@borski, you'd be proud :) The PR is here: https://github.com/DeaneG1967/Lucid-Motors-WearOS-Companion-App/pull/12

The fact that it handled all the forking, generation of PRs and even took the screenshots I requested during testing is truly astounding. It even killed developer mode and disabled the debugging access that is had upon request.

Attached are screenshots of the next logging flow, which updates the password entry screen to show the email address so that if your login fails, you can easily see if the email was what you intended.

If you are using the existing app and can't enter anything more than a single letter before the preview screen stops visually responding, hang in there, this should fix it.
Many, many thanks @coma24. I'll have a look at your pull request and will try to get a new build out in a day or two.
 
I had the same issue with my Galaxy Watch 7. I finally got it to work after killing the app a couple of times. Glad you were able to get a fix!
 
I had the same issue with my Galaxy Watch 7. I finally got it to work after killing the app a couple of times. Glad you were able to get a fix!
I was wondering if any other GW folks had the issue, thanks for the sanity check, but I'm glad to hear you were able to get logged in under your own steam.
 
Back
Top