HM-MOD-RPI-PCB Anlernproblem

[tSaM89]

Hallo zusammen.

Zuerst einmal die Vorgeschichte.

Ich habe einen Pi 3 mit dem “HM-MOD-RPI-PCB” Funkmodul.
Dieses hatte ich zuvor mir openHAB 2 und homegear mit zwei Funktastern ( HomeMatic Funk-Tasterschnittstelle 4-fach) im Einsatz. Das funktionierte auch problemlos.

Die Konfiguration habe ich wie hier beschrieben vorgenommen: link

Jetzt habe ich openHAB 3 installiert und alles wie zuvor gemacht.
Leider funktioniert es nicht. Die Installation lief problemlos, nur das Anlernen der beiden Funktaster funktioniert nicht.

Mir fehlt leider jeglicher Anhaltspunkt für die Fehlersuche.
Wie kann ich Prüfen ob homegear mit dem “HM-MOD-RPI-PCB” Funkmodul kommunizieren kann?
Ist bei dem “erneuten” Binden der Funktaster etwas anders als beim ersten Mal?

Ich bin über jede Hilfe dankbar

[pmayer]

Hey tsa,

willkommen im Forum.

Openhab hat grundliegend erst mal nichts mit Homegear zu tun - sprich, die können auch völlig unabhängig voneinander existieren.

Was hast du denn in homegear konfiguriert? /etc/homegear/families/homematicbidcos.conf?
Was steht im Log beim starten von Homegear? /var/log/homegear/homegear.log

Das Backup deiner alten Homegear-Installation könntest du zum Beispiel wie hier beschrieben übernehmen:

Hardwarewechsel vom Pi3 auf den Pi4

Nachdem hier einige Probleme bzgl. Hardwarewechsel von RaspberryPi 3 auf den RaspberryPi 4 waren, habe ich das mal durchgeführt. (Der Plan war schon länger da, ich hatte nur bisher keine Lust.) Das alles habe ich mit @pmayer s CC1101-Modul gemacht. (Kein LAN-GW und auch kein HM-MOD-RPI-PCB). Wechseln nach root (auf beiden Pis) sudo -s Auslesen von /boot/config.txt auf Pi3 und Anpassen der relevanten Einträge auf Pi4: dtparam=i2c_arm=on dtparam=spi=on Beenden von Homegear auf Pi3 sy…

Gruß,
p

[tSaM89]

Ein Backup habe ich natürlich nicht.

In der “/etc/homegear/families/homematicbidcos.conf” habe ich folgendes “einkommentiert”:

[HomeMatic Wireless Module for Raspberry Pi]

id = My-HM-MOD-RPI-PCB

default = true

deviceType = hm-mod-rpi-pcb

device = /dev/ttyAMA0

responseDelay = 95

gpio1 = 18

Und hier der Log “/var/log/homegear/homegear.log”:

