Ich benötige Hilfe beim aufsetzen eines BC-PB-2-WM

[nikoh]

Hey Leute,

Ich bin relativ neu was fhem angeht und habe dieses Forum noch nie genutzt. Deswegen weiss ich nicht ob ich grad an der richtigen Stelle frage.

Ich benutze einen Raspberry Pi 3 Model B V1.2 und ein HM-MOD-RPI-PCB HomeMatic Funkmodul welches ich unter befolgung von vielen Tutorials, guides und wiki einträgen in fhem eingebunden habe. Anbei ein Screenshot der Konfiguration.

Ich möchte nun einen Eco Taster anbinden. Da dieser aber über Max läuft muss ich meines Wissens das attribut rfmode auf MAX stellen. ich führe alse folgende befehle aus:

define CUL0 CUL /dev/ttyACM0@115200 0000  # die 115200 weicht ab von der im wiki beschriebenen zahl aber selbst mit 9600 funktioniert es auch nicht
attr CUL0 rfmode MAX
define cm CUL_MAX 123456

zusätzlich habe ich es jeweils probiert mit

attr cm IODev CUL0
und
attr cm IODev myHmUART

aber nichts funktioniert.

wenn ich den cm in den pairmode versetze, kriege ich folgende nachricht ungefähr 6 mal:

2024.01.24 16:16:53 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-41:myHmUART, help me!
2024.01.24 16:16:54 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.

wenn ich den myHmUART in den pairmode versetze kriege ich das Gerät eingelernt aber der state bleibt auf "? ??" und ich kann nichts damit machen.

Ich weiss nicht ob ich was falsch mache. Kann mir irgendwer helfen?

Hier die fhem.cfg nach ein wenig troubleshooting:

Code Auswählen Erweitern

attr global userattr cmdIcon devStateIcon:textField-long devStateStyle icon sortby webCmd webCmdLabel:textField-long widgetOverride
attr global autoload_undefined_devices 1
attr global logfile ./log/fhem-%Y-%m.log
attr global modpath .
attr global statefile ./log/fhem.save
attr global verbose 3

define WEB FHEMWEB 8083 global
setuuid WEB 65b126e2-f33f-3340-75dd-ff19f5e7a37edc8e

# Fake FileLog entry, to access the fhem log from FHEMWEB
define Logfile FileLog ./log/fhem-%Y-%m.log Logfile
setuuid Logfile 65b126e2-f33f-3340-1ab2-0195c5599ad06602

define autocreate autocreate
setuuid autocreate 65b126e2-f33f-3340-45a9-617d367f0defa1fd
attr autocreate filelog ./log/%NAME-%Y.log

define eventTypes eventTypes ./log/eventTypes.txt
setuuid eventTypes 65b126e2-f33f-3340-45d8-952fa77ab97b76da

# Disable this to avoid looking for new USB devices on startup
define initialUsbCheck notify global:INITIALIZED usb create
setuuid initialUsbCheck 65b126e2-f33f-3340-5b02-5d62081f2612578e
attr initialUsbCheck disable 1
define myHmUART HMUARTLGW /dev/ttyAMA0
setuuid myHmUART 65b127d6-f33f-3340-0ed3-c78325df2019efbf
attr myHmUART hmId 123456
define CUL0 CUL /dev/ttyAMA0@115200 0000
setuuid CUL0 65b12900-f33f-3340-ddbe-a2dec7201615029e
attr CUL0 rfmode MAX
define cm CUL_MAX 123456
setuuid cm 65b12920-f33f-3340-dd51-3d95fbae608ff418
attr cm IODev myHmUART
attr cm fakeSCaddr 222222
attr cm fakeWTaddr 111111
define FileLog_HM_1576A2 FileLog ./log/HM_1576A2-%Y.log HM_1576A2
setuuid FileLog_HM_1576A2 65b12b66-f33f-3340-3ee4-563e01cea7c68c2d
attr FileLog_HM_1576A2 logtype text
attr FileLog_HM_1576A2 room CUL_HM


