(Gelöst) Pairing mit HM-MOD-RPI-PCB klappt nicht, Pakete werden aber empfangen (meine erste Installation)

Hallo,

ich versuche nun schon seit einigen Tagen ein neu gekauftes Heizkörperthermostat mit einem neu gekauften HM-MOD-RPI-PCB an meinen nicht mehr ganz so neuen Raspberry PI 3 zu verbinden.
Bei der Installation habe ich mich weitestgehend an die Homegear Dokumentation gehalten. Mein HM-MOD-RPI-PCB war auf Version 1.2.1, zwischenzeitlich habe ich ihn auf Version 1.4.1 geupdated. Das Modul ist übrigens funktionsfähig (Ich hatte es zwischenzeitlich mit einem RaspberryMatic Image getestet). So viel am Rande, aber zurück zu meinem Problem. Wenn ich den pairing mode (pon) an beiden Geräten aktiviere, laufen die 60/30 Sekunden ab, aber in meiner Liste (ls) ist nichts zu finden (No peers are paired to this central) .

Auf Loglevel 6 sieht der Verbindungsversuch so aus:

01/26/18 03:10:49.885 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD00200101050000
01/26/18 03:10:49.886 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 230284005D10D300
01/26/18 03:10:49.886 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 00001400954F4551
01/26/18 03:10:49.887 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 3132353738323159
01/26/18 03:10:49.888 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 00FFFFEBAE
01/26/18 03:10:49.888 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD00200101050000230284005D10D30000001400954F4551313235373832315900FFFFEBAE
01/26/18 03:10:49.888 Debug (My-HM-MOD-RPI-PCB): Packet 1A0284005D10D30000001400954F4551313235373832315900FFFF enters raisePacketReceived.
01/26/18 03:10:49.889 Debug (My-HM-MOD-RPI-PCB): Packet 1A0284005D10D30000001400954F4551313235373832315900FFFF is now passed to the EventHandler.
01/26/18 03:10:49.888 HomeMatic BidCoS packet received (My-HM-MOD-RPI-PCB, RSSI: -35 dBm): 1A0284005D10D30000001400954F4551313235373832315900FFFF
01/26/18 03:10:49.889 Module HomeMatic BidCoS: Debug: Device 5: Access granted for packet 1A0284005D10D30000001400954F4551313235373832315900FFFF
01/26/18 03:10:49.890 Module HomeMatic BidCoS: Debug: Setting physical device's wake up flag.
01/26/18 03:10:49.890 Module HomeMatic BidCoS: Debug: Sending peer to LGW "My-HM-MOD-RPI-PCB": Address 5D10D3, AES enabled 0, AES map 00.
01/26/18 03:10:49.890 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD0009010E065D10D3000000C340
01/26/18 03:10:49.891 Module HomeMatic BidCoS: Info: Pushing pending queues.
01/26/18 03:10:49.891 Debug (My-HM-MOD-RPI-PCB): Packet processing of packet 1A0284005D10D30000001400954F4551313235373832315900FFFF took 3 ms.
01/26/18 03:10:49.893 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0004010E04088D
01/26/18 03:10:49.894 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: D3
01/26/18 03:10:49.894 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0004010E04088DD3
01/26/18 03:10:49.944 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD0009010F065D10D3000000D346
01/26/18 03:10:49.947 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0004010F04080D
01/26/18 03:10:49.948 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: C4
01/26/18 03:10:49.948 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0004010F04080DC4
01/26/18 03:10:49.982 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Ignoring time packet.
01/26/18 03:10:49.998 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD00090110065D10D3000000A301
01/26/18 03:10:50.001 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0004011004088C
01/26/18 03:10:50.001 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 4B
01/26/18 03:10:50.002 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0004011004088C4B
01/26/18 03:10:50.052 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD00090111065D10D3000000B307
01/26/18 03:10:50.055 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0004011104080C
01/26/18 03:10:50.055 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 5C
01/26/18 03:10:50.055 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0004011104080C5C
01/26/18 03:10:50.106 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD00090112065D10D3000000830D
01/26/18 03:10:50.109 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0004011204080C
01/26/18 03:10:50.109 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 60
01/26/18 03:10:50.109 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0004011204080C60
01/26/18 03:10:50.159 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD00090113065D10D3000000930B
01/26/18 03:10:50.162 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0004011304088C
01/26/18 03:10:50.163 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 77
01/26/18 03:10:50.163 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0004011304088C77
01/26/18 03:10:50.213 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD00090114065D10D3000000E319
01/26/18 03:10:50.216 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0004011404080C
01/26/18 03:10:50.216 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 18
01/26/18 03:10:50.217 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0004011404080C18
01/26/18 03:10:50.267 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD00090115065D10D3000000F31F
01/26/18 03:10:50.270 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0004011504088C
01/26/18 03:10:50.270 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 0F
01/26/18 03:10:50.270 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0004011504088C0F
01/26/18 03:10:50.321 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD00090116065D10D3000000C315
01/26/18 03:10:50.324 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0004011604088C
01/26/18 03:10:50.324 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 33
01/26/18 03:10:50.324 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0004011604088C33
01/26/18 03:10:50.374 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD00090117065D10D3000000D313
01/26/18 03:10:50.377 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0004011704080C
01/26/18 03:10:50.378 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 24
01/26/18 03:10:50.378 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0004011704080C24
01/26/18 03:10:50.428 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD00090118065D10D30000002331
01/26/18 03:10:50.432 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD00100118040701
01/26/18 03:10:50.433 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 010001FFFFFFFFFF
01/26/18 03:10:50.433 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FFFFFFDACF
01/26/18 03:10:50.433 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD00100118040701010001FFFFFFFFFFFFFFFFDACF
01/26/18 03:10:50.434 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD00090119065D10D30000003337
01/26/18 03:10:50.437 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD00100119040701
01/26/18 03:10:50.438 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 010001FFFFFFFFFF
01/26/18 03:10:50.439 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FFFFFFDBC9
01/26/18 03:10:50.439 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD00100119040701010001FFFFFFFFFFFFFFFFDBC9
01/26/18 03:10:50.439 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD000D011A0A5D10D3000102030405061E97
01/26/18 03:10:50.444 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0004011A04018C
01/26/18 03:10:50.445 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: F5
01/26/18 03:10:50.445 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0004011A04018CF5
01/26/18 03:10:50.445 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD0009011B065D10D3000000133B
01/26/18 03:10:50.449 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0010011B040701
01/26/18 03:10:50.449 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 010001FFFFFFFFFF
01/26/18 03:10:50.450 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FFFFFFD9C5
01/26/18 03:10:50.450 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0010011B040701010001FFFFFFFFFFFFFFFFD9C5
01/26/18 03:10:50.450 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD0009011C065D10D30000006329
01/26/18 03:10:50.454 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0010011C040701
01/26/18 03:10:50.455 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 010001FFFFFFFFFF
01/26/18 03:10:50.456 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FFFFFFDED7
01/26/18 03:10:50.456 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0010011C040701010001FFFFFFFFFFFFFFFFDED7
01/26/18 03:10:50.456 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD0009011D065D10D3000100F52C
01/26/18 03:10:50.460 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0010011D040701
01/26/18 03:10:50.460 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 010001FFFFFFFFFF
01/26/18 03:10:50.461 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FFFFFFDFD1
01/26/18 03:10:50.461 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0010011D040701010001FFFFFFFFFFFFFFFFDFD1
01/26/18 03:10:52.893 Module HomeMatic BidCoS: Debug: Deleting queue 1 for BidCoS peer with address 0x5D10D3

