HM-MOD-RPI-PCB an PI3 mit Openhab Umzug auf buster

[ThomyTP]

Hallo.
ich habe meinen Openhab2 neu aufgesetzt und somit das Update von jessie auf buster vollzogen.
Vorher habe ich mit sudo $OPENHAB_RUNTIME/bin/backup Opbenhab gesichtert.
Nach der Neuinstallation habe über openhabian-config homegear wider installiert und das Backup Wiederhergestellt und die /boot/cmdline + config-txt analog zu der alten Installation angepasst.
Danach habe ich
sudo systemctl disable serial-getty@ttyAMA0.service
sudo systemctl disable serial-getty@serial0.service
sudo systemctl disable serial-getty@ttyS0.service
durchgeführt und die homematicbidcos.conf eingespielt.

Nach einen Neustart startet homegear leider nicht. Ich bekomme folgende Meldung:

07/18/20 15:51:54.132 Starting Homegear…
07/18/20 15:51:54.132 Homegear version 0.7.45-3101
07/18/20 15:51:54.132 Determining maximum thread count…
07/18/20 15:51:55.266 Maximum thread count is: 218
07/18/20 15:51:55.274 Info: Backing up database…
07/18/20 15:51:55.454 Initializing database…
07/18/20 15:51:56.635 Debug: Loading licensing modules
07/18/20 15:51:56.636 Initializing system variable controller…
07/18/20 15:51:56.637 Debug: Loading family modules
07/18/20 15:51:56.637 Info: Loading family module (type 1) mod_miscellaneous.so
07/18/20 15:51:56.645 Info: Loading settings from /etc/homegear/families/miscellaneous.conf
07/18/20 15:51:56.646 Info: Loading family module (type 1) mod_max.so
07/18/20 15:51:56.655 Info: Loading settings from /etc/homegear/families/max.conf
07/18/20 15:51:56.656 Info: Loading family module (type 1) mod_homematicbidcos.so
07/18/20 15:51:56.673 Info: Loading settings from /etc/homegear/families/homematicbidcos.conf
07/18/20 15:51:56.675 Info: Loading family module (type 1) mod_homematicwired.so
07/18/20 15:51:56.686 Info: Loading settings from /etc/homegear/families/homematicwired.conf
07/18/20 15:51:56.687 Info: Homegear is (now) running as user with id 112 and group with id 119.
07/18/20 15:51:56.770 Starting script engine server…
07/18/20 15:51:56.811 Script Engine Server: Critical: Couldn’t delete existing socket: /var/run/homegear/homegearSE.sock. Please delete it manually. The script engine won’t work. Error: Permission denied
07/18/20 15:51:56.812 Critical: Cannot start script engine server. Exiting Homegear.
07/18/20 15:51:56.813 Closing database…
07/18/20 15:51:56.813 Debug: Can’t execute “COMMIT”: cannot commit - no transaction is active
07/18/20 15:51:56.897 Info: Disposing family module mod_miscellaneous.so
07/18/20 15:51:56.897 Debug: Deleting factory pointer of module mod_miscellaneous.so
07/18/20 15:51:56.897 Debug: Closing dynamic library module mod_miscellaneous.so
07/18/20 15:51:56.898 Debug: Dynamic library mod_miscellaneous.so disposed
07/18/20 15:51:56.898 Info: Disposing family module mod_max.so
07/18/20 15:51:56.898 Debug: Deleting factory pointer of module mod_max.so
07/18/20 15:51:56.898 Debug: Closing dynamic library module mod_max.so
07/18/20 15:51:56.898 Debug: Dynamic library mod_max.so disposed
07/18/20 15:51:56.898 Info: Disposing family module mod_homematicwired.so
07/18/20 15:51:56.898 Debug: Deleting factory pointer of module mod_homematicwired.so
07/18/20 15:51:56.898 Debug: Closing dynamic library module mod_homematicwired.so
07/18/20 15:51:56.898 Debug: Dynamic library mod_homematicwired.so disposed
07/18/20 15:51:56.898 Info: Disposing family module mod_homematicbidcos.so
07/18/20 15:51:56.899 Debug: Deleting factory pointer of module mod_homematicbidcos.so
07/18/20 15:51:56.899 Debug: Closing dynamic library module mod_homematicbidcos.so
07/18/20 15:51:56.899 Debug: Dynamic library mod_homematicbidcos.so disposed

