Skip to content

Debugging the Connect with "Blinky Lights"#

Starting with firmware version 2.1.18, Connect is able to blink out codes reflecting it's internal state. All current Connects should have firmware > 2.1.18, but if you're in doubt, you could call GET /users/bridges/mine

Verbose status mode is enabled by quickly pressing the button on Connect three times. 'Normal' status mode is re-enabled each time that Connect reboots.

While in verbose status mode, the green and red LEDs are used to blink status codes. You can decode the status of Connect by counting the number of times that an LED flashes and looking up the status on this table.


Informational#

Informational status codes are shown as some number of short flashes of the green LED:

#FlashesState
1Waiting for WiFi Provisioning
2OTA Update
3Connecting to WiFi
4Connecting to BLE
5Connected to BLE
6ASL showing dirty state
7ASL showing busy state
8ASL not advertising

Warnings#

Warning status codes are shown as some number of short flashes of the red LED:

#FlashesWarning
1 WAC Timeout
2 WiFi Link Down
3 WiFi association failure
4 Config socket error
5 RBS socket error
6 RBS server error
7 BLE communication error

Failures#

Failure status codes are shown as some number of long flashes of the red LED:

#FlashesFailure
1Out of Memory
2 Out of Threads
3 Library init failure
4 Can't get credentials
5 Socket IO
6 HTTP Setup
7 Server Communication
8 JSON formatting
9 Key Store failure
10 Server Authorization Failure
11 Bad Bridge ID
12 WiFi Authorization Failure

⚠ Warning#

It is often not possible to display the status codes as fast as the state of the Connect changes.

Since these status codes are not enqueued and displayed in order, a new status code may overlap an old status code. In that case, it may appear that an improbable or undefined state is being displayed. Relax–it's just two or more different status codes being concatenated.