Homegate puzzle

Hello, I face a strange (to me) problem so any help would be welcome.
I have a medium home installation with
6 5512RVF
1 5504D2A
8 5054NL
10 5058NL
an old b/w touch screen
a homegate v3.9.

Although I've programmed the installation almost 3 years ago, the latest month strange things are happening (or the customer just now noticed them).

One of the buttons on the homegate was turning on and off although the actual light was continuously on and all other inputs that were using it (keys and touch screen) had the correct indication. After changing the group address this problem was mysteriously solved.

Now we face a problem with two different groups that are turned on for 30-40 secs (pulse) from 2 different buttons on the homegate project. When you press the button, sometimes, turns on and starts counting the seconds to turn off again but after a few seconds the timer stops and the group remains to on for ever. In the same time the indication of the group in the homegate starts turning on and off like the previously mention problem. When the same timer is activated from the touch screen or a key there is no problem at all. Whatever I have tried seems to fail and the only clue I have, but I'm not sure is relative though,is from the cgate log that shows before losing the timer a command:
13/4/2010 12:16:02 ii C-Gate : Rx "# lighting SyncUpdate //ASIMAKOP/254/56/2 level=0 #sourceunit=-1 OID=142d53b0-9b0a-1029-ac62-d6aa8d79e3e9"
And that is repeated from time to time.

Can it be a communication problem, let say from the wiring to pc-interface that connects the homegate to the c-bus? Anybody have any ideas or met souch a problem before?

Thank you for your patience to read this very long message.

 

The message from C-Gate was:

# lighting SyncUpdate //ASIMAKOP/254/56/2 level=0 #sourceunit=-1

In this case, the # prefix from C-Gate is saying the message is like a "comment".

This message is saying that lighting group address 2 is at level 0 and that this was found during the background sync process (SyncUpdate). C-Gate has read the information from a unit which believes that the level was 0, so C-Gate has reported this.

The thing which is not clear is exactly why this is happening, and why it has just started happening recently.

To solve this, there are a few things we are going to need:
1. A HomeGate log spanning the period where this problem occurs
2. A C-Gate event level 9 log for the same period
3. A description of what was done and when and what happened
4. Possibly, the HomeGate project

Either send this to CIS Tech Support with a note to forward it to me, or send using the Help | Report a Problem menu item.

 

Thank you very much both for your quick response. Darren I took your advise ,I hope I sent you all the data you need.