Hi, I had a comfort system installed 6 years ago but not configured (thought I would do it myself, then never found the time!)
Any good local installers (or non-local willing to travel) who would be willing to quote?
Experience with C-Bus integration preferred.
I\'m in the Stratford-upon-Avon area CV37

The new UCM/Modbus  is now available.
See the new UCM/Modbus forum at http://www.comfortforums.com/forum133/4565.html

Cytech\'s new UCM/Modbus allows Modbus devices to be interfaced to Cytech\'s Comfort system. The UCM/Modbus can be programmed as Client/Master or Server/Slave on  Modbus. Master mode is for Comfort to control other Modbus Slave products, and Slave mode is for  other Modbus devices and software to control Comfort. Both modes are capable of 2- way communications, ie Comfort to Modbus and Modbus to Comfort

Modbus over RS485 (Modbus/RTU) and Modbus over IP are possible by plugging in the RS485 or ETH03 Ethernet submodule onto the UCM/Modbus baseboard.
The UCM/Modbus can work with other Comfort modules including Intelligent  Remote Input/Output Modules (IRIO), Temperature Sensor Module (TSM01), Hotel I/O (HIO) as well as 3rd party systems on the Comfort Bus including C-Bus, KNX etcPlease visit the UCM/Modbus website at https://www.cytech.biz/brochure/ucm-modbus.html

Specifications

• Configurable as Master or Slave  on Modbus
• Implements Modbus/RTU by RS485  and Modbus/TCP using plug in sub-modules RS485 or ETH03 respectively. RS232 is also possible for Modbus RTU
  
• Comfort (CM9000), UCM/Logic, LGX01 Logic Engine can act as the central controller for UCM/Modbus
• In /Master Mode: 256 Modbus addresses in Modbus to Comfort
• For Modbus/RTU, baud rate selectable from 1200, 2400, 4800, 9600, 19200, 38400, 76800 bps. Parity None, Even or Odd
• As  Modbus Master, Comfort Counters, Flags, Sensors, Inputs, Outputs, security commands and alarm conditions can be accessed (read/write) by a Modbus Master
• As Modbus Slave, Comfort Counters, Flags, Sensors, Inputs, Outputs, Alarm conditions can be accessed via Modbus Registers
• Modbus Monitor mode shows the receive abd transmit communications between UCM/Modbus and Modbus. It works for RTU and TCP interfaces, as well as Master and Slave
  

• Comfort Ultra/OPT or UCM/Logic or LGX01 Firmware 7.116 or above can act as controllers.
  
• UCM/Modbus firmware 7.103 or above
• Comfigurator 3.11.12 or above

