Here's my experience with the Blink<->LEAF charging options
If Blink is set to "Charge Immediately" (no timer mode) the LEAF behaves as it would if plugged into an AV or CC.
If LEAF has Timer mode programmed; need to press Timer Override button to start charging immediately.
Otherwise, blue lights just scroll, indicating valid connection with EVSE and Timer mode "ON"
Blink makes "thunk" sound when first connected in this mode then "thunks" again (relays on, then off)
If Blink is set for "Scheduled Charge" and that time has not arrived, plugging in the LEAF results in a momentary beep (from LEAF) but no "thunk" sounds. I think the beep indicates LEAF is connected (Blink screen acknowledges) but since there's no "active" connection signal, neither the LEAF scrolling lights (timer mode) nor charging lights come on.
When Blink "Scheduled Charge" time arrives, "active" connection signal happens and LEAF blue lights either
scroll while it waits for it's Timer mode to reach it's start charging time or
charging starts if Timer Override button was pressed or Timer mode is not active
In all cases, with the Blink, the charge timer clock runs whenever there's an active LEAF connection and the Blink is in charge mode (Scheduled or Immediate). This is of course, bogus since no charging is taking place if the LEAF is in Timer mode or if LEAF has completed charging. So, you can pretty much ignore the Blink charge timer clock on the screen.
As long as the Blink "Scheduled Charge" fully encompasses the LEAF Timer mode times then things work fine. I see no reason to use the Blink Scheduled Charge over the LEAFs. Except... if they get their website working so I can access my Blink from my phone or computer, I can imagine sometime wanting to Stop charging at some time before I between 80- 100% SOC. I can't do that with the Carwings (yet), so maybe this would be a useful feature from Blink.
One side note: If the Blink has lost it's WiFi connection, the button presses have a large lag to them so that it seems like it's way more unresponsive than usual. They've got too many cpu cycles tied up with the network stuff I guess so UI gets no attention when there's network issues.
If Blink is set to "Charge Immediately" (no timer mode) the LEAF behaves as it would if plugged into an AV or CC.
If LEAF has Timer mode programmed; need to press Timer Override button to start charging immediately.
Otherwise, blue lights just scroll, indicating valid connection with EVSE and Timer mode "ON"
Blink makes "thunk" sound when first connected in this mode then "thunks" again (relays on, then off)
If Blink is set for "Scheduled Charge" and that time has not arrived, plugging in the LEAF results in a momentary beep (from LEAF) but no "thunk" sounds. I think the beep indicates LEAF is connected (Blink screen acknowledges) but since there's no "active" connection signal, neither the LEAF scrolling lights (timer mode) nor charging lights come on.
When Blink "Scheduled Charge" time arrives, "active" connection signal happens and LEAF blue lights either
scroll while it waits for it's Timer mode to reach it's start charging time or
charging starts if Timer Override button was pressed or Timer mode is not active
In all cases, with the Blink, the charge timer clock runs whenever there's an active LEAF connection and the Blink is in charge mode (Scheduled or Immediate). This is of course, bogus since no charging is taking place if the LEAF is in Timer mode or if LEAF has completed charging. So, you can pretty much ignore the Blink charge timer clock on the screen.
As long as the Blink "Scheduled Charge" fully encompasses the LEAF Timer mode times then things work fine. I see no reason to use the Blink Scheduled Charge over the LEAFs. Except... if they get their website working so I can access my Blink from my phone or computer, I can imagine sometime wanting to Stop charging at some time before I between 80- 100% SOC. I can't do that with the Carwings (yet), so maybe this would be a useful feature from Blink.
One side note: If the Blink has lost it's WiFi connection, the button presses have a large lag to them so that it seems like it's way more unresponsive than usual. They've got too many cpu cycles tied up with the network stuff I guess so UI gets no attention when there's network issues.