HM-MOD-RPI-PCB und Openhab2:Anfänger


#1

moin zusammen,

bin noch recht neu hier und habe gleich ne Frage :slight_smile:
Ich habe mir oben besagtes Teil für meinen Rasp 3 besorgt…war bereits gelötet… und wurde von mir hoffentlich korrekt aufgesteckt.

Nun habe ich auf dem Raspian von Openhab2 (2.2) die Installationsschritte gemäß
https://doc.homegear.eu/data/homegear-homematicbidcos/configuration.html#config-hm-mod-rpi-pcb
durchgeführt…allerdings bekomme ich über dmesg einige Fehlermeldungen präsentiert…mit denen ich nichts anfangen kann :frowning:

 bcm2835-aux-uart 3f215040.serial: could not get clk: -517
- vc_vchi_sm_init: failed to open VCHI service (-1)
- [vc_sm_connected_init]: failed to initialize shared memory service
- brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.10.39 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-10-23 03:47:14

Wer kann helfen?? Danke schon mal im voraus


#2

Hmm,

die Meldung kenne ich so nich. Allerdings ist nur die erste Zeile für dich wichtig. Der rest ist von der GPU mit shared memory.

Hast du wirklich alles von 5.2.6.1.2 - 5.2.6.1.3 inklusive den Sachen in der orangenen Box gemacht?

Was sagt ls -la /dev/tty*?


#3

[07:07:29] openhabian@openHABianPi:~$ ls -la /dev/tty*

crw-rw---- 1 homegear homegear 204, 64 Feb 20 07:07 /dev/ttyAMA0
crw------- 1 root root 5, 3 Feb 19 20:29 /dev/ttyprintk
crw-rw---- 1 root dialout 4, 64 Feb 19 20:29 /dev/ttyS0


#4

Und noch meine Konfiguration…

boot/config.txt
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=spi=on

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


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

# Enable audio (loads snd_bcm2835)
dtparam=audio=on
gpu_mem=16
enable_uart=1
force_turbo=1
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
/boot/cmdline.txt
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
dwc_otg.lpm_enable=0 console=tty1  root=PARTUUID=b998aa25-02 rootfstype=ext4 elevator=deadline fsck.repair=y$
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

homematicbidcos.conf (habe alles rausnommen was scheinbar nicht benötigt wird)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++_
__________________________________________________________________________

---------------------------- 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 = 0xFD0001

## 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 = 00112233445566778899AABBCCDDEEFF

## 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

######################################
########### 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 = SC-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, homegeargateway
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

#5

grafik

Benutz doch bitte die Formatierungsfunktionen des Forums.


Die ttyS* devices kannst du im Post löschen. Wichtig war, dass /dev/ttyAMA0 da ist und von Homegear verwendet wird.
Aber bist du dir sicher, dass du die udev-rules gelöscht hast? ttyS0 dürfte glaube ich nicht mehr da sein.

Ansonsten könnte es mit der Firmware des HM-MOD-RPI-PCB zu tun zu haben. Schau mal hier: Firmware Update for HM-MOD-RPI-PCB


Und les dir in jedem Fall mal die Sachen über AES durch. Der von dir verwendete rfKey ist denkbar schlecht: Grundlagen Homegear / Starter-Guide - Abschnitt AES und https://wiki.fhem.de/wiki/AES_Encryption#Hinweise

@job, hast du noch ne Idee?


#6

Also ich hab bei mir in der config noch dtoverlay=pi3-miniuart-wifi drin stehen. Allerdings habe ich den HM_MOD-RPI-PCB aktuell nicht mehr im Einsatz.


#7

Die Firmware habe ich aktualisiert, die rules-Datei gelöscht… der Fehler bleibt :frowning: Vielleicht ist ja doch das Modul defekt?!?

Ich habe mal versucht mit den Windows-Tools von Homematic auf die “ccu” zu konnekten. Das scheint zu klappen. Allerdings erscheint beim Aufruf des Punktes “Einstellungen” immer die Fehlermeldung “An internal error was detected in the service software”


#8

Schau mal hier:


#9

Ok schmunzel aber ja…das andere dort ist eingestellt.

Schade das der Homegear keine Statusinformationen rausgibt… ein Punkt “-status” wäre ja vielleicht hilfreich.


#10

Würdest du bitte deine Beiträge editieren und die Formatierungsfunktionen des Forums nutzen? Danke :slight_smile:


