Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums

(Advanced Search)

Latest Threads
HELP ! CBUS/KNX translato...
Last Post: slychiu
2 hours ago
UCMA/Pi for Home Assistan...
Last Post: slychiu
3 hours ago
CBUS to KNX translator - ...
Last Post: Home
6 hours ago
Cbus to KNX translator - ...
Last Post: slychiu
Today, 01:58 AM
System not announcing are...
Last Post: slychiu
Today, 01:43 AM
Trouble connecting
Last Post: Home
09-21-2026, 03:42 PM
Comfort Analog Input Grap...
Last Post: slychiu
09-12-2026, 08:31 AM
Comfort Server Manager 2
Last Post: slychiu
09-08-2026, 04:48 AM
Comfort App Converter Dow...
Last Post: slychiu
09-08-2026, 02:00 AM
Comfort Android App 2.1 t...
Last Post: slychiu
09-08-2026, 01:56 AM

Forum Statistics
» Members: 53,661,   » Latest member: PaulGordon,   » Forum threads: 5,216,   » Forum posts: 28,681,  
Full Statistics

  Risco Nova 6 Siren/bellbox connection to SEM
Posted by: The Old Scholar - 08-13-2016, 09:15 PM - Forum: Questions on Installation and Connection - Replies (2)

I have added a second bell box (Risco Nova 6) to my Comfort system via an existing SEM, but can\'t get it to work. I have made connections below and it is completely dead so I\'m presuming I\'ve done something stupid, but I can\'t see what.


Nova 6 > Comfort
___________________
STR- > STR-
S- > SRN-
12V > SRN+
0V > COM (also link made in bell box from 0V to TMPF)
TMPR > TAMP


I thought that perhaps 12V should link to 12VF on Comfort instead of SRN+, but that doesn\'t seem to work either.

What am I doing wrong? Any help would be appreciated.

Print this item

  Problems upgrading Vocab in Firmware 7.112
Posted by: cc_uk - 08-13-2016, 04:28 PM - Forum: Vocabulary Issues - Replies (15)

I am trying to update my Comfort II system with the kate39.bin Vocab file following upgrade to the 7.112 beta firmware to support partitions.

The Firmware upgrade to 7.112 went well.     My ETh03 & UCM are already ont he latest firmware, and I am using Comfigurator 3.11.6.0

When I try to upload the Kate39.bin file I get The upgrading Vocabulary dialogue box appear but it never progresses.  The KP04A keypad displays Keypad not polled for a while, and eventually I get Vocabulary upgrade incomplete, Please try Vocabulary Upgrade again. 

After that Comfort resets and I get WRONG TEXT PUSH *1 together on the keypad.

Comfigurator then reports the vocabulary version as 255

Any help appreciated.

Print this item

  Comfort Firmware 7.112 - 7.113
Posted by: slychiu - 08-13-2016, 12:17 PM - Forum: Comfort Firmware - Replies (4)

Changes for Firmware 7.112

Known Issues

  1. 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
  2. Bypass action has other problem of clearing a memory bit
  3. After Upgrading firmware to 7.113, some unused zones (Null zone  Type)  may have Partition 3 setting, and this causes the system to be unable to arm, and causes the keypads to give a strange beeping sound. UCM and Keypad is unable to log in until the arming aborts after 5 minutes.
  4. Actions Add counter, Add counter give wrong answer from 7.039
  5. Vocabulary Upgrade does not work, causes vocabulary to be erased. This has been fixed in version 7.113
  6. CM9000- OPT firmware bug Clear all outputs action 8 does not work
  7. Do Action 190 serial command DABE does not do the actions following action 190 correctly. The 1st action is continually repeated
  8. Action 73, 16 Get  keypadId/ If Keypad ID does not work

Bugs Fixed
  • Fixed bug if incoming time message has no seconds, the minutes change is not updated.
  • Fixed occasional problem where KP04 \"wrong text press *1\" cannot work, still get wrong text press *1\"  but after comfort reset this does not happen. Fixed the problem no more wrong text press *1.  LCD text is actually good but wrong status shown in Keypad
  • Fixed Bug for sentence table upgrade failure
  • Fixed BUG when entry door causes intruder alarm due to no sign in, the Entry zone restore message is not sent to SMS or CMS if the zone response or Alarm response  loads zones and if any other zones are triggered between the entry door open and the intruder alarm.
  • Fixed bug from 7.099 - KNX and CBUS mapped to Comfort time could not change time in Comfort.
  • Fixed BUG from 7.077  when controlling zwave from the control menu, smart polling did not work correctly. This has no effect on zwave control
  • Program entry warning time actually programmed entry time BUG from 7.077
