Device Constantly Reboots after Assigning Zones (Error -11)

If your Konnected device is stuck in a reboot loop after you've assigned one or more sensors to a zone/pin, you may unfortunately be a victim of a rare error that we're (affectionately) calling "Error -11". 

This issue is caused by an unknown HTTP error that usually shows up immediately after the device tries to update SmartThings with the status of a sensor. The error is unhandled and causes an internal panic error, resulting in the application rebooting. You'll see a very brief flash of the blue status LED upon reboot, sometimes followed one or more short flashes indicating sensor updates. This pattern will repeat itself indefinitely.

If you connect your device to ESPlorer to view the debug output, you will see some output like this:

NodeMCU 1.5.4.1
Konnected Security 2.0.5
 build 20170825 powered by Lua 5.1.4 on SDK 1.5.4.1(39cb9a32)
Heap:   41264  Initializing Konnected
Heap:   36840  Version:   2.1.0
Heap:   35184  Connecting to Wifi..
> Heap:   39656  Wifi connected with IP:   172.16.0.19  255.255.255.0  172.16.0.1
Heap:   36112  UPnP:   Listening for UPnP discovery
Heap:   35688  HTTP:   Starting server at http://172.16.0.19:17066
Heap:   35336  Loaded:   server
Heap:  31504  Initializing sensor pin:  6
Heap:  31456  Initializing sensor pin:  2
Heap:  31456  Initializing sensor pin:  9
Heap:  31456  Initializing sensor pin:  1
Heap:  31456  Initializing sensor pin:  7
Heap:  31456  Initializing sensor pin:  5
Heap:  31456  Initializing actuator pin:  8  Trigger:  nil
Heap:   31232  Loaded:   application
HTTP client: Disconnected with error: -11
HTTP client: Connection timeout
HTTP client: Connection timeout

 ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x40100000, len 24580, room 16 
tail 4
chksum 0xa2
load 0x3ffe8000, len 2268, room 4 
tail 8
chksum 0x7d
load 0x3ffe88dc, len 136, room 0 
tail 8
chksum 0x89
csum 0x89
„ã ì ÃgäÛsƒò'|ä$d$l` „ã{“dŒl Œþ

What Causes This Error?

We know that the error is related to the SSL/TLS implementation in the NodeMCU firmware version 1.5.4.1 which Konnected is built upon. We're hopeful that an upcoming release of the NodeMCU firmware will solve the problem. There are open issues here and here that we believe are related, and are working with the NodeMCU team to move these along. For now we can only work around the issue.

Who is Affected?

This issue seems to only affect a small (1% - 2%) percentage of users with a cable company provided cable modem. We don't understand why, but some cable company leased modems will cause this problem. This particular issue has been shown to be either present all the time, or not at all.

The Workaround

Most customers who have encountered this issue are able to resolve it by requesting a new modem from their cable company, or purchasing their own modem. Once the new cable modem is installed, the problem goes away. We know it sounds pretty ridiculous, but it usually works.