From: Michael S. <mi...@st...> - 2013-01-14 01:43:58
|
On Jan 13, 2013 12:43PM, Marc wrote: > > On Sun, Jan 13, 2013 at 12:24:29PM -0600, Michael Stovenour wrote: > > > > Nice! Thanks for testing this out for me. I'm sure I'll break i1 and i2 > > support at some point and will need an environment to duplicate the issues. > > Would it make your life easier if you had an I1 device? I can likely mail > you one, or even order you one on the smarthome website and ship it to your > place :) I might take you up on an i1 device or two. Could trade some i2 devices for them. But I also don't mind buying one or two if I can. Do you have a link where I can order an i1 device from Smarthome? I was under the impression they were no longer available. > > Now specifically why that command does "nothing" is a bug. The tie_event is > > missing from the code that sets up the voice commands. I've corrected that > > in my local copy, but now the i2CS device just NACKs the link add. I would > > argue that there is no use for this voice command. sync_links() will add > > It works/worked for I1 and was useful, but it's ok if it doens't/can't work > for I2CS. Can you explain how it is useful for i1 devices assuming that "sync links" and "sync all links" will install the same link? I'm considering removing it but would never do that if you or others say it is useful. Again I'm probably showing my lack of understanding for real Misterhouse/Insteon use cases. Having a list of use cases is a major help for development. Beyond helping with testing, it helps the developer ensure that new code doesn't break a valid use case. In my professional world use cases are the cornerstone of all development activity. Sincerely, Michael |