Homegear + Homematic-IP + HM-MOD-RPI-PCB pairing geht nicht

Johnny · January 15, 2018, 7:12pm

Hi,

ich verwende einen PI Version 3B mit dem Homegear Linux Image. Ich habe den HM-MOD-RPI-PCB selbst gelötet und vorher auf Homematik getestet - da geht das Paring, ich sehe die Devices und kann auch die Werte auslesen (z.B. Temperatur von HmIP-STHD).

Ich bekomme aber unter Homegear kein Pairing hin:

root@homegearpi-f7-f6-d5:/home/pi# homegear -r
01/10/18 10:50:01.751 Debug: debugLevel set to 6
01/10/18 10:50:01.752 Debug: memoryDebugging set to 1
01/10/18 10:50:01.752 Debug: devLog set to 1
01/10/18 10:50:01.752 Debug: enableCoreDumps set to 1
01/10/18 10:50:01.752 Debug: setDevicePermissions set to 1
01/10/18 10:50:01.752 Debug: workingDirectory set to /var/lib/homegear/
01/10/18 10:50:01.752 Debug: socketPath set to /var/run/homegear/
01/10/18 10:50:01.752 Debug: dataPath set to /var/lib/homegear/
01/10/18 10:50:01.752 Debug: familyDataPath set to /var/lib/homegear/families/
01/10/18 10:50:01.752 Debug: databaseMemoryJournal set to 0
01/10/18 10:50:01.752 Debug: databaseWALJournal set to 1
01/10/18 10:50:01.752 Debug: databaseSynchronous set to 1
01/10/18 10:50:01.752 Debug: databaseMaxBackups set to 10
01/10/18 10:50:01.752 Debug: logfilePath set to /var/log/homegear/
01/10/18 10:50:01.752 Debug: enableUPnP set to 1
01/10/18 10:50:01.752 Debug: uPnPIpAddress set to enxb827eba91c5b
01/10/18 10:50:01.753 Debug: caPath set to /etc/homegear/homegearca.crt
01/10/18 10:50:01.753 Debug: certPath set to /etc/homegear/homegear.crt
01/10/18 10:50:01.753 Debug: keyPath set to /etc/homegear/homegear.key
01/10/18 10:50:01.753 Debug: loadDHParamsFromFile set to 1
01/10/18 10:50:01.753 Debug: dhParamPath set to /etc/homegear/dh1024.pem
01/10/18 10:50:01.753 Debug: deviceDescriptionPath set to /etc/homegear/devices/
01/10/18 10:50:01.753 Debug: clientSettingsPath set to /etc/homegear/rpcclients.conf
01/10/18 10:50:01.753 Debug: serverSettingsPath set to /etc/homegear/rpcservers.conf
01/10/18 10:50:01.753 Debug: mqttSettingsPath set to /etc/homegear/mqtt.conf
01/10/18 10:50:01.753 Debug: familyConfigPath set to /etc/homegear/families/
01/10/18 10:50:01.753 Debug: phpIniPath set to /etc/homegear/php.ini
01/10/18 10:50:01.753 Debug: gpioPath set to /sys/class/gpio/
01/10/18 10:50:01.753 Debug: scriptPath set to /var/lib/homegear/scripts/
01/10/18 10:50:01.753 Debug: enableFlows set to 1
01/10/18 10:50:01.753 Debug: flowsPath set to /var/lib/homegear/flows/
01/10/18 10:50:01.754 Debug: flowsDataPath set to /var/lib/homegear/flows/data/
01/10/18 10:50:01.754 Debug: nodeBlueDebugOutput set to 1
01/10/18 10:50:01.754 Debug: libraryPath set to /var/lib/homegear/modules/
01/10/18 10:50:01.754 Debug: firmwarePath set to /usr/share/homegear/firmware/
01/10/18 10:50:01.754 Debug: tempPath set to /var/lib/homegear/tmp/
01/10/18 10:50:01.754 Debug: lockFilePath set to /var/run/homegear/
01/10/18 10:50:01.754 Debug: lockFilePathPermissions set to 504
01/10/18 10:50:01.754 Debug: lockFilePathUser set to homegear
01/10/18 10:50:01.754 Debug: lockFilePathGroup set to homegear
01/10/18 10:50:01.754 Debug: Added replaceClientServerAddress xmlrpc_bin://127.0.0.1:1999 xmlrpc_bin://$remoteip:1999
01/10/18 10:50:01.755 Debug: Added replaceClientServerAddress http://127.0.0.1:9292/bidcos http://$remoteip:9292/bidcos
01/10/18 10:50:01.755 Debug: prioritizeThreads set to 1
01/10/18 10:50:01.755 Debug: secureMemorySize set to 65536
01/10/18 10:50:01.755 Debug: workerThreadWindow set to 3000
01/10/18 10:50:01.755 Debug: scriptEngineMaxThreadsPerScript set to 4
01/10/18 10:50:01.755 Debug: scriptEngineMaxScriptsPerProcess set to 50
01/10/18 10:50:01.755 Debug: scriptEngineThreadCount set to 5
01/10/18 10:50:01.755 Debug: scriptEngineServerMaxConnections set to 10
01/10/18 10:50:01.755 Debug: scriptEngineWatchdogTimeout set to 60000
01/10/18 10:50:01.755 Debug: flowsProcessingThreadCountServer set to 5
01/10/18 10:50:01.755 Debug: flowsProcessingThreadCountNodes set to 10
01/10/18 10:50:01.755 Debug: flowsServerMaxConnections set to 50
01/10/18 10:50:01.755 Debug: maxNodeThreadsPerProcess set to 60
01/10/18 10:50:01.755 Debug: flowsWatchdogTimeout set to 60000
01/10/18 10:50:01.756 Debug: ipcThreadCount set to 5
01/10/18 10:50:01.756 Debug: ipsServerMaxConnections set to 20
01/10/18 10:50:01.756 Debug: cliServerMaxConnections set to 50
01/10/18 10:50:01.756 Debug: rpcServerMaxConnections set to 50
01/10/18 10:50:01.756 Debug: rpcServerThreadPriority set to 0
01/10/18 10:50:01.756 Debug: rpcServerThreadPolicy set to 0
01/10/18 10:50:01.756 Debug: rpcClientMaxThreads set to 50
01/10/18 10:50:01.756 Debug: rpcClientThreadPriority set to 0
01/10/18 10:50:01.756 Debug: rpcClientThreadPolicy set to 0
01/10/18 10:50:01.756 Debug: workerThreadPriority set to 0
01/10/18 10:50:01.756 Debug: workerThreadPolicy set to 0
01/10/18 10:50:01.756 Debug: physicalInterfaceThreadPriority set to 45
01/10/18 10:50:01.756 Debug: physicalInterfaceThreadPolicy set to 1
01/10/18 10:50:01.756 Debug: packetReceivedThreadPriority set to 0
01/10/18 10:50:01.757 Debug: packetReceivedThreadPolicy set to 0
01/10/18 10:50:01.757 Debug: eventThreadCount set to 5
01/10/18 10:50:01.757 Debug: eventThreadPriority set to 0
01/10/18 10:50:01.757 Debug: eventThreadPolicy set to 0
Debug: Trying to connect...
Connected to Homegear (version 0.7.12-1492).
>
Debug: Trying to connect...
Connected to Homegear (version 0.7.12-1492).
> ls
   ID ? Name
