Domoticz

Domoticz Integration with eHouse BMS System

Integration eHouse controllers with Domoticz Home Automation Software

Domoticz is Home Automation Software for integration various types of systems. The core of the system is written i C++, so it is relatively faster than other competitive software (OpenHab, Open Remote, etc) written in Java.

Domoticz integration use eHouse TCP/IP & UDP protocols.

eHouse TCP/IP & UDP Protocol is documented :eHouse IP Protocol

eHouse IP based controllers (LAN, WiFi, PRO):

  • send UDP broadcast status which is available in Local Network (Ethernet+WiFi)
  • have TCP/IP sockets client/server for sending/receiving commands (eHouse Events)
  • can send status also via TCP/IP (sockets) to the Internet
  • eHouse.Pro Server gathers all eHouse statuses from any controllers and can send them to any client application via TCP/IP (sockets)

Best way of integration is reception UDP Status from eHouse Controllers and send command via TCP/IP on local network.
Domoticz can be run on the same machine, where eHouse PRO server is running if efficiency is sufficient.
For testing purposes domoticz can also be run on the Internet side if we have public access via Internet.

Our Domoticz repository is located at eHouse 4 Domoticz
It can be compiled under Windows (Visual Studio Community Edition 2017) or Linux (CMAKE) for various hardware & OS.
It can be added Directly to Visual Studio cloning https://github.com/ehousepro/domoticz.git repository.

Domoticz Configuration for eHouse System Integration:

  • IP address of eHouse.PRO server (required for remote TCP/IP connection). Default PRO address in the system is 192.168.0.200
  • PORT (TCP/IP) – Server Port for all eHouse controllers & eHouse PRO server. Default TCP/IP port: 9876
  • PORT (UDP) – Broadcast of controller statuses are distributed via local network on port: 6789 (non editable value)
  • Password – password which will be used for dynamic code authorization to controllers 6 ascii chars. Default: “abBrac”
  • Auto Discovery – This mode enables automatically discovery of all eHouse Devices in the installation.
  • Enable PRO – enables eHouse PRO (directly connected I/O buffers) and BMS hardware (thermostats, temp sensors, RFID, etc)
  • Enable Alarm Inputs – future use. Add Alarm signals for each inputs (Early Warning, Monitoring, Silent Alarm, Horn, Warning Light). Increase Domoticz Input objects for PRO/CM/LM (~5..6 times)
  • Option A – additional options (bitwise). Administrative purposes keep it to 0 – don’t modify it unless you know exactly what You are doing
  • Option B – additional options (bitwise). Administrative purposes keep it to 0 – don’t modify it unless you know exactly what You are doing

Integration/Connection of various eHouse IP Controllers:

  • eHouse Ethernet: directly on LAN/WiFi Network. Do not require eHouse PRO server in LAN Network for continuous work of Domoticz – after complete auto-discovery of all controllers
  • eHouse WiFi: directly on WiFi/LAN Network. Do not require eHouse PRO server in LAN Network for continuous work of Domoticz – after complete auto-discovery of all controllers
  • eHouse PRO: directly on WiFi/LAN Network

Integration of various eHouse NON IP Controllers (indirectly VIA eHouse PRO Server & Communication gateways):

  • eHouse RS-485: must work under Main Host Supervision: CommManager, LevelManager, eHouse.Exe or eHousePRO. Require eHouse PRO server (or other host) for continuous work for integration with Domoticz
  • eHouse Aura: Thermostats must work under Main Host Supervision: eHousePRO connected via USB->AURA-485 gateway. Require eHouse PRO server for continuous work for integration with Domoticz
  • eHouse CAN/RF: currently not implemented (future) must work under Main Host Supervision: eHousePRO. Require eHouse PRO server (or other host) for continuous work for integration with Domoticz
  • eHouse RFID: currently not implemented (future) must work under Main Host Supervision: eHousePRO. Require eHouse PRO server (or other host) for continuous work for integration with Domoticz
  • eHouse BMS: other systems integrated with eHouse (future)

eHouse Controllers Supported by domoticz.

eHouse Ethernet controllers are large ( more than 50 intelligent points) microcontroller based units which can work standalone/autonomic after remote configuration via Windows application “eHouseWiFi.exe”:

1) ERM (EthernetRoomManager) – Room Controller

