Changes between Version 35 and Version 36 of WikiStart


Ignore:
Timestamp:
2014-04-30 12:31:58 (10 years ago)
Author:
lolodomo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v35 v36  
    2929=== Setup of received protocols === 
    3030 
    31 Once you have the RFXtrx controller and plug-in installed you now need to start looking at the RF protocols you want the RFXtrx device to receive and you can do this by accessing the Settings tab of the RFXtrx Controller device. 
     31Once you have the RFXtrx controller and plug-in installed you now need to start looking at the RF protocols you want the RFXtrx device to receive and you can do this by accessing the tab "RFXtrx settings" of the RFXtrx Controller device. 
    3232By default, you may notice a number already switched on, it matches what is currently saved in the RFXtrx memory. But it’s now time to think about which protocols you actually want to use, because 
    3333 * not all can coexist, 
    … …  
    4040 * these settings are lost after a firmware update of the RFXtrx and need to be set again. 
    4141 
    42 === Setup of temperature and speed units === 
     42=== General plugin settings === 
    4343 
    44 ... 
     44You can adjust general plugin settings in the tab "Plugin settings" of the RFXtrx Controller device. 
     45These settings include: 
     46 * selection of the temperature unit, 
     47 * selection of the speed unit, 
     48 * filling the voltage for the power calculation, 
     49 * enabling or disabling the debug logs, 
     50 * enabling or disabling the automatic creation of devices by the plugin. 
     51Just push the Set button at right of each setting to validate your change; no need to reload the Vera. 
     52 
    4553 
    4654=== Creation of Vera devices === 
    … …  
    4856By default, the devices are created automatically by the plugin accordingly to the messages received from the RFXtrx. 
    4957 
    50 To disable the automatic creation of devices, you can access the Advanced tab of the RFXtrx Controller device and set the value of the variable named "!AutoCreate" to 0. Then push the red button "Save" at top right in the dashboard to validate your change. 
     58To disable the automatic creation of devices, you can access the tab "Plugin settings" of the RFXtrx Controller device, select "OFF" at right of the setting "Automatic creation of devices" and finally push the button "Set" to validate your change. 
    5159 
    52 Even while keeping the automatic creation mechanism (variable "!AutoCreate" set to 1), it is possible to disable the creation of certain devices. It can be useful for example if your RFXtrx Controller device receives data from your neighbors's devices like weather sensors and you don't want them in your Vera dashboard. To do that, you have to use the new variable "!DisabledDevices" to list the devices you don't want to be created by the plugin. You can access this variable in the Advanced tab of the RFXtrx Controller device. The value of this variable is a comma-separated list of "device id". The "device id" is the value of the attribute "altid" you can get for each Vera device in the advanced tab. 
     60Even while keeping the automatic creation mechanism (variable "!AutoCreate" set to 1), it is possible to disable the creation of certain devices. It can be useful for example if your RFXtrx Controller device receives data from your neighbors's devices like weather sensors and you don't want them in your Vera dashboard. To do that, you have to use the new variable "!DisabledDevices" to list the devices you don't want to be created by the plugin. You can access this variable in the tab "Advanced" of the RFXtrx Controller device. The value of this variable is a comma-separated list of "device id". The "device id" is the value of the attribute "altid" you can get for each Vera device in the advanced tab. 
    5361Here is an example of value that will disable the creation of two devices, an Oregon temperature sensor and a Blyss switch device: "TS/T1/1537,LS/L6.0/9C4B/E1". Note that you will have to delete manually the unwished devices that are already created. After updating the variable, push the red button "Save" at top right in the dashboard to validate your change. 
    5462 
    55 Few devices can be created manually by the user using the Settings tab of the RFXtrx Controller device. 
     63Few devices can be created manually by the user using the tab "New device" of the RFXtrx Controller device. 
    5664... 
    5765 
    … …  
    118126|| La Crosse - TX2, TX3, TX4, TX17, WS2300 || 433.92MHz || Yes || No || La Crosse || Yes || || 
    119127|| La Crosse - TX5 || 433.92MHz || Yes || No || La Crosse || No || || 
    120 || Alecto - WS1200 || 433.92MHz || Yes || No || La Crosse || Yes (will be in beta 2) || || 
     128|| Alecto - WS1200 || 433.92MHz || Yes || No || La Crosse || Yes || || 
    121129|| TFA - TS15C, TS34C, 30.3133 || 433.92MHz || Yes || No || Hideki / UPM || Yes || || 
    122130|| Oregon 1.0 - THR128,THR138,THC138 || 433.92MHz || Yes || No || Oregon Scientific || Yes || || 
    123 || Oregon 2.1 / Huger - THGN122N, THGR122NX, THGN123N, RGR126, UVN128, UVR128, THGN132N, THGN132ES, UV138, THGR228N, THGRN228NX, THGR238, THGR268, RTGN318, RTHN318, RTGR328N, THGR328N, RTGR368N, THGN500, RGR682, THGR918, BTHR918, BTHR918N, RGR918, STR918, WGR918, RGR928, STR928, THGR928, WGR928, BTHR968, EW109 || 433.92MHz || Yes || No || Oregon Scientific || Yes (EW109 in coming beta 2) || || 
     131|| Oregon 2.1 / Huger - THGN122N, THGR122NX, THGN123N, RGR126, UVN128, UVR128, THGN132N, THGN132ES, UV138, THGR228N, THGRN228NX, THGR238, THGR268, RTGN318, RTHN318, RTGR328N, THGR328N, RTGR368N, THGN500, RGR682, THGR918, BTHR918, BTHR918N, RGR918, STR918, WGR918, RGR928, STR928, THGR928, WGR928, BTHR968, EW109 || 433.92MHz || Yes || No || Oregon Scientific || Yes || || 
    124132|| Oregon 3.0 - PCR800,UVN800,WGR800,WTGR800,TGHN800,TGHN801,THGR810 || 433.92MHz || Yes || No || Oregon Scientific || Yes || || 
    125133|| Oregon BWR101/BWR102 || 433.92MHz || Yes || No || Oregon Scientific || Yes || || 
    126134|| Oregon GR101 || 433.92MHz || Yes || No || Oregon Scientific || Yes || || 
    127 || OWL CM113, cent-a-meter, Electrisave || 433.92MHz || Yes || No || Oregon Scientific || Yes (will be in beta 2) || || 
     135|| OWL CM113, cent-a-meter, Electrisave || 433.92MHz || Yes || No || Oregon Scientific || Yes || || 
    128136|| OWL CM119 / CM160 / CM180 || 433.92MHz || Yes || No || Oregon Scientific || Yes || || 
    129 || OWL CM180i || 433.92MHz || Yes || No || Oregon Scientific || Yes (will be in beta 2) || || 
     137|| OWL CM180i || 433.92MHz || Yes || No || Oregon Scientific || Yes || || 
    130138|| UPM/Esic - WT260,WT260H,WT440H,WT450,WT450H,WDS500,RG700 || 433.92MHz || Yes || No || Hideki / UPM || Yes || || 
    131139|| Viking 02035, 02038, 02811 || 433.92MHz || Yes || No || !FineOffset / Viking || Yes || || 
    132140|| KD101 smoke detector - Avidsen, Chacon, NEXA, Flamingo || 433.92MHz || Yes || Yes || Always on || Yes || || 
    133 || Alecto SA30 smoke detector || 433.92MHz || Yes || Yes || Oregon Scientific || Yes (will be in beta 2) || || 
     141|| Alecto SA30 smoke detector || 433.92MHz || Yes || Yes || Oregon Scientific || Yes || || 
    134142|| Harrison curtain || 433.92MHz || No || Yes || || Yes || except program command || 
    135143|| !RollerTrol blinds || 433.92MHz || Yes || Yes || !RollerTrol / Hasta || Yes || except set limit command || 
    … …  
    156164The RFXtrx plugin is discussed in two main places 
    157165 
    158  * [http://forum.micasaverde.com/index.php/topic,9563.0.html Micasaverde forum thread] (in english) 
     166 * [http://forum.micasaverde.com/index.php/board,45.0.html Micasaverde forum thread] (in english) 
    159167 * [http://touteladomotique.com/forum/viewtopic.php?f=48&t=7218 Toute la domotique forum thread] (in french)