??????????????????????????????????????
    0 ? HomeMatic BidCoS
    6 ? Sonos
    9 ? Kodi
   10 ? IPCam
  254 ? Miscellaneous
??????????????????????????????????????
> fs 0
Device family "HomeMatic BidCoS" selected.
For information about the family's commands type: "help"
(Family)> pon
Pairing mode enabled for 60 seconds.
(Family)> ls
No peers are paired to this central.
(Family)> pon
Pairing mode enabled for 60 seconds.
(Family)> ls
No peers are paired to this central.
(Family)> pon
Pairing mode enabled for 60 seconds.
(Family)> ls
No peers are paired to this central.
(Family)>

(Taste am Fühler zum Anlernen ist natürlich gdrückt worden / Batterie neu eingelegt worden)

        homegear.log
01/10/18 10:49:40.919 Starting IPC server...
01/10/18 10:49:40.919 IPC Server: Debug: Waiting for IPC server's client threads to finish.
01/10/18 10:49:40.926 Start listening for packets...
01/10/18 10:49:42.935 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Connecting to HM-MOD-RPI-PCB...
01/10/18 10:49:42.936 Debug: GPIO 18 set to 0.
01/10/18 10:49:42.937 Startup complete. Waiting for physical interfaces to connect.
01/10/18 10:49:42.937 Module Sonos: Event server "My-Sonos-1234": Info: Started listening on address 10.10.10.78 and port 7373
01/10/18 10:49:42.937 All physical interfaces are connected now.
01/10/18 10:49:42.937 Starting UPnP server...
01/10/18 10:49:42.938 Info: UPnP server: Binding to address: 10.10.10.78
01/10/18 10:49:42.939 UPnP Server: Info: Started listening.
01/10/18 10:49:43.036 Debug: GPIO 18 set to 1.
01/10/18 10:49:43.936 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD000C000000436F5F4350555F424C7251
01/10/18 10:49:43.936 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000C000000436F5F4350555F424C7251
01/10/18 10:49:44.936 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD0003000003180A
01/10/18 10:49:45.362 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD000400000401993D
01/10/18 10:49:45.362 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000400000401993D
01/10/18 10:49:45.374 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD000D000000436F
01/10/18 10:49:45.375 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 5F4350555F417070
01/10/18 10:49:45.375 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: D831
01/10/18 10:49:45.375 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000D000000436F5F4350555F417070D831
01/10/18 10:49:45.375 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Co_CPU_App packet received.
01/10/18 10:49:45.376 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD00030001021E0C
01/10/18 10:49:45.378 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD000A0001040201
01/10/18 10:49:45.379 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 0003010401BE8A
01/10/18 10:49:45.379 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000A00010402010003010401BE8A
01/10/18 10:49:45.379 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Firmware version: 1.4.1
01/10/18 10:49:45.379 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD000400020A003D10
01/10/18 10:49:45.381 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD00040002040119
01/10/18 10:49:45.381 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 16
01/10/18 10:49:45.382 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0004000204011916
01/10/18 10:49:45.382 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD000300030B9239
01/10/18 10:49:45.384 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD000E000304024F
01/10/18 10:49:45.385 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 4551303330363936
01/10/18 10:49:45.385 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 385705
01/10/18 10:49:45.385 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000E000304024F4551303330363936385705
01/10/18 10:49:45.385 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Serial number: OEQ0306968
01/10/18 10:49:45.386 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD000800040E5A55EFC900CC47
01/10/18 10:49:45.388 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD00040004040119
01/10/18 10:49:45.389 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 6E
01/10/18 10:49:45.389 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD000400040401196E
01/10/18 10:49:45.389 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD0014010503A1FADE81BABE08C1A7DFF9C9E1D02AEC01CC37
01/10/18 10:49:45.394 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0004010504010D
01/10/18 10:49:45.395 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 7A
01/10/18 10:49:45.395 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0004010504010D7A
01/10/18 10:49:45.395 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD0006010600FC7DBABE6E09
01/10/18 10:49:45.398 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD0004010604010D
01/10/18 10:49:45.398 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 46
01/10/18 10:49:45.398 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0004010604010D46
01/10/18 10:49:45.398 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Sending: FD00030007068A17
01/10/18 10:49:45.401 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: FD00040007040119
01/10/18 10:49:45.401 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received. Raw data: 52
01/10/18 10:49:45.401 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Debug: Packet received from HM-MOD-RPI-PCB: FD0004000704011952
01/10/18 10:49:45.402 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Init queue completed. Sending peers...
01/10/18 10:49:45.402 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Info: Peer sending completed.
01/10/18 10:50:01.757 Info: CLI connection accepted. Client number: 13
01/10/18 10:50:01.767 Listening for incoming commands from client number 13.
01/10/18 10:50:42.015 UPnP Server: Debug: Sending notify packets.
01/10/18 10:51:42.009 UPnP Server: Debug: Sending notify packets.
01/10/18 10:51:48.697 Debug: SSDP server: Binding to address: 10.10.10.78
01/10/18 10:51:48.698 Debug: Searching for SSDP devices ...
01/10/18 10:52:19.914 Debug: SSDP server: Binding to address: 10.10.10.78
01/10/18 10:52:19.914 Debug: Searching for SSDP devices ...
01/10/18 10:52:42.085 UPnP Server: Debug: Sending notify packets.
01/10/18 10:52:45.630 Debug: SSDP server: Binding to address: 10.10.10.78
01/10/18 10:52:45.630 Debug: Searching for SSDP devices ...
01/10/18 10:53:11.346 Debug: SSDP server: Binding to address: 10.10.10.78
01/10/18 10:53:11.346 Debug: Searching for SSDP devices ...
01/10/18 10:53:37.062 Debug: SSDP server: Binding to address: 10.10.10.78
01/10/18 10:53:37.062 Debug: Searching for SSDP devices ...
01/10/18 10:53:42.061 UPnP Server: Debug: Sending notify packets.
01/10/18 10:54:02.773 Debug: SSDP server: Binding to address: 10.10.10.78
01/10/18 10:54:02.773 Debug: Searching for SSDP devices ...
01/10/18 10:54:25.404 Info: Connection to CLI client number 13 closed.
01/10/18 10:54:28.490 Debug: SSDP server: Binding to address: 10.10.10.78
01/10/18 10:54:28.490 Debug: Searching for SSDP devices ...
01/10/18 10:54:42.031 UPnP Server: Debug: Sending notify packets.
01/10/18 10:54:43.041 Debug: Joining read thread of CLI client 0
01/10/18 10:54:43.042 Debug: CLI client 0 removed.
root@homegearpi-f7-f6-d5:/home/pi#



