Martin Herbst

Maybe they try to keep the amount of data in JSON as small as possible. But you are right, an "official" statement would be good.

@jlaur Please excuse my late answer. I am a bit busy at the moment. I will try to find allocate time in the next days to compare both source version....

I have got an installation with 5 heating groups on a Raspberrymatic system (CCU3 like system) with no problems. As far as I remember, this part of the binding code...

I think it would be necessary to install the bridge in Main UI, too. Because as far as I can see in the logs the requests causing the problems appear...

> I also suspect some kind of timing issue, that was introduced with 3.2, especially since calbackRegTimeout was introduced with 3.2. In addition to this the RpcClient init looks much...

> Maybe I also have to remove services/homematic.cfg? What did you configure here? Normally the CCU is automatically discovered after the binding has been installed or OH has been restarted....

I have compared the log files and I can see that the request sequence and the state changes of the bridge differ between both releases. You can now try the...

Thanks for your support. Will need some time to analyze the logs, but it really seems that there maybe are too many parallel requests for the CCU. The problem seems...

I am not sure whether this problem is really caused by the binding's code or by the Jetty version used. I have got several heating groups and non of them...

As far as I can see, the Homematic binding is also affected. It implements the `channelLinked` method to request the current values of all linked channels at startup.