Application 1 vs Application 208 / Outputs and Doorbell

[Nick Locke]

I asked this one a couple of years back and the consensus was \"can\'t happen\".  I\'m now going to ask again!  I\'ve attached a screenshot from C-Bus toolkit showing an extract from the application log.  As expected, I can see security events being reported on both application 208 and application 1.

Looking closely at application 1 though, I am seeing ramp commands rather than on/off commands.  When I first asked this, I was told that it could not happen - the C-Bus UCM will only issue on/off not ramps.  This is happening with the latest version of Toolkit and it still looks the same.  Unit 253 is the C-Bus UCM.  Clues welcome!

Now to the more important question.  I need C-Bus to be aware whenever Comfort switches on an Output and when someone presses the doorbell.  I guess I can do this by using responses to issue C-Bus commands (maybe I should use Application 2 for that to keep it away from everything else?).  Just wondered whether I am missing something and if there is an easier way.

Thanks, Nick.

 

[slychiu]

What you are seeing in the log for Application 1 is Ramp to 000 and Ramp to 255; these are effective off and on commands. the value 255 corresponds to ON and 0 to off. The toolkit does not know about how Application 1 is used, so it reporting it like a Lighting application

To report a doorbell press to Cbus, use the Doorbell Response in Responses > Misc Events to send a Cbus command to any group address. I suppose you could use application 2, but lighting application could also be used, and perhaps easier to do

To report the state of outputs, there is no output response when outputs are switched, so you will have to send the Cbus commands together with the commands switching the outputs

[Nick Locke]

Thanks Chiu,

Ramp to 000 and Ramp to 255; these are effective off and on commands. the value 255 corresponds to ON and 0 to off. The toolkit does not know about how Application 1 is used, so it reporting it like a Lighting application.

Understood, but I think C-Bus is seeing a \"ramp\" rather than \"on\".  I am using logic in HomeGate and have to code \"level <> 0\" rather than \"level = 255\" to get an immediate notification.  If I use \"level=255\", it seems to be four seconds before the logic reacts.

I suppose you could use application 2, but lighting application could also be used, and perhaps easier to do. To report the state of outputs, there is no output response when outputs are switched, so you will have to send the Cbus commands together with the commands switching the outputs

The rationale for using application 2 for the outputs is that I won\'t then see any numbering conflicts - Comfort Outputs 1 to 64 can map to Group Addresses 1 to 64.  If I use the lighting app (or app 1), then I can\'t get that simplicity!

Thanks again.  Nick.

[slychiu]

I see, but Comfort is sending a level of 00 for off and 255 for on. It does not send any ramping time in the message. In C-Touch the zone will turn off and on correctly
I cannot say there is no delay always but that is because of C-Bus, not becauuse of ramping
I believe what you see is due to Homegate handling the message wrongly. We dont use Homegate so I cannot verify

[Nick Locke]

Thanks again Chiu.  Bottom line, is that I have it working now (albeit with \"<> 0\" rather than \"= 255\"), so everything is good!!

Nick