Recently, we implemented code for both the bleconfd server (running on the rPi 3 B+), and the Android app client, to set wifi settings via BLE.
The client has asked us to extend the functionality available in the bleconfd server to include modifying .ini files on the rPi using JSON RPC calls over BLE. We are going to target GLib for this functionality.
Read all current keys and values from the rPi via the Android app, displaying them in the Android app
Add a new key and value from the Android app, having it be persistent on the rPi
Edit an existing key / value from the Android app, having it be persistent on the rPi
Delete an existing key / value from the Android app, having it be persistent on the rPi
Add, modify, and delete groups from the ini file, via the Android app
Communication
All communication will be done over BLE, from the Android app to the rPi 3 B+, and vice versa. Keep in mind that we recently tweaked the communication a bit so that there's no more header, and messages are delineated with an ASCII character 30. (https://github.com/jmgasper/bleconfd/issues/7)
Target rPi
We are going to target the rPi 3 B+ specifically. Note that we will not support the B, just the B+. We will target the latest version of Raspbian as the deployment OS on the rPi.
We can target whatever version of GLib comes standard with Raspbian.
The path to the .ini file should be configurable, but having it just default to ./bleconfd.ini is fine.
We will add new code to the bleconfd app to support JSON RPC messages that will allow us to manipulate the key/value pairs and groups.
Target Android
For the Android app, please target Android 8+. The existing app is available in the Git repo, in the AndroidClientApp folder. We will expand on that app for this challenge.
For the Android app, we will add a new option to the UI to allow for modifying the INI file. Please use a standard side menu or tabbed interface, to now have two options:
Wifi Settings
INI file
The UI doesn't have to be fancy, but it should work as expected. The wifi functionality that exists should still remain in the app and work as expected.
The key/value pairs should be:
Retrieved over BLE via JSON RPC and the bleconfd, from the rPi
Displayed in the app, with grouping information displayed, preferably in some sort of table or a UI element that makes sense.
The user should be able to:
Modify / Add / Delete groups
Modify / Add / Delete key/value pairs
All changes should be automatically persisted back to the rPi as the updates happen in the app.
Validation
Because the .ini file modified by GLib should be human-readable, we can validate by:
Change something in the Android app
cat bleconfd.ini to see the change, or something similar, on the rPi
Please ensure your validation document covers this clearly.
Recently, we implemented code for both the bleconfd server (running on the rPi 3 B+), and the Android app client, to set wifi settings via BLE.
The client has asked us to extend the functionality available in the bleconfd server to include modifying .ini files on the rPi using JSON RPC calls over BLE. We are going to target GLib for this functionality.
https://developer.gnome.org/glib/stable/glib-Key-value-file-parser.html
We want to be able to:
Communication
All communication will be done over BLE, from the Android app to the rPi 3 B+, and vice versa. Keep in mind that we recently tweaked the communication a bit so that there's no more header, and messages are delineated with an ASCII character 30. (https://github.com/jmgasper/bleconfd/issues/7)
Target rPi
We are going to target the rPi 3 B+ specifically. Note that we will not support the
B, just theB+. We will target the latest version of Raspbian as the deployment OS on the rPi.We can target whatever version of GLib comes standard with Raspbian.
The path to the .ini file should be configurable, but having it just default to
./bleconfd.iniis fine.We will add new code to the
bleconfdapp to support JSON RPC messages that will allow us to manipulate the key/value pairs and groups.Target Android
For the Android app, please target Android 8+. The existing app is available in the Git repo, in the
AndroidClientAppfolder. We will expand on that app for this challenge.For the Android app, we will add a new option to the UI to allow for modifying the INI file. Please use a standard side menu or tabbed interface, to now have two options:
Wifi SettingsINI fileThe UI doesn't have to be fancy, but it should work as expected. The wifi functionality that exists should still remain in the app and work as expected.
The key/value pairs should be:
The user should be able to:
All changes should be automatically persisted back to the rPi as the updates happen in the app.
Validation
Because the .ini file modified by GLib should be human-readable, we can validate by:
cat bleconfd.inito see the change, or something similar, on the rPiPlease ensure your validation document covers this clearly.