Raspberry PI3 und HM-MOD-RPI-PCB funktioniert nicht mehr

[siod]

Hallo,

ich habe einen Pi3 auf dem ich Openhab2 laufen habe sowie das HM-MOD-RPI-PCB installiert habe. Das einzige device das ich mit Homegear steuern möchte ist ein Rolladen Aktor.
Das hatte alles bereits funktioniert, bis ich meinen Pi komplett neu aufsetzen und Openhab2.2 installieren musste. Denn nun musste ich auch Homegear wieder neu aufsetzen, was aus meiner Sicht auch gut gelungen ist, z.B. hatte ich ja die alten Config Files gesichert und wieder rüberkopiert. Allerdings bekomme ich nun keine Verbindung mehr zu meine Rolladen Aktor zustande.
Ich weiß leider nicht wo ich mit dem Troubleshooting anfangen soll, ich hoffe mir kann hier unter die Arme gegriffen werden…

hier mal mein log:

01/21/18 10:30:01.222 Starting Homegear...
01/21/18 10:30:01.222 Homegear version 0.7.12-1492
01/21/18 10:30:01.222 Git commit SHA of libhomegear-base: -
01/21/18 10:30:01.222 Git branch of libhomegear-base:     -
01/21/18 10:30:01.222 Git commit SHA of Homegear:         -
01/21/18 10:30:01.222 Git branch of Homegear:             -
01/21/18 10:30:01.223 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
01/21/18 10:30:01.223 Info: Core file size now is "4294967295".
01/21/18 10:30:01.223 Info: Setting maximum thread priority to "4294967295" for user with id 0 and group with id 0.
01/21/18 10:30:01.223 Info: Maximum thread priority now is "4294967295".
01/21/18 10:30:01.230 Info: Backing up database...
01/21/18 10:30:01.299 Initializing database...
01/21/18 10:30:01.302 Info: Loading family module mod_homematicbidcos.so
01/21/18 10:30:01.318 /etc/homegear/families/homematicbidcos.conf
01/21/18 10:30:01.323 Info: Loading family module mod_miscellaneous.so
01/21/18 10:30:01.326 /etc/homegear/families/miscellaneous.conf
01/21/18 10:30:01.327 Info: Loading family module mod_homematicwired.so
01/21/18 10:30:01.354 /etc/homegear/families/homematicwired.conf
01/21/18 10:30:01.355 Info: Setting up physical interfaces and GPIOs...
01/21/18 10:30:01.357 Info: Dropping privileges to user homegear (113) and group homegear (118)
01/21/18 10:30:01.358 Info: Homegear is (now) running as user with id 113 and group with id 118.
01/21/18 10:30:01.364 Starting script engine server...
01/21/18 10:30:01.372 Initializing licensing controller...
01/21/18 10:30:01.372 Loading licensing controller data...
01/21/18 10:30:01.373 Loading devices...
01/21/18 10:30:01.373 Loading XML RPC devices...
01/21/18 10:30:02.853 Loading device 2
01/21/18 10:30:02.853 Module HomeMatic BidCoS: Info: Central address set to 0xFDDA82.
01/21/18 10:30:02.854 Info: Not initializing device family HomeMatic Wired, because no physical interface was found.
01/21/18 10:30:02.854 Info: Disposing family module mod_homematicwired.so
01/21/18 10:30:02.859 Loading XML RPC devices...
01/21/18 10:30:02.863 Loading device 1
01/21/18 10:30:02.864 Initializing RPC client...
01/21/18 10:30:02.864 Starting XML RPC server RPCServer1 listening on :::2001...
01/21/18 10:30:02.866 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
01/21/18 10:30:02.867 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
01/21/18 10:30:02.905 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
01/21/18 10:30:02.905 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
01/21/18 10:30:02.939 Starting CLI server...
01/21/18 10:30:02.939 RPC Server (Port 2003): Info: RPC Server started listening on address :: and port 2003
01/21/18 10:30:02.939 Initializing event handler...
01/21/18 10:30:02.939 Loading events...
01/21/18 10:30:02.940 Starting flows server...
01/21/18 10:30:02.945 Starting IPC server...
01/21/18 10:30:02.950 Start listening for packets...
01/21/18 10:30:04.951 Startup complete. Waiting for physical interfaces to connect.
01/21/18 10:30:04.951 All physical interfaces are connected now.
01/21/18 10:30:04.951 Starting UPnP server...
01/21/18 10:30:04.952 Info: UPnP server: Binding to address: 192.168.1.50
01/21/18 10:30:04.953 UPnP Server: Info: Started listening.
01/21/18 10:30:05.951 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too small packet received: 0C000000436F5F4350555F424C7251
01/21/18 10:30:21.247 Info: CLI connection accepted. Client number: 13
01/21/18 10:30:35.051 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
01/21/18 10:30:36.979 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
01/21/18 10:30:38.980 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
01/21/18 10:31:09.081 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
01/21/18 10:31:10.145 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
01/21/18 10:31:12.145 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
01/21/18 10:31:12.281 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: CRC (69FB) failed on packet received from HM-MOD-RPI-PCB: FD000C000000436F5F4350555F424C72000C000000436F
01/21/18 10:31:12.282 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too large packet received: 4350555F424C72
01/21/18 10:31:12.282 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (3). Trying to reconnect...
01/21/18 10:31:13.282 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
01/21/18 10:31:42.246 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
01/21/18 10:31:44.246 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
01/21/18 10:31:44.383 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too large packet received: 000C000000436F
01/21/18 10:31:44.383 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (3). Trying to reconnect...
01/21/18 10:31:45.384 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
01/21/18 10:32:14.347 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
01/21/18 10:32:16.348 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
01/21/18 10:32:16.485 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too large packet received: 000C000000436F
01/21/18 10:32:16.485 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too large packet received: 4350555F424C72
01/21/18 10:32:46.449 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
01/21/18 10:32:47.506 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
01/21/18 10:32:49.507 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
01/21/18 10:32:49.643 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too small packet received: 0C000000436F

