Embedded Files
Bron : http://www.openhab.org/features.html
Waarom mijn keuze valt op openHAB, en de opbouw wordt ook bekomen van de verschillende soorten protocol communicatie mdv bindings, gebruik makend van libraries.
https://github.com/openhab/openhab/wiki/
Our Vision and Philosophy
Our Vision and Philosophy
There are many home automation solutions and Internet-of-Things (IoT) gadgets on the market, which are all useful on their own.
They come with their own way on how to setup and configure devices and are perfect for their intended use cases.
The problem with all of these systems and devices is that these use cases are defined by the manufacturer - but as a user, you will quickly come up with wishes that are not supported out of the box or which require interaction between the different systems.
openHAB fills this gap: It puts the user in the focus and allows him to do what he wants to do. It thus serves as an integration point for all your home automation needs and lets systems talk to each other across any vendor or protocol boundaries.
From our point of view, a commercial product can never stay up to date with all interesting things that can be integrated. So the only way to be sure that you do not bet on a dead horse is by using an open source solution that is maintained by a big community and which does not depend on the fate of a single company.
openHAB is hence the best choice for a future-proof Smart Home setup.
Considering the user perspective also means caring for data privacy. With openHAB, all data (like sensor data or actuator commands) belongs to the user and it is up to him to decide, what data should potentially leave his house and where it is sent.
Furthermore, there is no remote access possible, if it is not desired - everything works nicely within the intranet and does not even require an Internet connection. We therefore also like to call it the "Intranet of Things".
Zie bijlage
Google Sites
Report abuse