Comfort Automation/ Security System Forums

I am trying to get the Comfort Alarm to issue Commands to the UCM Universal when it sees certain incoming messages from the same UCM universal.
The response I have setup has 2 commands in it (They can be seen in the \"Commands to Device\" tab). When I right click the response and choose \"Execute Response\" both commands execute perfectly.
I then choose click Learn in the \"Device to Comfort\" tab and the  expected message appears. I choose type as Response and then select the Response that tested successfully earlier and then click \"Write to EEprom\". 
The Comfort does not seem to execute the Response when the message is seen. Am I doing something wrong? Is this the correct way to get the comfort to send a command to the UCM universal when it sees a particular message from the UCM universal?

Also of note is that the Device connected to the UCM terminates all commands with CRLF. When I used 0D as the terminator it would attach ForwardSlash-r to the start of every learned message. Using 0A as the terminator seems to clear this up (No appearance of ForwardSlash-n though)

Matching of the received commands can be tricky and there may well be a bugcan ypu send the cclx file and point out the conmands in quetsion/.Please email to support@cytech.biz

This issue was fixed in Universal 7.117 firmware, see http://www.comfortforums.com/view_topic.php?id=4111&forum_id=94

Hi Krobar
Your problem with the terminator is because the devuce sends CR, LF ie 0x0D, 0x0A
If you enter  CR as Terminator then you get \
ie 0x0A on the next line
if you use LF as terminator then 0x0D (CR) will fail the matching of messages
The solution is to use CR (0xD) as terminator, specify a Header ByteIt seems from your cclx file that ~ could be a Header byte that starts the new messagehence any characters after th terninator CR would be ignored. so you do not see \\N in the next line
The new test firmware Universal 7.126 fxies a bug with 7.117 that when you have a terminator, it cuts off the last character of the messsage received. That bug did not affect you because you have CR, LFI hope this explanation is not too confusing