New Firmware Pushed : L2R.1.3A

[evnow]

The technician I talked to from blink got me worried about their attitude.

Was this after the new firmware or before. Let us keep this thread to changes observed/not observed in the new firmware.

[TomT]

I didn't pay any attention to the Blink before I left this morning since I was successfully charged to my normal 80% but I just checked the Blink network and it shows my charger with the new firmware but still charging...

[evnow]

I didn't pay any attention to the Blink before I left this morning since I was successfully charged to my normal 80% but I just checked the Blink network and it shows my charger with the new firmware but still charging...

Yes - mine didn't change the status when I disconnected. But this has happenned before - though not consistantly.

[Fabio]

I believe the 1.3A firmware was pushed to my blink yesterday during the day (I am 90% sure), I know that it's running 1.3A right now.
When I came home and I connected the leaf, it didn't go in the usual 3 blinking light mode (wait for timer).
I had to reboot the blink twice for the blink to get to the leaf to get into wait for time.

The technician I talked to from blink got me worried about their attitude.

Was this after the new firmware or before. Let us keep this thread to changes observed/not observed in the new firmware.

[Gonewild]

Did they add a screen saver to this version because I did not see it before. Now the screen stops at a calibrate view where before it all was had a clock.

[Fabio]

My impression is that it rotates from the calibrate (with a timer shown as a reverse-progress bar growing from left to right, very counter intuitive, BTW) screen to the main screen and back.

Did they add a screen saver to this version because I did not see it before. Now the screen stops at a calibrate view where before it all was had a clock.

[sparky]

I suggested to Blink that they send and email when firmware is updated.
I received a very prompt response with this description of 1.3A

The issues the 1.3a are to fix are the following:
1 Pointer calibration loop.
The Blink goes into pointer calibration randomly. Sometimes, it will return to the pointer calibration after performing it or letting it time out. It may loop forever doing this. (Coherence #6376)

2 Reboot / Reset
The Blink will reboot randomly, especially while charging. (Coherence #6041, 6423)

3 Scheduled charge timer wrong
The Blink may omit the hour field, and put the days pending field in the timer that shows when a scheduled charge will begin. (Coherence #6491)

4 Wifi connectivity
The Wifi will randomly stop working, requiring either a reboot or to do the setup over again. (Coherence #6330.) The Wifi will now be automatically reset, so there will be brief interruptions, but the user won’t have to do anything.

[evnow]

1 Pointer calibration loop.
4 Wifi connectivity

Apparently they have fixed 2 problems I faced. I'll power loop today and observe whether the problems are actually fixed over the next week ...

Still, not fixed
- "Charging" message when just connected
- Leaf timer vs Blink timer issues
- Screen saver

[turbo2ltr]

4 Wifi connectivity
The Wifi will randomly stop working, requiring either a reboot or to do the setup over again. (Coherence #6330.) The Wifi will now be automatically reset, so there will be brief interruptions, but the user won’t have to do anything.

This isn't a fix, it's a bandaid for poorly designed hardware. I think all blinks with the current hardware rev will continue to have problems. Software can only fix so much.

I've noticed that the LEAF charger puts out a lot of EMI on the powerline, and I have a feeling the blink isn't handling it well.

[bowthom]

Hello Blinkers,
About an hour ago an update got pushed into the Blink, still shows ver 1.3A

Apr 1 18:07:25 evse2 user.notice core.out: udhcpc (v1.17.1) started
Jan 1 00:00:28 evse2 syslog.info syslogd started: BusyBox v1.17.1
Apr 1 18:06:59 evse2 syslog.info syslogd exiting

Noted changes:
Last charge window has re-appeared.
Device ID has returned
Calling home at 15 min intervals again.
"System uptime" has been reset.
Notice the time stamp on the update, it is logging at 6:07 PM 7 hours ahead. This exceeds any DST + time zone difference. Looks like logging is at UTC.
Repeated clock errors in the sys log seem to be gone.
Time errors between screens (blink & UI) still present.