FHEM Forum

FHEM - Hausautomations-Systeme => Homematic => Thema gestartet von: Andi79 am 26 Februar 2024, 10:20:20

Titel: Readings von hmip-wkp keypad
Beitrag von: Andi79 am 26 Februar 2024, 10:20:20
Hat jemand ein hmip-wkp keypad?
Ich kapiere es nicht richtig, wie kann ich zwischen lock/unlock unterscheiden?
Ich bekomme
2024-02-25 10:48:35 HMCCUDEV keypad activity: alive
2024-02-25 10:48:35 HMCCUDEV keypad 0.UNREACH: alive
2024-02-25 10:48:35 HMCCUDEV keypad rssidevice: -75
2024-02-25 10:48:35 HMCCUDEV keypad 0.RSSI_DEVICE: -75
2024-02-25 10:48:35 HMCCUDEV keypad 0.CONFIG_PENDING: false
2024-02-25 10:48:35 HMCCUDEV keypad devstate: ok
2024-02-25 10:48:35 HMCCUDEV keypad hmstate: KNOWN_CODE_ID_RECEIVED
2024-02-25 10:48:38 HMCCUDEV keypad sabotage: false
2024-02-25 10:48:38 HMCCUDEV keypad 0.SABOTAGE: false
2024-02-25 10:48:38 HMCCUDEV keypad 0.BLOCKED_TEMPORARY: false
2024-02-25 10:48:38 HMCCUDEV keypad 0.USER_AUTHORIZATION_04: true
2024-02-25 10:48:38 HMCCUDEV keypad KNOWN_CODE_ID_RECEIVED
2024-02-25 10:48:38 HMCCUDEV keypad 0.CODE_STATE: KNOWN_CODE_ID_RECEIVED
2024-02-25 10:48:38 HMCCUDEV keypad 0.SABOTAGE_STICKY: false
2024-02-25 10:48:38 HMCCUDEV keypad rssidevice: -74
2024-02-25 10:48:38 HMCCUDEV keypad 0.RSSI_DEVICE: -74
2024-02-25 10:48:38 HMCCUDEV keypad 0.USER_AUTHORIZATION_08: true
2024-02-25 10:48:38 HMCCUDEV keypad 0.USER_AUTHORIZATION_07: true
2024-02-25 10:48:38 HMCCUDEV keypad battery: ok
2024-02-25 10:48:38 HMCCUDEV keypad 0.LOW_BAT: ok
2024-02-25 10:48:38 HMCCUDEV keypad 0.CONFIG_PENDING: false
2024-02-25 10:48:38 HMCCUDEV keypad 0.ERROR_CODE: 0
2024-02-25 10:48:38 HMCCUDEV keypad 0.OPERATING_VOLTAGE_STATUS: NORMAL
2024-02-25 10:48:38 HMCCUDEV keypad 0.USER_AUTHORIZATION_02: true
2024-02-25 10:48:38 HMCCUDEV keypad 0.DUTY_CYCLE: false
2024-02-25 10:48:38 HMCCUDEV keypad 0.CODE_ID: 1
2024-02-25 10:48:38 HMCCUDEV keypad voltage: 2.6
2024-02-25 10:48:38 HMCCUDEV keypad 0.OPERATING_VOLTAGE: 2.6
2024-02-25 10:48:38 HMCCUDEV keypad 0.BLOCKED_PERMANENT: false
2024-02-25 10:48:38 HMCCUDEV keypad activity: alive
2024-02-25 10:48:38 HMCCUDEV keypad 0.UNREACH: alive
2024-02-25 10:48:38 HMCCUDEV keypad 0.USER_AUTHORIZATION_03: true
2024-02-25 10:48:38 HMCCUDEV keypad 0.USER_AUTHORIZATION_01: true
2024-02-25 10:48:38 HMCCUDEV keypad 0.USER_AUTHORIZATION_05: true
2024-02-25 10:48:38 HMCCUDEV keypad 0.USER_AUTHORIZATION_06: true
2024-02-25 10:48:38 HMCCUDEV keypad devstate: ok
2024-02-25 10:48:38 HMCCUDEV keypad hmstate: KNOWN_CODE_ID_RECEIVED.

Allerdings sowohl für lock als auch für unlock.

424976892_10233166984945037_6041123734593743961_n.jpg