Hier die logfile nach ein wenig troubleshooting:

Code Auswählen Erweitern

2024.01.24 16:01:56 1: Including fhem.cfg
2024.01.24 16:01:57 3: WEB: port 8083 opened
2024.01.24 16:01:57 2: eventTypes: loaded 0 lines from ./log/eventTypes.txt
2024.01.24 16:01:58 1: Messages collected while initializing FHEM:SecurityCheck:
  WEB is not password protected

Protect this FHEM installation by defining an allowed device with define allowed allowed
You can disable this message with attr global motd none

2024.01.24 16:01:58 1: usb create starting
2024.01.24 16:01:58 3: Probing ZWDongle device /dev/serial1
2024.01.24 16:01:58 3: Probing CUL device /dev/ttyAMA0
2024.01.24 16:01:58 3: Probing TCM_ESP3 device /dev/ttyAMA0
2024.01.24 16:01:58 3: Probing ZWDongle device /dev/ttyAMA0
2024.01.24 16:01:59 3: Probing SIGNALDuino device /dev/ttyAMA0
2024.01.24 16:01:59 3: Probing MYSENSORS device /dev/ttyAMA0
2024.01.24 16:01:59 3: Probing ArduCounter device /dev/ttyAMA0
2024.01.24 16:01:59 3: Probing ElsnerWS device /dev/ttyAMA0
2024.01.24 16:02:00 3: Probing FRM device /dev/ttyAMA0
2024.01.24 16:02:05 1: usb create end
2024.01.24 16:02:05 0: Featurelevel: 6.2
2024.01.24 16:02:05 0: Server started with 6 defined entities (fhem.pl:28227/2023-11-29 perl:5.032001 os:linux user:fhem pid:3428)
2024.01.24 16:03:52 0: Server shutdown
2024.01.24 16:04:01 1: Including fhem.cfg
2024.01.24 16:04:02 3: WEB: port 8083 opened
2024.01.24 16:04:02 2: eventTypes: loaded 0 lines from ./log/eventTypes.txt
2024.01.24 16:04:02 1: Including ./log/fhem.save
2024.01.24 16:04:02 1: Messages collected while initializing FHEM:SecurityCheck:
  WEB is not password protected

Protect this FHEM installation by defining an allowed device with define allowed allowed
You can disable this message with attr global motd none

2024.01.24 16:04:02 1: usb create starting
2024.01.24 16:04:02 3: Probing ZWDongle device /dev/serial0
2024.01.24 16:04:03 3: Probing ZWDongle device /dev/serial1
2024.01.24 16:04:03 3: Probing CUL device /dev/ttyAMA0
2024.01.24 16:04:03 3: Probing TCM_ESP3 device /dev/ttyAMA0
2024.01.24 16:04:03 3: Probing ZWDongle device /dev/ttyAMA0
2024.01.24 16:04:03 3: Probing SIGNALDuino device /dev/ttyAMA0
2024.01.24 16:04:04 3: Probing MYSENSORS device /dev/ttyAMA0
2024.01.24 16:04:04 3: Probing ArduCounter device /dev/ttyAMA0
2024.01.24 16:04:04 3: Probing ElsnerWS device /dev/ttyAMA0
2024.01.24 16:04:05 3: Probing FRM device /dev/ttyAMA0
2024.01.24 16:04:10 3: Probing CUL device /dev/ttyS0
2024.01.24 16:04:10 1: usb create end
2024.01.24 16:04:10 0: Featurelevel: 6.2
2024.01.24 16:04:10 0: Server started with 6 defined entities (fhem.pl:28227/2023-11-29 perl:5.032001 os:linux user:fhem pid:567)
2024.01.24 16:08:06 3: Opening myHmUART device /dev/ttyAMA0
2024.01.24 16:08:06 3: Setting myHmUART serial parameters to 115200,8,N,1
2024.01.24 16:08:06 3: myHmUART device opened
2024.01.24 16:08:21 1: MKDIR restoreDir/save/2024-01-24
2024.01.24 16:08:48 0: Server shutdown
2024.01.24 16:08:58 1: Including fhem.cfg
2024.01.24 16:08:59 3: WEB: port 8083 opened
2024.01.24 16:08:59 2: eventTypes: loaded 12 lines from ./log/eventTypes.txt
2024.01.24 16:08:59 1: Including ./log/fhem.save
2024.01.24 16:08:59 1: Messages collected while initializing FHEM:SecurityCheck:
  WEB is not password protected

Protect this FHEM installation by defining an allowed device with define allowed allowed
You can disable this message with attr global motd none

2024.01.24 16:08:59 3: Opening myHmUART device /dev/ttyAMA0
2024.01.24 16:09:00 3: Setting myHmUART serial parameters to 115200,8,N,1
2024.01.24 16:09:00 3: myHmUART device opened
2024.01.24 16:09:00 0: Featurelevel: 6.2
2024.01.24 16:09:00 0: Server started with 7 defined entities (fhem.pl:28227/2023-11-29 perl:5.032001 os:linux user:fhem pid:572)
2024.01.24 16:13:04 3: Opening CUL0 device /dev/ttyAMA0
2024.01.24 16:13:04 3: Setting CUL0 serial parameters to 115200,8,N,1
2024.01.24 16:13:13 1: Cannot init /dev/ttyAMA0, ignoring it (CUL0)
2024.01.24 16:13:26 2: Switched CUL0 rfmode to MAX
2024.01.24 16:13:41 1: cm, did not find suitable IODev (CUL etc. in rfmode MAX)! You may want to execute 'attr cm IODev SomeCUL'
2024.01.24 16:13:45 0: Server shutdown
2024.01.24 16:13:53 1: Including fhem.cfg
2024.01.24 16:13:54 3: WEB: port 8083 opened
2024.01.24 16:13:54 2: eventTypes: loaded 12 lines from ./log/eventTypes.txt
2024.01.24 16:13:55 3: Opening CUL0 device /dev/ttyAMA0
2024.01.24 16:13:55 3: Setting CUL0 serial parameters to 115200,8,N,1
2024.01.24 16:14:04 1: Cannot init /dev/ttyAMA0, ignoring it (CUL0)
2024.01.24 16:14:04 2: Switched CUL0 rfmode to MAX
2024.01.24 16:14:04 1: Including ./log/fhem.save
2024.01.24 16:14:04 1: Messages collected while initializing FHEM:SecurityCheck:
  WEB is not password protected

Protect this FHEM installation by defining an allowed device with define allowed allowed
You can disable this message with attr global motd none

2024.01.24 16:14:04 3: Opening myHmUART device /dev/ttyAMA0
2024.01.24 16:14:04 3: Setting myHmUART serial parameters to 115200,8,N,1
2024.01.24 16:14:04 3: myHmUART device opened
2024.01.24 16:14:04 0: Featurelevel: 6.2
2024.01.24 16:14:04 0: Server started with 9 defined entities (fhem.pl:28227/2023-11-29 perl:5.032001 os:linux user:fhem pid:569)
2024.01.24 16:14:09 1: cm, did not find suitable IODev (CUL etc. in rfmode MAX)! You may want to execute 'attr cm IODev SomeCUL'
2024.01.24 16:16:51 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:16:51 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-41:myHmUART, help me!
2024.01.24 16:16:51 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:16:51 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-42:myHmUART, help me!
2024.01.24 16:16:52 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:16:52 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-41:myHmUART, help me!
2024.01.24 16:16:53 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:16:53 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-41:myHmUART, help me!
2024.01.24 16:16:54 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:16:54 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-40:myHmUART, help me!
2024.01.24 16:17:58 3: CUL_HM start Queues
2024.01.24 16:17:59 0: Server shutdown
2024.01.24 16:18:12 1: Including fhem.cfg
2024.01.24 16:18:14 3: WEB: port 8083 opened
2024.01.24 16:18:14 2: eventTypes: loaded 12 lines from ./log/eventTypes.txt
2024.01.24 16:18:14 3: Opening CUL0 device /dev/ttyAMA0
2024.01.24 16:18:14 3: Setting CUL0 serial parameters to 115200,8,N,1
2024.01.24 16:18:23 1: Cannot init /dev/ttyAMA0, ignoring it (CUL0)
2024.01.24 16:18:23 2: Switched CUL0 rfmode to MAX
2024.01.24 16:18:24 1: Including ./log/fhem.save
2024.01.24 16:18:24 1: Messages collected while initializing FHEM:SecurityCheck:
  WEB is not password protected

