Search results

Yeah, it makes perfect sense. I'm just not sure why, at least in my case, it changed all of a sudden and high regen seems to have started taking a much bigger hit on efficiency.

I did just over 2500 miles across 10 days from San Diego to New Mexico and back. Some of the areas we went through have no chargers so I was trying to be as efficient as possible with the charging stops I was able to do. For now I'm going to keep it on standard regen to see how the...

This particular stretch from Carlsbad > Alamogordo includes the Cloudtop > Alamogordo section from 8600 ft down to 4000 ft that is almost all a 6% grade.

The two big chunks of driving on that Show Low > Casa Grande leg of the trip (the middle section is broken up a lot because I stopped to take pictures in a bunch of places) thanks to the great LucidTracker+ trips feature:

Yes. I don't often do many downhill grades like that here in SoCal but going from Cloudcroft, NM (elev ~8500ft) to Alamogordo, NM (elev ~4000) is where I first changed it. With standard I was able coast down the mostly 6% grade easily, at the start in high I was having to keep using the...

I've complained a few times recently that my efficiency dropped pretty significantly after one of the 3.5.x updates, even to the point that I asked service to look at it when I had the window regulator replaced last month. I've always used the high regen setting but on my road trip I was...

You're confusing two different things. Yes, the adaptive lights dim when they detect a car. These spots are there even if you disable the adaptive lights and are part of the light array placed there to create small gaps in the lighting beam to not blind oncoming drivers (nothing to do with the...

I got the Home Assistant notification that my Gravity was downloading an update but it hasn't popped up as available in the app for me yet.

No, there was a new option added in the Lucid app (v2.18) under where you do the fob software update that allowed you to name the key fob. It seems to have disappeared the the most recent app update (v2.18.1). Borrowed a pic @037 posted on his Facebook group to show the option:

EVgo keeps giving me $10 credits for some reason and so I go to one of the several near me to use them and they're always super slow. That said, on my road trip I ended up 50/50 with EA chargers working or not. Both Rivian chargers I tried were broken too. One charged at 49kW and then was...

I just used the ABRP app in CarPlay

I just used ABRP extensively on my road trip and it was great. You can actually go in to your saved vehicle and adjust the efficiency to your actual numbers to have it be more accurate with range.

I'm back. 2500+ miles in a bit over 10 days including several days of downpours in New Mexico. The wipers still have a little squeak when dry or just with a little washer fluid but worked great in the rain with no noise or chattering at all.

I'm surprised EVgo rates so high, the ones near me are terrible.

That has generally been my test as well but I was just on a 2500+ mi road trip and while in New Mexico several people flashed their headlights at me making me think the adaptive lights weren't working. I turned them off just in case only to have several more people flash their lights at me when...

Yeah, I think something gets stuck until the next sleep/reset.

Did you remove a charging stop that was automatically added and then add your own? That's the only time I've seen this bug.

I'd strongly recommend trying a faraday bag or box to put the key in. The cards won't activate the unlock from a distance but if the key moves at all (even shaking it if it's hanging on a hook) it can trigger the proximity unlock. I have a faraday box and even standing very close to the car...

Yes, there were definitely people who reported having the GPS stuck somewhere before CarPlay/AA were added. It seemed like it was happening late last year and then went away for a while and might be back.

Well I suddenly have this too for the first time. The biggest problem is that it disabled Dream Drive because it thinks I’m in a 25mph school zone. (and horrible timing as I leave on a 2500+ mile road trip on Wednesday) As to CarPlay/AA being involved, I know this bug existed for people before...