Whitelist Lucid domains?

[NoseyReporter]

Recently I've connected my Gravity to a new network that sits behind pfsense router. This particular router uses pfblockerng with some semi aggressive blocking.

Well when I'm on this network, the Lucid app cannot connect to the car. Both the phone and the car are both connected to the same network, so presumably one of the blocking filters on the router is causing an issue.

Does anyone have a list of domains I can whitelist?

 

[doubletwist]

Not off the top of my head but if you enable logging on the pfsense, you should be able to figure them out. Alternatively you might be able to do a packet capture to figure it out.

I'm not sure when I'll have time but if I can (and if I remember) I'll try the same with my Unifi setup and post here. Mine is an Air but I can't imagine they don't use the same same endpoints.

 

[knewman]

Not sure if Lucid has published anything, but here's everything my car has queried over the past day or so:

www.google.com
connectivitycheck.gstatic.com
streamingapi-lucid24-gdg2-prod.mountain.siriusxm.com
www.buzzsprout.com
audio.buzzsprout.com
cloud-logger-vehicle-icc-customer.data.lucidmotors.com
router.hereapi.com
emqx-oss.deneb.prod.infotainment.pdx.atieva.com
vehicle.deneb.prod.infotainment.pdx.atieva.com
spclient.wg.spotify.com
cloud-logger-vehicle-customer.data.lucidmotors.com
api.pocketcasts.com
prfx.byspotify.com
play.podtrac.com
traffic.megaphone.fm
dcs.megaphone.fm
refresh.pocketcasts.com
smy.iheart.com
api-us-oci-lucid.houndify.com
traffic.vector.hereapi.com
crashlyticsreports-pa.googleapis.com
locs-vr-us.pictor.pdx.prod.dataconnectivity.lucidcars.io

 

[socktucker]

Not sure if Lucid has published anything, but here's everything my car has queried over the past day or so:

www.google.com
connectivitycheck.gstatic.com
streamingapi-lucid24-gdg2-prod.mountain.siriusxm.com
www.buzzsprout.com
audio.buzzsprout.com
cloud-logger-vehicle-icc-customer.data.lucidmotors.com
router.hereapi.com
emqx-oss.deneb.prod.infotainment.pdx.atieva.com
vehicle.deneb.prod.infotainment.pdx.atieva.com
spclient.wg.spotify.com
cloud-logger-vehicle-customer.data.lucidmotors.com
api.pocketcasts.com
prfx.byspotify.com
play.podtrac.com
traffic.megaphone.fm
dcs.megaphone.fm
refresh.pocketcasts.com
smy.iheart.com
api-us-oci-lucid.houndify.com
traffic.vector.hereapi.com
crashlyticsreports-pa.googleapis.com
locs-vr-us.pictor.pdx.prod.dataconnectivity.lucidcars.io

I wondered who provided the garbage Lucid Assistant. Sound Hound apparently

 

[NoseyReporter]

Not sure if Lucid has published anything, but here's everything my car has queried over the past day or so:

www.google.com
connectivitycheck.gstatic.com
streamingapi-lucid24-gdg2-prod.mountain.siriusxm.com
www.buzzsprout.com
audio.buzzsprout.com
cloud-logger-vehicle-icc-customer.data.lucidmotors.com
router.hereapi.com
emqx-oss.deneb.prod.infotainment.pdx.atieva.com
vehicle.deneb.prod.infotainment.pdx.atieva.com
spclient.wg.spotify.com
cloud-logger-vehicle-customer.data.lucidmotors.com
api.pocketcasts.com
prfx.byspotify.com
play.podtrac.com
traffic.megaphone.fm
dcs.megaphone.fm
refresh.pocketcasts.com
smy.iheart.com
api-us-oci-lucid.houndify.com
traffic.vector.hereapi.com
crashlyticsreports-pa.googleapis.com
locs-vr-us.pictor.pdx.prod.dataconnectivity.lucidcars.io

Thank you sir! You saved me a bunch of time, and I would have happily sat down this weekend to do it but I figured I'd ask around first.

First try, I added:
.lucidcars.io
.lucidmotors.com

Forced a reload on pfblockerng, and everything seems to be working good now.

Oh i just noticed the atieva domain. I better add that too.

 

[blagar1000]

I was curious what these websites do, so I asked Gemini and ChatGPT... let me know if they clearly got any of this wrong:

1. Connectivity & Diagnostics ​

• connectivitycheck.gstatic.com & www.google.com: These are used to verify internet access. Cars often use it to determine if they can reach cloud services or need to switch connectivity modes (Wi-Fi / cellular).
• crashlyticsreports-pa.googleapis.com: This is a standard Google service (Firebase Crashlytics) that reports the vehicle’s infotainment or connected systems log errors/crashes to Lucid's engineers.
• cloud-logger-vehicle...lucidmotors.com: Lucid cloud backends that collect vehicle telemetry & logs. This is the car sending its "health reports" back to the mothership. It tracks things like battery performance, sensor data, and system logs.

2. Infotainment & Audio ​

• streamingapi...siriusxm.com: Specifically for the 360L experience. This allows for the "On Demand" and "Extra Channels" features that stream over data.
• spclient.wg.spotify.com & prfx.byspotify.com: These are for handling streaming, album art, metadata, and configurations for Spotify.
• api.pocketcasts.com & refresh.pocketcasts.com: Since Lucid has native Pocket Casts integration, these sync "New Episodes" and playback progress.
• play.podtrac.com, traffic.megaphone.fm, & audio.buzzsprout.com: These aren't apps; they are the "plumbing" for podcasts. Most podcasters use these services for hosting and download analytics. When you play a show on Pocket Casts, the car reaches out to these servers to pull the actual audio file.
• smy.iheart.com: iHeartMedia podcast/streaming endpoints for audio delivery & stats.

