Over the weekend I had an opportunity (read: snowed in) to put together a proof-of-concept video as a response to an idea a friend posited: a recent released-to-market toilet with LED night lights should have included a proximity sensor and BTLE.
I first thought “okay - let’s make that”, but then started to think about the what and why behind the concept. What would be the use of having wireless communications on your toilet? What would be useful to the end-user? (I should state that my friend and I have explored the concept of “too much information” with sensor-laden and projection-mapped Port-o-Potties in large venues before, so already have some background in this area )
In the end I came up with a thought experiment: what if even the most basic of tasks were able to present the cost of resources and wasted time to the user? Would it change their habits? Make them “go” quicker? Would it matter?
I used a spark core w/ battery and the pressure sensor and photoresistor that came in the Spark Maker Kit, attaching them to the toilet in our spare room, with the spark hidden on the floor behind. I built a simple web page using jquery to repeatedly call the values of each sensor separately every 3 seconds; if the light was on, start one timer, if the pressure sensor was pressed, start a different timer. Each timer updated a per-second value based on the real cost of using the five lights in the bathroom (times a future-scenario markup) and the current minimum wage in my state (again times a future markup).
I also played with the idea of a future where bathrooms were the only private space one would have, and that using one would have a direct financial cost. This is why the web page shows a welcome message to an identified private space, and showing the cost the user could be charged.
There was a bit of choreography needed between me and my wife for me to be able to film my iPhone using her iPhone, get in and out of the room, turn on and off the lights, etc. Was a good was to spend a Sunday.
I love asking questions and being able to make real, working examples to show possible answers. The spark is proving to be very useful for rapid prototypes in areas that may not have normal power or networking abilities.
Here’s the video (nothing gross):