Homematic Things went offline after some minutes, have to restart homegear

English Forums Devices
#1

Hello,

I setup openHAB2 on a Raspberry 3 with homegear and a CUL to control my Homematic thermostats. Everything worked fine for some days and I was able to change what I want using PaperUI. Unfortunately since yesterday the Things went offline with a “communication_error” and I have to restart home gear to bring it back to life. This works for some minutes and than the Things went offline again. Any idea what the problem could be? I was not successful to find a solution in the forum and the log files didn’t say anything to me as a layman…

Would be happy if someone knows what it could be!
Best, Sebastian

#2

Hi,

could you please post the log so that we can have a look at it?

Cheers,
p

#3

Sure:

05/06/17 21:44:22.553 RPC Server (Port 2001): Info: Connection from ::ffff:192.168.178.31:35994 accepted. Client number: 32
05/06/17 21:44:22.554 RPC Server (Port 2001): Info: Connection to client number 29 closed (3).
05/06/17 21:44:22.554 RPC Server (Port 2001): Info: RPC server client id for client number 32 is: 11
05/06/17 21:44:22.554 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) MASTER
05/06/17 21:44:22.571 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578170:0
(String) VALUES
05/06/17 21:44:22.576 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:0
(String) MASTER
05/06/17 21:44:22.592 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0577914:0
(String) VALUES
05/06/17 21:44:22.597 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) MASTER
05/06/17 21:44:22.614 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: getParamset (2) Parameters:
(String) MEQ0578135:0
(String) VALUES
05/06/17 21:44:22.618 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: getParamset (2) Parameters:
(String) ITD00012FD1:0
(String) MASTER
05/06/17 21:44:22.621 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: getParamset (2) Parameters:
(String) ITD00012FD1:0
(String) VALUES
05/06/17 21:44:22.627 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: getParamset (2) Parameters:
(String) ITD00012FD1:1
(String) MASTER
05/06/17 21:44:22.630 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: getParamset (2) Parameters:
(String) ITD00012FD1:1
(String) VALUES
05/06/17 21:44:22.674 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: getParamset (2) Parameters:
(String) ITD00000400:0
(String) MASTER
05/06/17 21:44:22.677 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: getParamset (2) Parameters:
(String) ITD00000400:0
(String) VALUES
05/06/17 21:44:22.684 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: getParamset (2) Parameters:
(String) ITD00000400:1
(String) MASTER
05/06/17 21:44:22.687 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: getParamset (2) Parameters:
(String) ITD00000400:1
(String) VALUES
05/06/17 21:44:23.045 RPC client: Info: Calling RPC method "system.listMethods" on server binary://192.168.178.31.
05/06/17 21:44:23.078 RPC client: Info: Calling RPC method "newDevices" on server 192.168.178.31.
05/06/17 21:44:30.104 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: listBidcosInterfaces (2) Parameters:
05/06/17 21:44:45.109 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: listBidcosInterfaces (2) Parameters:
05/06/17 21:45:00.113 RPC Server (Port 2001): Info: Client number 32 is calling RPC method: listBidcosInterfaces (2) Parameters:
[21:45:02] root@openHABianPi:/media/usbstick/cul/nanoCUL#