UCM/Cbus

[Ingo]

I\'ve downloaded the new code so let\'s see what happens.

Ingo

[ident]

So there has been no problems since the upgrade to Cbus 6.011 since the upgrade for any of you?

[Ingo]

Mine has been running stable since the upgrade but we know it sometimes take more than two weeks to \'break\'. I would give it another week or two before I can really say that it\'s working better than before. It does look promising though...

Ingo

[Ingo]

I just had another partial failure. I had a power failure for about 20 minutes where the Cbus network went down but obviously Comfort stayed up and running. Checking functionality after the power failure I saw commands go to/from Cbus to/from Comfort and back EXCEPT when I do a Cbus \'Get Status\' command below.

2011/10/05 19:47:45  Info     : Special Function \"Security Status Request\" Executed

Usually this command forces the UCM/Cbus to send all the zones status to Cbus but it doesn\'t do anything. Resetting the UCM/CBus via software restarted the zone updates again.

Ingo

[slychiu]

The communications both ways between cbus and comfort were working after the power failure?

Did you know if the zones were already updated to Cbus before you send the Security Status command? Does the security status command work in normal cases?

[Ingo]

[user=1]slychiu[/user] wrote:

The communications both ways between cbus and comfort were working after the power failure?

Did you know if the zones were already updated to Cbus before you send the Security Status command? Does the security status command work in normal cases?

1. Yes.

2. Good question - I don\'t know, it\'s not something I check regularly, perhaps once or twice a week. Under normal conditions it works perfectly.

[slychiu]

Perhaps you can switch off the Cbus for a few seconds  and try
The UCM/Cbus shoulod resend the zones info once it detets that the Power has retured, so it should not be necessary to query security zones

[Ingo]

I simulated the conditions of last night but this morning the Security command worked as expected. It seems that this issue is not related to the thread we are currently busy with. I sent you a PM earlier with some findings.

Ingo

[palmlodge]

Is this 6.0 stream now stable and Ok to upgrade from 5.x ?

[ident]

Yes, as far as we know, that is why they have been released.
We have not heard from you if the firmware has fixed the problem you reported. This was one of the problems we intended to fix, so until we have a confirmation from you we dont really know if it does fix it, because the problemnms repirted could not be duplicated