<![CDATA[Comfort Automation/ Security System Forums - UCM/Zwave Firmware]]> https://www.comfortforums.com/ Fri, 11 Sep 2026 11:35:09 +0000 MyBB <![CDATA[Zwave 7.102]]> https://www.comfortforums.com/thread-4672.html Tue, 04 Apr 2017 12:06:11 -0400 ]]> https://www.comfortforums.com/thread-4672.html
When a Counter is mapped to a Zwave Node, any change in the Zwave node obtained by polling by the UCM/Zwave of the node will trigger  the Counter Response based on its value

This makes it consistent with Sensor mapped to Zwave node - any change in the zwave node triggers the Sensor Response based on the value

Note that the polling time varies from a few seconds to 20 seconds maximum so the update and response may not be immediate

This new feature allows Zwave nodes to trigger Responses in Comfort without needing to Associate the Zwave node to a Virtuak Node


]]>
When a Counter is mapped to a Zwave Node, any change in the Zwave node obtained by polling by the UCM/Zwave of the node will trigger  the Counter Response based on its value

This makes it consistent with Sensor mapped to Zwave node - any change in the zwave node triggers the Sensor Response based on the value

Note that the polling time varies from a few seconds to 20 seconds maximum so the update and response may not be immediate

This new feature allows Zwave nodes to trigger Responses in Comfort without needing to Associate the Zwave node to a Virtuak Node


]]> <![CDATA[Problem programming a response to access a second UCM/Z-Wave]]> https://www.comfortforums.com/thread-4635.html Wed, 15 Feb 2017 14:57:21 -0500 ]]> https://www.comfortforums.com/thread-4635.html
UCM02 is part of a Vera Edge network and UCM03 is part of a Fibaro network. Both UCMs have learnt the devices in their respective networks and those devices correctly appear in the Z-Wave mapping screens in Comfigurator Modules.

When I try to write a response to perform a basic get or set command for a Z-Wave device, if the UCM Name is set to UCM02 (default) then the Devices that appear in the Device IDs pop-up are correctly the ones for the UCM02 network. However, if I change the UCM Name to UCM03, then the devices that appear are again the UCM02 network devices, not the UCM03 network devices.

I can work round the problem by adding a command for UCM02 then manually editing the response or the action codes changing the UCM number and the deviceID but clearly it would be nicer if Comfigurator displayed the correct Device IDs.

I am using Comfigurator V3.11.10.0]]>
UCM02 is part of a Vera Edge network and UCM03 is part of a Fibaro network. Both UCMs have learnt the devices in their respective networks and those devices correctly appear in the Z-Wave mapping screens in Comfigurator Modules.

When I try to write a response to perform a basic get or set command for a Z-Wave device, if the UCM Name is set to UCM02 (default) then the Devices that appear in the Device IDs pop-up are correctly the ones for the UCM02 network. However, if I change the UCM Name to UCM03, then the devices that appear are again the UCM02 network devices, not the UCM03 network devices.

I can work round the problem by adding a command for UCM02 then manually editing the response or the action codes changing the UCM number and the deviceID but clearly it would be nicer if Comfigurator displayed the correct Device IDs.

I am using Comfigurator V3.11.10.0]]> <![CDATA[Zwave 7.068 - 7.072 ]]> https://www.comfortforums.com/thread-4166.html Sat, 28 Mar 2015 04:24:49 -0400 ]]> https://www.comfortforums.com/thread-4166.html
If a zwave device is mapped to a counter and causes a change in the counter value, Comfort will broadcast the change in counter value to all UCMs. The Zwave UCM acts on the counter change and sends the change back to the mapped Zwave node. This may cause a racing state in certain situations, eg the Zwave node is a dimmer which is dimming slowly. The reflection of the counter value back to the zwaave node causes the dimmer level to switch back to a previous level

Zwave 7.068 prevents the counter broadcast from being sent back to the Zwave node if the counter change orginated from the same node earllier

This may solve some strange problems which cause some nodes to switch on and off


NOTE Comfort firmware 7.070 is required for this function
]]>
If a zwave device is mapped to a counter and causes a change in the counter value, Comfort will broadcast the change in counter value to all UCMs. The Zwave UCM acts on the counter change and sends the change back to the mapped Zwave node. This may cause a racing state in certain situations, eg the Zwave node is a dimmer which is dimming slowly. The reflection of the counter value back to the zwaave node causes the dimmer level to switch back to a previous level