Meine Konfigurationsdatei unter /etc/homegear/families/homematicbidcos.conf :

___________________________________________________________________________

---------------------------- HomeMatic BidCoS  ----------------------------
___________________________________________________________________________

#######################################
########## General Settings  ##########
#######################################

[General]

## The BidCoS address of Homegear. It is recommended to change this to a random 3 byte hexadecimal
## value starting with 0xFD (e. g. 0xFD43AB). Only change this, when no HomeMatic BidCoS devices
## are paired to Homegear as existing pairings will not work anymore!
centralAddress = 0xFD43AB

## Specify a 16 byte (32 characters) long AES key here to protect your wireless communication
## !!! IMPORTANT: It is highly recommended to change this key before pairing the first device.
## !!! IMPORTANT: Never ever lose this key. That would render your devices useless.
## To remove the key from your devices, you need to factory reset them using Homegear. The factory
## reset on the device is not possible!!!
rfKey = 4E645267556B58703273357638792F42

## With each key change currentRFKeyIndex needs to be
## incremented by 1
currentRfKeyIndex = 1

## When you change rfKey, put the old key here. To change the key Homegear needs to know the
## old and the new one.
## !!! Do not set oldRFKey when you set rfKey for the first time !!!
##oldRFKey = 00112233445566778899AABBCCDDEEFF

