Code Monkey home page Code Monkey logo

hmccu's Introduction

HMCCU

Module for FHEM - Homematic CCU Integration

Version 5.0

Support

If you like this module and would like to support development I would appreciate a donation:

Installation

Warning! This is a beta version of the HMCCU modules. Please backup your FHEM installation before you install it.

In FHEM enter

update all https://raw.githubusercontent.com/zapccu/HMCCU/master/controls_HMCCU.txt

Configuration

Define a HMCCU device representing your CCU

Assuming your CCU has the IP address 192.168.1.100, use the following command to define a new HMCCU (I/O) device:
define myCCU HMCCU 192.168.1.100
Depending on the number of devices known by the CCU the definition of the I/O device can take up to 1 minute. During definition the CCU configuration is read by HMCCU.

Create FHEM devices for CCU devices

Use command "get createDev" to create new FHEM devices. If a CCU device type is not known by HMCCU, you must define it manually.

Migrating from HMCCU version 4.3

General

HMCCU 5.0 comes with a new auto detection function for Homematic devices. If a device can be detected automatically, most of the attributes like substitute, statevals, ... are no longer needed.

Resetting default attributes for devices

If one defines a new device of type HMCCUDEV or HMCCUCHN, HMCCU tries to detect the role of the new device and automatically assigns default settings to it.

To use the new default attributes approach for existing devices, execute the following command:

set myDevice defaults reset

Don't forget to save your configuration after changing the attributes.

hmccu's People

Contributors

zapccu avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar

Forkers

tkempken erdalga

hmccu's Issues

Add support for brightness sensor

Device channels and datapoints

DEV Helligkeitssensor 000D5BE9A46818 interface=HmIP-RF type=HmIP-SLO
CHN 000D5BE9A46818:0 Helligkeitssensor:0
DPT {b} HmIP-RF.000D5BE9A46818:0.CONFIG_PENDING = false [RE]
DPT {b} HmIP-RF.000D5BE9A46818:0.DUTY_CYCLE = false [RE]
DPT {b} HmIP-RF.000D5BE9A46818:0.INSTALL_TEST = true [RW]
DPT {b} HmIP-RF.000D5BE9A46818:0.LOW_BAT = false [RE]
DPT {f} HmIP-RF.000D5BE9A46818:0.OPERATING_VOLTAGE = 3.100000 [RE]
DPT {i} HmIP-RF.000D5BE9A46818:0.OPERATING_VOLTAGE_STATUS = 0 [RE]
DPT {n} HmIP-RF.000D5BE9A46818:0.RSSI_DEVICE = 220 [RE]
DPT {n} HmIP-RF.000D5BE9A46818:0.RSSI_PEER = 0 [RE]
DPT {b} HmIP-RF.000D5BE9A46818:0.UNREACH = false [RE]
DPT {b} HmIP-RF.000D5BE9A46818:0.UPDATE_PENDING = false [RE]
CHN 000D5BE9A46818:1 HmIP-SLO 000D5BE9A46818:1
DPT {f} HmIP-RF.000D5BE9A46818:1.AVERAGE_ILLUMINATION = 188.700000 [RE]
DPT {i} HmIP-RF.000D5BE9A46818:1.AVERAGE_ILLUMINATION_STATUS = 0 [RE]
DPT {f} HmIP-RF.000D5BE9A46818:1.CURRENT_ILLUMINATION = 117.280000 [RE]
DPT {i} HmIP-RF.000D5BE9A46818:1.CURRENT_ILLUMINATION_STATUS = 0 [RE]
DPT {f} HmIP-RF.000D5BE9A46818:1.HIGHEST_ILLUMINATION = 240.400000 [RE]
DPT {i} HmIP-RF.000D5BE9A46818:1.HIGHEST_ILLUMINATION_STATUS = 0 [RE]
DPT {f} HmIP-RF.000D5BE9A46818:1.LOWEST_ILLUMINATION = 117.280000 [RE]
DPT {i} HmIP-RF.000D5BE9A46818:1.LOWEST_ILLUMINATION_STATUS = 0 [RE]

Device detection:
No state datapoint detected
No control datapoint detected

Failed to detect device settings. Device must be configured manually.

Device description

