<![CDATA[Comfort Automation/ Security System Forums

<![CDATA[Comfort Automation/ Security System Forums - KNX Support]]> https://www.comfortforums.com/ Sun, 09 Aug 2026 00:08:33 +0000 MyBB <![CDATA[UCM/KNX with C-Bus to KNX Translator]]> https://www.comfortforums.com/thread-5220.html Wed, 16 Sep 2020 17:14:46 -0400 mgedrych]]> https://www.comfortforums.com/thread-5220.html D10 blinks red every now and then. D9 is steady red. D8 is off.

There is 29V at the KNX connector.

What might this mean?

Thanks

]]> D10 blinks red every now and then. D9 is steady red. D8 is off.

There is 29V at the KNX connector.

What might this mean?

Thanks

]]> <![CDATA[Counters (1-Bit) -&t KNX]]> https://www.comfortforums.com/thread-5026.html Tue, 26 Feb 2019 12:16:23 -0500 ]]> https://www.comfortforums.com/thread-5026.html
KNX -> Comfort...
0/4/7 (1-Bit) \'Blind up/down\' mapped to Counter031

Counter031 response...[indent]If LastUcmCounter = 0 Then[/indent][indent]Do BlindUp[/indent][indent]Else[/indent][indent]Do BlindDn[/indent][indent]End If[/indent] Counters->KNX (1-Bit)...
Counter031 mapped to 0/4/8 (1-Bit) \'Blind up/down status\'

In this instance (If I understand the UCM manual correctly) GA 0/4/7 should alter the value of counter 031, which should alter the state of GA 0/4/8.
In reality, when Group Address 0/4/7 is set to \'ON\' the blinds come down, and when Group Address 0/4/7 is set to \'OFF\' the blind go up and I can see the counter value change in Comfigurator (Comfort Registers) so this all seems to be correct.
However, the status value DOES NOT change in the status columns of the UCM and I don\'t see any telegrams to Group Address 0/4/8 in the group monitor on ETS, or any other indication that I\'m receiving feedback from the UCM_KNX2.
What am I doing wrong?
]]>
KNX -> Comfort...
0/4/7 (1-Bit) \'Blind up/down\' mapped to Counter031

Counter031 response...[indent]If LastUcmCounter = 0 Then[/indent][indent]Do BlindUp[/indent][indent]Else[/indent][indent]Do BlindDn[/indent][indent]End If[/indent] Counters->KNX (1-Bit)...
Counter031 mapped to 0/4/8 (1-Bit) \'Blind up/down status\'

In this instance (If I understand the UCM manual correctly) GA 0/4/7 should alter the value of counter 031, which should alter the state of GA 0/4/8.
In reality, when Group Address 0/4/7 is set to \'ON\' the blinds come down, and when Group Address 0/4/7 is set to \'OFF\' the blind go up and I can see the counter value change in Comfigurator (Comfort Registers) so this all seems to be correct.
However, the status value DOES NOT change in the status columns of the UCM and I don\'t see any telegrams to Group Address 0/4/8 in the group monitor on ETS, or any other indication that I\'m receiving feedback from the UCM_KNX2.
What am I doing wrong?
]]> <![CDATA[Error writing to KNX ]]> https://www.comfortforums.com/thread-4842.html Sun, 21 Jan 2018 02:18:50 -0500 ]]> https://www.comfortforums.com/thread-4842.html
This is probably due to a [color=\"#ff0000\"]very old UCM firmware[/color] (UCM/USB or UCM/ETH03) for the UCM used to program the system. The old UCM firmware is not able to support new features in Comfort or Comfigurator, and thus needs to be upgraded

The UCM firmware should be upgraded to the latest, by right clicking on the UCM under Modules and selecting \"Check for Firmware Upgrades\"

You will be asked to press F0 on the keypad to enable Engineer Mode

If you see that message, please press F0 on the keypad. This is a protection against unauthorised upgrade.
This will allow the firmware upgrade to start

]]>
This is probably due to a [color=\"#ff0000\"]very old UCM firmware[/color] (UCM/USB or UCM/ETH03) for the UCM used to program the system. The old UCM firmware is not able to support new features in Comfort or Comfigurator, and thus needs to be upgraded

The UCM firmware should be upgraded to the latest, by right clicking on the UCM under Modules and selecting \"Check for Firmware Upgrades\"

You will be asked to press F0 on the keypad to enable Engineer Mode

If you see that message, please press F0 on the keypad. This is a protection against unauthorised upgrade.
This will allow the firmware upgrade to start

]]> <![CDATA[KNX Programming via Comfort]]> https://www.comfortforums.com/thread-4836.html Sun, 07 Jan 2018 21:26:48 -0500 ]]> https://www.comfortforums.com/thread-4836.html I had a KNX system installed in my new home end of 2011 which controls heating and lighting and also had a Comfort II system installed which provides security as well as a few other things.