[pmayer]

Sers,

hast du alles gemacht, was hier stand um die Schnittstelle für das HM-MOD-RPI-PCB freizuräumen: https://doc.homegear.eu/data/homegear-homematicbidcos/configuration.html#config-hm-mod-rpi-pcb

Es könnte außerdem sein, dass die Firmware des HM-MOD-RPI-PCB geupdatet werden muss. Da ich selbst keins habe, bin ich da nicht der Fachmann. Aber durchsuch mal das Forum diesbezüglich.

so long,
p

[siod]

Ich habe alles so gemacht wie beschrieben, einzig diese Sache nicht, bin mir auch nicht sicher ob nötig da ich ein Openabian image nutze:

If you’re using the official Raspbian, you need to comment the lines containing “gpio” in file /etc/udev/rules.d/99-com.rules (place a “#” at the beginning of the lines) for Homegear to be able to access the GPIOs.

Ausserdem steht in fast jeder Zeile was mit gpio, soll ich die wirklich alle auskommentieren? Keine Ahnung…

[sathya]

Hallo @siod,

da kommt auf jeden Fall Müll über die serielle Schnittstelle. Hauptgrund: Die serielle Konsole ist noch aktiv. Auch sollte der HM-MOD-RPI-PCB nicht über Mini-UART angesprochen werden. Wenn du der Anleitung aber gefolgt bist, sollte es eigentlich passen. Wie sieht deine /boot/cmdline.txt aus? Wenn da etwas von /dev/serial0 steht, nimm das auch raus.

Weitere mögliche Gründe: Netzteil nicht leistungsstark genug oder Hardware defekt (ESD-Schaden, Lötschaden, …).

Viele Grüße

Sathya

[siod]

meine cmdline.txt:

dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=59dc21dd-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait

Hardwareschäden schließe ich komplett aus, es hat ja funktioniert bis ich den Pi neu aufgesetzt habe. Auch das Netzteil ist das gleiche.

edit:
Noch zur Info: Ich habe homegear über das Installations menü von openhabian installiert.
Danach habe ich noch folgende Schritte aus der Homegear Anleitung ausgeführt:

5.2.6.1.2. Raspberry Pi 3
On the Raspberry Pi 3 /dev/ttyAMA0 is used by the Wifi and Bluetooth module. There is a “mini UART” available on /dev/ttyS0 by default. It is better though, to use the hardware UART and switch the Wifi/Bluetooth module to mini UART. To do that, add this line at the end of /boot/config.txt:

dtoverlay=pi3-miniuart-bt
Additionally remove any references to ttyAMA0 from /boot/cmdline.txt. Our file looks like this:

dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
5.2.6.1.3. All Raspberry Pis
Make sure enable_uart=1 is in /boot/config.txt. Our file looks like this:

.
.
.
enable_uart=1
dtparam=spi=on
dtparam=i2c_arm=on
Disable the serial interface in Raspbian Jessie:

systemctl disable serial-getty@ttyAMA0.service
systemctl disable serial-getty@serial0.service
systemctl disable serial-getty@ttyS0.service
Reboot the Raspberry Pi.

Warning

If you’re using the official Raspbian, you need to comment the lines containing “gpio” in file /etc/udev/rules.d/99-com.rules (place a “#” at the beginning of the lines) for Homegear to be able to access the GPIOs.

5.2.6.2. Configuring Homegear to Use the HM-MOD-RPI-PCB
To tell Homegear to use the HM-MOD-RPI-PCB, insert these lines into homematicbidcos.conf:

[HomeMatic Wireless Module for Raspberry Pi]
id = My-HM-MOD-RPI-PCB
# Uncomment this if you want the HM-MOD-RPI-PCB to be your default communication module.
#default = true
deviceType = hm-mod-rpi-pcb
device = /dev/ttyAMA0
responseDelay = 95
gpio1 = 18

Habe ich irgendwas vergessen?

[job]

Habe ich irgendwas vergessen?

Ja.

meine cmdline.txt:

dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=59dc21dd-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait

Wie sieht deine /boot/cmdline.txt aus? Wenn da etwas von /dev/serial0 steht, nimm das auch raus.

Genau das.
serial0 = /dev/serial0

Das ist nur relativer Pfad vs. absoluter Pfad.

[siod]

Ok, habe es rausgenommen.

Leider hat es mein Problem nicht gelöst, bekomme weiterhin keine Verbindung zu meinem Aktor hergestellt. Hier noch mal das aktuelle Log:

01/21/18 16:45:09.240 Starting Homegear...
01/21/18 16:45:09.240 Homegear version 0.7.12-1492
01/21/18 16:45:09.241 Git commit SHA of libhomegear-base: -
01/21/18 16:45:09.241 Git branch of libhomegear-base:     -
01/21/18 16:45:09.241 Git commit SHA of Homegear:         -
01/21/18 16:45:09.242 Git branch of Homegear:             -
01/21/18 16:45:09.243 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
01/21/18 16:45:09.243 Info: Core file size now is "4294967295".
01/21/18 16:45:09.244 Info: Setting maximum thread priority to "4294967295" for user with id 0 and group with id 0.
01/21/18 16:45:09.244 Info: Maximum thread priority now is "4294967295".
01/21/18 16:45:09.256 Info: Backing up database...
01/21/18 16:45:09.349 Initializing database...
01/21/18 16:45:09.353 Info: Loading family module mod_homematicbidcos.so
01/21/18 16:45:09.364 /etc/homegear/families/homematicbidcos.conf
01/21/18 16:45:09.366 Info: Loading family module mod_miscellaneous.so
01/21/18 16:45:09.370 /etc/homegear/families/miscellaneous.conf
01/21/18 16:45:09.371 Info: Loading family module mod_homematicwired.so
01/21/18 16:45:09.377 /etc/homegear/families/homematicwired.conf
01/21/18 16:45:09.377 Info: Setting up physical interfaces and GPIOs...
01/21/18 16:45:09.379 Info: Dropping privileges to user homegear (113) and group homegear (118)
01/21/18 16:45:09.380 Info: Homegear is (now) running as user with id 113 and group with id 118.
01/21/18 16:45:09.386 Starting script engine server...
01/21/18 16:45:09.394 Initializing licensing controller...
01/21/18 16:45:09.394 Loading licensing controller data...
01/21/18 16:45:09.394 Loading devices...
01/21/18 16:45:09.394 Loading XML RPC devices...
01/21/18 16:45:10.295 Loading device 2
01/21/18 16:45:10.296 Module HomeMatic BidCoS: Info: Central address set to 0xFDDA82.
01/21/18 16:45:10.296 Info: Not initializing device family HomeMatic Wired, because no physical interface was found.
01/21/18 16:45:10.297 Info: Disposing family module mod_homematicwired.so
01/21/18 16:45:10.297 Loading XML RPC devices...
01/21/18 16:45:10.299 Loading device 1
01/21/18 16:45:10.299 Initializing RPC client...
01/21/18 16:45:10.299 Starting XML RPC server RPCServer1 listening on :::2001...
01/21/18 16:45:10.302 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
01/21/18 16:45:10.302 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
01/21/18 16:45:10.341 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
01/21/18 16:45:10.341 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
01/21/18 16:45:10.373 Starting CLI server...
01/21/18 16:45:10.374 RPC Server (Port 2003): Info: RPC Server started listening on address :: and port 2003
01/21/18 16:45:10.374 Initializing event handler...
01/21/18 16:45:10.374 Loading events...
01/21/18 16:45:10.375 Starting flows server...
01/21/18 16:45:10.380 Starting IPC server...
01/21/18 16:45:10.384 Start listening for packets...
01/21/18 16:45:12.385 Startup complete. Waiting for physical interfaces to connect.
01/21/18 16:45:12.385 All physical interfaces are connected now.
01/21/18 16:45:12.385 Starting UPnP server...
01/21/18 16:45:12.386 Info: UPnP server: Binding to address: 192.168.1.50
01/21/18 16:45:12.386 Error: A core file exists in Homegear's working directory ("/var/lib/homegear/core"). Please send this file to the Homegear team including information about your system (Linux distribution, CPU architecture), the Homegear version, the current log files and information what might've caused the error.
01/21/18 16:45:12.386 UPnP Server: Info: Started listening.
01/21/18 16:45:13.385 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too small packet received: 0C000000436F5F43FF
01/21/18 16:45:42.485 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
01/21/18 16:45:44.414 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
01/21/18 16:45:44.449 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.1.128:33921 accepted. Client number: 14
01/21/18 16:45:44.449 RPC Server (Port 2001): Info: RPC server client id for client number 14 is: 0
01/21/18 16:45:46.415 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
01/21/18 16:45:46.551 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too small packet received: 0C000000436F
01/21/18 16:46:08.656 Info: CLI connection accepted. Client number: 16
01/21/18 16:46:16.515 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
01/21/18 16:46:17.571 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
01/21/18 16:46:19.572 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
01/21/18 16:46:19.709 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too large packet received: 0C000000436F
01/21/18 16:46:19.709 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too large packet received: 5F4350555F424C72
01/21/18 16:46:39.745 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.1.128:52978 accepted. Client number: 19
01/21/18 16:46:39.746 RPC Server (Port 2001): Info: RPC server client id for client number 19 is: 1
01/21/18 16:46:49.673 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
01/21/18 16:46:50.727 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
01/21/18 16:46:52.727 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
01/21/18 16:47:22.828 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
01/21/18 16:47:23.891 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
01/21/18 16:47:25.827 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.1.128:54456 accepted. Client number: 23
01/21/18 16:47:25.828 RPC Server (Port 2001): Info: RPC server client id for client number 23 is: 2
01/21/18 16:47:25.892 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
01/21/18 16:47:26.033 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: CRC (674E) failed on packet received from HM-MOD-RPI-PCB: FD000C000000436F0C000000436F5F4350FF
01/21/18 16:47:55.993 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
01/21/18 16:47:57.058 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
01/21/18 16:47:59.059 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
01/21/18 16:47:59.195 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too small packet received: 0C000000436F
01/21/18 16:48:22.760 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.1.128:56753 accepted. Client number: 27
01/21/18 16:48:22.760 RPC Server (Port 2001): Info: RPC server client id for client number 27 is: 3
01/21/18 16:48:29.160 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
01/21/18 16:48:30.227 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
01/21/18 16:48:32.228 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
01/21/18 16:49:02.328 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
01/21/18 16:49:03.390 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
01/21/18 16:49:05.391 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
01/21/18 16:49:05.529 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: CRC (CE2D) failed on packet received from HM-MOD-RPI-PCB: FD000C000000436F0C000000436F5F436AEAFE
01/21/18 16:49:16.832 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.1.128:40009 accepted. Client number: 32
01/21/18 16:49:16.832 RPC Server (Port 2001): Info: RPC server client id for client number 32 is: 4
01/21/18 16:49:35.492 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
01/21/18 16:49:36.556 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Connection closed (1). Trying to reconnect...
01/21/18 16:49:38.557 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connected to HM-MOD-RPI-PCB.
01/21/18 16:49:38.693 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too small packet received: 0C000000436F
01/21/18 16:49:38.694 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Warning: Too large packet received: 5F4350555F424C7251

[sathya]

Ja ja, UART auf dem Pi :-P. Das kann ganz schön nerven… Ich habe serial0 jetzt mal in der Doku ergänzt. Der Hinweis kam auch hier aus dem Forum, ich hatte nur zu dem Zeitpunkt vergessen, ihn in der Doku mit aufzunehmen . Eigentlich sollte es das gewesen sein. Neugestartet hast du vermutlich? Falls ja, gehen mir die Ideen aus. Ich würde vorschlagen, einmal zu schauen, ob es mit dem Homegear-Image klappt. Wenn du eine zweite SD-Karte hast, ist das ja schnell probiert.

[siod]

Ja, neugestartet hatte ich bereits.

Das mit dem Homegear Image ist einen Versuch wert, dann allerdings erst nächstes Wochenende…

[siod]

Hab es hinbekommen, mit meinem ursprünglichen Image!

Es muss tatsächlich an diesem ominösen /etc/udev/rules.d/99-com.rules file gelegen haben. Nachdem ich sie wie unten angepasst habe geht es endlich wieder! Vielen Dank für eure Hilfe!!!

SUBSYSTEM=="input", GROUP="input", MODE="0660"
SUBSYSTEM=="i2c-dev", GROUP="i2c", MODE="0660"
SUBSYSTEM=="spidev", GROUP="spi", MODE="0660"
#SUBSYSTEM=="bcm2835-gpiomem", GROUP="gpio", MODE="0660"

#SUBSYSTEM=="gpio", GROUP="gpio", MODE="0660"
#SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c '\
#	chown -R root:gpio /sys/class/gpio && chmod -R 770 /sys/class/gpio;\
#	chown -R root:gpio /sys/devices/virtual/gpio && chmod -R 770 /sys/devices/virtual/gpio;\
#	chown -R root:gpio /sys$devpath && chmod -R 770 /sys$devpath\
'"

KERNEL=="ttyAMA[01]", PROGRAM="/bin/sh -c '\
	ALIASES=/proc/device-tree/aliases; \
	if cmp -s $ALIASES/uart0 $ALIASES/serial0; then \
		echo 0;\
	elif cmp -s $ALIASES/uart0 $ALIASES/serial1; then \
		echo 1; \
	else \
		exit 1; \
	fi\
'", SYMLINK+="serial%c"

KERNEL=="ttyS0", PROGRAM="/bin/sh -c '\
	ALIASES=/proc/device-tree/aliases; \
	if cmp -s $ALIASES/uart1 $ALIASES/serial0; then \
		echo 0; \
	elif cmp -s $ALIASES/uart1 $ALIASES/serial1; then \
		echo 1; \
	else \
		exit 1; \
	fi \
'", SYMLINK+="serial%c"