<![CDATA[Comfort Automation/ Security System Forums - UCM/KNX Firmware]]> https://www.comfortforums.com/ Tue, 28 Jul 2026 02:55:47 +0000 MyBB <![CDATA[UCM/KNX 8.002]]> https://www.comfortforums.com/thread-5571.html Tue, 19 Nov 2024 20:54:52 -0500 ]]> https://www.comfortforums.com/thread-5571.html UCM/KNX2 8.002
Affects Arm and Non-arm
  • Fixed Bug Learn Mode in KNX to Comfort does not work sometimes
  • UCM/KNX updates counters, sensors, Inputs, Flags, and Alarms  to mapped KNX group addresses when UCM/KNX first detects KNX bus message incoming
  • If knx to Comfort has mapping to Flags, Counters, Sensors, Inputs, the same Flags, Counters, Sensors, Inputs to KNX can map to different KNX addresses in the respective tabs
]]> UCM/KNX2 8.002
Affects Arm and Non-arm
  • Fixed Bug Learn Mode in KNX to Comfort does not work sometimes
  • UCM/KNX updates counters, sensors, Inputs, Flags, and Alarms  to mapped KNX group addresses when UCM/KNX first detects KNX bus message incoming
  • If knx to Comfort has mapping to Flags, Counters, Sensors, Inputs, the same Flags, Counters, Sensors, Inputs to KNX can map to different KNX addresses in the respective tabs
]]> <![CDATA[UCM/KNX2 firmware 7.122 to 7.131]]> https://www.comfortforums.com/thread-5086.html Sun, 21 Jul 2019 00:34:34 -0400 ]]> https://www.comfortforums.com/thread-5086.html
  • KNX Monitor mode includes Send to KNX
  • UCM/KNX2 alarms and Inputs to KNX work with Partitioned alarm system. Older Firmware does not support partitions

    • ]]>
  • KNX Monitor mode includes Send to KNX
  • UCM/KNX2 alarms and Inputs to KNX work with Partitioned alarm system. Older Firmware does not support partitions

    • ]]>         <![CDATA[Comfort as a KNX device]]> https://www.comfortforums.com/thread-5049.html Sun, 21 Apr 2019 05:17:07 -0400 ]]> https://www.comfortforums.com/thread-5049.html Comfort need to part of the KNX project file device list.
    When programming in KNX tracing the source of where things come from and go to is essential. 
    So taking a basic example of using Comfort (internet) time. Setting this up from the Comfort side is easy it simply requires a KNX group address to be input into event 33 and 34 of the KNX UCM schedule.
    HOWEVER looking from the KNX ETS program side there is no way of telling that the Comfort telegram is being used (apart from ..... (1) monitoring the address (2) using a dummy KNX device (Ive called it Comfort alarm and got it grom the GIRA device list).

    ]]>     Comfort need to part of the KNX project file device list.
    When programming in KNX tracing the source of where things come from and go to is essential. 
    So taking a basic example of using Comfort (internet) time. Setting this up from the Comfort side is easy it simply requires a KNX group address to be input into event 33 and 34 of the KNX UCM schedule.
    HOWEVER looking from the KNX ETS program side there is no way of telling that the Comfort telegram is being used (apart from ..... (1) monitoring the address (2) using a dummy KNX device (Ive called it Comfort alarm and got it grom the GIRA device list).

    ]]>         <![CDATA[UCM/KNX2 7.087 to 7.097]]> https://www.comfortforums.com/thread-4728.html Mon, 07 Aug 2017 12:30:12 -0400 ]]> https://www.comfortforums.com/thread-4728.html KNX 7.087
    Bugs
    1. Date and Time from KNX (when mapped to KNX) did not get sent to Comfort
    Bugs Fixed
    1. Fixed Bug - bypass zone to KNX did not work
    2. Fixed bug on Bypass zones to KNX
    3. Fixed bugs in security modes to KNX.
    4. Fixed bugs in EIS10 2 byte counter, EIS5. sFixed bugs in EIS10 2 byte counter, EIS5.
    5. Fixed BUG: Action send command to KNX does not update Comfort register which is mapped to the KNX address
    Changes
    1. Even if counter> KNX 1 bit programmed, send to KNX > Comfort 1-byte group address if present. Even if counter> KNX 1 byte programmed, send to KNX > Comfort 1 bit group address if present
    2. When sensor value changes, send sensor value to mapped KNX address KNX to Comfort mapped to Comfort sensor.
    3. When security mode changes, send value to KNX to Comfort for security mode group address.
    4. Added Status Message  \"invalid physical address\"
    5. UCM/KNX2 Status Error will appear if no confirmation for telegram to KNX.
    6. Improved status report to Comfigurator
    7. If no EEPROM, flash ERR LED


    UCM/KNX1 firmware 7.079 can be upgraded to UCM/KNX2
    ]]>     KNX 7.087
    Bugs
    1. Date and Time from KNX (when mapped to KNX) did not get sent to Comfort
    Bugs Fixed
    1. Fixed Bug - bypass zone to KNX did not work
    2. Fixed bug on Bypass zones to KNX
    3. Fixed bugs in security modes to KNX.
    4. Fixed bugs in EIS10 2 byte counter, EIS5. sFixed bugs in EIS10 2 byte counter, EIS5.
    5. Fixed BUG: Action send command to KNX does not update Comfort register which is mapped to the KNX address
    Changes
    1. Even if counter> KNX 1 bit programmed, send to KNX > Comfort 1-byte group address if present. Even if counter> KNX 1 byte programmed, send to KNX > Comfort 1 bit group address if present
    2. When sensor value changes, send sensor value to mapped KNX address KNX to Comfort mapped to Comfort sensor.
    3. When security mode changes, send value to KNX to Comfort for security mode group address.
    4. Added Status Message  \"invalid physical address\"
    5. UCM/KNX2 Status Error will appear if no confirmation for telegram to KNX.
    6. Improved status report to Comfigurator
    7. If no EEPROM, flash ERR LED


    UCM/KNX1 firmware 7.079 can be upgraded to UCM/KNX2
    ]]>         <![CDATA[KNX 7.076 Beta]]> https://www.comfortforums.com/thread-4452.html Thu, 19 May 2016 13:34:56 -0400 ]]> https://www.comfortforums.com/thread-4452.html
    1. [size=\"3\"]In some rare circumstances the D3 BUSY2 stayed on until UCM/KNX is reset. To fix this a reinitialisation  timer of 4 minutes was added. This should not affect normal operation[/size]
    2. [size=\"3\"]Enabled audio for ucm/knx so aud01 can be connected on knx ucm for special applications[/size]
    3. [size=\"3\"]Allow  upgrade to UCM/KNX2.[/size]
    4. [size=\"3\"]fixed  problem of counter racing when KNX initiate counter change which is  broadcast back to UCM/KNX again[/size]
    [size=\"3\"]Please download for testing from https://www.cytech.biz/product_details.php?item_id=232[/size]

    ]]>
    1. [size=\"3\"]In some rare circumstances the D3 BUSY2 stayed on until UCM/KNX is reset. To fix this a reinitialisation  timer of 4 minutes was added. This should not affect normal operation[/size]
    2. [size=\"3\"]Enabled audio for ucm/knx so aud01 can be connected on knx ucm for special applications[/size]
    3. [size=\"3\"]Allow  upgrade to UCM/KNX2.[/size]
    4. [size=\"3\"]fixed  problem of counter racing when KNX initiate counter change which is  broadcast back to UCM/KNX again[/size]
    [size=\"3\"]Please download for testing from https://www.cytech.biz/product_details.php?item_id=232[/size]

    ]]>         <![CDATA[KNX 7.030 ]]> https://www.comfortforums.com/thread-3780.html Sat, 19 Apr 2014 12:02:22 -0400 ]]> https://www.comfortforums.com/thread-3780.html
    This fixes the bug from 6.111/6/112 that sending a telegram to KNX also triggers the counter response for the mapped group address.

    Sending a telegram to KNX should update the mapped Comfort counter but it should not activate the Counter Response
    ]]>
    This fixes the bug from 6.111/6/112 that sending a telegram to KNX also triggers the counter response for the mapped group address.

    Sending a telegram to KNX should update the mapped Comfort counter but it should not activate the Counter Response
    ]]>         <![CDATA[KNX 6.111 and 6.112]]> https://www.comfortforums.com/thread-3291.html Wed, 20 Feb 2013 07:04:49 -0500 ]]> https://www.comfortforums.com/thread-3291.html
    1. Fixed BUG from KNX 6.024 - KNX to Comfort mapping for Keypad Keys, Arm commands, Panic, Bypass Zones, and Zones  did not work. Map to Counters, Sensors, Virtual Inputs do work
    2. Function to use COPY button to press and hold to change UCM/KNX ID has been implemented. However this only affects UCM/KNX which has the pushbutton available.
    KNX 1 bit and 1 byte objects mapped to Comfort Counters are ignored if the value is unchanged, eg On command folllowed by another ON command, or Off comand followed by another off command, or the same value in a 1 byte object


    ]]>
    1. Fixed BUG from KNX 6.024 - KNX to Comfort mapping for Keypad Keys, Arm commands, Panic, Bypass Zones, and Zones  did not work. Map to Counters, Sensors, Virtual Inputs do work
    2. Function to use COPY button to press and hold to change UCM/KNX ID has been implemented. However this only affects UCM/KNX which has the pushbutton available.
    KNX 1 bit and 1 byte objects mapped to Comfort Counters are ignored if the value is unchanged, eg On command folllowed by another ON command, or Off comand followed by another off command, or the same value in a 1 byte object


    ]]>         <![CDATA[KNX 6.024]]> https://www.comfortforums.com/thread-3058.html Thu, 06 Sep 2012 09:41:08 -0400 ]]> https://www.comfortforums.com/thread-3058.html https://www.cytech.biz/ucmknx_firmware.h...ory_id=101

    Known Bugs

    1. KNX to Comfort for Keypad keys, Panic, Time, Date, Arm system, Bypass zone do not work.
    Bugs Fixed
    1. If a Floating Point Telegram Type is mapped to a Sensor, receiving a telegram may cause a telegram to be sent to KNX with the value of 1. This problem was reported in http://www.comfortforums.com/forum12/2150.html
    2. If a 1-bit Drive Control Telegram is mapped to a counter 255 this may cause a spurious Response from Comfort to KNX.  This problem was reported in http://www.comfortforums.com/forum12/2816.html
    Improvements
    1. Send Floating Point EIS5 Telegram allows -32768 to + 32767
    Please note that products purchased  may not have the latest firmware. Firmware can be upgraded using another  UCM and Comfigurator

    ]]>     https://www.cytech.biz/ucmknx_firmware.h...ory_id=101

    Known Bugs

    1. KNX to Comfort for Keypad keys, Panic, Time, Date, Arm system, Bypass zone do not work.
    Bugs Fixed
    1. If a Floating Point Telegram Type is mapped to a Sensor, receiving a telegram may cause a telegram to be sent to KNX with the value of 1. This problem was reported in http://www.comfortforums.com/forum12/2150.html
    2. If a 1-bit Drive Control Telegram is mapped to a counter 255 this may cause a spurious Response from Comfort to KNX.  This problem was reported in http://www.comfortforums.com/forum12/2816.html
    Improvements
    1. Send Floating Point EIS5 Telegram allows -32768 to + 32767
    Please note that products purchased  may not have the latest firmware. Firmware can be upgraded using another  UCM and Comfigurator

    ]]>         <![CDATA[KNX 6.015 ]]> https://www.comfortforums.com/thread-2670.html Fri, 30 Dec 2011 23:25:06 -0500 ]]> https://www.comfortforums.com/thread-2670.html
    1. KNX relative dim levels are wrong when SCALE switch is shunted
    2. KNX Floating point EIS5 calculation wrong


    Those who are affected by these problems please upgrade to test, and let us know the results


    .zip   KNX6_015.zip (Size: 16.48 KB / Downloads: 0) ]]>
    1. KNX relative dim levels are wrong when SCALE switch is shunted
    2. KNX Floating point EIS5 calculation wrong


    Those who are affected by these problems please upgrade to test, and let us know the results


    .zip   KNX6_015.zip (Size: 16.48 KB / Downloads: 0) ]]>         <![CDATA[KNX 6.011]]> https://www.comfortforums.com/thread-2567.html Sun, 06 Nov 2011 01:14:31 -0400 ]]> https://www.comfortforums.com/thread-2567.html Please download firmware file from https://www.cytech.biz/product_details.php?item_id=232
    ]]>     Please download firmware file from https://www.cytech.biz/product_details.php?item_id=232
    ]]>         <![CDATA[UCM/KNX 5.234]]> https://www.comfortforums.com/thread-2294.html Fri, 10 Jun 2011 08:11:16 -0400 ]]> https://www.comfortforums.com/thread-2294.html https://www.cytech.biz/ucmknx_firmware.html
    A new UCM/KNX manual is also available from https://www.cytech.biz/ucmknx_manual.html

    Known Issues

    1. KNX relative dim levels are wrong when SCALE switch is shunted
    2. KNX Floating point EIS5 calculation wrong

    Bugs Fixed
    1. When zones are bypassed from Comfort, the mapped KNX group address is not updated with the bypass state
    Note that Comfigurator 3.2.9 allows the UCM/KNX Physical address to specify Area 0 (previously areas 1 to 15 only), Line 0 (previously 1 to 15 only) and Address 1 to 255 (previously 1 to 200). This is not a firmware function
    ]]>     https://www.cytech.biz/ucmknx_firmware.html
    A new UCM/KNX manual is also available from https://www.cytech.biz/ucmknx_manual.html

    Known Issues

    1. KNX relative dim levels are wrong when SCALE switch is shunted
    2. KNX Floating point EIS5 calculation wrong

    Bugs Fixed
    1. When zones are bypassed from Comfort, the mapped KNX group address is not updated with the bypass state
    Note that Comfigurator 3.2.9 allows the UCM/KNX Physical address to specify Area 0 (previously areas 1 to 15 only), Line 0 (previously 1 to 15 only) and Address 1 to 255 (previously 1 to 200). This is not a firmware function
    ]]>         <![CDATA[UCM/KNX 5.213]]> https://www.comfortforums.com/thread-1876.html Wed, 09 Jun 2010 00:50:06 -0400 ]]> https://www.comfortforums.com/thread-1876.html New Features
    1. When UCM/KNX is connected to Comfort, existing Trouble and bypass conditions are reported to KNX
    2. When UCM/KNX is  reset, all trouble conditions and zone states are reported to KNX
    3. KNX Configurator KNX to Comfort has new KNX type called Virtual Inputs where KNX group addresses are assigned as Virtual Inputs, and the physical input in Security > Zone Types is set as Virtual Input and is ignored. This allows KNX PIRs to be treated as Comfort Inputs. Requires Comfort Firmware 5.195 and Comfigurator 3.2.1 which supports Virtual Inputs
    Bug Fixes
    1. When zone is in Trouble state, other zone on or off would restore the zone trouble
    2. When any Trouble condition is restored, a prevaling RS485 Communications failure is reported as AC Failure
    Known Bugs
    1. KNX relative dim levels are wrong when SCALE switch is shunted
    2. KNX Floating point EIS5 calculation wrong
    3. When a zone is bypassed on Comfort the Bypass state of the zone is not sent to KNX
     

     


    .zip   KNX5_213.zip (Size: 14.13 KB / Downloads: 13) ]]>     New Features
    1. When UCM/KNX is connected to Comfort, existing Trouble and bypass conditions are reported to KNX
    2. When UCM/KNX is  reset, all trouble conditions and zone states are reported to KNX
    3. KNX Configurator KNX to Comfort has new KNX type called Virtual Inputs where KNX group addresses are assigned as Virtual Inputs, and the physical input in Security > Zone Types is set as Virtual Input and is ignored. This allows KNX PIRs to be treated as Comfort Inputs. Requires Comfort Firmware 5.195 and Comfigurator 3.2.1 which supports Virtual Inputs
    Bug Fixes
    1. When zone is in Trouble state, other zone on or off would restore the zone trouble
    2. When any Trouble condition is restored, a prevaling RS485 Communications failure is reported as AC Failure
    Known Bugs
    1. KNX relative dim levels are wrong when SCALE switch is shunted
    2. KNX Floating point EIS5 calculation wrong
    3. When a zone is bypassed on Comfort the Bypass state of the zone is not sent to KNX
     

     


    .zip   KNX5_213.zip (Size: 14.13 KB / Downloads: 13) ]]>         <![CDATA[UCM/KNX Firmware]]> https://www.comfortforums.com/thread-1858.html Tue, 25 May 2010 09:16:25 -0400 ]]> https://www.comfortforums.com/thread-1858.html [size=\"3\"]KNX 5.203 (30 April 2010)[/size]
    New Features
    1. added Zone Not Ready 1 byte object with value of zone number
    Bugs Fixed
    1. Arm Ready 1 bit group address does not work
    Known Issues
    1. KNX relative dim levels are wrong when SCALE switch is shunted
    2. KNX Floating point EIS5 calculation wrong
    3. when any Comfort Trouble condition is restored, the Rs485 communications failure affects the AC Fail condtion for the Mapped KNX group address. Hence if Comms fail is restored, so is AC Fail
    4. Mapping of KNX group addresses to Counters > 128 do not work. Please keep to counter numbers < 128
    5. When a Zone Trouble condition is seen by the KNX mapped group address, another zone on or off will clear the KNX Zone trouble condition
    6. Date to KNX may be wrong
    7. If Slave is installed, Bypass Zone mapping to Group address does not work
    8. When a zone is bypassed on Comfort the Bypass state of the zone is not sent to KNX
    [size=\"3\"]KNX 5.195 (Initial Release 4 August 2009)[/size]

    Known Issues
    1. Mapping of KNX group addresses to Counters > 128 do not work. Please keep to counter numbers < 128
    2. Arm Ready 1 bit group address does not work
    3. Date to KNX may be wrong
    4. If Slave is installed, Bypass Zone mapping to Group address does not work
    ]]>     [size=\"3\"]KNX 5.203 (30 April 2010)[/size]
    New Features
    1. added Zone Not Ready 1 byte object with value of zone number
    Bugs Fixed
    1. Arm Ready 1 bit group address does not work
    Known Issues
    1. KNX relative dim levels are wrong when SCALE switch is shunted
    2. KNX Floating point EIS5 calculation wrong
    3. when any Comfort Trouble condition is restored, the Rs485 communications failure affects the AC Fail condtion for the Mapped KNX group address. Hence if Comms fail is restored, so is AC Fail
    4. Mapping of KNX group addresses to Counters > 128 do not work. Please keep to counter numbers < 128
    5. When a Zone Trouble condition is seen by the KNX mapped group address, another zone on or off will clear the KNX Zone trouble condition
    6. Date to KNX may be wrong
    7. If Slave is installed, Bypass Zone mapping to Group address does not work
    8. When a zone is bypassed on Comfort the Bypass state of the zone is not sent to KNX
    [size=\"3\"]KNX 5.195 (Initial Release 4 August 2009)[/size]

    Known Issues
    1. Mapping of KNX group addresses to Counters > 128 do not work. Please keep to counter numbers < 128
    2. Arm Ready 1 bit group address does not work
    3. Date to KNX may be wrong
    4. If Slave is installed, Bypass Zone mapping to Group address does not work
    ]]>