Limit charging to 95%???

Gen 4 Prime behaved that way too. I know there isn't a way to stop the charge automatically below the full charge level for the Gen 4 (at least that I've ever seen or head about. I suspect Gen 5 is similar, only because your post is the first of the Gen 5 Primes to get a post about it. but I'd love to hear someone find a way to stop the charge at 90 or 95% SOC.
With a downhill like you describe above you should be able to figure out at what SOC you need to stop the charge to get to the bottom with 100% SOC and no engine startup. Though in the summer you'll probably have to stop the charge earlier.

 

Depending upon your technical ability, you can use "smart home" automation to this. In my case, I use Home Assistant and a smart plug which monitors watt-hours. I can configure the plug to shut off after a certain number of watt-hours has elapsed which is fairly accurate assuming you tend to start with a empty battery. Obviously, this isn't as handy as being able to set a "max charge %" in the car's menu, but it does work.

 

Remember full charge is only around 80% charge, IIRC, just as "empty" is 20% full. I just don't worry about it and let the battery mgmt. sys. do its thang.

 

Any device suggestions? Can the smart plugs and app connect without any other equipment needed?
If other equipment is needed to get the monitoring functionality to work, what would be a minimal setup, either device(s) or cost wise?

 

The process is not for the faint of heart, but can make for a fun project if you like to tinker.

I use a Sonoff S31 smart plug which can also measure energy usage. I then flashed Tasmota to the S31 following this procedure. Once that is done, you need to install and configure Home Assistant. There are lots of devices that you can install this to, but probably the least expensive is a Raspberry Pi. Then, you link Tasmota running on your S31 switch to Home Assistant. This will let you monitor the energy usage and do actions based on it.

 

Thanks for the links and warning . I watched the Tasmota flashing videos and sussed out some more info about hubs and devices at amazon. Looks to me that to keep the home systems out of the cloud based services, it takes a bit of extra work. Keeping the smart devices on the local network is nice for added privacy since no one knows what's actually going on in the vendor cloud except maybe the vendor ( depending on which one's being used ).
I also read some descriptions in the Home Assistant forums about shelly z-wave and zigbee devices
Thought that maybe this Sonoff - Zigbee wifi gateway might work, until I remembered the ckiud and the real reason for flashing Tasmota.
SONOFF Zigbee 3.0 USB Dongle Plus-E - SONOFF Official
I've already got enough wifi devices, and should probably start administering them better than I have been instead of simply turning the unused ones on when they're needed occasionally.

 

Yes, that's why I put Tasmota on because that keeps everything local. As you say, it's a few more hoops, but I'd prefer to be the sole reason for my network outages. I haven't gotten into Zigbee yet as everything I use is currently WiFi.

 

Ashevillian is right that running the engine for five minutes is bad for it. ICEs wear most in the first few seconds on a cold start, before lubrication has come up to pressure and begun to fully flow. While they are running cold (and rich), they blow lots of unburned hydrocarbons into their oil, which would normally evaporate out when the oil got hot enough. Instead, if the engine does not warm up, it will stay there and corrode the engine from the inside. The same types of unburned hydrocarbons condense in the cold exhaust system and do the same kind of mischief there as well. Any mechanical engineer will tell you that if you start an ICE, you should run it until it's fully warmed up. In a non-hybrid vehicle, that takes about 10 miles. It will be further with a hybrid.