Diagnostics

This page groups the first checks to make when a Bee Thing board does not behave as expected.

Check Configuration Mode

When the board is in configuration mode:

bee-config show

The output includes the reason why configuration mode was entered, for example:

config.mode.reason=config button wakeup

If the command times out, the board may not be in configuration mode. It may have completed its normal cycle and gone back to sleep.

LED

State	Meaning
Off	The board is sleeping, or no action is in progress.
Solid blue	Configuration mode is active.
Blue-green / cyan with a breathing pattern	WiFi configuration portal is active.
Yellow / orange	Configuration mode is active, but configuration is missing or invalid.
Short green	Measurement sent successfully.
Short red	Startup, sensor, transport, or command error.
Short white	Command received in configuration mode.

Colors can depend on the board and LED used, but firmware states remain the same.

Common Issues

Symptom	Check
Board stays in configuration mode	Missing or invalid configuration, missing token, invalid URL, button held down.
bee-config does not answer	Board sleeping, wrong serial port, firmware not started, charge-only USB cable.
The BeeThing-Config network does not appear	Board not in configuration mode, button not held long enough, board too far from the phone or computer.
HX711 error	DT / SCK wiring, module power, load cell wiring, HX711 not ready.
WiFi upload impossible	SSID, password, WiFi range, ingestion URL, token.
4G upload impossible	SIM, PIN, antenna, coverage, APN, configuration URL, modem power.
Incoherent measurement	Calibration, tare, mechanical build, test weight.

Check Messages in Bee Thing

Recently received messages are visible in the application, in a scale’s activity. They help distinguish:

• a board that sends nothing;
• a received but rejected request;
• an accepted measurement not linked to an active colony.

See also: HTTP ingestion.