Device 000D5BE9A46818 Helligkeitssensor [HmIP-SLO]
AES_ACTIVE: 1
AVAILABLE_FIRMWARE: 0.0.0
CHILDREN: 000D5BE9A46818:0,000D5BE9A46818:1,000D5BE9A46818:2,000D5BE9A46818:3
DIRECTION: NONE
FIRMWARE: 1.0.16
FIRMWARE_UPDATE_STATE: UP_TO_DATE
FLAGS: Visible
PARAMSETS: MASTER,SERVICE
RF_ADDRESS: 6272892
ROAMING: 0
RX_MODE: CONFIG
SUBTYPE: SLO
UPDATABLE: 1
Channel 000D5BE9A46818:0 Helligkeitssensor:0 [MAINTENANCE]
AES_ACTIVE: 1
DIRECTION: NONE
FLAGS: Visible
PARAMSETS: MASTER,VALUES,SERVICE
PARENT: 000D5BE9A46818
PARENT_TYPE: HmIP-SLO
RF_ADDRESS: 0
ROAMING: 0
RX_MODE:
UPDATABLE: 1
Channel 000D5BE9A46818:1 HmIP-SLO 000D5BE9A46818:1 [BRIGHTNESS_TRANSMITTER]
AES_ACTIVE: 1
DIRECTION: NONE
FLAGS: Visible
PARAMSETS: MASTER,VALUES,SERVICE
PARENT: 000D5BE9A46818
PARENT_TYPE: HmIP-SLO
RF_ADDRESS: 0
ROAMING: 0
RX_MODE:
UPDATABLE: 1
Channel 000D5BE9A46818:2 HmIP-SLO 000D5BE9A46818:2 [COND_SWITCH_TRANSMITTER]
AES_ACTIVE: 1
DIRECTION: SENDER
FLAGS: Visible
LINK_SOURCE_ROLES: CONDITIONAL_SWITCH
PARAMSETS: MASTER,VALUES,LINK,SERVICE
PARENT: 000D5BE9A46818
PARENT_TYPE: HmIP-SLO
RF_ADDRESS: 0
ROAMING: 0
RX_MODE:
UPDATABLE: 1
Channel 000D5BE9A46818:3 HmIP-SLO 000D5BE9A46818:3 [COND_SWITCH_TRANSMITTER]
AES_ACTIVE: 1
DIRECTION: SENDER
FLAGS: Visible
LINK_SOURCE_ROLES: CONDITIONAL_SWITCH
PARAMSETS: MASTER,VALUES,LINK,SERVICE
PARENT: 000D5BE9A46818
PARENT_TYPE: HmIP-SLO
RF_ADDRESS: 0
ROAMING: 0
RX_MODE:
UPDATABLE: 1

Grouping of HMCCUCHN/HMCCUDEV devices

If multiple HMCCUCHN devices belonging to the same Homematic device are defined by using "get create" or "get createDev", they should be automatically grouped by using the FHEM group attribute. Name of the group is the name of the Homematic device.

Add support for device type HM-SEN-MDIR-O-2

https://forum.fhem.de/index.php/topic,107077.msg1147616.html#msg1147616

https://forum.fhem.de/index.php/topic,107077.msg1147802.html#msg1147802

Device channels and datapoints

DEV Bewegungsmelder XXXXXXXXX interface=BidCos-RF type=HM-Sen-MDIR-O-2
CHN XXXXXXXXX:0 Bewegungsmelder:0
DPT {b} BidCos-RF.XXXXXXXXX:0.UNREACH = false [RE]
DPT {b} BidCos-RF.XXXXXXXXX:0.STICKY_UNREACH = false [RWE]
DPT {b} BidCos-RF.XXXXXXXXX:0.CONFIG_PENDING = false [RE]
DPT {b} BidCos-RF.XXXXXXXXX:0.LOWBAT = false [RE]
DPT {n} BidCos-RF.XXXXXXXXX:0.RSSI_DEVICE = 1 [RE]
DPT {n} BidCos-RF.XXXXXXXXX:0.RSSI_PEER = 160 [RE]
DPT {b} BidCos-RF.XXXXXXXXX:0.DEVICE_IN_BOOTLOADER = false [RE]
DPT {b} BidCos-RF.XXXXXXXXX:0.UPDATE_PENDING = false [RE]
DPT {n} BidCos-RF.XXXXXXXXX:0.AES_KEY = 0 [R]
DPT {b} BidCos-RF.XXXXXXXXX:0.ENTER_BOOTLOADER = [W]
CHN XXXXXXXXX:1 Bewegungsmelder:1
DPT {i} BidCos-RF.XXXXXXXXX:1.BRIGHTNESS = 195 [RE]
DPT {b} BidCos-RF.XXXXXXXXX:1.MOTION = false [RE]
DPT {b} BidCos-RF.XXXXXXXXX:1.INSTALL_TEST = [E]

