HMCCU Beispiel Geräte-Definitionen

JuergenR · 21 April 2020, 19:09:24

Ja, es ist mein einziges BidCos-Gerät auf der CCU3. Sollte auch nur ein Test sein, bevor ich HmIP-Geräte anschaffe.

zap · 21 April 2020, 22:30:49

Und läuft der RPC Server? Welche Meldungen werden beim Start des RPC Servers ins Log geschrieben?

JuergenR · 22 April 2020, 07:31:51

Ja, der läuft:


HMCCU: [CCU3 : 22745] Initialized version 4.3.024
2020.04.22 07:21:10 1: HMCCU: [CCU3 : 22745] HMCCU: Initializing device
2020.04.22 07:21:10 1: HMCCU: [CCU3 : 22745] HMCCU: Read 3 devices with 104 channels from CCU 192.168.178.30
2020.04.22 07:21:10 1: HMCCU: [CCU3 : 22745] HMCCU: Read 4 interfaces from CCU 192.168.178.30
2020.04.22 07:21:10 1: HMCCU: [CCU3 : 22745] HMCCU: Read 0 programs from CCU 192.168.178.30
2020.04.22 07:21:10 1: HMCCU: [CCU3 : 22745] HMCCU: Read 0 virtual groups from CCU 192.168.178.30
2020.04.22 07:21:10 1: HMCCURPCPROC: [d_rpc178030BidCos_RF : 22745] Initialized version 1.9.001 for interface BidCos-RF with I/O device CCU3
2020.04.22 07:21:10 1: HMCCURPCPROC: [d_rpc178030HmIP_RF : 22745] Initialized version 1.9.001 for interface HmIP-RF with I/O device CCU3
...
2020.04.22 07:21:38 2: HMCCU: [CCU3 : 22745] Get RPC device for interface BidCos-RF
2020.04.22 07:21:38 2: HMCCU: [CCU3 : 22745] Get RPC device for interface HmIP-RF
2020.04.22 07:21:38 2: HMCCURPCPROC: [d_rpc178030BidCos_RF : 22745] RPC server process started for interface BidCos-RF with PID=22834
2020.04.22 07:21:38 2: HMCCURPCPROC: [d_rpc178030BidCos_RF : 22834] Initializing RPC server CB2001178111178030 for interface BidCos-RF
2020.04.22 07:21:38 1: HMCCURPCPROC: [d_rpc178030BidCos_RF : 22745] RPC server starting
2020.04.22 07:21:38 2: HMCCURPCPROC: [d_rpc178030HmIP_RF : 22745] RPC server process started for interface HmIP-RF with PID=22835
2020.04.22 07:21:38 2: HMCCURPCPROC: [d_rpc178030HmIP_RF : 22835] Initializing RPC server CB2010178111178030 for interface HmIP-RF
2020.04.22 07:21:38 1: HMCCURPCPROC: [d_rpc178030HmIP_RF : 22745] RPC server starting
2020.04.22 07:21:39 2: HMCCURPCPROC: [d_rpc178030BidCos_RF : 22834] Callback server CB2001178111178030 created. Listening on port 7411
2020.04.22 07:21:39 2: HMCCURPCPROC: [d_rpc178030BidCos_RF : 22834] CB2001178111178030 accepting connections. PID=22834
2020.04.22 07:21:39 2: HMCCURPCPROC: [d_rpc178030HmIP_RF : 22835] Callback server CB2010178111178030 created. Listening on port 7420
2020.04.22 07:21:39 2: HMCCURPCPROC: [d_rpc178030HmIP_RF : 22835] CB2010178111178030 accepting connections. PID=22835
2020.04.22 07:21:40 2: HMCCURPCPROC: [d_rpc178030BidCos_RF : 22745] RPC server CB2001178111178030 enters server loop
2020.04.22 07:21:40 2: HMCCURPCPROC: [d_rpc178030BidCos_RF : 22745] Registering callback http://192.168.178.30:7411/fh2001 of type A with ID CB2001178111178030 at http://192.168.178.30:2001
2020.04.22 07:21:40 1: HMCCURPCPROC: [d_rpc178030BidCos_RF : 22745] RPC server CB2001178111178030 running
2020.04.22 07:21:40 1: HMCCURPCPROC: [d_rpc178030BidCos_RF : 22745] Scheduled CCU ping every 300 seconds
2020.04.22 07:21:40 2: HMCCURPCPROC: [d_rpc178030HmIP_RF : 22745] RPC server CB2010178111178030 enters server loop
2020.04.22 07:21:41 2: HMCCURPCPROC: [d_rpc178030HmIP_RF : 22745] Registering callback http://192.168.178.30:7420/fh2010 of type A with ID CB2010178111178030 at http://192.168.178.30:2010
2020.04.22 07:21:41 1: HMCCURPCPROC: [d_rpc178030HmIP_RF : 22745] RPC server CB2010178111178030 running
2020.04.22 07:21:41 1: HMCCU: [CCU3 : 22745] All RPC servers running
2020.04.22 07:21:41 2: HMCCU: [CCU3 : 22745] Updating 1 of 1 client devices matching devexp=.* filter=ccudevstate=active,ccuif=BidCos-RF|HmIP-RF
2020.04.22 07:21:41 2: HMCCU: [CCU3 : 22745] Update success=1 failed=0