ERM
Domoticz Support:

  • Single Outputs: on/off
  • Double Outputs (blinds): open/close/set value
  • Dimmer (on/off/set value)
  • Thermostat Regulation Point (+/-/Set value)
  • Measurement input associated with Thermostat Preset
  • 10 Light Scenes/Programs (on/off outs + dimmers)
  • 10 ADC Measurement Programs
  • Inputs status Show
  • Room Plan Auto Creation

2) CM/LM (CommManager/LevelManager) – centralized controller with security system functionality

Ethernet LevelManager/CommManager
Domoticz Support:

  • Single Outputs: on/off
  • Double Outputs (blinds): open/close/set value
  • Thermostat Regulation Point (+/-/Set value)
  • Measurement input associated with Thermostat Preset
  • 10 Blinds Scenes/Programs (on/off outs + dimmers)
  • 10 ADC Measurement Programs
  • Inputs status Show
  • Room Plan Auto Creation

3) EPM (Ethernet Pool Manager) – Swimming Pool Controller

(dedicated firmware for optimal control of Swimming POOL): Ethernet Pool Manager Domoticz Support (In the future):

eHouse WiFi 2.4GHz b/g/n

controllers are medium size ( more than 10 intelligent points) microcontroller based units which can work standalone/autonomic after remote configuration via Windows application “eHouseWiFi.exe”:
eHouse WiFi All-In-One
– Domoticz Support:

  • Single Outputs: on/off
  • Double Outputs (blinds): open/close/set value
  • Dimmers (on/off/set value)
  • Thermostat Regulation Point (+/-/Set value)
  • Measurement input associated with Thermostat Preset
  • Inputs status Show
  • Room Plan Auto Creation

eHouse PRO/BMS

eHouse BMS

eHouse PRO are centralized Home Automation system based on Linux Microcomputer (Raspberry PI 1/2/3, Banana Pi/Pro, etc). With I/O Buffers and integrations (eHouse BMS, Thermostat, MySQL, Cloud, etc).
eHouse PRO server software without I/O buffers can also run on PC computers.
– Domoticz Support:

  • Single Outputs: on/off
  • Double Outputs (blinds): open/close/set value
  • Inputs status Show
  • 10 Light Scenes/Programs (on/off outs)
  • 10 Blinds Scenes/Programs (open/close – double outputs )
  • 10 Security Zones (on/off inputs masks)
  • Room Plan Auto Creation

eHouse RS-485 controllers

are large ( more than 49 intelligent points) microcontroller based units which can work standalone/autonomic after remote configuration via Windows application “eHouse.exe”:
1) RM (RoomManager) – Room Controller: eHouse RS-485
– Domoticz Support:

  • Single Outputs: on/off
  • Measurement input show as temperature
  • 10 Light Scenes/Programs (on/off outs + dimmers)
  • 10 ADC Measurement Programs
  • Inputs status Show
  • Room Plan Auto Creation

2) HM (HeatManager) – Boiler Room, Central Heating, Ventilation Controller

(dedicated firmware for optimal control of Heating): Heat Manger

3) CM/LM (CommManager/LevelManager) – centralized controller with security system functionality

CommManager/LevelManager

Aura Wireless thermostat + temperature sensor

– thermometer with LED Display
– Thermostat Preset Local/Server
– Domoticz Support:
– Thermostat Regulation Point (+/-/Set value)
– Thermometer associated with Thermostat Preset
– Special Inputs status Show
– Room Plan Auto Creation for all Aura controllers
– 10 ADC Measurement Programs for all Aura controllers

Step By step operations for Domoticz

  • Name all signals for each controller: unused devices should starting from ‘@’ => signal will be ignored and won’t add it to domoticz
  • Configure all eHouse LAN, WiFi controllers with eHouseWiFi.exe application & press Save Settings (only via Ethernet)
  • Configure all eHouse RS-485 controllers with eHouse.exe application & press Update settings (require eHouse RS-485 full duplex dongle)
  • Configure eHouse PRO server (copy all eHouse LAN, WiFi, RS-485 controller settings if kept in other place)
  • Configure all eHouse Aura Thermostat (require eHouse Aura Dongle connected to eHouse.PRO)
  • Install/Compile Domoticz on eHouse PRO server Hardware (RPI2/3) or PC: recent version of repository : eHouse 4 Domoticz
  • Configure Domoticz (Setup/Hardware/Add) – “eHouse UDP + TCP – LAN Interface”
  • Data Timeout: Disabled
  • Refresh ms: 1000
  • Default IP: 192.168.0.200 for eHouse PRO server used in local Ethernet/WiFi network.
    In case of entering external public IP not in 192.168.x.x network eHouse Gateway for Domoticz will use TCP/IP connection to server instead of UDP.
  • Port: 9876 (TCP/IP) – to send events or for Internet connection via TCP/IP
  • Password [6 ascii chars] Default:”abBrac”. Password must be set the same for all eHouse controllers. Each controller must have “XOR Password” – dynamic authorization set.
  • Auto Discovery = 1 – Automatically discover new eHouse controllers on restart of eHouse Service for Domoticz
  • EnablePRO = 1 – Enable eHouse PRO centralized system
  • Alarm Inputs = 0 – Enable Alarm system (5 times more objects for each eHousePRO/CM inputs) – FUTURE
  • OptA = 0, OptB = 0 – bitwise administrative options (should be 0 for normal operation)
  • When all controllers will be automatically discovered “Auto Discovery” flag can be disabled (however “Auto Discovery” is initiated only on Restart of eHouse Hardware gateway for Domoticz)
  • You can modify discovered names in Domoticz (don’t change ID and other fields). Already existed signals (IDs) and names will not be overwritten.