Device detection:
No state datapoint detected
No control datapoint detected

Failed to detect device settings. Device must be configured manually.

Device description

Device XXXXXXXXX Bewegungsmelder [HM-Sen-MDIR-O-2]
CHILDREN: XXXXXXXXX:0,XXXXXXXXX:1
FIRMWARE: 1.6
FLAGS: Visible
INTERFACE: YYYYYYYYYY
PARAMSETS: MASTER
RF_ADDRESS: 2906099
ROAMING: 0
RX_MODE: LAZY_CONFIG,BURST
UPDATABLE: 1
Channel XXXXXXXXX:0 Bewegungsmelder:0 [MAINTENANCE]
AES_ACTIVE: 0
DIRECTION: NONE
FLAGS: Visible,Internal
PARAMSETS: MASTER,VALUES
PARENT: XXXXXXXXX
PARENT_TYPE: HM-Sen-MDIR-O-2
Channel XXXXXXXXX:1 Bewegungsmelder:1 [MOTION_DETECTOR]
AES_ACTIVE: 1
DIRECTION: SENDER
FLAGS: Visible
LINK_SOURCE_ROLES: KEYMATIC,SWITCH,WINMATIC
PARAMSETS: LINK,MASTER,VALUES
PARENT: XXXXXXXXX
PARENT_TYPE: HM-Sen-MDIR-O-2

Channel 0
Paramset VALUES
AES_KEY: INTEGER [R] [] RANGE=0...127 DFLT=0
CONFIG_PENDING: BOOL [R,E] [Visible,Sticky,Service] RANGE=0...1 DFLT=0
DEVICE_IN_BOOTLOADER: BOOL [R,E] [Visible,Sticky,Service] RANGE=0...1 DFLT=0
ENTER_BOOTLOADER: ACTION [W] [Visible,Sticky,Internal] RANGE=0...1 DFLT=0
LOWBAT: BOOL [R,E] [Visible,Sticky,Service] RANGE=0...1 DFLT=0
RSSI_DEVICE: INTEGER [R,E] [Visible,Sticky] RANGE=-2147483648...2147483647 DFLT=0
RSSI_PEER: INTEGER [R,E] [Visible,Sticky] RANGE=-2147483648...2147483647 DFLT=0
STICKY_UNREACH: BOOL [R,W,E] [Sticky,Internal] RANGE=0...1 DFLT=0
UNREACH: BOOL [R,E] [Visible,Sticky,Service] RANGE=0...1 DFLT=0
UPDATE_PENDING: BOOL [R,E] [Visible,Sticky,Service] RANGE=0...1 DFLT=0
Channel 1
Paramset LINK
PEER_NEEDS_BURST: BOOL [R,W] [Visible,Sticky] RANGE=0...1 DFLT=0
Paramset MASTER
AES_ACTIVE: BOOL [R,W] [Visible,Sticky,Internal] RANGE=0...1 DFLT=0
BRIGHTNESS_FILTER: INTEGER [R,W] [Visible,Sticky] RANGE=0...7 DFLT=7
CAPTURE_WITHIN_INTERVAL: BOOL [R,W] [Visible,Sticky] RANGE=0...1 DFLT=0
EVENT_FILTER_NUMBER: INTEGER [R,W] [Visible,Sticky] RANGE=1...15 DFLT=1
EVENT_FILTER_PERIOD: FLOAT [R,W] [Visible,Sticky] RANGE=0.5...7.5 DFLT=0.5 UNIT=s
LED_ONTIME: FLOAT [R,W] [Visible,Sticky] RANGE=0...1.275 DFLT=0.5 UNIT=s
MIN_INTERVAL: INTEGER [R,W] [Visible,Sticky] RANGE=0...4 DFLT=4
Paramset VALUES
BRIGHTNESS: INTEGER [R,E] [Visible,Sticky] RANGE=0...255 DFLT=0
INSTALL_TEST: ACTION [E] [Visible,Sticky,Internal] RANGE=0...1 DFLT=0
MOTION: BOOL [R,E] [Visible,Sticky] RANGE=0...1 DFLT=0

Add support for device type HM-CC-VD

https://forum.fhem.de/index.php/topic,107077.msg1147616.html#msg1147616

https://forum.fhem.de/index.php/topic,107077.msg1147802.html#msg1147802

Device channels and datapoints

