03/28/19 17:12:11.813 Starting Homegear... 03/28/19 17:12:11.814 Homegear version 0.8.0-2570 03/28/19 17:12:11.814 Git commit SHA of libhomegear-base: - 03/28/19 17:12:11.814 Git branch of libhomegear-base: - 03/28/19 17:12:11.814 Git commit SHA of Homegear: - 03/28/19 17:12:11.814 Git branch of Homegear: - 03/28/19 17:12:11.821 Info: Setting allowed core file size to "4294967295" for user with id 0 and group with id 0. 03/28/19 17:12:11.821 Info: Core file size now is "4294967295". 03/28/19 17:12:11.821 Info: Setting maximum thread priority to "4294967295" for user with id 0 and group with id 0. 03/28/19 17:12:11.821 Info: Maximum thread priority now is "4294967295". 03/28/19 17:12:11.895 Info: Backing up database... 03/28/19 17:12:12.046 Initializing database... 03/28/19 17:12:12.075 Info: Loading licensing module mod_licensing.so 03/28/19 17:12:12.092 Info: Loading family module (type 1) mod_miscellaneous.so 03/28/19 17:12:12.117 Info: Loading settings from /etc/homegear/families/miscellaneous.conf 03/28/19 17:12:12.124 Info: Loading family module (type 1) mod_max.so 03/28/19 17:12:12.174 Info: Loading settings from /etc/homegear/families/max.conf 03/28/19 17:12:12.176 Info: Loading family module (type 1) mod_homematicbidcos.so 03/28/19 17:12:12.237 Info: Loading settings from /etc/homegear/families/homematicbidcos.conf 03/28/19 17:12:12.278 Info: Setting up physical interfaces and GPIOs... 03/28/19 17:12:12.282 Info: Dropping privileges to user homegear (111) and group homegear (115) 03/28/19 17:12:12.283 Info: Homegear is (now) running as user with id 111 and group with id 115. 03/28/19 17:12:12.437 Starting script engine server... 03/28/19 17:12:12.483 Initializing licensing controller... 03/28/19 17:12:12.610 Loading licensing controller data... 03/28/19 17:12:12.611 Loading devices... 03/28/19 17:12:12.611 Loading XML RPC devices... 03/28/19 17:12:14.547 Loading device 1 03/28/19 17:12:14.623 Module HomeMatic BidCoS: Info: Central address set to 0xFD43AB. 03/28/19 17:12:14.651 Loading XML RPC devices... 03/28/19 17:12:14.892 Loading device 2 03/28/19 17:12:14.892 Module MAX: Info: Central address set to 0xFD34EB. 03/28/19 17:12:14.909 Loading XML RPC devices... 03/28/19 17:12:14.937 Loading device 3 03/28/19 17:12:14.945 Initializing RPC client... 03/28/19 17:12:14.945 Starting XML RPC server FamilyRPCServer listening on ::1:2000... 03/28/19 17:12:14.985 RPC Server (Port 2000): Info: Enabling basic authentication for WebSockets. 03/28/19 17:12:14.985 Starting XML RPC server RPCServer1 listening on :::2001... 03/28/19 17:12:14.986 RPC Server (Port 2000): Info: RPC Server started listening on address ::1 and port 2000 03/28/19 17:12:15.019 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/28/19 17:12:15.020 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/28/19 17:12:15.020 RPC Server (Port 2001): Info: Enabling session authentication for WebSockets. 03/28/19 17:12:15.020 Starting XML RPC server RPCServer2 listening on :::2002, SSL enabled... 03/28/19 17:12:15.020 RPC Server (Port 2001): Info: RPC Server started listening on address :: and port 2001 03/28/19 17:12:15.055 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/28/19 17:12:15.055 RPC Server (Port 2002): Info: Enabling session authentication for WebSockets. 03/28/19 17:12:15.123 Starting XML RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled... 03/28/19 17:12:15.125 RPC Server (Port 2002): Info: RPC Server started listening on address :: and port 2002 03/28/19 17:12:15.159 RPC Server (Port 2003): Info: Enabling basic authentication. 03/28/19 17:12:15.159 RPC Server (Port 2003): Info: Enabling client certificate authentication. 03/28/19 17:12:15.159 RPC Server (Port 2003): Info: Enabling session authentication for WebSockets. 03/28/19 17:12:15.188 Initializing event handler... 03/28/19 17:12:15.188 Loading events... 03/28/19 17:12:15.189 Start listening for packets... 03/28/19 17:12:15.194 Starting Node-BLUE server... 03/28/19 17:12:15.423 Starting IPC server... 03/28/19 17:12:15.432 Startup complete. Waiting for physical interfaces to connect. 03/28/19 17:12:15.432 Info: Waiting for physical interfaces to connect (0 of 180s). 03/28/19 17:12:15.432 All physical interfaces are connected now. 03/28/19 17:12:15.432 Starting UPnP server... 03/28/19 17:12:15.434 Info: UPnP server: Binding to address: 192.168.178.44 03/28/19 17:12:15.435 UPnP Server: Info: Started listening. 03/28/19 17:12:24.662 IPC Server: Info: Connection accepted. Client number: 12 03/28/19 17:12:24.663 IPC Server: Info: Client 0 successfully registered RPC method "managementGetCommandStatus" (this method is registered by 1 client(s)). 03/28/19 17:12:24.664 IPC Server: Info: Client 0 successfully registered RPC method "managementSleep" (this method is registered by 1 client(s)). 03/28/19 17:12:24.664 IPC Server: Info: Client 0 successfully registered RPC method "managementDpkgPackageInstalled" (this method is registered by 1 client(s)). 03/28/19 17:12:24.665 IPC Server: Info: Client 0 successfully registered RPC method "managementGetConfigurationEntry" (this method is registered by 1 client(s)). 03/28/19 17:12:24.666 IPC Server: Info: Client 0 successfully registered RPC method "managementServiceCommand" (this method is registered by 1 client(s)). 03/28/19 17:12:24.666 IPC Server: Info: Client 0 successfully registered RPC method "managementReboot" (this method is registered by 1 client(s)). 03/28/19 17:12:24.667 IPC Server: Info: Client 0 successfully registered RPC method "managementSetConfigurationEntry" (this method is registered by 1 client(s)). 03/28/19 17:12:24.669 IPC Server: Info: Client 0 successfully registered RPC method "managementWriteCloudMaticConfig" (this method is registered by 1 client(s)). 03/28/19 17:12:24.671 IPC Server: Info: Client 0 successfully registered RPC method "managementSetUserPassword" (this method is registered by 1 client(s)). 03/28/19 17:12:24.672 IPC Server: Info: Client 0 successfully registered RPC method "managementAptUpdate" (this method is registered by 1 client(s)). 03/28/19 17:12:24.673 IPC Server: Info: Client 0 successfully registered RPC method "managementAptUpgrade" (this method is registered by 1 client(s)). 03/28/19 17:12:24.679 IPC Server: Info: Client 0 successfully registered RPC method "managementAptFullUpgrade" (this method is registered by 1 client(s)). 03/28/19 17:12:24.679 IPC Server: Info: Client 0 successfully registered RPC method "managementHomegearUpdateAvailable" (this method is registered by 1 client(s)). 03/28/19 17:12:24.680 IPC Server: Info: Client 0 successfully registered RPC method "managementSystemUpdateAvailable" (this method is registered by 1 client(s)). 03/28/19 17:12:24.681 IPC Server: Info: Client 0 successfully registered RPC method "managementCreateBackup" (this method is registered by 1 client(s)). 03/28/19 17:12:24.682 IPC Server: Info: Client 0 successfully registered RPC method "managementRestoreBackup" (this method is registered by 1 client(s)). 03/28/19 17:12:24.683 IPC Server: Info: Client 0 successfully registered RPC method "managementCaExists" (this method is registered by 1 client(s)). 03/28/19 17:12:24.684 IPC Server: Info: Client 0 successfully registered RPC method "managementCreateCa" (this method is registered by 1 client(s)). 03/28/19 17:12:24.685 IPC Server: Info: Client 0 successfully registered RPC method "managementCreateCert" (this method is registered by 1 client(s)). 03/28/19 17:12:24.686 IPC Server: Info: Client 0 successfully registered RPC method "managementDeleteCert" (this method is registered by 1 client(s)). 03/28/19 17:12:24.687 IPC Server: Info: Client 0 successfully registered RPC method "managementGetNetworkConfiguration" (this method is registered by 1 client(s)). 03/28/19 17:12:24.688 IPC Server: Info: Client 0 successfully registered RPC method "managementSetNetworkConfiguration" (this method is registered by 1 client(s)). 03/28/19 17:12:24.688 IPC Server: Info: Client 0 successfully registered RPC method "managementCopyDeviceDescriptionFile" (this method is registered by 1 client(s)). 03/28/19 17:12:51.946 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:48992 accepted. Client number: 13 03/28/19 17:12:51.946 RPC Server (Port 2001): Info: RPC server client id for client number 13 is: 0 03/28/19 17:12:52.764 RPC Server (Port 2001): Info: Client number 13 is calling RPC method: getDeviceDescription (1) Parameters: (String) BidCoS-RF 03/28/19 17:12:52.877 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:48994 accepted. Client number: 14 03/28/19 17:12:52.878 RPC Server (Port 2001): Info: RPC server client id for client number 14 is: 1 03/28/19 17:12:52.882 RPC Server (Port 2001): Info: Client number 14 is calling RPC method: listBidcosInterfaces (1) Parameters: 03/28/19 17:12:52.934 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:48996 accepted. Client number: 15 03/28/19 17:12:52.934 RPC Server (Port 2001): Info: RPC server client id for client number 15 is: 2 03/28/19 17:12:52.938 RPC Server (Port 2001): Info: Client number 15 is calling RPC method: init (1) Parameters: (String) http://openhab.validation:1000 03/28/19 17:12:52.938 Info: Client with IP ::ffff:127.0.0.1 is calling "init". 03/28/19 17:12:53.160 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:49006 accepted. Client number: 16 03/28/19 17:12:53.161 RPC Server (Port 2001): Info: RPC server client id for client number 16 is: 3 03/28/19 17:12:53.170 RPC Server (Port 2001): Info: Client number 16 is calling RPC method: init (2) Parameters: (String) binary://192.168.178.44:9126 (String) RF-112c74ef (Integer) 34 03/28/19 17:12:53.170 Info: Client with IP ::ffff:127.0.0.1 is calling "init". 03/28/19 17:12:53.170 Info: Adding server "binary://192.168.178.44". 03/28/19 17:12:53.171 Info: Calling init methods on server "binary://192.168.178.44". 03/28/19 17:12:53.188 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:49008 accepted. Client number: 17 03/28/19 17:12:53.188 RPC Server (Port 2001): Info: RPC server client id for client number 17 is: 4 03/28/19 17:12:53.189 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: listDevices (2) Parameters: 03/28/19 17:12:53.199 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: getDeviceInfo (2) Parameters: 03/28/19 17:12:53.239 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: getAllSystemVariables (2) Parameters: 03/28/19 17:12:53.245 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: getAllScripts (2) Parameters: 03/28/19 17:13:23.354 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: ping (2) Parameters: (String) 112c74ef 03/28/19 17:13:23.363 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: listBidcosInterfaces (2) Parameters: 03/28/19 17:13:34.289 IPC Server: Info: Connection accepted. Client number: 20 03/28/19 17:13:34.290 IPC Server: Info: Client 1 successfully registered RPC method "cliOutput" (this method is registered by 1 client(s)). 03/28/19 17:13:34.292 IPC Server: Info: Client 1 successfully registered RPC method "cliOutput-1" (this method is registered by 1 client(s)). 03/28/19 17:13:38.369 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: ping (2) Parameters: (String) 112c74ef 03/28/19 17:13:38.374 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: listBidcosInterfaces (2) Parameters: 03/28/19 17:13:41.394 IPC Server: Info: Client number 1 is calling RPC method: familyExists Parameters: (Integer64) 0 03/28/19 17:13:51.663 HomeMatic BidCoS packet received (My-CC1101, RSSI: -39 dBm): 3101008F1911B4F00003103014F711A00000D8A9AA9521000100000102011008040336214ED1D35B90DB374CC75931B2EA2E 03/28/19 17:13:52.020 HomeMatic BidCoS packet received (My-CC1101, RSSI: -41 dBm): 3101008F1911B4F00003103014F711A00000D8A9AA9521000100000102011008040336214ED1D35B90DB374CC75931B2EA2E 03/28/19 17:13:53.379 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: ping (2) Parameters: (String) 112c74ef 03/28/19 17:13:53.383 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: listBidcosInterfaces (2) Parameters: 03/28/19 17:13:54.485 HomeMatic BidCoS packet received (My-CC1101, RSSI: -51 dBm): 3101008F1911B4F00003103014F711A00000D8A9AA9521000100000102011008040336214ED1D35B90DB374CC75931B2EA2E 03/28/19 17:14:00.246 HomeMatic BidCoS packet received (My-CC1101, RSSI: -48 dBm): 3101008F1911B4F00003103014F711A00000D8A9AA9521000100000102011008040336214ED1D35B90DB374CC75931B2EA2E 03/28/19 17:14:03.391 HomeMatic BidCoS packet received (My-CC1101, RSSI: -47 dBm): 3101008F1911B4F00003103014F711A00000D8A9AA9521000100000102011008040336214ED1D35B90DB374CC75931B2EA2E 03/28/19 17:14:05.870 HomeMatic BidCoS packet received (My-CC1101, RSSI: -48 dBm): 3101008F1911B4F00003103014F711A00000D8A9AA9521000100000102011008040336214ED1D35B90DB374CC75931B2EA2E 03/28/19 17:14:08.389 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: ping (2) Parameters: (String) 112c74ef 03/28/19 17:14:08.395 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: listBidcosInterfaces (2) Parameters: 03/28/19 17:14:15.724 HomeMatic BidCoS packet received (My-CC1101, RSSI: -41 dBm): 3101008F1911B4F00003103014F711A00000D8A9AA9521000100000102011008040336214ED1D35B90DB374CC75931B2EA2E 03/28/19 17:14:23.400 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: ping (2) Parameters: (String) 112c74ef 03/28/19 17:14:23.405 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: listBidcosInterfaces (2) Parameters: 03/28/19 17:14:25.636 HomeMatic BidCoS packet received (My-CC1101, RSSI: -41 dBm): 3101008F1911B4F00003103014F711A00000D8A9AA9521000100000102011008040336214ED1D35B90DB374CC75931B2EA2E 03/28/19 17:14:35.584 HomeMatic BidCoS packet received (My-CC1101, RSSI: -41 dBm): 3101008F1911B4F00003103014F711A00000D8A9AA9521000100000102011008040336214ED1D35B90DB374CC75931B2EA2E 03/28/19 17:14:38.410 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: ping (2) Parameters: (String) 112c74ef 03/28/19 17:14:38.416 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: listBidcosInterfaces (2) Parameters: 03/28/19 17:14:45.558 HomeMatic BidCoS packet received (My-CC1101, RSSI: -41 dBm): 3101008F1911B4F00003103014F711A00000D8A9AA9521000100000102011008040336214ED1D35B90DB374CC75931B2EA2E 03/28/19 17:14:53.421 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: ping (2) Parameters: (String) 112c74ef 03/28/19 17:14:53.426 RPC Server (Port 2001): Info: Client number 17 is calling RPC method: listBidcosInterfaces (2) Parameters: 03/28/19 17:14:55.491 HomeMatic BidCoS packet received (My-CC1101, RSSI: -41 dBm): 3101008F1911B4F00003103014F711A00000D8A9AA9521000100000102011008040336214ED1D35B90DB374CC75931B2EA2E