Homematic Binding can not connect to Homegear after OH4 Upgrade

Setup, Configuration and Use Migration
, ,
21

09/06/23 16:19:03.309 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.

09/06/23 16:19:03.309 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.

09/06/23 16:19:03.309 RPC Server (Port 2001): Info: Enabling no authentication.

09/06/23 16:19:03.309 RPC Server (Port 2001): Info: Enabling session authentication for WebSockets.

09/06/23 16:19:03.309 Critical: Can’t start more threads. Thread limit reached (217 threads).

09/06/23 16:19:03.309 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.

09/06/23 16:19:03.309 RPC Server (Port 2002): Info: Enabling no authentication.

09/06/23 16:19:03.309 RPC Server (Port 2002): Info: Enabling session authentication for WebSockets.

09/06/23 16:19:03.350 Critical: Can’t start more threads. Thread limit reached (217 threads).

09/06/23 16:19:03.350 RPC Server (Port 2003): Info: Enabling basic authentication.

09/06/23 16:19:03.350 RPC Server (Port 2003): Info: Enabling client certificate authentication.

09/06/23 16:19:03.350 RPC Server (Port 2003): Info: Enabling session authentication for WebSockets.

09/06/23 16:19:03.388 RPC Server (Port 2004): 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.

09/06/23 16:19:03.389 RPC Server (Port 2004): Info: Enabling no authentication.

09/06/23 16:19:03.389 RPC Server (Port 2004): Info: Enabling session authentication for WebSockets.

09/06/23 16:19:03.389 Critical: Can’t start more threads. Thread limit reached (217 threads).

09/06/23 16:19:03.389 RPC Server (Port 2080): 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.

09/06/23 16:19:03.389 RPC Server (Port 2080): Info: Enabling no authentication.

09/06/23 16:19:03.389 RPC Server (Port 2080): Info: Enabling session authentication for WebSockets.

09/06/23 16:19:03.389 Critical: Can’t start more threads. Thread limit reached (217 threads).

09/06/23 16:19:03.389 RPC Server (Port 2443): Info: Enabling no authentication.

09/06/23 16:19:03.389 RPC Server (Port 2443): Info: Enabling session authentication for WebSockets.

22

changing seetings on one of the components of the MAX! install leads to nice reactions in the console. So something seems to be alive. It just does not endup in openhab.

23

Yes.

I believe this is your issue: something is spawning a lot of threads in HG before the HM server comes up, so it can’t spawn its own thread and thus doesn’t start up. Is there anything before that in the log?

I guess MAX does have its own handling in HG, though? What happens if you disable that one (in HG, not OH), does HM start working?

(That’s an obvious difference to my setup, BTW: I only use HM in Homegear)

24

09/06/23 18:15:21.168 Starting Homegear…

09/06/23 18:15:21.168 Homegear version: 0.8.1-3519

09/06/23 18:15:21.168 Determining maximum thread count…

09/06/23 18:15:22.333 Maximum thread count is: 217

09/06/23 18:15:22.480 Info: Backing up database…

09/06/23 18:15:22.584 Initializing database…

09/06/23 18:15:23.604 Homegear instance ID: 178211241CFEE859-00000000-AEBA-8CAC-7B48-AB3488AF206F

09/06/23 18:15:23.605 Debug: Loading licensing modules

09/06/23 18:15:23.606 Initializing system variable controller…

09/06/23 18:15:23.606 Debug: Loading family modules

09/06/23 18:15:23.607 Info: Loading family module (type 1) mod_miscellaneous.so

09/06/23 18:15:23.612 Info: Loading settings from /etc/homegear/families/miscellaneous.conf

09/06/23 18:15:23.615 Info: Loading translations from /var/lib/homegear/admin-ui/translations/modules/miscellaneous/

09/06/23 18:15:23.616 Info: Loading family module (type 1) mod_max.so

09/06/23 18:15:23.627 Info: Loading settings from /etc/homegear/families/max.conf