Wenn ich mir das Verzeichniss /var/run/homegear anschauen. gehört dies dem root. homegear läuft aber unter dem User homegear. Wenn das Verzeichniss anpassen auf Owner homegear, startet homegear zwar, nach einem Neustart ist diese Änderung aber wieder weg.
Wenn es startet bekomme ich dann folgende Meldung:
07/18/20 16:04:04.686 Starting Homegear…
07/18/20 16:04:04.686 Homegear version 0.7.45-3101
07/18/20 16:04:04.686 Determining maximum thread count…
07/18/20 16:04:05.813 Maximum thread count is: 218
07/18/20 16:04:05.827 Info: Backing up database…
07/18/20 16:04:05.942 Initializing database…
07/18/20 16:04:06.158 Debug: Loading licensing modules
07/18/20 16:04:06.159 Initializing system variable controller…
07/18/20 16:04:06.160 Debug: Loading family modules
07/18/20 16:04:06.160 Info: Loading family module (type 1) mod_miscellaneous.so
07/18/20 16:04:06.164 Info: Loading settings from /etc/homegear/families/miscellaneous.conf
07/18/20 16:04:06.165 Info: Loading family module (type 1) mod_max.so
07/18/20 16:04:06.173 Info: Loading settings from /etc/homegear/families/max.conf
07/18/20 16:04:06.174 Info: Loading family module (type 1) mod_homematicbidcos.so
07/18/20 16:04:06.187 Info: Loading settings from /etc/homegear/families/homematicbidcos.conf
07/18/20 16:04:06.188 Info: Loading family module (type 1) mod_homematicwired.so
07/18/20 16:04:06.195 Info: Loading settings from /etc/homegear/families/homematicwired.conf
07/18/20 16:04:06.196 Info: Homegear is (now) running as user with id 112 and group with id 119.
07/18/20 16:04:06.277 Starting script engine server…
07/18/20 16:04:06.324 Initializing licensing controller…
07/18/20 16:04:06.325 Loading licensing controller data…
07/18/20 16:04:06.325 Loading devices…
07/18/20 16:04:06.325 Loading XML RPC devices…
07/18/20 16:04:07.540 Loading device 1
07/18/20 16:04:07.553 Module HomeMatic BidCoS: Info: Central address set to 0xFD2103.
07/18/20 16:04:07.559 Loading XML RPC devices…
07/18/20 16:04:07.718 Loading device 2
07/18/20 16:04:07.723 Loading XML RPC devices…
07/18/20 16:04:07.856 Loading device 3
07/18/20 16:04:07.856 Module MAX: Info: Central address set to 0xFD33A3.
07/18/20 16:04:07.863 Loading XML RPC devices…
07/18/20 16:04:07.866 Warning: configParameters with id “config” does not exist.
07/18/20 16:04:07.877 Loading device 4
07/18/20 16:04:07.880 Initializing RPC client…
07/18/20 16:04:07.880 Starting XML RPC server RPCServer1 listening on :::2001…
07/18/20 16:04:07.921 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.
07/18/20 16:04:07.921 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.
07/18/20 16:04:07.921 RPC Server (Port 2001): Info: Enabling no authentication.
07/18/20 16:04:07.921 RPC Server (Port 2001): Info: Enabling session authentication for WebSockets.
07/18/20 16:04:07.921 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled…
07/18/20 16:04:07.922 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001
07/18/20 16:04:07.962 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.
07/18/20 16:04:07.962 RPC Server (Port 2002): Info: Enabling no authentication.
07/18/20 16:04:07.963 RPC Server (Port 2002): Info: Enabling session authentication for WebSockets.
07/18/20 16:04:08.014 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled…
07/18/20 16:04:08.014 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002
07/18/20 16:04:08.055 RPC Server (Port 2003): Info: Enabling basic authentication.
07/18/20 16:04:08.055 RPC Server (Port 2003): Info: Enabling client certificate authentication.
07/18/20 16:04:08.055 RPC Server (Port 2003): Info: Enabling session authentication for WebSockets.
07/18/20 16:04:08.130 Initializing event handler…
07/18/20 16:04:08.131 Loading events…
07/18/20 16:04:08.132 Start listening for packets…
07/18/20 16:04:09.364 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.111.83:60868 accepted. Client number: 4
07/18/20 16:04:09.364 RPC Server (Port 2001): Info: RPC server client id for client number 4 is: 0
07/18/20 16:04:09.374 RPC Server (Port 2001): Info: Client number 4 is calling RPC method: getDeviceDescription (1) Parameters:
(String) BidCoS-RF
07/18/20 16:04:09.441 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.111.83:60870 accepted. Client number: 5
07/18/20 16:04:09.441 RPC Server (Port 2001): Info: RPC server client id for client number 5 is: 1
07/18/20 16:04:09.445 RPC Server (Port 2001): Info: Client number 5 is calling RPC method: listBidcosInterfaces (1) Parameters:
07/18/20 16:04:09.487 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.111.83:60872 accepted. Client number: 6
07/18/20 16:04:09.488 RPC Server (Port 2001): Info: RPC server client id for client number 6 is: 2
07/18/20 16:04:09.491 RPC Server (Port 2001): Info: Client number 6 is calling RPC method: init (1) Parameters:
(String) http://openhab.validation:1000
07/18/20 16:04:09.491 Info: Client with IP ::ffff:192.168.111.83 is calling “init”.
07/18/20 16:04:09.661 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.111.83:60882 accepted. Client number: 7
07/18/20 16:04:09.661 RPC Server (Port 2001): Info: RPC server client id for client number 7 is: 3
07/18/20 16:04:09.663 RPC Server (Port 2001): Info: Client number 7 is calling RPC method: init (2) Parameters:
(String) binary://192.168.111.83:9126
(String) RF-333527BD-1D21-0623-C048-B60043753478
(Integer) 34
07/18/20 16:04:09.663 Info: Client with IP ::ffff:192.168.111.83 is calling “init”.
07/18/20 16:04:09.663 Info: Adding server “binary://192.168.111.83”.
07/18/20 16:04:09.664 Info: Calling init methods on server “binary://192.168.111.83”.
07/18/20 16:04:09.679 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.111.83:60884 accepted. Client number: 8
07/18/20 16:04:09.679 RPC Server (Port 2001): Info: RPC server client id for client number 8 is: 4
07/18/20 16:04:09.680 RPC Server (Port 2001): Info: Client number 8 is calling RPC method: listDevices (2) Parameters:
07/18/20 16:04:09.690 RPC Server (Port 2001): Info: Client number 8 is calling RPC method: getDeviceInfo (2) Parameters:
07/18/20 16:04:09.696 RPC Server (Port 2001): Info: Client number 8 is calling RPC method: getAllSystemVariables (2) Parameters:
07/18/20 16:04:09.715 RPC Server (Port 2001): Info: Client number 8 is calling RPC method: getAllScripts (2) Parameters:
07/18/20 16:04:10.133 Info: Could not set thread priority. The executing user does not have enough privileges. Please run “ulimit -r 100” before executing Homegear.
07/18/20 16:04:10.134 Starting IPC server…
07/18/20 16:04:10.134 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.
07/18/20 16:04:10.140 Starting Node-BLUE server…
07/18/20 16:04:10.174 Debug: Adding method system.multicall
07/18/20 16:04:10.174 Debug: Adding method event
07/18/20 16:04:10.174 Debug: Adding method deleteDevices
07/18/20 16:04:10.174 Debug: Adding method newDevices
07/18/20 16:04:10.279 Startup complete. Waiting for physical interfaces to connect.
07/18/20 16:04:10.279 Info: Waiting for physical interfaces to connect (0 of 180s).
07/18/20 16:04:10.280 All physical interfaces are connected now.
07/18/20 16:04:10.280 Starting UPnP server…
07/18/20 16:04:12.453 IPC Server: Info: Connection accepted. Client number: 0, file descriptor ID: 12
07/18/20 16:04:12.456 IPC Server: Info: Client 0 successfully registered RPC method “managementGetCommandStatus” (this method is registered by 1 client(s)).
07/18/20 16:04:12.458 IPC Server: Info: Client 0 successfully registered RPC method “managementSleep” (this method is registered by 1 client(s)).
07/18/20 16:04:12.459 IPC Server: Info: Client 0 successfully registered RPC method “managementDpkgPackageInstalled” (this method is registered by 1 client(s)).
07/18/20 16:04:12.460 IPC Server: Info: Client 0 successfully registered RPC method “managementGetSystemInfo” (this method is registered by 1 client(s)).
07/18/20 16:04:12.461 IPC Server: Info: Client 0 successfully registered RPC method “managementGetConfigurationEntry” (this method is registered by 1 client(s)).
07/18/20 16:04:12.463 IPC Server: Info: Client 0 successfully registered RPC method “managementServiceCommand” (this method is registered by 1 client(s)).
07/18/20 16:04:12.464 IPC Server: Info: Client 0 successfully registered RPC method “managementReboot” (this method is registered by 1 client(s)).
07/18/20 16:04:12.465 IPC Server: Info: Client 0 successfully registered RPC method “managementSetConfigurationEntry” (this method is registered by 1 client(s)).
07/18/20 16:04:12.467 IPC Server: Info: Client 0 successfully registered RPC method “managementWriteCloudMaticConfig” (this method is registered by 1 client(s)).
07/18/20 16:04:12.468 IPC Server: Info: Client 0 successfully registered RPC method “managementSetUserPassword” (this method is registered by 1 client(s)).
07/18/20 16:04:12.469 IPC Server: Info: Client 0 successfully registered RPC method “managementInstallNode” (this method is registered by 1 client(s)).
07/18/20 16:04:12.474 IPC Server: Info: Client 0 successfully registered RPC method “managementUninstallNode” (this method is registered by 1 client(s)).
07/18/20 16:04:12.475 IPC Server: Info: Client 0 successfully registered RPC method “managementGetNodePackages” (this method is registered by 1 client(s)).
07/18/20 16:04:12.476 IPC Server: Info: Client 0 successfully registered RPC method “managementAptRunning” (this method is registered by 1 client(s)).
07/18/20 16:04:12.477 IPC Server: Info: Client 0 successfully registered RPC method “managementAptUpdate” (this method is registered by 1 client(s)).
07/18/20 16:04:12.478 IPC Server: Info: Client 0 successfully registered RPC method “managementAptUpgrade” (this method is registered by 1 client(s)).
07/18/20 16:04:12.479 IPC Server: Info: Client 0 successfully registered RPC method “managementAptUpgradeSpecific” (this method is registered by 1 client(s)).
07/18/20 16:04:12.480 IPC Server: Info: Client 0 successfully registered RPC method “managementAptFullUpgrade” (this method is registered by 1 client(s)).
07/18/20 16:04:12.481 IPC Server: Info: Client 0 successfully registered RPC method “managementHomegearUpdateAvailable” (this method is registered by 1 client(s)).
07/18/20 16:04:12.481 IPC Server: Info: Client 0 successfully registered RPC method “managementSystemUpdateAvailable” (this method is registered by 1 client(s)).
07/18/20 16:04:12.482 IPC Server: Info: Client 0 successfully registered RPC method “managementCreateBackup” (this method is registered by 1 client(s)).
07/18/20 16:04:12.483 IPC Server: Info: Client 0 successfully registered RPC method “managementRestoreBackup” (this method is registered by 1 client(s)).
07/18/20 16:04:12.485 IPC Server: Info: Client 0 successfully registered RPC method “managementSystemReset” (this method is registered by 1 client(s)).
07/18/20 16:04:12.486 IPC Server: Info: Client 0 successfully registered RPC method “managementCaExists” (this method is registered by 1 client(s)).
07/18/20 16:04:12.486 IPC Server: Info: Client 0 successfully registered RPC method “managementCreateCa” (this method is registered by 1 client(s)).
07/18/20 16:04:12.487 IPC Server: Info: Client 0 successfully registered RPC method “managementCreateCert” (this method is registered by 1 client(s)).
07/18/20 16:04:12.488 IPC Server: Info: Client 0 successfully registered RPC method “managementDeleteCert” (this method is registered by 1 client(s)).
07/18/20 16:04:12.489 IPC Server: Info: Client 0 successfully registered RPC method “managementGetNetworkConfiguration” (this method is registered by 1 client(s)).
07/18/20 16:04:12.490 IPC Server: Info: Client 0 successfully registered RPC method “managementSetNetworkConfiguration” (this method is registered by 1 client(s)).
07/18/20 16:04:12.491 IPC Server: Info: Client 0 successfully registered RPC method “managementCopyDeviceDescriptionFile” (this method is registered by 1 client(s)).
^C
[16:04:15] openhabian@openhab:~$ mc
GNU nano 3.2 /var/log/homegear/homegear.log