JuergenR · 22 April 2020, 15:04:21

Nun ist ab heute noch ein HMIP-SWDO dazugekommen.
Dieser verhält sich im FHEM genau so:
Er liefert über HMCCU nur per Hand mit get devstate Readings, sonst nicht.

Code Auswählen


2020.04.22 15:00:33 2: HMCCURPCPROC: [d_rpc178030HmIP_RF : 10334] Callback server CB2010178111178030 created. Listening on port 7420
2020.04.22 15:00:33 2: HMCCURPCPROC: [d_rpc178030HmIP_RF : 10334] CB2010178111178030 accepting connections. PID=10334
2020.04.22 15:00:33 1: HMCCURPCPROC: [d_rpc178030BidCos_RF : 6627] RPC server CB2001178111178030 running
2020.04.22 15:00:33 1: HMCCURPCPROC: [d_rpc178030BidCos_RF : 6627] Scheduled CCU ping every 300 seconds
2020.04.22 15:00:33 2: HMCCURPCPROC: [d_rpc178030HmIP_RF : 6627] RPC server CB2010178111178030 enters server loop
2020.04.22 15:00:33 2: HMCCURPCPROC: [d_rpc178030HmIP_RF : 6627] Registering callback http://192.168.178.30:7420/fh2010 of type A with ID CB2010178111178030 at http://192.168.178.30:2010
2020.04.22 15:00:33 1: HMCCURPCPROC: [d_rpc178030HmIP_RF : 6627] RPC server CB2010178111178030 running
2020.04.22 15:00:33 1: HMCCU: [CCU3 : 6627] All RPC servers running
2020.04.22 15:00:34 2: HMCCU: [CCU3 : 6627] Updating 2 of 2 client devices matching devexp=.* filter=ccudevstate=active,ccuif=BidCos-RF|HmIP-RF
2020.04.22 15:00:34 2: HMCCU: [CCU3 : 6627] Update success=2 failed=0

Vielleicht sollte ich noch erwähnen, das die CCU3 ein ELV Charly ist.

zap · 22 April 2020, 15:46:32

Mach mal morgen das Update für 88_HMCCU.pm. Vorher würde ich die RPC Server stoppen.

JuergenR · 23 April 2020, 08:30:27

Nach dem Update heute morgen ist das Verhalten unverändert.

Borkk · 25 April 2020, 16:04:10

Hallo Zusammen,

ich habe da mal eine Frage bei der ich bisher nicht fündig wurde. Ich habe meine schon viele Jahre alte Homematic Anbindung von HM-MOD-RPI-PCB (HMUARTGW) auf HMCCU via RPI-RF-MOD (Raspberrymatic) umgestellt. Der Grund war, das ich HmIP Geräte einbinden wollte und mich eben für HmIP öffnen wollte. Der Umstieg war bei über 40 HM Geräten zwar sehr aufwendig, hat aber gut funktioniert. Leider sind die Schaltzeiten jetzt deutlich länger aber evtl. kann ich da noch was optimieren.

Meine eigentliche Frage dreht sich um das 16fach LED Modul HM-OU-LED16. Mit der alten Anbindung konnte ich mit dem Befehl

Code Auswählen

"set 16_LED ilum 1 3" oder "set 16_LED ilum 2 0"

das Panel in der Nacht oder bei Abwesenheit aus- bzw. einschalten. Dabei hat sich das Panel die Zustände der einzelnen LEDs behalten. Ich finde einen vergleichbaren Befehl weder für einen HMCCUCHN Channel noch für einen HMCCUDEV Device.

kjmEjfu · 25 April 2020, 19:48:02

Vielleicht bin ich ja etwas pinzig, aber wir sind hier im Thread "HMCCU Beispiel Geräte-Definitionen" und in letzter Zeit sind hier dauernd HMCCU-Probleme ...
Ist etwas nervig, wenn man eine Notification auf den Thread hat, aber dadurch immer mehr false positives.

Borkk · 25 April 2020, 23:45:37

Zitat von: kjmEjfu am 25 April 2020, 19:48:02
Vielleicht bin ich ja etwas pinzig, aber wir sind hier im Thread "HMCCU Beispiel Geräte-Definitionen" und in letzter Zeit sind hier dauernd HMCCU-Probleme ...
Ist etwas nervig, wenn man eine Notification auf den Thread hat, aber dadurch immer mehr false positives.

Meine Frage muss ja kein Problem sein, sicher gibt es eine einfache Antwort. Ich hatte in diesem Thread viele sehr nützliche Hinweise gefunden ...

maclovlin · 25 Mai 2020, 22:46:44

Zitat von: gloob am 06 März 2020, 08:49:29
Hat jemand zufällig ein Beispiel für eine Integration von HB-UNI-RGB-LED-CTRL?

Hi, ich habe es so umgesetzt. Die Userreadings brauchst Du nicht mit zu berücksichtigen, die sind für meine HM FB Programme.
Falls es jemand optimieren kann, nur her damit

Code Auswählen


defmod HM_UNI_RGB_LED_CTRL HMCCUDEV TV_LED
attr HM_UNI_RGB_LED_CTRL IODev HOMECCU
attr HM_UNI_RGB_LED_CTRL alias TV Licht
attr HM_UNI_RGB_LED_CTRL ccureadingfilter (STATE|COLOR|LEVEL|PROGRAM|ACT)
attr HM_UNI_RGB_LED_CTRL cmdIcon on:general_an off:general_aus
attr HM_UNI_RGB_LED_CTRL event-on-update-reading .*
attr HM_UNI_RGB_LED_CTRL eventMap /datapoint 1.LEVEL 0:off/datapoint 1.LEVEL 1:on/datapoint 2.COLOR:2.COLOR:colorpicker,HUE,0,1,200/datapoint 3.PROGRAM:3.PROGRAM:select,0,1,2,3,4,5,6
attr HM_UNI_RGB_LED_CTRL group Licht
attr HM_UNI_RGB_LED_CTRL hmstatevals true):unreachable;;^LOW_?BAT!(1|true):warn_battery'
attr HM_UNI_RGB_LED_CTRL icon hue_filled_lightstrip
attr HM_UNI_RGB_LED_CTRL room HM,Wohnzimmer
attr HM_UNI_RGB_LED_CTRL statedatapoint 1.LEVEL
attr HM_UNI_RGB_LED_CTRL substexcl control
attr HM_UNI_RGB_LED_CTRL substitute LEVEL!#0-0:off,#0.1-1:on;;
attr HM_UNI_RGB_LED_CTRL userReadings cColor cPrg
attr HM_UNI_RGB_LED_CTRL webCmd control:on:off:2.COLOR:3.PROGRAM
attr HM_UNI_RGB_LED_CTRL widgetOverride control:slider,0,0.1,1,1

setstate HM_UNI_RGB_LED_CTRL on
setstate HM_UNI_RGB_LED_CTRL 2020-05-25 22:31:57 1.LEVEL on
setstate HM_UNI_RGB_LED_CTRL 2020-05-25 06:39:42 2.COLOR 180
setstate HM_UNI_RGB_LED_CTRL 2020-05-23 11:37:26 3.ACT_BRIGHTNESS 0
setstate HM_UNI_RGB_LED_CTRL 2020-05-23 11:37:26 3.ACT_MAX_BOARDER 0
setstate HM_UNI_RGB_LED_CTRL 2020-05-23 11:37:26 3.ACT_MIN_BOARDER 0
setstate HM_UNI_RGB_LED_CTRL 2020-05-25 22:33:06 3.PROGRAM 1
setstate HM_UNI_RGB_LED_CTRL 2020-05-25 22:32:56 activity alive
setstate HM_UNI_RGB_LED_CTRL 2020-05-23 11:37:26 battery ok
setstate HM_UNI_RGB_LED_CTRL 2020-05-25 22:33:01 cColor 0
setstate HM_UNI_RGB_LED_CTRL 2020-05-25 22:33:06 cPrg 1
setstate HM_UNI_RGB_LED_CTRL 2020-05-25 22:33:01 color 0
setstate HM_UNI_RGB_LED_CTRL 2020-05-25 22:31:57 control 1.000000
setstate HM_UNI_RGB_LED_CTRL 2020-05-25 22:33:06 hmstate on
setstate HM_UNI_RGB_LED_CTRL 2020-05-25 22:31:57 state on

Jamo · 26 Juni 2020, 21:53:43

Ich habe einen HmIP-PCBS2, das ist ein 2-Kanal Schalter, somit brauche ich 2 statedatapoints.
Die entsprechenden Schaltkanäle sind "4.STATE"und "8.STATE"

Allerdings erlaubt das attribut statedatapoint nur die Definition von einem Kanal.

Weiss jemand wie ich den 2-ten Kanal in den Statedatapoint bekomme? Ich mächte ja beide Kanäle an- und ausschalten

Hier das list und die datapoints:

Code Auswählen

CHN 00199A1234A123:0 HmIP-PCBS2 00199A1234A123:0
  DPT {f} HmIP-RF.00199A1234A123:0.ACTUAL_TEMPERATURE = 28.000000 [RE]
  DPT {b} HmIP-RF.00199A1234A123:0.CONFIG_PENDING = false [RE]
  DPT {b} HmIP-RF.00199A1234A123:0.DUTY_CYCLE = false [RE]
  DPT {n} HmIP-RF.00199A1234A123:0.ERROR_CODE = 0 [RE]
  DPT {b} HmIP-RF.00199A1234A123:0.ERROR_OVERHEAT = false [RE]
  DPT {b} HmIP-RF.00199A1234A123:0.INSTALL_TEST = true [RW]
  DPT {f} HmIP-RF.00199A1234A123:0.OPERATING_VOLTAGE = 0.000000 [RE]
  DPT {i} HmIP-RF.00199A1234A123:0.OPERATING_VOLTAGE_STATUS = 0 [RE]
  DPT {n} HmIP-RF.00199A1234A123:0.RSSI_DEVICE = 194 [RE]
  DPT {n} HmIP-RF.00199A1234A123:0.RSSI_PEER = 196 [RE]
  DPT {b} HmIP-RF.00199A1234A123:0.UNREACH = false [RE]
  DPT {b} HmIP-RF.00199A1234A123:0.UPDATE_PENDING = false [RE]
CHN 00199A1234A123:1 HmIP-PCBS2 00199A1234A123:1
  DPT {b} HmIP-RF.00199A1234A123:1.PRESS_LONG =  [E]
  DPT {b} HmIP-RF.00199A1234A123:1.PRESS_SHORT =  [E]
CHN 00199A1234A123:2 HmIP-PCBS2 00199A1234A123:2
  DPT {b} HmIP-RF.00199A1234A123:2.PRESS_LONG =  [E]
  DPT {b} HmIP-RF.00199A1234A123:2.PRESS_SHORT =  [E]
CHN 00199A1234A123:3 HmIP-PCBS2 00199A1234A123:3
  DPT {i} HmIP-RF.00199A1234A123:3.PROCESS = 0 [RE]
  DPT {i} HmIP-RF.00199A1234A123:3.SECTION = 2 [RE]
  DPT {i} HmIP-RF.00199A1234A123:3.SECTION_STATUS = 0 [RE]
  DPT {b} HmIP-RF.00199A1234A123:3.STATE = true [RE]
CHN 00199A1234A123:4 HmIP-PCBS2 00199A1234A123:4
  DPT {s} HmIP-RF.00199A1234A123:4.COMBINED_PARAMETER =  [W]
  DPT {f} HmIP-RF.00199A1234A123:4.ON_TIME =  [W]
  DPT {i} HmIP-RF.00199A1234A123:4.PROCESS = 0 [RE]
  DPT {i} HmIP-RF.00199A1234A123:4.SECTION = 2 [RE]
  DPT {i} HmIP-RF.00199A1234A123:4.SECTION_STATUS = 0 [RE]
  DPT {b} HmIP-RF.00199A1234A123:4.STATE = true [RWE]
CHN 00199A1234A123:5 HmIP-PCBS2 00199A1234A123:5
  DPT {s} HmIP-RF.00199A1234A123:5.COMBINED_PARAMETER =  [W]
  DPT {f} HmIP-RF.00199A1234A123:5.ON_TIME =  [W]
  DPT {i} HmIP-RF.00199A1234A123:5.PROCESS = 0 [RE]
  DPT {i} HmIP-RF.00199A1234A123:5.SECTION = 0 [RE]
  DPT {i} HmIP-RF.00199A1234A123:5.SECTION_STATUS = 0 [RE]
  DPT {b} HmIP-RF.00199A1234A123:5.STATE = false [RWE]
CHN 00199A1234A123:6 HmIP-PCBS2 00199A1234A123:6
  DPT {s} HmIP-RF.00199A1234A123:6.COMBINED_PARAMETER =  [W]
  DPT {f} HmIP-RF.00199A1234A123:6.ON_TIME =  [W]
  DPT {i} HmIP-RF.00199A1234A123:6.PROCESS = 0 [RE]
  DPT {i} HmIP-RF.00199A1234A123:6.SECTION = 0 [RE]
  DPT {i} HmIP-RF.00199A1234A123:6.SECTION_STATUS = 0 [RE]
  DPT {b} HmIP-RF.00199A1234A123:6.STATE = false [RWE]
CHN 00199A1234A123:7 HmIP-PCBS2 00199A1234A123:7
  DPT {i} HmIP-RF.00199A1234A123:7.PROCESS = 0 [RE]
  DPT {i} HmIP-RF.00199A1234A123:7.SECTION = 0 [RE]
  DPT {i} HmIP-RF.00199A1234A123:7.SECTION_STATUS = 0 [RE]
  DPT {b} HmIP-RF.00199A1234A123:7.STATE = false [RE]
CHN 00199A1234A123:8 HmIP-PCBS2 00199A1234A123:8
  DPT {s} HmIP-RF.00199A1234A123:8.COMBINED_PARAMETER =  [W]
  DPT {f} HmIP-RF.00199A1234A123:8.ON_TIME =  [W]
  DPT {i} HmIP-RF.00199A1234A123:8.PROCESS = 0 [RE]
  DPT {i} HmIP-RF.00199A1234A123:8.SECTION = 0 [RE]
  DPT {i} HmIP-RF.00199A1234A123:8.SECTION_STATUS = 0 [RE]
  DPT {b} HmIP-RF.00199A1234A123:8.STATE = false [RWE]
CHN 00199A1234A123:9 HmIP-PCBS2 00199A1234A123:9
  DPT {s} HmIP-RF.00199A1234A123:9.COMBINED_PARAMETER =  [W]
  DPT {f} HmIP-RF.00199A1234A123:9.ON_TIME =  [W]
  DPT {i} HmIP-RF.00199A1234A123:9.PROCESS = 0 [RE]
  DPT {i} HmIP-RF.00199A1234A123:9.SECTION = 0 [RE]
  DPT {i} HmIP-RF.00199A1234A123:9.SECTION_STATUS = 0 [RE]
  DPT {b} HmIP-RF.00199A1234A123:9.STATE = false [RWE]
