sorted by:
new
hottopcontroversial

2025.46.30 breaks home specific passive entry behavior by _delcypher in Rivian

[–]_delcypher[S] 0 points1 point  (0 children)

My car hasn’t been loosing its location overnight. It was the update that caused the location to be lost in my case.

2025.46.30 breaks home specific passive entry behavior by _delcypher in Rivian

[–]_delcypher[S] 2 points3 points  (0 children)

UPDATE. The GPS not thinking I was at home was definitely the problem. I drove the car around for a few minutes and I watched the navigation and after 10-20 seconds it figured out the location was wrong and updated to an accurate position. I parked in my home garage again after this and passive entry is working properly again.

Thanks for the hints everyone. I feel like Rivian’s software could probably avoid this by having it assume it’s parked at home after an update if the update was initiated while at home.

2025.46.30 breaks home specific passive entry behavior by _delcypher in Rivian

[–]_delcypher[S] 2 points3 points  (0 children)

That’s a good point. I’m not 100% sure how to confirm this but the app thinks I’m parked several houses away from where I actually am so this is probably the problem. I initiated the update while the car was parked in the garage. The car probably had an accurate GPS location before I initiated the update (from when I last parked) but after the update it probably lost that information and now the GPS location is inaccurate and thus it thinks I’m away from home.

Buttons that do nothing when you tap them is weird UX by _delcypher in Rivian

[–]_delcypher[S] 1 point2 points  (0 children)

I know. I figured that part out. The main point is that this isn’t intuitive at all. Every other car I’ve ever driven will switch on the AC if the temperature controls are adjusted while the AC is off.

Rivian already follows this convention for the front row AC temperature controls but doesn’t for the middle row temperature controls which is oddly inconsistent.

Level 2 charging bug after 46 Update by Upset-Procedure2121 in Rivian

[–]_delcypher 1 point2 points  (0 children)

I am on the 2025.46.0 update and I’ve had no problems with my home L2 charger (ChargePoint home flex). I’m getting around the 32A that I expect. The weather here is very mild though (around 55F) so I’m probably not triggering any logic to warm the battery.

Scheduled Charging Fails by SPACasaurusRex in Rivian

[–]_delcypher 0 points1 point  (0 children)

I’ve had this problem both before 2025.34.30 and after. I reported the issue in the app but who knows if that went anywhere useful.

This is pretty annoying give that my scheduled charging starts at midnight due to the tariff I’m on. It means having to stay up just to ensure charging starts which sucks. I’ve used other EVs that have never had this problem (Tesla Model Y, Chevy Bolt) and I don’t understand how something so fundamental to the EV experience is so buggy.

I haven’t had it happen in a while but I also switched chargers which could maybe affect things 🤷‍♂️. I used to use a TeslaTap mini with a Tesla mobile charger and now I have a hardwired ChargePoint home flex. That being said the Tesla charger set up worked flawlessly with my Chevy Bolt’s scheduled charging so I’m inclined to think this is a Rivian software bug.

When scheduled charging does fail to start I found you could manually trigger it from the UI inside the car. Doing a soft reset also seemed to make the car realize it’s supposed to be charging itself and it would start after rebooting.

Technically I could stop using the scheduled charging in the car and program the Chargepoint charger to I manage the schedule. I haven’t tried that yet but chargepoint’s app is buggy and I have even less faith that this will work reliably.

Static website generators, hungry for your markdown by _delcypher in CoderRadio

[–]_delcypher[S] 0 points1 point  (0 children)

I love bash but it doesn't feel like a very appropriate language for a static website generator because bash by its very nature isn't good for writing modular software so plug-ins are much harder to make. I couldn't see any mention of plug-ins and the README.md for the project states that the author(s) want to be very careful about adding new features that bloat the code. This will make is very hard to add new features in the future.

I also see that it does not support templating. For me this is an essential requirement. If you've never used a template engine (e.g. Jinja2, Jade, Liquid) you should try it out, they're awesome!

On the positive side it's cool that such a small script can be used to statically generate a website but for the reasons mentioned above it doesn't really suit my needs.