This page last changed on Nov 22, 2009 by juha.

All,

after finishing the first implementation of Russound support, I was wondering how to combine this with my KNX switches. So instead of using the Russound panels to turn on a zone or switch the source for a zone, I would like to use my KNX switches todo that.

The idea is to have the KNX support within the controller listen to the KNX bus and when a particular group address is sent, I want the controller to trigger the Russound event to eg. turn on zone1.

We could think that further and combine this we status and rules which are stored on the controller eg. when home is in "sleep" mode and "button light1" is pressed only dimm "light 1" to 20% instead of turning it on to 100%. These are rule connections which are supported eg by linknx or the Gira Homeserver.

--Marcus

Very nice.... this way you can use your KNX panels to control your Russound system and it is all integrated. Nice. How do you plan on adding this support?

Posted by marcf at Nov 22, 2009 21:53

We went through the steps over Skype, here's the summary.

Rule engine is going to bind these pieces together.

  • We have an API for sending remote commands in Boss 1.0
  • We have an API for receiving device updates and server push to consoles in Boss 2.0

In Boss 3.0 we will review these APIs with the rule engine binding in mind.

The use case is:

If state update (X) KNX then send command (Y) Russound

The cycle here is the following:

  1. listen to KNX status update in the Boss KNX protocol implementation (basic flow being put in place in Boss 2.0)
  2. create command to change Russound on zone 1 (this is in place since Boss 1.0)
  3. push KNX status update to consoles (implemented in Boss 2.0)
  4. push Russound status update to consoles (implemented in Boss 2.0)

The steps 1. and 2. are bound together by a rule engine. The last two steps of pushing status updates to consoles occur as normal event processing as its being implemented for Boss 2.0 (by year end)

We should target the rule engine integration for Boss 3.0 (starting next year).

Posted by juha at Nov 22, 2009 22:18

That sounds great.

Combining this with internal states, which I mentioned above (eg. home in "sleep" mode), we are starting to catch up with "pro" solutions.

I just looked into the listener support for KNX with Calimero NG and was already able to receive the messages from my KNX bus within Boss.

Posted by mredeker at Nov 22, 2009 22:56

Boss 3.0? Shoot, did I miss a step?  Are you trying to quickly rev to 3.1 to follow in the glorious steps of windows? (Neil should cue in about right here)

Posted by marcf at Nov 23, 2009 08:32

Yes, I am trying to get up to 11.0 quickly so I can release Boss 2011.

Posted by juha at Nov 23, 2009 08:49
Document generated by Confluence on Jun 05, 2016 09:31