Yeah, until you test it again for the 102nd time, then it won't be all green anymore... Been there done that, not with 1.7A but 1.5A and 1.6A. Gave up and had Blink send someone back to install the PLI.svBackstreets said:P.S. Thought I'd check my color sequence before I posted, so I ran the test for the 101st time. All green now.
Sent an email to Blink Support - apparently the 1.7 update wasn't supposed to fix the random reboot issues - so my bad luck may be a fluke. They are working on fixing the issue, but it appears it will take another month or two for a proper fix. Not good!drees said:FWIW - my Blink was very stable on 1.6 - rebooting perhaps once a week. Seems like its rebooting every 1-3 days now after upgrading to 1.7.
Have gotten maybe one good day of charge data uploaded to the website. So at least for me - 1.7 appears to be a step backwards in stability.
Since the update, mine has been rebooting about that often, too. A real possibility is that they did this on purpose. It's an old trick used by bad programmers who can't find bugs that crop up after the system has run for a while. Rebooting regularly will mask resource leaks and other things that cause problems. A "fix" for the 502 error, maybe?drees said:Sent an email to Blink Support - apparently the 1.7 update wasn't supposed to fix the random reboot issues - so my bad luck may be a fluke. They are working on fixing the issue, but it appears it will take another month or two for a proper fix. Not good!
Could be - sounds like the code is a bit of a mess.davewill said:Since the update, mine has been rebooting about that often, too. A real possibility is that they did this on purpose. It's an old trick used by bad programmers who can't find bugs that crop up after the system has run for a while. Rebooting regularly will mask resource leaks and other things that cause problems. A "fix" for the 502 error, maybe?
I concur - my symptoms are similar, though I've missed about every other day of uploads. And judging by the errors in my Blink's system log:drees said:FWIW - my Blink was very stable on 1.6 - rebooting perhaps once a week. Seems like its rebooting every 1-3 days now after upgrading to 1.7.
Have gotten maybe one good day of charge data uploaded to the website. So at least for me - 1.7 appears to be a step backwards in stability.
Aug 29 16:17:19 L2R17A user.crit MiniKitBrowser: [MINIKIT] fatal error, initiating reboot. Received EVSE HTTP Status code 502 on call to core wrapper.
Aug 31 08:42:35 L2R17A user.crit MiniKitBrowser: [MINIKIT] fatal error, initiating reboot. Core failure. Core threw an exception from getCurrentState method during EvseIPC processStateChange call.
Aug 31 08:42:35 L2R17A user.err MiniKitBrowser: [EVSECORE] Error: 12
Aug 31 08:41:35 L2R17A user.crit MiniKitBrowser: [MINIKIT] fatal error, initiating reboot. Core failure. Core threw an exception from getCurrentState method during EvseIPC processStateChange call.
Aug 31 08:41:35 L2R17A user.err MiniKitBrowser: [EVSECORE] Error: 12
Aug 31 08:40:34 L2R17A user.crit MiniKitBrowser: [MINIKIT] fatal error, initiating reboot. Core failure. Core threw an exception from getCurrentState method during EvseIPC updateCurrentState call.
Aug 31 08:40:34 L2R17A user.err MiniKitBrowser: [EVSECORE] Error: 12
Make sure you notify Blink support of your issues.SharonaLA said:Wanted to notify you that my blink crashed last night, failed to charge my car and then failed to charge it again when I returned home from teaching this afternoon.
I would suggest making this the 1st troubleshooting step!lkkms2 said:So, as one of the troubleshooting steps always reboot the Blink together with any other steps you think of to find/resolve the problem. It may save you an unnecessary trip to the dealers.
Enter your email address to join: