This article gives explains the status area at the top of the Wireless Endpoint. This is open area in the screenshot below. Most of the elements we'll discuss will familiar to those who have already used the Wireless Endpoint. Still some debug elements might be new.

All devices use the same UI and nearly the same back-end code. The top area indicates the state of the app.  In the same order as on the UI, there are following statuses

• Ready
• Contacting
• Registered
• Armed
• Running

Ready state

This is an uncommon state of the app. You can get here by pressing the red "Unregister" button. In this state the app is doesn't initiate network traffic, but is it's ready to start registering with the MeetingPoint. To go to this next state requires manual action, you need to click the blue 'Register' button. The app will then try to register at the MeetingPoint.

This state is mostly used for debugging an Access Point. As we'll explain later, normally the App continuously contacts the MeetingPoint. During debugging, it can help to just stop traffic for a moment to understand what is going on.

Contacting state

In this state the app tries to contact it MeetingPoint. For as long as it fails to register, the Wireless Endpoint will remain in this state. The does keep trying once every second. An example of the contacting state is shown below.

In good circumstances, the app moves on the next state (Registered) very quickly. When the App fails to do so, this can be due to following reasons:

• The MeetingPoint isn't reachable. The client device itself might have no network, or the issue can be further in the network.
• No MeetingPoint is running at the contacted to address.
  Not every ByteBlower has the MeetingPoint add-on. You can always ask for a demo at your sales contact or through support.byteblower@excentis.com .

From this state you can go to the Ready stay by pressing the 'Unregister' button. The itself will automatically move to the Registered state as soon it successfully contacts its MeetingPoint,

Registered state

The is the idle state of Wireless Endpoint: it has registered with the MeetingPoint is and is waiting for order to start a test. Like the contacting state, the device will contact the MeetingPoint at regular intervals. This is shown in the little heartbeat.

If this heartbeat fails several times in a row, the device returns to the contacting state.

If the user requests to start a scenario, the device will go to the armed state. In this state the deivce ready to go but waits a small moment to allow other devices (other clients, but also the ByteBlower) to start.

Armed state

The armed state is an intermittent state right before starting the Wireless Endpoint test.

Running state

The running state is where the Wireless Endpoint executes its tests. In this state the Wireless Endpoint doesn't communicate with the MeetingPoint.

At the end of its test, the Wireless Endpoint returns back to the registered state and searches contact again with its MeetingPoint.

Aborting a test early is a manual action. You need to press the cancel button at the bottom of the Wireless Endpoint screen.