DEV Keller-Ventil1 XXXXXXXXX interface=BidCos-RF type=HM-CC-VD
CHN XXXXXXXXX:0 Keller-Ventil1:0
DPT {b} BidCos-RF.XXXXXXXXX:0.UNREACH = false [RE]
DPT {b} BidCos-RF.XXXXXXXXX:0.STICKY_UNREACH = false [RWE]
DPT {b} BidCos-RF.XXXXXXXXX:0.CONFIG_PENDING = false [RE]
DPT {b} BidCos-RF.XXXXXXXXX:0.LOWBAT = false [RE]
DPT {n} BidCos-RF.XXXXXXXXX:0.RSSI_DEVICE = 1 [RE]
DPT {n} BidCos-RF.XXXXXXXXX:0.RSSI_PEER = 184 [RE]
CHN XXXXXXXXX:1 Keller-Ventil1:1
DPT {i} BidCos-RF.XXXXXXXXX:1.VALVE_STATE = 14 [RE]
DPT {i} BidCos-RF.XXXXXXXXX:1.ERROR = 0 [RE]

Device detection:
No state datapoint detected
No control datapoint detected

Failed to detect device settings. Device must be configured manually.

Device description

Device XXXXXXXXX Keller-Ventil1 [HM-CC-VD]
CHILDREN: XXXXXXXXX:0,XXXXXXXXX:1
FIRMWARE: 2.0
FLAGS: Visible
INTERFACE: YYYYYYYYYY
PARAMSETS: MASTER
RF_ADDRESS: 1738077
ROAMING: 0
RX_MODE: ALWAYS,LAZY_CONFIG
UPDATABLE: 0
Channel XXXXXXXXX:0 Keller-Ventil1:0 [MAINTENANCE]
AES_ACTIVE: 0
DIRECTION: NONE
FLAGS: Visible,Internal
PARAMSETS: MASTER,VALUES
PARENT: XXXXXXXXX
PARENT_TYPE: HM-CC-VD
Channel XXXXXXXXX:1 Keller-Ventil1:1 [CLIMATECONTROL_VENT_DRIVE]
AES_ACTIVE: 0
DIRECTION: RECEIVER
FLAGS: Visible
LINK_TARGET_ROLES: CLIMATECONTROL_TC
PARAMSETS: LINK,MASTER,VALUES
PARENT: XXXXXXXXX
PARENT_TYPE: HM-CC-VD

Channel 0
Paramset VALUES
CONFIG_PENDING: BOOL [R,E] [Visible,Sticky,Service] RANGE=0...1 DFLT=0
LOWBAT: BOOL [R,E] [Visible,Sticky,Service] RANGE=0...1 DFLT=0
RSSI_DEVICE: INTEGER [R,E] [Visible,Sticky] RANGE=-2147483648...2147483647 DFLT=0
RSSI_PEER: INTEGER [R,E] [Visible,Sticky] RANGE=-2147483648...2147483647 DFLT=0
STICKY_UNREACH: BOOL [R,W,E] [Sticky,Internal] RANGE=0...1 DFLT=0
UNREACH: BOOL [R,E] [Visible,Sticky,Service] RANGE=0...1 DFLT=0
Channel 1
Paramset MASTER
VALVE_ERROR_POSITION: INTEGER [R,W] [Visible,Sticky] RANGE=0...99 DFLT=0 UNIT=%
VALVE_OFFSET_VALUE: INTEGER [R,W] [Visible,Sticky] RANGE=0...25 DFLT=0 UNIT=%
Paramset VALUES
ERROR: ENUM [R,E] [Visible,Sticky,Service] RANGE=0...4 DFLT=0 VALUES=NO_ERROR,VALVE_DRIVE_BLOCKED,VALVE_DRIVE_LOOSE,ADJUSTING_RANGE_TO_SMALL,LOWBAT
VALVE_STATE: INTEGER [R,E] [Visible,Sticky] RANGE=0...99 DFLT=0 UNIT=%

Incorrect statedatapoint for devices with combined state channel

https://forum.fhem.de/index.php/topic,107077.msg1148499.html#msg1148499

Channel scheme (can be repeated for HmIP-Wired multi switches)

XXXX_TRANSMITTER (read only)
XXXX_VIRTUAL_RECEIVER (read/write)
XXXX_VIRTUAL_RECEIVER (read/write)
XXXX_VIRTUAL_RECEIVER (read/write)

Device detection / definition (1)

  • Use HMCCUDEV
  • Set statedatapoint to channel with role XXXX_TRANSMITTER
  • Set controldatapoint to first channel with role XXXX_VIRTUAL_RECEIVER

Device detection / definition (2)

  • Use HMCCUCHN
  • Set statedatapoint and controldatapoint to first channel with role XXXX_VIRTUAL_RECEIVER

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.