I am think of purchasing a copy of ETS so I can familiarize myself with KNX, see how it works, how I can make changes, etc. I know to communicate with KNX I need a KNX/USB or KNX/IP interface but these seem to run quite expensive.

Seeing as my Comfort II system has UCM/KNX module installed, will ETS allow me to configure KNX through this interface over the LAN, assuming I also have a UCM/ETH03 installed?
Or, will I have to just purchase a KNX IP or KNX USB interface?

Hope my question make sense, I am just getting started.

Many thanks!
]]> I had a KNX system installed in my new home end of 2011 which controls heating and lighting and also had a Comfort II system installed which provides security as well as a few other things.

I am think of purchasing a copy of ETS so I can familiarize myself with KNX, see how it works, how I can make changes, etc. I know to communicate with KNX I need a KNX/USB or KNX/IP interface but these seem to run quite expensive.

Seeing as my Comfort II system has UCM/KNX module installed, will ETS allow me to configure KNX through this interface over the LAN, assuming I also have a UCM/ETH03 installed?
Or, will I have to just purchase a KNX IP or KNX USB interface?

Hope my question make sense, I am just getting started.

Many thanks!
]]> <![CDATA[Bypass zone from KNX]]> https://www.comfortforums.com/thread-4739.html Mon, 28 Aug 2017 19:42:27 -0400 ]]> https://www.comfortforums.com/thread-4739.html I am using KNX2 firmware 7.097 and I have now implemented a \"Bypass\" feature in my KNX visualisation: Group addresses are mapped with register type \"Bypass Zone\" to individual zones. This works fine so far.
The surprising thing is that this while bypassing from a keypad needs a sign in the KNX bypass telegram works without any prior sign-in, regardless of the arming status and even in Away mode. This means a possible intruder could actually disable the alarm system without any signing in by accessing the KNX bus and sending to the correct group adresses.
Is there any way to make Comfort require a sign-in for a KNX bypass, similar to the \"Need Code\" setting for the keypad?
Thanks,Stefan]]> I am using KNX2 firmware 7.097 and I have now implemented a \"Bypass\" feature in my KNX visualisation: Group addresses are mapped with register type \"Bypass Zone\" to individual zones. This works fine so far.
The surprising thing is that this while bypassing from a keypad needs a sign in the KNX bypass telegram works without any prior sign-in, regardless of the arming status and even in Away mode. This means a possible intruder could actually disable the alarm system without any signing in by accessing the KNX bus and sending to the correct group adresses.
Is there any way to make Comfort require a sign-in for a KNX bypass, similar to the \"Need Code\" setting for the keypad?
Thanks,Stefan]]> <![CDATA[UCM2 is not a UCM/KNX2]]> https://www.comfortforums.com/thread-4658.html Tue, 14 Mar 2017 12:30:10 -0400 ]]> https://www.comfortforums.com/thread-4658.html Recently, I had some problems with UCM/KNX or UCM/KNX2.
When I try write to EEPROM, I have a error: \"UCM 2 is not a UCM/KNX2\". And when I try a second time I have a diferent error: \"Error writing configurator\".
If I try Read from EEPROM, I can but is isn\'t the configuration what I want.
How can I solve this problem?

Best regards,
Thanks.

.png

ERRO CYTECH.png (Size: 71.67 KB / Downloads: 26) ]]> Recently, I had some problems with UCM/KNX or UCM/KNX2.
When I try write to EEPROM, I have a error: \"UCM 2 is not a UCM/KNX2\". And when I try a second time I have a diferent error: \"Error writing configurator\".
If I try Read from EEPROM, I can but is isn\'t the configuration what I want.
How can I solve this problem?

Best regards,
Thanks.

.png

