If you want to learn about your Renault ZOE electric vehicle, you’ve come to a good starting point. We will supply you with an app that displays driving stats and lots of interesting information about your car. All you need is a Bluetooth OBDII dongle or a super fast do-it-yourself build CanSee dongle, and an Android device. For a more detailed description of the app see the about or the screenshot page. There is a sister project for Apple iOS.
Renault changed it’s API totally for the complimentary MY Renault app. Muscat did some reverse engineering and I implemented that in Node-RED. Please note there is zero error checking. The bottom two rows are examples that can be fed the same message as the Get battery status node.
I’ve been busy recoding the interface between my home automation and ZE services as Renault changed their entire apps and API to “MY Renault”. That worked out with the kind help provided by James. All back on track again in Node-RED.
While doing some research I ran into a post from one of the developers on the French forum. This was one of the things he mentioned that has always been “somewhat known”, but more precisely formulated now.
Start of charge
During charging, every 30 minutes (every 15min for Z.E. 40)
End of charge
Beginning of a journey
During the trip, every 30 minutes (every 15min for Z.E. 40) or every 5% of SOC (state of charge of the battery)
End of a trip
Before sleep (3 min after lockout) if the battery value has changed since the last message
Before sleep (3 min after lockout) if the car is not connected, a charge is programmed and the charge level is less than 100%
In the last 14 days almost 50% of all crashes came from one single user on Android 8.1 and Cubot J3 hardware. If you are that user, could you please leave a reply? We’d love to figure out what’s going on!
As mentioned a few times, the last few month lots of effort has gone into quality instead of features. And it has payed off. ANRs (App not responsive) and crashes levels are at or better than the average app. It seems dongle crashes have gone down too. Given the massive diversity in devices (dongles and phones/tablets), we consider this a great improvement, though admittedly you, the individual user, probably hardly noticed. A non-crash is and should be indeed a non-event.
This process isn’t finished. First of all it is something that we continuously monitor, especially after new features or fixes. Secondly and as announced earlier, we are in the process of sunsetting unmaintained languages as well as Fluence/Kangoo support to further cleanup code.
With this major effort behind us, this slowly gives space for functional development again. At this moment there are three issues that need our attention:
Resetting DTCs doesn’t work anymore (this seems to be a regression);
Setting TPMS IDs seems either buggy or not working at all (see next paragraph);
We need to make a version where all data is retrieved through ISO-TP commands. This requires lots of research but will enhance speed and stability on ELM type dongles a lot. For CanSee dongles, free frames are actually faster, so we try to use them as much as possible there.
Now features like TPMS are hard to implement and maintain. Being early adopters we don’t own cars with TPMS. It’s a bit hit and miss and politely asking for access to other people’s cars. And that issue is bound to get a lot worse soon: the new ZOE (nicknamed Gen 2) will be released in a few month. It will feature CCS, have a somewhat larger battery and I expect it will feature the same motor as the R110. Especially CCS will have significant impact on what we do with CanZE, notably of course in the charger sections.
We have no access to Renault’s designs, nor the Clip tool, nor a car to play with. Speaking for myself, I have no intention of buying a Gen 2 anytime soon. My 2013 Q210, which has done over 100.000 km now is trotting along quite nicely, showing 97% battery SOH (!!) and I sincerely hope it will for at least another 5.5 years.
We’ll have to see how we can keep up. With almost 5000 CanZE users on the current models, there is no reason for any immediate measures.