Zwave 7.068 prevents the counter broadcast from being sent back to the Zwave node if the counter change orginated from the same node earllier

This may solve some strange problems which cause some nodes to switch on and off


NOTE Comfort firmware 7.070 is required for this function
]]> <![CDATA[UCM/Zwave 7.062 Beta]]> https://www.comfortforums.com/thread-4069.html Fri, 05 Dec 2014 05:00:13 -0500 ]]> https://www.comfortforums.com/thread-4069.html
The timeout during the learning process for query of a zwave node has been increased from 8 seconds to 70 seconds. This may help prevent situations where UCM/Zwave is unable to detect a multichannel device which results in it being assigned as a Basic node.

This may happen due to  Zwave network issues

The increased time-out does not mean that it will  take longer to learn a zwave network from the primary. It means that if there are nodes which do not respond at all, the learning may take longer. Nodes which take longer than 8 seconds to reply will be learned correctly
]]>
The timeout during the learning process for query of a zwave node has been increased from 8 seconds to 70 seconds. This may help prevent situations where UCM/Zwave is unable to detect a multichannel device which results in it being assigned as a Basic node.

This may happen due to  Zwave network issues

The increased time-out does not mean that it will  take longer to learn a zwave network from the primary. It means that if there are nodes which do not respond at all, the learning may take longer. Nodes which take longer than 8 seconds to reply will be learned correctly
]]> <![CDATA[UCM/Zwave 7.061]]> https://www.comfortforums.com/thread-4027.html Tue, 28 Oct 2014 11:31:02 -0400 ]]> https://www.comfortforums.com/thread-4027.html Please download from https://www.cytech.biz/ucmzwave_firmware.html

  1. Flags can be used for mapping for Zwave nodes are 2 state ie either On or Off
  2. Fixed a bug with Manufacturer query not supported


If the same flag is mapped to other devices eg Cbus, then it allows this mechanism to be used for sending commands from one system to another

Changing the state of the flag also changes the state of the mapped Zwave node, ie it is a 2 way control

Cmfigurator 3.9.5 (Beta) is required to support the new feature
]]> Please download from https://www.cytech.biz/ucmzwave_firmware.html

  1. Flags can be used for mapping for Zwave nodes are 2 state ie either On or Off
  2. Fixed a bug with Manufacturer query not supported


If the same flag is mapped to other devices eg Cbus, then it allows this mechanism to be used for sending commands from one system to another

Changing the state of the flag also changes the state of the mapped Zwave node, ie it is a 2 way control

Cmfigurator 3.9.5 (Beta) is required to support the new feature
]]> <![CDATA[Z-Wave 7.043]]> https://www.comfortforums.com/thread-3771.html Fri, 18 Apr 2014 02:08:13 -0400 ]]> https://www.comfortforums.com/thread-3771.html
This has a minor change to improve the processing of the send command to Zwave via Action 197 (Response Wizard) to filter out illegal commands in action 197


]]>
This has a minor change to improve the processing of the send command to Zwave via Action 197 (Response Wizard) to filter out illegal commands in action 197


]]> <![CDATA[UCM/Zwave 7.031]]> https://www.comfortforums.com/thread-3571.html Sun, 20 Oct 2013 00:07:50 -0400 ]]> https://www.comfortforums.com/thread-3571.html
  1. Implemented \"smart\" auto polling of Z-Wave nodes where  the nodes are polled when required by Comfort, ie when needed by the control menu or in the Comfort apps.  \"Poll Time\" must be set to 0. Poll time = 255 means no polling at all.
  2. Changing counter values affect Z nodes that are mapped to the counters. The Zwave nodes can be turned on, off or dimmed according to the counter values eg 255 = On, 0 = On, 1 to 99 = Dim Level
  3. Improved Comfigurator status reporting with additional messages
  4.  Better performance overall to address Z-Wave network issues
