Hi everyone,
First off, thanks for the great discussion and the work on the homematic binding.
I had similar issues as described above and some more, but found a workaround, so here goes.
First the problem itself:
I’ve experienced similar problems with the binding after updating to OH 3.1 (and meanwhile to 3.2), i.e. I got the "device-id “xyz” is not found on gateway-id “abc" error described above by @jochenfroehlich . But in addition some of my homematic things stopped updating their states, at random time intervals and, at least for me, in an unpredictable manner. Especially for door/window contacts, that’s quite problematic and it disrupts graphing and persistence based rules. This made my homematic devices close to useless in openhab, of course.
I’m very new to Openhab and also only have very rudimentary knowledge of Linux based systems, let alone programming in Java or Python.For the same reason I’m a little careful with manually installing addons etc.
I found a workaround in periodically disabling and reenabling the CCU thing via rule. I had been doing the same for weeks via the UI button, whenever I noticed the issue coming up again. This way, it’s much easier and I don’t have to monitor my system several times a day, at least.
I’m aware that manually installing the newer version of the binding is a better solution, but for newbies like me, this rule based workaround may also be a viable option, for a limited time at least. The rule itself is posted here:
Also, enabling and disabling things via rule may in itself be quite useful and I found it pretty hard to find a working solution for this in Openhab 3, since there seem to have been some changes. The REST requests for disabling/enabling things that worked in OH2 don’t work in OH 3 anymore (see above link).
Anyway, I hope this post still fits the topic here. It certainly was a revelation to get the rule running and have this automatic workaround until there is an official new version of the homematic binding available.
Keep up the great work!