I also enabled the debug logging for the homematic integration but i do not see any errors that would point me in the right direction. I restarted homeassistant and homematic multiple time but still no success.
Here is the debug log from restarting the ccu via homeassistant:
I’m searching the web for 3 days and sadly have not found any hint on what could be done to fix the problem. The three thermostats (not homematic ip) are not shown in homeassisatnt (no climate entity is present).
The problem probably is caused by your callback_ip and callback_port configuration. What is your reasoning to set these options manually? They are just needed in special setups.
If really needed, the callback_ip is the IP address at which the CCU would reach Home Assistant. 192.168.1.1 seems correct if that’s really the IP (however it’s unusual, because in such a subnet the .1 typically is your router).
The callback_port only works if you also set local_port. This should be a random port that is not being used by Home Assistant. This is NOT the port when you open Home Assistant in the brower. For HomeMatic a special server process with its own port (either dynamic or as specified by local_port) is started.
To sum this up: if you don’t have a reason to manually set the optional settings, then don’t. If it doesn’t work without them, read carefully what the optional settings really do.
I added the callback_ip and port because of the description in the homematic integration. There is stated that this can be used in combination with docker. I already tried to get it running without it but had no success.
I’ve removed them from the configuraiton but the problem remains the same, the homematic entities are not showing up in homeassistant.
Since there is no callback_ip and port set, homeassistant is listening on a address in the docker ip range. I’m not sure if this would work either.