Control devices?

[thenewwazoo]

Control devices?

[thenewwazoo]

Hi @sergei202, this project is only an implementation of the protocol, which doesn't have a concept of a device as such. I wrote a bit about it in the readme. This library is what you would use to communicate in order to control a dimmer, but the logic to do that would live elsewhere. It might be worth looking around to see if there are any other users of this library that could be inspiration.

[sergei202]

For anyone who arrives here looking for the same thing, it's actually very easy to control devices:

Get your device object from bridge.getDeviceInfo(), it'll look something like this:

  {
    Name: 'Cans',
    DeviceType: 'WallDimmer',
    AssociatedArea: { href: '/area/5' },
    href: '/device/11',
    SerialNumber: 64668928,
    FullyQualifiedName: [ 'Office', 'Cans'],
    Parent: { href: '/project' },
    ModelNumber: 'PD-6WCL-XX',
    LocalZones: [ { href: '/zone/8' } ],
    LinkNodes: [ { href: '/device/11/linknode/11' } ],
    DeviceRules: [ { href: '/devicerule/27' } ],
    AddressedState: 'Addressed'
  }

Then pass the LocalZones[0].href to client.request():

client.request('CreateRequest', '/zone/8/commandprocessor',
    {'Command':{'CommandType':'GoToLevel','Parameter':[{'Type':'Level','Value':50}]}}
).then(r => console.log('response=%o', r));

[thenewwazoo]

Thank you for documenting that! I've been chewing on it, and I think having a separate abstraction for physical devices, as a place to encode the kind of logic you've written here, is probably a good idea. Given that a few different devices use similar commands, I even think a device-command-protocol MVC-ish style approach would allow a clean implementation.