07/18/20 16:04:12.477 IPC Server: Info: Client 0 successfully registered RPC method “managementAptUpdate” (this method is registered by 1 client(s)).
07/18/20 16:04:12.478 IPC Server: Info: Client 0 successfully registered RPC method “managementAptUpgrade” (this method is registered by 1 client(s)).
07/18/20 16:04:12.479 IPC Server: Info: Client 0 successfully registered RPC method “managementAptUpgradeSpecific” (this method is registered by 1 client(s)).
07/18/20 16:04:12.480 IPC Server: Info: Client 0 successfully registered RPC method “managementAptFullUpgrade” (this method is registered by 1 client(s)).
07/18/20 16:04:12.481 IPC Server: Info: Client 0 successfully registered RPC method “managementHomegearUpdateAvailable” (this method is registered by 1 client(s)).
07/18/20 16:04:12.481 IPC Server: Info: Client 0 successfully registered RPC method “managementSystemUpdateAvailable” (this method is registered by 1 client(s)).
07/18/20 16:04:12.482 IPC Server: Info: Client 0 successfully registered RPC method “managementCreateBackup” (this method is registered by 1 client(s)).
07/18/20 16:04:12.483 IPC Server: Info: Client 0 successfully registered RPC method “managementRestoreBackup” (this method is registered by 1 client(s)).
07/18/20 16:04:12.485 IPC Server: Info: Client 0 successfully registered RPC method “managementSystemReset” (this method is registered by 1 client(s)).
07/18/20 16:04:12.486 IPC Server: Info: Client 0 successfully registered RPC method “managementCaExists” (this method is registered by 1 client(s)).
07/18/20 16:04:12.486 IPC Server: Info: Client 0 successfully registered RPC method “managementCreateCa” (this method is registered by 1 client(s)).
07/18/20 16:04:12.487 IPC Server: Info: Client 0 successfully registered RPC method “managementCreateCert” (this method is registered by 1 client(s)).
07/18/20 16:04:12.488 IPC Server: Info: Client 0 successfully registered RPC method “managementDeleteCert” (this method is registered by 1 client(s)).
07/18/20 16:04:12.489 IPC Server: Info: Client 0 successfully registered RPC method “managementGetNetworkConfiguration” (this method is registered by 1 client(s)).
07/18/20 16:04:12.490 IPC Server: Info: Client 0 successfully registered RPC method “managementSetNetworkConfiguration” (this method is registered by 1 client(s)).
07/18/20 16:04:12.491 IPC Server: Info: Client 0 successfully registered RPC method “managementCopyDeviceDescriptionFile” (this method is registered by 1 client(s)).
07/18/20 16:04:15.281 UPnP Server: Info: UPnP server: Binding to address: 192.168.111.83
07/18/20 16:04:18.013 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.111.63:51080 accepted. Client number: 14
07/18/20 16:04:18.013 RPC Server (Port 2001): Info: RPC server client id for client number 14 is: 5
07/18/20 16:04:39.790 RPC Server (Port 2001): Info: Client number 8 is calling RPC method: ping (2) Parameters:
(String) 333527BD-1D21-0623-C048-B60043753478
07/18/20 16:04:39.795 RPC Server (Port 2001): Info: Client number 8 is calling RPC method: listBidcosInterfaces (2) Parameters:
07/18/20 16:04:40.134 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “My-HM-MOD-RPI-PCB”: Error: No init packet received.
07/18/20 16:04:42.157 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “My-HM-MOD-RPI-PCB”: Warning: Connection closed (1). Trying to reconnect…
07/18/20 16:04:44.158 Module HomeMatic BidCoS: HM-MOD-RPI-PCB “My-HM-MOD-RPI-PCB”: Connected to HM-MOD-RPI-PCB.
07/18/20 16:04:44.160 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 i$
07/18/20 16:04:54.800 RPC Server (Port 2001): Info: Client number 8 is calling RPC method: ping (2) Parameters:
(String) 333527BD-1D21-0623-C048-B60043753478
07/18/20 16:04:54.803 RPC Server (Port 2001): Info: Client number 8 is calling RPC method: listBidcosInterfaces (2) Parameters:
07/18/20 16:05:09.807 RPC Server (Port 2001): Info: Client number 8 is calling RPC method: ping (2) Parameters:
(String) 333527BD-1D21-0623-C048-B60043753478
07/18/20 16:05:09.811 RPC Server (Port 2001): Info: Client number 8 is calling RPC method: listBidcosInterfaces (2) Parameters:
07/18/20 16:05:12.541 IPC Server: Info: Client number 0 is calling RPC method: lifetick Parameters:

