2018-03-06: Recently we've received several reports of users' devices becoming unresponsive with a continuously rapidly blinking blue LED following a OTA (Over the Air) update. After some investigation, we've confirmed that OTA updates on devices with software version 2.1.1 and older will fail and leave the device in a bad state because they cannot contact GitHub. This problem just started occurring, and we think it's related to some change on GitHub's infrastructure.
Konnected's OTA update function works by checking GitHub's API for a newer released version of the Konnected code, and then downloading it. Recently and suddenly, the Konnected device is no longer able to query GitHub. It's possible that GitHub is intentionally blocking this type of API request, or that some change on GitHub's infrastructure has unintentionally broken this functionality.
My device is running version 2.1.1 or older, what should I do?
DO NOT tap the "Check for Update" button on the device status page. This will make the device unresponsive. We're working on a new solution to update the device safely. We will update this page when something is available.
My device is stuck in the failed update. How do I fix it?
Fortunately, it is easy to recover the device from the update loop. You will need to connect the device to your computer using a USB cable with a micro-USB connection.
Disconnect the power first!
It's easiest to do this step by removing the WiFi module from the Konnected base, and bring it to your computer desk.
- If you're using a Windows or Mac computer, installing a driver is necessary to connect to the device. Install the CH340 device driver for your operating system from here.
- Download ESPlorer which is a Java application that allows you to connect to, debug, and develop software for the ESP wifi modules. Drag ESPlorer into your Applications folder. You may also need to install Java if it's not already on your computer.
- Plug in the wifi module to your computer using a data quality USB cable.
- Open ESPlorer and select your the device port from the drop-down list. On Mac it’s something like
/dev/cu.wchusbserial1410and on Windows something like
Check your cable
If a serial port doesn't show up in the drop-down box, check your USB cable. Make sure it's a high quality cable that is capable of transmitting data.
- Set the baud rate to 115200 in the drop-down
- Click Open to establish a connection, then click RTS button twice to reset the device and you should begin to see output:
- Copy and paste the following command into the command bar in the lower right panel of ESPlorer:
- Click Send to execute the command. This will remove the files that cause the update process to initialize.
- Press the RST button on the device or toggle RTS in ESPlorer on and off to restart the device. It should now be operating normally.
- Unplug the WiFi module from your computer, re-insert the device back into its base, and re-connect the power.