Was auch cool wäre ist wenn man den Annäherungssensor irgendwie per reading abgreifen könnte oder die LED nutzen, gibt es für so was ne custom firmware?
Titel: Aw: Readings von hmip-wkp keypad
Beitrag von: zap am 27 Februar 2024, 13:23:53
Kannst Du mal ein get deviceinfo vom Device posten?
Titel: Aw: Readings von hmip-wkp keypad
Beitrag von: Andi79 am 27 Februar 2024, 18:25:52
DEV keypad 002EA0C98EEE8B interface=HmIP-RF type=HmIP-WKP
CHN 002EA0C98EEE8B:0 keypad:0
   0.BLOCKED_PERMANENT = false {b} [RE]
   0.BLOCKED_TEMPORARY = false {b} [RE]
   0.CLEAR_ERROR =  {i} [W]
   0.CODE_ID = 32 {i} [RE]
   0.CODE_STATE = 0 {i} [RE]
   0.CONFIG_PENDING = false {b} [RE]
   0.DUTY_CYCLE = false {b} [RE]
   0.ERROR_CODE = 2 {i} [RE]
   0.INSTALL_TEST = true {b} [RW]
   0.LOW_BAT = false {b} [RE]
   0.OPERATING_VOLTAGE = 2.700000 {f} [RE]
   0.OPERATING_VOLTAGE_STATUS = 0 {i} [RE]
   0.RSSI_DEVICE = -78 {i} [RE]
   0.RSSI_PEER = -79 {i} [RE]
   0.SABOTAGE = false {b} [RE]
   0.SABOTAGE_STICKY = true {b} [RE]
   0.UNREACH = false {b} [RE]
   0.UPDATE_PENDING = false {b} [RE]
   0.USER_AUTHORIZATION_01 = true {b} [RE]
   0.USER_AUTHORIZATION_02 = true {b} [RE]
   0.USER_AUTHORIZATION_03 = true {b} [RE]
   0.USER_AUTHORIZATION_04 = true {b} [RE]
   0.USER_AUTHORIZATION_05 = true {b} [RE]
   0.USER_AUTHORIZATION_06 = true {b} [RE]
   0.USER_AUTHORIZATION_07 = true {b} [RE]
   0.USER_AUTHORIZATION_08 = true {b} [RE]
CHN 002EA0C98EEE8B:1 keypad_1
   1.ACCESS_AUTHORIZATION =  {i} [W]
   1.PRESS_LOCK =  {b} [E]
CHN 002EA0C98EEE8B:2 HmIP-WKP 002EA0C98EEE8B:2
   2.ACCESS_AUTHORIZATION =  {i} [W]
   2.PRESS_UNLOCK =  {b} [E]
CHN 002EA0C98EEE8B:3 HmIP-WKP 002EA0C98EEE8B:3
   3.ACCESS_AUTHORIZATION =  {i} [W]
   3.PRESS_LOCK =  {b} [E]
CHN 002EA0C98EEE8B:4 HmIP-WKP 002EA0C98EEE8B:4
   4.ACCESS_AUTHORIZATION =  {i} [W]
   4.PRESS_UNLOCK =  {b} [E]
CHN 002EA0C98EEE8B:5 HmIP-WKP 002EA0C98EEE8B:5
   5.ACCESS_AUTHORIZATION =  {i} [W]
   5.PRESS_LOCK =  {b} [E]
CHN 002EA0C98EEE8B:6 HmIP-WKP 002EA0C98EEE8B:6
   6.ACCESS_AUTHORIZATION =  {i} [W]
   6.PRESS_UNLOCK =  {b} [E]
CHN 002EA0C98EEE8B:7 HmIP-WKP 002EA0C98EEE8B:7
   7.ACCESS_AUTHORIZATION =  {i} [W]
   7.PRESS_LOCK =  {b} [E]
CHN 002EA0C98EEE8B:8 HmIP-WKP 002EA0C98EEE8B:8
   8.ACCESS_AUTHORIZATION =  {i} [W]
   8.PRESS_UNLOCK =  {b} [E]
CHN 002EA0C98EEE8B:9 HmIP-WKP 002EA0C98EEE8B:9
   9.ACCESS_AUTHORIZATION =  {i} [W]
   9.PRESS_LOCK =  {b} [E]
CHN 002EA0C98EEE8B:10 HmIP-WKP 002EA0C98EEE8B:10
   10.ACCESS_AUTHORIZATION =  {i} [W]
   10.PRESS_UNLOCK =  {b} [E]
CHN 002EA0C98EEE8B:11 HmIP-WKP 002EA0C98EEE8B:11
   11.ACCESS_AUTHORIZATION =  {i} [W]
   11.PRESS_LOCK =  {b} [E]
CHN 002EA0C98EEE8B:12 HmIP-WKP 002EA0C98EEE8B:12
   12.ACCESS_AUTHORIZATION =  {i} [W]
   12.PRESS_UNLOCK =  {b} [E]
CHN 002EA0C98EEE8B:13 HmIP-WKP 002EA0C98EEE8B:13
   13.ACCESS_AUTHORIZATION =  {i} [W]
   13.PRESS_LOCK =  {b} [E]