Protect this FHEM installation by defining an allowed device with define allowed allowed
You can disable this message with attr global motd none

2024.01.24 16:18:24 3: Opening myHmUART device /dev/ttyAMA0
2024.01.24 16:18:24 3: Setting myHmUART serial parameters to 115200,8,N,1
2024.01.24 16:18:24 3: myHmUART device opened
2024.01.24 16:18:24 0: Featurelevel: 6.2
2024.01.24 16:18:24 0: Server started with 9 defined entities (fhem.pl:28227/2023-11-29 perl:5.032001 os:linux user:fhem pid:570)
2024.01.24 16:18:29 1: cm, IODev has no VERSION
2024.01.24 16:18:29 1: cm, detected very old firmware version 0 of the CUL-compatible IODev CUL0
2024.01.24 16:19:39 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:19:41 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-42:myHmUART, help me!
2024.01.24 16:19:41 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:19:41 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-36:myHmUART, help me!
2024.01.24 16:19:41 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:19:41 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-35:myHmUART, help me!
2024.01.24 16:19:42 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:19:42 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-33:myHmUART, help me!
2024.01.24 16:19:43 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:19:43 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-33:myHmUART, help me!
2024.01.24 16:19:44 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:19:44 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-33:myHmUART, help me!
2024.01.24 16:20:04 1: PERL WARNING: Use of uninitialized value $args[0] in int at ./FHEM/14_CUL_MAX.pm line 450.
2024.01.24 16:20:13 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:20:13 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-57:myHmUART, help me!
2024.01.24 16:20:14 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:20:14 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-41:myHmUART, help me!
2024.01.24 16:20:15 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:20:15 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-53:myHmUART, help me!
2024.01.24 16:20:16 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:20:16 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-38:myHmUART, help me!
2024.01.24 16:20:17 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:20:17 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-35:myHmUART, help me!
2024.01.24 16:20:47 3: CUL_HM start Queues
2024.01.24 16:21:05 0: Server shutdown
2024.01.24 16:21:17 1: Including fhem.cfg
2024.01.24 16:21:18 3: WEB: port 8083 opened
2024.01.24 16:21:19 2: eventTypes: loaded 13 lines from ./log/eventTypes.txt
2024.01.24 16:21:19 3: Opening CUL0 device /dev/ttyAMA0
2024.01.24 16:21:19 3: Setting CUL0 serial parameters to 115200,8,N,1
2024.01.24 16:21:28 1: Cannot init /dev/ttyAMA0, ignoring it (CUL0)
2024.01.24 16:21:28 2: Switched CUL0 rfmode to MAX
2024.01.24 16:21:31 1: Including ./log/fhem.save
2024.01.24 16:21:31 1: Messages collected while initializing FHEM:SecurityCheck:
  WEB is not password protected

Protect this FHEM installation by defining an allowed device with define allowed allowed
You can disable this message with attr global motd none