Hat jemand eine Idee woran dieses beiden Verhalten liegen können.
Vielen Dank
ThomyTP

[mstormi]

@ThomyTP

und die /boot/cmdline + config-txt analog zu der alten Installation angepasst.
Danach habe ich
sudo systemctl disable serial-getty@ttyAMA0.service
sudo systemctl disable serial-getty@serial0.service
sudo systemctl disable serial-getty@ttyS0.service

Sollte alles unnötig sein.
Warum übernehmen so viele Leute ohne weiteres Nachdenken immer Einstellungen und Installations-Schritte die Jahre zuvor mal Gültigkeit hatten, vergessen aber sich über nötige Änderungen kundig zu machen und wundern sich dann wenn es nicht geht?

@ThomyTP

Script Engine Server: Critical: Couldn’t delete existing socket: /var/run/homegear/homegearSE.sock. Please delete it manually. The script engine won’t work. Error: Permission denied

Da hast du doch den Grund.
Trage in /lib/systemd/system/homegear.service user=homegear und group=homegear nach.
Und ändere RuntimeDirectory=homegear. Außerdem kann man noch RuntimeDirectoryMode setzen.
Doku zu allen Optionen siehe Manpage zu systemd.exec(5).

[ThomyTP]

Hallo,
danke für deine Antwort, sorry wenn ich alte Schritt genutzt hatte, diese hatte 2017 bei meiner Erstinstallation noch Gültigkeit und hatte auch so funktioniert. Wo gibt es für buster die aktuellen Einstellungen=?? Das Internet ist voll von den “alten” Einstellungen… Sorry aber wenn man nicht jeden Tag den der Installation schraubt passiert das halt.

