Homematic Binding: not all devices read from CCU

Hello,

my name is Rayk. I am a software developer and have been involved in home automation for 15 years now.
Since I lack the time to keep my self-developed home automation system up to date, I am currently looking at openHAB 3.2.
I mainly use devices of the Homematic system. Currently I have the following problems using the Homematic binding.

I have a CCU2 with about 70 Homematic and Homematic IP devices in use.
After configuring, a few devices are missing from the ‘INBOX’. Even with a rescan the devices are not found.
When debugging the binding I found that the devices are present in the device list sent from the CCU to the binding.
For all devices the binding reads the device description from the CCU individually. The whole process obviously takes so long that the reading of the device description is aborted. So I changed the parameter ‘Install Mode Duration’ in the binding configuration from 60s (default) to 120s. After that all devices are found during a new scan. In my opinion the parameter should only be used for teaching the devices to the CCU, but not for reading the devices from the CCU into openHAB.

The second (bigger problem) for which I can’t find a solution is the following:
After restarting openHAB, the Things (Homematic devices), which could only be created by setting the ‘Install Mode Duration’ parameter high, show the error “CONFIG: ERROR” (Device with address ‘ABC’ not found on gateway ‘xyz’) and show no reaction in openHAB.
After a new, manually triggered scan, the Things are ready for use again.

What can I do to work around this bug? Running a manual scan after every reboot is absolutely not an option.

Greetings,
Rayk

1 Like

I have the same problem since last week. Increasing the discover time helped me at first.
Now some devices are missing on every restart of openHAB!

I’m having a similar issue, not sure for how long, but I remember not having had this when I started with OH 3.1.0: After rebooting OH, not all things manage to get online with the Device with address 'xxx' not found on gateway 'yyy' error message

2022-03-17 20:16:38.328 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'homematic:HMIP-SWDO:MEQ0227988:0000DD898C64A9' changed from INITIALIZING to ONLINE
2022-03-17 20:16:38.457 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Thermostat_Garten_Humidity' changed from 69 to 69 %
2022-03-17 20:16:39.881 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'homematic:HmIP-SMI:MEQ0227988:00091D899E19B2' changed from INITIALIZING to ONLINE
2022-03-17 20:16:40.039 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Rolladen_Kueche_Rechts_Stop' changed from OFF to NULL
2022-03-17 20:16:41.408 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'homematic:HmIP-BSL:MEQ0227988:001A5BE9A65495' changed from INITIALIZING to ONLINE
2022-03-17 20:16:42.884 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'homematic:HmIP-BROLL:MEQ0227988:00111A49A8DEF0' changed from INITIALIZING to OFFLINE (CONFIGURATION_ERROR): Device with address '00111A49A8DEF0' not found on gateway 'MEQ0227988'
2022-03-17 20:16:42.888 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'homematic:HmIP-BROLL:MEQ0227988:00111A49A8DDCC' changed from INITIALIZING to OFFLINE (CONFIGURATION_ERROR): Device with address '00111A49A8DDCC' not found on gateway 'MEQ0227988'
2022-03-17 20:16:42.891 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'homematic:HmIP-BROLL:MEQ0227988:00111A49A8DDD0' changed from INITIALIZING to OFFLINE (CONFIGURATION_ERROR): Device with address '00111A49A8DDD0' not found on gateway 'MEQ0227988'

This is especially odd because most devices manage to get online.

Does anyone have an idea?

Do you have CCU2 or CCU3? It seems that this problem only occurs if a CCU2 is used.

Can you enable TRACE log mode, restart OH and post the relevant parts from openHAB. Maybe it provides some more information. Maybe it is possible to raise an OH internal timeout.

Thanks! I’m currently trying out something different, since I have the impression that this problem is somehow related to various other connection-unstability-problems I keep having (also see here).

Since I’m running everything on Raspi/Docker, I could re-install and restore my entire system this morning in <30 minutes, so I’m curious to see whether all the connection problems are now (hopefully) solved.