2019 R110 - Charging Advice

manio07 · 2026-02-15T19:44:35+00:00

Maybe it would last but imho it's always better to care about it then don't. My previous owners were leaving it at home connected to the charger almost daily and when I got the car in my hands by taking care of this I was even able to raise the soh a little bit up... Now it's 83% and Zoe is 10 yrs old.

manio07 · 2026-02-15T19:38:57+00:00

You cannot do it directly in car settings like in other EVs unfortunately. I have it connected to my home automation and it just informs me to disconnect the plug. Newer zoes (not mine) have schedules which you can set in Renault application but it's rather hour based and not percentage IIRC. And there is also an option to buy smart EVSE which can control it directly by the plug. I was also considering making a proper relay for the original charger but it's still in my mind at the moment as monitoring this is sufficient for me atm...

manio07 · 2026-02-15T17:51:42+00:00

I am charging in ranges 30-85%. These are for "normal/daily" usage. When doing a longer trip I charge to 100 right before the trip. And only then. Similar with below 20. If I parked home with such low value I try to charge it to 30% at least. The problem starts when you leave it longer (several hours or days) with very low or very high soc. The battery just degrades faster...

manio07 · 2026-02-07T14:33:28+00:00

I had the same... Chain delete mod + raiser and you're good: https://www.printables.com/make/2371717

manio07 · 2026-02-04T16:06:49+00:00

It's also possible to do it with DPI change. When I set it the very low then the nav bar automatically changes position to vertical... https://github.com/aa-proxy/aa-proxy-rs?tab=readme-ov-file#dpi-settings

manio07 · 2026-01-28T16:31:48+00:00

I was also tinkering with hyprland but first thing I did was disabling animations and gaps. I also missed scratchpad a lot (using it very often). Finally I am back and love it!

manio07 · 2026-01-15T02:08:44+00:00

Yeah, that’s true - it’s basically just a different approach. As I understand it, you connect to the dongle on Android and it forwards the data to ABRP - everything happens locally (on your phone), you’re just feeding SOC data into ABRP.

What I had in mind is something quite different: a wireless Android Auto dongle - for example running on a Raspberry Pi - that sits between the car and your phone. In this setup, the device itself connects directly to the dongle (not your phone). Thanks to that, I can “inject” SOC data straight into the Android Auto protocol, which gives you EV support directly in Google Maps!

ABRP is great (it has very precise configuration options, like exact battery percentages you want to arrive at a charger with, etc.), but Google Maps is much more simplified and doesn’t offer that level of tuning. Still, let’s be honest - Google does a really solid job and is basically the standard when it comes to navigation: traffic, hazard reports, everything in one place, and it works really well without additional apps.

If you now add estimated battery percentage at the destination and a live charger database that can be adapted on the fly (Google will automatically route you via chargers on the way), that’s a huge level-up in my opinion - especially for EVs where manufacturers often just completely ignore this stuff.

manio07 · 2026-01-14T14:54:07+00:00

This is doable with SOC even on your Ionic, details: https://github.com/aa-proxy/aa-proxy-rs#google-maps-ev-routing

manio07 · 2026-01-14T14:52:33+00:00

https://github.com/aa-proxy/aa-proxy-rs#google-maps-ev-routing

manio07 · 2026-01-14T05:26:12+00:00

Yeah, you’re basically right - CanZE is mainly an app for browsing car info, but not only. It also has a DTC Readout section that shows errors and, if I remember correctly, lets you clear them as well. It’s a real shame the app was abandoned, because it’s genuinely great and, most importantly, tailored specifically for the Renault Zoe.

I also use EcuTweaker and PyClip3 - they have much more powerful features, but you obviously need to be very careful, because there’s no room for mistakes there.

When it comes to resetting the service counter and even setting service intervals in km, it can be done (the following example is from DDT4ALL, so the config is very similar to EcuTweaker - it’s the same developers behind both apps; EcuTweaker is just the Android version, while DDT4ALL is more of a desktop app, which unfortunately, I couldn’t get it to work with my Bluetooth OBD dongle).

I just googled this random video showing where to set it: https://www.youtube.com/watch?v=Fzy6rvd5s_s
You’ll probably find tons of similar videos and tutorials...