• UCM/Modbus-485 with Rs485 Interface
• UCM/Modbus-ETH with Ethernet Interface

 Slychiu, may I ask to you consider as matter of urgency to make changes (which as a Software Engineer I think are low risk and on the small side but yield more than the simpleness of the change itself - so from the users point of view makes life easier and better. When I consider other Zwave Primary controllers that must have a complex web front end to represent the device to do stuff, your implementation can stand ahead the competition in terms of reliability and speed. It does what it says without hassle. Hardware ZWave devices  work and conform to the Zwave standard, and as Comfort sticks to core Zwave Messages rather than complex Web device representation it is not tangled up to the point device is not fully working as happens so frequently in primary controllers.

May I ask others who read this to lend their support if necessary to make changes described below.

Just a recap for others users benefit and has important information if not familiar

Step 1 add the ZWave device to the primary controller.
See topic  ZWave Hints and Tips Installation, Commissioning

Step 2 - ZWAve Tips - Install and Management - ZWave Sensors 
Note that just because the sensor reading is not displayed or works correctly in the Primary Controller, it does not mean it can not be used by Comfort to get the sensor reading. In other words Comfort can still use the device and sensor readings like temperature. The issue is that the device works but Vera or other primary controller does not fully support it yet properly. Because the device is fully functional and fulfill the ZWave standard, Comfort only needs the device registered in the Primary Controller.

Now to the point -  - the node type must change from Basic to Multilevel Sensor.
In Comfort the node type changes during the Learn phase. However this is a two step process.

Learn step 1 get ID of the device from Primary Controller (actually the Alt ID) that Primary Controller only can create.

Learn Step 2 after all the devices are found and with their IDs Comfort goes into a second loop and speaks to the device directly (not via the primary controller) to get its device type so that the node can change to Mutlilevel Sensor.

ProblemIf you have many devices loaded and identified as Multilevel Sensor - and you want to add a new device, a new Learn process will reset the device as Basic. You can loose all the nodes that are Multilevel Senor and are set back to Basic. If you have many as I have, I have  spend days and weeks, months on different Learns to get the node back to Multilevel Sensor. 

Due to uncertainties in when and how the device respond with the device type, Comfort may not be able get the right information from the device on any and every Learn.
This means the Learn is a Hit and Miss affair for setting the node type. As Vera only gives a  1  minutes  - there are also timing issues. You can do a Comfort Learn without putting the Primary Controller in Learn Mode when Comfort in Vera has already been Learned and this can make it easier but because Comfort resets the node type back to Basic if the device does does not give the right information - this can happen for various reasons  - then you can still loose all your existing Multivlevel Senors being reset to Basic.
I have still got devices loaded as Multilevel Sensor, but I can not go further the more loaded - the more difficult it is. I plead with you to change this.

What is needed - change request - for Comfort Learn
Option 1
Split out from Learn  - getting and Setting Device type  and add a new button for this to Just make sure the device is NOT reset to Basic on subsequent requests.  Only go out to devices that are Basic node and not Node  like Multilevel Senors or the Other Types. Once set this way do not change it. Only allow the user to change back to Basic. 
When second/new button is pressed, then for  each Basic node found in Comfort only and not  Multilevel Senors or the Other Types go to the node to query the device to set the node type.
This will make Learniong from the primrary controller quicker and more robust. The Second Learn to Set the node type will be easier to manage.

Option 2
Split out from Learn  - getting and Setting Device type. 
Make the node type a drop down box. 
Allow the user to set the Node Type to Multilevel Sensor or the other Node Types. If necessary only - Comfort goes to Node to confirm the Node type but because there issues beyond Comfort control - this may or should be avoided perhaps, but if there are details the device responds with that is needed by Comfort to make things work - then you may have no choice - but if you do not need it to make it work - why bother just let the user set the Node type via Drop down.

Please may I ask you to make this change

Comfort supports the following sensor message types.

• Sensor Multilevel V4,  Multilevel Sensor

1. Fibaro Smoke Sensor  - wired
2. Fibaro Motion Sensor
3. All Qubino ZWave modules (dimmers, on/off, thermostats, pilot wire controllers) –have temperature senor information - just connect Qubino Temperature Sensor  and you will have temperature. I have 14 Qubino  devices – 8 Pilot wire, 2 thermostats(Flush Module Plus), 4 dimmers and all can be used to get temperature into Comfort. 
4. Horstman/Secure SIR 321 immersion heater controller support – this is a really good device – just add temperature sensor and is very reliable. This is a really straight forward device. It has a countdown timer - so the device can be switched on for half an hour, or 2 hours for example. It is great for immersion heaters but also lights or anything else that should be switched on for a certain amount of time. The sensor information is fast and very reliable. It should be on your list of devices to get.

Known Bugs

1. Strobe does not work on Slave. This is not a new issue
   

1. Fixed bug SEM sent ack 4DH to Comfort which is  only used by KP LCD and caused problems

1. [color=\"#ff0000\"]Auto Detect LEM03 on SEM. LEM03 can be connected to the last SEM in the system[/color]
   
2. Suppprt EL EOL query command. Supports software  eol feature for setting of No EOL or Double EOL without use of Shunts (requires new Hardware)
   
3. Accept single message from Comfort with 31 zone types at reset
   
4. Support ID Button to set SEM ID (if button is present). Requires new hardware
   
5. Handle rs485 comms status 92H message
   

Bugs Fixes

1. Fixed bug UCM/ETH03 upgrade by cable fails 1st time Allow LT to be received without login so UCM can reply OK, not NA.
2. Fixed BUG from UCM 7.075. for Sensor commands  s!NNVVVV if repeated same value ucm replies NA. s? gave wrong reply
3. Fixed bug F!nn03 toggle reply FL was wrong. Bug From UCM 7.060

1. Increased message size of rs485 messages to 140 bytes
2. Speed up erasing of EEPROM for Write to UCM/EEPROM by erasing in blocks
3. When UCM reports a sensor value, and Comfort broadcasts the new sensor value, the original reporting UCM ignores the sensor value in order to prevent multiple racing commands
   
4. UCM sends output command to Comfort only if output changed
5. Messages S? BP, DI, EV, O? A? I? a? DT, FL  will not be sent to PC unless logged in
6. Support H! and H? Commands for HIO
7. Support EL command
8. Login add partition  (0-3 or FF),
   

Hello,
I have a CM9000-ULT. In software Configurator, the Confort Version is 7.116 and UCM01 is 5.192. When I try update UCM01 firmware to 7.026 I have the next error attached.
How I can update my UCM01?

Thanks.

Attached Files

Thumbnail(s)
   

Known Issues

1. Engineer Menu 4,5 Keypad Area (Anouncement) is wrong.
   
2. Execute Response in Comfigurator (DA) with multiple actions - security alarm actions eg bypass, Do Alarm cause subsequent actions do not work. eg Bypass zone 1, bypass zone 2, output 1 on Only Bypass zone 1 will work. However the Response executed by Comfort events will work
3. Bypass action has other problem of clearing a memory bit
4. Partition keypad disarm does not off siren when disarm partition if there is a trouble alarm, until the code is entered 2 times
5. CM9000- OPT firmware bug Clear all outputs action 8 does not work
6. Do Action 190 serial command DABE does not do the actions following action 190 correctly. The 1st action is continually repeated
7. Action 73, 16 Get  keypadId/ If Keypad ID does not work

1. Fixed BUG add counter and add sensor actions did not work
2. Fixed BUG from 7.112  For partitions if last zone has no zone type but has a nonzero partition (due to eeprom) after upgrade, the arming to night mode causes keypad to give strange sound and system cannot be armed.

1. Sensor registers enabled for OPTIMUM
   
2. Comfort automatically detects of LEM03 at reset
   

Known Issues

1. In Flags screen, if Check Status box is checked for a flag, the status is updated, but if the flag changes subsequently, the flag status in the centre pane is not updated until you go to another page and back, or uncheck and check the box (old bug)
2. In Modbus configurator, Sensors cannot be mapped to Modbus
3. for TSM, if older firmware eg TSM 7.001 has read from EEPROM, this may cause  an exception. Workaround is to upgrade TSM to  the latest (7.003) firmware first
   

1. \"If Input\" comparison action did not work for Input > 64 to 96. This also applies for older versions
   
2. Deg C /deg F in Comfiguration flags is incorrect
   
3. Comfort Optimum when adding  UCM/KNX2 caused exception
4. Read from KP06A or KP04A does not change the KP06A/KP04A settings  in Comfigurator
5. IRIO IR codes do not refresh when new IR codes are learned. Refresh button is needed
   
6. Default template def40.cctx for UCM/Logic is missing from the installation.
   
7. Export Scenario dis not work. Selecting any items will cause an exception

1. Added parameters; Heating / Cooling Mode, Virtual Input, Heating/Cooling Output, Virtual Alarm Offset, Calibration Offset. This implements the Temperature Alarm Monitoring feature which maps to Virtual Input to trigget the Temperature Alarm. New Temperature Alarm Type, TempNO Zone Type added to defaults.

1. Added Lighting Sequence Timer Parameter for delay between each light turning off in Occupancy Detection Mode

1. Added Resistive Sensor Input Functions