CHN 002EA0C98EEE8B:14 HmIP-WKP 002EA0C98EEE8B:14
   14.ACCESS_AUTHORIZATION =  {i} [W]
   14.PRESS_UNLOCK =  {b} [E]
CHN 002EA0C98EEE8B:15 HmIP-WKP 002EA0C98EEE8B:15
   15.ACCESS_AUTHORIZATION =  {i} [W]
   15.PRESS_LOCK =  {b} [E]
CHN 002EA0C98EEE8B:16 HmIP-WKP 002EA0C98EEE8B:16
   16.ACCESS_AUTHORIZATION =  {i} [W]
   16.PRESS_UNLOCK =  {b} [E]
CHN 002EA0C98EEE8B:18 HmIP-WKP 002EA0C98EEE8B:18
   18.COMBINED_PARAMETER =  {s} [W]
   18.WEEK_PROGRAM_CHANNEL_LOCKS = 255 {i} [RE]
   18.WEEK_PROGRAM_TARGET_CHANNEL_LOCK =  {i} [W]
   18.WEEK_PROGRAM_TARGET_CHANNEL_LOCKS =  {i} [W]


Device detection:
No state datapoint detected
No control datapoint detected

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

Current state datapoint = 0.CODE_STATE

Device description

Device 002EA0C98EEE8B keypad [HmIP-WKP]
  AES_ACTIVE: 1
  AVAILABLE_FIRMWARE: 0.0.0
  CHILDREN: 002EA0C98EEE8B:0,002EA0C98EEE8B:1,002EA0C98EEE8B:2,002EA0C98EEE8B:3,002EA0C98EEE8B:4,002EA0C98EEE8B:5,002EA0C98EEE8B:6,002EA0C98EEE8B:7,002EA0C98EEE8B:8,002EA0C98EEE8B:9,002EA0C98EEE8B:10,002EA0C98EEE8B:11,002EA0C98EEE8B:12,002EA0C98EEE8B:13,002EA0C98EEE8B:14,002EA0C98EEE8B:15,002EA0C98EEE8B:16,002EA0C98EEE8B:17,002EA0C98EEE8B:18
  DIRECTION: NONE
  FIRMWARE: 1.0.12
  FIRMWARE_UPDATE_STATE: UP_TO_DATE
  FLAGS: Visible
  PARAMSETS: MASTER,SERVICE
  RF_ADDRESS: 11511358
  ROAMING: 0
  RX_MODE: CONFIG
  SUBTYPE: WKP
  UPDATABLE: 1
