Bug fixes only. Changelog can be found here.
Things have been slow as vacation progressed. And of course now work is competing. But that doesn’t mean things have halted. A new release is in the making, though it mainly fixes language and edge case stability issues. No new functionality.
- Growth has slowed down but is still going on quite nicely: 2.4% in the last 30 days and we’re now at about 5300 active Android devices
- ANR’s are virtually zero (one user impacted)
- Crashes are down to a record low 0.15%, less than one per day. This is half of the peer median. And half of those are Bluetooth related.
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%
- Low battery alert
- Instant pre-conditioning set point.
- 3.3% growth last month
- One ANR from a very old version. That doesn’t count 😉
- Crashes about 1.5 per day, more than half of them caused by an uncatchable error related to Android 8.1
Thank you all for installing and running no less than 5000 CanZE instances on Android! A humbling number for a total amateur project.
Copied from the comments section……..
A new beta was just released today.
You can download this beta by following this link : https://testflight.apple.com/join/nhMX6f5n
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
Although the last picture of Raplh’s Zoe Plugin has a make-like flair, he didn’t stop there and even installed some led indicators using a NeoPixel strip.
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!
Thanks to Ralph for sending me pictures of his Zoe plugin, which is basically a CanSee dongle that exactly fit’s into the car. But take a look at the pictures yourself.