The UCM/Zwave  manual can be downloaded from https://www.cytech.biz/ucmzwave_manual.h...ory_id=107


]]>
  1. Implemented \"smart\" auto polling of Z-Wave nodes where  the nodes are polled when required by Comfort, ie when needed by the control menu or in the Comfort apps.  \"Poll Time\" must be set to 0. Poll time = 255 means no polling at all.
  2. Changing counter values affect Z nodes that are mapped to the counters. The Zwave nodes can be turned on, off or dimmed according to the counter values eg 255 = On, 0 = On, 1 to 99 = Dim Level
  3. Improved Comfigurator status reporting with additional messages
  4.  Better performance overall to address Z-Wave network issues
The UCM/Zwave  manual can be downloaded from https://www.cytech.biz/ucmzwave_manual.h...ory_id=107


]]> <![CDATA[UCM/Zwave 7.016]]> https://www.comfortforums.com/thread-3461.html Wed, 24 Jul 2013 04:28:06 -0400 ]]> https://www.comfortforums.com/thread-3461.html http://www.comfortforums.com/forum25/3424.html

This firmware can be upgraded by Comfigurator according to instructions in http://www.comfortforums.com/forum92/3400.html

The changes from Zwave 6.024 are

  • Virtual node counter update triggers Comfort Response, even if the value is unchanged so Scene commands can work.
  • Improved EEPROM write cycle during Learn mode.  Previously, it did not respond to Poll command during write.
  • Backup Z-Wave data block in case of learn failure[size=, ][/size]which causes it to reset and all virtual nodes lost. This workaround is recommended by Z-Wave.  In event of failure, data block is restored to same network ID and node ID. If the controller is not in network before learn, the backup will not be initiated.
  • EEPROM is updated automatically, after virtual node is added or removed.  Hence, no need to \"learn\" from Primary Controller again.
  • UCM/Zwave Learn mode time-out increased to 60 secs.  This caters for cases where learn error happened, but user is unaware and keeps waiting for completion.
  • Automatic \"factory default reset\" when controller is excluded from network. Added new auto report status when UCM source 1D is available.
  • Cater for Multilevel switch command class. Status report value cannot be 100(Ox64) to 254(OxFE). If value falls in this forbidden range, will report as 255(OxFF) instead.
  • During learn, controllers are polled for supported command classes as well.
  • Patched Multilevel Switch Report Command.  Previously, registers are not updated correctly[size=.][/size]
  • Inhibit Z-Wave commands to send to non-existing nodes or channels in nodes. Also inhibit Z- Wave commands sending to non-supported nodes.
  • Inhibit Z-Wave GET commands for multichannel bit address (ie. requiring reply from destination).
  •  Add new status to indicate when response commands are inhibited.

]]> http://www.comfortforums.com/forum25/3424.html

This firmware can be upgraded by Comfigurator according to instructions in http://www.comfortforums.com/forum92/3400.html

The changes from Zwave 6.024 are

  • Virtual node counter update triggers Comfort Response, even if the value is unchanged so Scene commands can work.
  • Improved EEPROM write cycle during Learn mode.  Previously, it did not respond to Poll command during write.
  • Backup Z-Wave data block in case of learn failure[size=, ][/size]which causes it to reset and all virtual nodes lost. This workaround is recommended by Z-Wave.  In event of failure, data block is restored to same network ID and node ID. If the controller is not in network before learn, the backup will not be initiated.
  • EEPROM is updated automatically, after virtual node is added or removed.  Hence, no need to \"learn\" from Primary Controller again.
  • UCM/Zwave Learn mode time-out increased to 60 secs.  This caters for cases where learn error happened, but user is unaware and keeps waiting for completion.
  • Automatic \"factory default reset\" when controller is excluded from network. Added new auto report status when UCM source 1D is available.
  • Cater for Multilevel switch command class. Status report value cannot be 100(Ox64) to 254(OxFE). If value falls in this forbidden range, will report as 255(OxFF) instead.
  • During learn, controllers are polled for supported command classes as well.
  • Patched Multilevel Switch Report Command.  Previously, registers are not updated correctly[size=.][/size]
  • Inhibit Z-Wave commands to send to non-existing nodes or channels in nodes. Also inhibit Z- Wave commands sending to non-supported nodes.
  • Inhibit Z-Wave GET commands for multichannel bit address (ie. requiring reply from destination).
  •  Add new status to indicate when response commands are inhibited.

]]> <![CDATA[UCM/Zwave Firmware 7.010 (Beta)]]> https://www.comfortforums.com/thread-3274.html Fri, 01 Feb 2013 04:20:11 -0500 ]]> https://www.comfortforums.com/thread-3274.html https://www.cytech.biz/product_details.php?item_id=288 for testing purposes

