Difference between revisions of "XMPPHWFS"
(→Device description) |
|||
| Line 13: | Line 13: | ||
fi | fi | ||
| − | the above example is crappy, because it would be better done with the event-driven interface that must be included. | + | the above example is crappy, because it would be better done with the event-driven interface that must be included. I propose sending all events to a bot, maybe ''event-master'' by default. This bot should then do what is needed with the event. For large systems, devices can communicate with specialized bots. |
| + | * The Fuse inteface should also be implemented as a bot. Simply specify where to mount the filesystem, connect your bot, you're done. No need to have a modified jabberd. | ||
| + | * GUI can also be implementd as a bot. Simple and clean. | ||
| + | * Debugging new hardware is simply done through communication with a human client. | ||
XMPPHWFS is meant to replace [http://david.lutolf.net/dt/locmon locmon], which in my opinion was a good idea but is too buggy and impractical. from a recent copy of ''20 minutes'', it seems the industry is also heading towards something alike, only for home robots and social networking. WTF, tell me why your vacuum cleaner should tell all your facebook friends there's a plant in its way. | XMPPHWFS is meant to replace [http://david.lutolf.net/dt/locmon locmon], which in my opinion was a good idea but is too buggy and impractical. from a recent copy of ''20 minutes'', it seems the industry is also heading towards something alike, only for home robots and social networking. WTF, tell me why your vacuum cleaner should tell all your facebook friends there's a plant in its way. | ||
it was suggested to use IRC for communication, but device description is be greatly improved through use of XML and XMPP is just that. | it was suggested to use IRC for communication, but device description is be greatly improved through use of XML and XMPP is just that. | ||
| + | |||
| + | == Device description == | ||
| + | Since XMPPWHFS is aimed towards real-world I/Os, for each variable we need info such as: | ||
| + | * variable name | ||
| + | * ro/rw flag | ||
| + | * unit (meters, seconds, °C..) | ||
| + | * update delay in seconds | ||
| + | * last update timestamp | ||
| + | * variable type and allowed values (int, float, enum..) | ||
| + | * I/O type (door, temperature, humidity...) | ||
| + | * location (GPS coordinates and/or description) | ||
| + | * text/blob, possibly containing icon | ||
== Hardware == | == Hardware == | ||
Revision as of 11:24, 11 January 2012
Under the barbarian name of XMPPHWFS stands the following idea:
hardware IOs made available on a fuse filesystem through xml messaging protocol
and imagine doing stuff like
garage_temp = myHome/garage/temperature garage_heat = myHome/heating/pump1 if (( $garage_temp < 2 )) then echo 1 > $garage_heat fi
the above example is crappy, because it would be better done with the event-driven interface that must be included. I propose sending all events to a bot, maybe event-master by default. This bot should then do what is needed with the event. For large systems, devices can communicate with specialized bots.
- The Fuse inteface should also be implemented as a bot. Simply specify where to mount the filesystem, connect your bot, you're done. No need to have a modified jabberd.
- GUI can also be implementd as a bot. Simple and clean.
- Debugging new hardware is simply done through communication with a human client.
XMPPHWFS is meant to replace locmon, which in my opinion was a good idea but is too buggy and impractical. from a recent copy of 20 minutes, it seems the industry is also heading towards something alike, only for home robots and social networking. WTF, tell me why your vacuum cleaner should tell all your facebook friends there's a plant in its way.
it was suggested to use IRC for communication, but device description is be greatly improved through use of XML and XMPP is just that.
Device description
Since XMPPWHFS is aimed towards real-world I/Os, for each variable we need info such as:
- variable name
- ro/rw flag
- unit (meters, seconds, °C..)
- update delay in seconds
- last update timestamp
- variable type and allowed values (int, float, enum..)
- I/O type (door, temperature, humidity...)
- location (GPS coordinates and/or description)
- text/blob, possibly containing icon
Hardware
to make XMPPHWFS as useful as possible, some hardware should be designed and the necessary firmware written
Software extensions
- communicate with Asterisk to send voice commands
- have some fun with XMMS2 / MPD
