Copied from the comments section……..

Hi everybody.

A new beta was just released today.

You can download this beta by following this link : https://testflight.apple.com/join/nhMX6f5n Edit: now published in the app store

WARNING : Version 4 of iOS CanZE need both WiFi and Cellular network.

To allow device connecting booth WiFi with dongle and Cellulat to CanZE Server, follow this tutorial :

  • Connect to the WiFi Dongle
  • Go to settings App
  • Go to WiFi settings
  • Select Dongle’s WiFi network
  • Tap the (i)
  • Note IP address and subnet mask
  • Switch from Automatic to Manual
  • Enter IP address and subnet mask
  • IMPORTANT, leave router blank
  • Validate

  • Growth slowing down to 2.4% last month
  • ANRs have gone to zero!
  • Crashes have gone down further, but a nasty regression slipped in just a few days ago. Put here is a 180 days graph for your perusal.

The problem is known and will be fixed soon. If you ignore that spike, you will see we went from hovering around 20 to around 3. Be aware that this graph runs across all app versions and there are always a few hundred un-updated versions out there.

As much as we like to cover the full ZE spectrum of the Renault brand, the time has come to end support for the Fluence ZE and Kangoo ZE. We have no access to these cars, there are no developers that do and there are active communities and apps for them. FluenceSpy by Alexandre Moleiro is one. Frankly, we never were able to do a good job there and we don’t want to promise more than we can deliver with at least some quality. It’s hard enough to maintain CanZE for the 90 and 110 models without free access to them.

The planning for deprecation is as follows

  • March 2019: this announcement
  • May 2019: message in the news bar in CanZE
  • July 2019: removal of specific code from the App

Of course you can still try to use CanZE in said models but some functions will not work properly anymore and we won’t accept any bug reports or requests that are specific for the models.

On the less sad side of things, a new Twizy owner has taken on the challenge to give the Twizy support a good crank. Stay tuned for news in that department.

As you probably noticed, a lot of work is being done. We’re gearing up for a new release again.

  • Added total kWh and charge counts in the (experimental) Charging history screen. Very useful if you are checking out a used ZOE.
  • Several bug fixes and internal improvements.
  • Some appearance cleanup.
  • Deleted Dutch language.

Some other announcements and tidbits

  • The usage of CanZE is growing more than 33% per 6 months.
  • Because of the frankly staggering numbers we’re now focusing more than we used to on usability, consistency and stability.
  • Largest countries (by far) are Germany, the UK and France, together more than 50% of the installs.
  • As a result, German, English and French are the installed default languages on over 70% of the CanZE users phones (meaning Android languages, not CanZE languages)

We are planning on discontinuing all but English, German and French language support and are in an active process of finding committed, tool based language maintainers for those. So if you want to become such a language maintainer (the named ones or another one), please contact us through the CanZE Github page.

After this release, it might be quiet for a while: while we urge anyone with even mild tinkering skills to build the CanSee dongle and dump the commercial one, we realize that over 99% of the users actually use and will keep on using those. We’re in a process of research and change to massively improve the stability of the ELM based dongles and we’re pretty sure most users will be very pleased when it’s done. However, it will take considerable time.

It’s only been an week, but we feel the need for some changes to be rolled out

  • Fixed negative numbers in Trip (Driving)
  • Much faster startup if you use the new, fast CanSee dongle
  • Fixed an issue that mostly produced wrong numbers in miles mode
  • Implemented a “news” bar on the main screen we can use to alert users
  • Moved Leak currents to Technical and made it more reliable
  • Fixed values not displaying in the experimental BCB screen

The trip function basically gives you a “Trip C”. Reset it by tapping it’s value area. It relies on trip B values supplied by the car so if you reset Trip B in the car, Trip C needs to be reset.

BCB and Leak Currents are helpful tools to assess charging problems. Note that HF Leak currents should not exceed 300 mA (preferably significantly lower), and that Ground resistance cannot exceed 150 or 200 ohms depending on model, and again, should preferably be significantly lower. On my home charger it is 11 ohms.

The next release of CanZE for Android will be released in the next few hours. I won’t be bothering you with with the usual bug fixes and small improvements, major internal cleanup, nor with the polished up support for the CanSee Dongle, about which we’ve teased you already so much. Though it is worth mentioning that using that dongle made a few things go so fast we had to tweak a few things to avoid the proverbial drinking from a hose. A few things are notable though.

Our friends in the UK will hopefully find our miles support vastly improved, especially in the consumption and driving screen.

After years of head scratching and lacking the means to find the issue, we can now finally get to the BCB and pry out all of it’s DTCs. As the BCB contains charging failure information, we’re really happy with this result. The issue was, as usual, completely trivial and implemented in maybe an hour so, but that’s always in hindsight.

We already announced TPMS. If you have a TPMS enabled car, get the IDs now before you have the tyres changed and then immediately again. The writing function is slightly under-tested with ELM dongles, so tread carefully. Feedback appreciated.

More is in the pipeline, which I think you will like.

We have an exciting new release coming up in a few days. Next to the inevitable bug fixes, we have a few new features we think you will love.

  • In the technical section, there is now a separate screen for the 12 volt battery. You can monitor here the voltage of the battery over time. Maybe we need to add current later. We’re not entirely happy about the color coded status lines, indicating charging and car status, but it was a needed compromise at this moment to show the changes in time.
  • We have slightly modified the consumption screen. We removed the capacity in Ah from the upper graph and replaced it with the SOC percentage from the lower graph. In the lower graph, we added a gradient representing the difference between real distance traveled and the change in the range indicator. It starts in the middle and will go up (red) if the range indicator decreases more than the distance traveled, or down (green) if it decreases less. We believe it is much more useful because it indicates if your initial planning, whatever that was, is still on track. If you love the old version, it has moved to the experimental section. We might depreciate it later though.
  • There is an experimental option to make a raw dump of all the frames we use. We need both your help and this activity to check out reports we’re getting about weird values when CanZE is used on Q90 and R90 cars.

Stay tuned and feedback, as always, is much appreciated.

Starting now, we might sometimes publish pre-release builds for people who want to be on the bleeding edge, but are unable to build from the source. I am still checking if these can be unsigned builds. Regard these pre-releases as unstable and unusable, but if you are not afraid of fiddling with APK files and not afraid to re-install older, more stable versions if things go haywire, you might want to grab these from github in the releases section. They will always be clearly marked with an orange “Pre-release” flag. Here is an example, where we added some interesting BCB stuff to the experimental section.