This firmware has new features which requires Comfigurator 3.6.4 or above which is described in http://www.comfortforums.com/view_topic.php?id=3261&forum_id=20

The new UCM/Zwave Manual version 3 can be downloaded from https://www.cytech.biz/product_details.php?item_id=230


New Features


  1. UCM/Zwave will update status bar on Comfigurator Zwave screen .
  2. After Virtual Node operations UCM/Zwave  will automaticallly read EEPROM when required and send to Comfigurator without having to Learn the network again from the primary controller
  3. Zwave Action has a new Multilevel Dimming function
  4. UCM/Zwave will update Comfort counters and sensors from Zwave commands even when the counter value has not changed. This allows status of Zwave devices controlled by Comfort and other Zwave nodes to be synchronised
The status messages show the status of the UCMs which were formerly available only by seeing the state of the LEds BUSY1, BUSY2, ERROR eg for Zwave
  • Normal/No error
  • EEPROM missing/faulty
  • EEPROM insufficent capacity
  • EEPROM data invalid
  • Communication error between UCM baseboard and Z-wave sub-module
  • UCM/Z-Wave not in any network
  • Waiting to receive network data. (Learn process)
  • Receiving network data. (Learn process)
  • Writing EEPROM. (Learn process)
  • Learn process success
  • Learn process completed with errors
  • Command transmitted.  Waiting for ACK
  • Z-Wave network busy/jammed (RF transmit error)
  • Unknown transmit error

]]> https://www.cytech.biz/product_details.php?item_id=288 for testing purposes

This firmware has new features which requires Comfigurator 3.6.4 or above which is described in http://www.comfortforums.com/view_topic.php?id=3261&forum_id=20

The new UCM/Zwave Manual version 3 can be downloaded from https://www.cytech.biz/product_details.php?item_id=230


New Features


  1. UCM/Zwave will update status bar on Comfigurator Zwave screen .
  2. After Virtual Node operations UCM/Zwave  will automaticallly read EEPROM when required and send to Comfigurator without having to Learn the network again from the primary controller
  3. Zwave Action has a new Multilevel Dimming function
  4. UCM/Zwave will update Comfort counters and sensors from Zwave commands even when the counter value has not changed. This allows status of Zwave devices controlled by Comfort and other Zwave nodes to be synchronised
The status messages show the status of the UCMs which were formerly available only by seeing the state of the LEds BUSY1, BUSY2, ERROR eg for Zwave
  • Normal/No error
  • EEPROM missing/faulty
  • EEPROM insufficent capacity
  • EEPROM data invalid
  • Communication error between UCM baseboard and Z-wave sub-module
  • UCM/Z-Wave not in any network
  • Waiting to receive network data. (Learn process)
  • Receiving network data. (Learn process)
  • Writing EEPROM. (Learn process)
  • Learn process success
  • Learn process completed with errors
  • Command transmitted.  Waiting for ACK
  • Z-Wave network busy/jammed (RF transmit error)
  • Unknown transmit error

]]> <![CDATA[New Features in UCM/Zwave3]]> https://www.comfortforums.com/thread-2897.html Wed, 06 Jun 2012 05:33:48 -0400 ]]> https://www.comfortforums.com/thread-2897.html

