Comfort Automation/ Security System Forums

Full Version: Failed to connect to UCM - please check the UCM Connection PORTS
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Ive recently run into a problem which this information *might* help others trying to use this great application. I have a Comfort system with a CBus and ETH3 UCM fitted. I run the Koochyrat software (slightly modified) on a RPi400 that links to my MQTT server on another RPi4. HA runs on a RPi5 and links to the MQTT server. Of course, this means I can control CBus lights etc from HA via MQTT and via the Python script that is looking at internal events on Comfort. Recently, I found I was unable to login using Comfigurator. I tried everything - new Ethernet cables; reset the ETH3 module; power off - nothing worked! I was looking at a (very expensive!) new ETH3 module, although I could ping the Comfort server and I could login via Julian Wigman\'s excellent application - Comfort Client v 5.1.6.2. But not Comfigurator! After many hours of frustration I noticed that my Comfiguarator network port was set to 1002 - as is the Koochyrat Python program! I changed this port to 1001 using the Options/Settings - and everything works!! How was it changed? I don\'t know - but I now have the port 1001 timeout set to 02 and port 1002 set to 00 (thanks, Slychiu, for that tip!). So, just make sure that your Comfigurator port is NOT the same as the Python access (or anything else)- and all appears well! I hope this tip -and the very useful error comment!! - helps......Smile
Good points. also check the Busy status of the 2 ports in comfort server manager. if the port is busy before you conect that means it is already being used