Partitions KNX/CBUS/UCM
  • Set maximum zone nased on last programmed nonzero Zone Type for Z?, KNX and C-Bus to report zones at reset, instead of all 96 zones or according to no of slaves. This takes care of virtual zones which exist outside installed slaves.
Control Menu
  • If Feedback Type = counter, flag or output, and if action key 0 and 1 have No words, then action key 0 and 1 automatically control the counter, flag or output, eg Flag and output off/on, counter = 00 or FF
LEM03
  • Automatically detect LEM03 and write to EEPROM LEM03 checkbox location
Actions
  • Added action 158:  158, counter number,  0 = clear, 1 = set, 2 = toggle
  • Added  Action 73 param 28 = partition for armed/ disarmed
  • Added Action 80 set partition for arming/disarming
Miscellaneous
  • No of Non-detector Alarms increased from 28 to 31 for future use by Comfort
  • If arm to same mode, reply with security mode instead of no reply MDss
  • Support control messages to HIO
  • Support EL command for EOL shunts settings for Comfort and SEM v7.100 +

Print this item

  TSM01 Temperature Sensor Module
Posted by: slychiu - 08-09-2016, 03:07 PM - Forum: NEWS & Announcements - No Replies

Cytech\'s new Temperature Sensor Module is now available



See http://www.comfortforums.com/forum131/4492.html

An external temperature sensor provides temperature readings to Comfort and can act as a thermostat with other Cytech modules like IRIO

Print this item

  TSM01 Temperature Sensor Module
Posted by: slychiu - 08-09-2016, 12:54 PM - Forum: Temperature Sensor - Replies (3)

The TSM01 Temperature sensor Module is able to monitor the temperature in Heating or cooling mode and to activate the alarm if the temperature setpoint is exceeded. This can be used to send SMS messages to max 8 mobile phones (using the UCM/GSM)




TSM01 with White Glass Frame


TSM01 with Aluminium (plastic) frame


TSM01 with FR1-EV-AL frame and Surface Mount Berker backbox



TSM01 with FR1-E2-AL frame and Merten surface Backbox

Features

  • External TH1 Thermistor Sensor connected by Terminal block.
  • Display of Temperature in Celsius, mapped to Comfort Sensor
  • Display of Setpoint mapped to Comfort Counter. Enable or disable Setpoint is mapped to a Comfort Flag.
  • Up/down keys adjust the Setpoint and enable/disable the setpoint.
  • Assignment of Comfort Output to control relay to achieve setpoint.
  • Heating or Cooling Mode.
  • Programmable Hysteresis
  • Temperature Alarm Monitoring by mapping to Virtual Input in Comfort. This allows a Temperature alarm to be activated when the temperature exceeds the setpoint by programmable alarm offset.  The Alarm can dial to mobile phones or trigger SMS messages via the UCM/GSM module.  Restore Temperature by SMS is possible.
  • Calibration of Temperature reading is possible
  • in-wall or surface mount backboxes are available
  • Standard 1 gang 55 x 55 size European frame from many manufacturers like Merten, Gira, Jung, ABB etc
  • Up to 15 TSMs in a network.
  • Comfigurator is used to program TSM01 and upgrade firmware.

Specifications
  • Units: deg Celsius
  • Accuracy +/- 1 deg C
  • Display Temperature in Celcius mapped to Sensor
  • Up/Down Setpoint button mapped to Counter.
  • Up to 15 TSM01s in a Comfort, Logic Engine or UCM/Logic network.

The TSM01 Manual can be downloaded from https://www.cytech.biz/temperature_sensor_module.html

Print this item

  Partitions in Comfort
Posted by: slychiu - 08-07-2016, 07:59 AM - Forum: Security System Programming - Replies (16)

This note explains how the new Partitions feature in Comfort  work.

Comfort implements up to 4 Partitions which are like independent security systems with their own zones, security armed modes, entry/exit path, entry doors,  keypads and door stations  but share a common Siren, strobe and Telephone line.

Minimum System Requirements

  • Comfort Firmware 7.163
  • Keypad KP04A or KP06A firmware 7.005 or above. KT03 firmware 7.082 or above. KP04/KP05/KP06 will not work with partitions.
  • Comfigurator 3.12.13 or above for programming
  • UCM 7.124 and above