root@homegearpi-f7-f6-d5:/home/pi# cat /var/log/homegear/homegear.err
01/10/18 10:49:37.781 Error: Cannot move file: /var/lib/homegear/db.sql.bak3
01/10/18 10:49:37.781 Error: Cannot move file: /var/lib/homegear/db.sql.bak2
01/10/18 10:49:37.782 Error: Cannot move file: /var/lib/homegear/db.sql.bak1
01/10/18 10:49:37.782 Error: Cannot move file: /var/lib/homegear/db.sql.bak0
01/10/18 10:49:37.782 Error copying file /var/lib/homegear/db.sql: Read-only file system
01/10/18 10:49:37.782 Error: Cannot copy file: /var/lib/homegear/db.sql.bak0
01/10/18 10:49:37.788 Warning: Can't execute "VACUUM": attempt to write a readonly database
01/10/18 10:49:37.792 Can't execute "PRAGMA journal_mode=WAL": attempt to write a readonly database
01/10/18 10:49:37.807 Could not set owner on /var/lib/homegear/db.sql.bak1
01/10/18 10:49:37.807 Could not set permissions on /var/lib/homegear/db.sql.bak1
01/10/18 10:49:37.807 Could not set owner on /var/lib/homegear/db.sql.bak0
01/10/18 10:49:37.808 Could not set permissions on /var/lib/homegear/db.sql.bak0
01/10/18 10:49:37.808 Could not set owner on /var/lib/homegear/db.sql
01/10/18 10:49:37.808 Could not set permissions on /var/lib/homegear/db.sql
01/10/18 10:49:37.808 Could not set owner on /var/lib/homegear/db.sql.bak2
01/10/18 10:49:37.808 Could not set permissions on /var/lib/homegear/db.sql.bak2
01/10/18 10:49:37.808 Could not set owner on /var/lib/homegear/db.sql.bak3
01/10/18 10:49:37.808 Could not set permissions on /var/lib/homegear/db.sql.bak3
01/10/18 10:49:40.613 Can't execute command "REPLACE INTO devices VALUES(?, ?, ?, ?, ?)": attempt to write a readonly database
01/10/18 10:49:40.652 Warning: Unknown parameter property: label
01/10/18 10:49:40.652 Warning: Unknown parameter property: label
root@homegearpi-f7-f6-d5:/home/pi#

