Everyone, following Mark's review of Indigo on www.automatedhome.co.uk I thought I would take a look myself. To do so I needed to integrate it with a Clipsal C-Bus system which is the primary system here at home.
At this point it is able to (at least on my network) dynamically generate Indigo devices based on your C-Bus configuration, provide support for relay and dimmer channels via the Indigo Mac UI and also monitors for changes on the C-Bus network which are then propagated back to Indigo. I have not yet tried Indigo Touch but I presume it should work.
The plugin requires a running instance of C-Gate somewhere on your network. There are a number of excellent guides on cbusforums.com to do this on devices other than Windows. Personally I have it running on a (debian) pi with ser2sock to avoid some of the pitfalls of java and serial ports. I would recommend you configure the C-Gate install to support remote connections (access.txt) and update both project.default and project.start values in C-GateConfig.txt to automatically connect C-Gate to your c-bus network.
The plugin code can be found at https://github.com/KieranBroadfoot/C-Bus.indigoPlugin. A zip can be downloaded from this site but you'll need to rename the resulting directory before you can copy into your Indigo install.
Some caveats:
- Only application 56 (lighting) is supported
- Config changes via Toolkit would not be noticed by this plugin
- Moving groups from dimmer to relay channels or vice-versa would would require some manual intervention
- I presume any group which is not attached to a physical C-Bus unit should be treated as a dimmer unit. This includes all-unit groups etc. I incorrectly use lighting groups for PIR activity from a Comfort alarm panel and for Sonos control from my DLTs hence the chosen default. Line 196 of plugin.py can be changed if you want all other groups to gain relay functionality instead.
Thanks to Matt and Jay for their help with my understanding of their API.
kieran.