Ich hatte das Problem mittlerweile selbst gelöst.
Durch das Restore lief der Service noch unter root…
Homegear läuft nun, es zeigt mir auch alle peers an. Leider funktioniert die Kommunikation nicht.
Der Anlernmodus startet, ohne Fehlermeldung. unter peers list werden keine Kommunikations Probleme angezeigt.

Muss ich nun alle Geräte doch Neu anlernen? Das Restore sollte doch eigentlich dies Umgehen…

Gruß
ThomyTP

[mstormi]

@ThomyTP

Muss ich nun alle Geräte doch Neu anlernen? Das Restore sollte doch eigentlich dies Umgehen…

Da kann ich nichts zu sagen. Dazu müßtest du mindestens sagen wie du “Backup/Restore” gemacht hast. Ich vermute du meinst openhab-cli backup/restore, aber das sichert halt nur was zu openHAB gehört und homegear ist halt nicht openHAB.
Ich vermute daß homegear seine Daten über angelernte Geräte irgendwo anders abspeichert.

EDIT: openHABian/Amanda sichert jetzt auch die homegear-Directories /var/lib/homegear, wenn homegear installiert ist.

[ThomyTP]

Hallo,
Ich hatte diese Anleitung genutzt.

https://doc.homegear.eu/homegear/backup.html + passend die Berechtigungen auf die Ordner gesetzt.

