Slashdot Mirror
Japanese Firms Create Home (Appliance) Network
JOstrow writes "The Japanese companies Toshiba, Mitsubishi, Sharp, and Sanyo are teaming up to create a standard for home appliances communicating over a network. Usage examples cited are ovens that download recipes and heating systems that can be adjusted remotely with a cell phone. The first products adhering to the standard, called iReady, are expected to be available by next year. The iReady adapter will be ready for use '...not only with commercialized Bluetooth and low powered wireless appliances but also wireless LAN and future transmission media.'"
Seriously though, perhaps we could use peer-to-peer networks to share recipes, with a rating system kind of like what Shareaza uses. I have a cookie recipe that I can share... It would be kind of interesting to join a network of like-minded recipe people and have recipes downloaded each day.
I have difficulty imagining the usefulness of this, but I'm really glad they're working together to develop a common standard instead of each company doing their own thing. I suspect someone will find something really cool to do with this technology that nobody's thought of yet, now that the framework exists.
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
I think some form of A/V network would be more useful than linking appliances. Why can't I just link my TV, VCR, Digital Tuner, DVD, Receiver, etc with a single cable and let them figure themselves out?
:(
Play on DVD tunes the TV to the right input, sets the receiver surround mode, knows to control the receiver's volume instead of TV's, etc. Watching TV, press record and the VCR knows what to do. Let me walk over to the kitchen and continue watching my DVD there. Etc.
A universal remote doesn't really make things that much simpler (constant mode switching, two different volume modes depending on where audio is routed, needing to know what plugs into what, etc). The alternative is an extremely complex/expensive crestron-type system.
Of course, under the DMCA/etc, you'll probably see this as a "what we're allowing you to do" connection instead.
I use Macs to up my productivity, so up yours Microsoft!
The future, as supplied by mega-corporations: More and more of what you need less and less.
Do you really want your toaster to be twice as expensive, half as reliable, licenced instead of owned, and subject to planned obsolescence?
There already is a whole raft of standards for home interconnection, and then home to outside world.
How does this new standard add to that?
Look at OSGi, uPnP and LonWorks just to show a few of them
Most new "modern" appliances with features that are anything near digital are already too difficult for the run-of-the-mill house caretaker, whether that be a woman or a man.
People want something simple that WORKS....I doubt there will be a widespread acceptance of this until the technology generation, the kids of the 90s, grow old enough to have to use household appliances(and take care of a house/apartment), which won't be for another 10 to 15 years.
Until then, therefore, I predict these things won't catch on too well. But you can never really predict consumer acceptance of a radical new idea, so I guess we'll have to wait and see.
One of the best things that this technology could do is
to standardize on how devices talk to their control panels.
This implies that the control panel is separate and distinct
from the device it controls. A washing machine's panel
for example isn't necessarily hard-coded and hard-wired
to the washer itself. Now, it would be possible for grandma,
who can hardly see, to have just three big buttons for the
washer, with loud audio feedback. But the slashgeek could
have the mega-LCARS interface that sets the washer based
on the rfid tags on the clothes that are tossed in, along with
woolen-color vs. cotton-whites incompatibility warnings.
Big, simple interfaces for seniors is overlooked by most
device makers these days. Lots of tiny, low contrast buttons
with nested menu structures only confuse most non-geeks.
Downside of this will be that you'll need a monthly subscription
for -everything- and selecting interfaces will also be an additional
charge, like cellphone ring tones.
What I gained from connecting these systems under one roof was
The biggest difficulty in setting up the system was not technical, but administrative. Although I had to write a device driver and some custom software, these proved to be relatively stable once debugged. The problems were in correctly specifying our living requirements, translating them into specifications, and testing the result. The first friends to visit us after I installed the system rang the doorbell and were greeted by the answering machine message (oops!) Now the system is very stable, but I would never think of modifying its configuration less than a month before leaving for a vacation.
Diomidis Spinellis - Code Reading: The Open Source Perspective
#include "/dev/tty"
A time server would be a really handy thing to have in a home network, imagine all the clocks in the appliances having the same, correct time all the time.
Sure beats the blinking 12:00 syndrome.
Everytime someone gets excited about a "home appliance network" (which seems to be every year, like clockwork, for the past 20 years or so), I ask myself: "Why? What does my toaster have to say to my lamp? What does my microwave have to say to my toaster?"
Other than a very few uses (your PC talking to your A/V components, for example) this is a technology in search of a problem.
Do that many people really spend so much time using their appliances that they need to have their own network? And, of course, this is just one more thing to break - maybe it's a conspiracy by appliance manufacturers to reduce the reliability and "it-just-always-works" nature of most appliances.