ERRO CYTECH.png (Size: 71.67 KB / Downloads: 26) ]]> <![CDATA[Incomplete zone status to KNX]]> https://www.comfortforums.com/thread-4600.html Sun, 08 Jan 2017 22:51:43 -0500 ]]> https://www.comfortforums.com/thread-4600.html
I have encountered an issue that after a reset only the status of the first 16 zones gets transmitted on the KNX bus (which can be seen as packets 1/7/1 ... 1/7/16 in the ETS diagnositic monitor).

Background:

I would like to display the status of my 24 Comfort zones inside my KNX visualization. For this I have mapped the zone status to a KNX address set 1/7/xxx in the UCM02 configuration.

As pointed out in this 5 year old topic it is not possible to read e.g. 1/7/8 via the KNX bus to get the status of Zone 08 as the UCM firmware is not capable of answering read requests (it\'s a pity that this has still not been implemented in the UCM02 firmware).

The recommended workaround in the above post was to force a system reset, either manually or e.g. via a custom response that would be hooked in when disarming.

This now does not work for me. I would need to manually open and close zones 17...24 in order to get the current status shown in the visualization every time the visualization is restarted (which is currently quite often as I am gradually enhancing the functionality).

I have verified that when e.g. zone 18 is opened this is correctly sent out as a 1/7/18 package on the bus.

Are there any plans to implement a KNX readable status or is there any other additional workaround?
]]>
I have encountered an issue that after a reset only the status of the first 16 zones gets transmitted on the KNX bus (which can be seen as packets 1/7/1 ... 1/7/16 in the ETS diagnositic monitor).

Background:

I would like to display the status of my 24 Comfort zones inside my KNX visualization. For this I have mapped the zone status to a KNX address set 1/7/xxx in the UCM02 configuration.

As pointed out in this 5 year old topic it is not possible to read e.g. 1/7/8 via the KNX bus to get the status of Zone 08 as the UCM firmware is not capable of answering read requests (it\'s a pity that this has still not been implemented in the UCM02 firmware).

The recommended workaround in the above post was to force a system reset, either manually or e.g. via a custom response that would be hooked in when disarming.

This now does not work for me. I would need to manually open and close zones 17...24 in order to get the current status shown in the visualization every time the visualization is restarted (which is currently quite often as I am gradually enhancing the functionality).

I have verified that when e.g. zone 18 is opened this is correctly sent out as a 1/7/18 package on the bus.

Are there any plans to implement a KNX readable status or is there any other additional workaround?
]]> <![CDATA[Bug in Comfigurator 3.11.0 to 3.11.1]]> https://www.comfortforums.com/thread-4438.html Mon, 18 Apr 2016 11:55:32 -0400 ]]> https://www.comfortforums.com/thread-4438.html Writing to EEPROM for UCM/KNX writes empty data, so the group addresses mapping is lost

This was found for Comfigurator 3.11.0 and 3.11.1

DO NOT write to EEPROM otherwise the data will be blank

3.11.2 will fix this problem
]]> Writing to EEPROM for UCM/KNX writes empty data, so the group addresses mapping is lost

This was found for Comfigurator 3.11.0 and 3.11.1

DO NOT write to EEPROM otherwise the data will be blank

3.11.2 will fix this problem
]]> <![CDATA[UCM/KNX race condition]]> https://www.comfortforums.com/thread-4436.html Sat, 16 Apr 2016 10:51:40 -0400 ]]> https://www.comfortforums.com/thread-4436.html
There looks to be a race condition within Comfort (7.0.92) and/or UCM/KNX (7.0.30). If I send two consecutive telegrams to switch on and off some load, then Comfort starts emitting an endless stream of on-off telegrams and I need to reset the unit. I\'ve noticed this today when I heard that relay clicking on and off twice per second.

In the attached screenshot a Zennio Z38i touchscreen (phys. addr. = 1.1.11) is sending two telegrams, an ON and an OFF, after which Comfort starts sending an endless stream of on and off telegrams. This looks to be a race condition of sorts.

The group address is mapped to counter #139 (\'KNX-3-0-3\')

Code:
&nbsp;&nbsp;&nbsp;&nbsp; &lt;Counter Number=\"139\" Name=\"KNX-3-0-3\" /&gt;

...

&nbsp;&nbsp; &nbsp; &lt;UcmKnxToComfort Type=\"OneBitSwitching\" GroupAddress=\"6147\" ItemNumber=\"139\" /&gt;