To use the partitions feature, Comfigurator View Mode must be set to Engineer Advanced


Partitions
4 partitions are available, numbered 0 to 3. Zones in existing systems are considered in Partition 0 (default)

There is no specific Partition Enable setting in Comfigurator. Partitions are enabled only if at least one zone is in Partition 1 to 3, and at least 1 keypad capable of supporting partitions is in Partition 1 to 3

Zones and Partitions
Each zone is assigned to only one partition 0 -3


Select Partition 0 to 3 for each zone.

Each Partition has its own exit/entry path, entry door zones, security armed mode, alarm state.

Important

If all zones are in the default Partition 0, then the system is not partitioned, even if Keypads and users are assigned to other partitions. As long as 1 zone is in a dfferent partition from 0, the partition is enabled.

Keypads and Partitions
Each keypad is assigned to one partition 0-3 (default 0).



A Keypad which is assigned to a partition can arm and disarm that partition only. To disarm the partition, a user who signs in on a keypad must also be enabled for the partition.

Keypads will hear the siren sounds for its own partition only eg arming beeps, intruder siren  sounds, arming zones, announcements. If there is an alarm the 12V siren will sound, but only the keypads for the alarm partition wil hear the keypad siren. Other keypads will not hear, but if a user signs in on a keypad for  another partition, the siren is also heard.

Security Check on a keypad will hear only the  zones open in that partition and see the zones open on the LCD.

If all zones are in partition 0, there are no partitions and keypads which are programmed in other partitions will work in Partition 0, ie the keypad partition is ignored.

If all keypads are in Partition 0, then the zones partition is ignored, and all zones are considered in partition 0, and the system is not partitioned

If no keypads in the system can handle Partitions, then partition settings are ignored, and the system is not partitioned. Only KP04A/KP06A firmware 7.005 and KT03 firmware 7.082 can handle partitions. KP01, KP03, KP04, KP06 cannot be used in Partitions.

The above checks ensures that older systems which are not partitioned when upgraded to the new Comfort firmware will not be unintentionally partitioned due to existing settings


Users and Partitions

Each User can be assigned to any combination of Partitions 0 to 3. This means that a user can be assigned to more than 1 partition, or all of them.



Each user can select area 0,1,2,3  to be enabled or disabled.
A user who is enabled for the partition is able to sign in on the keypad for the partition. If a user is enabled for all 4 partitions, he/she can sign in on any keypad for all partitions.
Eg User 1 is enabled for partition 0,1
User 2 is enabled for partitions 2
User 3 is enabled for partition 3
etc

Sirens
The 12V siren is common used for all partitions. Any full alarm will turn on the siren
Dial to CMS
Dial to cms will show the partition number that caused the alarm but it will be numbered as Partition 1 to 4 not 0 to 3 to conform to conventional understanding. if the system has no partition, it will report partition as 0

Door Stations and Partitions
Each door station is assigned to a partition. When the door station is pressed, only the keypads in the same partition will have the Doorbell chime. However any keypad in any partition can press a key to talk to the door station.



UCMs and Partitions

User who signs in on a  UCM with user code will log in to the 1st partition they are enabled for. Eg user 1 is enabled for partition 0 and 1. If sign in the user is logged into partition 0 not 1. He can arm and disarm partition 0 not 1.
Arming and Disarming Partitions
each partition can be independently armed and disarmed with its own entry door and entry/exit path.


SMS and PartitionsUsing UCM/GSM4, arming and disarming of any partition can be sent by SMS. However arming of security commands will work on Partition 0 only.




Security Mode Responses The Security Mode Responses ie (Off, Away, Night Day Mode) has separate responses for each partition.
Events > Miscellaneous Events now have Away, Night, Day, Security Off Responses for each partition.




Sirens and Speakers in Partitions
Sirens and Speakers can be connected to different partitions by specifying an Output for each partition which turns on when the Siren Output is activated by an alarm.A Relay can be connected to the selected Output to turn on the Siren in the partition. If a speaker is requuied for the partition, then use a Double Pole Relay and connnect the Speaker to the 2nd pole. The speaker when switched by the output would sound only for Alarms that activate the siren, and not for Trouble alarms and Arming beeping sounds

Note that the Speaker output if not switched by the relay would sound for all partitions, and is not recommended




