OPENHAB open source project Sample Clauses

OPENHAB open source project. Vision The open source project OpenHAB [18] wants to allow interoperability between all the existing protocols in smart home/home automation. OpenHAB provides a gateway which is based on OSGi. Approach The OpenHAB project focuses on home automation protocols and interoperability between them. Some more elaborate scenarios are provided. OpenHAB is an architecture based on OSGi where each home automation protocols are integrated by bundles. Inside the architecture an asynchronous event bus allows to share events between bundles. Figure 8: OpenHAB architecture [18] Relevance to PRECIOUS OpenHAB is a popular solution (an important open source community) to manage interoperability inside a house. It is only focused on the interoperability of home automation devices with a separation between home automation protocols and high-levels protocol. However, the interoperability is managed in a central piece of hardware running OSGi. In that case, all the functionalities of a home automation system will be centralized in one gateway. Criteria Description Architecture style OSGi-based Interoperability OSGi-based + OpenHAB event bus Seamless communication OSGi-based Motivational system x Communication protocol Home automation protocols (e.g. KNX) and high-level protocols (e.g. MQTT) Multimodal user interface Web UI Test in lab/Field test x
AutoNDA by SimpleDocs

Related to OPENHAB open source project

  • Open Source 15.1 All software created for the Buyer must be suitable for publication as open source, unless otherwise agreed by the Buyer.

  • Third Party Software/Open Source Nothing in this Agreement shall restrict, limit or otherwise affect any rights or obligations You may have, or conditions to which You may be subject, under any applicable open source licenses to any open source code contained in the Software. The Software may include or be bundled with other software programs licensed under different terms and/or licensed by a licensor other than Licensor. Use of any software programs accompanied by a separate license agreement is governed by that separate license agreement. Any third party software that may be provided with the Software is included for use at Your option.

  • OPEN SOURCE COMPONENTS The DS Offerings may include open source components. Whenever notices (such as acknowledgment, copies of licenses or attribution notice) are required by the original licensor, such notices are included in the Documentation of the DS Offerings. Moreover, some open source components may not be distributed and licensed under the terms of the Agreement but under the terms of their original licenses as set forth in the Documentation of the DS Offerings themselves. Source code for open source software components is available upon request. Except for components mentioned in the section EXCLUSIONS below, the warranty and indemnification provided by DS under the Agreement apply to all open source software components and shall be provided by DS and not by the original licensor, but only for the use of the DS Offerings that is in compliance with the terms of the Agreement, and in conjunction with the DS Offerings. The original licensors of said open source software components provide them on an “as is” basis and without any liability whatsoever to Customer.

  • Open Source Software The Software product may include certain open source components that are subject to open source licenses (“Open Source Software”), in which case, the embedded Open Source Software is owned by a third party. The Open Source Software is not subject to the terms and conditions of this XXXX. Instead, each item of Open Source Software is licensed under its applicable license terms which accompanies such Open Source Software. Nothing in this XXXX limits your rights under, nor grants you rights that supersede, the terms and conditions of any applicable license terms for the Open Source Software. Any fees charged by GC in connection with the SOFTWARE, do not apply to the Open Source Software for which fees may not be charged under the applicable license terms. The terms and conditions of the applicable license for the Open Source Software are available on the LICENSE.txt file, which is provided with the SOFTWARE.

  • Unbundled Sub-Loop Concentration System (USLC 2.9.1 Where facilities permit and where necessary to comply with an effective Commission order, BellSouth will provide <<customer_name>> with the ability to concentrate its sub-loops onto multiple DS1s back to the BellSouth Central Office. The DS1s will then be terminated into <<customer_name>>’s collocation space. TR-008 and TR303 interface standards are available.

  • Open Source Assurance Program For Software that is Red Hat branded, purchases under this Agreement may entitle Client to participate in Red Hat’s Open Source Assurance Program which is described at xxxx://xxx.xxxxxx.xxx/rhel/details/assurance/. The terms for this optional program are subject to a separate agreement which can be viewed at xxxx://xxx.xxxxxx.xxx/legal/open_source_assurance_agreement.html.

  • Project acronym Use the project acronym as indicated in the submitted proposal. It cannot be changed, unless agreed during the negotiations. The same acronym should appear on each page of the grant agreement preparation documents to prevent errors during its handling.

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

  • Unbundled Network Element Combinations 4.1 For purposes of this Section, references to “Currently Combined” Network Elements shall mean that the particular Network Elements requested by NewPhone are in fact already combined by BellSouth in the BellSouth network. References to “

  • Unbundled Sub-Loop Feeder 2.8.4.1 Unbundled Sub-Loop Feeder (USLF) provides connectivity between BellSouth's central office and cross-box (or other access point) that serves an end user location.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!