09/06/23 18:15:23.629 Info: Loading translations from /var/lib/homegear/admin-ui/translations/modules/max/

09/06/23 18:15:23.633 Info: Loading family module (type 1) mod_homematicbidcos.so

09/06/23 18:15:23.652 Info: Loading settings from /etc/homegear/families/homematicbidcos.conf

09/06/23 18:15:23.654 Info: Loading translations from /var/lib/homegear/admin-ui/translations/modules/homematicbidcos/

09/06/23 18:15:23.659 Info: Loading family module (type 1) mod_homematicwired.so

09/06/23 18:15:23.668 Info: Loading settings from /etc/homegear/families/homematicwired.conf

09/06/23 18:15:23.670 Info: Loading translations from /var/lib/homegear/admin-ui/translations/modules/homematicwired/

09/06/23 18:15:23.674 Info: Homegear is (now) running as user with id 111 and group with id 117.

09/06/23 18:15:23.676 Loading common translations…

09/06/23 18:15:23.785 Starting script engine server…

09/06/23 18:15:23.851 Initializing licensing controller…

09/06/23 18:15:23.851 Loading licensing controller data…

09/06/23 18:15:23.851 Loading devices…

09/06/23 18:15:23.851 Loading XML RPC devices…

09/06/23 18:15:25.182 Loading device 1

09/06/23 18:15:25.182 Module HomeMatic BidCoS: Info: Central address set to 0xFDBDC0.

09/06/23 18:15:25.183 Loading XML RPC devices…

09/06/23 18:15:25.246 Loading device 2

09/06/23 18:15:25.248 Loading XML RPC devices…

09/06/23 18:15:25.373 Loading device 3

09/06/23 18:15:25.373 Module MAX: Info: Central address set to 0xFD0C39.

09/06/23 18:15:25.375 Loading XML RPC devices…

09/06/23 18:15:25.380 Warning: variables with id “custom_ch7_values” does not exist.

09/06/23 18:15:25.391 Warning: configParameters with id “config” does not exist.

09/06/23 18:15:25.403 Warning: configParameters with id “config” does not exist.

09/06/23 18:15:25.409 Warning: variables with id “custom_ch7_values” does not exist.

09/06/23 18:15:25.421 Loading device 4

09/06/23 18:15:25.422 Initializing RPC client…

09/06/23 18:15:25.422 Initializing RPC server RPCServer1 listening on :::2001…

09/06/23 18:15:25.469 Initializing RPC server RPCServer2 listening on :::2002, SSL enabled…

09/06/23 18:15:25.515 Initializing RPC server RPCServer3 listening on :::2003, SSL enabled, authentication enabled…

09/06/23 18:15:25.560 Initializing RPC server RPCServer4 listening on 0.0.0.0:2004…

09/06/23 18:15:25.606 Initializing RPC server WebServer1 listening on :::2080…

09/06/23 18:15:25.654 Initializing RPC server WebServer2 listening on :::2443, SSL enabled…

09/06/23 18:15:25.704 Start listening for packets…

09/06/23 18:15:25.705 Starting IPC server…

09/06/23 18:15:25.712 Starting Node-BLUE server…

09/06/23 18:15:25.713 Info: Stopping Node-PINK WebSockets.

09/06/23 18:15:25.715 Critical: Can’t start more threads. Thread limit reached (217 threads).

25

so weit der log bis die threads überlaufen

26

My suggestion would be disabling modules: do you e.g. actually use HM-wired? That way, you could find out which module is spawning that huge number of threads. FWIW, HG has 114 threads spawned in my case.

27

already killed the wired part. No success :face_with_raised_eyebrow:

28

switched to settings in bidcos.conf. Still max threads

29

Hmm, I’m running out of ideas. Maybe check the HG forum? This post looks like.it might be related.

30

Thanks for your help anyway

Since homegear is connecting to the CUN and receiving packets I will look more into the handshaking between homematic binding and homegear.