Difference between revisions of "Domoverse platform"
From Tmplab
m (→Resources) |
m (→Resources) |
||
| Line 30: | Line 30: | ||
= Resources = | = Resources = | ||
| − | http://del.icio.us/fthiery/domoverse | + | * http://del.icio.us/fthiery/domoverse |
| − | http://community.webbricksystems.com/files/folders/manuals/entry15.aspx | + | * [http://community.webbricksystems.com/files/folders/manuals/entry15.aspx WebBrickSystems API example] |
| + | * [http://www.automatedhome.co.uk/New-Products/LinuxMCE-710-An-Overview.html LinuxMCE] supports various home automation protocols | ||
Revision as of 20:24, 14 June 2008
Description
This page is intended as placeholder for preparing the Domoverse platform project.
It is a project whose aim is to explore the HMI capabilities of Metaverse-related technologies (OpenSim/OpenLife/OpenCroquet/Solipsis) in a domotics context (X10/Z-Wave, Gumstix, ZigBee...), as home server control and root web house.
Project organization
- State of the art: metaverse platforms and domotics management systems
- Evaluation of metaverse and domotics management systems candidates
- Implementation of a tmplab server for experimentation
- 3D Replication of the lab and it's electronic devices
- Implementation of XMLRPC-like server for services exposition (X10, ...)
- Linking virtual objects' actions to XMLRPC calls
- Gluing all together
Components
- XMLRPC server:
- keeps a list of all detected devices and features
- exposes their functionality trough the remote procedure call interface
- hosts a 3D modelization of controlled items
- device_connectors: protocol-specific plugins
- X10 devices exploitation
- ZigBee
- Z-Wave
- metaverse_connectors: metaverse-specific components (speaks with metaverse server)
- metaverse objects and scripting codebases and snippets, domoverse-related templates and coding resources
Resources
- http://del.icio.us/fthiery/domoverse
- WebBrickSystems API example
- LinuxMCE supports various home automation protocols