Channel 002EA0C98EEE8B:0 keypad:0 [MAINTENANCE]
  AES_ACTIVE: 1
  DIRECTION: NONE
  FLAGS: Visible
  PARAMSETS: MASTER,VALUES,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:1 keypad_1 [ACCESS_TRANSCEIVER]
  AES_ACTIVE: 1
  DIRECTION: SENDER
  FLAGS: Visible
  LINK_SOURCE_ROLES: REMOTE_CONTROL
  PARAMSETS: MASTER,VALUES,LINK,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:2 HmIP-WKP 002EA0C98EEE8B:2 [ACCESS_TRANSCEIVER]
  AES_ACTIVE: 1
  DIRECTION: SENDER
  FLAGS: Visible
  LINK_SOURCE_ROLES: REMOTE_CONTROL
  PARAMSETS: MASTER,VALUES,LINK,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:3 HmIP-WKP 002EA0C98EEE8B:3 [ACCESS_TRANSCEIVER]
  AES_ACTIVE: 1
  DIRECTION: SENDER
  FLAGS: Visible
  LINK_SOURCE_ROLES: REMOTE_CONTROL
  PARAMSETS: MASTER,VALUES,LINK,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:4 HmIP-WKP 002EA0C98EEE8B:4 [ACCESS_TRANSCEIVER]
  AES_ACTIVE: 1
  DIRECTION: SENDER
  FLAGS: Visible
  LINK_SOURCE_ROLES: REMOTE_CONTROL
  PARAMSETS: MASTER,VALUES,LINK,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:5 HmIP-WKP 002EA0C98EEE8B:5 [ACCESS_TRANSCEIVER]
  AES_ACTIVE: 1
  DIRECTION: SENDER
  FLAGS: Visible
  LINK_SOURCE_ROLES: REMOTE_CONTROL
  PARAMSETS: MASTER,VALUES,LINK,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:6 HmIP-WKP 002EA0C98EEE8B:6 [ACCESS_TRANSCEIVER]
  AES_ACTIVE: 1
  DIRECTION: SENDER
  FLAGS: Visible
  LINK_SOURCE_ROLES: REMOTE_CONTROL
  PARAMSETS: MASTER,VALUES,LINK,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:7 HmIP-WKP 002EA0C98EEE8B:7 [ACCESS_TRANSCEIVER]
  AES_ACTIVE: 1
  DIRECTION: SENDER
  FLAGS: Visible
  LINK_SOURCE_ROLES: REMOTE_CONTROL
  PARAMSETS: MASTER,VALUES,LINK,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:8 HmIP-WKP 002EA0C98EEE8B:8 [ACCESS_TRANSCEIVER]
  AES_ACTIVE: 1
  DIRECTION: SENDER
  FLAGS: Visible
  LINK_SOURCE_ROLES: REMOTE_CONTROL
  PARAMSETS: MASTER,VALUES,LINK,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:9 HmIP-WKP 002EA0C98EEE8B:9 [ACCESS_TRANSCEIVER]
  AES_ACTIVE: 1
  DIRECTION: SENDER
  FLAGS: Visible
  LINK_SOURCE_ROLES: REMOTE_CONTROL
  PARAMSETS: MASTER,VALUES,LINK,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:10 HmIP-WKP 002EA0C98EEE8B:10 [ACCESS_TRANSCEIVER]
  AES_ACTIVE: 1
  DIRECTION: SENDER
  FLAGS: Visible
  LINK_SOURCE_ROLES: REMOTE_CONTROL
  PARAMSETS: MASTER,VALUES,LINK,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:11 HmIP-WKP 002EA0C98EEE8B:11 [ACCESS_TRANSCEIVER]
  AES_ACTIVE: 1
  DIRECTION: SENDER
  FLAGS: Visible
  LINK_SOURCE_ROLES: REMOTE_CONTROL
  PARAMSETS: MASTER,VALUES,LINK,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:12 HmIP-WKP 002EA0C98EEE8B:12 [ACCESS_TRANSCEIVER]
  AES_ACTIVE: 1
  DIRECTION: SENDER
  FLAGS: Visible
  LINK_SOURCE_ROLES: REMOTE_CONTROL
  PARAMSETS: MASTER,VALUES,LINK,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:13 HmIP-WKP 002EA0C98EEE8B:13 [ACCESS_TRANSCEIVER]
  AES_ACTIVE: 1
  DIRECTION: SENDER
  FLAGS: Visible
  LINK_SOURCE_ROLES: REMOTE_CONTROL
  PARAMSETS: MASTER,VALUES,LINK,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:14 HmIP-WKP 002EA0C98EEE8B:14 [ACCESS_TRANSCEIVER]
  AES_ACTIVE: 1
  DIRECTION: SENDER
  FLAGS: Visible
  LINK_SOURCE_ROLES: REMOTE_CONTROL
  PARAMSETS: MASTER,VALUES,LINK,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:15 HmIP-WKP 002EA0C98EEE8B:15 [ACCESS_TRANSCEIVER]
  AES_ACTIVE: 1
  DIRECTION: SENDER
  FLAGS: Visible
  LINK_SOURCE_ROLES: REMOTE_CONTROL
  PARAMSETS: MASTER,VALUES,LINK,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:16 HmIP-WKP 002EA0C98EEE8B:16 [ACCESS_TRANSCEIVER]
  AES_ACTIVE: 1
  DIRECTION: SENDER
  FLAGS: Visible
  LINK_SOURCE_ROLES: REMOTE_CONTROL
  PARAMSETS: MASTER,VALUES,LINK,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:17 HmIP-WKP 002EA0C98EEE8B:17 [ALARM_COND_SWITCH_TRANSMITTER]
  AES_ACTIVE: 1
  DIRECTION: NONE
  FLAGS:
  PARAMSETS: MASTER,VALUES,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1
Channel 002EA0C98EEE8B:18 HmIP-WKP 002EA0C98EEE8B:18 [SWITCH_WEEK_PROFILE]
  AES_ACTIVE: 1
  DIRECTION: NONE
  FLAGS: Visible
  PARAMSETS: MASTER,VALUES,SERVICE
  PARENT: 002EA0C98EEE8B
  PARENT_TYPE: HmIP-WKP
  RF_ADDRESS: 0
  ROAMING: 0
  RX_MODE:
  UPDATABLE: 1

Defaults

Titel: Aw: Readings von hmip-wkp keypad
Beitrag von: zap am 28 Februar 2024, 17:47:21
Du wirst vermutlich wie bei fast allen Homematic-Geräten, die PRESS-Events schicken sollen, in der CCU ein Dummy-Programm erstellen müssen, das die entsprechenden Kanäle (also die Tastendrücke) abfragt. Das Programm muss eigentlich nichts machen, ich würde aber einfach bei einem Tastendruck eine Systemvariable setzen lassen (als Aktion).

Sobald dieses Programm erstellt ist, sollten in FHEM die Readings PRESS_LOCK, PRESS_UNLOCK ankommen.

Wenn Du hier im Forum nach "CCU Dummy Programm" suchst, müsste es ein paar Ergebnisse geben.