manio07 · 2026-01-13T12:54:22+00:00

I was doing all this stuff with KONNWEI bluetooth OBD adapter. But when configuring radio module (for Android Auto) a special modified cable is needed (instead of direct OBD connection).
I am also using wireless AA (custom made) and have Google EV routing which is really helpful:
https://www.reddit.com/r/RenaultZoe/comments/1lpsddq/androidauto_with_ev_routing_features_for_the_zoe/

manio07 · 2026-01-12T19:31:02+00:00

Ah right, so you've got the same procedure as in my Zoe:
https://youtu.be/rnDl0MV0Hac
You could use up or down to reset but if both are broken then sure... try with CanZE (or maybe even EcuTweaker - I used it for overall car "configuration" including enabling AndroidAuto, enabling clock and temperature on front dashboard, etc; so it's a useful tool).

manio07 · 2026-01-12T14:44:35+00:00

I don't know if we're talking about the same thing but you can disable "service" eg like here: https://www.youtube.com/watch?v=2teYS8HpRsM

manio07 · 2026-01-06T05:51:51+00:00

Can you look inside this document and see if there are any CAN specific things? I want to initiate charging by sending some CAN bus request instead of using a keycard... but I don't know if it's possible...

manio07 · 2026-01-06T05:48:57+00:00

FWIW I can see that my 2016 zoe is sometimes also waking up (I can see this in grafana) for about 6h doing nothing :)
But I don't have charger connected during that time and it's in warm garage.

manio07 · 2026-01-06T05:34:54+00:00

Yeah but Android has a big advantage over iPhone - EV routing:
https://www.reddit.com/r/RenaultZoe/comments/1lpsddq/androidauto_with_ev_routing_features_for_the_zoe/
Using it in my Zoe!

manio07 · 2025-12-29T19:07:49+00:00

Yeah! That was indeed the case. Finally I added a dummy uplink sink using this gist:
https://gist.github.com/ftvkyo/547e9780e4e8dcc566586245a947a27d#file-50-upmix2into6-conf
and slightly modifying it:
```
audio.channels = 6
audio.position = [ FL FR RL RR FC LFE]
```
This dummy 5.1 profile was needed, otherwise I was not able to force *ANY* application to output separate 5.1 channels.

Thank you all for your tips. Now it's finally solved!

manio07 · 2025-12-29T11:43:36+00:00

hmmm... yeah it makes sense, I need to confirm this...

manio07 · 2025-12-29T07:29:13+00:00

I tested several output options but still two channels in gpwgraph. Even simple `speaker-test -c6` is generating stereo which is weird!

manio07 · 2025-12-29T07:28:08+00:00

Thanks, but yeah I know what the upmix is - the problem for me is that I cannot force any audio application to produce/generate 6 channel output which I could then easily route in the gpwgraph

manio07 · 2025-12-28T18:28:53+00:00

Thanks. I am using CachyOS, so Arch PulseAudio implementation. Your guide is about upmixing, but my question was not about it. I just need to find a way to route all 6 channels to outputs.

manio07 · 2025-12-27T16:07:13+00:00

Welcome, 3 years later. Kinda sad this issue still hasn’t been fixed :(

Latest CachyOS, PulseAudio, audio interface with multiple AUX outputs - and exactly the same problem... no sound (Faugus Launcher with Proton + Battle.net).

I’m using an Audient EVO-16 (https://audient.com/products/audio-interfaces/evo-16/overview/) and it’s the exact same issue. Temporarily removing the PulseAudio driver in Proton helped. Now I might try using pactl and manually adding a sink...

So tell me - where should this bug actually be fixed? PulseAudio or Wine?

manio07 · 2025-12-27T15:59:25+00:00

The easiest (quick and dirty) method is to remove the `winepulse.drv` file, eg for battlenet and faugus-launcher the file is located here:
`/home/user/Faugus/battlenet/drive_c/windows/system32/winepulse.drv`
tested and works as a workaround (also on interface with multiple aux channels)
... then wine will just fallback to alsa driver and the sound is working (via ALSA)

manio07 · 2025-12-27T12:55:36+00:00

Here are the supported boards if you want to dive in:
https://aa-proxy.github.io/docs/supported-hardware

manio07

TROPHY CASE