Die Geräte werden angezeigt aber sind nicht im Zugriff. Etwas fehlt also…
Gruß

[ThomyTP]

hier noch mal ein Auszug aus dem homegear.log

(String) OEQ0296481:1
(String) LEVEL
(Float) 0.75
07/19/20 19:15:16.090 Warning: !!!Not!!! sending packet, because init sequence is not complete: 0C26A011FD210356EF60020196
07/19/20 19:15:16.242 IPC Server: Info: Client number 0 is calling RPC method: lifetick Parameters:

[ThomyTP]

homegear.log (85,0 KB) homegear.service.txt (550 Bytes) Hallo,
ich muss mich leider korrigieren, nach einem Reboot läuft Homegear wieder nicht. Dies scheint ein Rechte Problem zu sein. Da ich alles frisch installiert habe und nur die beiden Homegear Verzeichnisse Restor habe denke ich es liegt an diesen.
Hat jemand noch eine Idee?

Anbei meine Logs, bzw. Dateien.
Danke, vielleicht finden wir hier ja noch einen Lösung um für andere User eine neue Installation einfacher zu gestalten…

[mstormi]

In homegear.service unter

[Service]
User=homegear
Group=homegear

nachtragen und daemon-reload

[ThomyTP]

Hi,
leider keine Besserung, so sieht die service Datei nun aus
Sorry ich steh auf dem Schlauch. Eigentlich passt alles…
RuntimeDirectoryMode habe ich mal test weise mit rein genommen…
[Service]
Type=simple
PIDFile=/var/run/homegear/homegear.pid
TimeoutSec=300
LimitRTPRIO=100
ExecStartPre=/etc/homegear/homegear-start.sh
ExecStart=/usr/bin/homegear -u homegear -g =homegear -p /var/run/homegear/homegear.pid
ExecStopPost=/etc/homegear/homegear-stop.sh
ExecReload=/bin/kill -HUP $MAINPID
Restart=on-failure
TasksMax=infinity
LimitRTPRIO=infinity
LimitRTTIME=infinity
LimitCORE=infinity
RuntimeDirectory=homegear
RuntimeDirectoryMode=0755
User=homegear
Group=homegear