The new features will be[size=\"3\"][font=\"Verdana\"][size=\"3\"][font=\"Verdana\"]:[/font][/size][/font][/size][size=\"2\"][size=\"3\"][font=\"Verdana\"]

[/font][/size][/size]
  1. [size=\"2\"]Add \"Get Status\" Button to show Zwave Module status in status Bar[/size]
  2. [size=\"2\"][font=\"Verdana\"][/font]Automatically display Zwave status on status bar during Learn Mod[/size]
  3. [size=\"2\"]Add Comment Field for each Device in Zwave Mapping Table to identify the node, which is saved in EEPROM[/size]
  4. [size=\"2\"][font=\"Verdana\"][/font]Reduce Read and Write to EEPROM Time by implementing maximum node number to read/write. After upgrading firmware, Learn again to get the benefit of the new feature[/size]
  5. [size=\"2\"]Warning when RESET to Default Button is pressed to prevent creating additional non-existent nodes in the Z-Wave Network[/size].
[size=\"3\"][font=\"Verdana\"][size=\"3\"][font=\"Verdana\"]
[size=\"2\"]Comfigurator 3.5.0 (currently in beta) is needed to take advantage of the new featurers. If an older Comfigurator version is used with the new firmware, it will still work but without the new features[/size]
[size=\"2\"]The possible status values in the status bar are;
[/size]
[/font][/size][/font][/size]
  • [size=\"3\"][font=\"Verdana\"][size=\"3\"][font=\"Verdana\"][size=\"2\"]“Normal/No Error” - UCM/Zwave is in a Zwave Network and working[/size][/font][/size][/font][/size][size=\"2\"][font=\"Verdana\"] [/font]correctly[/size]
  • [size=\"2\"]“EEPROM Missing/Faulty” - U2 EEPROM problem[/size]
  • “Communication Error between UCM baseboard and Zwave Submodule” -[size=\"2\"] Problem with Zwave submodule or connection to baseboard[/size]
  • [size=\"2\"]“UCM/Zwave not in any Network” - UCM/Zwave has not gone through Learn process[/size]
  • “Waiting to Receive Network Data”. This status is seen during the Learn[size=\"2\"] Process.[/size]
  • [size=\"2\"]“Receiving Network Data”. This status is seen during the Learn Process.[/size]
  • [size=\"2\"]“Writing EEPROM”. This status is seen during the Learn Process.[/size]
  • [size=\"2\"]“Learn Process Success”. This status is seen when Learn is completed.[/size]
  • “Learn Process Completed with Errors” This status is seen when Learn is[size=\"2\"] completed.[/size]
  • “Command Transmitted - waiting for ACK” This is seen when a Z-Wave command has transmitted and is waiting for a response from Z-Wave[size=\"2\"] network.[/size]
  • Z-Wave Network Busy/Jammed (RF Error”). This is seen when there is a[size=\"2\"] Z-Wave network problem.[/size]
  • [size=\"2\"]“Unknown Transmit Error” -  undefined error during transmission to Z-Wave[/size]
[size=\"3\"][font=\"Verdana\"][size=\"3\"][font=\"Verdana\"]
[size=\"2\"]The \"Get Status\" Button will cause the current Z-Wave status to appear on the status bar. However during the Learn Process, the Z-Wave status automatically appears on the status bar[/size]
[size=\"2\"]The new Comments field for every Z-Wave node seen in the Zwave Mapping table allows each node to be identified with text, eg \"Living Room Light\". This is saved in the UCM/Zwave EEPROM by a Write to EEPROM and thus can be read back. In previous firmware, the Zwave Nodes have no text identification so it may be difficult to know what the nodes are especially in a large network.[/size]

[size=\"2\"]The Read from EEPROM and Wriite to EEPROM process has been considerably speeded up when the number of Z-Wave nodes are small. After upgrading the firmware to Zwave 6.023, you must repeat the Learn process with the promiiary controller to updare the Z-Wave network to the UCM/Zwave in order too take advantage of the feature[/size]

[size=\"2\"]Lastly the RESET button when pressed will pop up a warning message. RESET does not reset the UCM/Zwave like the physical reset button on the UCM, it clears the EEPROM in UCM/Zwave so all the Z-Wave Network information is lost. This should NOT be done without leaving the existing Z-Wave network otherwise the UCM/Zwave remains part of the network. If the RESET to default button is pressed and the UCM/Zwave is learned again, The UCM/Zwave is added aagain to the Zwave network and another \"Static Controller\"  will be seen in the list of Zwave nodes.[/size]

[size=\"2\"]The RESET to default button should only be used as a last resort when the UCM/Zwave has been physically removed from the site.[/size]
[/font][/size][/font][/size]]]>

The new features will be[size=\"3\"][font=\"Verdana\"][size=\"3\"][font=\"Verdana\"]:[/font][/size][/font][/size][size=\"2\"][size=\"3\"][font=\"Verdana\"]

[/font][/size][/size]
  1. [size=\"2\"]Add \"Get Status\" Button to show Zwave Module status in status Bar[/size]
  2. [size=\"2\"][font=\"Verdana\"][/font]Automatically display Zwave status on status bar during Learn Mod[/size]
  3. [size=\"2\"]Add Comment Field for each Device in Zwave Mapping Table to identify the node, which is saved in EEPROM[/size]
  4. [size=\"2\"][font=\"Verdana\"][/font]Reduce Read and Write to EEPROM Time by implementing maximum node number to read/write. After upgrading firmware, Learn again to get the benefit of the new feature[/size]
  5. [size=\"2\"]Warning when RESET to Default Button is pressed to prevent creating additional non-existent nodes in the Z-Wave Network[/size].
[size=\"3\"][font=\"Verdana\"][size=\"3\"][font=\"Verdana\"]
[size=\"2\"]Comfigurator 3.5.0 (currently in beta) is needed to take advantage of the new featurers. If an older Comfigurator version is used with the new firmware, it will still work but without the new features[/size]
[size=\"2\"]The possible status values in the status bar are;
[/size]
[/font][/size][/font][/size]
  • [size=\"3\"][font=\"Verdana\"][size=\"3\"][font=\"Verdana\"][size=\"2\"]“Normal/No Error” - UCM/Zwave is in a Zwave Network and working[/size][/font][/size][/font][/size][size=\"2\"][font=\"Verdana\"] [/font]correctly[/size]
  • [size=\"2\"]“EEPROM Missing/Faulty” - U2 EEPROM problem[/size]
  • “Communication Error between UCM baseboard and Zwave Submodule” -[size=\"2\"] Problem with Zwave submodule or connection to baseboard[/size]
  • [size=\"2\"]“UCM/Zwave not in any Network” - UCM/Zwave has not gone through Learn process[/size]
  • “Waiting to Receive Network Data”. This status is seen during the Learn[size=\"2\"] Process.[/size]
  • [size=\"2\"]“Receiving Network Data”. This status is seen during the Learn Process.[/size]
  • [size=\"2\"]“Writing EEPROM”. This status is seen during the Learn Process.[/size]
  • [size=\"2\"]“Learn Process Success”. This status is seen when Learn is completed.[/size]
  • “Learn Process Completed with Errors” This status is seen when Learn is[size=\"2\"] completed.[/size]
  • “Command Transmitted - waiting for ACK” This is seen when a Z-Wave command has transmitted and is waiting for a response from Z-Wave[size=\"2\"] network.[/size]
  • Z-Wave Network Busy/Jammed (RF Error”). This is seen when there is a[size=\"2\"] Z-Wave network problem.[/size]
  • [size=\"2\"]“Unknown Transmit Error” -  undefined error during transmission to Z-Wave[/size]
[size=\"3\"][font=\"Verdana\"][size=\"3\"][font=\"Verdana\"]
[size=\"2\"]The \"Get Status\" Button will cause the current Z-Wave status to appear on the status bar. However during the Learn Process, the Z-Wave status automatically appears on the status bar[/size]
[size=\"2\"]The new Comments field for every Z-Wave node seen in the Zwave Mapping table allows each node to be identified with text, eg \"Living Room Light\". This is saved in the UCM/Zwave EEPROM by a Write to EEPROM and thus can be read back. In previous firmware, the Zwave Nodes have no text identification so it may be difficult to know what the nodes are especially in a large network.[/size]

[size=\"2\"]The Read from EEPROM and Wriite to EEPROM process has been considerably speeded up when the number of Z-Wave nodes are small. After upgrading the firmware to Zwave 6.023, you must repeat the Learn process with the promiiary controller to updare the Z-Wave network to the UCM/Zwave in order too take advantage of the feature[/size]

[size=\"2\"]Lastly the RESET button when pressed will pop up a warning message. RESET does not reset the UCM/Zwave like the physical reset button on the UCM, it clears the EEPROM in UCM/Zwave so all the Z-Wave Network information is lost. This should NOT be done without leaving the existing Z-Wave network otherwise the UCM/Zwave remains part of the network. If the RESET to default button is pressed and the UCM/Zwave is learned again, The UCM/Zwave is added aagain to the Zwave network and another \"Static Controller\"  will be seen in the list of Zwave nodes.[/size]

[size=\"2\"]The RESET to default button should only be used as a last resort when the UCM/Zwave has been physically removed from the site.[/size]
[/font][/size][/font][/size]]]> <![CDATA[UCM/Zwave 6.011]]> https://www.comfortforums.com/thread-2568.html Sun, 06 Nov 2011 01:16:33 -0400 ]]> https://www.comfortforums.com/thread-2568.html Please download firmware .cbf file from https://www.cytech.biz/product_details.php?item_id=288
]]> Please download firmware .cbf file from https://www.cytech.biz/product_details.php?item_id=288
]]> <![CDATA[Zwave 5.180 and 5.184]]> https://www.comfortforums.com/thread-2117.html Fri, 31 Dec 2010 00:31:31 -0500 ]]> https://www.comfortforums.com/thread-2117.html Zwave 5.184 (13 May 2009)
  • [img]file:///C:/DOCUME%7E1/LUYUNG%7E1/LOCALS%7E1/Temp/moz-screenshot-15.png[/img]Fixed problem of  counter update even if value is not changed.
Zwave 5.180 (5 March 2009)
  • Supports Zwave Configurator with EEPROM in UCM/Zwave.  Requires Comfigurator 3.2.3
  • AUX \'H\' shunt no longer needed for copy operation.
  • New commands activated from Zwave Configurator software : Abort, factory default, learn, node info.
  • Fixed wrong LED indication showing receiving information in learn mode when it is not (Only happens for modules which are not learnt previously)
  • Supports Scanning of Modules by Comfigurator
]]> Zwave 5.184 (13 May 2009)
  • [img]file:///C:/DOCUME%7E1/LUYUNG%7E1/LOCALS%7E1/Temp/moz-screenshot-15.png[/img]Fixed problem of  counter update even if value is not changed.
Zwave 5.180 (5 March 2009)
  • Supports Zwave Configurator with EEPROM in UCM/Zwave.  Requires Comfigurator 3.2.3
  • AUX \'H\' shunt no longer needed for copy operation.
  • New commands activated from Zwave Configurator software : Abort, factory default, learn, node info.
  • Fixed wrong LED indication showing receiving information in learn mode when it is not (Only happens for modules which are not learnt previously)
  • Supports Scanning of Modules by Comfigurator
]]> <![CDATA[UCM/Zwave Firmware 5.218]]> https://www.comfortforums.com/thread-2116.html Fri, 31 Dec 2010 00:29:06 -0500 ]]> https://www.comfortforums.com/thread-2116.html Zwave 5.218 (22 July 2010)
  • [img]file:///C:/DOCUME%7E1/LUYUNG%7E1/LOCALS%7E1/Temp/moz-screenshot-14.png[/img]Slow down node polling speed to allow Zwave Modules to cope
  • Sync string ID after timeout, in case of errors. Initialises polling parameters during reset.
  • Skip polling controllers for multi-channel support (unnecessary)
  • Stop polling devices during learn mode so led status is correct.
  • Fixed bug for multichannel polling
  • Supports Zwave Multi-channel Command Class (MK Astral)
The latest firmware can be downloaded from https://www.cytech.biz/ucmzwave_firmware.html

The latest UCM/Zwave Manual can be downloaded from https://www.cytech.biz/ucmzwave_manual.html
]]> Zwave 5.218 (22 July 2010)
  • [img]file:///C:/DOCUME%7E1/LUYUNG%7E1/LOCALS%7E1/Temp/moz-screenshot-14.png[/img]Slow down node polling speed to allow Zwave Modules to cope
  • Sync string ID after timeout, in case of errors. Initialises polling parameters during reset.
  • Skip polling controllers for multi-channel support (unnecessary)
  • Stop polling devices during learn mode so led status is correct.
  • Fixed bug for multichannel polling
  • Supports Zwave Multi-channel Command Class (MK Astral)
The latest firmware can be downloaded from https://www.cytech.biz/ucmzwave_firmware.html

The latest UCM/Zwave Manual can be downloaded from https://www.cytech.biz/ucmzwave_manual.html
]]>