Homegear findet kein device =(

ingeling · September 25, 2017, 5:22pm

hi, ich bin allmählich am verzweifeln…
ich habe einen Raspberry Pi3 und das Homematic Sendemodul HD-MOD-RPI-PCB. Ich möchte gerne meine Homematic Geräte mit Homegear pairen um sie dann mit Homeassistant zu nutzen.

ich habe es schon mehrfach probiert und mich an die Anleitung gehalten. Mit sudo homegear -r startet homegear auch korrekt aber mit families select 0 findet er einfach kein device =(

Ich habe alle ähnlichen Themen durchgearbeitet und konnte das Problem trotzdem nicht lösen.
Mit Raspberrymatic funktioniert alles einwandfrei deshalb ist es kein Hardwarefehler.

Meine Vorgehensweise beim Installieren:
Raspbian Stretch Lite komplett neu installiert

sudo apt-get update
sudo apt-get rpi-update
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

als root:

apt install apt-transport-https
wget https://homegear.eu/packages/Release.key && apt-key add Release.key && rm Release.key
echo 'deb https://homegear.eu/packages/Raspbian/ stretch/' >> /etc/apt/sources.list.d/homegear.list
apt update
apt install homegear homegear-nodes-core
apt install homegear-homematicbidcos

cmdline.txt wie unten angepasst
config.txt wie unten angepasst

systemctl disable serial-getty@ttyAMA0.service
systemctl disable serial-getty@serial0.service
systemctl disable serial-getty@ttyS0.service
/etc/udev/rules.d/99-com.rules gelöscht

homematicbidcos.conf wie unten angepasst

die Firmware des Moduls ist: 2.29.22.20170902
Anbei sind die log Datei, meine config.txt und die cmdline.txt

homegear.log:

09/25/17 18:22:14.852 Info: SIGHUP received...
    09/25/17 18:22:19.193 RPC Server (Port 2001): Error: Server could not start listening on port 2001: Address already in use
    09/25/17 18:22:19.193 RPC Server (Port 2002): Error: Server could not start listening on port 2002: Address already in use
    09/25/17 18:22:19.193 RPC Server (Port 2003): Error: Server could not start listening on port 2003: Address already in use
    09/25/17 18:22:19.194 Info: Backing up database...
    09/25/17 18:22:19.194 Closing database...
    09/25/17 18:22:19.194 Error: Can't execute "PRAGMA journal_mode = DELETE": database is locked
    09/25/17 18:22:19.198 Info: Reloading...
    09/25/17 18:22:19.198 Error: Cannot reload. Startup is not completed.
    09/25/17 18:22:19.203 Info: Backing up database...
    09/25/17 18:22:19.211 Can't execute "PRAGMA journal_mode=DELETE": database is locked
    09/25/17 18:22:22.367 Reloading flows server...
    09/25/17 18:22:22.368 Reloading script engine server...
    09/25/17 18:22:22.368 Info: Reload complete.
    09/25/17 18:22:22.368 Stopping UPnP server...
    09/25/17 18:22:22.433 (Shutdown) => Stopping Event handler
    09/25/17 18:22:22.434 (Shutdown) => Stopping RPC servers
    09/25/17 18:22:24.194 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
    09/25/17 18:22:24.194 RPC Server (Port 2003): Info: RPC Server started listening on address :: and port 2003
    09/25/17 18:22:24.194 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
    09/25/17 18:22:24.195 RPC Server (Port 2001): Info: Waiting for threads to finish.
    09/25/17 18:22:24.295 RPC Server (Port 2002): Info: Waiting for threads to finish.
    09/25/17 18:22:24.395 RPC Server (Port 2003): Info: Waiting for threads to finish.
    09/25/17 18:22:24.399 (Shutdown) => Stopping RPC client
    09/25/17 18:22:24.400 (Shutdown) => Closing physical interfaces
    09/25/17 18:22:24.400 (Shutdown) => Stopping IPC server...
    09/25/17 18:22:24.413 (Shutdown) => Stopping flows server...
    09/25/17 18:22:24.515 (Shutdown) => Stopping script engine server...
    09/25/17 18:22:24.600 (Shutdown) => Saving device families
    09/25/17 18:22:24.601 (Shutdown) => Saving devices
    09/25/17 18:22:24.601 (Shutdown) => Saving Miscellaneous central...
    09/25/17 18:22:24.601 (Shutdown) => Disposing device families
    09/25/17 18:22:24.601 (Shutdown) => Disposing database
    09/25/17 18:22:24.602 Closing database...
    09/25/17 18:22:26.217 (Shutdown) => Disposing family modules
    09/25/17 18:22:26.217 Info: Disposing family module mod_miscellaneous.so
    09/25/17 18:22:26.217 (Shutdown) => Disposing licensing modules
    09/25/17 18:22:26.262 (Shutdown) => Shutdown complete.
    09/25/17 18:22:40.911 Starting Homegear...
    09/25/17 18:22:40.913 Homegear version 0.7.9-1375
    09/25/17 18:22:40.913 Git commit SHA of libhomegear-base: -
    09/25/17 18:22:40.913 Git branch of libhomegear-base:     -
    09/25/17 18:22:40.913 Git commit SHA of Homegear:         -
    09/25/17 18:22:40.914 Git branch of Homegear:             -
    09/25/17 18:22:40.915 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
    09/25/17 18:22:40.915 Info: Core file size now is "4294967295".
    09/25/17 18:22:40.915 Info: Setting maximum thread priority to "4294967295" for user with id 0 and group with id 0.
    09/25/17 18:22:40.915 Info: Maximum thread priority now is "4294967295".
    09/25/17 18:22:41.024 Info: Backing up database...
    09/25/17 18:22:45.835 Initializing database...
    09/25/17 18:22:45.839 Info: Loading family module mod_miscellaneous.so
    09/25/17 18:22:45.876 /etc/homegear/families/miscellaneous.conf
    09/25/17 18:22:45.879 Info: Loading family module mod_homematicbidcos.so
    09/25/17 18:22:45.950 /etc/homegear/families/homematicbidcos.conf
    09/25/17 18:22:45.975 Info: Setting up physical interfaces and GPIOs...
    09/25/17 18:22:45.975 Info: Dropping privileges to user homegear (110) and group homegear (114)
    09/25/17 18:22:45.976 Info: Homegear is (now) running as user with id 110 and group with id 114.
    09/25/17 18:22:46.003 Starting script engine server...
    09/25/17 18:22:46.029 Initializing licensing controller...
    09/25/17 18:22:46.029 Loading licensing controller data...
    09/25/17 18:22:46.029 Loading devices...
    09/25/17 18:22:46.029 Info: Not initializing device family HomeMatic BidCoS, because no physical interface was found.
    09/25/17 18:22:46.029 Info: Disposing family module mod_homematicbidcos.so
    09/25/17 18:22:46.030 Loading XML RPC devices...
    09/25/17 18:22:46.087 Loading device 1
    09/25/17 18:22:46.092 Initializing RPC client...
    09/25/17 18:22:46.092 Starting XML RPC server RPCServer1 listening on :::2001...
    09/25/17 18:22:46.104 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
    09/25/17 18:22:46.105 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
    09/25/17 18:22:46.226 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
    09/25/17 18:22:46.226 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
    09/25/17 18:22:46.286 Starting CLI server...
    09/25/17 18:22:46.286 RPC Server (Port 2003): Info: RPC Server started listening on address :: and port 2003
    09/25/17 18:22:46.286 Initializing event handler...
    09/25/17 18:22:46.286 Loading events...
    09/25/17 18:22:46.287 Starting flows server...
    09/25/17 18:22:46.362 Starting IPC server...
    09/25/17 18:22:46.367 Start listening for packets...
    09/25/17 18:22:46.367 Startup complete. Waiting for physical interfaces to connect.
    09/25/17 18:22:46.367 All physical interfaces are connected now.
    09/25/17 18:22:46.367 Starting UPnP server...
    09/25/17 18:22:46.368 Info: UPnP server: Binding to address: 192.168.178.48
    09/25/17 18:22:46.368 UPnP Server: Info: Started listening.
    09/25/17 18:23:58.853 Info: CLI connection accepted. Client number: 8
    09/25/17 18:24:13.190 Info: Connection to CLI client number 8 closed.

config.txt:

    # For more op
tions and information see
    # http://rpf.io/configtxt
    # 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
    gpu_mem=16
    enable_uart=1
    # For more options and information see
    # http://rpf.io/configtxt
    # 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
    gpu_mem=16
    enable_uart=1
    dtoverlay=pi3-disable-bt
    dtoverlay=pi3-disable-wifi

cmdline.txt:

dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=760588c5-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait

homematicbidcos.conf;

#######################################
########### HM-MOD-RPI-PCB  ###########
#######################################

## The device family this interface is for
#[HomeMatic Wireless Module for Raspberry Pi]

## Specify an unique id here to identify this device in Homegear
id = My-HM-MOD-RPI-PCB

## When default is set to "true" Homegear will assign this device
## to new peers.
#default = true

## Options: cul, cc1100, coc, cunx, hmcfglan, hmlgw, hm-mod-rpi-pcb
deviceType = hm-mod-rpi-pcb

device = /dev/ttyAMA0

## Default: responseDelay = 95
## Should be "95" for CUL or COC, "100" for TI CC1101 and "60" for HM-CFG-LAN or HM-LGW
responseDelay = 95

## Default: gpio1 = 0
## "18" for HM-MOD-RPI-PCB
gpio1 = 18

ich hoffe ihr seht daraus woran es liegt.

P.s.: in raspberrymatic wird mein Modul angezeigt als: HM-RCV-50 BidCoS-RF, dabei ist es das HD-MOD-RPI-PCB Modul von ELV.

Danke schonmal und Gruß

pmayer · September 25, 2017, 5:28pm

Hi @ingeling,

aus meiner Sicht sieht das mit dem seriellen Anschluss gut aus, allerdings habe ich kein HM-MOD-RPI-PCB.
Wichtig: Nach den Änderungen an der cmdline.txt und den systemctl Aufrufen, musst du neu starten.

Hier hätte folgendes gereicht:

sudo apt update
sudo apt full-upgrade
sudo raspi-config

apt full-upgrade / apt-get dist-upgrade macht das upgrade mit.

Hier muss die Sektion einkommentiert werden. Beim Starten siehts du dann im Log All physical devices connected, wenn alles gut läuft.

ingeling · September 25, 2017, 6:23pm

danke für die schnelle Antwort.

Das heißt ich soll einfach ein zweites # vor #[HomeMatic Wireless Module for Raspberry Pi] schreiben?

Dies habe ich getan und bekomme nach einem Neustart in der logdatei:

09/25/17 20:01:18.649 (Shutdown) => Stopping Homegear (Signal: 15)
09/25/17 20:01:18.649 Flows Engine Server: Info: Stopping nodes.
09/25/17 20:01:18.650 (Shutdown) => Stopping CLI server
09/25/17 20:01:19.184 Stopping UPnP server...
09/25/17 20:01:20.565 (Shutdown) => Stopping Event handler
09/25/17 20:01:20.566 (Shutdown) => Stopping RPC servers
09/25/17 20:01:20.598 RPC Server (Port 2001): Info: Waiting for threads to finish.
09/25/17 20:01:20.698 RPC Server (Port 2002): Info: Waiting for threads to finish.
09/25/17 20:01:23.203 RPC Server (Port 2003): Info: Waiting for threads to finish.
09/25/17 20:01:23.206 (Shutdown) => Stopping RPC client
09/25/17 20:01:23.207 (Shutdown) => Closing physical interfaces
09/25/17 20:01:23.207 (Shutdown) => Stopping IPC server...
09/25/17 20:01:23.305 (Shutdown) => Stopping flows server...
09/25/17 20:01:23.406 (Shutdown) => Stopping script engine server...
09/25/17 20:01:23.410 (Shutdown) => Saving device families
09/25/17 20:01:23.410 (Shutdown) => Saving devices
09/25/17 20:01:23.410 (Shutdown) => Saving Miscellaneous central...
09/25/17 20:01:23.410 (Shutdown) => Disposing device families
09/25/17 20:01:23.410 (Shutdown) => Disposing database
09/25/17 20:01:23.411 Closing database...
09/25/17 20:01:24.866 (Shutdown) => Disposing family modules
09/25/17 20:01:24.866 Info: Disposing family module mod_miscellaneous.so
09/25/17 20:01:24.867 (Shutdown) => Disposing licensing modules
09/25/17 20:01:24.867 (Shutdown) => Shutdown complete.
09/25/17 20:01:40.240 Starting Homegear...
09/25/17 20:01:40.243 Homegear version 0.7.9-1375
09/25/17 20:01:40.243 Git commit SHA of libhomegear-base: -
09/25/17 20:01:40.244 Git branch of libhomegear-base:     -
09/25/17 20:01:40.244 Git commit SHA of Homegear:         -
09/25/17 20:01:40.244 Git branch of Homegear:             -
09/25/17 20:01:40.245 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
09/25/17 20:01:40.245 Info: Core file size now is "4294967295".
09/25/17 20:01:40.245 Info: Setting maximum thread priority to "4294967295" for user with id 0 and group with id 0.
09/25/17 20:01:40.245 Info: Maximum thread priority now is "4294967295".
09/25/17 20:01:40.354 Info: Backing up database...
09/25/17 20:01:44.366 Initializing database...
09/25/17 20:01:44.370 Info: Loading family module mod_miscellaneous.so
09/25/17 20:01:44.405 /etc/homegear/families/miscellaneous.conf
09/25/17 20:01:44.407 Info: Loading family module mod_homematicbidcos.so
09/25/17 20:01:44.467 /etc/homegear/families/homematicbidcos.conf
09/25/17 20:01:44.490 Info: Setting up physical interfaces and GPIOs...
09/25/17 20:01:44.490 Info: Dropping privileges to user homegear (110) and group homegear (114)
09/25/17 20:01:44.490 Info: Homegear is (now) running as user with id 110 and group with id 114.
09/25/17 20:01:44.512 Starting script engine server...
09/25/17 20:01:44.532 Initializing licensing controller...
09/25/17 20:01:44.532 Loading licensing controller data...
09/25/17 20:01:44.532 Loading devices...
09/25/17 20:01:44.533 Info: Not initializing device family HomeMatic BidCoS, because no physical interface was found.
09/25/17 20:01:44.533 Info: Disposing family module mod_homematicbidcos.so
09/25/17 20:01:44.533 Loading XML RPC devices...
09/25/17 20:01:44.587 Loading device 1
09/25/17 20:01:44.591 Initializing RPC client...
09/25/17 20:01:44.592 Starting XML RPC server RPCServer1 listening on :::2001...
09/25/17 20:01:44.601 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
09/25/17 20:01:44.601 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
09/25/17 20:01:44.682 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
09/25/17 20:01:44.683 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
09/25/17 20:01:44.716 Starting CLI server...
09/25/17 20:01:44.716 RPC Server (Port 2003): Info: RPC Server started listening on address :: and port 2003
09/25/17 20:01:44.716 Initializing event handler...
09/25/17 20:01:44.716 Loading events...
09/25/17 20:01:44.717 Starting flows server...
09/25/17 20:01:44.793 Starting IPC server...
09/25/17 20:01:44.797 Start listening for packets...
09/25/17 20:01:44.797 Startup complete. Waiting for physical interfaces to connect.
09/25/17 20:01:44.797 All physical interfaces are connected now.
09/25/17 20:01:44.797 Starting UPnP server...
09/25/17 20:01:44.798 Info: UPnP server: Binding to address: 192.168.178.48
09/25/17 20:01:44.798 UPnP Server: Info: Started listening.
09/25/17 20:03:14.960 Info: CLI connection accepted. Client number: 8
09/25/17 20:03:39.984 Info: Connection to CLI client number 8 closed.

in der Tat steht da All physical devices are connected now.

Allerdings findet homegear immer noch nichts:

pi@RPi3:~ $ sudo homegear -r
Connected to Homegear (version 0.7.9-1375).
> families list
   ID │ Name
──────┼───────────────────────────────
  254 │ Miscellaneous
──────┴───────────────────────────────
> families select 0
Device family not found.
>

habe ich etwas vergessen?

Gruß

edit: ich sehe gerade dass “All physical devices are connected now” auch schon im ersten log steht.
interessanterweise erhalte ich folgendes wenn ich “modules list” eingebe:

ID    Family Name                   Filename                      Compiled For  Loaded
254   Miscellaneous                 mod_miscellaneous.so          0.7.9-1375    true
0     HomeMatic BidCoS              mod_homematicbidcos.so        0.7.9-1375    false

wie kann ich ihn nun starten? das müsste ja das problem lösen oder?

pmayer · September 25, 2017, 8:40pm

Du musst du Sektion __ein__kommentieren… also ohne # am Start. Die Zeile in [] beginnt die Sektion, für die die folgenden Zeilen gelten.

[HomeMatic Wireless Module for Raspberry Pi]

Dadurch, dass die Sektion nicht “eingeschaltet” ist, sind alles devices connected weil es keine anderen gibt.

ingeling · September 26, 2017, 6:33am

Es hat geklappt!! Kann nun das modul verwenden. Vielen dank

Eine frage noch: wenn ich den rfkey vor dem pairen ändere muss ich direkt currentrfkeyindex auf 2 stellen oder beim ersten mal noch nicht?

Gruß

pmayer · September 26, 2017, 9:26am

Beim ersten mal noch nicht

pmayer · September 27, 2017, 10:02pm