The relevant counter is only mapped to a control menu item, and it has two simple responses to turn the load on or off as follows:

Code:
&nbsp;&nbsp;&nbsp; &lt;Response Fixed=\"false\" Number=\"109\" Description=\"anakykloforia ZNX\" Name=\"KNX_3_0_3_ON\" ActionCodeString=\"197,18,2,24,3,1, 255\"&gt;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;ActionSource&gt;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;string&gt;Knx On UCM02_KNX 6147 ! 3/0/3&lt;/string&gt;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/ActionSource&gt;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;Errors /&gt;

&nbsp;&nbsp;&nbsp; &lt;/Response&gt;

&nbsp;&nbsp;&nbsp; &lt;Response Fixed=\"false\" Number=\"110\" Description=\"anakykloforia ZNX OFF\" Name=\"KNX_3_0_3_OFF\" ActionCodeString=\"197,18,2,24,3,0, 255\"&gt;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;ActionSource&gt;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;string&gt;Knx Off UCM02_KNX 6147 ! 3/0/3&lt;/string&gt;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/ActionSource&gt;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;Errors /&gt;

&nbsp;&nbsp;&nbsp; &lt;/Response&gt;

&nbsp;

This is difficult to reproduce (it doesn\'t happen always), however whenever it happens its very annoying as it clogs down the bus and it can cause premature wear to the relays.

.png

race_condition.png (Size: 67.77 KB / Downloads: 16) ]]>
There looks to be a race condition within Comfort (7.0.92) and/or UCM/KNX (7.0.30). If I send two consecutive telegrams to switch on and off some load, then Comfort starts emitting an endless stream of on-off telegrams and I need to reset the unit. I\'ve noticed this today when I heard that relay clicking on and off twice per second.

In the attached screenshot a Zennio Z38i touchscreen (phys. addr. = 1.1.11) is sending two telegrams, an ON and an OFF, after which Comfort starts sending an endless stream of on and off telegrams. This looks to be a race condition of sorts.

The group address is mapped to counter #139 (\'KNX-3-0-3\')

Code:
&nbsp;&nbsp;&nbsp;&nbsp; &lt;Counter Number=\"139\" Name=\"KNX-3-0-3\" /&gt;

...

&nbsp;&nbsp; &nbsp; &lt;UcmKnxToComfort Type=\"OneBitSwitching\" GroupAddress=\"6147\" ItemNumber=\"139\" /&gt;

The relevant counter is only mapped to a control menu item, and it has two simple responses to turn the load on or off as follows:

Code:
&nbsp;&nbsp;&nbsp; &lt;Response Fixed=\"false\" Number=\"109\" Description=\"anakykloforia ZNX\" Name=\"KNX_3_0_3_ON\" ActionCodeString=\"197,18,2,24,3,1, 255\"&gt;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;ActionSource&gt;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;string&gt;Knx On UCM02_KNX 6147 ! 3/0/3&lt;/string&gt;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/ActionSource&gt;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;Errors /&gt;

&nbsp;&nbsp;&nbsp; &lt;/Response&gt;

&nbsp;&nbsp;&nbsp; &lt;Response Fixed=\"false\" Number=\"110\" Description=\"anakykloforia ZNX OFF\" Name=\"KNX_3_0_3_OFF\" ActionCodeString=\"197,18,2,24,3,0, 255\"&gt;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;ActionSource&gt;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;string&gt;Knx Off UCM02_KNX 6147 ! 3/0/3&lt;/string&gt;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/ActionSource&gt;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;Errors /&gt;

&nbsp;&nbsp;&nbsp; &lt;/Response&gt;

&nbsp;

This is difficult to reproduce (it doesn\'t happen always), however whenever it happens its very annoying as it clogs down the bus and it can cause premature wear to the relays.

.png

race_condition.png (Size: 67.77 KB / Downloads: 16) ]]> <![CDATA[KNX UCM]]> https://www.comfortforums.com/thread-4359.html Mon, 16 Nov 2015 09:40:07 -0500 ]]> https://www.comfortforums.com/thread-4359.html Regards Paul]]> Regards Paul]]> <![CDATA[Upgrading UCM/Knx]]> https://www.comfortforums.com/thread-4120.html Thu, 05 Feb 2015 11:19:30 -0500 ]]> https://www.comfortforums.com/thread-4120.html Can you tell me what are the best versions of Comfigurator, Controller (Comfort II Ultra) and UCM/Eth03 to be able to upgrade old KNX? And what is the best way to do it, cable or local file?

