[[Category:Ongoing_ProjectsClosed_Projects]]
Under the barbarian name of XMPPHWFS stands the following idea:
'''hardware IOs made available ''' (on a fuse filesystem ) '''through xml xmpp messaging protocol'''. The latest idea is to use fuse only as on option, so the name will definitely change. ''locmon2'' seems like a good candidate to me.
== Description ==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 imagine doing stuff likeimpractical. 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. Any suggestions are welcome, coding has not really started yet anyway.
garage_temp = myHome/garage/temperature garage_heat = myHome/heating/pump1 if (( $garage_temp < 2 )) then echo 1 > $garage_heat fi[[Image:Xmpphwfs arch.svg|thumb|XMPPHWFS architecture]]
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.
* ''corecode'' suggest to use the [http://xmpp.org/extensions/xep-0060.html PubSub] [http://jabber.org/protocols/pubsub mechanism] for event notification, I think he's bloody right on this. Some bot can catch these events and update the cache DB as well.
* GUI can be implemented as a bot (ctrl_bot?). Simple and clean. Use of a cache DB is a good idea to minimize traffic and load on HALs. For the interface, I'd suggest HTML with Ajax with templates and possibility to include content like webcams and the such. Help is needed here.
* some other bot (log_bot?) can generate [http://oss.oetiker.ch/mrtg/MRTG MRTG graphs] and update the cache database on the same occasion. MRTG config can of course be generated automatically and graphs included in the GUI.
* The Fuse inteface, if needed, 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 and the resulting filesystem can be mounted on any host. Any interface of this type (read: local interface, as opposed to html-based) should not talk directly to HALs, but communicate with a bot (ctrl_bot?) that has access to the cache database.
* in case you ''really'' want to notify your friends through twitter, facebook or whatever else, create a bot and make it subscribe to particular events
[[Image:Xmpphwfs archit was suggested to use IRC for communication, but device description is be greatly improved through use of XML and XMPP is just that. AFAIK, IRC does not have a PubSub mechanism.svg|thumb|XMPPHWFS architecture]]
XMPPHWFS is meant to replace [http://david.lutolf.net/dt/locmon locmon], which in my opinion was I've been dreaming of a good idea but is too buggy 3D GUI where you can walk around and impractical. from a recent copy of ''20 minutes'', it seems interract with 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 hardware in a plant in its waynatural fashion.Volunteers?
it was suggested to use IRC for communication, but device === Device description ===Since XMPPWHFS is be greatly improved through use aimed towards real-world I/Os, we need lots of XML useful info that must be made available by each HAL==== About the HAL ====* name* description* location (GPS coordinates and XMPP is /or description)* icon? I think we don't really care about the HAL itself, it's just that.a way to conveniently group I/Os
== Device description ==Since XMPPWHFS is aimed towards real-world I/Os, for About devices on each variable we need info such as:HAL ====
* variable name
* variable type and allowed values (int, float, enum..)
* I/O type (lock, temperature, humidity...). a more or less standard list must be written
* ro/rw flag
* unit (meters, seconds, °C..)
* update delay in seconds
* last update timestamp
* variable type and allowed values (int, float, enum..)warn/alarm thresholds for event notification* icon? maybe not necessary. one can be chosen from the I/O name or type (door, temperature, humidity...)* location (GPS coordinates and/or description)* text/blob, possibly containing icon* min/max trigger values
==== Sample session ====;To HAL:Here, it should be a good thing This is to have flags such as ''update_all_values''get the simple, ''used_cached_values''human-readable output<pre>help</pre>;From HAL:
<pre>
<describe />rfid_reader: last RFID tag readdoor_lock: status of door locklock_delay: how long should the door stay opentemperature: tell me how cold it is outside
</pre>
;To HAL:Here, it should be a good thing to have flags such as ''force_update'' if bot supports it.<pre>describe</pre>;From HAL:I suppose it would be nice to include output from the ''help'' command above. XML validity needs to be checked anyway. Too many line breaks are added on purpose for readability on the wiki.
<pre>
<hal name='HalName' target='event_main' backup_target='event_backup'>
<device
name='rfid_reader'
attrs='ro' type='rfid'
last_update_timestamp=1326310608
value='00EFC0B554' />
name='door_lock'
attrs='rw'
type='enum' value='closed'>
<value>open</value>
<valueselected="selected">closed</value>
<value>locked</value>
<value>unlocked</value>
</hal>
</pre>
;To HAL:
<pre><set device='door_lock' value='open' />temperature</pre>
;From HAL:
<pre><hal name='HalName'> <devices> <device name='door_locktemperature' value='open' 23.5 /> </devicespre></hal></pre>
;To HAL:
<pre><get device='temperature' />door_lock unlocked</pre>
;From HAL:
<pre><hal device name='HalNamedoor_lock'value='unlocked' /></pre> ;To HAL:<devicespre>door_lock foobar</pre>;From HAL: format needs to be thought a little better here.. <pre><device name='temperaturedoor_lock' value=23.5 'open' /> error: new value out of range</devicesdevice></hal></pre>
Discussion must be done around where the values should go in the XML, and if the whole device XML string should be sent back when requesting a single value. I say it should, as it simplifies the code (and let's not care too much about the overhead) === Events ===When an event is detected by a HAL (threshold exceeded for example), the HAL sends the info with the Pub/Sub mechanism. other bots can subscribe to events, and then decide what to do. we'll get something like: (suggestions welcome!)<pre><device name='temperature' value=11.8>warn_low_value</device></pre> == Obstacle ==* lack of expertise and motivation to implement a client in a µC* weak programming skills == Components ===== Software ===Some things can can be handy:* [http://thp.io/2007/python-jabberbot/ JabberBot] in python === Hardware ===
to make XMPPHWFS as useful as possible, some hardware should be designed and the necessary firmware written
* [[SuperCaptor]]
* [[GPIO relay board]]
=== Software extensions ===
* communicate with Asterisk to send voice commands
* have some fun with XMMS2 / MPD
== Schedule ==
=== as soon as possible ===
* design a smart way to handle events (scripting/rules interface)
* implement test HAL client/bot with Pub/Sub
* implement event_master with Pub/Sub
* implement ctrl_bot
=== when the above is done... ===
* implement web interface on ctrl_bot
* implement fs_bot
* implement HAL bot on µC ([[SuperCaptor]]!!)
== Participant ==
* [[User:Petaflot]]