[mstormi]

Die Config hat einige evtl. schadende überflüssige Zeilen. Mein homegear läuft mit der u.g. Config.

Räum mal auf. Siehe openHABian + Homegear (Fehler: Could not connect to socket. Permission denied)

Nota bene: wir reden über /etc/systemd/system/homegear.service, nicht über /lib/...
Hast du beide, hat /etc Vorrang.
Was heißt überhaupt “läuft nicht” ?
Was sagen systemctl status homegear und journalctl -xu homegear ?

[Unit]
Description=Homegear

[Service]
Type=simple
User=homegear
Group=homegear
RuntimeDirectory=homegear
RuntimeDirectoryMode=0755
LimitRTPRIO=100
TasksMax=infinity
LimitCORE=infinity
ExecStart=/usr/bin/homegear

[Install]
WantedBy=multi-user.target

[sathya]

Die Berechtigungen in /etc/homegear stimmen nicht. Korrigieren kannst du diese mit:

sudo systemctl stop homegear
sudo chown -R root:root /etc/homegear
sudo find /etc/homegear -type d -print0 | xargs -0 chmod 755
sudo find /etc/homegear -type f -print0 | xargs -0 chmod 644
sudo find /etc/homegear -name "*.key" -print0 | xargs -0 chmod 644
sudo find /etc/homegear -name "*.key" -print0 | xargs -0 chown homegear:homegear
sudo chown homegear:homegear /etc/homegear/rpcclients.conf
sudo chmod 400 /etc/homegear/rpcclients.conf
sudo chown homegear:homegear -R /var/log/homegear

Dann sollten eigentlich alle Berechtigungen passen. Alle anderen Berechtigungen korrigiert Homegear beim Start. Von der GPIO-Thematik im von @mstormi verlinkten Thread bist du ebenso betroffen.

Viele Grüße

Sathya

[mstormi]

habe ich mal in openHABian in die “correct permissions” Funktion aufgenommen.

[sathya]

Cool, vielen Dank!