Domoticz Device ID construction hex coded: <I/O Nr>
Initial conditions: eHouse IP controllers must be on static IP – DHCP Settings outside eHouse RANGE (LSB=50..99), MSB:0 strongly recommended:

  • eHouse PRO IP: 192.168.0.200 (Default)
  • eHouse LAN ERM IP: 192.168.0.201…248 (Required Range)
  • eHouse LAN EPM IP: 192.168.0.249 (Required Range)
  • eHouse LAN CM/LM IP: 192.168.0.254…250 (Required Range)
  • eHouse WiFi IP: 192.168.0.100…199 (Required Range)
  • Illegal values u.x.y.z for eHouse LAN, PRO, WiFi controllers: y<>(1,2,55,85,120-140),
    Necessary values u=192, x=168

Reserved addresses (high):

  • y=1 allocated for HeatManager (RS-485)
  • y=2 allocated for ExternalManager (RS-485)
  • y=55 allocated for RoomManagers (RS-485)
  • y=85 allocated for infrared barrier (RS-485)
  • y=120..127 allocated for eHouse RF
  • y=128 allocated for eHouse CAN
  • y=129 allocated for eHouse AURA thermostat
  • y=130..140 future use

(+) success
(-) not tested
(*) – suggested platforms

Stability and efficiency precautions:
– eHouse Pro Server with eHouse PRO I/O processor utilization (~5-15%) RPI3
– Domoticz processor utilization (1-5%) RPI3 – inactive web interface In case of serious efficiency problems:
– Domoticz software can be installed on another computer (RPI3 or more efficient 8 cores, PC, etc)
– Disable “Auto Discovery” after system setting up system (no changes any longer)### Build Status

(continuous) 12*RM,HM, 12*AURA, PRO128/128 (~1000 Domoticz points/devices) + eHouse.PRO Server

HW OS Compilation LAN UDP/TCP Internet TCP/IP 100% Tested eHouse Controllers
PC x64(2,4,8) Win 7 VS2017 CE (+) (+) (+) (*) 12*RM,HM, 12*AURA, PRO128/128, 12*ERM,CM, 22*WIFI (~1900 Domoticz points/devices)
PC x64 Win 8.1 VS2017 CE (-) (-) (-) 12*RM,HM, 12*AURA, PRO128/128, 12*ERM,CM, 22*WIFI (~1900 Domoticz points/devices)
PC x64 Win 10 VS2017 CE (-) (-) – (*) 12*RM,HM, 12*AURA, PRO128/128, 12*ERM,CM, 22*WIFI (~1900 Domoticz points/devices)
PC x64 Ubuntu 16 CMAKE (+) (+) + (*) 12*RM,HM, 12*AURA, PRO128/128, 12*ERM,CM, 22*WIFI (~1900 Domoticz points/devices)
PC x64 Ubuntu 17 CMAKE (+) (+) + (*) 12*RM,HM, 12*AURA, PRO128/128, 12*ERM,CM, 22*WIFI (~1900 Domoticz points/devices)
RPI1 Raspbian CMAKE (-) (-) (-) 1 ERM, PRO – stability test without WWW interface utilization ( ~ 300 Domoticz points/devices)
RPI2 Raspbian CMAKE (+) (-) (-)
RPI3 Raspbian CMAKE (+) (+) (+) (*) 12*RM,HM, 12*AURA, PRO128/128, 12*ERM,CM, 22*WIFI (~1900 Domoticz points/devices)+ eHousePRO Server