Action Codes for Partitions
Testing for Partitions in Responses
It is necessary in some Responses to know what security Partition is active. For example in Intruder Alarm  Response, turn on Lights. Which partition caused the alarm? There is a new If Partition action ..




eg
If Partition = 0 Then
  Do Lights On
Else
    If Partition =1 Then
      Do Lights 2 on
    Endif
Endif
Set Partition
Many of the security-related actions are applied to a Partition
eg
  • Get Security Mode
  • Get alarm state
  • Get last security mode
  • Get entry alert
  • Get last zone
  • Get arming
  • Get entry alert
  • Get alarm type
  • Get away/vacation mode
  • Start entry delay
  • Cancel entry delay
  • Set exterminator
  • Skip alarm
  • Key arm
  • Auto arm
  • Bypass zones
  • Unbypass zones
  • Get input state
  • Do alarm report zonepartition
  • Do alarm report user
  • Alternate entry time

if the Response “Knows” the Partition then it will work as expected, For example a Zone Response will set the active partition according to the Zone Partition, so the Response actions will have the corect partition. Keypad and Door station Responses also know the partition because  each keypad and Door station  has a partition.

However other events like Time Programs do not have an assigned partition. A Time program will work on default partition 0. eg the Auto Arm and Auto Disarm Time programs will work on Partition 0. For Time programs to work on other partitions, the Set partition action is needed





eg
If Partition=2 and SecurityMode = SecurityOff Then
    AutoArm NightMode
End If

Compatibility with Non-partition systems
In an existing system or non-partitioned system, zones and keypads are  assigned to partition 0.
Old keypads can be used with new firmware if there are no partitions. If partitions are used, new keypads KP04A or KP06A which support the partitions feature must be used.

The keypad menu can also be used for programming (to a certain extent). See the attached document
The document has a pdf version of this instruction
https://www.cytech.biz/partitions_in_comfort.html


For Door Stations and Partitions, see http://www.comfortforums.com/view_topic.php?id=5383&forum_id=86

Print this item

  VPN
Posted by: strickers - 08-05-2016, 09:46 PM - Forum: Comfort Android App - Replies (9)

Hi,

I have changed my system to now use the eth03. With my old eth I could VPN into my home network and use the android app with comfort. I am using the latest app and now when I VPN in the app cannot talk to comfort but works fine when I am at home on the local network.

I do not want to forward any ports and only want to have remote access to comfort when the VPN is active.

Any ideas?

Thanks.

Print this item

  KT03 Upgrade failed from 7.072
Posted by: srooks - 08-01-2016, 11:28 PM - Forum: KT03 Touchscreen Keypad (OBSOLETE) - Replies (4)

I was unaware of the upgrade bug in 7.072 and tried to upgrade via Comfigurator/UCM to 74. This failed and the KT03 now appears dead. No LEDs lit.I tried to upgrade directly from ETH3UCM using a programming cable but this doesn\'t work, again no LEDs visible when plugged in.
Help!

Print this item

  Comfigurator 3.11.6
Posted by: slychiu - 07-30-2016, 01:11 PM - Forum: Comfigurator 3.x Old Versions (Archive) - Replies (13)

Known Bugs

  1. If Input does not work for Input > 64 to 96. This also applies for older versions
  2. Deg C /deg F in Comfiguration flags is incorrect
  3. Optimum when adding  UCM/KNX2 causes 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. Please do File > Update Defaults to update the set of  default templates.
  7. 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)
  8. Export Scenario does not work. Selecting any items will cause an exception
Bugs Fixed
  1. Actions for UCM/KNX2 did not work
  2. Importing a Configuration Item from a file with a different file system causes exception (old bug)
  3. Known Bugs in HIO and IRIO have been fixed
New Features
  1. Support for 4 Partitions in Comfort (requires Comfort Firmware 7.110)
  2. In Security > Zones, each zone has new settings for Partition and EOL shunts. These are for future Comfort features
  3. Support for UCM/Logic in File > New

Print this item

  ComfortClient
Posted by: juwi_uk - 07-28-2016, 04:01 PM - Forum: ComfortClient - No Replies

It was mentioned the other day how the ObjectMatrix is useful for troubleshooting sync problems with CBUS so I thought I\'d attach a screenshot for those who don\'t know what this is.
Ju



Attached Files Thumbnail(s)
   
Print this item


Online Users
There are currently 1125 online users. » 0 Member(s) | 1121 Guest(s)
Baidu, Bing, Facebook, Google

Powered By MyBB, © 2002-2026 Melroy van den Berg.