New Firmware Pushed : L2R.1.3A

[Elofan]

I've been using my Blink for two weeks now. I noticed yesterday that firmware version L2R.1.3A had been pushed onto it. The main issues that I have been having is the "charging" message when no charging was actually happening (since I have a timer set), the wireless dropping periodically requiring a power cycle, and most annoying is the 80% timer in the car would not start, or it would start then stop or generate a fault message on the Blink.

This morning I checked the car and it has successfully charged to 80%, although the Blink still indicates "charging". We'll see if it successfully charges a few times before I call that issue fixed.

[sparky]

Thanks for the heads up. Mine has been updated to 1.3A as well.
This is my 4th firmware update in about 10 weeks of Blink-ing.
My unit exhibited similar problems to what you described, and in the last two days had gotten much worse with two failed timer mode charging cycles and an annoying "Charging Delayed" screen when I power-cycled the unit that required me to wait 10 more mins to see if it would start charging!

I hope those problems were before the last update.
I wish Blink would email me when they do these updates so I know to monitor behavior more closely.

[Randy]

My Blink downloaded firmware 3A last night, but now it has lost all network connectivity.

I came out into the garage this morning to take out the trash and I unplugged the car. The Blink screen screen still said "Now Charging" with the charge time still ticking away. I unplugged it and rebooted it, waited a few minutes and tried to connect with my browser. It woudn't connect, so I went out to the garage and re-setup the wireless network. I tried both static IP and DHCP and neither produced any conectivity. Rebooted my WAP and laptops can connect to it fine, but the Blink acts like no wireless signal is present...

It charged my car last night, but has lost network functionality with this new firmware update. Anyone else having the same issue? I'm going to let ECOtality nkow about it...

Randy

[evnow]

Anyone has a list of fixes they have observed ?

[DeaneG]

So that's what the clunking and beeping was in my garage late last night...a firmware reboot. Where is the changelog??

[DarkStar]

My Blink was all locked up this morning, however it is stuck on "Charging." I unplugged the car and pushed the option to stop charging and I left it with the "Processing" screen just sitting there...

When I get home tonight, I imagine that the "Processing" screen will still be there and I'll have to cold-boot the Blink... I did notice though that it had no wireless connection this morning before I unplugged.

[bowthom]

Hello Blinkers,
My unit updated too. Ethernet last communication was 11:46 PM 3/31 according to the display and no network connection but I can log into the UI so it has to work. The "day:hour:minute:second" digits are displaying in the UI although it shows 14:11:38:42. 14 days? It's been installed for 19 days.

Under the info screen (UI and Blink) the device ID has gone blank and now the network connection says "yes."
System uptime is 15 hours so it may have upgraded at 6:00 PM last night.

The last charge window no longer appears and checking the Blink network reveals my charge data from yesterday is not present but it shows the last charge as April 1.

The clock was slow by 12 hours. Don't know what happened there, maybe that's why the data is missing.

While I was standing there the screen went blank and came back up on the setup screen which I started then escaped and it was back to normal. Did not reset the "system uptime."

System log lists repeated clock errors???????
Apr 1 16:54:36 evse2 daemon.info EVSE-Client[25392]: HTTP error 400:E001 in blink clock service: [E001]: No GUID provided in request

It appears they have slowed down the connection interval, no longer calling home every 15 min.

In conclusion, IMO this was a quickie band aide to solve some issue but the main ones are still pending until the next update. Clock displays are still off between UI and the unit.

Dang it, I have to redo all the drive, charge & reporting tests. I still can not correlate Blink data to the Carwings data.

[azdre]

Got the new firmware and it forgot the network key overnight. At least it remembered my hidden SSID and I only had to re-enter the key.

[Jimmydreams]

My Blink is still running the L2R.1.2A firmware. It's hardwired, so I doubt there were any connectivity issues. Tech support is supposed to call today to work through some of the issues I've been having. We shall see....

I wonder if they specified the upgrade to individual units to avoid a 'Blink wide' problem should the new upgrade not work very well?

[Fabio]

The technician I talked to from blink got me worried about their attitude.
I was told that a problem that can be fixed by a hard reboot is not a big deal (except if it happens at 1am, and I have no charge in the morning), that I should be using the blink timer and not the leaf timer (despite the fact that you can't possibly program it to charge at the recommended 80%). I'm having 2nd thoughts about getting ready of the aerovironment unit. It may be built cheaply, but its simplicity may be its best feature (the less moving parts, the less things that can go wrong)

My Blink is still running the L2R.1.2A firmware. It's hardwired, so I doubt there were any connectivity issues. Tech support is supposed to call today to work through some of the issues I've been having. We shall see....

I wonder if they specified the upgrade to individual units to avoid a 'Blink wide' problem should the new upgrade not work very well?