User Tools

Site Tools


nexasystem

Differences

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

Link to this comparison view

Next revision
Previous revision
nexasystem [2009/06/28 23:08] – created seststnexasystem [2018/11/03 02:59] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +{{keywords>nethome java home automation nexa}}
 {{  :nexatotal.jpg  |Nexa devices}} {{  :nexatotal.jpg  |Nexa devices}}
  
 ====== NetHomeServer Nexa Connection ====== ====== NetHomeServer Nexa Connection ======
-Nexa is a radio based system for remote control of switches and dimmers. It also includes PIR-detectors, magnet switches for windows and other detectors which work as remotes and can control the switches.+Nexa is a radio based system for remote control of switches and dimmers. Nexa is really just one of the names this system is sold under. The actual devices are made by ArcTec, but branded by resellers in Europe and US. It is also sold under the product names: Chacon, Elro AB600 and Proove. The system also includes PIR-detectors, magnet switches for windows and other detectors which work as remotes and can control the switches.
  
-Nexa has two addressing systems, one old where devices are explicitly given a house code and device code and one newer "self learning" system where transmitters have unique addresses and the receivers "learn" the code of the sender which is controlling it. NetHomeServer supports both variants, which in reality are two entirely different protocols.+Nexa has two addressing systems, one old where devices are explicitly given a house code and device code with code wheels and one newer "self learning" system where transmitters have unique addresses and the receivers "learn" the code of the sender which is controlling it. NetHomeServer supports both variants, which in reality are two entirely different protocols.
  
-The Nexa system have no native computer interface. It does however use the standard 443MHz radio band (in Europe), which makes it possible to use the generic 443MHz receiver and sender of the NetHomeServer to send and receive commands to and from Nexa devices. +The Nexa system have no native computer interface. It does however use the standard 433MHz radio band (in Europe), which makes it possible to use the generic 433MHz receiver and sender of the NetHomeServer to send and receive commands to and from Nexa devices. 
  
-This means that NetHomeServer interfaces with the FS20-system via the [[AudioProtocolParser]] and the [[AudioProtocolTransmitter]] interface modules. Currently you will have to build the hardware for the actual transmitters and receivers yourself, but it is quite easy done by modifying existing products. +You can use the [[cul|NetHomeServer CUL Connection]] for sending the radio control messages 
 + 
 +You can also use the [[AudioProtocolParser]] and the [[AudioProtocolTransmitter]] interface modules. Currently you will have to build the hardware for the actual transmitters and receivers yourself, but it is quite easy done by modifying existing products.
  
   * [[modupm |Building receiver is done by modifying an UPM thermometer]]   * [[modupm |Building receiver is done by modifying an UPM thermometer]]
Line 16: Line 19:
   * Remote control of devices - you can switch on and off lamps via the WEB-interfaces   * Remote control of devices - you can switch on and off lamps via the WEB-interfaces
   * Interface module - via the NetHomeServers interfaces (TCP/IP, SOAP UDP/IP) you can let other software control the lamps   * Interface module - via the NetHomeServers interfaces (TCP/IP, SOAP UDP/IP) you can let other software control the lamps
-  * Home automation - via NetHomeServer:s timers and other control objects you can automate and link events to actions on Nexa-controlled appliances.+  * Nexa Home Automation - via NetHomeServer:s timers and other control objects you can automate and link events to actions on Nexa-controlled appliances.
   * Home integration - let Nexa wall switches and PIR-detectors control other actions or remote systems via the NetHomeServer   * Home integration - let Nexa wall switches and PIR-detectors control other actions or remote systems via the NetHomeServer
  
Line 22: Line 25:
 The Nexa-Related objects in the NetHomeServer are: The Nexa-Related objects in the NetHomeServer are:
   * //[[NexaLamp]]// Controls a dimmer or a switch   * //[[NexaLamp]]// Controls a dimmer or a switch
-  * //[[NexaRemapButton]]// Lets you control other Items with a Nexa-switch+  * //[[NexaRemapButton]]// Lets you control other Items with a Nexa remote control
   * //[[NexaLCLamp]]// Controls a dimmer or a switch using the Learning Code protocol   * //[[NexaLCLamp]]// Controls a dimmer or a switch using the Learning Code protocol
   * //[[AudioProtocolParser]]// General protocol receiver using the microphone input, used to receive Nexa radio signals   * //[[AudioProtocolParser]]// General protocol receiver using the microphone input, used to receive Nexa radio signals
   * //[[AudioProtocolTransmitter]]// General protocol transmitter using the audio output of the PC to send RF-signal and control Nexa switches.   * //[[AudioProtocolTransmitter]]// General protocol transmitter using the audio output of the PC to send RF-signal and control Nexa switches.
 +  * //[[cultransceiver|CULTransceiver]]// Interfaces with the [[cul|CUL]] RF transmitter
  
 +===== Limitations =====
 +The old Nexa system where you manually set the adresses has a big limitation in the way dimmers are controlled which makes computer controlled dimming of Nexa devices practically impossible. The self learning version however has excellent support for dimming to an absolute level.
  
 +Dimming of an old Nexa Device is done by holding down the button of the remote control for a while - this starts the "dim mode" where the dim level constantly rises and falls. When the wanted dim level is reached, you press the button again to freeze the current level. This means you actually have to see the lamp while dimming and it needs very low latency on the control (to stop at the right moment). This makes it difficult to use in computer controlled remote control applications. The on/off function however is good, in the sense that it has separate on and off commands (not just toggle), this is very good for computer control. See [[comparesystems|system comparison page]] for comparison with other remote control systems.
  
  
nexasystem.1246223280.txt.gz · Last modified: 2018/11/03 02:57 (external edit)