...domesticate the Internet of Things.
See ioBroker wiki for more information
ioBroker is an integration platform for the Internet of Things, focused on Building Automation, Smart Metering, Ambient Assisted Living, Process Automation, Visualization and Data Logging. It aims to be a possible replacement for software like f.e. fhem, OpenHAB or the thing system by the end of 2014. ioBroker will be the successor of CCU.IO, a project quite popular in the german HomeMatic community.
ioBroker is not just an application, it's more of a a concept, a database schema, and offers a very easy way for systems to interoperate. ioBroker defines some common rules for a pair of databases used to exchange data and publish events between different systems.
ioBroker uses Redis and CouchDB. Redis is an in-memory key-value data store and also a message broker with publish/subscribe pattern. It's used to maintain and publish all states of connected systems. CouchDB is used to store rarely changing and larger data, like metadata of systems and things, configurations or any additional files.
Systems are attached to ioBrokers databases via so called adapters, technically processes running anywhere in the network and connecting all kinds of systems to ioBrokers databases. A connection to ioBrokers databases can be implemented in nearly any programming language on nearly any platform and an adapter can run on any host that is able to reach the databases via ip networking.
|admin||The admin user interface. Comfortably install and update adapters, manage adapter instance configuration and more||0.6.5|
|history||Manage state history in a two-staged process. A configurable amount of datapoints is kept in Redis for high-speed access, long-time archiving is written to CouchDB with a configurable retention-time. Configuration can be done individually for each state.||beta|
|web||Express based webserver||1.0.2|
|virtual||Map states into virtual namespaces and apply basic rules on the mappings (average, sum, min, max, offset, factor, toggle, timeout, history pattern matching and more).||planned|
|scenes||Create and sequence scenes||0.2.1|
|trigger||Trigger simple actions, scenes or scripts by state change pattern recognition ("reverse-scenes")||planned|
|python||Python script engine||planned 2016|
|php||PHP script engine||planned 2016|
|mobile||jQuery Mobile based User Interface (yahui successor)||alpha|
|vis||Template based HTML5 User Interface (Successor of DashUI - the successful UI-Builder-Framework of CCU.IO. View DashUI Demos||0.7.4|
|cul||Different RF Devices (FS20, MAX!, FHT, HMS, ...) via CUL/COC and culfw||alpha|
|artnet||Control DMX512 devices via Art-Net (Stage-Lighting: powerful LED RGB Lamps and effects, powerful Dimmers and Switches, moving light effects, fog machines and much more.)||alpha|
|digital||Control digitalSTROM devices||planned 2016|
|EnOcean||Control EnOcean devices via EnOcean Pi||planned 2016|
|hm-rpc||Homematic XML-RPC. Control Homematic Devices via Bidcos-Interfaces (unlimited number of CCUs, RF-LAN-Adapters with rfd and Homegear)||0.5.2|
|hm-rega||Homematic CCU1 or CCU2 (Logic Layer "ReGaHSS", needed in addition to )||0.2.2|
|hue||Philips Hue LED bulbs and stripes, Smartlink capable LivingColors and LivingWhites||0.4.4|
|homeeasy||Home easy||planned 2016|
|maxcube||MAX! via MAX! Cube||planned ?|
|irtrans||IRTrans Send and receive infrared commands||planned ?|
|lirc||LIRC Send and receive infrared commands||planned 2016|
|onkyo||Onkyo AV Receiver||0.1.9|
|...||...several TVs and AV Receivers (Pioneer, Onkyo, Yamaha, Samsung, ...)||planned|
|imap||Control ioBroker with emails in clear text over imap protocoll||planned ?|
|nma||Notify My Android||planned ?|
|pushover||Send Pushover notifications||0.1.1|
|pushbullet||Send Pushbullet notifications||0.0.11|
|ping||Use system "ping" command to poll configured IP addresses.||0.1.4|
|rest||REST compliant API||1.0.0|
|telnet||Telnet Client. Connect to a server and send and receive data||planned 2016|
|b-control-em||B-Control Energy Manager||beta|
|graphite||Manage huge amounts of history data and draw charts with Graphite||beta|
|nagios||Offer selected objects as Nagios/Icinga checks with optional performance data, include nagios hosts as ioBroker objects||planned 2015|
|dwd||fetch weather warnings from DWD (germany only)||beta|
|yr||fetch 48h weather forecasts from yr.no (worldwide)||beta|
|gpio||Use GPIOs, SPI, I2C and 1-Wire on Raspberry Pi, Banana Pi, Cubietruck, ...||planned 2016|
|owfs||1-Wire Devices via (http://owfs.org/)||0.0.2|
|piface||Use PiFace||planned ?|
|tessel||Control Tessel Modules||planned ?|
|geofency||Receive Geofency webhooks||planned 2016|
|ical||Fetch iCal/VCALENDAR events||1.1.1|
|noble||Bluetooth Low Energy devices via noble (Parrot Flower Power, ...)||planned|
|text-commands||Control ioBroker with commands in clear text, like "Switch on the light in the living room". Used by other adapters, like imap or voice control||planned|
|text2speech||Text to speech adapter||0.3.13|
ioBroker is designed to be accessed by trusted adapters inside trusted networks. This means that usually it is not a good idea to expose the ioBroker databases, adapters or any smarthome devices directly to the internet or, in general, to an environment where untrusted clients can directly access these network services. Adapters that offer services supposed to be exposed to the internet should be handled with care, for example with additional security measures like VPN, VLAN and reverse proxys.
Operating System and Hardware
ioBroker.nodejs should run on any hardware and os that runs Node.js (ARM, x86, Windows, Linux, OSX). Binary builds for CouchDB and Redis are also available for the ARM and x86 under Windows, Linux and OSX. ioBroker spawns a new Node.js-Process for every adapter instance, so RAM becomes is a limiting factor. A single adapters memory fingerprint is roundabout 10-60MB. Since CouchDB can create quite a lot of load a dual core system is beneficial.
Installation and first steps
- automated installation packages for windows and linux coming soon
- ioBroker.nodejs manual install
- get help in the ioBroker Forums (english, german and russian language)
Docs for (adapter-)developers
- Core Concepts and Database Schema
- ioBroker styleguides
- ioBroker.nodejs Changelog
- ioBroker.nodejs Roadmap
- Direct access to all ioBroker Objects is possible via the CouchDB-Webinterface "Futon":
- Use the view selector on the upper right in CouchDB to browse ioBroker objects
- you can use
redis_cliand issue the command
PSUBSCRIBE *to watch all stateChange Events on the Console
The MIT License (MIT)
Copyright (c) 2014-2016 bluefox
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.