3. The "Brain" ​

• ...atieva.com: Atieva was the original name of Lucid Motors (and remains their corporate engineering name). These URLs are the core "nervous system" of your car and are used for in-car systems, media, nav, and app frameworks.
  • deneb is the internal code name Lucid uses for its infotainment platform, and deneb.prod.infotainment suggests the car is communicating with the production environment.
  • emqx-oss suggests they are using EQMX, an open source MQTT (Message Queuing Telemetry Transport) broker. This is a lightweight messaging protocol designed for real-time machine-to-machine and Internet of Things communication. It’s likely what allows the car to talk to the Lucid mobile app.
• api-us-oci-lucid.houndify.com: This is the engine behind "Hey Lucid." Houndify (by SoundHound) is the voice AI that processes natural language requests.

4. Location & DreamDrive​

• router.hereapi.com & traffic.vector.hereapi.com: Lucid uses HERE Technologies for its mapping and navigation data. These are providing GPS rounting and map tile requests and real-time traffic updates, respectively.
• locs-vr-us.pictor.pdx...lucidcars.io:
  • Gemini says: This appears to be part of Lucid’s data pipeline for "Visual Recognition" or location-based services. "Pictor" is often associated with image or visual data pipelines, and "pdx" usually refers to a regional data hub (Portland). This suggests it's likely involved in how the car processes map data or sensor information for the DreamDrive system.
  • ChatGPT says: A telemetry/position reporting service (typically vehicle location, possibly ROOT Analytics / backend routing).

 

[Truthlesshunter]

lay.podtrac.com, traffic.megaphone.fm, & audio.buzzsprout.com: These aren't apps; they are the "plumbing" for podcasts. Most podcasters use these services for hosting and download analytics. When you play a show on Pocket Casts, the car reaches out to these servers to pull the actual audio file.

that's pretty cool. That would explain why I don't hear some ads when i'm listening to pocket casts at home while connected to pi hole and i hear them in the car

 

[borski]

I was curious what these websites do, so I asked Gemini and ChatGPT... let me know if they clearly got any of this wrong:

1. Connectivity & Diagnostics ​

• connectivitycheck.gstatic.com & www.google.com: These are used to verify internet access. Cars often use it to determine if they can reach cloud services or need to switch connectivity modes (Wi-Fi / cellular).
• crashlyticsreports-pa.googleapis.com: This is a standard Google service (Firebase Crashlytics) that reports the vehicle’s infotainment or connected systems log errors/crashes to Lucid's engineers.
• cloud-logger-vehicle...lucidmotors.com: Lucid cloud backends that collect vehicle telemetry & logs. This is the car sending its "health reports" back to the mothership. It tracks things like battery performance, sensor data, and system logs.

2. Infotainment & Audio ​

• streamingapi...siriusxm.com: Specifically for the 360L experience. This allows for the "On Demand" and "Extra Channels" features that stream over data.
• spclient.wg.spotify.com & prfx.byspotify.com: These are for handling streaming, album art, metadata, and configurations for Spotify.
• api.pocketcasts.com & refresh.pocketcasts.com: Since Lucid has native Pocket Casts integration, these sync "New Episodes" and playback progress.
• play.podtrac.com, traffic.megaphone.fm, & audio.buzzsprout.com: These aren't apps; they are the "plumbing" for podcasts. Most podcasters use these services for hosting and download analytics. When you play a show on Pocket Casts, the car reaches out to these servers to pull the actual audio file.
• smy.iheart.com: iHeartMedia podcast/streaming endpoints for audio delivery & stats.

3. The "Brain" ​

• ...atieva.com: Atievawas the original name of Lucid Motors (and remains their corporate engineering name). These URLs are the core "nervous system" of your car and are used for in-car systems, media, nav, and app frameworks.
  • deneb is the internal code name Lucid uses for its infotainment platform, and deneb.prod.infotainment suggests the car is communicating with the production environment.
  • emqx-oss suggests they are using EQMX, an open source MQTT (Message Queuing Telemetry Transport) broker. This is a lightweight messaging protocol designed for real-time machine-to-machine and Internet of Things communication. It’s likely what allows the car to talk to the Lucid mobile app.
• api-us-oci-lucid.houndify.com: This is the engine behind "Hey Lucid." Houndify (by SoundHound) is the voice AI that processes natural language requests.

4. Location & DreamDrive​

• router.hereapi.com & traffic.vector.hereapi.com: Lucid uses HERE Technologies for its mapping and navigation data. These are providing GPS rounting and map tile requests and real-time traffic updates, respectively.
• locs-vr-us.pictor.pdx...lucidcars.io:
  • Gemini says: This appears to be part of Lucid’s data pipeline for "Visual Recognition" or location-based services. "Pictor" is often associated with image or visual data pipelines, and "pdx" usually refers to a regional data hub (Portland). This suggests it's likely involved in how the car processes map data or sensor information for the DreamDrive system.
  • ChatGPT says: A telemetry/position reporting service (typically vehicle location, possibly ROOT Analytics / backend routing).

All look correct to me