controlling cgate by device name

Discussion in 'C-Bus Toolkit and C-Gate Software' started by countach, Sep 20, 2013.

  1. countach

    countach

    Joined:
    Dec 22, 2005
    Messages:
    49
    Likes Received:
    0
    It's been a while since I controlled my house with cgate for various reasons. Anyway, I downloaded all the latest software and set it up.

    Anyway, I tried to do things the way I used to, which is to connect to cgate with telnet, and control lights with things like

    on bathroom

    etc. But its not allowing that. I have to use the network number:

    on //MYHOUSE/254/56/5

    etc.

    If I look at it with Cbus toolkit all my lights have proper names under the "Applications->Lighting" section, as I would expect. But Cgate doesn't seem to know about those meaningful names.

    What am I missing?
     
    countach, Sep 20, 2013
    #1
  2. countach

    countach

    Joined:
    Dec 22, 2005
    Messages:
    49
    Likes Received:
    0
    dbverify

    I don't know if this is relevant, but dbverify gave the following:

    345-Difference: Tag database address 15 and C-Bus address 254/56/15 are different (Field: Phantom does not match)
    345-Difference: Tag database address 33 and C-Bus address 254/56/33 are different (Field: Area does not match)
    345-Difference: 36 missing from C-Bus (Group not defined in C-Gate)
    345-Difference: 136 missing from C-Bus (Application not defined in C-Gate)
    345-Difference: 202 missing from C-Bus (Application not defined in C-Gate)
    345-Difference: 203 missing from C-Bus (Application not defined in C-Gate)
    345-Difference: 224 missing from C-Bus (Application not defined in C-Gate)
    345-Difference: 0 missing from C-Bus (Unit not defined in C-Gate)
    345-Difference: Tag database address 1 and C-Bus address 254/p/1 are different (Field: UnitName does not match)
    345-Difference: Tag database address 1 and C-Bus address 254/p/1 are different (Field: CatalogNumber does not match)
    345-Difference: Tag database address 2 and C-Bus address 254/p/2 are different (Field: UnitName does not match)
    345-Difference: Tag database address 2 and C-Bus address 254/p/2 are different (Field: CatalogNumber does not match)
    345-Difference: Tag database address 3 and C-Bus address 254/p/3 are different (Field: UnitName does not match)
    345-Difference: Tag database address 3 and C-Bus address 254/p/3 are different (Field: CatalogNumber does not match)
    345-Difference: Tag database address 4 and C-Bus address 254/p/4 are different (Field: UnitName does not match)
    345-Difference: Tag database address 4 and C-Bus address 254/p/4 are different (Field: CatalogNumber does not match)
    345-Difference: Tag database address 5 and C-Bus address 254/p/5 are different (Field: CatalogNumber does not match)
    345-Difference: Tag database address 6 and C-Bus address 254/p/6 are different (Field: UnitName does not match)
    345-Difference: Tag database address 6 and C-Bus address 254/p/6 are different (Field: CatalogNumber does not match)
    345-Difference: Tag database address 7 and C-Bus address 254/p/7 are different (Field: UnitName does not match)
    345-Difference: Tag database address 7 and C-Bus address 254/p/7 are different (Field: CatalogNumber does not match)
    345-Difference: Tag database address 8 and C-Bus address 254/p/8 are different (Field: UnitName does not match)
    345-Difference: Tag database address 9 and C-Bus address 254/p/9 are different (Field: UnitName does not match)
    345-Difference: Tag database address 10 and C-Bus address 254/p/10 are different (Field: UnitName does not match)
    345-Difference: Tag database address 11 and C-Bus address 254/p/11 are different (Field: UnitName does not match)
    345-Difference: Tag database address 12 and C-Bus address 254/p/12 are different (Field: UnitName does not match)
    345-Difference: Tag database address 12 and C-Bus address 254/p/12 are different (Field: SerialNumber does not match)
    345-Difference: Tag database address 13 and C-Bus address 254/p/13 are different (Field: UnitName does not match)
    345-Difference: Tag database address 14 and C-Bus address 254/p/14 are different (Field: UnitName does not match)
    345-Difference: Tag database address 15 and C-Bus address 254/p/15 are different (Field: UnitName does not match)
    345-Difference: Tag database address 16 and C-Bus address 254/p/16 are different (Field: UnitName does not match)
    345-Difference: Tag database address 17 and C-Bus address 254/p/17 are different (Field: UnitName does not match)
    345-Difference: Tag database address 18 and C-Bus address 254/p/18 are different (Field: UnitName does not match)
    345-Difference: Tag database address 19 and C-Bus address 254/p/19 are different (Field: UnitName does not match)
    345-Difference: 20 missing from C-Bus (Unit not defined in C-Gate)
    345-Difference: Tag database address 21 and C-Bus address 254/p/21 are different (Field: UnitName does not match)
    345-Difference: Tag database address 22 and C-Bus address 254/p/22 are different (Field: FirmwareVersion does not match)
    345-Difference: Tag database address 22 and C-Bus address 254/p/22 are different (Field: UnitType does not match)
    345-Difference: Tag database address 22 and C-Bus address 254/p/22 are different (Field: UnitName does not match)
    345-Difference: Tag database address 22 and C-Bus address 254/p/22 are different (Field: CatalogNumber does not match)
    345-Difference: Tag database address 22 and C-Bus address 254/p/22 are different (Field: SerialNumber does not match)
    345-Difference: Tag database address 23 and C-Bus address 254/p/23 are different (Field: UnitName does not match)
    345-Difference: 24 missing from C-Bus (Unit not defined in C-Gate)
    345-Difference: Tag database address 25 and C-Bus address 254/p/25 are different (Field: UnitName does not match)
    345-Difference: Tag database address 26 and C-Bus address 254/p/26 are different (Field: UnitName does not match)
    345-Difference: Tag database address 27 and C-Bus address 254/p/27 are different (Field: UnitName does not match)
    345-Difference: 28 missing from C-Bus (Unit not defined in C-Gate)
    345-Difference: Tag database address 29 and C-Bus address 254/p/29 are different (Field: UnitName does not match)
    345-Difference: Tag database address 30 and C-Bus address 254/p/30 are different (Field: UnitName does not match)
    345-Difference: Tag database address 31 and C-Bus address 254/p/31 are different (Field: UnitName does not match)
    345-Difference: Tag database address 32 and C-Bus address 254/p/32 are different (Field: UnitName does not match)
    345-Difference: Tag database address 33 and C-Bus address 254/p/33 are different (Field: UnitName does not match)
    345-Difference: Tag database address 35 and C-Bus address 254/p/35 are different (Field: UnitName does not match)
    345-Difference: Tag database address 36 and C-Bus address 254/p/36 are different (Field: UnitName does not match)
    345-Difference: Tag database address 38 and C-Bus address 254/p/38 are different (Field: UnitName does not match)
    345-Difference: Tag database address 39 and C-Bus address 254/p/39 are different (Field: UnitName does not match)
    345-Difference: 40 missing from C-Bus (Unit not defined in C-Gate)
    345-Difference: Tag database address 42 and C-Bus address 254/p/42 are different (Field: UnitName does not match)
    345-Difference: Tag database address 44 and C-Bus address 254/p/44 are different (Field: UnitName does not match)
    345-Difference: Tag database address 47 and C-Bus address 254/p/47 are different (Field: UnitName does not match)
    345-Difference: Tag database address 47 and C-Bus address 254/p/47 are different (Field: CatalogNumber does not match)
    345-Difference: Tag database address 255 and C-Bus address 254/p/255 are different (Field: UnitName does not match)
    408 Operation failed: (Verify failed: 62 differences)
     
    countach, Sep 20, 2013
    #2
  3. countach

    daniel C-Busser Moderator

    Joined:
    Jul 26, 2004
    Messages:
    766
    Likes Received:
    20
    Location:
    Adelaide
    Yes it has been a while!

    Since Toolkit 1.11.0 (more than 3 years ago) the use of tagname addressing was deprecated because it caused unpredictable behaviour. if a user had multiple objects (projects, networks, units, applications, groups or levels) called "bathroom", there was no way of telling what would actually happen when you sent these commands. Diagnosing such problems in the field was really painful.

    Bearing in mind the above caveats with tagname conflicts, and with a warning that you should not rely on this for commercial sites, you CAN still invoke tagname addressing by prefixing the tagname with an exclamation mark:

    on !bathroom
     
    Last edited by a moderator: Sep 23, 2013
    daniel, Sep 23, 2013
    #3
  4. countach

    countach

    Joined:
    Dec 22, 2005
    Messages:
    49
    Likes Received:
    0
    Thanks

    Interesting. I would have thought CGATE would know about the names of all the objects, and if there was a conflict, to report an appropriate error message.

    Still, as long as I can use the !!! syntax, I'm happy. Wouldn't want this "secret" feature to accidentally disappear in the future though. :)

    So... would it be stupid to ask what is the purpose of the tag name, now that it is deprecated?
     
    countach, Sep 24, 2013
    #4
  5. countach

    daniel C-Busser Moderator

    Joined:
    Jul 26, 2004
    Messages:
    766
    Likes Received:
    20
    Location:
    Adelaide
    Tagnames themselves aren't deprecated, they are still crucial as human readable names for C-Bus concepts. Client applications will still display "bathroom" and let you turn it on, but instead of telling C-Gate "on bathroom" they use the correct address and instruct C-Gate "on 254/56/5".

    None of our applications need or use the ! prefix but there are no plans to remove it - as you've shown it can be useful in scenarios where the user is very familiar with the project.
     
    daniel, Sep 24, 2013
    #5
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.
Similar Threads

  1. Case changes automatically in the Tag Name and Notes Field

  2. Two channels with same name ?

  3. NEWUNIT in part name field in Database view.

  4. Unit name and Tag names in toolkit question

  5. Lower case project name

  6. Retrieving Tag Name via Code in Logic Engine

  7. Toolkit Unit Name

  8. Max Size of Group Name

Loading...