Comfort Automation/ Security System Forums - UCM/CBUS Problems

Tracking Responses sending Cbus Commands

Sat, 07 Sep 2019 15:50:04 -0400

I am using Comfigurator with Comfort 2Z Ultra (v 7.160), Cbus2 Ucm (v7.106)

Code:
 
DateTime= 2019/09/07 20:56:35.245   App= 202  Trigger Control      Group= 014  Kitchen              Unit= 008  PC_CNIEI/INL_CNI     Event= Action Selector triggered : 50, \'Motion-AutoLights OFF\'

 DateTime= 2019/09/07 20:56:35.629   App= 056  Lighting             Group= 039  Kitchen Light 1      Unit= 009  PC_PACA/MOHAUPAC     Event= Group ramped to 063 ( 25%) over 12 seconds

 DateTime= 2019/09/07 20:56:35.632   App= 056  Lighting             Group= 040  Kitchen Light 2      Unit= 009  PC_PACA/MOHAUPAC     Event= Group ramped to 073 ( 29%) over 30 seconds

 DateTime= 2019/09/07 20:56:38.386   App= 056  Lighting             Group= 039  Kitchen Light 1      Unit= 127  EN_CMFT/COMFORT      Event= Group ramped to 064 ( 25%) over 0 seconds

 DateTime= 2019/09/07 20:56:38.598   App= 202  Trigger Control      Group= 014  Kitchen              Unit= 009  PC_PACA/MOHAUPAC     Event= Trigger Indicator Kill

I am using the Control Menu to send most of the On/Off commands to Cbus (mainly for using Comfort iPhone and my outgoing GSM Ucm)

I have included a log (above) from Cbus Toolkit which shows Comfort Ucm/Cbus (EN_CMFT/COMFORT) ramping Kitchen Light 1 to 25% over 0 seconds after a trigger event is raised.

I tried looking at all the responses where Kitchen Light One is referred to and for the life of me, I cannot track where in Comfort this occurs.

Zone UnBypass not logged in Toolkit Logs

Mon, 29 Oct 2018 04:00:19 -0400

When I bypass a zone in Comfort, the event is logged in C-Bus Toolkit (Security zone isolated). I expected to see an event to indicate this when the zone is UnBypassed, but all I see is the Security Zone sealed. Is the Zone Unbypass sent to CBUS?

I am using Comfort II ULTRA (7.142) with CbusUCM Cbus2 (7.068)

Capture.JPG (Size: 46.54 KB / Downloads: 16)

Error writing to EEPROM

Sun, 21 Jan 2018 02:21:53 -0500

When writing to EEPROM for KNX, Cbus, GSM4 and other UCM interfaces, if the message \"Error Writing Configuration\" appears..

This is probably due to a [color=\"#ff0000\"]very old UCM firmware[/color] (UCM/USB or UCM/ETH03) for the UCM used to program the system. The old UCM firmware is not able to support new features in Comfort or Comfigurator, and thus needs to be upgraded

The UCM firmware should be upgraded to the latest, by right clicking on the UCM under Modules and selecting \"Check for Firmware Upgrades\"

You will be asked to press F0 on the keypad to enable Engineer Mode

If you see that message, please press F0 on the keypad. This is a protection against unauthorised upgrade.
This will allow the firmware upgrade to start

Repeat actions showing in Comfort log

Mon, 06 Mar 2017 12:19:23 -0500

We use CBUS to control curtain movement. The curtains are moved by a timer in C-Bus and also by pressing wall buttons. The coding uses Ã¢â¬ËcurtainÃ¢â¬â¢ flags to keep track of whether the curtains are open or closed. Changes to the flag trigger a counter in Comfort that then is programmed to bypass the PIR in the appropriate area. (Without these bypass and unbypass instructions closing or opening of the curtains whilst we are away sometimes sets off the alarm when the temperature differential interprets it as a movement.)
Looking at the Comfort log when the curtains are triggered by a timer we get multiple bypass instructions.
03/06 17:51 Bypass Zone # Dining_Room (8)
03/06 17:51 Bypass Zone # Lounge (9)
03/06 17:51 Bypass Zone # Dining_Room (8)
03/06 17:51 Bypass Zone # Lounge (9)
03/06 17:51 Bypass Zone # Dining_Room (8)
03/06 17:51 Bypass Zone # Lounge (9)
03/06 17:51 Bypass Zone # Dining_Room (8)
03/06 17:51 Bypass Zone # Lounge (9)
03/06 17:51 Bypass Zone # Dining_Room (8)
03/06 17:51 Bypass Zone # Lounge (9)
03/06 17:51 Bypass Zone # Dining_Room (8)
03/06 17:51 Bypass Zone # Lounge (9)
03/06 17:51 Bypass Zone # Dining_Room (8)
03/06 17:51 Bypass Zone # Lounge (9)
03/06 17:51 Bypass Zone # Dining_Room (8)
03/06 17:51 Bypass Zone # Lounge (9)
03/06 17:51 Bypass Zone # Dining_Room (8)
03/06 17:51 Bypass Zone # Lounge (9)
03/06 17:51 Bypass Zone # Dining_Room (8)
03/06 17:51 Bypass Zone # Lounge (9)
03/06 17:52 UnBypass Zone # Dining_Room (8)
03/06 17:52 UnBypass Zone # Lounge (9)

When the curtains are triggered by a button we get a repeated bypass/unbypass

03/06 20:03 Bypass Zone # Main_Bedroom (12)
03/06 20:03 Bypass Zone # Main_Bedroom (12)
03/06 20:03 Bypass Zone # Main_Bedroom (12)
03/06 20:03 UnBypass Zone # Main_Bedroom (12)
03/06 20:03 Bypass Zone # Main_Bedroom (12)
03/06 20:03 Bypass Zone # Main_Bedroom (12)
03/06 20:03 Bypass Zone # Main_Bedroom (12)
03/06 20:03 Bypass Zone # Main_Bedroom (12)
03/06 20:03 Bypass Zone # Main_Bedroom (12)
03/06 20:03 UnBypass Zone # Main_Bedroom (12)

Why would instructions repeat when CBus is only executing one flag change to initiate the process?

not all UCM CBUS2 commands received

Fri, 14 Aug 2015 06:53:59 -0400

Hi
I\'ve just upgraded my UCM/CBUS unit to V2 (by replacing the CBUS plug-in) and am running V7.068
Most of the functionality is working as it should but I have a few responses that contain multiple CBUS commands (AllOff etc..) that are not processing all the individual steps.
These responses worked flawlessly with my V1 unit but are now causing issues.I have tested by adding a 1 second \'Wait\' command between cbus commands and this corrects the issue but it is not how I want, or expect, the system to behave.
Is this a known bug or is there are fix I need to implement?
thanks

Arming and Control Menu stopped working via Cbus2

Fri, 11 Apr 2014 11:24:14 -0400

Hi,

A few weeks ago, I could arm, disarm and switch Cbus lights on and off using the Control Menu on the iPhone APP. I had the following then...

Controller Fimware 7.047
Cbus1 Firmware 6.083 (beta test)

Since then I upgraded the following (including Comfigurator)

Controller Firmware 7.050
Cbus2 Firmware 7.042 (Beta)

From the iPhone App, I am no longer able to arm to any mode, or control Cbus lights via the Control Menu. I can still disarm.

I am using an iPhone 5s with iOS 7.1. I have emailed the new project and loaded that on the phone and I got the same results.

I can however arm from the iPad App, but the Control Menu gives the same results there.

CBus 2 Comfort

Thu, 03 Oct 2013 18:32:40 -0400

I have noticed that on the first TX from Cbus 2 Comfort nothing happens.
I am aware that this could be on the Cbus end but has any one else had this problem?
Comfigurator 3.75
Firmware 7.029
Cbus v6.083

Response
Output UPS4 Off
Cbus RampInst UCM-Cbus 190 0
128,36,0, 197,19,190,2,0, 255

Any thoughts?
Mike

UCM CBUS Issues HELP!!!

Tue, 23 Jul 2013 07:51:18 -0400

HI All,

I have been getting some help from admin but they cannot replicate this issue- I think it is an issue with the UCM CBUS as my CBUS network appears fine (all buttons work & status is updated in the toolkit). Within Comfort the status of each CBUS takes a minute or so to update, I am also unable to issue any commands for example turn lights off or on. It looks like Comfort issues the command but it receives the same response everytime.

Admin have suggested I return the module but I would prefer to try and identify the issue before I send it off for repair / replacement.

When I issue a command I always get the same response back
< RA0000 for example selecting a response: Cbus On UCM02 3 I get the following:
> DAC5120379FF
< RA0000

The strange thing is that if I remove the wiring from the CBUS Sim and then put the wires back in it appears to work fine for 10 minutes and then stops again.

I have checked all wiring and replaced the wiring between the UCM Cbus & Cbus. can anyone give any suggestions as to what may be happening.

Hopefully I can resolve before having to return the module.

UCM/CBUS stops broadcasting Zone Statuses

Mon, 11 Mar 2013 00:55:18 -0400

UCM/CBUS firmware 6.011
Utra firmware 7.022

I use a C-bus PAC controller to do most of my lighting logic.

At times, lights would not turn on/off as I would expect and initially I thought my PICED logic was at fault. After months and months of investigating, I noted that there are times when Toolkit would not show any change in Comfort Zone Statuses (Application 001 & 208) as the UCM did not transmit the statuses.

When the UCM is in this bad state, the Alarm status changes (Day,OFF, Night, etc) are transmitted, only the Zone Statuses are affected. When this happens, disconnecting and reconnecting the UCM seems to fix the problem.

Not sure when or what may be causing this. I\'ve had to disconnect and reconnect the UCM about 3 times this month. After reconnecting, everything seems to start working as desired for a while till the next disconnect.

UCM/Cbus

Sun, 14 Aug 2011 02:12:41 -0400

Ingo and Palmlodge have encountered a problem with the UCM/Cbus where after some time, it stops receiving any Cbus messages, ie it does not generate a counter update CT as seen in Monitor IO This could not be duplicated by Cytech so far even when testing with Ingos configuration

However the problems reported by Ingo and palmlodge are not consistent

Correct me if I am wrong, Ingo had no issues with UCM/Cbus 5.208 but started having problems with 5.216 with the new ST7 SIM. After a fea days or week, the UCM/CBus would stop receiving Cbus messages and updating counters but could still send message to Cbus

Ingo upgraded to UCM 5.235 with the old SIM and had no problems
But when the ST7 SIM was used, the same problems still occured but after a longer interval. So with Ingo it seems the problem only happens with the new ST7 SIM

Palmlodge reported the same issue with receiving cbus messages and counter updates (but not reported whether Comfort can send messages to Cbus) with 5.235 whereas he had noi problems with 5.216 for several years, see http://www.comfortforums.com/forum73/2397.html
He is using the new ST7 SIM

CBUS firmware 5.235 generally fixes bugs in 5.216 and also has significant improvements see http://www.comfortforums.com/forum85/2293.html

I hope this is an accurate summary of the problem reported so far

Issues since CBUS UCM upgrade

Thu, 11 Aug 2011 14:56:19 -0400

I\'ve got a strange issue where Comfort and CBUS occaisionally aren\'t talking - I have various CBUS buttons to kick off Comfort responses for critical items, and have been doing so for around 5 years with no issues.

I\'ve recently upgraded the CBUS UCM to 5.235 (the latest) - co-incidence ?

I can see in the CBUS monitor the button is pressed, but Comfort I/O monitor shows no signs of activity. The HomeSeer log shows no real activity, so it cannot be bus traffic overload (that is being reported)

Previously, I have been pressing the \"reset\" button on the CBUS UCM to kick things back into life, but tonight, I kept trying the same CBUS button until eventually it started working again. The same code on this particular button has not changed in 4 years.

How can we debug this ?

Sending comands to non-lighting applications affects Counter

Sun, 20 Mar 2011 10:09:53 -0400

There is a bug in UCM/Cbus firmware up to 5.217 which was recently discovered

When Comfort sends a command to a non-lighting application eg Trigger, the counter corresponding to that group address is also changed. Counters should only be changed by the Lighting application group address.

However receiving messages from other Cbus applications does not affect the counter for the group address, it is only transmitting from Comfort that has this problem

The problem will be fixed in the next UCM/Cbus firmware

C-Bus ucm stops reporting

Thu, 29 Apr 2010 12:10:42 -0400

I installed a C-Bus UCM a couple of weeks ago and noticed that I get an irregular problem with the UCM \"locking up\". I\'m primarily using the UCM to translate zone on/off status and the security mode to the C-Bus lighting application.

When the UCM locks up, it stops sending levels to the C-Bus, Comfort itself carrys on working fine. LEDs on the UCM show RDY as on, and D10 & D9 flashing, all other LEDs are off.

Resetting the UCM does not recover C-Bus communications, that requires a reset of the main Comfort panel.

I\'ve currently on quite an old Comfort system, Pro 4.170. C-Bus UCM is 5.154.

Concatenation Gotcha

Thu, 17 Jul 2008 03:39:19 -0400

I am posting this so others have a chance of not being caught out like me. My version of Ultra is quite old and therefore has the known limitation that the Counters below 128 react not only to C-Bus groups 0 through 127, but also react to 128 through 255. This effectively means that I have only half of the Group Addresses within the Lighting Application available for use.

I have recently identified a need to have the status of some Comfort outputs visible to C-Bus. I chose to do this by using responses to switch on Group Addresses in a C-Bus application (57) created for the purpose. My choice of 57 follows Clipsal\'s recommendations.

That all works fine and I can see on/off messages for the outputs.

However, when I try to do things which affect both groups, I have discovered that this code (generated by Comfigurator):

Code:
CBUS Off 2 8 0 57

CBUS Off 2 22

or this code (manually written by me to try and fix the problem):

Code:
CBUS Off 2 8 0 57

CBUS Off 2 22 0 56

did not work as expected. In both cases, the second command appears on C-Bus for Application 57 (not 56 as expected).

The fix is very simple - turn off the concatenation check-box against the UCM in Comfigurator. This does not seem to have had any adverse effects, but I don\'t have any really lengthy C-Bus commands going out from Comfort.

This might be a bug, it might be expected behaviour, it might be fixed in a newer UCM version. Thinking about it, it might even be a feature in Comfigurator when it turns \"code\" into \"actions\" and finds adjacent C-Bus commands.

I have found a fix that works for me. As I said, have only posted to avoid anyone else having the same challenge.