| actually what george is getting at makes a lot of sense, and i would think would be easier to support and develop for...
instead of having a cable (or bluetooth) and fat client.. do it like many network appliances do.
the controller has a mini menu to change the IP (or leave it on DHCP by default) then have and RJ-45 ethernet port and/or wireless
it attaches to the network and then its accessible via a webpage.
using a static IP or a zero config protocol like bonjour would make this easier
but then the webpage has all of the programing settings and then also has output data. this way people could publish this existing web page to the internet if they want to (something MANY people go to great lengths to do).. nothing extra since its already there.. if the web page is built using back-end XML those files could then be downloaded VIA http or ftp for all the ubergeeks that want to play with it
but it seems like with a wireless/wires enabled network webserver you have everything we have been looking for. accessibility, no fat client, internet publishing, graphing, platform independent, upgradability (by uploading firmware files). none of this is new, this is how any network appliance works today..
the other nice thing is it should be a lot cheaper for you to add a wireless card than a bluetooth adapter, and more people are familiar with this.. not to mention faster transfer speeds.
i know i dont see the "big picture" but i dont see a downside (other than its a major direction change...lol)
__________________ Show people you appreciate there advice, click the  icon under there name and give them Reputation points | 