## When set to "true" unsigned broadcast packets are processed by Homegear. This could enable an
## attacker to make Homegear do things, you don't want. That means, this option is a security
## risk.
processBroadcastWithAesEnabled = false



[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

die /boot/config.txt (sowohl ausprobiert mit “dtoverlay=pi3-miniuart-bt” als auch mit dtoverlay=pi3-disable-bt):

# For more options and information see
# http://rpf.io/configtxtreadme
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
# dtparam=audio=on

#HM-MOD-RPI-PCB Ergänzung
#dtoverlay=pi3-miniuart-bt
dtoverlay=pi3-disable-bt
enable_uart=1
dtparam=spi=on
dtparam=i2c_arm=on

dann noch die /boot/cmdline.txt:

dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait

und die /etc/udev/rules.d/99-com.rules

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*", 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"

Ebenfalls durchgeführt wurden:

systemctl disable serial-getty@ttyS0.service
systemctl disable serial-getty@serial0.service
systemctl disable serial-getty@ttyAMA0.service

Berechtigungen auf ttyAMA0:
crw-rw---- 1 homegear homegear 204, 64 Jan 26 12:35 /dev/ttyAMA0

Zwischenzeitlich war ich auf der Stable Version von Homegear, um diesen Fehler zu lösen hatte ich am Ende auf die Nightly geupdated.

Ich hatte im Forum auch über ein Problem mit einer relativ aktuellen Nightly gelesen, aber ich glaube nicht das ich dasselbe Problem habe, da bei mir keine der Meldungen zu sehen sind. Allerdings habe ich auch eine Neuinstallation, in dem Beitrag handelt es sich ja wiederum um ein Update einer bestehenden Version

Ich hoffe wirklich jemand kann mir helfen, mittlerweile ist schon viel Zeit in dieses Projekt geflossen, und ich würde mich sehr ärgern wenn es an dem Punkt scheitert. Danke auf jeden Fall schon mal für das Lesen meines Problems, auch ohne Antwort rechne ich das hoch an.

Grüße,
Marvin

Hallo @Nikushin,

da hat sich ein Fehler in den Quelltext eingeschlichen, dieser ist mittlerweile gefixed und es wird auch bereits eine neue Stable-Version kompiliert. Du kannst entweder noch ein paar Stunden (Raspbian Jessie) oder bis morgen früh (Raspbian Stretch) warten oder dir das aktuelle Nightly installieren.

Siehe auch: HM-MOD-RPI-PCB sendet nicht mehr, empfängt aber Daten

Viele Grüße

Sathya

2 Likes

Danke für die Antwort, nach dem Update scheint alles zu klappen :smiley:
Den Foreneintrag hatte ich auch schon gelesen, nur wusste ich nicht ob das Problem auch bei einer Neueinrichtung auftritt.

Noch mal danke und Grüße,

Marvin