When power is applied to the IoTBox, it will try to connect to the stored WiFi access point and will show the IP address on the screen if successful. The screen will show an error message if it cannot connect.
The IoTBox uses two WiFi modes simultaneously:
- Client Mode = It will connect to an Access Point.
- Access Point Mode = It will behave as an Access Point.
To configure the IoTBox, look for an open network with the same ID as shown on the OLED display, it will be similar to “iotbox00fcf9ab”.
The first thing to do is to upgrade to the latest version of the IoTBox firmware. For this, you will need to be connected to an external Access Point chosen on the WiFi settings page and then select OTA Upgrade. The IoTBox will download the updated firmware and then reboot into the new version.
The ESP8266 on the IoTBox is configured as two slots. The OTA firmware is downloaded and stored in the other slot. If it has downloaded correctly, it will reboot into the other slot. You may switch back to the old versiion by using the Switch ROM menu option.
If you have configured something that is causing an issue with the IoTBox, you can reset it using the button (wired to GPIO0). The button on the IoTBox has three functions:
- If the button is held down while powering on, you can update the firmware on the chip with a programmer. This is only required when putting the initial firmware on the chip.
- If the button is pressed for more than 0.5 seconds and less than 10 seconds (2 seconds is ideal), a message is sent to the button MQTT topic.
- If the button is pressed for more than 10 seconds, the settings are cleared to the default values. You will need to set the WiFi and MQTT parameters again.
IoTBox has an MQTT v3.1 client built into the firmware and is the main way of communicating to other systems. When MQTT is enabled, it will try to connect every 10 seconds and when successful, it will post “online’ to the LWT topic.
The following topics are supported:
Note: MQTT can use wildcards, such as ‘+’. This means that a subscription to ‘+/out/led/1’ will pick up data for ‘iotbox00112233/out/led/1’ and ‘iotbox56229922/out/led/1’. This is useful when sending the same information to many devices.
LED: For the example shown above, the IoTBox is listening on:
A payload of ‘0’ or ‘1’ to these topics switches the LED colour (red, green or blue) off or on. This will likely change in the future to support PWM and a single Topic.
DISPLAY: For the example shown above, the IoTBox is listening on:
A payload of upto 20 characters will be displayed on lines 3-8 on the OLED screen. Useful for notifications and information.
BUTTON: A button press creates a payload of ‘1’ on the Topic.
TEMPERATURE: Readings from the sensor (DS18B20 or DHT22) are sent every 10 seconds to this topic.
HUMIDITY: Readings from a DHT22 (if connected) are sent every 10 seconds).
LAST WILL & TESTAMENT: When the IoTBox is connected to MQTT, a payload of ‘online’ is sent to this Topic. The MQTT server will send ‘offline’ if it does not receive a heartbeat from IoTBox.
The best way of exploring how IoTBox uses these Topics is to use the MQTT-SPY application found at MQTT-SPY Homepage.