Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
##KNX - The Worldwide STANDARD for Home and Building Control. In order to transfer control data to all building management components, a system is required that does away with the problems of isolated devices by ensuring that all components communicate via one common language: in short, a system such as the manufacturer and application domains independent KNX Bus. This standard is based upon more than 20 years of experience in the market, amongst others with predecessor systems to KNX: EIB, EHS and BatiBUS. Via the KNX medium to which all bus devices are connected (twisted pair, radio frequency, power line or IP/Ethernet), they are able to exchange information. (Source: KNX.org)
##Hardware Bus devices can either be sensors or actuators needed for the control of building management equipment such as: lighting, blinds / shutters, security systems, energy management, heating, ventilation and air-conditioning systems, signaling and monitoring systems, interfaces to service and building control systems, remote control, metering, audio / video control, white goods, etc. All these functions can be controlled, monitored and signaled via a uniform system without the need for extra control centers. (Source: KNX.org)
When choosing products make sure they offer extra group addresses for status feedback. This works best with the current OpenRemote KNX implementation.
The functionalities of the following products are supported by OpenRemote. Certified products are extensively tested in combination with Professional Designer and supported by OpenRemote certified Integrators.
##Configuration of System The KNX IP gateways support auto discovery and OpenRemote tries to find your gateway via this functionality. If OpenRemote does not find your gateway you can try and configure it's IP and port in the config.properties file. There you find these 2 pramaters:
## # KNX-IP interface host name to use. If no hostname is provided here, # the KNX-IP driver will use first interface to be discovered. knx.ip.interface.hostname= ## # KNX-IP interface UDP port to use. This configuration is mandatory only # if a KNX-IP interface hostname is provided knx.ip.interface.port=3671
##Importing devices in the Designer - Building Modeler Currently the following commands and related DPT's are supported:
- DIM and SCALE can either get the value from a parameter (slider) or directly with the command e.g. "DIM 42"
- The xx with SCENE and LEARN_SCENE must be a number 1-64.
- The TEMP command only accepts integer in the moment eg. from a slider.
- Single and double decimal temperature commands can only receive paramter through rules at the moment.
- The TEXT command can send a 14 char text to KNX. The can either come through rules or directly with the command e.g. "TEXT this is text"
- The RGB command works together with the ColorPicker.
For more information on how to configure KNX devices with OpenRemote look here:
##Specific Designer Remarks - UI Designer Once you have your commands, sensors, switches and sliders configured within the "Building Modeler" you can go ahead and use them in your designs.
- Always check the OpenRemote forum for the latest developments.
- Translate 1-Wire to KNX
- Video: OpenRemote Russound, KNX and Rules Integration