Ich hatte das Modul vorher per Anleitung geflasht:

root@homegearpi-f7-f6-d5:/home/pi# cd hmcfgusb/
root@homegearpi-f7-f6-d5:/home/pi/hmcfgusb# ./flash-hmmoduart -U /dev/ttyAMA0 ./coprocessor_update.eq3

HM-MOD-UART flasher version 0.103-git

Reading firmware from ../coprocessor_update.eq3...
Firmware with 43 blocks successfully read.

Initializing HM-MOD-UART...
Waiting for bootloader to settle...
HM-MOD-UART opened.

Flashing 43 blocks: |

Firmware update successfull!

Zum Pairen stehen mir zur Verfügung:

2x HmIP-STHD Temp. and Humidity Sensor
1x HMIP-SWDO Fenster und Türkontakt

hmmm… irgendwie weiß ich nicht weiter: MIr bleiben noch

Firmware Problem auf dem Modul
Termostate haben immer noch alte Config trotz reset
???

Kann da jemand helfen?

Viele Grüße & Danke,

John

pmayer · January 10, 2018, 7:17pm

Hey @Johnny,

hast du den UART vorher freigeräumt?

https://doc.homegear.eu/data/homegear-homematicbidcos/configuration.html#homematic-wireless-module-for-raspberry-pi-hm-mod-rpi-pcb - 5.2.6.1.2. und 5.2.6.1.3.

