livebox:xap_adapter

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		 Previous revision
Next revisionBoth sides next revision
livebox:xap_adapter [2011/12/17 19:32] – created brettlivebox:xap_adapter [2011/12/18 18:17] – [Inputs and Relays] brett
Line 24: Line 24:
 There are several sections in the ///etc/xap-livebox.ini// which are use to control and configure its runtime behaviour. There are several sections in the ///etc/xap-livebox.ini// which are use to control and configure its runtime behaviour.
  
-The webserver interacts with this daemon by using an internal (127.0.0.1) socket connection on port 79.  This allows each component to be restarted independently of the other.  If the web server fails to communicate with the xap-livebox daemon you will see the message "**Could not connect**" being displayed on the webserver.  If this occurs, verify that the xap-livebox process is running.+The webserver interacts with this daemon by using an internal (127.0.0.1) socket connection on port 79.  This allows each component to be restarted independently of the other.  If the web server fails to communicate with the xap-livebox daemon you will see the message "**?**" being displayed on the webserver.  If this occurs, verify that the xap-livebox process is running. 
 ===== 1-Wire ===== ===== 1-Wire =====
 +
 +{{:livebox:1wire-setup.jpg|}}
  
 <code ini> <code ini>
Line 38: Line 41:
 Each sensor can be given a label using the nomenclature "sensor#.label=<your label>".  These are best setup using the WEB interface but can be done manually too. The assigned label will be included in the xAP message that is generated when the temperature changes. The 'displaytext' tag will have the format 'displaytext=<label> <temperature>' e.g. displaytext=Inside 21.0 Each sensor can be given a label using the nomenclature "sensor#.label=<your label>".  These are best setup using the WEB interface but can be done manually too. The assigned label will be included in the xAP message that is generated when the temperature changes. The 'displaytext' tag will have the format 'displaytext=<label> <temperature>' e.g. displaytext=Inside 21.0
  
-===== RF =====+===== Inputs and Relays =====
  
-The RF sections contains the pulse codes that are loaded into the EEPROM of the MEGA8 chip to control the RF transmitter. As the HAH boots up, these codes are sent to the MEGA8. However, the EEPROM is only written to if the code presented is different from the one already stored. This reduces the 'wear' on the EEPROM. +{{:livebox:config-relays-inputs.jpg|}}
- +
-Details regarding the format of the hex strings can be found [[http://www.dbzoo.com/livebox/hah#rf|here]] +
- +
-Note that the codes shown below are for the Lidl Rf Mains sockets. If you plan to use BBSB sockets, you will need to use our little Rf code generator program to prepare the correct strings for the .ini file  (and you will also need the Mega8 microcontroller that is programmed for use with BBSB). \\ +
-<code ini> +
-[rf] +
-# Up to 12 RF channels may be defined. +
-devices=4 +
-rf1.off=4D2AAAAAAA80 +
-rf1.on=4D2AAAAB2B00 +
-rf2.off=4D2AAACAAC80 +
-rf2.on=4D2AAACB2D00 +
-rf3.off=4D2AAAB2AB00 +
-rf3.on=4D2AAAB32A80 +
-rf4.off=4D2AAAD2AD00 +
-rf4.on=4D2AAAD32C80 +
-rf1.label=RF 1 +
-rf2.label=RF 2 +
-rf3.label=RF 3 +
-rf4.label=RF 4 +
-</code> +
- +
-More recently, we've introduced a 'universal' RF command. Details are [[http://www.dbzoo.com/livebox/universalrf|here]]  +
- +
-===== Inputs and Relays =====+
  
 These sections allow us to configure user friendly names that will appear on the webserver interface.  The xAP protocol does not make use of these labels. These sections allow us to configure user friendly names that will appear on the webserver interface.  The xAP protocol does not make use of these labels.
  • livebox/xap_adapter.txt
  • Last modified: 2012/03/20 12:13
  • by minerva9