CHN 00199A1234A123:10 HmIP-PCBS2 00199A1234A123:10
  DPT {s} HmIP-RF.00199A1234A123:10.COMBINED_PARAMETER =  [W]
  DPT {f} HmIP-RF.00199A1234A123:10.ON_TIME =  [W]
  DPT {i} HmIP-RF.00199A1234A123:10.PROCESS = 0 [RE]
  DPT {i} HmIP-RF.00199A1234A123:10.SECTION = 0 [RE]
  DPT {i} HmIP-RF.00199A1234A123:10.SECTION_STATUS = 0 [RE]
  DPT {b} HmIP-RF.00199A1234A123:10.STATE = false [RWE]
CHN 00199A1234A123:11 HmIP-PCBS2 00199A1234A123:11
  DPT {i} HmIP-RF.00199A1234A123:11.WEEK_PROGRAM_CHANNEL_LOCKS = 0 [RE]
  DPT {i} HmIP-RF.00199A1234A123:11.WEEK_PROGRAM_TARGET_CHANNEL_LOCK =  [W]
  DPT {i} HmIP-RF.00199A1234A123:11.WEEK_PROGRAM_TARGET_CHANNEL_LOCKS =  [W]

Code Auswählen

Internals:
   DEF        00199A1234A123 4 8
   FUUID      4e34203d-f33f-3256-f92f-d36cdeff2e504e4
   IODev      HMCCU3
   NAME       HMIP_PCBS2
   NR         3386
   STATE      1:on