Auf den ersten Block würde ich sagen, sieht es nach einem Berechtigungsproblem aus.

Denk bitte dran, dass du die Geräte vorher ordentlich abgelernt und werksresettet haben musst und dass du in der homematicbidcos.conf ein ordentliche centralAddress und einen ordentlichen rfKey konfigurierst.
Allgemein gilt bei Homematic mit AES: https://wiki.fhem.de/wiki/AES_Encryption#Hinweise

so long,
p

Johnny · January 15, 2018, 11:33am

Servus @pmayer,

DANKE für Deine schnelle Antwort!

also die UART Anweisungen habe ich befolgt:

root@homegearpi-f7-f6-d5:/home/pi# cat /boot/cmdline.txt
dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait

Eine inittab hat Euer Image nicht:

root@homegearpi-f7-f6-d5:/home/pi# find / -iname inittab
root@homegearpi-f7-f6-d5:/home/pi#


root@homegearpi-f7-f6-d5:/home/pi# ls /dev/A*
ls: Zugriff auf '/dev/A*' nicht möglich: Datei oder Verzeichnis nicht gefunden

root@homegearpi-f7-f6-d5:/home/pi# ls -lah /dev/ttyAMA0
crw-rw---- 1 homegear homegear 204, 64 Jan 15 10:35 /dev/ttyAMA0


root@homegearpi-f7-f6-d5:/home/pi# cat /boot/config.txt
# 20180108 - johnny: Enabled for homegear
enable_uart=1
dtparam=spi=on
dtparam=i2c_arm=on
#gpu_mem=16
#dtoverlay=pi3-miniuart-bt
#dtoverlay=pi3-disable-bt

Test auf serial devices:

root@homegearpi-f7-f6-d5:/home/pi# systemctl status serial-getty@ttyAMA0.service
● serial-getty@ttyAMA0.service - Serial Getty on ttyAMA0
   Loaded: loaded (/lib/systemd/system/serial-getty@.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
     Docs: man:agetty(8)
           man:systemd-getty-generator(8)
           http://0pointer.de/blog/projects/serial-console.html

root@homegearpi-f7-f6-d5:/home/pi# systemctl status serial-getty@serial0.service
● serial-getty@serial0.service - Serial Getty on serial0
   Loaded: loaded (/lib/systemd/system/serial-getty@.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
     Docs: man:agetty(8)
           man:systemd-getty-generator(8)
           http://0pointer.de/blog/projects/serial-console.html

root@homegearpi-f7-f6-d5:/home/pi# systemctl status serial-getty@ttyS0.service
● serial-getty@ttyS0.service - Serial Getty on ttyS0
   Loaded: loaded (/lib/systemd/system/serial-getty@.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
     Docs: man:agetty(8)
           man:systemd-getty-generator(8)
           http://0pointer.de/blog/projects/serial-console.html
root@homegearpi-f7-f6-d5:/home/pi#

Test mit neuem Aktor:
Habe nun zum Anlernen ein fabrikneues Thermostat HMIP-eTRV genommen, Debuglevel 6:

root@homegearpi-f7-f6-d5:/home/pi# homegear -r
01/15/18 11:14:36.382 Debug: debugLevel set to 6
01/15/18 11:14:36.382 Debug: memoryDebugging set to 1
01/15/18 11:14:36.382 Debug: devLog set to 1
01/15/18 11:14:36.382 Debug: enableCoreDumps set to 1
01/15/18 11:14:36.383 Debug: setDevicePermissions set to 1
01/15/18 11:14:36.383 Debug: workingDirectory set to /var/lib/homegear/
01/15/18 11:14:36.383 Debug: socketPath set to /var/run/homegear/
01/15/18 11:14:36.383 Debug: dataPath set to /var/lib/homegear/
01/15/18 11:14:36.383 Debug: familyDataPath set to /var/lib/homegear/families/
01/15/18 11:14:36.383 Debug: databaseMemoryJournal set to 0
01/15/18 11:14:36.383 Debug: databaseWALJournal set to 1
01/15/18 11:14:36.383 Debug: databaseSynchronous set to 1
01/15/18 11:14:36.383 Debug: databaseMaxBackups set to 10
01/15/18 11:14:36.383 Debug: logfilePath set to /var/log/homegear/
01/15/18 11:14:36.383 Debug: enableUPnP set to 1
01/15/18 11:14:36.383 Debug: uPnPIpAddress set to enxb827eba91c5b
01/15/18 11:14:36.383 Debug: caPath set to /etc/homegear/homegearca.crt
01/15/18 11:14:36.383 Debug: certPath set to /etc/homegear/homegear.crt
01/15/18 11:14:36.383 Debug: keyPath set to /etc/homegear/homegear.key
01/15/18 11:14:36.383 Debug: loadDHParamsFromFile set to 1
01/15/18 11:14:36.384 Debug: dhParamPath set to /etc/homegear/dh1024.pem
01/15/18 11:14:36.384 Debug: deviceDescriptionPath set to /etc/homegear/devices/
01/15/18 11:14:36.384 Debug: clientSettingsPath set to /etc/homegear/rpcclients.conf
01/15/18 11:14:36.384 Debug: serverSettingsPath set to /etc/homegear/rpcservers.conf
01/15/18 11:14:36.384 Debug: mqttSettingsPath set to /etc/homegear/mqtt.conf
01/15/18 11:14:36.384 Debug: familyConfigPath set to /etc/homegear/families/
01/15/18 11:14:36.384 Debug: phpIniPath set to /etc/homegear/php.ini
01/15/18 11:14:36.384 Debug: gpioPath set to /sys/class/gpio/
01/15/18 11:14:36.384 Debug: scriptPath set to /var/lib/homegear/scripts/
01/15/18 11:14:36.384 Debug: enableFlows set to 1
01/15/18 11:14:36.384 Debug: flowsPath set to /var/lib/homegear/flows/
01/15/18 11:14:36.384 Debug: flowsDataPath set to /var/lib/homegear/flows/data/
01/15/18 11:14:36.384 Debug: nodeBlueDebugOutput set to 1
01/15/18 11:14:36.384 Debug: libraryPath set to /var/lib/homegear/modules/
01/15/18 11:14:36.385 Debug: firmwarePath set to /usr/share/homegear/firmware/
01/15/18 11:14:36.385 Debug: tempPath set to /var/lib/homegear/tmp/
01/15/18 11:14:36.385 Debug: lockFilePath set to /var/run/homegear/
01/15/18 11:14:36.385 Debug: lockFilePathPermissions set to 504
01/15/18 11:14:36.385 Debug: lockFilePathUser set to homegear
01/15/18 11:14:36.385 Debug: lockFilePathGroup set to homegear
01/15/18 11:14:36.385 Debug: Added replaceClientServerAddress xmlrpc_bin://127.0.0.1:1999 xmlrpc_bin://$remoteip:1999
01/15/18 11:14:36.385 Debug: Added replaceClientServerAddress http://127.0.0.1:9292/bidcos http://$remoteip:9292/bidcos
01/15/18 11:14:36.385 Debug: prioritizeThreads set to 1
01/15/18 11:14:36.386 Debug: secureMemorySize set to 65536
01/15/18 11:14:36.386 Debug: workerThreadWindow set to 3000
01/15/18 11:14:36.386 Debug: scriptEngineMaxThreadsPerScript set to 4
01/15/18 11:14:36.386 Debug: scriptEngineMaxScriptsPerProcess set to 50
01/15/18 11:14:36.386 Debug: scriptEngineThreadCount set to 5
01/15/18 11:14:36.386 Debug: scriptEngineServerMaxConnections set to 10
01/15/18 11:14:36.386 Debug: scriptEngineWatchdogTimeout set to 60000
01/15/18 11:14:36.386 Debug: flowsProcessingThreadCountServer set to 5
01/15/18 11:14:36.386 Debug: flowsProcessingThreadCountNodes set to 10
01/15/18 11:14:36.386 Debug: flowsServerMaxConnections set to 50
01/15/18 11:14:36.386 Debug: maxNodeThreadsPerProcess set to 60
01/15/18 11:14:36.386 Debug: flowsWatchdogTimeout set to 60000
01/15/18 11:14:36.386 Debug: ipcThreadCount set to 5
01/15/18 11:14:36.386 Debug: ipsServerMaxConnections set to 20
01/15/18 11:14:36.386 Debug: cliServerMaxConnections set to 50
01/15/18 11:14:36.387 Debug: rpcServerMaxConnections set to 50
01/15/18 11:14:36.387 Debug: rpcServerThreadPriority set to 0
01/15/18 11:14:36.387 Debug: rpcServerThreadPolicy set to 0
01/15/18 11:14:36.387 Debug: rpcClientMaxThreads set to 50
01/15/18 11:14:36.387 Debug: rpcClientThreadPriority set to 0
01/15/18 11:14:36.387 Debug: rpcClientThreadPolicy set to 0
01/15/18 11:14:36.387 Debug: workerThreadPriority set to 0
01/15/18 11:14:36.387 Debug: workerThreadPolicy set to 0
01/15/18 11:14:36.387 Debug: physicalInterfaceThreadPriority set to 45
01/15/18 11:14:36.387 Debug: physicalInterfaceThreadPolicy set to 1
01/15/18 11:14:36.387 Debug: packetReceivedThreadPriority set to 0
01/15/18 11:14:36.387 Debug: packetReceivedThreadPolicy set to 0
01/15/18 11:14:36.387 Debug: eventThreadCount set to 5
01/15/18 11:14:36.387 Debug: eventThreadPriority set to 0
01/15/18 11:14:36.388 Debug: eventThreadPolicy set to 0
Debug: Trying to connect...
Connected to Homegear (version 0.7.12-1492).
**> fs 0**

** Device family “HomeMatic BidCoS” selected.**
** For information about the family’s commands type: “help”**
** (Family)> pon**
** Pairing mode enabled for 60 seconds.**
** (Family)> ls**
** No peers are paired to this central.**

centraladdress und rfkey sind in selber Länge wie Vorgabe hexadezimal konfiguriert. Mit emacs auf Sonderzeichen gecheckt - Zeilen sind sauber.

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

## The device family this interface is for

#20180108 - be safe to have the [WHOLE AREA UNCOMMENTED]
[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

hmmm… ich teste heute Abend nochmal eine CCU auf Raspian, gestartet auf selbem PI mit anderer SD- wenn es dort geht, dann kann es nur noch an der Konfig liegen (wovon ich immer noch ausgehe)…

Viele Grüße

Johnny

pmayer · January 15, 2018, 11:34am

Zum Image muss @sathya was sagen. Ich meine aber, dass da schon die system-config für das HM-MOD-RPI-PCB gemacht sein sollte.

Johnny · January 15, 2018, 7:08pm

Hi @pmayer und @sathya,

hier noch ein Update, das für Euch interessant sein könnte:

Ich habe die selbe Hardware nun nochmal mit einer anderen SD Karte und Rasperrymatik gestartet. Alle 2 Thermostate gingen sofort anzulernen und auch die 3 Temp. / Feuchtemesser wurden binnen 10sec. angelernt.
Ich habe nach dem erfolgreichen Test alle Geräte gelöscht und auf Werkeinstellungen zurückgesetzt.

Habe danach nochmal die SD mit Eurem Image und der oben beschriebenen Konfig eingelegt und mit fs0 und pon in homegear versucht, die Geräte zu pairen. Dort funktioniert das Anlernen nicht. Anlernmodus bei den Gräten habe ich bei beiden Images glichartig vorgenommen (Batterien raus und Taster drücken --> Reset)…

Es ist also kein Hardwareproblem, sondern es muss mit der Konfig oder Eurem Image zusammenhängen. Fehlt da vielleicht ein Modul oder ein Stückchen Code für Homematik IP?

pmayer · January 26, 2019, 5:17pm

Sorry, hatte nicht mitbekommen, dass es hier um Homematic-IP geht. Homegear unterstützt zu diesem Zeitpunkt überhaupt kein Homematic-IP.

Homematic BidCOS != Homematic IP

Tut mir leid, dass du dir die ganze Mühe gemacht hast…

Johnny · January 15, 2018, 7:17pm

@pmayer, @sathya

Ahhhhh… das muss ich wohl irgendwie überlesen haben. dann solltet Ihr in der Config vielleicht auch noch kennzeichnen, dass es mometan keine Unterstützung von Homematik IP gibt.

Gibt es einen Plan, Homematik IP irgendwann zu unterstützen? So ein bisschen Sichrheit (AES 128) finde ich eigentlich schon ganz gut… auch wenn der Aufwand höher ist!

pmayer · January 15, 2018, 7:25pm

Der Name der Konfigurationsdatei homematicbidcos.conf verrät das schon recht genau

Mit AES128 werden auch Kommandos bei Homematic signiert - aber du hast natürlich recht, dass es schön wäre wenn Homematic-IP unterstützt wird.
Meine Information nach steht momentan die Z-Wave-Unterstützung ganz oben auf dem Programm. Wenn andere Projekte (Open-Source) allerdings Homematic-IP implementiert haben, sollte es nicht so ein großes Problem sein.

Siehe dazu auch hier: Neues Homematic Protokoll "Homematic IP" auf Basis von IPv6/AES128-CCM

Da muss @sathya aber was zu sagen.

Micha · January 16, 2018, 9:09pm

Also der Stick funktioniert (noch) nicht, aber ueber den Umweg mit einer CCU2 (siehe “HomeMatic CCU2” im Nightly) sollte es funktionieren. HmIP konnte ich bislang damit leider noch nicht testen, da ich nur “classic” HomeMatic hier habe … das steht aber fuer die kommenden Tage auf meiner ToDo-Liste.

Theoretisch sollte es auch mit Raspberrymatic funktionieren …

– Micha

Johnny · January 26, 2018, 5:18pm

@pmayer
Nun ja, die homematicbidcos.conf ist ja auch für das Funkmodul. Und das kann nun mal auch die Homematik IP ansteuern -. oder?

Johnny · January 26, 2018, 5:20pm

@Micha
ich hatte halt’ gehofft, Raspberrymatik komplett umgehen zu können…

So hat Sicherheit immer einen steinigeren Weg als die einfache Lösung…

Micha · January 26, 2018, 5:39pm

@Johnny naja, Du nutzt es dann nur als “besseres” Mediagateway Du brauchst im Prinzip (ausser fuer die Ersteinrichtung) noch nicht mal die WebUI von Raspberrymatic, das komplette Device-Handling (inkl. An-/Ablernen) kann ueber Homegear erfolgen. Ich bin mir grad allerdings nicht sicher, ob die Doku fuer das neue CCU2-Modul schon online ist

HmIP funktioniert btw. mit der CCU2 ohne Probleme, eben erst getestet. Sollte also mit Raspberrymatic auch tun.

– Micha

Johnny · January 26, 2018, 5:50pm

@Micha
Ich habe die Homematik IP Thermostate und Heizungsregler - wie ich schon schrieb…

Eigentlich will ich ja nur dié Hardware (HM-MOD-RPI-PCB) als Sender / Empfänger und dann selbst definieren können, was und wann passieren soll…

Aber es is Homematik IP

pmayer · January 26, 2018, 6:45pm

Homematic BidCos != Homematic IP