Thanks]]> Can you tell me what are the best versions of Comfigurator, Controller (Comfort II Ultra) and UCM/Eth03 to be able to upgrade old KNX? And what is the best way to do it, cable or local file?

Thanks]]> <![CDATA[KNX 1 bit switching map to Comfort Away Arm not working]]> https://www.comfortforums.com/thread-3621.html Mon, 25 Nov 2013 06:30:00 -0500 ]]> https://www.comfortforums.com/thread-3621.html
I was trying to map KNX button to Comfort Away Arm.
But I is not working.

Besides that, then \"Learn\" function is not working too.

I am able to test the \"On\", \"Off\" by manually set the KNX address.

Please guide me on this.

Comfort OPT version: 6.028
UCM/KNX version: 6.112

Edit: KNX to Comfort is not working, but Comfort to KNX is working fine.

Thank you!]]>
I was trying to map KNX button to Comfort Away Arm.
But I is not working.

Besides that, then \"Learn\" function is not working too.

I am able to test the \"On\", \"Off\" by manually set the KNX address.

Please guide me on this.

Comfort OPT version: 6.028
UCM/KNX version: 6.112

Edit: KNX to Comfort is not working, but Comfort to KNX is working fine.

Thank you!]]> <![CDATA[UCM/KNX in Monitor Mode]]> https://www.comfortforums.com/thread-3286.html Mon, 18 Feb 2013 03:03:27 -0500 ]]> https://www.comfortforums.com/thread-3286.html In Monitor mode, the KNX to Comfort mapping does NOT work

If you leave the Monitor tab that ends the monitor mode and KNX to Comfort commands will work again

However, we have found that if you log out or close comfigurator without leaving the monitor mode tab, then the UUCM/KNX remains in Monitor mode and KNX to Comfort commands will NOT WORK

We shall try to fix this in Comfigurator (currentlly 3.6.4)
In the meantime, please ensure that you leave Monitor mode always before leaving the UCM/KNX

The UCM/KNX Manual has been updated with this warning
https://www.cytech.biz/ucmknx_manual.htm...ory_id=107

]]> In Monitor mode, the KNX to Comfort mapping does NOT work

If you leave the Monitor tab that ends the monitor mode and KNX to Comfort commands will work again

However, we have found that if you log out or close comfigurator without leaving the monitor mode tab, then the UUCM/KNX remains in Monitor mode and KNX to Comfort commands will NOT WORK

We shall try to fix this in Comfigurator (currentlly 3.6.4)
In the meantime, please ensure that you leave Monitor mode always before leaving the UCM/KNX

The UCM/KNX Manual has been updated with this warning
https://www.cytech.biz/ucmknx_manual.htm...ory_id=107

]]> <![CDATA[KNX Support Subforums]]> https://www.comfortforums.com/thread-3109.html Fri, 05 Oct 2012 08:45:43 -0400 ]]> https://www.comfortforums.com/thread-3109.html
The support-related topics have been moved from the main forum into this subforum

Those who would like to follow this forum please remember to Watch this Forum in Menu > My Account so that emails or Daily Digest can be sent to you when new topics or replies are posted]]>
The support-related topics have been moved from the main forum into this subforum

Those who would like to follow this forum please remember to Watch this Forum in Menu > My Account so that emails or Daily Digest can be sent to you when new topics or replies are posted]]> <![CDATA[Sending Floating Point Type Telegram to KNX]]> https://www.comfortforums.com/thread-3071.html Fri, 14 Sep 2012 23:01:36 -0400 ]]> https://www.comfortforums.com/thread-3071.html
This has now been fixed in Comfigurator 3.5.6, the latest release, see http://www.comfortforums.com/view_topic.php?id=3036&forum_id=20&jump_to=12957#p12957

It is advisable to upgrade to the new Comfigurator as well as to the latest UCM/KNX firmware
]]>
This has now been fixed in Comfigurator 3.5.6, the latest release, see http://www.comfortforums.com/view_topic.php?id=3036&forum_id=20&jump_to=12957#p12957

It is advisable to upgrade to the new Comfigurator as well as to the latest UCM/KNX firmware
]]>