2:off
   TYPE       HMCCUDEV
   ccuaddr    00199A1234A123
   ccudevstate active
   ccuif      HmIP-RF
   ccuname    HmIP-PCBS2 00199A1234A123
   ccutype    HmIP-PCBS2
   channels   12
   firmware   1.10.10
   statevals  devstate|on|off
   READINGS:
     2020-06-26 00:08:04   0.ACTUAL_TEMPERATURE 30.0
     2020-06-26 00:20:58   0.CONFIG_PENDING 0
     2020-06-26 00:20:58   0.DUTY_CYCLE    0
     2020-06-26 00:08:04   0.ERROR_CODE    0
     2020-06-26 00:08:04   0.ERROR_OVERHEAT 0
     2020-06-26 00:08:04   0.INSTALL_TEST  true
     2020-06-26 00:08:04   0.OPERATING_VOLTAGE 0.000000
     2020-06-26 00:08:04   0.OPERATING_VOLTAGE_STATUS 0
     2020-06-26 00:20:58   0.RSSI_DEVICE   -50
     2020-06-26 00:20:53   0.RSSI_PEER     -44
     2020-06-26 00:20:58   0.UNREACH       0
     2020-06-26 00:08:04   0.UPDATE_PENDING false
     2020-06-26 00:15:44   10.PROCESS      0
     2020-06-26 00:15:44   10.SECTION      0
     2020-06-26 00:15:44   10.SECTION_STATUS 0
     2020-06-26 21:39:06   10.STATE        0
     2020-06-26 00:08:04   11.WEEK_PROGRAM_CHANNEL_LOCKS 0
     2020-06-26 00:20:56   3.PROCESS       0
     2020-06-26 00:20:56   3.SECTION       2
     2020-06-26 00:20:56   3.SECTION_STATUS 0
     2020-06-26 21:46:55   3.STATE         1
     2020-06-26 00:20:56   4.PROCESS       0
     2020-06-26 00:20:56   4.SECTION       2
     2020-06-26 00:20:56   4.SECTION_STATUS 0
     2020-06-26 08:57:49   4.STATE         0
     2020-06-26 00:20:56   5.PROCESS       0
     2020-06-26 00:20:56   5.SECTION       0
     2020-06-26 00:20:56   5.SECTION_STATUS 0
     2020-06-26 21:46:55   5.STATE         0
     2020-06-26 00:20:57   6.PROCESS       0
     2020-06-26 00:20:57   6.SECTION       0
     2020-06-26 00:20:57   6.SECTION_STATUS 0
     2020-06-26 21:46:57   6.STATE         0
     2020-06-26 00:15:44   7.PROCESS       0
     2020-06-26 00:15:44   7.SECTION       0
     2020-06-26 00:15:44   7.SECTION_STATUS 0
     2020-06-26 21:39:06   7.STATE         0
     2020-06-26 00:15:44   8.PROCESS       0
     2020-06-26 00:15:44   8.SECTION       0
     2020-06-26 00:15:44   8.SECTION_STATUS 0
     2020-06-26 08:57:56   8.STATE         0
     2020-06-26 00:15:44   9.PROCESS       0
     2020-06-26 00:15:44   9.SECTION       0
     2020-06-26 00:15:44   9.SECTION_STATUS 0
     2020-06-26 21:39:06   9.STATE         0
     2020-06-26 21:46:57   control         on
     2020-06-26 21:46:57   hmstate         on
     2020-06-26 20:57:32   on1             off
     2020-06-26 20:57:32   on2             off
     2020-06-26 21:46:57   state           on
     2020-06-26 21:46:57   state1          on
     2020-06-26 21:39:07   state2          off
   hmccu:
     devspec    00199A1234A123
     dp:
       0.ACTUAL_TEMPERATURE:
         OVAL       28.000000
         VAL        28.000000
       0.CONFIG_PENDING:
         OVAL       0
         VAL        0
       0.DUTY_CYCLE:
         OVAL       0
         VAL        0
       0.ERROR_CODE:
         OVAL       0
         VAL        0
       0.ERROR_OVERHEAT:
         OVAL       false
         VAL        false
       0.INSTALL_TEST:
         OVAL       true
         VAL        true
       0.OPERATING_VOLTAGE:
         OVAL       0.000000
         VAL        0.000000
       0.OPERATING_VOLTAGE_STATUS:
         OVAL       0
         VAL        0
       0.RSSI_DEVICE:
         OVAL       -62
         VAL        -63
       0.RSSI_PEER:
         OVAL       -60
         VAL        -61
       0.UNREACH:
         OVAL       0
         VAL        0
       0.UPDATE_PENDING:
         OVAL       false
         VAL        false
       10.PROCESS:
         OVAL       0
         VAL        0
       10.SECTION:
         OVAL       0
         VAL        0
       10.SECTION_STATUS:
         OVAL       0
         VAL        0
       10.STATE:
         OSVAL      false
         OVAL       false
         SVAL       0
         VAL        0
       11.WEEK_PROGRAM_CHANNEL_LOCKS:
         OVAL       0
         VAL        0
       3.PROCESS:
         OVAL       0
         VAL        0
       3.SECTION:
         OVAL       2
         VAL        2
       3.SECTION_STATUS:
         OVAL       0
         VAL        0
       3.STATE:
         OSVAL      1
         OVAL       1
         SVAL       1
         VAL        1
       4.PROCESS:
         OVAL       0
         VAL        0
       4.SECTION:
         OVAL       2
         VAL        2
       4.SECTION_STATUS:
         OVAL       0
         VAL        0
       4.STATE:
         OSVAL      on
         OVAL       1
         SVAL       on
         VAL        1
       5.PROCESS:
         OVAL       0
         VAL        0
       5.SECTION:
         OVAL       0
         VAL        0
       5.SECTION_STATUS:
         OVAL       0
         VAL        0
       5.STATE:
         OSVAL      0
         OVAL       0
         SVAL       0
         VAL        0
       6.PROCESS:
         OVAL       0
         VAL        0
       6.SECTION:
         OVAL       0
         VAL        0
       6.SECTION_STATUS:
         OVAL       0
         VAL        0
       6.STATE:
         OSVAL      0
         OVAL       0
         SVAL       0
         VAL        0
       7.PROCESS:
         OVAL       0
         VAL        0
       7.SECTION:
         OVAL       0
         VAL        0
       7.SECTION_STATUS:
         OVAL       0
         VAL        0
       7.STATE:
         OSVAL      false
         OVAL       false
         SVAL       0
         VAL        0
       8.PROCESS:
         OVAL       0
         VAL        0
       8.SECTION:
         OVAL       0
         VAL        0
       8.SECTION_STATUS:
         OVAL       0
         VAL        0
       8.STATE:
         OSVAL      off
         OVAL       false
         SVAL       off
         VAL        0
       9.PROCESS:
         OVAL       0
         VAL        0
       9.SECTION:
         OVAL       0
         VAL        0
       9.SECTION_STATUS:
         OVAL       0
         VAL        0
       9.STATE:
         OSVAL      false
         OVAL       false
         SVAL       0
         VAL        0