Du solltest ziemlich viele Info’s in /var/log/homegear/homegear.log finden. In der Config und mit der Homegear-Konsole kannst du das debug level hochsetzen.

Was sagt denn das Log bei einem Start von homegear?


#11
02/20/18 22:04:56.878 Starting Homegear...
02/20/18 22:04:56.878 Homegear version 0.7.15-1580
02/20/18 22:04:56.878 Git commit SHA of libhomegear-base: -
02/20/18 22:04:56.878 Git branch of libhomegear-base:     -
02/20/18 22:04:56.878 Git commit SHA of Homegear:         -
02/20/18 22:04:56.878 Git branch of Homegear:             -
02/20/18 22:04:56.879 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0.
02/20/18 22:04:56.880 Info: Core file size now is "4294967295".
02/20/18 22:04:56.880 Info: Setting maximum thread priority to "4294967295" for user with id 0 and group with id 0.
02/20/18 22:04:56.880 Info: Maximum thread priority now is "4294967295".
02/20/18 22:04:57.063 Info: Backing up database...
02/20/18 22:04:57.216 Initializing database...
02/20/18 22:04:57.232 Info: Loading family module mod_homematicbidcos.so
02/20/18 22:04:57.323 /etc/homegear/families/homematicbidcos.conf
02/20/18 22:04:57.406 Info: Loading family module mod_miscellaneous.so
02/20/18 22:04:57.445 /etc/homegear/families/miscellaneous.conf
02/20/18 22:04:57.445 Info: Loading family module mod_homematicwired.so
02/20/18 22:04:57.503 /etc/homegear/families/homematicwired.conf
02/20/18 22:04:57.507 Info: Setting up physical interfaces and GPIOs...
02/20/18 22:04:57.526 Info: Dropping privileges to user homegear (111) and group homegear (116)
02/20/18 22:04:57.526 Info: Homegear is (now) running as user with id 111 and group with id 116.
02/20/18 22:04:57.560 Starting script engine server...
02/20/18 22:04:57.575 Initializing licensing controller...
02/20/18 22:04:57.576 Loading licensing controller data...
02/20/18 22:04:57.576 Loading devices...
02/20/18 22:04:57.576 Loading XML RPC devices...
02/20/18 22:04:59.574 Loading device 2
02/20/18 22:04:59.574 Module HomeMatic BidCoS: Info: Central address set to 0xFDDDE0.
02/20/18 22:04:59.614 Info: Not initializing device family HomeMatic Wired, because no physical interface was found.
02/20/18 22:04:59.614 Info: Disposing family module mod_homematicwired.so
02/20/18 22:04:59.624 Loading XML RPC devices...
02/20/18 22:04:59.633 Loading device 1
02/20/18 22:04:59.642 Initializing RPC client...
02/20/18 22:04:59.642 Starting XML RPC server RPCServer1 listening on :::2001...
02/20/18 22:04:59.645 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
02/20/18 22:04:59.645 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
02/20/18 22:04:59.740 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
02/20/18 22:04:59.740 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
02/20/18 22:04:59.771 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.33:47945 accepted. Client number: 5
02/20/18 22:04:59.771 RPC Server (Port 2001): Info: RPC server client id for client number 5 is: 0
02/20/18 22:04:59.772 RPC Server (Port 2001): Info: Client number 5 is calling RPC method: listBidcosInterfaces (2) Parameters:
02/20/18 22:04:59.775 Starting CLI server...
02/20/18 22:04:59.775 RPC Server (Port 2003): Info: RPC Server started listening on address :: and port 2003
02/20/18 22:04:59.775 Initializing event handler...
02/20/18 22:04:59.775 Loading events...
02/20/18 22:04:59.776 Starting flows server...
02/20/18 22:04:59.781 Starting IPC server...
02/20/18 22:04:59.785 Start listening for packets...
02/20/18 22:05:01.793 Startup complete. Waiting for physical interfaces to connect.
02/20/18 22:05:01.793 All physical interfaces are connected now.
02/20/18 22:05:01.793 Starting UPnP server...
02/20/18 22:05:01.794 Info: UPnP server: Binding to address: 192.168.178.28
02/20/18 22:05:01.794 UPnP Server: Info: Started listening.
02/20/18 22:05:04.235 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "SC-HM-MOD-RPI-PCB": Info: Firmware version: 1.4.1
02/20/18 22:05:04.242 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "SC-HM-MOD-RPI-PCB": Info: Serial number: OEQ2297160
02/20/18 22:05:04.257 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "SC-HM-MOD-RPI-PCB": Info: Init queue completed. Sending peers...
02/20/18 22:05:04.257 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "SC-HM-MOD-RPI-PCB": Info: Peer sending completed.
02/20/18 22:05:04.794 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.33:47951 accepted. Client number: 13
02/20/18 22:05:04.794 RPC Server (Port 2001): Info: RPC server client id for client number 13 is: 1
02/20/18 22:05:04.794 RPC Server (Port 2001): Info: Client number 13 is calling RPC method: listBidcosInterfaces (2) Parameters:
02/20/18 22:05:07.365 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.33:47955 accepted. Client number: 14
02/20/18 22:05:07.365 RPC Server (Port 2001): Info: RPC server client id for client number 14 is: 2
02/20/18 22:05:07.595 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.33:47956 accepted. Client number: 15
02/20/18 22:05:07.595 RPC Server (Port 2001): Info: RPC server client id for client number 15 is: 3