03/21/21 13:42:04.369 Starting Homegear...
03/21/21 13:42:04.369 Homegear version: 0.7.48-3324
03/21/21 13:42:04.369 Determining maximum thread count...
03/21/21 13:42:05.514 Maximum thread count is: 217
03/21/21 13:42:05.516 Warning: No database found. Trying to restore backup.
03/21/21 13:42:05.771 Warning: Database could not be restored. Creating new database.
03/21/21 13:42:05.804 Initializing database...
03/21/21 13:42:07.646 Default password for user "homegear" set to: gBC5Gf3a]L@:
03/21/21 13:42:07.646 Could not set owner on /var/lib/homegear/defaultPassword.txt
03/21/21 13:42:07.665 Homegear instance ID is 0005BE0B46F0E7DE-2A6A46ED-7580-289D-F568-683A8F748397
03/21/21 13:42:07.671 Homegear instance ID: 0005BE0B46F0E7DE-2A6A46ED-7580-289D-F568-683A8F748397
03/21/21 13:42:07.684 Debug: Loading licensing modules
03/21/21 13:42:07.684 Initializing system variable controller...
03/21/21 13:42:07.685 Debug: Loading family modules
03/21/21 13:42:07.685 Info: Loading family module (type 1) mod_homematicbidcos.so
03/21/21 13:42:07.706 Info: Loading settings from /etc/homegear/families/homematicbidcos.conf
03/21/21 13:42:07.718 Info: Loading family module (type 1) mod_max.so
03/21/21 13:42:07.727 Info: Loading settings from /etc/homegear/families/max.conf
03/21/21 13:42:07.727 Info: Loading family module (type 1) mod_miscellaneous.so
03/21/21 13:42:07.731 Info: Loading settings from /etc/homegear/families/miscellaneous.conf
03/21/21 13:42:07.736 Info: Loading family module (type 1) mod_homematicwired.so
03/21/21 13:42:07.742 Info: Loading settings from /etc/homegear/families/homematicwired.conf
03/21/21 13:42:07.743 Info: Homegear is (now) running as user with id 111 and group with id 118.
03/21/21 13:42:07.863 Starting script engine server...
03/21/21 13:42:07.936 Initializing licensing controller...
03/21/21 13:42:07.936 Loading licensing controller data...
03/21/21 13:42:07.936 Loading devices...
03/21/21 13:42:07.936 Loading XML RPC devices...
03/21/21 13:42:08.788 Module HomeMatic BidCoS: Created HomeMatic BidCoS central with id 0, address 0xFDACAA and serial number VBC6112802
03/21/21 13:42:08.799 Loading XML RPC devices...
03/21/21 13:42:08.847 Module HomeMatic Wired: Created HomeMatic Wired central with id 0, address 0x00000001 and serial number VWC8372208
03/21/21 13:42:08.859 Loading XML RPC devices...
03/21/21 13:42:08.954 Module MAX: Created MAX central with id 0, address 0xFD57F6 and serial number VBC6415663
03/21/21 13:42:08.967 Loading XML RPC devices...
03/21/21 13:42:08.980 Warning: configParameters with id "config" does not exist.
03/21/21 13:42:08.989 Warning: script2 in "runProgram" does not contain CDATA.
03/21/21 13:42:08.992 Warning: configParameters with id "config" does not exist.
03/21/21 13:42:08.995 Warning: variables with id "custom_ch7_values" does not exist.
03/21/21 13:42:09.000 Warning: variables with id "custom_ch7_values" does not exist.
03/21/21 13:42:09.003 Module Miscellaneous: Created Miscellaneous central with id 0.
03/21/21 13:42:09.009 Initializing RPC client...
03/21/21 13:42:09.010 Starting XML RPC server RPCServer1 listening on :::2001...
03/21/21 13:42:09.056 RPC Server (Port 2001): Warning: SSL is not enabled for this RPC server. It is strongly recommended to disable all unencrypted RPC servers when the connected clients support it.
03/21/21 13:42:09.057 RPC Server (Port 2001): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when the connected clients support it.
03/21/21 13:42:09.057 RPC Server (Port 2001): Info: Enabling no authentication.
03/21/21 13:42:09.057 RPC Server (Port 2001): Info: Enabling session authentication for WebSockets.
03/21/21 13:42:09.057 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
03/21/21 13:42:09.057 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
03/21/21 13:42:09.104 RPC Server (Port 2002): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when the connected clients support it.
03/21/21 13:42:09.104 RPC Server (Port 2002): Info: Enabling no authentication.
03/21/21 13:42:09.104 RPC Server (Port 2002): Info: Enabling session authentication for WebSockets.
03/21/21 13:42:09.151 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
03/21/21 13:42:09.151 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
03/21/21 13:42:09.197 RPC Server (Port 2003): Info: Enabling basic authentication.
03/21/21 13:42:09.197 RPC Server (Port 2003): Info: Enabling client certificate authentication.
03/21/21 13:42:09.197 RPC Server (Port 2003): Info: Enabling session authentication for WebSockets.
03/21/21 13:42:09.235 Starting XML RPC server RPCServer4 listening on ::1:2004...
03/21/21 13:42:09.282 RPC Server (Port 2004): Info: Enabling no authentication.
03/21/21 13:42:09.282 RPC Server (Port 2004): Info: Enabling session authentication for WebSockets.
03/21/21 13:42:09.282 RPC Server (Port 2004): Info: RPC Server started listening on address ::1 and port 2004
03/21/21 13:42:09.287 Initializing event handler...
03/21/21 13:42:09.287 Loading events...
03/21/21 13:42:09.288 Start listening for packets...
03/21/21 13:42:09.288 Starting IPC server...
03/21/21 13:42:09.294 Starting Node-BLUE server...
03/21/21 13:42:09.302 Error in file Node-BLUE/NodeManager.cpp line 197 in function static std::vector<std::shared_ptr<Homegear::NodeManager::NodeInfo> > Homegear::NodeManager::getNodeInfo(): Could not open directory "/var/lib/homegear/node-blue/nodes/"
03/21/21 13:42:09.309 Starting variable profile manager...
03/21/21 13:42:09.310 Startup complete. Waiting for physical interfaces to connect.
03/21/21 13:42:09.310 Info: Waiting for physical interfaces to connect (0 of 180s).
03/21/21 13:42:09.310 All physical interfaces are connected now.
03/21/21 13:42:09.310 Starting UPnP server...
03/21/21 13:42:14.311 UPnP Server: Info: UPnP server: Binding to address: 192.168.178.50
03/21/21 13:42:14.313 UPnP Server: Info: Created new UPnP UDN: 607D15BE-90E3-AE17-16DF-812BBB3FE773
03/21/21 13:42:18.257 IPC Server: Info: Connection accepted. Client number: 0, file descriptor ID: 7
03/21/21 13:42:18.259 IPC Server: Info: Client 0 successfully registered RPC method "managementGetCommandStatus" (this method is registered by 1 client(s)).
03/21/21 13:42:18.260 IPC Server: Info: Client 0 successfully registered RPC method "managementSleep" (this method is registered by 1 client(s)).
03/21/21 13:42:18.259 IPC Server: Info: Client 0 successfully registered RPC method "managementGetCommandStatus" (this method is registered by 1 client(s)).
03/21/21 13:42:18.260 IPC Server: Info: Client 0 successfully registered RPC method "managementSleep" (this method is registered by 1 client(s)).
03/21/21 13:42:18.261 IPC Server: Info: Client 0 successfully registered RPC method "managementDpkgPackageInstalled" (this method is registered by 1 client(s)).
03/21/21 13:42:18.262 IPC Server: Info: Client 0 successfully registered RPC method "managementGetSystemInfo" (this method is registered by 1 client(s)).
03/21/21 13:42:18.264 IPC Server: Info: Client 0 successfully registered RPC method "managementGetConfigurationEntry" (this method is registered by 1 client(s)).
03/21/21 13:42:18.265 IPC Server: Info: Client 0 successfully registered RPC method "managementServiceCommand" (this method is registered by 1 client(s)).
03/21/21 13:42:18.266 IPC Server: Info: Client 0 successfully registered RPC method "managementReboot" (this method is registered by 1 client(s)).
03/21/21 13:42:18.267 IPC Server: Info: Client 0 successfully registered RPC method "managementShutdown" (this method is registered by 1 client(s)).
03/21/21 13:42:18.268 IPC Server: Info: Client 0 successfully registered RPC method "managementSetConfigurationEntry" (this method is registered by 1 client(s)).
03/21/21 13:42:18.270 IPC Server: Info: Client 0 successfully registered RPC method "managementWriteCloudMaticConfig" (this method is registered by 1 client(s)).
03/21/21 13:42:18.271 IPC Server: Info: Client 0 successfully registered RPC method "managementSetUserPassword" (this method is registered by 1 client(s)).
03/21/21 13:42:18.272 IPC Server: Info: Client 0 successfully registered RPC method "managementInstallNode" (this method is registered by 1 client(s)).
03/21/21 13:42:18.273 IPC Server: Info: Client 0 successfully registered RPC method "managementUninstallNode" (this method is registered by 1 client(s)).
03/21/21 13:42:18.274 IPC Server: Info: Client 0 successfully registered RPC method "managementGetNodePackages" (this method is registered by 1 client(s)).
03/21/21 13:42:18.275 IPC Server: Info: Client 0 successfully registered RPC method "managementAptRunning" (this method is registered by 1 client(s)).
03/21/21 13:42:18.276 IPC Server: Info: Client 0 successfully registered RPC method "managementAptUpdate" (this method is registered by 1 client(s)).
03/21/21 13:42:18.277 IPC Server: Info: Client 0 successfully registered RPC method "managementAptUpgrade" (this method is registered by 1 client(s)).
03/21/21 13:42:18.278 IPC Server: Info: Client 0 successfully registered RPC method "managementAptUpgradeSpecific" (this method is registered by 1 client(s)).
03/21/21 13:42:18.279 IPC Server: Info: Client 0 successfully registered RPC method "managementAptFullUpgrade" (this method is registered by 1 client(s)).
03/21/21 13:42:18.279 IPC Server: Info: Client 0 successfully registered RPC method "managementHomegearUpdateAvailable" (this method is registered by 1 client(s)).
03/21/21 13:42:18.280 IPC Server: Info: Client 0 successfully registered RPC method "managementSystemUpdateAvailable" (this method is registered by 1 client(s)).
03/21/21 13:42:18.279 IPC Server: Info: Client 0 successfully registered RPC method "managementHomegearUpdateAvailable" (this method is registered by 1 client(s)).
03/21/21 13:42:18.280 IPC Server: Info: Client 0 successfully registered RPC method "managementSystemUpdateAvailable" (this method is registered by 1 client(s)).
03/21/21 13:42:18.281 IPC Server: Info: Client 0 successfully registered RPC method "managementAptInstall" (this method is registered by 1 client(s)).
03/21/21 13:42:18.282 IPC Server: Info: Client 0 successfully registered RPC method "managementAptRemove" (this method is registered by 1 client(s)).
03/21/21 13:42:18.283 IPC Server: Info: Client 0 successfully registered RPC method "managementCreateBackup" (this method is registered by 1 client(s)).
03/21/21 13:42:18.284 IPC Server: Info: Client 0 successfully registered RPC method "managementRestoreBackup" (this method is registered by 1 client(s)).
03/21/21 13:42:18.285 IPC Server: Info: Client 0 successfully registered RPC method "managementSystemReset" (this method is registered by 1 client(s)).
03/21/21 13:42:18.285 IPC Server: Info: Client 0 successfully registered RPC method "managementCaExists" (this method is registered by 1 client(s)).
03/21/21 13:42:18.286 IPC Server: Info: Client 0 successfully registered RPC method "managementCreateCa" (this method is registered by 1 client(s)).
03/21/21 13:42:18.286 IPC Server: Info: Client 0 successfully registered RPC method "managementCreateCert" (this method is registered by 1 client(s)).
03/21/21 13:42:18.287 IPC Server: Info: Client 0 successfully registered RPC method "managementDeleteCert" (this method is registered by 1 client(s)).
03/21/21 13:42:18.288 IPC Server: Info: Client 0 successfully registered RPC method "managementGetNetworkConfiguration" (this method is registered by 1 client(s)).
03/21/21 13:42:18.288 IPC Server: Info: Client 0 successfully registered RPC method "managementSetNetworkConfiguration" (this method is registered by 1 client(s)).
03/21/21 13:42:18.289 IPC Server: Info: Client 0 successfully registered RPC method "managementCopyDeviceDescriptionFile" (this method is registered by 1 client(s)).
03/21/21 13:42:18.290 IPC Server: Info: Client 0 successfully registered RPC method "managementUploadDeviceDescriptionFile" (this method is registered by 1 client(s)).
03/21/21 13:43:18.343 IPC Server: Info: Client number 0 is calling RPC method: lifetick Parameters:
03/21/21 13:44:18.396 IPC Server: Info: Client number 0 is calling RPC method: lifetick Parameters:
03/21/21 13:45:18.450 IPC Server: Info: Client number 0 is calling RPC method: lifetick Parameters:
03/21/21 13:45:52.909 IPC Server: Info: Connection to IPC server's client number 0 closed.
03/21/21 13:45:53.018 (Shutdown) => Stopping Homegear (Signal: 15)
03/21/21 13:45:54.019 IPC Server: Info: IPC client 0 removed.
03/21/21 13:45:54.027 Node-BLUE Server: Info: Stopping nodes.
03/21/21 13:45:54.027 Script Engine Server: Info: Stopping devices.
03/21/21 13:45:54.027 Info: Shutting down shared object family modules...
03/21/21 13:45:54.027 Info: Shutting down shared object family module "HomeMatic BidCoS"...
03/21/21 13:45:54.027 Info: Shutting down shared object family module "HomeMatic Wired"...
03/21/21 13:45:54.027 Info: Shutting down shared object family module "MAX!"...
03/21/21 13:45:54.027 Info: Shutting down shared object family module "Miscellaneous"...
03/21/21 13:45:54.027 Info: Shutting down shared object family module "MAX!"...
03/21/21 13:45:54.027 Info: Shutting down shared object family module "Miscellaneous"...
03/21/21 13:45:54.027 Stopping UPnP server...
03/21/21 13:45:54.076 (Shutdown) => Stopping Event handler
03/21/21 13:45:54.077 (Shutdown) => Stopping RPC servers
03/21/21 13:45:54.083 RPC Server (Port 2001): Info: Waiting for threads to finish.
03/21/21 13:45:54.177 RPC Server (Port 2002): Info: Waiting for threads to finish.
03/21/21 13:45:54.205 RPC Server (Port 2004): Info: Waiting for threads to finish.
03/21/21 13:45:54.208 (Shutdown) => Stopping RPC client
03/21/21 13:45:54.208 (Shutdown) => Closing physical interfaces...
03/21/21 13:45:54.208 (Shutdown) => Stopping IPC server...
03/21/21 13:45:54.215 (Shutdown) => Stopping Node-BLUE server...
03/21/21 13:45:54.249 (Shutdown) => Stopping script engine server...
03/21/21 13:45:54.268 (Shutdown) => Saving device families
03/21/21 13:45:54.268 (Shutdown) => Saving devices
03/21/21 13:45:54.268 (Shutdown) => Saving HomeMatic BidCoS central...
03/21/21 13:45:54.278 (Shutdown) => Saving devices
03/21/21 13:45:54.278 (Shutdown) => Saving HomeMatic Wired central...
03/21/21 13:45:54.279 (Shutdown) => Saving devices
03/21/21 13:45:54.279 (Shutdown) => Saving MAX! central...
03/21/21 13:45:54.279 (Shutdown) => Saving devices
03/21/21 13:45:54.279 (Shutdown) => Saving Miscellaneous central...
03/21/21 13:45:54.279 (Shutdown) => Disposing device families
03/21/21 13:45:56.984 (Shutdown) => Disposing database
03/21/21 13:45:56.985 Closing database...
03/21/21 13:45:57.034 Debug: Can't execute "COMMIT": cannot commit - no transaction is active
03/21/21 13:45:57.131 (Shutdown) => Disposing family modules
03/21/21 13:45:57.131 Info: Disposing family module mod_miscellaneous.so
03/21/21 13:45:57.131 Debug: Deleting factory pointer of module mod_miscellaneous.so
03/21/21 13:45:57.131 Debug: Closing dynamic library module mod_miscellaneous.so
03/21/21 13:45:57.131 Debug: Dynamic library mod_miscellaneous.so disposed
03/21/21 13:45:57.131 Info: Disposing family module mod_max.so
03/21/21 13:45:57.131 Debug: Deleting factory pointer of module mod_max.so
03/21/21 13:45:57.131 Debug: Closing dynamic library module mod_max.so
03/21/21 13:45:57.131 Debug: Dynamic library mod_max.so disposed
03/21/21 13:45:57.131 Info: Disposing family module mod_homematicwired.so
03/21/21 13:45:57.131 Debug: Deleting factory pointer of module mod_homematicwired.so
03/21/21 13:45:57.131 Debug: Closing dynamic library module mod_homematicwired.so
03/21/21 13:45:57.132 Debug: Dynamic library mod_homematicwired.so disposed
03/21/21 13:45:57.132 Info: Disposing family module mod_homematicbidcos.so
03/21/21 13:45:57.132 Debug: Deleting factory pointer of module mod_homematicbidcos.so
03/21/21 13:45:57.132 Debug: Closing dynamic library module mod_homematicbidcos.so
03/21/21 13:45:57.132 Debug: Dynamic library mod_homematicbidcos.so disposed
03/21/21 13:45:57.132 Debug: Closing dynamic library module mod_homematicbidcos.so
03/21/21 13:45:57.132 Debug: Dynamic library mod_homematicbidcos.so disposed
03/21/21 13:45:57.132 (Shutdown) => Disposing licensing modules
03/21/21 13:45:57.209 (Shutdown) => Shutdown complete.
03/21/21 19:36:19.233 Starting Homegear...
03/21/21 19:36:19.234 Homegear version: 0.7.48-3324
03/21/21 19:36:19.234 Determining maximum thread count...
03/21/21 19:36:20.414 Maximum thread count is: 217
03/21/21 19:36:20.463 Info: Backing up database...
03/21/21 19:36:20.570 Initializing database...
03/21/21 19:36:21.786 Homegear instance ID: 0005BE0B46F0E7DE-2A6A46ED-7580-289D-F568-683A8F748397
03/21/21 19:36:21.799 Debug: Loading licensing modules
03/21/21 19:36:21.801 Initializing system variable controller...
03/21/21 19:36:21.812 Debug: Loading family modules
03/21/21 19:36:21.812 Info: Loading family module (type 1) mod_homematicbidcos.so
03/21/21 19:36:21.883 Info: Loading settings from /etc/homegear/families/homematicbidcos.conf
03/21/21 19:36:21.910 Info: Loading family module (type 1) mod_max.so
03/21/21 19:36:21.949 Info: Loading settings from /etc/homegear/families/max.conf
03/21/21 19:36:21.958 Info: Loading family module (type 1) mod_miscellaneous.so
03/21/21 19:36:21.975 Info: Loading settings from /etc/homegear/families/miscellaneous.conf
03/21/21 19:36:21.977 Info: Loading family module (type 1) mod_homematicwired.so
03/21/21 19:36:22.009 Info: Loading settings from /etc/homegear/families/homematicwired.conf
03/21/21 19:36:22.016 Info: Homegear is (now) running as user with id 111 and group with id 118.
03/21/21 19:36:22.132 Starting script engine server...
03/21/21 19:36:22.210 Initializing licensing controller...
03/21/21 19:36:22.210 Loading licensing controller data...
03/21/21 19:36:22.210 Loading devices...
03/21/21 19:36:22.210 Loading XML RPC devices...
03/21/21 19:36:23.897 Loading device 1
03/21/21 19:36:23.897 Module HomeMatic BidCoS: Info: Central address set to 0xFDACAA.
03/21/21 19:36:23.913 Loading XML RPC devices...
03/21/21 19:36:24.065 Loading device 2
03/21/21 19:36:24.067 Loading XML RPC devices...
03/21/21 19:36:24.287 Loading device 3
03/21/21 19:36:24.288 Module MAX: Info: Central address set to 0xFD57F6.
03/21/21 19:36:24.292 Loading XML RPC devices...
03/21/21 19:36:24.302 Warning: configParameters with id "config" does not exist.
03/21/21 19:36:24.311 Warning: script2 in "runProgram" does not contain CDATA.
03/21/21 19:36:24.315 Warning: configParameters with id "config" does not exist.
03/21/21 19:36:24.317 Warning: variables with id "custom_ch7_values" does not exist.
03/21/21 19:36:24.323 Warning: variables with id "custom_ch7_values" does not exist.
03/21/21 19:36:24.326 Loading device 4
03/21/21 19:36:24.326 Initializing RPC client...
03/21/21 19:36:24.326 Loading device 4
03/21/21 19:36:24.326 Initializing RPC client...
03/21/21 19:36:24.327 Starting XML RPC server RPCServer1 listening on :::2001...
03/21/21 19:36:24.374 RPC Server (Port 2001): Warning: SSL is not enabled for this RPC server. It is strongly recommended to disable all unencrypted RPC servers when the connected clients support it.
03/21/21 19:36:24.375 RPC Server (Port 2001): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when the connected clients support it.
03/21/21 19:36:24.375 RPC Server (Port 2001): Info: Enabling no authentication.
03/21/21 19:36:24.375 RPC Server (Port 2001): Info: Enabling session authentication for WebSockets.
03/21/21 19:36:24.375 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled...
03/21/21 19:36:24.376 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
03/21/21 19:36:24.423 RPC Server (Port 2002): Warning: RPC server has no authorization enabled. Everybody on your local network can login into this installation. It is strongly recommended to enable authorization on all RPC servers when the connected clients support it.
03/21/21 19:36:24.423 RPC Server (Port 2002): Info: Enabling no authentication.
03/21/21 19:36:24.424 RPC Server (Port 2002): Info: Enabling session authentication for WebSockets.
03/21/21 19:36:24.474 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled...
03/21/21 19:36:24.474 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
03/21/21 19:36:24.521 RPC Server (Port 2003): Info: Enabling basic authentication.
03/21/21 19:36:24.521 RPC Server (Port 2003): Info: Enabling client certificate authentication.
03/21/21 19:36:24.522 RPC Server (Port 2003): Info: Enabling session authentication for WebSockets.
03/21/21 19:36:24.560 Starting XML RPC server RPCServer4 listening on ::1:2004...
03/21/21 19:36:24.616 RPC Server (Port 2004): Info: Enabling no authentication.
03/21/21 19:36:24.616 RPC Server (Port 2004): Info: Enabling session authentication for WebSockets.
03/21/21 19:36:24.617 RPC Server (Port 2004): Info: RPC Server started listening on address ::1 and port 2004
03/21/21 19:36:24.621 Initializing event handler...
03/21/21 19:36:24.621 Loading events...
03/21/21 19:36:24.622 Start listening for packets...
03/21/21 19:36:26.626 Starting IPC server...
03/21/21 19:36:26.626 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error in file PhysicalInterfaces/Hm-Mod-Rpi-Pcb.cpp line 969 in function void BidCoS::Hm_Mod_Rpi_Pcb::doInit(): Failed to open value file for GPIO with index 1 and device "hm-mod-rpi-pcb": Unable to retrieve path.
03/21/21 19:36:26.632 Starting Node-BLUE server...
03/21/21 19:36:26.646 Starting variable profile manager...
03/21/21 19:36:26.647 Startup complete. Waiting for physical interfaces to connect.
03/21/21 19:36:26.647 Info: Waiting for physical interfaces to connect (0 of 180s).
03/21/21 19:36:26.647 All physical interfaces are connected now.
03/21/21 19:36:26.647 Starting UPnP server...
03/21/21 19:36:29.867 (Shutdown) => Stopping Homegear (Signal: 15)
03/21/21 19:36:29.867 Node-BLUE Server: Info: Stopping nodes.
03/21/21 19:36:29.867 Script Engine Server: Info: Stopping devices.
03/21/21 19:36:29.868 Info: Shutting down shared object family modules...
03/21/21 19:36:29.868 Info: Shutting down shared object family module "HomeMatic BidCoS"...
03/21/21 19:36:29.868 Info: Shutting down shared object family module "HomeMatic Wired"...
03/21/21 19:36:29.868 Info: Shutting down shared object family module "HomeMatic BidCoS"...
03/21/21 19:36:29.868 Info: Shutting down shared object family module "HomeMatic Wired"...
03/21/21 19:36:29.868 Info: Shutting down shared object family module "MAX!"...
03/21/21 19:36:29.868 Info: Shutting down shared object family module "Miscellaneous"...
03/21/21 19:36:29.868 Stopping UPnP server...
03/21/21 19:36:31.649 UPnP Server: Info: UPnP server: Binding to address: 192.168.178.50
03/21/21 19:36:31.651 (Shutdown) => Stopping Event handler
03/21/21 19:36:31.651 (Shutdown) => Stopping RPC servers
03/21/21 19:36:31.688 RPC Server (Port 2001): Info: Waiting for threads to finish.
03/21/21 19:36:31.787 RPC Server (Port 2002): Info: Waiting for threads to finish.
03/21/21 19:36:31.830 RPC Server (Port 2004): Info: Waiting for threads to finish.
03/21/21 19:36:31.843 (Shutdown) => Stopping RPC client
03/21/21 19:36:31.843 (Shutdown) => Closing physical interfaces...
03/21/21 19:36:56.627 Module HomeMatic BidCoS: HM-MOD-RPI-PCB "My-HM-MOD-RPI-PCB": Error: No init packet received.
03/21/21 19:36:56.628 (Shutdown) => Stopping IPC server...
03/21/21 19:36:56.690 (Shutdown) => Stopping Node-BLUE server...
03/21/21 19:36:56.799 (Shutdown) => Stopping script engine server...
03/21/21 19:36:56.880 (Shutdown) => Saving device families
03/21/21 19:36:56.881 (Shutdown) => Saving devices
03/21/21 19:36:56.881 (Shutdown) => Saving HomeMatic BidCoS central...
03/21/21 19:36:56.881 (Shutdown) => Saving devices
03/21/21 19:36:56.881 (Shutdown) => Saving HomeMatic Wired central...
03/21/21 19:36:56.891 (Shutdown) => Saving devices
03/21/21 19:36:56.891 (Shutdown) => Saving MAX! central...
03/21/21 19:36:56.892 (Shutdown) => Saving devices
03/21/21 19:36:56.892 (Shutdown) => Saving Miscellaneous central...
03/21/21 19:36:56.892 (Shutdown) => Disposing device families
03/21/21 19:36:58.308 (Shutdown) => Disposing database
03/21/21 19:36:58.356 Closing database...
03/21/21 19:36:58.357 Debug: Can't execute "COMMIT": cannot commit - no transaction is active
03/21/21 19:36:58.383 (Shutdown) => Disposing family modules
03/21/21 19:36:58.383 Info: Disposing family module mod_miscellaneous.so
03/21/21 19:36:58.383 Debug: Deleting factory pointer of module mod_miscellaneous.so
03/21/21 19:36:58.383 Debug: Closing dynamic library module mod_miscellaneous.so
03/21/21 19:36:58.383 Debug: Dynamic library mod_miscellaneous.so disposed
03/21/21 19:36:58.383 Info: Disposing family module mod_max.so
03/21/21 19:36:58.383 Debug: Deleting factory pointer of module mod_max.so
03/21/21 19:36:58.383 Debug: Closing dynamic library module mod_max.so
03/21/21 19:36:58.384 Debug: Dynamic library mod_max.so disposed
03/21/21 19:36:58.384 Info: Disposing family module mod_homematicwired.so
03/21/21 19:36:58.384 Debug: Deleting factory pointer of module mod_homematicwired.so
03/21/21 19:36:58.384 Debug: Closing dynamic library module mod_homematicwired.so
03/21/21 19:36:58.384 Debug: Dynamic library mod_homematicwired.so disposed
03/21/21 19:36:58.384 Debug: Closing dynamic library module mod_homematicwired.so
03/21/21 19:36:58.384 Debug: Dynamic library mod_homematicwired.so disposed
03/21/21 19:36:58.384 Info: Disposing family module mod_homematicbidcos.so
03/21/21 19:36:58.384 Debug: Deleting factory pointer of module mod_homematicbidcos.so
03/21/21 19:36:58.384 Debug: Closing dynamic library module mod_homematicbidcos.so
03/21/21 19:36:58.384 Debug: Dynamic library mod_homematicbidcos.so disposed
03/21/21 19:36:58.384 (Shutdown) => Disposing licensing modules
03/21/21 19:36:58.485 (Shutdown) => Shutdown complete.