Attributes:
   IODev      HMCCU3
   alexaName  Bekant
   alias      Bekant
   ccureadingfilter STATE
   ccureadingname 0.OPERATING_VOLTAGE:battery;4.STATE:state1;8.STATE:state2
   devStateIcon 1.on:ios-on-green:off 1.off:ios-off:on 2.on:ios-on-green:off 2.off:ios-off:on
   event-on-change-reading .*
   eventMap   /datapoint 4.STATE 1:state1 on/datapoint 4.STATE 0:state1 off/datapoint 8.STATE 1:state2 on/datapoint 8.STATE 0:state2 off/
   genericDeviceType switch
   group      SCHALTER
   room       HomeMaticIP,Schalter
   stateFormat 1:state1
2:state2
   statedatapoint 4.STATE
   statevals  on:1,off:0
   substitute 4.STATE!(0|false):off,(1|true):on;8.STATE!(0|false):off,(1|true):on

zap · 26 Juni 2020, 22:24:16

Ich würde 2 HMCCUCHN Devices definieren, für jeden Kanal eins.

Oder du verwendest den Befehl set datapoint zum Schalten, also z.B.

set xy datapoint 4.STATE 1

slor · 23 September 2020, 18:08:57

Hallo zusammen,
habe heute einen HM-Sen-DB-PCB (Klingelsensor) an der CCU angelernt.
Leider noch keine Beispiel Defenitionen dafür vorhanden.
Hat den zufällig jemand schon fertig definert?
Ich brauche in Fhem ja nur Klingel ja/nein, da müsste doch auch ein CCUCHAN auf Kanal 1 reichen?

Code Auswählen

   IODev      HMCCU
   NAME       EG_FL_DB
   NR         2389
   STATE      ???
   TYPE       HMCCUDEV
   ccuaddr    
   ccudevstate active
   ccuif      BidCos-RF
   ccuname    EG_FL_DB
   ccutype    HM-Sen-DB-PCB
   channels   2
   statevals  devstate
   READINGS:
     2020-09-23 16:39:03   0.AES_KEY       off
     2020-09-23 17:59:25   0.CONFIG_PENDING 0
     2020-09-23 16:39:03   0.DEVICE_IN_BOOTLOADER false
     2020-09-23 16:39:03   0.RSSI_DEVICE   1
     2020-09-23 16:39:03   0.RSSI_PEER     205
     2020-09-23 16:39:03   0.STICKY_UNREACH false
     2020-09-23 16:39:03   0.UPDATE_PENDING false
     2020-09-23 17:59:25   1.INSTALL_TEST  1
     2020-09-23 17:59:25   1.PRESS_SHORT   1
     2020-09-23 16:39:03   activity        alive
     2020-09-23 16:39:03   battery         ok

zap · 23 September 2020, 19:10:47

Mach mal bitte ein "get deviceinfo"

slor · 23 September 2020, 20:43:54

Code Auswählen

CHN MEQ0045230:0 EG_FL_DB:0
  DPT {b} BidCos-RF.MEQ0045230:0.UNREACH = false [RE]
  DPT {b} BidCos-RF.MEQ0045230:0.STICKY_UNREACH = false [RWE]
  DPT {b} BidCos-RF.MEQ0045230:0.CONFIG_PENDING = false [RE]
  DPT {b} BidCos-RF.MEQ0045230:0.LOWBAT = false [RE]
  DPT {n} BidCos-RF.MEQ0045230:0.RSSI_DEVICE = 1 [RE]
  DPT {n} BidCos-RF.MEQ0045230:0.RSSI_PEER = 205 [RE]
  DPT {b} BidCos-RF.MEQ0045230:0.DEVICE_IN_BOOTLOADER = false [RE]
  DPT {b} BidCos-RF.MEQ0045230:0.UPDATE_PENDING = false [RE]
  DPT {n} BidCos-RF.MEQ0045230:0.AES_KEY = 0 [R]
CHN MEQ0045230:1 EG_FL_DB:1
  DPT {b} BidCos-RF.MEQ0045230:1.PRESS_SHORT = false [WE]
  DPT {b} BidCos-RF.MEQ0045230:1.INSTALL_TEST = false [E]
  DPT {b} BidCos-RF.MEQ0045230:1.PRESS_CONT =  [E]