OH4 - Homegear 0.8 - Homematic binding

Add-ons Bindings
1

Ok, I was trying to migrate to OH4. So far so good. Or not?

The setup of homegear together with homematic is absolutely not willing to work. As an optimistic I tried upgrading my 3.4 setup. Went to hell. Next I bought some new cards an got them setup. After spending several hours to manually adapt my old system to the new conditions I was stuck with homegear/homematic. Maybe it is caused by restoring my old configuration?
So once again. Make a fresh install. Wait for it to start. Get homegear installed through openhab-config. Get the homematic binding and hope for the best. Nope hours and hours spent it will not work.

It appears as if the homegear side might be working. At least I do see informations flowing back from thermostats to the cube and into homegear. Even though I am somewhat concerned with maximum threads reached very often while starting. What it does not say in the log is whether it simply discontinues trying to open ports (80, 443) and therefore never allows for a connection of homematic to homegear. Homematic constantly shows ERROR because of connection refused plus all this java stuff.

Anyone a nice idea how to get it working?

by the way. I am operating openhab on a raspi 3b+. For the time being with the old version of openhab

2

another fresh install and no success. Installed fresh OH4. Follow the initial setups. Rebootet. Installed homegear. Installed homematic and once again. Nothing.

With a fresh nightly install (0.9…) at least the ports 80 and 443 were no issue. Therefore the ipc crashed and homegear shut down.

reading through the specialists comments one would expect an immediate start more or less right after the setup.

3

openhab4 install LOG looks pretty much OK. Only npm suggestion to upgrade to 10.xx version.
homegear install through openhabian config does not come up with any error according to the LOG.

in Homegear LOG the following shows:
09/12/23 18:00:35.683 Starting Node-BLUE server…

09/12/23 18:00:35.683 Info: Stopping Node-PINK WebSockets.

and tons of:
Critical: Can’t start more threads. Thread limit reached (217 threads).

in the end it seems all ports could get connection:
09/12/23 18:00:35.702 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/12/23 18:00:35.702 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/12/23 18:00:35.702 RPC Server (Port 2001): Info: Enabling no authentication.

09/12/23 18:00:35.702 RPC Server (Port 2001): Info: Enabling session authentication for WebSockets.

09/12/23 18:00:35.702 Critical: Can’t start more threads. Thread limit reached (217 threads).

09/12/23 18:00:35.702 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/12/23 18:00:35.702 RPC Server (Port 2002): Info: Enabling no authentication.

09/12/23 18:00:35.702 RPC Server (Port 2002): Info: Enabling session authentication for WebSockets.

09/12/23 18:00:35.742 Critical: Can’t start more threads. Thread limit reached (217 threads).

09/12/23 18:00:35.742 RPC Server (Port 2003): Info: Enabling basic authentication.

09/12/23 18:00:35.743 RPC Server (Port 2003): Info: Enabling client certificate authentication.

09/12/23 18:00:35.743 RPC Server (Port 2003): Info: Enabling session authentication for WebSockets.

09/12/23 18:00:35.781 RPC Server (Port 2004): Info: Enabling no authentication.

09/12/23 18:00:35.781 RPC Server (Port 2004): Info: Enabling session authentication for WebSockets.

09/12/23 18:00:35.782 Critical: Can’t start more threads. Thread limit reached (217 threads).

09/12/23 18:00:35.782 RPC Server (Port 80): 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/12/23 18:00:35.782 RPC Server (Port 80): Info: Enabling no authentication.

09/12/23 18:00:35.782 RPC Server (Port 80): Info: Enabling session authentication for WebSockets.

09/12/23 18:00:35.783 Critical: Can’t start more threads. Thread limit reached (217 threads).

09/12/23 18:00:35.783 RPC Server (Port 443): Info: Enabling no authentication.

09/12/23 18:00:35.783 RPC Server (Port 443): Info: Enabling session authentication for WebSockets.

I assume that either the node pink shutdown is causing problems or the trouble with the threads.

All this is happening on a raspi 3B with 1 GB