[pmayer]

03/21/21 19:36:26.647 All physical interfaces are connected now.

Sieht ansich gut aus.

Schau dir mal das Log mit Debuglevel 4 oder 5 an beim anlernen.

sudo homegear -r
dl 5

Anlernen geht auch darüber:

fs 0
pon

In nem zweiten Fenster währenddessen das Log mit tail -f /var/log/homegear/homegear.log verfolgen.

[tSaM89]

Da passiert irgendwie nichts.

[pmayer]

Hast du in dem Moment auch die Anlerntaste am Gerät gedrückt?

Wenn ja eventuell das Gerät oder der HM-MOD-RPI-PCB einen weg.

[tSaM89]

Ja klar. Die LED am Tastermodul blinkt mehrfach grün. Ein erfolgreiches Binden würde laut Handbuch mit einem zwei 2 Sekunden langen grünen Leuchten signalisiert werden.

Woher weiß ich denn wer den Fehler hat?
Mir fehlt da irgendwie das Feedback.

Lassen sich die Homematic Module einfach so an ein neues System anbinden?
Wie zuvor geschrieben waren die beiden taster zuvor ja schonmal im Einsatz.

[pmayer]

Wenn du den gleiche AES-key (rfKey) und die gleiche centralAddress hast, ja.
Falls du die nicht mehr weißt und AES am Gerät an war, muss es du eq3 zum resetten. Ansonsten am Gerät Werksreset machen.

Man sollte vom Anlernen Pakete im Log sehen, da ist aber gar nichts. Ergo: Kein Funkverkehr.

[tSaM89]

Der Key ist beide Male der default Key. Wie genau wird denn ein eq3 Reset durchgeführt?

[pmayer]

@tSaM89

Wie genau wird denn ein eq3 Reset durchgeführt?

Hinschicken, Geld zahlen, zurück bekommen

Versuch es erst mal mit einem Werksreset und guck, ob das überhaupt auf deine Geräte zutrifft:
https://wiki.fhem.de/wiki/AES_Encryption#Hinweise

[tSaM89]

Hat eventuell noch jemand eine Idee die mir hilft die Fehlerursache zu lokalisieren?