This is the repository for the BrewPi web interface. The web interface will communicate with the Python script, which will in turn talk to the BrewPi Spark
At present, the user has to "know" which sensor they want to use for each function. If they plug all 3 (beer/fridge/ambient) in at once, then they will have to know the address of each sensor in order to correctly distinguish them.
A simple solution is to write documentation to suggest first physically labeling all sensors, and then plugging each sensor in one at a time and refreshing the device list. The new sensor that appears unassigned in the device can then be assigned to the function it was labelled with.
The UI could be developed in various ways improve this:
develop a wizard in the UI that asks the user to plug in each beer/fridge/ambient sensor in turn - the code detects the new sensor that was connected and assigns it to the function.
a proactive UI that reacts to when a new sensor is detected. "A new sensor has been found. What do you want to use this for?" With selection for beer/fridge/ambient function.
A more advanced UI, the sensor appears as a labelled icon on the page in a pool of unassigned devices, and the user can drag it to the relevant fridge/beer/ambient part in a systematic view of the brewpi camber/beer setup.
At present, the user has to "know" which sensor they want to use for each function. If they plug all 3 (beer/fridge/ambient) in at once, then they will have to know the address of each sensor in order to correctly distinguish them.
A simple solution is to write documentation to suggest first physically labeling all sensors, and then plugging each sensor in one at a time and refreshing the device list. The new sensor that appears unassigned in the device can then be assigned to the function it was labelled with.
The UI could be developed in various ways improve this: