C-touch randomly sending Cbus commands

Discussion in 'C-Touch/HomeGate/SchedulePlus/PICED Software' started by nsa195, Apr 16, 2018.

  1. nsa195

    nsa195

    Joined:
    Oct 27, 2014
    Messages:
    18
    Likes Received:
    0
    Location:
    Sydney
    Hi all,

    The Cbus intall (2012~) in my house has seldom been totally stable. The most irritating issue is that the CTC2 (unit 3) randomly sends commands on the network that affect lighting. I get this message repeatedly through the PICED Event Log, always for groups 4 5 6 and 7, plus some more random groups but not as often as these four.

    16/04/2018 11:55:10 C-Gate : Rx "lighting off //MM14/254/56/4 #sourceunit=3 OID=949501c0-2329-1036-9624-982f4d5299ca"
    16/04/2018 11:55:10 C-Bus Rx : Set G.Garage Entry Off (unit 3)
    16/04/2018 11:55:10 C-Gate : Rx "lighting off //MM14/254/56/5 #sourceunit=3 OID=94954fe0-2329-1036-9626-982f4d5299ca"
    16/04/2018 11:55:10 C-Bus Rx : Set G.Dining Pendant Off (unit 3)
    16/04/2018 11:55:10 C-Gate : Rx "lighting off //MM14/254/56/6 #sourceunit=3 OID=94959e00-2329-1036-9628-982f4d5299ca"
    16/04/2018 11:55:10 C-Bus Rx : Set G.Powder Room Pendant Off (unit 3)
    16/04/2018 11:55:10 C-Gate : Rx "lighting off //MM14/254/56/7 #sourceunit=3 OID=9495ec20-2329-1036-962a-982f4d5299ca"
    16/04/2018 11:55:10 C-Bus Rx : Set G.Lift Outside Powder Off (unit 3)

    16/04/2018 12:30:35 C-Gate : Rx "lighting off //MM14/254/56/89 #sourceunit=3 OID=94a50750-2329-1036-968d-982f4d5299ca"
    16/04/2018 12:30:35 C-Bus Rx : Set B.Bed 2 Ens Vanity LED Off (unit 3)
    16/04/2018 12:30:35 C-Gate : Rx "lighting off //MM14/254/56/90 #sourceunit=3 OID=94a52e60-2329-1036-968e-982f4d5299ca"
    16/04/2018 12:30:35 C-Bus Rx : Set B.Bed 3 Ens Vanity LED Off (unit 3)

    16/04/2018 13:35:58 C-Gate : Rx "lighting off //MM14/254/56/4 #sourceunit=3 OID=949501c0-2329-1036-9624-982f4d5299ca"
    16/04/2018 13:35:58 C-Bus Rx : Set G.Garage Entry Off (unit 3)
    16/04/2018 13:35:58 C-Gate : Rx "lighting off //MM14/254/56/5 #sourceunit=3 OID=94954fe0-2329-1036-9626-982f4d5299ca"
    16/04/2018 13:35:58 C-Bus Rx : Set G.Dining Pendant Off (unit 3)
    16/04/2018 13:35:58 C-Gate : Rx "lighting off //MM14/254/56/6 #sourceunit=3 OID=94959e00-2329-1036-9628-982f4d5299ca"
    16/04/2018 13:35:58 C-Bus Rx : Set G.Powder Room Pendant Off (unit 3)
    16/04/2018 13:35:58 C-Gate : Rx "lighting off //MM14/254/56/7 #sourceunit=3 OID=9495ec20-2329-1036-962a-982f4d5299ca"
    16/04/2018 13:35:58 C-Bus Rx : Set G.Lift Outside Powder Off (unit 3)

    16/04/2018 13:38:22 C-Gate : Rx "lighting off //MM14/254/56/4 #sourceunit=3 OID=949501c0-2329-1036-9624-982f4d5299ca"
    16/04/2018 13:38:22 C-Bus Rx : Set G.Garage Entry Off (unit 3)
    16/04/2018 13:38:22 C-Gate : Rx "lighting off //MM14/254/56/5 #sourceunit=3 OID=94954fe0-2329-1036-9626-982f4d5299ca"
    16/04/2018 13:38:22 C-Bus Rx : Set G.Dining Pendant Off (unit 3)
    16/04/2018 13:38:22 C-Gate : Rx "lighting off //MM14/254/56/6 #sourceunit=3 OID=94959e00-2329-1036-9628-982f4d5299ca"
    16/04/2018 13:38:22 C-Bus Rx : Set G.Powder Room Pendant Off (unit 3)
    16/04/2018 13:38:22 C-Gate : Rx "lighting off //MM14/254/56/7 #sourceunit=3 OID=9495ec20-2329-1036-962a-982f4d5299ca"
    16/04/2018 13:38:22 C-Bus Rx : Set G.Lift Outside Powder Off (unit 3)

    Incidentally, units 4 5 6 and 7 do not exist on the network (see attached picture): any possible relationship between the random trigger of group numbers and the absence of the same units numbers ? Or just weird coincidence ?

    Units on network.JPG

    When the CTC2 is manually switched off (unplugged from power) none of this happens (i can check it from the Toolkit log). It otherwise functions properly (schedules etc...). Any clue to look for ?

    Many thx.
     
    nsa195, Apr 16, 2018
    #1
    1. Advertisements

  2. nsa195

    jboer

    Joined:
    Apr 27, 2012
    Messages:
    358
    Likes Received:
    8
    Location:
    Sydney
    Hey,

    Out of interest are these groups that are being erratic all on the same output unit (relay, dimmer) or across a couple?
     
    jboer, Apr 18, 2018
    #2
    1. Advertisements

  3. nsa195

    nsa195

    Joined:
    Oct 27, 2014
    Messages:
    18
    Likes Received:
    0
    Location:
    Sydney
    Yes 4 5 6 7 are all on the same dimmer. But other groups affected randomly are spread on other units.

    2018_04_20 errors.JPG


    Also interesting, in nearly all cases the command is just repeating the present state, it is clear in this example:

    DateTime= 19/04/2018 17:24:27.247 App= 056 Lighting Group= 005 G.Dining Pendant Unit= 060 Event= Group ramped to 171 ( 67%) over 0 seconds
    DateTime= 19/04/2018 17:28:57.452 App= 056 Lighting Group= 013 G.Kitchen Wall Lt Unit= 003 Event= Group ramped to 255 (100%) over 4 seconds
    DateTime= 19/04/2018 17:29:30.294 App= 205 Multi-room Audio Group= N/A Unit= 003 Event= Output Device Status Request: Parameter 0
    DateTime= 19/04/2018 17:29:36.904 App= 223 Clock and Timekeeping Group= N/A Unit= 003 Event= Group on
    DateTime= 19/04/2018 17:30:22.077 App= 223 Clock and Timekeeping Group= N/A Unit= 003 Event= Date Broadcast: Date set to Thursday 2018-04-19.
    DateTime= 19/04/2018 17:30:22.078 App= 223 Clock and Timekeeping Group= N/A Unit= 003 Event= Time Broadcast: Time set to 17:30:18. Daylight saving offset set to 0 hours.
    DateTime= 19/04/2018 17:32:29.914 App= 056 Lighting Group= 006 G.Powder Room Pendant Unit= 003 Event= Group off
    DateTime= 19/04/2018 17:32:29.915 App= 056 Lighting Group= 007 G.Lift Outside Powder Unit= 003 Event= Group off
    DateTime= 19/04/2018 17:32:38.825 App= 056 Lighting Group= 005 G.Dining Pendant Unit= 003 Event= Group ramped to 171 ( 67%) over 0 seconds
    DateTime= 19/04/2018 17:32:56.856 App= 056 Lighting Group= 000 Ext.Front Door Wall Lt Unit= 003 Event= Group on
    DateTime= 19/04/2018 17:34:02.850 App= 056 Lighting Group= 021 G.Steps Lts Unit= 003 Event= Group on
    DateTime= 19/04/2018 17:34:02.890 App= 056 Lighting Group= 021 G.Steps Lts Unit= 003 Event= Group on
    DateTime= 19/04/2018 17:38:25.850 App= 056 Lighting Group= 005 G.Dining Pendant Unit= 003 Event= Group ramped to 171 ( 67%) over 0 seconds
    DateTime= 19/04/2018 17:47:08.038 App= 056 Lighting Group= 005 G.Dining Pendant Unit= 003 Event= Group ramped to 171 ( 67%) over 0 seconds

    You can see group 005 being set manually (first line) at 67%, and then unit 003 (CTC) repeats it 3 times over the next 30 minutes.

    It sometimes trigger a scene which lights on several groups that were previously off.
     
    nsa195, Apr 20, 2018
    #3
  4. nsa195

    jboer

    Joined:
    Apr 27, 2012
    Messages:
    358
    Likes Received:
    8
    Location:
    Sydney
    Just for kicks, I would suggest unplugging the dimmer and seeing if it resolves the problem. I have seen many times where another unit (often output unit) starts transmitting the exact same command it received back out again, complete with the originating unit address.
     
    jboer, Apr 20, 2018
    #4
  5. nsa195

    nsa195

    Joined:
    Oct 27, 2014
    Messages:
    18
    Likes Received:
    0
    Location:
    Sydney
    With the dimmer on which groups 4 5 6 7 are wired being taken out of the Cbus network (by unplugging both Cbus wires), the global behaviour is still the same but the CTC is affecting other groups of consecutive numbers, such as 36 37 38 39, or 68 69 70:

    2018_04_21 errors.JPG
     
    nsa195, Apr 21, 2018
    #5
  6. nsa195

    nsa195

    Joined:
    Oct 27, 2014
    Messages:
    18
    Likes Received:
    0
    Location:
    Sydney
    Traffic report (of the Diagnostic Utility) shows a large number of CAL messages, is it normal ? The reliability test gives perfect results on most units, good on some. Installation MMI Results shows, from one second to the next, units present or in conflict, that in fact do not exist, and disappear the next second. Application 56 MMI Results is similarly unstable from one second to the next, sometimes says not a single group address is present, shows group address errors or group address on for group numbers that do not exist, and the next second all is ok (appMMI 1.jpg below is the ok state).

    2018_04_21 traffic Report.JPG

    appMMI 1.JPG appMMI 2.JPG appMMI 3.JPG appMMI 4.JPG
     
    nsa195, Apr 21, 2018
    #6
  7. nsa195

    NickD Moderator

    Joined:
    Nov 1, 2004
    Messages:
    1,305
    Likes Received:
    17
    Location:
    Adelaide
    It sounds like the touchscreen is trying to correct a status inconsistency.

    The ongoing occurrence of this could suggest a unit with a faulty transceiver.. which is either not receiving the MMI correctly or not transmitting its contribution correctly.

    When an inconsistency is detected on any given group, the last unit to set that group is responsible for re-broadcasting the correct state.

    jboer's suggestion of unplugging the output unit that the groups being corrected exist in is a good one. If the problem goes away then it may be this unit is faulty.

    As for the large number (and rate) of CAL messages... this does not sound normal. Do you have any monitor components in your touchscreen project (monitoring unit voltage is the most common one)? These use CAL messages, but the rate is still very high, which either suggests you have too many of them or there are communication problems resulting in a lot or retries.

    Nick
     
    Last edited: May 9, 2018
    NickD, May 9, 2018
    #7
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.