Overview
Wi-Fi Access Point
Upon booting up, the BrioSens will start Wi-Fi access point and provide a configuration dashboard.
The access point will have the name (SSID) corresponding to the device serial number. This serial number can be found on a sticker under the device.
Credentials
The credentials for the platform can be found here
Configuration Dashboard
The configuration dashboard is accessible via http://192.168.43.1
Configurations are saved under the file /mnt/storage/bsns.conf
To restore default settings, delete the configuration file and restart the dashboard service using systemctl restart dashboard
WI-FI Settings
Connect the BrioSens to a nearby Wi-Fi by choosing it from the scroll-down list and by providing its associated password. The list of available access points is refreshed every 10 seconds. If a hidden access point is used, the SSID must be manually entered in the corresponding field.
Mobile Settings
For cellular connectivity, it may be required to provide an access point name (APN) and a host health check address. The health check address is used to send a ping which ensures that the device is still connected.
Cloud Settings
In order to connect the BrioSens with a MQTT broker, a broker address with a port, a username and a password are required. To enable communication with www.briosphere.io, please refer to the Briosphere Cloud section.
NAT Settings
The BrioSens can share its Wi-Fi and cellular connection via a Wi-Fi hotspot.
The connection can be shared by translating the network source address for the chosen interface (SNAT). The following iptables rule is added when an interface is selected:
iptables -t nat -A POSTROUTING -o <chosen interface> -j MASQUERADE
Cellular Connectivity
By default the BrioSens Gateway has a systemd service called bitpipe.service
that will handle the cellular connection according to the configured APN. This APN can be set through the Wi-Fi dashboard or via the file /mnt/storage/apn.config
.
For additional details, refer to the Cellular Conectivity section under peripherals
Connecting to the BrioSens
Via SSH
The BrioSens offers an SSH terminal through its WiFi access point using port 22. Inbound connections from all interfaces are blocked (except the Wi-Fi access point as mentioned above).
Via the serial console
Instead of using the SSH terminal, a user can also connect via the Serial Console
BLink (REST API)
BLink is a hardware abstraction tool that can be used to simplify the development of applications on the BrioSens. This tool offers a REST API that is only accessible (by default) either via the Wi-Fi access point or locally from the device itself on the port 16601
You may use the programming language of your choice to interact with the REST API.
Refer to the API definition for more info.
Usage examples
Reading the digital input #1 from a device connected to the Wi-Fi access point, using cURL
curl -G "192.168.43.1:16601/gpio?name=DIN1"
=> {"value":true}
Reading the analog analog input #1, locally, on the BrioSens
curl -G "127.0.0.1:16601/analog?name=AIO1"
=> {"value":5}
Visiting the url in a browser (useful during development) http://192.168.43.1:16601/temperature
Overlay File System
BrioSens mounts the root filesystem /
using OverlayFS. This type of filesystem has the advantage of being very robust and tolerant to power failures. The downfall being that changes to the filesystem are not persistent through power cycles. Any power cycle will reset the filesystem to its original state.
In order to save files in a persistent manner, files must be written to /mnt/storage
.
If files in the file root filesystem must be edited, refer to filesystem edit mode.