#12
02/20/18 22:05:01.793 Startup complete. Waiting for physical interfaces to connect.
02/20/18 22:05:01.793 All physical interfaces are connected now.
...
02/20/18 22:05:04.235 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "SC-HM-MOD-RPI-PCB": Info: Firmware version: 1.4.1
02/20/18 22:05:04.242 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "SC-HM-MOD-RPI-PCB": Info: Serial number: OEQ2297160
02/20/18 22:05:04.257 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "SC-HM-MOD-RPI-PCB": Info: Init queue completed. Sending peers...
02/20/18 22:05:04.257 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "SC-HM-MOD-RPI-PCB": Info: Peer sending completed.

Das hier sieht meiner Meinung nach sehr gut aus. Homegear kommt an dein HM-MOD-RPI-PCB. Sollte eigentlich funktionieren.

Was passiert, wenn du ein Gerät anlernen willst?


#13

es klappt… froi

Danke schön… nun kann ich die ganzen Ventile anlernen…


#14

Isses ok…wenn ich hier weitermache???

Nun kommt im Openhab2

2018-02-20 22:36:57.985 [thome.event.ExtensionEvent] - Extension 'binding-homematic' has been installed.

2018-02-20 22:36:58.005 [hingStatusInfoChangedEvent] - 'homematic:bridge:98933067' changed from UNINITIALIZED to INITIALIZING

==> /var/log/openhab2/openhab.log <==

2018-02-20 22:36:58.254 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'WIRED' on gateway '98933067' not available, disabling support

2018-02-20 22:36:58.263 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'HMIP' on gateway '98933067' not available, disabling support

2018-02-20 22:36:58.268 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'CUXD' on gateway '98933067' not available, disabling support

2018-02-20 22:36:58.273 [INFO ] [ternal.communicator.client.RpcClient] - Interface 'GROUP' on gateway '98933067' not available, disabling support

2018-02-20 22:36:58.353 [INFO ] [ommunicator.AbstractHomematicGateway] - HmGatewayInfo[id=HOMEGEAR,type=Homegear,firmware=0.7.15-1580,address=VBC5190872,wired=false,hmip=false,cuxd=false,group=false]

2018-02-20 22:36:58.656 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'homematic:HG-HM-CC-RT-DN:98933067:NEQ0309523' to inbox.

==> /var/log/openhab2/events.log <==

2018-02-20 22:36:58.661 [home.event.InboxAddedEvent] - Discovery Result with UID 'homematic:HG-HM-CC-RT-DN:98933067:NEQ0309523' has been added.

==> /var/log/openhab2/openhab.log <==

2018-02-20 22:36:58.670 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'ReadMe.txt' contains invalid characters, new Datapoint name 'ReadMe_txt'

2018-02-20 22:36:58.672 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'Test.php' contains invalid characters, new Datapoint name 'Test_php'

2018-02-20 22:36:58.674 [INFO ] [ng.homematic.internal.misc.MiscUtils] - Datapoint name 'Connect.php' contains invalid characters, new Datapoint name 'Connect_php'

==> /var/log/openhab2/events.log <==

2018-02-20 22:36:58.691 [hingStatusInfoChangedEvent] - 'homematic:bridge:98933067' changed from INITIALIZING to ONLINE

#15

Entschuldige, aber was ist die Frage?

:wink:

Oder was ist das Problem?

Deine Bridge und dein Heizkörperthermostat sind in openHAB angekommen.


#16

3 posts were split to a new topic: Inbetriebnahme HM-RPI-MOD-PCB