2024.01.24 16:21:31 3: Opening myHmUART device /dev/ttyAMA0
2024.01.24 16:21:31 3: Setting myHmUART serial parameters to 115200,8,N,1
2024.01.24 16:21:31 3: myHmUART device opened
2024.01.24 16:21:31 0: Featurelevel: 6.2
2024.01.24 16:21:31 0: Server started with 9 defined entities (fhem.pl:28227/2023-11-29 perl:5.032001 os:linux user:fhem pid:574)
2024.01.24 16:21:36 1: cm, IODev has no VERSION
2024.01.24 16:21:36 1: cm, detected very old firmware version 0 of the CUL-compatible IODev myHmUART
2024.01.24 16:21:59 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:21:59 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-43:myHmUART, help me!
2024.01.24 16:22:00 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:22:00 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-46:myHmUART, help me!
2024.01.24 16:22:01 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:22:01 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-48:myHmUART, help me!
2024.01.24 16:22:02 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:22:02 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-38:myHmUART, help me!
2024.01.24 16:22:03 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:22:03 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-39:myHmUART, help me!
2024.01.24 16:22:16 1: PERL WARNING: Use of uninitialized value $args[0] in int at ./FHEM/14_CUL_MAX.pm line 450.
2024.01.24 16:22:20 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:22:20 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-47:myHmUART, help me!
2024.01.24 16:22:21 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:22:21 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-47:myHmUART, help me!
2024.01.24 16:22:22 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:22:22 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-59:myHmUART, help me!
2024.01.24 16:22:24 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:22:24 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-42:myHmUART, help me!
2024.01.24 16:22:25 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:22:25 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-40:myHmUART, help me!
2024.01.24 16:22:55 3: HMUARTLGW myHmUART entered pairing-mode
2024.01.24 16:23:06 3: CUL_HM start Queues
2024.01.24 16:23:18 2: autocreate: define HM_1576A2 CUL_HM 1576A2
2024.01.24 16:23:18 2: autocreate: define FileLog_HM_1576A2 FileLog ./log/HM_1576A2-%Y.log HM_1576A2
2024.01.24 16:23:18 3: CUL_HM pair: HM_1576A2 virtual, model unknown serialNr
2024.01.24 16:23:18 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-38:myHmUART, help me!
2024.01.24 16:23:19 1: PERL WARNING: Use of uninitialized value in string comparison (cmp) at ./FHEM/10_CUL_HM.pm line 4596.
2024.01.24 16:23:19 1: PERL WARNING: Use of uninitialized value in string ne at ./FHEM/10_CUL_HM.pm line 4604.
2024.01.24 16:23:19 1: PERL WARNING: Use of uninitialized value $h in string ne at ./FHEM/10_CUL_HM.pm line 4604.
2024.01.24 16:23:55 3: HMUARTLGW myHmUART left pairing-mode
2024.01.24 16:28:17 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:28:17 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-41:myHmUART, help me!
2024.01.24 16:28:18 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:28:18 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-57:myHmUART, help me!
2024.01.24 16:28:19 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:28:19 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-45:myHmUART, help me!
2024.01.24 16:28:20 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:28:20 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-39:myHmUART, help me!
2024.01.24 16:28:21 2: CUL_HM received learning message from unknown id 1576A2 outside of pairing mode. Please enable pairing mode first or define a virtual device w. model: CCU-FHEM.
2024.01.24 16:28:21 3: myHmUART: Unknown code A1A0020001576A20000001005054E45513039333435373805050000::-39:myHmUART, help me!


[rudolfkoenig]

Deswegen weiss ich nicht ob ich grad an der richtigen Stelle frage.

Vermutich nicht, da es (soweit ich sehe) um Probleme mit HomeMatic geht.
Verschieben kann man das Thema mit dem Knopf unten Links.

define CUL0 CUL /dev/ttyACM0@115200 0000

CUL ist das falsche Modul fuer HM-MOD-RPI-PCB, das wurde beim Plug and Play (siehe log weiter unten) schon richtig dem HMUARTLGW zugeordnet. Das dazugehoerige logische Modul heisst aus historischen Gruenden trotzdem CUL_HM.

Die anderen Probleme bitte in der Homematic Gruppe ansprechen.

[Wzut]

ein HM-MOD-RPI-PCB HomeMatic Funkmodul

Das HM-MOD-RPI-PCB ist nur für Homematic Geräte geeignet nicht für MAX! (obwohl beide von eQ3 sind)
Für den MAX! Eco Taster brauchst du einen CUL.